One of the discussions on yesterday's irc meeting involved the (lack of) Koha documentation. I agreed to start a discussion of what is needed, who should contribute, what format(s) will be used, etc. I'd like to start the discussion by proposing that there are really four different types of documentation that need to be produced: 1. Documentation for OPAC users. This would have to be provided as online help, since OPAC users are not going to have access to any other type of documentation. 2. Documentation for systems administrators. This would encompass installing Koha and setting the parameters, as well as maintaining the system. This documentation could (should?) be in several formats. 3. Documentation for librarians (staff). While much of the Koha intranet tasks will be familiar to many librarians, librarians who have never used an automated system before will need help. Again, this should probably be available in multiple formats. 4. Documentation for developers. For those who want to join the development effort, we need database schema, good perldocs in the code, etc. Anything else I've forgotten? Any comments? I'd also like to start emphasizing that _everyone_ on this list can help. I'm particularly interested in hearing from those of you who feel you have no clue as to how Koha works. I'd like to start collecting a list of questions that we need to address, and that includes even the simplest questions. There's no such thing as a "dumb" question. If you have a question about Koha, chances are good that many other people have the same question, and the documentation will need to have a clear answer for that question. So send 'em in. (If you're shy, send directly to me -- shedges@skemotah.com -- but usually it's better to send to the list, because your question might remind people of other questions.) -- Stephen Hedges Skemotah Solutions, USA www.skemotah.com -- shedges@skemotah.com