Hi Joseph, I'm definitely interested in this.
In Fall of 2013, Thomas Maillart and I co-instructed a course at UC Berkeley's School of Information called "Open Collaboration and Peer Production," aimed at Masters students in the department. We ran it as an open source project. You can explore the results here: http://courses.ischool.berkeley.edu/i290m-ocpp/site/information.html which is a Pelican website, repository here: https://github.com/sbenthall/i290m-ocpp-site You might be especially interested in the readings: http://courses.ischool.berkeley.edu/i290m-ocpp/site/syllabus.html As for assignments, we had every student in the class find an open collaborative project to participate in, and blog their experiences with prompts reflecting themes covered in the readings. We didn't want to require software projects, so we got one student looking at a wiki and another looking into citizen science. But for the most part they chose open source software projects--taking on a number of different roles. They also collaborated as a class on a final report with 27 authors. While instructive on some level, the report is as you might imagine a mess. We've decided not to teach it again this coming year--I need to prioritize research myself. But I'm very interested in contributing to this project. Thanks, Seb On Wed, Jul 2, 2014 at 9:05 AM, Joseph B. Ottinger <[email protected]> wrote: > Hello, all. > > > My name is Joseph Ottinger. I'm an engineer at Red Hat, presently tasked > with creating a curriculum for the purpose of providing students with an > awareness of open source culture, tools, goals, and community. > > We are in the beginning stages of creating an open source project around > the creation of this curriculum, and we would like to invite any interested > parties to participate. We are passionate around the open source way, and > think that creating this curriculum through a visible, open process will > allow it to serve as a model for the concepts it is designed to teach. > > We have a general table of contents already, but it's very much only an > initial concept; consider this an invitation to please help flesh it out > and improve it, so that we can create the highest quality material > possible; one of our primary goals is to take this open curriculum and have > it published as a textbook. Any suggestions are welcomed, from actual > topical concerns to additional resources to consider. > > > The (current, proposed) table of contents looks like this: > > > 1) Introduction > 2) Open Source Fundamentals (what "open source" means) > 3) Communities (defining "community," and interacting with it) > 4) Legal Aspects > 5) Principles (what makes "open source" open source) > 6) Practices and Toolchains (the processes through which open source > projects operate) > 7) History and Evolution > 8) When and Why to Make Something Open Source > 9) Open Source Cultures (discussing the mores of the different types of > open source communities) > > > Thank you. > > > > _______________________________________________ > tos mailing list > [email protected] > http://lists.teachingopensource.org/mailman/listinfo/tos >
_______________________________________________ tos mailing list [email protected] http://lists.teachingopensource.org/mailman/listinfo/tos
