Now that the project has attracted a little bit of attention it's a good time to get a little bit more serious about putting up some documentation for new users/people evaluating the RDKit. Getting a "little bit more serious" shouldn't be too tricky since I've done very little along these lines so far. :-)
I'd like for it to be possible for people other than Santosh and myself to contribute to this effort with howto's or cookbooks, or whatever. I'm looking for suggestions for how to do this. Some criteria that are important to me: - It has to be more or less trivial for the contributors to use. Having any remotely substantial barrier to entry for contributing is, IMO, not going to work. - The system needs to support the concept of users. This project is intended to be open and transparent. To me transparent includes "identifying yourself". - It needs to be easy to add users (or to have users add themselves) - There needs to be some way to get the data out of the system (e.g. export to HTML or XML or whatever). I'd like to be able to easily do backups and I'm not particularly interested in getting locked into a particular piece of software/hosting scheme. - It needs to be relatively easy to install and very easy to administer. The obvious solution is to use a wiki, some other type of cms, or a multi-user blog with a comment system. I'm not enamored of the blog idea because I don't think it contributes that much value beyond a publicly archived mailing list. I played around a little bit with the wiki provided by sourceforge for projects and it seems too slow and painful to actually use. Plus the permissions model appears to be either "anyone can write" (I assume this means anonymous users) or "only project members can write". That's too coarse grained. Does anyone have suggestions? Thanks, -greg
