Over time, people have come up to me asking how to best publish code as an Open Source project. I end up sharing the same resources over and over - so I'm collecting them here.

Most people come to free and open source software in three stages: Typically, first people use projects. In a later development people try to publish their own code - not thinking much about the burden of maitainership. At some stage, most people realize the value that exists when contributing changes back to projects, become involved more, likely start taking on leadership roles in existing projects - likely leading efforts to publish code and growing a community around it later on.

• Using Open Source

  • See https://tech.europace.de/oss-downstream/ for criteria for selecting Open Source projects to use (German language)

• Contributing to Open Source

  • See https://github.com/MaineC/ribbit for arguments to help you make a decision to contribute to existing Open Source projects

• Publishing Open Source projects

• Article: Mozilla Open Source archetypes ... OSS and business models - why should I decide to go for an Open Source route?
• Series: IEEE Open Source expanded ... IEEE article series (why do people decide to publish projects, how do they solve problems along the way?)
• Book: Producing Open Source Software ... OSS best practices (how to run a successful Open Source project)
• Book: Building successful online communities ... Online community building - how to grow your project online
• Book: Open organization ... leading open teams - why and how to lead open teams
• Book: Reinventing organizations ... top down vs bottom up - why and how to lead teams in a decentralized fashion
• Webpage: Choose a foundation ... help with choosing an open source foundation as home for your project

Collaboration groups:

• TODO Group, "TODO is an open group of companies who want to collaborate on practices, tools, and other ways to run successful and effective open source projects and programs."
• CHAOSS, open source metrics
• InnerSource Commons, while focussed on using open source collaboration inside of organisations it provides clear, concise patterns on those exact collaboration patterns that help understand where the value of Open Source is coming from and how to benefit from it.

• Open Chain project, Open Source strategy template from a license compliance perspective
• German Open Chain Spec

Talks:

• Best practice: Delegate like a boss, Deb Nicholson
• Best practice: FOSS Governance, the good, the bad and the ugly, Deb Nicholson
• Best practice: Open collaboration, Bertrand Delacretaz
• Background: Corporate Shenanigans, Mike Milinkovich
• Background: The selfish contributor explained
• Best practice: Community anti-patterns, Mark Thomas
• Background: Governance in Open Source, Shane Coughlan
• Best Practice: Mentoring, Rich Bowen
• Best Practice: Async decision making, Bertrand Delacretaz
• Best Practice: Passing the baton, VMBrasseur

Self check and training material:

• Maturity model: Apache maturity model
• Apache Way for corporate players: Horthonworks internal training
• Apache Way for corporate players: Confluent internal guidelines
• Apache Way for corporate players: Google internal training

More self certification:

• CII - certify core OSS infrastructure
• REUSE
• ClearlyDefined - license, docs, security

• Background: The core values of software Freedom, Matthias Kirschner

• Background: Open Source at the European level, Thomas Gageik
• Background: The impact of tech when roled out without taking local conditions into consideration, Nanjala, Nyabola
• Background: some history behind the ASF, Danese Cooper
• Background: Open Source for rocket scientists, Andreas Schreiber