Levels of Formality in FOSS Communities

  • Andrew Schofield
  • Grahame S. Cooper
Part of the IFIP — The International Federation for Information Processing book series (IFIPAICT, volume 234)


One of the aspects of Free and Open Source Software (FOSS) which may act as a significant deterrent to its adoption, is the method used to collaboratively develop the software and provide support through the use of communities. It is not until this method is examined more closely that its many advantages can be realised. The method can, however, seem very disorganised especially when compared with traditional proprietary development styles. A key difference between these two development approaches lies in the management of projects, and perhaps as a consequence, in the level of formality in the community environment. This paper presents the results of empirical survey research investigating FOSS community participants’ views on the level of formality in FOSS, and the way in which this affects both development and support provision activities. The paper then concludes by analysing what can be learnt from the participant’s views.


Large Project Cultural Formality Managerial Formality Proprietary Software Informal Environment 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

5 References

  1. 1.
    Ghosh, R., A., Glott, R., Krieger, B., Robles, G. (2002), “Survey of Developers”, Free/Libre and Open Source Software: Study and Survey, International Institute of Infonomics, University of Maastricht, The Netherlands, Available at: http://www.infonomics.nl/FLOSS/report/, (Accessed May 2006)Google Scholar
  2. 2.
    Hann, I. H., (2004) “Why Developers Participate in Open Source Software Projects: And Empirical Study”, Twenty-Fifth International Conference on Information Systems.Google Scholar
  3. 3.
    Hertel, G., Niedner, S., Herrmann, S. (2003), “Motivation of Software Developers in Open Source Projects: An Internet-based Survey of Contributors to the Linux Kernel”, Research Policy, Special Issue on Open Source Software Development, Available at: http://opensource.mit.edu/papers/hertel.pdf,(Accessed February 2004)Google Scholar
  4. 4.
    Lakhani, K. R., Wolf, R.G. (2003), “Why Hackers Do What They Do: Understanding Motivation Effort in Free Open Source Software Projects”, MIT Sloan School of Management Working paper, Available at: http://freesoftware.mit.edu/papers/lakhaniwolf.pdf, Accessed (February 2004)Google Scholar
  5. 5.
    Moody, G. (2001), “Rebel Code: How Linus Torvalds, Linux and the Open Source Movement Are Outmastering Microsoft”, The Penguin Press, EnglandGoogle Scholar
  6. 6.
    Oh, W., Jeon, S., (2004) “Membership Dynamics and Network Stability in the Open-Source Community: The Ising Perspective” Twenty-Fifth International Conference on Information Systems.Google Scholar
  7. 7.
    Pavlicek, R. C. (2000), “Embracing Insanity: Open Source Software Development”, Sams Publishing, USAGoogle Scholar
  8. 8.
    Scacchi, W., Feller, J., Fitzgerald, B., Hissam, S., Lakhani, K., (2005) “Understanding Free/Open Source Software Development Processes”, Available at: (http://www.ics.uci.edu/~wscacchi/Papers/New/SPIP-FOSS-Intro-Dec2005.pdf) (Accessed December 2005)Google Scholar
  9. 9.
    Schofield, A., Mitra, A. (2005), “Free and Open Source Software Communities as a Support Mechanism”, UK Academy of Information Systems conference 2005, Newcastle, UKGoogle Scholar
  10. 10.
    Zhang, W. & Storck, J, (2001) “Peripheral Members in Online Communities”, Americas Conference on Information Systems, Boston, USAGoogle Scholar

Copyright information

© International Federation for Information Processing 2007

Authors and Affiliations

  • Andrew Schofield
    • 1
  • Grahame S. Cooper
    • 2
  1. 1.Salford Business SchoolUniversity of SalfordSalfordUK
  2. 2.School of Computing, Science, and EngineeringUniversity of SalfordSalfordUK

Personalised recommendations