Hi, Andrew Hamblin wrote: > The contributor mountain example feels to be problematic, as though it > reflects a hierarchy, rather than an open process.
I like the analogy, it seems appropriate. There definitely is a hierarchy in free software projects, and like a mountain, anyone can climb higher in that hierarchy. There are no barriers, but that doesn't mean it'll be easy. > It is also a really > great way to provide a road map towards participation, but I wonder if > we couldn't find a better metaphor, and one that could be carried > through the whole book. Any process which involves growth and learning, and confronting new challenges, would do. Mountain climbing works, as does (say) running a marathon, playing in a sports team (moving from young enthusiast, to training regularly with the team, maybe spending some time as a substitute, winning your place on the team, and finally (potentially) becoming a leader of the team, and thinking of bigger objectives (winning championships, what's best for the team, etc). Or a hypothetical story starting with someone moving to a new neighbourhood, and ending with them being elected to city council (too culturally specific, perhaps?). Cheers, Dave. -- Dave Neary GNOME Foundation member dne...@gnome.org _______________________________________________ tos mailing list tos@teachingopensource.org http://teachingopensource.org/mailman/listinfo/tos
