[RFC] More *.bazaar-vcs.org sites

[Ian Clatworthy]

Martin Pool wrote:

> I've been thinking we should turn www into a more structured web site,
> rather than a wiki, to give a more finished feel.  Matthew Nuzum was
> interested in helping run Drupal, which Ubuntu.com runs, and at least
> some of whose developers are happily using Bazaar.  Ian, maybe you
> could talk to Matthew about getting eg staging.bazaar-vcs.org running
> drupal so we can try it out and prepare some text?

I agree, so sure.

>> * dev.bazaar-vcs.org (blueprints, API doc, other developer stuff)
>> * plugins.bazaar-vcs.org (there's a lot of these now)
> 
> Yes, maybe a little php or python application that kept a more
> structured list of them would be good.

Hmm, my RFC was more about *what* sites we wanted, rather than how we
tracked them though. I think having the main site a bit more structured
is great, but that implies ultimately moving some pages onto other
sites, logically if not physically. And if we're going to do that and
update URLs around the place (Launchpad's Blueprint Tracker, FreshMeat
for plug-ins, etc.), then best to do it once and get it right/stable
prior to 1.0.

I still want a wiki or two for specs, plugins, etc. Do we go with just
one (community.bazaar-vcs.org say) or get a little more audience
filtered immediately with two or more?

Specs on a wiki works fine IMO. Putting them, roadmaps and other
goodness on a developer-centric site would be nice. There are quite a
few projects that do the same: http://developer.gnome.org/,
http://techbase.kde.org/ (formerly http://developer.kde.org) ,
http://developer.mozilla.org/, etc.

For the other stuff, my leaning is towards a Wiki, either the same one
or another one, but I feel other options need to be briefly considered
at least ...

I *really* like our plug-in architecture and the Web page currently
lists 64 plug-ins, excluding the obsolete ones! Currently though, there
isn't much information about most of them, short of downloading them and
looking for READMEs, etc. The simple solution is to stick with a Wiki
and add a bit more structure, e.g. a page for each plug-in based on a
common template. But perhaps there's better technology for this sort of
database, e.g. one that supports ratings, comments, popularity, etc.?

There's no hurry on this. We can get staging.bazaar-vcs.org setup first
and go from there. But I felt it was worth asking the question about
what sites our community would like to see. To date, the response has
been silence. I guess that means "whatever Martin thinks". :-)

Ian C.