Thursday, February 15, 2007

Labeling your projects

I realize that there might have been a lack of clarity on this topic.

As you all know, you can assign one or more labels to describe your project. We discussed the idea of using a "COMP 412" label so our class projects can be clearly identified. In looking at your projects I noticed that the labels comp412 and comp412.cs.luc.edu have both been used. May I suggest that we go with comp412.cs.luc.edu for consistency? It is trivial to make this change, and you are more than welcome to continue using comp412. I'd like all projects from our class to use the more precise label just in case another university is offering a COMP 412. I realize that this is unlikely but after nearly 3 years of offering this course, I noticed the other day that COMP 412 is being offered in LT 412. So there is no end to what coincidences are possible.

You can view this filter to see whether your project has the correct label. If your project does not show up in the list, it is likely that you did not use the label comp412.cs.luc.edu.

Wednesday, February 14, 2007

Welcome

You've reached the blog for the Open Source Practicum. This course is aimed at introducing students to the ideas of Free and Open Source (FOSS) software development. Students work on developing an actual FOSS project, which can be one entirely of their own creation, contributing to an existing project, or even developing documentation (similar to the motivation behind the Linux Documentation Project).

For the current incarnation of this course, which is now in its fourth offering, students will be hosting their projects on Google Code--a terrific FOSS project hosting site still in the making.

Although this site is primarily aimed at students enrolled in the course at Loyola University Chicago, we welcome involvement and participation of interested outsiders. You must be a registered Blogger/Google user to comment on anything you see here but are welcome to participate in our efforts.

Please do not hesitate to comment here or contact me directly with any questions.