OSL Alliance #
OSL Alliance is Open Science Labs' single program for mission-aligned open-source projects. It replaces the former Project Affiliation and Project Incubation programs, bringing their overlapping benefits and project listings together in a structure that is easier for maintainers, contributors, and OSL volunteers to understand and operate.
The change is primarily organizational: existing benefits remain largely unchanged. Projects can gain visibility, connect with the OSL community and other maintainers, access shared knowledge and eligible infrastructure, seek mentoring or technical guidance when available, and propose participation in contributor programs such as Google Summer of Code. Access to limited programs, contributor slots, mentoring, or funding is never guaranteed and depends on readiness and available capacity.
A shared commitment #
OSL supports member projects, and member projects help OSL operate and grow. Each Alliance project is expected to identify a maintainer representative who can participate in the Alliance Maintainers Council and contribute to community work according to the team's expertise and availability.
Examples include reviewing affiliation requests or project ideas, mentoring contributors, answering questions, improving OSL websites and infrastructure, developing bots or scripts, helping organize programs and events, outreach, and identifying sponsors, grants, or partner relationships. These are flexible ways to help, not a requirement to perform every task. OSL and the Council will keep coordination and contribution recording lightweight and will communicate changes in expectations with reasonable transition time.
The Council helps coordinate cross-project activities and advises OSL leadership. It is not a replacement for OSL's governing board, and membership does not automatically grant legal board authority.
Membership and project independence #
Alliance members retain control over their own repositories, licenses, intellectual property, roadmaps, technical decisions, governance, and releases. OSL membership is not a certification or a guarantee of long-term maintenance, funding, interns, reviewers, or GSoC participation.
Projects should have an OSI-approved open-source license, a public Code of Conduct, at least one reachable maintainer, public development and contact channels, and alignment with OSL's values. A mature or stable project does not need to make frequent commits to remain responsibly maintained.
Applying #
Open a request in the OSL Alliance requests repository. Share a project description, repository and documentation links, license, Code of Conduct, maintainer contacts, maintenance status, and what kind of involvement you expect. OSL will review eligibility and follow up if anything needs clarification.
For current members of the former affiliation or incubation programs, the main change is participating in the shared Council and identifying ways to help the wider OSL community. Existing project listings have been combined in the Alliance directory. Any additional onboarding steps or changes to expectations will be explained directly to maintainers in advance.