From Teaching Open Source

• So far, all this curricula assumes that profs want their classes to get involved with OSS code development. What about other kinds of work - testing, marketing, etc? (We have at least one business prof, iirc.) Our setup is heavily biased towards CS classes, is that okay?
• When should the topic of asking smart questions come up?
• Useful time to start drawing analogies between working on an OSS project and running an "OSS class"? (for instance, using bug reporting style for classroom feedback, having a course wiki instead of just using it for code projects too, etc.)

Mchua 15:01, 28 May 2009 (UTC)