=========================== #teachingopensource Meeting =========================== Meeting started by mchua at 14:21:23 UTC. The full logs are available at http://meetbot.fedoraproject.org/teachingopensource/2010-04-22/posse_worcester_curriculum_ii.2010-04-22-14.21.log.html . Meeting summary --------------- * LINK: http://meetbot.fedoraproject.org/teachingopensource/2010-04-21/posse_worcester_curriculum_brainstorming.2010-04-21-19.57.html (mchua, 14:23:25) * that's where we left off last time (mchua, 14:23:32) * Wednesday (mchua, 14:23:35) * ACTION: walterbender find a large codebase to dive through, sugar-core or otherwise, that has a sane setup. (mchua, 14:32:05) * Activity: large codebase dive-in (mchua, 14:32:18) * Thursday (mchua, 14:33:25) * Goals: Deployment day! (1) send people home with a customized soas remix of what the image will look like once their changes are merged, (2) debugging tools and strategies, (3) discuss student projects in preparation for Friday (mchua, 14:45:19) * Activity: work through as many merge/review requests as possible for Activity inclusion on SoaS, wrap up this portion of the day by building a remix (mchua, 14:45:55) * Activity: Debugging tools and strategies - testing/support, or "what to do when stuff goes wrong" (mchua, 14:46:33) * Activity: Discussion on student projects, prepare for tomorrow's teaching-focused day (mchua, 14:46:47) * Activity: big dinner downtown with local open source / Sugar folks (mchua, 14:47:02) * ACTION: walterbender pick a location for Thursday's big dinner (mchua, 14:47:56) * Friday (mchua, 14:49:39) * Goal: discussion of future plans for classrooms, wrap-up (mchua, 14:50:00) * That's really it - we end at noon, and then people are free (mchua, 14:50:20) * Walter, Sebastian, and Mel should have a working lunch afterwards to wrap up (mchua, 14:50:42) * Review of the week, and action items between now and June (mchua, 14:53:29) * ACTION: mchua make sure the join processes for each type of account are actually sane, and that all account registrations can be completed in <1h; make screencast if necessary, hack code if necessary. (mchua, 14:54:26) * ACTION: mchua make sure we have one good tutorial available for each communications method (mchua, 14:54:49) * ACTION: sdziallas make sure we have a SoaS image, usage guide, customization guide to hand out to people (mchua, 14:55:43) * ACTION: mchua purchase USB sticks for attendees and burn the provided SoaS image on them before the start of POSSE (mchua, 14:56:03) * ACTION: sdziallas make sure we have a Fedora-based image (spin, remix, etc) for professors to use as their dev environment throughout the week, and that it has tools for all the activities we'll be doing throughout the week (mchua, 14:56:33) * ACTION: mchua make sure we have computing power available to run said image, and easy instructions to do so, whether that's a RH-provided VM somehow or a solution that will let attendees easily spin up VMs on their computers, or loaner computers (mchua, 14:57:16) * ACTION: walterbender pick and provide a Sugar Activity development IDE that's easy for novices to learn to use (Eclipse? DrPython? Gedit?) (mchua, 14:58:00) * ACTION: walterbender sdziallas mchua make sure the Sugar community is aware that POSSE is going to happen, and that professors will be arriving for this one week (mchua, 14:58:32) * ACTION: sdziallas prepare for evening packaging sessions, focused on Sugar activities (mchua, 14:58:47) * ACTION: mchua work with #sugar devs to come up with a good "what is jhbuild? how to explore it on your own!" resource since we won't be exploring jhbuild specifically during the week, due to scope (mchua, 14:59:17) * ACTION: mchua make sure all attendees have a computer that can boot SoaS (mchua, 14:59:38) * ACTION: mchua make sure we have SoaS activity inclusion criteria - start first draft, final signoff by sdziallas (mchua, 15:00:00) * ACTION: walterbender make sure we have good "how to start Activity development" and "how to modify Activities" resources (mchua, 15:00:22) * ACTION: mchua and sdziallas test-drive and choose some intro-to-Python resources to have on hand (mchua, 15:02:37) * ACTION: sdziallas sync with pbrobinson about this POSSE week and SoaS work needed to get ready for it (mchua, 15:03:00) * ACTION: mchua choose an "intro to git" tutorial (mchua, 15:03:15) * ACTION: mchua fix up "how to do a bug report" resources (mchua, 15:06:20) * ACTION: walterbender prepare resources/explanation/tutorial for patch, merge, diff (mchua, 15:09:43) * ACTION: watlerbender make sure Activity maintainers can be active in accepting merge requests during that week (so we can steer people towards Activities with active maintainers) (mchua, 15:24:49) * ACTION: mchua make sure we have a good "why should you blog?" nudge, and that the SL community is geared up to comment on planet posts (mchua, 15:25:14) * ACTION: mchua make sure we will have fast turnaround on "add my blog to planet" at the start of POSSe week (mchua, 15:25:26) * ending meeting, will resume after this next one (mchua, 16:01:23) Meeting ended at 16:01:24 UTC. Action Items ------------ * walterbender find a large codebase to dive through, sugar-core or otherwise, that has a sane setup. * walterbender pick a location for Thursday's big dinner * mchua make sure the join processes for each type of account are actually sane, and that all account registrations can be completed in <1h; make screencast if necessary, hack code if necessary. * mchua make sure we have one good tutorial available for each communications method * sdziallas make sure we have a SoaS image, usage guide, customization guide to hand out to people * mchua purchase USB sticks for attendees and burn the provided SoaS image on them before the start of POSSE * sdziallas make sure we have a Fedora-based image (spin, remix, etc) for professors to use as their dev environment throughout the week, and that it has tools for all the activities we'll be doing throughout the week * mchua make sure we have computing power available to run said image, and easy instructions to do so, whether that's a RH-provided VM somehow or a solution that will let attendees easily spin up VMs on their computers, or loaner computers * walterbender pick and provide a Sugar Activity development IDE that's easy for novices to learn to use (Eclipse? DrPython? Gedit?) * walterbender sdziallas mchua make sure the Sugar community is aware that POSSE is going to happen, and that professors will be arriving for this one week * sdziallas prepare for evening packaging sessions, focused on Sugar activities * mchua work with #sugar devs to come up with a good "what is jhbuild? how to explore it on your own!" resource since we won't be exploring jhbuild specifically during the week, due to scope * mchua make sure all attendees have a computer that can boot SoaS * mchua make sure we have SoaS activity inclusion criteria - start first draft, final signoff by sdziallas * walterbender make sure we have good "how to start Activity development" and "how to modify Activities" resources * mchua and sdziallas test-drive and choose some intro-to-Python resources to have on hand * sdziallas sync with pbrobinson about this POSSE week and SoaS work needed to get ready for it * mchua choose an "intro to git" tutorial * mchua fix up "how to do a bug report" resources * walterbender prepare resources/explanation/tutorial for patch, merge, diff * watlerbender make sure Activity maintainers can be active in accepting merge requests during that week (so we can steer people towards Activities with active maintainers) * mchua make sure we have a good "why should you blog?" nudge, and that the SL community is geared up to comment on planet posts * mchua make sure we will have fast turnaround on "add my blog to planet" at the start of POSSe week Action Items, by person ----------------------- * mchua * mchua make sure the join processes for each type of account are actually sane, and that all account registrations can be completed in <1h; make screencast if necessary, hack code if necessary. * mchua make sure we have one good tutorial available for each communications method * mchua purchase USB sticks for attendees and burn the provided SoaS image on them before the start of POSSE * mchua make sure we have computing power available to run said image, and easy instructions to do so, whether that's a RH-provided VM somehow or a solution that will let attendees easily spin up VMs on their computers, or loaner computers * walterbender sdziallas mchua make sure the Sugar community is aware that POSSE is going to happen, and that professors will be arriving for this one week * mchua work with #sugar devs to come up with a good "what is jhbuild? how to explore it on your own!" resource since we won't be exploring jhbuild specifically during the week, due to scope * mchua make sure all attendees have a computer that can boot SoaS * mchua make sure we have SoaS activity inclusion criteria - start first draft, final signoff by sdziallas * mchua and sdziallas test-drive and choose some intro-to-Python resources to have on hand * mchua choose an "intro to git" tutorial * mchua fix up "how to do a bug report" resources * mchua make sure we have a good "why should you blog?" nudge, and that the SL community is geared up to comment on planet posts * mchua make sure we will have fast turnaround on "add my blog to planet" at the start of POSSe week * sdziallas * sdziallas make sure we have a SoaS image, usage guide, customization guide to hand out to people * sdziallas make sure we have a Fedora-based image (spin, remix, etc) for professors to use as their dev environment throughout the week, and that it has tools for all the activities we'll be doing throughout the week * walterbender sdziallas mchua make sure the Sugar community is aware that POSSE is going to happen, and that professors will be arriving for this one week * sdziallas prepare for evening packaging sessions, focused on Sugar activities * mchua make sure we have SoaS activity inclusion criteria - start first draft, final signoff by sdziallas * mchua and sdziallas test-drive and choose some intro-to-Python resources to have on hand * sdziallas sync with pbrobinson about this POSSE week and SoaS work needed to get ready for it * **UNASSIGNED** * walterbender find a large codebase to dive through, sugar-core or otherwise, that has a sane setup. * walterbender pick a location for Thursday's big dinner * walterbender pick and provide a Sugar Activity development IDE that's easy for novices to learn to use (Eclipse? DrPython? Gedit?) * walterbender make sure we have good "how to start Activity development" and "how to modify Activities" resources * walterbender prepare resources/explanation/tutorial for patch, merge, diff * watlerbender make sure Activity maintainers can be active in accepting merge requests during that week (so we can steer people towards Activities with active maintainers) People Present (lines said) --------------------------- * mchua (110) * sdziallas (47) * erwqt (6) * zodbot (4) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot