Skip to main content
Log in

The search for a research method for studying OSS process innovation

  • Published:
Empirical Software Engineering Aims and scope Submit manuscript

Abstract

Medium-sized, open-participation Open Source Software (OSS) projects do not usually perform explicit software process improvement on any routine basis. It would be useful to understand how to get such a project to accept a process improvement proposal and hence to perform process innovation. We want to determine an effective and feasible qualitative research method for studying the above question. We present (narratively) a case study of how we worked towards and eventually found such a research method. The case involves four attempts at collecting suitable data about innovation episodes (direct participation (twice), polling developers for episodes, manually finding episodes in mailing list archives) and the adaptation of the Grounded Theory data analysis methodology. Direct participation allows gathering rather rich data, but does not allow for observing a sufficiently large number of innovation episodes. Polling developers for episodes did not prove to be useful. Using mailing list archives to find data to be analyzed is both feasible and effective. We also describe how the data thus found can be analyzed based on the Grounded Theory Method with suitable adjustments. By-and-large, our findings ought to apply to studying various phenomena in OSS development processes that are similarly heavyweight and infrequent. However, specific details may block this possibility and we cannot predict which details that might be. The amount of effort involved in direct participation approaches to qualitative research can easily be underestimated. Also, survey approaches are not well-suited for many process issues in OSS, because too few developers are sufficiently process-conscious. An approach based on passive observation is a viable alternative in the OSS context due to the availability of large amounts of fairly complete archival data.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Fig. 1
Fig. 2
Fig. 3
Fig. 4

Similar content being viewed by others

Notes

  1. This is opposed to the few large high-profile projects such as Apache, Linux, OpenOffice, or Mozilla, many of which are carried to a large degree by a formal organization (O’Mahony 2005).

  2. http://www.kde.org/

  3. http://www.gnome.org/

  4. Bergquist and Ljungberg (2001) call such behavior towards OSS projects a code gift and consider it an important means for gaining influence.

  5. http://www.freecol.org/

  6. In particular user lists of tools and APIs commonly used for Open Source development such as http://lists.boost.org/mailman/listinfo.cgi/boost (a C+ + library for common application development tasks), http://lists.gnu.org/mailman/listinfo/autoconf (a package for generating platform-specific scripts to be used in the build-process of applications), http://subversion.tigris.org/ds/viewForumSummary.do?dsForumId=1065 (a software for source code version management), http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org (a multimedia library for accessing input and graphics devices), and http://lists.mozilla.org/listinfo/support-bugzilla (a software for bug-tracking).

  7. We also received a small number of critical comments by email, for instance “1) This is lame. 2) You get paid for this and we don’t”.

  8. The Debian project collects many packages of OSS software, performs package management (in particular dependency modeling) on them, and develops a package management software. Krafft (2009, p.xiii) calls Debian “arguably the largest OSS project with over 1000 developers”.

  9. http://gmane.org

  10. For instance, the threads titled “Changes to U-Boot Development Process” and “Making it Easier to Contribute to Bugzilla (2007 Edition)” turned out to represent innovation episodes, while “Talking about regressions...” and “Quietly promoting ArgoUML” did not.

  11. In order to avoid distorting the observations, it is important that exactly appropriate concepts be used. This is easiest to achieve when new concepts are being invented specifically for this analysis. When previously existing concepts are used, they have to be “re-invented”.

  12. http://gmanda.sf.net

References

Download references

Acknowledgements

The authors would like to thank Robert Schuster, Luis Quintela-Garcia, and Alexander Roßner, who conducted three of the studies as part of their theses, and the participants of the Open Source projects without whom this work would not have been possible. We thank the reviewers for insisting on some changes that make this article a less complicated read.

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Lutz Prechelt.

Additional information

Editors: Carolyn Seaman, Jonathan Sillito, Rafael Prikladnicki, Tore Dybå, and Kari Rönkkö

Rights and permissions

Reprints and permissions

About this article

Cite this article

Prechelt, L., Oezbek, C. The search for a research method for studying OSS process innovation. Empir Software Eng 16, 514–537 (2011). https://doi.org/10.1007/s10664-011-9160-1

Download citation

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s10664-011-9160-1

Keywords

Navigation