> -----Original Message----- > From: tos-boun...@teachingopensource.org [mailto:tos- > boun...@teachingopensource.org] On Behalf Of Mel Chua > Sent: Monday, April 04, 2011 4:30 PM > To: TOS > Subject: [TOS] POSSE 2011 cohort admissions - new applications, 10/15 > seats remain > > I wonder if there's a nice opportunity here to kill two birds with one > stone - if the class picks *one* piece of infrastructure that a number > of TOS schools would love to see improved, implements fixes on it that > will specifically make that piece of software (Trac? Mediawiki? etc?) > much easier for schools, students, and classes easier to use and > deploy, > tries it out themselves, and then turns around and (probably the > following semester or school year) works with UNH's IT department to > deploy it for other classes, and possibly other local TOS professors to > deploy it experimentally in theirs... you've got a development project > working with a major FOSS upstream to serve local consumers of that > project's software. Karl's Software Development class and Kristina's > NLP > class (among others, I'm sure) are running during the spring semester, > both not too far from UNH (decent roadtrip or > let's-all-meet-at-a-local-conference distance). Possibly an ambitious > target here that will take a couple more years than I'm thinking, but > that's one possible Big Awesome Milestone.
The CIS program at UNHM is very much interested in a Mediawiki infrastructure that would support all CIS courses. We are stuck right now with a BitNami WAMP stack on a low performance server. We'd love to upgrade to XAMPP on Linux using a more powerful server (which is still in its original shipped box). > > I'd like to hear some thoughts/suggestions on more concrete projects > this class could do - I'm trying to envision where they're going to fit > within the TOS ecosystem and it's still a little fuzzy to me - but I'm > inclined to say that if we get that sort of feedback and discussion > this > week, this should be a +1 yes. There's definitely potential we can tap > here. > The concrete projects students have worked on are "client-oriented" rather than "community-oriented", where the clients are local nonprofits and government agencies. The projects have not made it through the university door, except for three instances in which summer fellowships or independent study projects involved individual students who committed full time to deploying the systems. In the process, students helped with migrating the systems to some proprietary technology that the organization was using. The special questions that these kind of projects raise in the TOS ecosystem are: * documenting system development * documenting end-user support * training end-users * system hosting and/or commercializing system support * sustaining client-oriented projects _______________________________________________ tos mailing list tos@teachingopensource.org http://teachingopensource.org/mailman/listinfo/tos
