Next Steps

It's clear from Friday's end-of-course review that the course needs shaking up. Before that starts, though, there's a higher-level question to answer: should the course notes be converted to a wiki to encourage contributions from others? It was always my hope that other people would contribute material, but in four years, only five ever have; perhaps wikification would change that.

Right now, the notes are stored as HTML pages in a Subversion repository and compiled by a little Python script to resolve cross-references, insert code samples, and so on. The advantages of this approach are:

1. People can work locally and push coordinated changes when ready.
2. Slide format can be skinned by changing a flag in the Makefile to select different CSS. (For example, I'm still hoping to get S5 or S5R working.)
3. The build step can also insert code fragments, ensure that bibliography references resolve, etc.

Advantages of a wiki are:

1. Easier collaboration: people can make small fixes in place without doing an "svn checkout" or running Make.

As a programmer, the first three weigh heavier in my mind than the last one, but again, only five people have contributed material in four years, which isn't sustainable. What do you think? Would switching to a wiki make you more likely to add material or not?

Originally posted 2009-08-02 by Greg Wilson in Content, Tooling.

comments powered by Disqus