all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Luis Felipe López Acevedo" <felipe.lopez@openmailbox.org>
Cc: guix-devel@gnu.org
Subject: Re: [ART] Website mockup rev2
Date: Wed, 25 Feb 2015 22:46:23 +0100	[thread overview]
Message-ID: <87pp8x3brk.fsf@gnu.org> (raw)
In-Reply-To: <1424889291.1437.61.camel@openmailbox.org> ("Luis Felipe López Acevedo"'s message of "Wed, 25 Feb 2015 13:34:51 -0500")

Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:

> El mié, 25-02-2015 a las 14:56 +0100, Ludovic Courtès escribió:

[...]

>> Regarding the section at the bottom, I wonder whether/how it could be
>> implemented in practice.  For instance, we’re not going to move to
>> GitHub just for that, and I’d rather not call out to openhub.com or
>> similar to get stats.  Yet, I’m not sure the cgit/gitweb instances at
>> Savannah provide a JSON API to extract this kind of data.  What are your
>> thoughts on this?
>> 
>> Maybe the answer is that we’ll have to work with the Savannah hackers to
>> add whatever service provides such an API to Savannah, and in the
>> meantime live without that section.
>
> I just thought that a JSON list of recent commits could be generated
> with a script+libgit2 (somewhere, once a day) and then put the JSON file
> in the website repository. But if that's expensive or just silly, I
> don't see any problem in leaving that section out.

If we go for self hosting as David suggests, we can do whatever sounds
appropriate on our own server.

>> One thing we need to decide is whether we keep the GuixSD web site
>> separate from gnu.org/s/guix.  I tend to think that it should be
>> separate (we can ask for guixsd.gnu.org), with the Guix web page mostly
>> unchanged, but I’m slightly concerned about overlap and the risk of
>> bitrot.  WDYT?
>
> I think that GuixSD should have its own website (at guixsd.gnu.org) and
> Guix should stay on gnu.org/s/guix.

Guix-specific info could go to a sub-page of the GuixSD site, I think.
This would avoid overlapping.

>> How can we make progress from here?  Would you be able to do the
>> CSS/HTML implementation of the web site?  What else is needed?
>
> I don't know if Pierre-Antoine Rault (rigelk) is still willing to take
> on implementation :)
>
> In any case, I've worked in "mockup-to-implementation" before¹, using
> Web frameworks like Django² or static-site generators like complexity³.
> I don't have any formal training, but I'm willing to help.

I would go either static (complexity or even Skribilo) or somehow use
Guile’s web server, but then again I’m not going to do it so I’m open to
whatever seems appropriate.

> As for what else would be needed for GuixSD website, 
>
> - A GuixSD project in Savannah
>     - CVS repository for website
>     - git repository for website source

Problem solved if we use our own server.  The Git repo for the site’s
source can go in a sub-directory of guix.git on Savannah.

Thanks,
Ludo’.

  parent reply	other threads:[~2015-02-25 21:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-21  2:02 [ART] Website mockup rev2 Luis Felipe López Acevedo
2015-02-21  7:31 ` Ricardo Wurmus
2015-02-21 14:10   ` Adam Pribyl
2015-02-23 21:06 ` Andreas Enge
2015-02-25 13:56 ` Ludovic Courtès
2015-02-25 18:34   ` Luis Felipe López Acevedo
2015-02-25 20:28     ` Andreas Enge
2015-02-25 20:34       ` Thompson, David
2015-02-25 21:13         ` Andreas Enge
2015-02-25 21:39         ` Ludovic Courtès
2015-02-25 22:27       ` Luis Felipe López Acevedo
2015-02-25 21:46     ` Ludovic Courtès [this message]
2015-02-25 22:01       ` David Thompson
2015-02-26  9:36         ` Taylan Ulrich Bayırlı/Kammer
2015-02-26 20:15           ` Thompson, David
2015-02-26 18:43         ` Ludovic Courtès
2015-02-26 20:03           ` Luis Felipe López Acevedo
  -- strict thread matches above, loose matches on Subject: below --
2015-02-21 20:39 Felix Friedlander

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pp8x3brk.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=felipe.lopez@openmailbox.org \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.