Information management as an explicit role in OSS projects

Globally distributed teams of volunteers and communication by electronic means are at the core of Open Source Software development. To help projects in managing their information, we defined a lightweight , role-based process improvement and observed its use in a longitudinal case study. Results gathered by mailing-list analysis give insights into the different types of information managed and their relative importance: While technical content such as how-tos and to-dos is most frequent, the amount of information regarding decision making is surprisingly low.

[1]  Kellogg S. Booth,et al.  Coordinating open-source software development , 1999, Proceedings. IEEE 8th International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises (WET ICE'99).

[2]  Kouichirou Eto,et al.  qwikWeb: integrating mailing list and WikiWikiWeb for group communication , 2005, Int. Sym. Wikis.

[3]  Mark S. Ackerman,et al.  Beyond threaded conversation , 2005, CHI EA '05.

[4]  Kevin Makice PoliticWiki: exploring communal politics , 2006, WikiSym '06.

[5]  Christian Pentzold,et al.  Foucault@Wiki: first steps towards a conceptual framework for the analysis of Wiki discourses , 2006, WikiSym '06.

[6]  L. Prechelt,et al.  On Understanding How to Introduce an Innovation to an Open Source Project , 2007, First International Workshop on Emerging Trends in FLOSS Research and Development (FLOSS'07: ICSE Workshops 2007).

[7]  Jim Hewitt Beyond Threaded Discourse , 2001 .

[8]  Ann Majchrzak,et al.  Enabling knowledge creation in far-flung teams: Best practices for IT support and knowledge sharing , 2004, IEEE Engineering Management Review.

[9]  Linda C. Smith,et al.  INFORMATION QUALITY DISCUSSIONS IN WIKIPEDIA , 2005 .