Abstract

To survive and thrive, a must attract new members, retain them, and help them be productive [1]. As openness becomes the norm in research, software development, and education, knowing how to do this has become an essential skill for principal investigators and managers alike. A growing body of knowledge in sociology, anthropology, education, and software engineering can guide decisions about how to facilitate this. What exactly do we mean by community? In the case of open source and open science, the most usual meaning is a community of practice. As defined by Lave and Wenger [2, 3], groups as diverse as knitting circles, oncology researchers, and web designers share three key characteristics: Participants have a common product or purpose that they work on or toward. They are mutually engaged, i.e., they assist and mentor each another. They develop shared resources and domain knowledge. Brown [4] specializes this to define a community of as …a formed in pursuit of a common goal. The goal can be definite or indefinite in time, and may not be clearly defined, but it is something that (generally speaking) the is aligned on. People working to preserve coral reefs in the face of global climate change are an example of such a community. No central organization coordinates their work, but the scientists who study coral reefs, the environmentalists who work to protect them, and the citizens who support them financially and politically are aware of each other’s efforts, collaborate in ad hoc ways, and are conscious of contributing toward a shared purpose. Open-source software projects are also communities of effort. E.g., the Mozilla Firefox [5] includes a mix of paid professionals, highly involved volunteers, and occasional contributors who not only create software, documentation, and tutorials but also organize events, answer questions in online forums, mentor newcomers, and advocate for open standards. Every of effort has unique features, but they have enough in common to profit from one another’s experience. The 10 rules laid out below are based on studies of such communities and on the authors’ experience as members, leaders, and observers. Our focus is on small and medium-sized projects, i.e., ones that have a handful of to a few hundred participants and are a few months to a few years old but may not (yet) have any formal legal standing, such as incorporation as a nonprofit.

Highlights

  • To survive and thrive, a community must attract new members, retain them, and help them be productive [1]

  • As openness becomes the norm in research, software development, and education, knowing how to do this has become an essential skill for principal investigators and community managers alike

  • In studying the evolution of how content is formed in these communities [37], newcomers can better understand the norms of a community and the best way to contribute [38]

Read more

Summary

Introduction

A community must attract new members, retain them, and help them be productive [1]. OPEN ACCESS Citation: Sholler D, Steinmacher I, Ford D, Averick M, Hoye M, Wilson G (2019) Ten simple rules for helping newcomers become contributors to open projects. Open-source software projects are communities of effort.

Results
Conclusion
Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call