On Fri, Mar 19, 2010 at 02:19:37AM -0400, Mel Chua wrote:
I'm a bit overwhelmed, though - I'm not sure how to apply all
these
things to the one story (which I've only read the single article for).
Maybe we could have storytelling time at some point, and then others
could point out (inline) where various principles applied?
I'm not even sure I can remember very many of them - I think I've
internalized this stuff so much I'm having a hard time remembering the
names and numbers. Maybe each principle needs a snappy catchprase - some
already have them, like "Quiet projects stay quiet. Noisy projects get
noisier" - but, for instance, "You need a version controlled repository
for content - code and documentation and art and etc" is less catchy.
Yeah, we can work on reworking sections to be snappier sounding. I
don't think we can totally (ab)use the pattern language method, but I
like at least some call outs about how many ways a story implements
the open source way.
Added to the big task list:
https://www.theopensourceway.org/wiki/Big_task_list#Content
... a list which could maybe be (re)visioned in Trac instead ...
- Karsten
--
name: Karsten 'quaid' Wade, Sr. Community Gardener
team: Red Hat Community Architecture
uri:
http://TheOpenSourceWay.org/wiki
gpg: AD0E0C41