Infrastructure for the community

Master on Free Software

Infrastructure for the community

Dynamics of the libre software community

Israel Herraiz<[email protected]>

A Coruña, November 16th 2007

mailto:[email protected]


What a project needs is...

● Communication among its members● Skilled people on the communication

technologies● All the tools are needed because you are

not working alone● You have to be aware of the rest of the

work● You have to make the rest be aware of

your work


Tools

● Remote● Keep record of everything● Not only tools but valuable sources of

information


Information management

● Automated tools are important● But the crucial factor is people● Tools are only that: tools


List of basic tools

● Web site● Mailing lists● Version Control● Bug Tracking● IRC


Mailing lists: minimal requirements

● List management software– i.e., Mailman

● Email and web (un)subscribing● Digest and on-the-fly modes● Moderation● Administrative interface● Manipulation of headers● Archiving


Netiquette in mailing lists

● Write intelligible messages● Some acronyms are ok though:

– IMHO In My Humble Opinion– YMMV Your Mileage May Vary– BTW By The Way– ROTFL Rolling on the Floor, Laughing– GISY Google is your friend

● Some other acronyms are not ok (RTFM)


Posting style

● Details at http://en.wikipedia.org/wiki/Posting_style

http://en.wikipedia.org/wiki/Posting_style


Top posting


Bottom posting


Inline reply


Headers of a typical message to a list

● Let's see how a message looks like● Using our list freeswmaster● Most of the archives strips out some

headers


Reply-to the controversy

● Reply to list?● Reply to original author?● A matter of taste● http://www.unicom.com/pw/reply-to-harmful.html

http://www.unicom.com/pw/reply-to-harmful.html


Archives

● Prompt updating● Referential stability● Backups● Thread support● Searchability


Some places to look for archives

● Google and Google Groups● The Mail Archive● GMANE● http://apache.markmail.org/● MARC (Mailing List ARChives)● Soon

– http://flossmetrics.org– http://researchfriendly.org

http://apache.markmail.org/

http://flossmetrics.org/

http://researchfriendly.org/


Version control

● See Introduction to Subversion during the Introduction course

● In this course, advanced topics● Research using the Version Control

System


Log of the version control

● Valuable source of information● Highly used for research purposes● Commit messages vs original log● Some examples of research will be shown

in this course


Example of results: CIA

● http://cia.vc/● Using the commit messages sent to the

commit mailing list

http://cia.vc/


Example of results: Libresoft.es

● CVSAnalY web interface● CVSAnalY whole SF.net dataset● http://libresoft.es/Results/

http://libresoft.es/Results/


Bug trackers

● Issue tracking systems● Life cycle of a bug● Many software systems for bug tracking

– Bugzilla– GNATS– Issue Tracker in Gforge– Trac


Life cycle of a bug


Recommendations

● Always report bugs...● ...but make sure that it is a bug● ...and it has not yet been reported● Provide test cases, memory dumps, etc● Provide concise information about your

system– Are you using the original sources or a

package of your distribution?– Which version?


IRC

● Synchronous communication system● Channels● More informal than mailing lists● Typically, not archiving


Pasting in a channel

● Don't flood the channel● Use a paste site

– Pastebin


Other tools

● Wikis● Web site● Forums● Blogs● Planets


Canned hosting or own solutions?

● Many sites provide hosting for libre software projects

● SourceForge.net● Morfeo-Project.org● Easier management of the community● Large and “traditional” projects prefer

customized solutions


Questions?

● Take a look at the materials of the course● Deep details are provided

Infrastructure for the community

Technology

Transcript of Infrastructure for the community