On Wed, Aug 02, 2006 at 09:55:02PM +0200, Benedikt Böhm wrote:
> Hi Community,
>
> as some of you may already know there is an ongoing effort to move
> linux-vserver.org to MediaWiki, the software used by Wikipedia. The
> new installation can temporarily be found at http://vwiki.croup.de
> (please do not register for now, email isn't setup yet)
>
> There are still many things that need to be discussed, some of them
> not entirely related to the new wiki, but it is probably the best to
> do things at once ;)
>
> The following things came to my mind where things still need to be
> decided and discussed:
>
> * SCM Repository
>
> This is mostly a question for Bertl, since he is managing the current
> releases. AFAIK git was suggested and i think it is the best choice for
> kernel development, but i don't have a preference here.
I don't think that I have a problem with a git repository in
the (near) future, just do not expect too much from it :)
> Another question would be if we should also setup Subversion/CVS
> (rather the former ;) for project hosting (util-vserver, libvserver,
> vserver-utils, openvcp, etc)
svn seems nice to me, had some bad experiences with mercurial
but cvs might be fine too, at least it does not require apache
to check out versions (note: for many distros svn requires
apache to be installed :)
> * Bug reporting
>
> Do we need a central instance here like Bugzilla, or do we manage all
> bugs via mailing list/irc as-is?
we already have bugs.linux-vserver.org, which seems to have
been used for something different lately :) i.e. I will remove
it from the name services soon ...
> * Public Relations
>
> Yeah, i know, anyone wants to do PR, but IIRC Bertl asked some time
> ago for PR help, so maybe we can sort this out and build a team
> responsible for PR...
that would be a nice thing ... I'm willing to check/proof
stuff if there is a need for it ...
> * Wiki Team
>
> One thing we really need, IMO. There should be a bunch of people
> maintaining locked pages, and review changes on a regular basis to
> keep the wiki easy to use and sorted...
do we really need 'locked' pages? anyway, the idea of some kind
of maintanence team here sounds appealing, many folks are already
helping with the wiki on a regular basis, like powerfox, derjohn, ...
> * Planet VServer
>
> I'm not sure how many people in the community do blogging but it may
> be worth thinking about an aggregator, since it nearly is no overhead
> to maintain and a nice (PR) thing to have ;)
sorry, can't help here, neither I nor my dog have a blog :)
> Beside discussing there is also real work to do: Move old wiki content
> to new mediawiki
>
> * Old wiki pages
>
> Bertl already said to prepare a sqldump of the current wiki to get at
> least _all_ content, since there does not seem to be a list-all-pages
> function in the current wiki.
yep, just remembered and will send it to you shortly ...
> * New structure
>
> The structure currently applied at vwiki.croup.de is by no means
> decided, however it fits the overall requirements quite good IMO.
> Nevertheless feel free to comment on that too.
>
> For all old pages there should be redirects to the new location of
> this piece of information, so that google links won't get invalid.
we should see that we get the new wiki in place quite soon
which means that most pages should use identical urls, and
those which do not fit, may become internal redirects to a
static version of the old wiki pages, which will be faded
out over time, no?
> Since this is the most time-consuming task, please drop a note if you
> are willing to help moving content and adapting the (sometimes) new
> wiki formatting.
>
> New structure in detail:
>
> * Paper: Bertl will review and update the current paper
> * FAQs: Many current pages can be consolidated (derjohn?)
> * Downloads: See below for Download Archives
> * Documentation: the biggest part, most help needed here, especially
> different distros etc..
> * Participate/Report Bug: Write down detailed information about bug
> reporting (testme/testfs etc)
here I definitely prefer if bug reports go to the mailing
list, so that we have something to work with, no problem
if they get submitted there via some bug tracker or directly
as long as they get there ...
> * Projects: list projects related to linux-vserver (util-vserver,
> vserver-utils, etc)
> * Related Projects: Gather all related projects, and probably do a
> comparison finally (wikipedia has a preliminary comparison, btw)
>
> Rest should be self-explanatory and is also quite easy to create..
>
> * Download archives
>
> Currently there are so many locations for utils, patches, etc, that
> confuses users. I suggest a central archive organized in a similar way
> to kernel.org where all developers can put their stuff. These archives
> should be reachable by HTTP/FTP and its structure should documented on
> the Downloads page...
okay, I think I can provide that, similar to the existing
http://vserver.13thfloor.at/* places ...
> I'd volunteer to setup and maintain the infrastructure for all parts
> listed above, but I seriously need help during migration and future
> wiki updates.
>
> TIA for comments and your time
thanks for your efford,
best,
Herbert
> Bene
> _______________________________________________
> Vserver mailing list
> Vserver@list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
Received on Thu Aug 3 17:00:40 2006