This is the mail archive of the
mailing list for the binutils project.
web sites (was: Re: git is live)
- From: Paul Smith <psmith at gnu dot org>
- To: John Darrington <john at darrington dot wattle dot id dot au>
- Cc: Joel Brobecker <brobecker at adacore dot com>, Fred Cooke <fred dot cooke at gmail dot com>, GDB Development <gdb at sourceware dot org>, Binutils Development <binutils at sourceware dot org>
- Date: Fri, 25 Oct 2013 14:27:32 -0400
- Subject: web sites (was: Re: git is live)
- Authentication-results: sourceware.org; auth=none
- References: <20131024073607 dot GA4688 at adacore dot com> <87hac6bwsu dot fsf at fleche dot redhat dot com> <52D0D88B-0741-4F41-A02F-893AC20D4B2D at adacore dot com> <C94C27E1-3182-45B0-B332-2FDFF971DD6D at adacore dot com> <20131024170536 dot GI4688 at adacore dot com> <87wql2a8lm dot fsf at fleche dot redhat dot com> <20131024175200 dot GJ4688 at adacore dot com> <CABZhLO_UJiBEVUswkfwdRB-7y5aAqLujxdnUL513HJHZFgEEMA at mail dot gmail dot com> <1382703078 dot 13360 dot 64 dot camel at homebase> <20131025123848 dot GO4688 at adacore dot com> <20131025172536 dot GA4054 at intra>
- Reply-to: psmith at gnu dot org
On Fri, 2013-10-25 at 19:25 +0200, John Darrington wrote:
> Why have two different web sites? Have one as the canonical site, and
> make the other redirect to it.
The GNU project definitely will want to preserve the gnu.org page: they
prefer to have www.gnu.org/software/<pkg>/ resolve to something
appropriate. It could be just an overview and point to the other site
for details, I guess: I'm not sure what the politics are there. I'm not
sure what the history is behind the other site so I can't speak to that.
One note: the gnu.org site would be a lot nicer if it used the standard
template HTML. Compare, for example:
Ditto for binutils. In addition to the standard look and feel stuff, it
uses SSI to allow changing of banners for announcements etc.
It turns out to be quite simple to make your GNU site match the rest.
You can get this via CVS:
cvs -d :pserver:firstname.lastname@example.org:/web/www co www/server/standards
then look at the boilerplate.html file and replace the appropriate bits
with info on your project (there are good directions embedded in
comments in the HTML file), then replace your project's web CVS
index.html with the result.
For the second and subsequent times where you want to update your
project's page, you can use the patch-from-parent script (also available
at the above site). Or do it by hand; it's usually not a big deal.