From: sirgazil <sirgazil@zoho.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 26006@debbugs.gnu.org
Subject: bug#26006: [Website] Integral update proposal
Date: Fri, 16 Jun 2017 09:46:31 -0500 [thread overview]
Message-ID: <493e9e04-fc8f-2a77-0927-a862f174aa55@zoho.com> (raw)
In-Reply-To: <877f0cjtul.fsf@gnu.org>
On 16/06/17 02:05, Ludovic Courtès wrote:
> Howdy!
>
> sirgazil <sirgazil@zoho.com> skribis:
>
>> On 15/06/17 02:59, Ludovic Courtès wrote:
> [...]
>
>>> On a more practical level, what would you like the workflow to be like
>>> from there on? I would prefer hosting the source on gnu.org rather than
>>> {bitbucket,gitlab,github}.com and I would also prefer Git over
>>> Mercurial, but I don’t want to be a hindrance so I’m open to
>>> discussions. :-)
>> No worries. The idea was to move the useful parts to guix-artwork on
>> gnu.org.
>>
>> To be honest, when I started this version of the website I was just
>> motivated on implementing the designs and exploring a way to organize
>> modules in a haunt website so that data, builders and templates were
>> separated. But I was not very interested in dealing with git workflows,
>> and strict commit messages. Sorry about that :)
> No problem, this is perfectly understandable (also I’m fine with relaxed
> conventions on guix-artwork.git).
>
>> So, what do we do? Create a branch on guix-artwork and drop these files
>> there to complete what is missing? I don't know...
> Yes we could do that. Should we investigate the missing bits first? I
> haven’t taken the time to do it yet, sorry about that.
Maybe you should learn how to do mitosis. Another civodul would come in
handy. Until that, take your time, no problem :)
I'm fine with investigating the missing parts before or after moving to
guix-artwork.git.
--
https://sirgazil.bitbucket.io/
next prev parent reply other threads:[~2017-06-16 14:30 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 2:02 bug#26006: [Website] Integral update proposal sirgazil
2017-03-07 11:16 ` ng0
2017-03-07 12:53 ` Catonano
2017-03-07 14:13 ` Ludovic Courtès
2017-03-10 16:46 ` sirgazil
2017-03-10 21:05 ` Ludovic Courtès
2017-10-01 11:02 ` ng0
2017-10-02 7:50 ` Ludovic Courtès
2017-10-02 8:36 ` ng0
2017-10-02 9:10 ` Ludovic Courtès
2017-06-08 19:06 ` sirgazil
2017-06-13 22:08 ` Ludovic Courtès
2017-06-14 20:36 ` sirgazil
2017-06-15 7:59 ` Ludovic Courtès
2017-06-16 2:52 ` sirgazil
2017-06-16 7:05 ` Ludovic Courtès
2017-06-16 14:46 ` sirgazil [this message]
2017-06-17 4:57 ` Catonano
2017-06-17 7:16 ` Catonano
2017-06-17 15:46 ` sirgazil
2017-06-17 16:09 ` Catonano
2017-06-17 16:41 ` sirgazil
2017-06-17 17:12 ` Catonano
2017-06-17 18:11 ` sirgazil
2017-06-17 15:19 ` sirgazil
2017-06-17 15:19 ` Catonano
2017-07-29 17:53 ` Ludovic Courtès
2017-08-01 22:13 ` sirgazil
2017-12-06 17:10 ` bug#26006: New web site is on line! Ludovic Courtès
2017-12-06 17:55 ` Alex Sassmannshausen
2017-12-06 22:10 ` Adonay Felipe Nogueira
2017-12-06 22:10 ` Adonay Felipe Nogueira
2017-12-07 8:54 ` Ludovic Courtès
2017-12-07 3:01 ` sirgazil
2017-12-07 9:16 ` Chris Marusich
2017-12-07 17:10 ` pelzflorian (Florian Pelz)
2017-12-07 20:58 ` Ludovic Courtès
2017-12-08 18:42 ` Quiliro Ordonez Baca
2017-12-08 19:07 ` pelzflorian (Florian Pelz)
2017-07-01 14:26 ` bug#26006: [Website] Integral update proposal Ludovic Courtès
2017-07-04 20:00 ` sirgazil
2017-07-04 20:09 ` Catonano
2017-07-05 0:45 ` sirgazil
2017-07-04 21:24 ` Ludovic Courtès
2017-07-05 1:26 ` sirgazil
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=493e9e04-fc8f-2a77-0927-a862f174aa55@zoho.com \
--to=sirgazil@zoho.com \
--cc=26006@debbugs.gnu.org \
--cc=ludo@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).