unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: ng0 <contact.ng0@cryptolab.net>
Cc: guix-devel@gnu.org
Subject: Re: website question
Date: Wed, 05 Apr 2017 20:38:21 +0200	[thread overview]
Message-ID: <87zifu1yzm.fsf@elephly.net> (raw)
In-Reply-To: <20170403120802.27zef5ueqnj5mcbh@abyayala>


ng0 <contact.ng0@cryptolab.net> writes:

> Most initial texts for pragmatique's website are now done.
> As I don't want to introduce it with a plain white one-page site, I
> thought about what I want to use. Jinja (taler.net) or Guile (guix,
> guile). The software part of the project is based on and into Guix, so
> it would be good to make use of Guile where possible. The only reason
> I'd choose taler.net template for is that it already has a solution for
> #26302 (translation of texts)[0].
>
> As I dislike keeping changes which could be beneficial for others:
> If I start with an individual repo, could patches which would fix 
> for example the translation problem still be applied "somehow" to
> guix-artwork although both repositories share no root but just similiar
> files?
> Or do I have to commit again into guix-artwork then to share the
> changes?
>
> It makes no sense for me to re-use the guix-artwork repository as too
> much content (graphics, texts, posts) will diverge from the one Guix
> uses. I guess there will be maybe 20% code of guix-artwork.git/website/
> left over.
>
> What do you suggest to do?

I don’t understand what this message is about.  Is there some context
I’m missing?

-- 
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

  reply	other threads:[~2017-04-05 18:38 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 [this message]
2017-04-05 20:17   ` Catonano
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=87zifu1yzm.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=contact.ng0@cryptolab.net \
    --cc=guix-devel@gnu.org \
    /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).