Why Modern Open Source Projects Fail

• Survey of 414 devs 29% response rate
• Why open source projects fail?
  • Usurped by competitor Environment 27
  • Obsolete Project 20
  • Lack of time Team 18
  • Lack of interest Team 18
  • Outdated technologies Project 14
  • Low maintainability Project 7
  • Conflicts among developers Team 3
  • Legal problems Environment 2
  • Acquisition Environment 1
• What practices impact success?
  • Contributing guidelines (large impact)
  • Continuous integration (medium impact)
  • Licences, home pages, and issue templates (small impact)
• Strategies to overcome and unmaintained account
  • Move to an org account
    • “with this kind of account it would be easier to attract new maintainers and to manage permissions.”
  • Transfer ownership [unsucccessful]
    • “We tracked the activity of the new maintainers, until February, 2017. They did not perform significant contributions to the projects, despite minor commits”
  • Accepting new core developers
    • ”volunteers offered to help with the maintenance, as core developers”
    • They were either turned away by the original owner or the owner requested a plan for development which the new core devs viewed as too high of a barrier to entry

http://opensourcesurvey.org/2017/

• Documentation helps orient newcomers: how to use a project, how to contribute back, the terms of use and contribution, and the standards of conduct in a community. Improving that documentation is an impactful way to contribute back to open source.
• When communicating on a project, use clear and accessible language for people who didn’t grow up speaking English, or read less-than-fluently.
• [My Thoughts] I wonder if, in creating the original documentation, we could 1) emphasize Karen’s vision for a tool used for the greater good and to protect the people and 2) interweave some feedback culture i.e. if you have a conflict, discuss in a private way rather than a public way. What would the downside to that be? Would it require private messaging? Is that a layer of complexity beyond? Would it be worth the investment? Could it be abused? Negative experiences impact project health
• Rudeness is the #1 negative behavior. How can that be somewhat negated upfront? State that part of the project credo is “Assume everyone is doing the best they can with what they know at that time?”
• [!!!!] The gender imbalance in open source remains profound: 95% of respondents are men; just 3% are women and 1% are non-binary.
• Half of contributors say that their open source work was somewhat or very important in getting their current role.
• Stability & security are top 2 in what users value in OS projects

https://opensource.guide/

• No matter which stage you decide to open source your project, every project should include the following documentation:
  • Open source license
  • README
  • Contributing guidelines
  • Code of conduct – https://opensource.guide/code-of-conduct/
• Name – What would it be called without the RIOT front end? http://ivantomic.com/projects/ospnc/
• How can we provide entry points for newbies to triage bugs/issues?
  • https://opensourcefriday.com/
  • https://www.codetriage.com/

image: By Bundesarchiv, Bild 102-09312 / CC-BY-SA 3.0, CC BY-SA 3.0 de, https://commons.wikimedia.org/w/index.php?curid=5414490

Part of my research is looking at what makes an open source project successful. Community has begun to emerge as a theme not only in researching open source projects, but also AI, global social unrest, and RIOT as a whole.

My initial thought on how to build a community for an open source project was really about attracting enough people. One of my ideas was to figure out who was already an important person in open source, get that person or those people on board and that would organically attract other people. Another thought I had was to market the project to people by targeting their specific interests. Taking a Netflix approach. “Hey I see you liked an open source project about facial recognition, perhaps you would like this project!”

I had the opportunity to talk to Sandra Ordonez, co-founder of the Internet Freedom Festival. I wanted to know from her what the magic formula was for building a new community. The secret, she told me, was…that…there really isn’t one. Her insight might seem obvious, but I truly thought if we target the right groups of people that would be a more efficient way of building a community. That strategy might still build a community, but it would likely be weak and subject to crumbling given the first sign of stress for individuals or small groups.

Building a strong community is an incredibly bespoke process. It is about looking at the strengths and challenges of the individuals and figuring out the best way to build relationships. It is a messy process that doesn’t have a set algorithm for success. What works in one situation may have a negative impact in another situation. What’s most important she says is, “seeing everyone as an individual and understanding they are not just a mass but a person with real feelings, emotions, goals.” People have to know each other and be invested in each other’s success in order for the project to also succeed.

While I haven’t used AIM in ages, other tech has taken its place. For example, I met one of my best friends through Foursquare. The Foursquare app (the check-in portion is now called Swarm) allowed users to create and name their own places. I created a spot for my house and named it Hall of Justice. Both being comic enthusiasts, we started chatting and became friends offline as well. Neither of us use Foursquare anymore, but our friendship has sustained. Building a strong community is a very messy and unpredictable process. The key, however, is that even if the project falls away, the connections between the people would still remain.

This was just the start of my adventure into the world of open source. This foundation of community is important because ultimately, to build the project, the community has to be happy. For example, GitHub points out the importance of documentation that is up-to-date and easy to read for both users and contributors as one quality that keeps the community happy. New questions and ponderings develop with each person I talk to and article I read. An article from Knight Lab at Northwestern University suggested having a clear vision for the project which made me wonder, what is the vision, who and what will be impacted the most by such a project? How can the vision for the project be expressed via the code of conduct and documentation? In the weeks to come, I’ll answer these questions and more in my adventures in open source.

Image: By Ryan Cash of Snowman (Ryan Cash of Snowman, via email) [CC BY-SA 3.0 (https://creativecommons.org/licenses/by-sa/3.0)%5D, via Wikimedia Commons