Hey!
Do you want to help us write the next version of the first textbook that teaches open source participation?
We need writers, editors, reviewers, and researchers to find or create content on:
- Testing code in FOSS communities.
- Working in open communities.
- Different types of open source community cultures.
- Open communities and diversity.
- Licensing FOSSÂ code.
- Threats and risk analysis of FOSS as a technology choice.
- FOSS business models.
- Determining program requirements.
- Designing FOSS programs.
Join the mailing list and let us know what you are interested in, or you can email me directly.
Note: The textbook Practical Open Source Software Exploration is licensed under the CC BY SA 3.0 Unported. We are very interested in reusing and modifying existing content that is compatibly licensed. This is especially true if we can use the content as an active downstream.
Tl;dnr version follows …
Earlier this year we released the first usable version of a textbook, “Practical Open Source Software Exploration”. This book fills a need that we hear about repeatedly from educators — there is no other standard textbook that teaches how to actually participate in a free and open source software (FOSS) project.
Although that first release, 0.8., had some problems, it was pretty solid in terms of having practical material for students to work through to check out code, build code, debug code, submit a patch, and write collaborative documentation.
However, in a meeting earlier this year with Tim Budd and Carlos Jensen of Oregon State University, Dr. Budd noted there was really only enough material in the book to teach a few weeks of classes. It was so practice heavy that a student, unless they ran in to technical problems, could go through the material relatively quickly. The book was extremely short on the other material a class needs — the theoretical side. It was missing material on the history, culture, types of communities, diversity, licensing, business models, and so forth.
Working with the professors who are using or planning to use the textbook, we figured out what the new chapters needed to be. Much of the material for those chapters probably exists already, some may be under a CC license we can use, so I’m hoping a good portion of this chapter work will be reusing and rewriting existing materials as a downstream.
I was just looking and it seems the book is on wiki, so, if anyone wants to contribute to existing chapters or has other ideas, my guess would be that this is a possibility as well.
Also, I noticed the chapter “Getting the Code” covers svn in detail but not git. Git should be covered as well. Lots of projects have moved to it, and it has a number of benefits.
Yes, collaboration is primarily on the wiki. It has some downsides, but it is excellent for getting a large and varied writing team able to collaborate.
We convert the work to DocBook XML for publication.
Regarding the inclusion of git, since this is a first-level introduction textbook, it isn’t supposed to cover all technology permutations … or even most of them. So, no problem with including git but first we need to be sure that we have accomplished the primary goals for that chapter with just one technology. Then we can talk about adding in other tech.
[…] of the response’s I got to from the call for writers for the Practical Open Source Software Exploration textbook was an offer of an excellent content […]
[…] to teach open source software development processes is asking for contributions. The announcement, “Looking for writers for Teaching Open Source textbook,” describes the first version of such a […]
Are you familiar with this program at UGA?
http://globaltext.terry.uga.edu/news_faqs?q=node/14
[…] getting organized and starting the big work on the next edition of the textbook. However, my recent calls for help have gained a fair amount of attention and multiple really good offers, so we are clearly underway […]
That’s fantastic, thanks. My fist glance through didn’t see an equivalent textbook, so perhaps they’d like to carry ours in their catalog. And of course, we’ll have to start looking through there for good content to reuse.
Great idea… especially in Africa where Open source solution has not fully penetrated… 🙂