19:33:56 <kwurst> #startmeeting 19:33:56 <zodbot> Meeting started Wed Feb 29 19:33:56 2012 UTC. The chair is kwurst. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:33:56 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:35:03 <kwurst> #topic How to Choose a Project 19:35:30 <kwurst> Relationship with maintainers is a very important consideration 19:35:55 <kwurst> You need to have student code reviewed quickly 19:36:15 <kwurst> Smaller group of maintainers is probably better - you can get to know them all. 19:38:05 <kwurst> #info 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. 19:39:40 <kwurst> #info You can get a lot of information on a project from sourceforge 19:40:21 <kwurst> #link http://sourceforge.net/ 19:40:35 <kwurst> #info ohloh has a lot of statistics on project 19:41:02 <kwurst> #link http://www.ohloh.net/ 19:41:50 <kwurst> #info OpenHatch is targeted at new contributors 19:41:55 <kwurst> #link http://openhatch.org/ 19:53:24 <kwurst> #topic How do you amortize your/your class' investment in figuring out the project so that you don't have to go though it again? 19:53:46 <kwurst> #info Make sure you contribute it back to the larger community 19:54:34 <kwurst> #info Work on vertical integration - get the students in the lower level classes involved, so that the information can be passed on... 19:54:51 <kwurst> #topic Joining a project vs. starting your own 20:03:24 <kwurst> #info An advantage to starting your own project is that you can provide the students good support - you can answer their questions 20:04:37 <kwurst> #info 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. 20:05:51 <kwurst> #info 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 20:06:15 <kwurst> #info jQuery makes it easy to write plugins 20:08:01 <kwurst> #topic Projects that can support non-coding contributions 20:12:27 <kwurst> #topic 20:13:16 <kwurst> #topic Fitting into a project 20:13:37 <kwurst> #info Need to contact the project to be sure that there is something for the students to do. 20:14:44 <kwurst> #info 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. 20:15:01 <kwurst> #topic 20:16:12 <kwurst> #topic Vertical Integration - How to you integrate students across class levels to provide institutional memory and interest 20:18:24 <kwurst> Where can you match up the students across the levels? 20:19:45 <kwurst> #info Matching students in classes 20:20:00 <kwurst> #info Seniors go present in sophomore level class 20:20:37 <kwurst> #info Require students in lower-level classes to attend presentations by students in the senior project class 20:21:53 <kwurst> #info Departmental blog showcasing the work students are doing in FOSS for lower-level students to read 20:22:57 <kwurst> #info Make a junior and sophomore level 1 credit course that is a prerequisite for the senior capstone course. 20:23:21 <kwurst> #info Lower-level students end up being apprentices in the project. 20:25:32 <kwurst> #info The Stack Exchange platform can be repurposed to build up some sort of knowledge repository to keep information about the project. 20:26:21 <kwurst> #info Piazza may be another option for this kind of institutional memory 20:28:02 <kwurst> #info Departmental senior project presentations/fair 20:32:44 <kwurst> #link http://docs.python.org/devguide/coredev.html 20:33:51 <kwurst> #Topic Intellectual Property issues with students working in FOSS 20:34:11 <kwurst> #info What about students wanting to own their own IP? 20:34:24 <kwurst> #info Dual licensing is possible 20:35:14 <kwurst> #info What about the institution's rules about IP? 20:37:45 <kwurst> #info See the meeting minutes for the other session - they are talking about IP and NDA as well... 20:38:26 <ghislop> time to take a break!! 20:39:17 <kwurst> #endmeeting