> 1 - requirements
> ================
> 
> In order to choose the best possible wiki implementation, we need to
> know our requirements. So what features do you think are essential or
> good to have? What syntax would we prefer to use?
> 
> I myself am a big fan of reStructuredText, which is quite simple,
> easy to pick up, highly readable, and has a good featureset. Plus, it
> is also reusable in other contexts (it is for example widely used in
> documentation of Python libraries). MediaWiki, MoinMoin and Trac have
> support for rst.

I'm not overly concerned about what wiki we use.   But may I suggest we 
approach gentoo-wiki to see whether they would like to be involved.

> 
> Some others:
> 
> - active upstream (bug fixes, security updates)
> - free open source software
> - ACLs
> - spam prevention measures
> - attachments (to upload screenshots for example)
> - feeds
> 
> Other distros and open source projects surely have had the same
> considerations. Can we find out and learn from them?
> 
> 
> 2 - maintainers
> ===============
> 
> Who is volunteering for maintaining the wiki? We need editors and
> moderators, people who look out for quality control and take care of
> spam removal. So let's get together a team. I'm sure if we ask on the
> forums we'll get some users interested as well.

I would like to help as I may.   Hopefully we can get a good body of users to 
help as well.  I'm of the firm belief that it will be users who should make 
this idea either fly or crash down hard.    Dev's have official means of 
documenting stuff. 

> 
> 
> 3 - edit access
> ===============
> 
> Do we keep to the original "free for all" model, with all the spam
> that includes, or do we go with registered users only? I think the
> latter is the smarter option. I also think we will want to mark
> certain pages "official" and lock down editing rights.
> 

Registered users only please.

> 
> Is there anything else we should consider before getting started?

What project should we create this under.

gdp is for official documentation so I don't think it should be under that but 
it could very well be under userrel.  Or it could be a new project.

I also have some other ideas that I would like to implement once I get around 
to brain-dumping them.   So I will simply ask this question.

Are there any complimentary services we could offer users besides a wiki?  
Maybe best to just think about this and not answer it here.

> 
> Cheers,

Alistair