From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: [ART] Website mockup rev2 Date: Wed, 25 Feb 2015 22:46:23 +0100 Message-ID: <87pp8x3brk.fsf@gnu.org> References: <1424484170.6354.13.camel@openmailbox.org> <87bnkixffw.fsf@gnu.org> <1424889291.1437.61.camel@openmailbox.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36913) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YQjmn-0003cN-PN for guix-devel@gnu.org; Wed, 25 Feb 2015 16:46:30 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YQjmk-00014L-GU for guix-devel@gnu.org; Wed, 25 Feb 2015 16:46:29 -0500 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:52290) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YQjmk-00014H-CR for guix-devel@gnu.org; Wed, 25 Feb 2015 16:46:26 -0500 In-Reply-To: <1424889291.1437.61.camel@openmailbox.org> ("Luis Felipe =?utf-8?Q?L=C3=B3pez?= Acevedo"'s message of "Wed, 25 Feb 2015 13:34:51 -0500") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Luis Felipe =?utf-8?Q?L=C3=B3pez?= Acevedo Cc: guix-devel@gnu.org Luis Felipe L=C3=B3pez Acevedo skribis: > El mi=C3=A9, 25-02-2015 a las 14:56 +0100, Ludovic Court=C3=A8s escribi= =C3=B3: [...] >> Regarding the section at the bottom, I wonder whether/how it could be >> implemented in practice. For instance, we=E2=80=99re not going to move = to >> GitHub just for that, and I=E2=80=99d rather not call out to openhub.com= or >> similar to get stats. Yet, I=E2=80=99m not sure the cgit/gitweb instanc= es at >> Savannah provide a JSON API to extract this kind of data. What are your >> thoughts on this? >>=20 >> Maybe the answer is that we=E2=80=99ll have to work with the Savannah ha= ckers 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=E2=80=99m 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=C2=B9, using > Web frameworks like Django=C2=B2 or static-site generators like complexit= y=C2=B3. > 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=E2=80=99s web server, but then again I=E2=80=99m not going to do it s= o I=E2=80=99m open to whatever seems appropriate. > As for what else would be needed for GuixSD website,=20 > > - 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=E2=80= =99s source can go in a sub-directory of guix.git on Savannah. Thanks, Ludo=E2=80=99.