> I think the public contribution area is the wiki itself. Log in and > edit? And the issue tracker seems to be the discussion section for each > page. IIRC, much of this was written during a doc sprint a few years
BE BOLD. http://opensource.com/education/12/4/teaching-open-source-team-operating-principles-can-be-used-any-project Just edit. Drop a note here after you make big edits, and ask for feedback. The text has not changed substantially for some time, and there's no harm in improving it in the way you're describing. Go for it. I'd love to see it have some good bits on git. As Karsten and Greg pointed out to me when we were on the sprint: we can always revert. I'm not suggesting we're going to revert your work, but just stating the (obvious?) that the nice thing about wikis (and version control systems in general) is that work towards the future never eradicates the past. I'm confident your efforts will improve the text, so go for it. > back. I'm not an authority on the TOS project at all; I'm just an > interested (and mostly quiet) party who has slowly been trying to > introduce FOSS to our students at Laurentian University through informal > talks, as I'm not part of the Comp Sci faculty and not really in a > position to influence the formal curriculum. Also, BE BOLD. And, ask questions. If the community can support you in your efforts in some way, ask. Closest to you is Seneca, and they're doing a lot of excellent work in this space, if you ever want to arrange a field trip for yourself and your students. Mostly saying "BE BOLD," Matt _______________________________________________ tos mailing list [email protected] http://lists.teachingopensource.org/mailman/listinfo/tos
