Project Joining

Overview

Thank you for your interest in joining Libre Space Foundation as a project.

This document provides a simple list of the LSF’s expectations of any Libre Space project, with pointers to the detailed policies or best practices. “Libre Space project” specifically means a top level project at the LSF.

1. Some things projects MUST do are requirements; failure to follow those will result in the board taking action to correct the issue.

2. There are many best practices that projects SHOULD do. Broad experience at the LSF shows these are proven methods that work well.

3. The LSF and some Libre Space projects have other suggestions and practices that projects MAY do.

Ultimately, Libre Space projects report to, and are responsible to, the Libre Space Foundation Board, which mandates these policies for the LSF as a whole.

Governance

1. Project decisions and direction MUST adhere to the Libre Space Manifesto.

2. Project technical decisions MUST be made and communicated on public and archived places.

3. Project discussions and interactions SHOULD be held in public in accessible, asynchronous and archived places.

4. Project discussions SHOULD use normal LSF-hosted communication channels.

5. Projects MAY use a documented consensus process or a VOTE for any new committers or project manager members, and carefully follow policies for granting access.

6. Projects MUST provide a quarterly status report to the Board.

7. Projects MUST govern themselves independently of undue commercial influence, and for the best interests of the project community as a whole.

Technical

1. The primary source control repository MUST be administered by the LSF Infra team on LSF organizational accounts.

2. Project SHOULD follow available tests and validation, preferrably included in a continuous integration process.

3. Project SHOULD use common LSF projects set-up.

4. Projects SHOULD use fully open source tool chains: all tools used in a Libre Space project SHOULD be open source and compatible to avoid locks.

Legal

1. Projects MUST use an open-source copyleft license for anything developed and released within the project, clearly marked in the source repository including LICENSE, and source headers.

2. Projects MUST NOT include software with unapproved or restricted licenses in Libre Space project releases unless following explicit exceptions.

3. Projects MAY include software with approved compatible licenses in Libre Space project releases.

Brand

1. Project websites and materials MUST comply with the Libre Space Project Branding Requirements.

2. Projects MAY request trademark registration and ownership by Libre Space Foundation.

Press & Marketing

1. Projects MUST work with Board Champion and Communications team on any formal press releases.

2. Projects SHOULD work with LSF Communications team to help coordinate any press, media, or analyst relations, or for marketing assistance.

How LSF assists

For all approved LSF projects the following support applies:

1. LSF SHOULD provide all needed infrastructure and tools for project development, deployment and operations. (e.g. repositories, discussion forums, servers)

2. LSF SHOULD sponsor the creation of a brand identity if the project is missing one.

3. LSF SHOULD provide legal guidance and help for a project.

4. LSF MUST provide governance, management and development guidance as requested by a project.

5. LSF MUST evaluate funding applications as submitted by a project and, if approved by the board, provide the funding and support around it. (e.g. development funds, internships, travel funding, event funding, tools and hardware).

6. LSF Board Champion of the project MUST work closely with the project manager or committee to ensure timely goal excecution and smooth project development.

Joining Process

1. A project interested in joining Libre Space Foundation should review the conditions above and note possible incompatibilities or points needing clarification and/or discussion.

2. The project should initiate contact with the Board sending an email directly to a board member or board@ expressing interest.

3. The Board appoints a Board Champion to work with the project ensuring compatibility of the application.

4. The Board votes on accepting the project as a Libre Space Foundation project.

5. All necessery actions regarding project transition to LSF Project are done by the Board Champion and the Libre Space Foundation Operations team.

6. Communications team coordinates the announcement of the project joining LSF.