(sorry, meant to email it to tos) -----Original Message----- From: Sabin, Mihaela Sent: Wednesday, April 20, 2011 8:05 AM To: 'Mel Chua' Subject: RE: [TOS] 2011-2012 school year POSSE Module scheduling - draft
Mel, the 'schedule map' looks good. The 'class journey' might get more involved with some activities and skim the surface in other instances. The biggest problem is that students' time commitment is limited to 10 hrs/week per course (in the best case). And as the end of the semester gets near, especially in a group project, the pieces don't quite fall in place. However, I do believe that FOSS is the way to solve this problem. The more prepared teachers are in orchestrating software development efforts the open source way, the more likely students achieve what we plan for at the beginning of the semester. Mihaela > -----Original Message----- > From: tos-boun...@teachingopensource.org [mailto:tos- > boun...@teachingopensource.org] On Behalf Of Mel Chua > Sent: Tuesday, April 19, 2011 1:52 AM > To: TOS > Subject: [TOS] 2011-2012 school year POSSE Module scheduling - draft > > I'm thinking about scheduling for the POSSE modules > (http://teachingopensource.org/index.php/POSSE_Modules) that will be > taught during the next school year - here's a rough draft, trying to > account for NA school schedules (where this year's attendees are based) > and the Fedora 16 and 17 release cycles, since that's where I plan on > drawing some of the examples from (though people are of course free to > use any FOSS project they'd like for all these activities.) > > If any of these dates are problematic for anyone, or if there's > something that would be more conveniently scheduled another time, or if > you wish a topic order could get switched around, etc. please let me > know - this isn't set in stone yet, but I'm trying to see how the > content and the various events, etc. we have for the 2011-2012 school > year can sync up schedule-wise. > > --Mel > > ------- > > * Aug 29: Trackers and tickets (The Alpha will just have come out.) > * Sep 05: Special guest: Fedora QA team test day (Beta change / Feature > completion deadline is Sep 06.) > * Sep 12: Release early, release often: feature and release processes > * Sep 19: The first 15 minutes: how to approach a new project (Beta > release is Sep 20.) > * Sep 26: Upstreaming: version control and the commit cycle > * Oct 03: Distributed team dynamics: timezones, language, culture, and > running excellent meetings > * Oct 10: How to be lazily productive: marketing, recruitment, > blogging, > and building momentum (Final change deadline is today, FIE is Oct 12- > 15.) > * Oct 17: Special guest: Design Team > * Oct 24: Remixability: Licensing and IP (Final release date is > initially set to Oct 25.) > * Oct 31: Getting your code used: packaging and distribution > * Nov 07: Special guest: Marketing team (Realistically, final release > will be Nov 08.) > * Nov 14: (Planning and development for F17 begins.) > * Nov 21: THANKSGIVING - NO CLASSES > * Nov 28: Attending events > * Dec 05: Special guest: Infrastructure team > * Dec 12: Deploying with your local community: QA, support, and > town-gown relations > * Dec 19: Special guest: FUDCon organizers > > (Feature submission deadline for F17 is likely to be Jan 25, giving > courses that run for both semesters some time to think about whether > they want to write proposals over break.) > > * Feb 06: Release early, release often: feature and release processes > (Feature freeze happens around this date.) > * Feb 13: The first 15 minutes: how to approach a new project > * Feb 20: How to be lazily productive: marketing, recruitment, > blogging, > and building momentum > * Feb 27: Trackers and tickets (SIGCSE is Feb 29 - Mar 03) > * Mar 05: Remixability: licensing and IP (SPRING BREAK. Alpha release > happens around this date.) > * Mar 12: Guest speaker: Infrastructure team (SPRING BREAK) > * Mar 19: Guest speaker: Documentation team (SPRING BREAK) > * Mar 26: Distributed team dynamics: timezones, language, culture, and > running excellent meetings (Feature-completeness happens around this > date) > * Apr 02: Upstreaming: Version control and the commit cycle > * Apr 09: Attending events (Beta release happens around this date.) > * Apr 16: Getting your code used: packaging and distribution > * Apr 23: Guest speaker: Marketing team (Final change deadline happens > around this date.) > * Apr 30: Deploying with your local community: QA, support, and > town-gown relations > > (Final release is likely to be end-of-May, giving us an opportunity to > get media out to schools as an end-of-year congratulations.) > > _______________________________________________ > tos mailing list > tos@teachingopensource.org > http://teachingopensource.org/mailman/listinfo/tos _______________________________________________ tos mailing list tos@teachingopensource.org http://teachingopensource.org/mailman/listinfo/tos
