Bug#276057: ITP: mediawiki -- Wikipedia wiki engine

[Roland Mas <lolando@debian.org>]

[Snipped Evan from Cc: list]

Andreas Tille, 2005-07-19 12:35:21 +0200 :

>> Besides apache config changes in 13) i don't understand,
>> toots@rastageeks.org's work is nice. I agree with real need for
>> team maintainance and scn to do a good job. You have my GO to open
>> the project on Alioth.

> OK, as I said I'm waiting a short time for lolando, but I guess it
> will not hurd him if I just start asking for the project on allioth
> to speed things up.  On the other hand I would not really love to be
> "Project Manager" of a project I'm not really managing (see above).
> Lolando, just speak up if you are reading your mail but has no time
> for any other work and give me a "go for it" if you think this is
> the best way.  For all others, who are no DDs but interested in
> doing something just post your alioth logins to this thread.

I absolutely do think Alioth is the way to go.  I'm potentially
swamped for the next month (meaning I don't know yet how much time
I'll have) and then I'll be touring the world from September to
November (included), but I'll be glad to act as a co-maintainer.

  As maintainer of Gforge, I do have some experience of PHP apps, as
well as database maintenance.  I haven't really had a look into
Mediawiki yet, though (apart from the five minutes I spent looking for
where to disable the "escape frames" feature).

  One word: something I've seen with Gforge, and which is likely to
happen with Mediawiki too, is that I know of several instances of the
application that are patched for integration in wherever they're run,
with local patches for various reasons (that includes Alioth, two
instances I run at my part-time job, and one I help run as part-time
freelance).  I therefore find it would be good to use Arch (or
Bazaar), so that people can maintain their local branches and
contribute changesets in an easy way.

Roland.
-- 
Roland Mas

Sauvez les castors, plantez des arbres.