On mer, 2003-01-29 at 20:09, Takuya Murata wrote:
Wikipedia is great because not only it is free, open-content but also because it is democratic. People made decision in their own. People go where they want to go without discussion. The important distinction is wikipedia is the place where not the rulers listen to people's demands but all of people rule.
Democracy is a two-way street, and the way to get involved is, well, to get involved. ;) This mailing list is open to subscription and can be read on the web by anyone. Our source repository can be examined on the web or by anonymous CVS access, and anyone showing interest and with a sourceforge account can be given commit access.
Pick a task, find an itch to scratch, and get working on it. The only reason I'm here is because I got involved in the Esperanto Wikipedia and wanted to modify the software to better support my favorite language. If I do anything else here, it's just to provide the infrastructure for the supersigno-conversion code. Now, if only I had the time to write some articles! ;)
Sorry I am just talking about something abstract. But this is why I felt the management should be more democratic. And again I don't know practical way. Developing wikipedia system in wiki? I don't know.
Oh, it can be done in theory: http://www.usemod.com/cgi-bin/mb.pl?FileReplacement
I dunno if we want to do that for our source, though...
Oh, anyway, can we set up the wikipedia for developing? Like hacker.wikipedia.org
I'd prefer to work on meta.wikipedia.org. But that's just me.
I like to document more information about the wikipedia software and also it would be nice if there is the place the developers find the tasks wikipedias want and exchange brainstorms. (Well, there is sourceforge. But no one is using it anyway. Most of stuff in sourceforge seems outdated like bug reports several months ago)
Those bug reports are still open because they're still not fixed. :) There are a lot of little parser errors, and little search errors, that can be best fixed by replacing the horribly fragile subsystems they're in with clean, testable code.
-- brion vibber (brion @ pobox.com)