Pardon me, but I feel the need to think in terms of a swim lane chart[1] in order to understand what teachingopensource.org (tos.o) & the Teaching Open Source (TOS) community need for technology.
[1] http://en.wikipedia.org/wiki/Swim_lane http://www.agilemodeling.com/style/activityDiagram.htm#Swimlanes I'd be happy to draw a real chart, perhaps, but first we really need to: 1. Agree on the swim lanes; 2. Agree on the sorting of services in to the lanes. Here's what I have so far: ====================================================================== ---------------------------------------------------------------------- ====================================================================== Lane 1 - Services for TOS events * Examples - Quick-usage services - stand-up, tear-down . SCM repositories . Demo wiki . IRC . Fedora installation/Live USB troubleshooting . ? - Ongoing-usage services . Mailing lists (event-specific) . Wiki content on main tos.o . POSSE-specific forum . ? * Specific services - One-click installs (Dreamhost; custom or found Amazon machine images) - POSSE instructors go to a WebUI to configure services quickly. - Sandbox stacks (MediaWiki, Mailman, Trac, SCMs, etc.) - ? * Use cases - Instructor needs Foo during POSSE, expectedly or unexpectedly ... - Attendee asks an unexpected question best answered with a live technology demo ... - Technology coordinator needs resources for a creative solution ... - ? ====================================================================== ---------------------------------------------------------------------- ====================================================================== Lane 2 - Services for TOS community members to consume * Examples - Classroom services . Sandboxes for professors and students to simulate and demo . Professor's curriculum with a need not in an existing project . Other curriculum needs that cannot be tied to a project - Mailing list(s) - Discussion forums - Collaborative documentation (wiki) * Specific services - Mailman - MediaWiki - Subversion - Git - Trac - ? * Use case - Textbook project discussion forum - Collaborative community documentation - Email discussions with public access and archives - Project planning and tracking - FOSS and free/open content management (SCM) - ? ====================================================================== ---------------------------------------------------------------------- ====================================================================== Lane 3 - Services to show TOS to the world * Examples - tos.o website - tos.o blog planet - ? * Specific services - MediaWiki - Mailman - Planet - Trac - ? * Use case - Public website for the world to learn about TOS - Mailing list archives so public can see transparent TOS processes - Aggregation of TOS community blogs for topical interest - Source code or content public view - ? ====================================================================== ---------------------------------------------------------------------- ====================================================================== Expansions, ideas, criticism, all welcome, welcome. - Karsten -- name: Karsten 'quaid' Wade, Sr. Community Gardener team: Red Hat Community Architecture uri: http://TheOpenSourceWay.org/wiki gpg: AD0E0C41
pgp8s7hYS7Ypm.pgp
Description: PGP signature
_______________________________________________ tos mailing list tos@teachingopensource.org http://teachingopensource.org/mailman/listinfo/tos
