[TOS] Fwd: Re: POSSE resources [was: Re: Feedback from your workshop on OSC]
Mel Chua
mel at purdue.edu
Wed Sep 26 12:33:13 UTC 2012
Forwarded to the list with Alexandro's permission. Comments welcome,
I'll try to get to it myself sometime this week between classes and
stuff. :)
-------- Original-Nachricht --------
Betreff: Re: POSSE resources [was: Re: Feedback from your workshop on OSC]
Datum: Tue, 25 Sep 2012 17:15:56 -0500
Von: Alexandro Colorado <jza at oooes.org>
An: Mel Chua <mel at purdue.edu>
ah ok, thanks.
most of our material is 'borrowed' from literature on the structure of
communities as well as technical organization (arquitectual) of code.
To give a better insight into how FLOSS behaves on organizational and
technical merits.
Literature includes books such as:
- The Architecture of Open Source Applications http://www.aosabook.org
- Producing Open Source Software http://producingoss.com/
- The Art of Unix Programming http://www.faqs.org/docs/artu/
and others.
As far as the syllabus is still on a mind-map stage and some ideas
include, view FOSS not only as Linux but as an ecosystem of web
communities not only restricted to software (open standards as well).
While at the same time have a practical approach of building,
commiting, reporting and communicating with different projects.
The challenge relies on:
- how to do this efficiently with limited time resources.
- which topic have priority over the next, sequencial processes are
not always the more friendly. (i.e. requesting a features is faster
than building/debugging).
- Disrupting a community with a false sense of commitment. (or try to
encapsulate the 'community experience' avoiding the real community)
As far as activities:
- Interact on IRC with some developers and communicate on mailing lists
- Pull source code and follow building instructions
- Reporting building/operational bugs, and producting quality use cases.
- Document architectual decisions between projects
Still a very rough draft of what we got and considering pulling or
pushing new items depending on the technical expertise, or the time it
can take away from the duration of the training.
More information about the tos
mailing list