paper from Michelle and Heidi in the SIGCSE
2012 proceedings has a framework for evaluating a project to tell if
it might be a good fit.(kwurst,
19:38:05)
You can get a lot of information on a project
from sourceforge(kwurst,
19:39:40)
How do you amortize your/your class' investment in figuring out the project so that you don't have to go though it again?(kwurst, 19:53:24)
Make sure you contribute it back to the larger
community(kwurst,
19:53:46)
Work on vertical integration - get the students
in the lower level classes involved, so that the information can be
passed on...(kwurst,
19:54:34)
Joining a project vs. starting your own(kwurst, 19:54:51)
An advantage to starting your own project is
that you can provide the students good support - you can answer
their questions(kwurst,
20:03:24)
An advantage to joining an existing project is
that it will continue on its own. You don't have to keep the project
going on your own, or hope that enough others get interested enough
to keep it going.(kwurst,
20:04:37)
A third choice is to write a plugin to a
project that has that sort of architecture. You will be able to
start from scratch, but be taking advantage of the community(kwurst,
20:05:51)
jQuery makes it easy to write plugins(kwurst,
20:06:15)
Projects that can support non-coding contributions(kwurst, 20:08:01)
Need to contact the project to be sure that
there is something for the students to do.(kwurst,
20:13:37)
Need to figure out how the project's schedule
meshes with your course's schedule, so that the project understands
when the students will show up, and when they will disappear.(kwurst,
20:14:44)