This repository contains details on what is needed for Call for Code projects to join the Linux Foundation under the Call for Code umbrella.
-
The LF provides a neutral home for the open source code that can power many business models on top
-
The project legal structure provides a way for many participants to improve the underlying technology
-
The LF has many avenues to access developers, funding, mentorship, events, and marketing
-
Successful projects depend on an ecosystem to develop solutions that the market will adopt. Adoption drives sustainability.
-
Learn more in this detailed presentation.
Once we have worked out the intended mission and scope of the sponsored project, we work to build out a formation group to draft the governance documents and finalize the project structure as a community.
Towards the end of the formation process we often convene a marketing team, and the LF will prepare the launch press release with input and feedback from the marketing team.
In addition to increased efficiency, working in formation teams allows for the community to begin collaborating before the project even formally launches.
- Prepare mission and scope statement for the Linux Foundation Technical Charter
- Analyze code for license consistency with Apache 2 LICENSE or other as needed
- Assess ecosystem of launch partners who would be part of the announcement (Ideally at least 1)
- Choose new name or hand over existing names and trademarks
- Identify marketing, content, communications or other needs for the project (including from IBM)
- Prep content for developers to take part in the project on day one
- Choose Technical Steering Committee members
- Prepare Slack channel or workspace for contributors
- Evaluate LFX options for marketing, community, funding
- Add the Apache 2 LICENSE to your GitHub repository and include the specific copyright header to your source code files using the relevant comment syntax for the programming language. Add the license file as is, then use the current year and list the names of your team members in your individual source files.
- Look at improving your documentation so that first time visitors clearly see the problem you are solving and how they can understand the solution in your README.md. Also consider enabling alternative language translations.
- Look at carefully documenting installation/duplication steps so that new developers can explore the technology on their own systems in order to contribute back fixes. This will also help you identify any potential dependency issues you might have on clean installations.
- Add a basic CONTRIBUTING.md that describes how others can start to collaborating with you. The Linux Foundation has a few sample files you can use for inspiration. The way you choose to accept fixes is up to you though.
- Strongly consider adding the Developer Certificate of Origin bot to your repositories. This provides assurance that anyone who contributes to your repository has the rights to the code they want to provide.
- Consider configuring GitHub pages to create a basic description and FAQ site, like gql.foundation
- Won the Call for Code Global Challenge in October 2018
- Executed an IBM Service Corps deployment, incubation, and field tests in 2019
- Created new ClusterDuck Protocol name and project at LF in March 2020
- The Project OWL name continues to be used for the successful startup
- The ClusterDuck Protocol has its own open source repo and web site
- Won the Call for Code Global Challenge in October 2019
- Executed an IBM Service Corps deployment, incubation, field tests in 2020
- Created new Pyrrha name and project at LF in July 2021
- The Prometeo name continues to be used for the successful startup
- The Pyrrha project has its own open source organization and web site
- Runner up in Call for Code Global Challenge in October 2018
- Created a new project named ISAC-SIMO, based on PD3R, in 2020
- Brought the ISAC-SIMO project and name to the LF in July 2021
- The Build Change name was used before and after for the non-profit organization
- The ISAC-SIMO project has its own open source organization and web site
- Won the IBMer Call for Code Global Challenge in October 2019
- Executed an IBM Service Corps deployment, incubation, field tests in 2020
- Transferred the Liquid Prep trademark to the LF in March 2021
- The Liquid Prep community, not a separate legal entity, manages the project
- Joined the Code and Response community in February 2020
- Created a new project named OpenEEW, in 2020
- Brought the OpenEEW project and name to the LF in August 2020
- The Grillo name was used before and after for the startup
- The OpenEEW project has its own open source organization and web site
- Won the IBMer Call for Code Global Challenge in October 2020
- Created a new project named OpenTempus, in 2022
- Brought the OpenTempus project and name to the LF in December 2022
- The OpenTempus project has its own open source organization and web site