[pylucene-dev] Re: Wiki?, was Re: status of pylucene & mod_python
ofer at smarter.com
Mon Mar 26 08:05:11 PST 2007
> -----Original Message-----
> From: pylucene-dev-bounces at osafoundation.org
> [mailto:pylucene-dev-bounces at osafoundation.org] On Behalf Of
> Andi Vajda
> Sent: Monday, March 26, 2007 8:58 AM
> To: Pete
> Cc: pylucene-dev at osafoundation.org
> Subject: [pylucene-dev] Re: Wiki?, was Re: status of pylucene
> & mod_python
> On Mon, 26 Mar 2007, Pete wrote:
> >> OSAF has several wikis already and would probably be open
> to hosting
> >> one for PyLucene. I just don't want to maintain it myself.
> Any volunteers ?
> > What's involved?
> - setting up the site
> - permissioning contributors
> - fighting spam
> - editing entries for accuracy
> - maintaining some sort of structure/consistency so things
> can be found
> - weeding out obsolete entries, dead example code, etc..
> - and more
I'm sensing that you feel overwhelmed... :)
The above list (minus points 1 and 2) are generally done by a small
community, not a single admin. In other words, the same people who are
spending so much time on this list.
If you active the PyLucene wiki, and just ensure that edits require being
logged in (that way abusive/spammy edits can be traced to an account and
disabled), we can take it from there. Worst case isn't worse than no wiki
It helps if your wiki app uses a captcha during registrations to thwart
automated spammers. Between that and requiring users to be logged in during
edits, we stand a great chance.
More information about the pylucene-dev