I just brought home the book Producing Open Source Software. I am roughly in the middle of it now but I already feel the need to manifest my admiration for it’s teachings. The book, written by Karl Fogel, an open source developer himself, not only exposes the dynamics of open source projects (how things get done and which tools are essential for it) but also, “between the lines”, gives a series of best practices that can be aplyed on any kind of collaborative project.

The book also has arrows, coincidense or sign? =)

Some of it’s teachings regarding the dynamics of the projects are already flowing into our projects. For example, our electric motorcycle frame project, the e.Moped project, now features a Developer Guidelines Page to help future developers find their way into contributing to the project. Another important suggestion from the book and now implemented, is the writing of a mission statement of the project, making it clear for developers and the outside world what the project is trying to accomplish. Also mentioned in the book is the importance having the type of License the project is running on, right on the front page of the project, which seams quite obvious but as the author points out, is often missed in many projects.

The book is opening my eyes to a lot of details on how successful open source software projects are organized and definitely suggest it to anyone interested in not only open source development but the social skills need for successful collaborative work.

In a near future, I will be posting questions that were raised in my head after getting to know more about the process of open source software development. In my opinion, there are a lot of tools missing that would make it possible to fully develop Hardware in the same way that Software is developed. There is already a spark of discussion started by Portuguese designer João Rocha at the forums. It would be nice to hear more voices on this subject.