On Mon, Aug 16, 2010 at 08:37:09PM -0700, tosmaillist.neophyte_...@ordinaryamerican.net wrote: > I'm looking for other people to express their opinions of the efficacy > of using a wiki to create a book. I agree with Matthew, there is a > need for controlled branching so there is an ability to carefully > discuss alternative contributions.
I'm snipping out your good suggestions about using the [[User:]] namespace for alternative editing, just wanted to put a +1 vote to that idea. It's a bit more inconvenient than cloning a code repository, but we're only ever going to be talking about a few dozen wiki pages so it might be workable. For the 0.8.1 release my recommendation is to focus on the content improvements and see what we can do to improve our tool experience with what we have. For most of the people involved, this was their first time doing this much content work in a wiki. I think we can improve this experience to let us focus on the content work that needs doing. For example, we can arrange some training sessions with other MediaWiki expert users (via IRC.) After 0.8.1 is released we can dive more in to a tool review. In the meantime, we should capture our reactions to the situations, any ideas we have, and generally keep the discussion open and simmering. I'll note that the content from the wiki does end up in DocBook XML in a git source code repository, and we could switch to that as the upstream source (instead of interim format) for the textbook. However, my experience and learned evidence is that we would put up a really high barrier to entry that would cut our effective contributors by 90%. - Karsten -- name: Karsten 'quaid' Wade, Sr. Community Gardener team: Red Hat Community Architecture uri: http://TheOpenSourceWay.org/wiki gpg: AD0E0C41
pgpt9lYEXnZhr.pgp
Description: PGP signature
_______________________________________________ tos mailing list tos@teachingopensource.org http://teachingopensource.org/mailman/listinfo/tos
