From michael_odonnell at acm.org  Mon Sep 20 12:13:04 2004
From: michael_odonnell at acm.org (Michael J. O'Donnell)
Date: Thu May 18 12:41:36 2006
Subject: [Cs22800] Free Software Practicum for AY 2004-5
Message-ID: <414F0FA0.1000907@acm.org>

Is there to be a Free Software Practicum in autumn 2004?

* The course must be organized and operated by the students. That's part 
of the point of free software. I serve as sounding board, critic, 
advisor, cheerleader, and certifier of course credit.

* Jonathan DiCarlo and Chris Hinrichs have indicated they would like to 
participate this autumn. I need at least 3 students, preferably more, 
for a successful course. Abid Sayed contacted me about a project, and 
might like to connect it to the course.

* The right place to discuss the Practicum is the mailing list 
cs22800.cs.uchicago.edu. If you are interested, and are not a member, 
join right away at 
http://mailman.cs.uchicago.edu/mailman/listinfo/cs22800. Then post your 
interest.

* We need to start right away in order to complete projects for credit 
in the autumn quarter. We may start somewhat more leisurely if the 
projects will extend into another quarter, with credit taken at completion.

* The first steps are for students to take over as mailing list 
moderator and webmaster 
(http://www.classes.cs.uchicago.edu/classes/archive/2002/fall/22800-1/, 
http://www.classes.cs.uchicago.edu/classes/archive/2003/spring/22800-1/).

* The precise nature of the course is entirely negotiable, and the more 
initiative from students the better. Experience from previous quarters 
provide the following initial conditions for negotiation.

* All sorts of contributions to free software are worth considering as 
projects. The process of contributing, social as well as technical, is 
as interesting as the product (usually, but not necessarily, program 
code). The course should generate insight into the way that each small 
contribution fits into the global software commons. UC students may work 
individually or in local teams, almost always in co-ordination with some 
remote project leader and/or group.

* Communication is as important as project work. In the past, we have 
scheduled one 3-hour meeting per week. I am available to meet on Fridays 
at any time other than 12:45-2:30. It will be difficult, but not 
absolutely impossible, to persuade me to another day of the week. 
Students should organize the meetings (how about a volunteer meeting 
moderator?).

* Each course group, and each project should produce a permanent record, 
normally on the course Web site.

* It is possible, but very challenging, to complete a project in one 
quarter. It's better to start in one quarter, then complete later 
without huge time pressure. The best approach is to work as an informal 
group now, then enroll for credit in the quarter in which you complete.

* We often have outside participants in meetings and discussion. Ziba 
Scott (course alum) may join us this quarter. Class discussion and 
documents should be just as open as the software.

* Credit and grading are inherently subjective, based on my best 
judgment. I welcome pass/nopass registrations. Whatever credit/grade I 
must assign I will base on my appreciation of *total* contribution to 
the class, including discussion and organization as well as project 
product. Good, short, clear written contribution is the best. Rather 
than dumping a bunch of stuff on me at the quarter deadline, you should 
continually show intermediate results, and I can give you feedback on my 
evaluation.