all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [ART] Website mockup rev2
Date: Wed, 25 Feb 2015 22:39:35 +0100	[thread overview]
Message-ID: <87egpd4qnc.fsf@gnu.org> (raw)
In-Reply-To: <CAJ=Rwfa1xDo_khwm5QcxqVBEoVYBhioOEs21V7SCEtiAF9w5hw@mail.gmail.com> (David Thompson's message of "Wed, 25 Feb 2015 15:34:30 -0500")

"Thompson, David" <dthompson2@worcester.edu> skribis:

> On Wed, Feb 25, 2015 at 3:28 PM, Andreas Enge <andreas@enge.fr> wrote:
>> On Wed, Feb 25, 2015 at 01:34:51PM -0500, Luis Felipe López Acevedo wrote:
>>> I think that GuixSD should have its own website (at guixsd.gnu.org) and
>>> Guix should stay on gnu.org/s/guix.
>>
>> Honestly, I do not quite understand why we would need two different websites.
>
> Yeah, I'm not convinced we need two sites, either.

OK but there’s the problem of the logo and focus.  Should perhaps the
main page be about GuixSD, and a sub-page would be about Guix as a
package manager, and such?  (Similar to what nixos.org does.)

> IMO, managing the site via gnu.org's antiquated CVS deployment setup
> is undesirable for the long term.  As assistant chief webmaster I've
> tried to influence a migration to git and more modern web development
> practices, but it's not going to happen.  I propose that we do as
> Mediagoblin does: Maintain a completely separate web server that we
> have full control over, and redirect http://gnu.org/s/guix to that web
> server.

That’s a terrible state of affairs, and I hope the FSF webmasters
realize that and realize that something must be done about it.

There’s the possibility of having a gnu.org sub-domain.  From a
practical perspective, we can probably get something on chapters.gnu.org
(administered by fellow hackers Nacho & José) very easily.  From there
we use either a static site generator or do something more Guilish if
someone is tempted.  We’d have a lot of flexibility.

How does that sound?

Ludo’.

  parent reply	other threads:[~2015-02-25 21:39 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 [this message]
2015-02-25 22:27       ` Luis Felipe López Acevedo
2015-02-25 21:46     ` Ludovic Courtès
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=87egpd4qnc.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=dthompson2@worcester.edu \
    --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.