From: Catonano <catonano@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: website question
Date: Wed, 5 Apr 2017 22:17:47 +0200 [thread overview]
Message-ID: <CAJ98PDw=mv4VubfOpmGyEa_M9rW0QRd3H5rxgMg1YrndYAYg+g@mail.gmail.com> (raw)
In-Reply-To: <87zifu1yzm.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]
2017-04-05 20:38 GMT+02:00 Ricardo Wurmus <rekado@elephly.net>:
>
>
> I don’t understand what this message is about. Is there some context
> I’m missing?
>
Ok, this is how I understand this issue
ng0 is preparing their web site for promoting their project (a live distro
based on Guix)
One feature ng0 wants for their site is the ability to show the contents of
such site localized in several languages.
Like the Taler site https://taler.net/de/index.html (only parts are
actually translated, as far as I can tell)
It seems that Artanis and Haunt have no such functionality
So ng0 is thinking to extend those and implement that functionality
themselves
Because they want something Guile based
So they're asking how to proceed in order to make the result of such effort
available not only to their site, but to the general Artanis/Haunt
community.
This is the context, to the extent that I'm aware of it
My suggestion would be to extend Artanis/Haunt and send patches upstream.
The Guile web site will catch up eventually.
Otherwise, ng0, you could manage to produce some patches that apply to the
common subset of files (common between Artanis/Haunt and your site)
[-- Attachment #2: Type: text/html, Size: 1772 bytes --]
next prev parent reply other threads:[~2017-04-05 20:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 12:08 website question ng0
2017-04-05 18:38 ` Ricardo Wurmus
2017-04-05 20:17 ` Catonano [this message]
2017-04-05 20:49 ` ng0
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ98PDw=mv4VubfOpmGyEa_M9rW0QRd3H5rxgMg1YrndYAYg+g@mail.gmail.com' \
--to=catonano@gmail.com \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).