Difference between revisions of "MOSS incubation overview"
m |
m |
||
Line 60: | Line 60: | ||
| Participatory<br /> | | Participatory<br /> | ||
- Code of conduct | - Code of conduct | ||
− | | TBD | + | | ''##TBD##'' |
| | | | ||
| X | | X |
Revision as of 00:22, 17 August 2021
Responsibility | MOSS | Website Listing | OSGeo Community | OSGeo Project |
---|---|---|---|---|
Geospatial - README or project description |
YES | X | X | X |
Geospatial - User guide or quickstart |
YES (from 1987) | X | X | |
Free or Open Source License - See LICENSE.md |
YES: Free | X | X | X |
Free or Open Source License - Check headers |
YES: Public Domain (included in all headers ?) | X | X | |
Free or Open Source License - Providence Review |
YES: Public Domain (MOSS came first (freedom zero), predates FOSS licences) | X | ||
Participatory - See CONTRIBUTING.md |
YES (github OSGeo/MOSS) | X | X | X |
Participatory - History of pull requests or patches |
YES (github OSGeo/MOSS) | X | X | |
Participatory - Code of conduct |
##TBD## | X | X | |
Open Community - communication channel |
YES: Mailing list | X | ||
Active Healthy Community - user and developer collaboration |
YES + YES: Maintainer team (since 2020), Open Access Publication (DOI/Zenodo) | X | ||
Development Process - version control |
YES: Version Control, open to new members, transparency, no issue tracker (yet) | X | ||
Documentation - user documentation |
YES (user + dev documentation from 1987 and older) | X | ||
Release Procedure - release process |
YES (from 1987) | X | ||
Foundation Resources | MOSS | Website Listing | OSGeo Community | OSGeo Project |
website project list | YES: MOSSGIS.org, MOSS.osgeo,org: pending | X | X | X |
website choose-a-project | ##TBD## (does this make sense for a heritage project ?) | X | X | X |
OSGeo Live | ##TBD## (potential feature: include PC MOSS and a MSDOS simulator for browser-based execution) | X | X | X |
Marketing Collateral | ##TBD## | X | X | |
Representation | ##TBD## | project officer | ||
infrastructure and facilities | ##TBC## | X | X | |
promotion & marketing | ##TBD## (we need tshirts!) | X | X | |
budget | ##TBD## (no need?)(òption: funding for MOSSGIS.org) | osgeo board | project budget | |
fundraising | ##TBD## (no need) | X | X |
Branding
Community | Project |
---|---|
Step 1: Add OSGeo Website Project Page
To be listed on the OSGeo website:
- Be geospatial
- Confirm by checking README or project description
- Have a free license or open source license
- The license must be OSI approved
- Welcome participation and new contributors.
- We look for a clear contribution policy
If you have questions about the above, or would like guidance on setting up your open source project, please reach out to us.
Step 2: Join Community Projects Program
Projects applying to the *OSGeo Community* program are asked to:
- Be geospatial
- Confirm by checking README or project description
- project page on the osgeo website
- We ask projects have some user documentation, for example an OSGeo Live quickstart
- Have a free license or an open source license.
- The license must be OSI approved
- We ask that the project team check the file headers and double check the license has been appropriately applied
- Welcome participation and new contributors.
- We look for a clear contribution policy
- We ask that the project demonstrate collaboration, perhaps with a history of bug report or pull requests
- Projects are required to have a code of conduct
OSGeo provides code of conduct guidance, many projects selecting contribution covenant).
OSGeo Community Projects can take part in the incubation committee for guidance on open source use, setting up project governance, promoting the project, and building the project community. We look forward to working with you.
Step 3: Incubation process and Graduation
The *OSGeo Project* designation is intended to recognize established projects with a diverse community of developers and users with a proven track record.
To be recognized as an *OSGeo Project* a project team applies for the OSGeo incubation program. Successful projects are teamed up with an experienced open source mentor to help answer questions, obtain legal council, and help guide work on transparency and community development as required.
Although incubation is a lot of work, this is opportunity for project teams to grow and improve and be publicly recognized for their accomplishment.
To be recognized as an *OSGeo Project* we ask that project teams excel in each of areas mentioned above, see graduation checklist or the comparison table on this page for more detail.
The OSGeo incubation process takes place in three stages:
- Initial Application
- Application request
- Mentor volunteer
- Incubator
- Project Status: project details, and a few resourcing questions for the system admin committee (see Project Status Template).
- Provenance Review: project team check to ensure the project is open source and has permission to distribute its source code.
- Project team and mentor work on graduation checklist priorities
- Graduation
- Mentor recommends project for graduation with motion to the incubation committee
- Committee chair informs the OSGeo board, who appoints the project team as a newly formed OSGeo committee