Difference between revisions of "OSGeo Community Projects"

From OSGeo
Jump to: navigation, search
(OSGeo Technology Project Selection Criteria)
(About OSGeo Community Projects)
 
(78 intermediate revisions by 7 users not shown)
Line 1: Line 1:
This is an OSGeo outreach initiative promoting "open source and participatory" geospatial technology. This outreach effort is undertaken by the OSGeo incubation committee to assist projects with open source and community development.
 
  
This initiative is currently being renamed (from OSGeo Labs) due to a conflict with GeoForAll committee use of the term.
+
This wiki page is a scratchpad of ideas forming the osgeo community program. To see how these ideas have been realized please see our [http://osgeo.org/committees/incubation website page].
  
See http://wiki.osgeo.org/wiki/Category:OSGeo_Labs
+
= Purpose =
  
== Purpose ==
+
The purpose of *OSGeo Community* projects is help foster innovation and include more project teams in the Open Source Geospatial Foundation.
  
Welcome to OSGeo Technology. The projects listed here are part of the Open Source Geospatial Foundation and range from new experimental projects to established pillars of our open source ecosystem.
+
= OSGeo support for project teams =
  
All projects here meet our goals as an organization - they are open source (no really we checked) and are inclusive and welcoming to new contributors. Projects that go on to establish excellence in community building, documentation, and governance can enter our "incubation" program.  
+
If you would like your software project to listed on the website, or apply to become an OSGeo community project, please send a description of your project to the [http://lists.osgeo.org/mailman/listinfo/incubator OSGeo Incubation Committee Mailing List]. We look forward to helping you!
  
=== Volunteers Needed ===
+
== About OSGeo Website Project List ==
  
The volunteers that work as part of OSGeo Technology Projects have the goal of helping OSGeo Technology Project qualify for incubation. To reach this goal,OSGeo Technology Project volunteers help OSGeo Technology Project with the following tasks:
+
To be listed on the OSGeo website:
  
* Project marketing.
+
# Be geospatial
* Development of user and programmer communities.
+
#* Confirm by checking README or project description
* Establishment of programs and policies for project documentation, copyright assignment, and licensing.
+
# Have a free license or open source license
* Establishment of programs and policies for software development. This includes version tracking, bug tracking, and feature request tracking, creation of a development road map, and organization of code sprints/events.
+
#* The license must be OSI approved
* Establishment of project governance programs and policies.
+
# Welcome participation and new contributors.
* Collaboration on technical standards, data formats, and code sharing with other open source geospatial software projects.
+
#* We look for a clear contribution policy
* Utilization of software development infrastructure like mailing lists, bug trackers, version control software/hosting, and web hosting.
+
  
== Comparison with Incubation ==
+
If you have questions about the above, or would like guidance on setting up your open source project, please reach out to us.
  
As shown below there is some overlap with the OSGeo incubation process.
+
== About OSGeo Community Projects==
 +
 
 +
In addition to being listed on the website, 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 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.
 +
 
 +
OSGeo provides [https://www.osgeo.org/code_of_conduct/ code of conduct guidance], many projects selecting [https://www.contributor-covenant.org/ contribution covenant]).
 +
 
 +
== About OSGeo Projects ==
 +
 
 +
To be recognized as an *OSGeo Project* we ask that project teams excel in each of areas mentioned above, see [https://github.com/OSGeo/osgeo/blob/master/incubation/documents/graduation_checklist.pdf graduation checklist] for more detail.
 +
 
 +
The *OSGeo Project* designation is intended to recognize established projects with a diverse community 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.
 +
 
 +
=== Comparison ===
 +
 
 +
As shown below there is some overlap requirements for an OSGeo projects (as defined by the  [http://www.osgeo.org/incubator/process/project_graduation_checklist.html incubation process] graduation checklist).
  
 
{| class="wikitable"
 
{| class="wikitable"
! style="text-align: center; font-weight: bold;" | Responsibility
+
! scope="col" width="310" style="text-align: center; font-weight: bold;" | Responsibility
! style="text-align: center; font-weight: bold;" | Technology
+
! scope="col" width="155" style="text-align: center; font-weight: bold;" | Website Listing
! style="text-align: center; font-weight: bold;" | Project
+
! scope="col" width="155" style="text-align: center; font-weight: bold;" | OSGeo Community
 +
! scope="col" width="155"  style="text-align: center; font-weight: bold;" | OSGeo Project
 
|-
 
|-
| Open Source
+
| Geospatial <br />
- check headers
+
- README or project description
 +
| X
 +
| X
 +
| X
 +
|-
 +
| Geospatial <br />
 +
- User guide or quickstart
 +
|
 +
| X
 +
| X
 +
|-
 +
| Free or Open Source License <br />
 
- See LICENSE.md
 
- See LICENSE.md
 +
| X
 
| X
 
| X
 
| X
 
| X
 
|-
 
|-
| Participatory
+
| Free or Open Source License <br />
 +
- Check headers
 +
|
 +
| X
 +
| X
 +
|-
 +
| Free or Open Source License <br />
 +
- Providence Review
 +
|
 +
|
 +
| X
 +
|-
 +
| Participatory<br />
 
- See CONTRIBUTING.md
 
- See CONTRIBUTING.md
 +
| X
 +
| X
 +
| X
 +
|-
 +
| Participatory<br />
 +
- History of pull requests or patches
 +
|
 +
| X
 +
| X
 +
|-
 +
| Participatory<br />
 +
- Code of conduct
 +
|
 
| X
 
| X
 
| X
 
| X
 
|-
 
|-
| Open Community
+
| Open Community<br />
- communication channel
+
- communication channel<br />
 
- decision making process
 
- decision making process
 +
|
 
|  
 
|  
 
| X
 
| X
 
|-
 
|-
| Active Healthy Community
+
| Active Healthy Community<br />
- user and developer collaboration
+
- user and developer collaboration<br />
 
- long term viability
 
- long term viability
 +
|
 
|  
 
|  
 
| X
 
| X
 
|-
 
|-
| Development Process
+
| Development Process<br />
- version control
+
- version control<br />
- issue tracker
+
- issue tracker<br />
- leadership open to new members
+
- leadership open to new members<br />
 
- transparent decision making
 
- transparent decision making
 +
|
 
|  
 
|  
 
| X
 
| X
 
|-
 
|-
| Documentation
+
| Documentation<br />
- user documentation
+
- user documentation<br />
 
- developer documentation
 
- developer documentation
 +
|
 
|  
 
|  
 
| X
 
| X
 
|-
 
|-
| Release Procedure
+
| Release Procedure<br />
- release process
+
- release process<br />
- documented testing process
+
- documented testing process<br />
 +
|
 
|  
 
|  
 
| X
 
| X
 
|-
 
|-
| style="font-weight: bold;" | Reward
+
| style="font-weight: bold;" | Foundation Resources
| style="font-weight: bold;" | Technology
+
! scope="col" width="155" style="text-align: center; font-weight: bold;" | Website Listing
| style="font-weight: bold;" | Project
+
! scope="col" width="155" style="text-align: center; font-weight: bold;" | OSGeo Community
 +
! scope="col" width="155"  style="text-align: center; font-weight: bold;" | OSGeo Project
 
|-
 
|-
| Foundation Representation
+
| website project list
| incubation chair
+
| X
 +
| X
 +
| X
 +
|-
 +
| website choose-a-project
 +
| X
 +
| X
 +
| X
 +
|-
 +
| OSGeo Live
 +
| X
 +
| X
 +
| X
 +
|-
 +
| Marketing Collateral
 +
|
 +
| X
 +
| X
 +
|-
 +
| Representation
 +
|
 +
|
 
| project officer
 
| project officer
 
|-
 
|-
| Foundation Resources
+
| infrastructure and facilities
- infrastructure and facilities
+
|
- budget, fundraising, marketing
+
| X
 +
| X
 +
|-
 +
| promotion & marketing
 +
|
 +
| X
 +
| X
 +
|-
 +
| budget
 +
|
 +
| osgeo board
 +
| project budget
 +
|-
 +
| fundraising
 +
|
 
| X
 
| X
 
| X
 
| X
 
|}
 
|}
  
== OSGeo Technology Project Selection Criteria ==
+
Activities with the OSGeoLive project or Marketing committee can be pursed at any time.
  
If your project would like to join OSGeo the technology initiative asks:
+
The incubation process establishes a project as a full fledged OSGeo committee, with a project project officer, with direct access to OSGeo treasurer, and reporting to the board during annual general meeting. While Community projects are not recognized as a committee, the OSGeo board maintains an "OSGeo Community" initiative with budget to support your activities. Attend one of the OSGeo board monthly meetings, or ask on the board mailing list, if your project has an activity that can benefit from financial support. For more information see [https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidance.pdf osgeo_financial_guidence.pdf]
  
# That your project is geospatial (or directly supports geospatial applications);
+
Available branding:
# Uses an OSI approved open source license;
+
# Participatory (accepts pull-requests)
+
  
Clarifications:
+
{| class="wikitable"
 
+
! scope="col" width="310" style="text-align: center; font-weight: bold;" | Community
* Data & doc projects would of course need an appropriate data or documentation license
+
! scope="col" width="310" style="text-align: center; font-weight: bold;" | Project
* When accepting external contributions care needs to be taken to keep your code base clear of encumbrances
+
|-
 
+
| [[File:OSGeo community.png|frameless|OSGeo Community Project]]
==Becoming a OSGeo Technology Project==
+
| [[File:OSGeo project.png|frameless|OSGeo Project]]
The goal is to keep the submission process for OSGeo Technology Project as simple and painless as possible. (The OSGeo Incubation Process is hard enough.) To submit your software project for inclusion in OSGeo Technology Project, simply send a description of the project to the [http://lists.osgeo.org/mailman/listinfo/incubator OSGeo Incubation Committee Mailing List], or [mailto:sunburned.surveyor@gmail.com e-mail Landon Blake.]
+
|}
 
+
==OSGeo Technology Project Set-Up Process==
+
Once a project has been accepted into OSGeo Technology Project, the OSGeo Technology Project volunteers will help the projects take these steps:
+
# Selection of an open source license if the project hasn't already done so.
+
# Creation a home page for the project. The OSGeo wiki is recommended for this page.
+
# Announce and discuss the project on the [http://lists.osgeo.org/mailman/listinfo/discuss OSGeo Discuss] email list.
+
# Set the project software development up on the OSGeo infrastructure if appropriate. (Sourceforge or other software development hosting sites can be used as an alternative.)
+
 
+
== OSGeo Technology Project Status Conditions ==
+
 
+
We’ve designed an informal “status” system to assist programmers and users evaluate projects in OSGeo Labs. Each project in labs is assigned one (1) of five (5) status conditions. The following factors are used to determine the status condition of the projects:
+
 
+
1) Source Code Completeness
+
2) Source Code Stability
+
3) Community Support (Mailing Lists, Documentation, Tutorials)
+
4) Project Deliverables (Programming Libraries and/or Executables)
+
5) Project Infrastructure (Source Code Versioning, Bug Trackers, Feature Trackers, Web Site, Mailing Lists, Discussion Forums)
+
6) Project Governance (Decision Making Processes, Licensing, Copyright Assignment, Release Schedule, Coding Standards)
+
7) Community Activity
+
8) Marketing and Outreach
+
 
+
Below are the different status conditions that can be assigned to a project in OSGeo Technology Project.
+
 
+
* '''Seed''': This project is in the conceptual stage. There may be some source code written, but it is incomplete or very experiemental. The project may lack deliverables, community support, project infrastructure, project governance, community activity, or marketing and outreach.
+
  
* '''Seedling''': This project is moving beyond the conceptual stage with some concrete code. However the code is still experimental and isn't stable. Projects at this status level could still experience a lot of change in their code base. This project should start to have some project infrastructure and some basic documentation.
+
== Community Projects ==
  
* '''Sapling''': This project has functional source code, although it may not be "mature and feature rich". For example, the code may only be usable as a programming library or a command line tool instead of featuring a GUI. The project has started to support users and programmers with communication tools, trackers, and documentation. The project has started to think about project governance and marketing, perhaps creating plans in these areas that are not fully implemented.
+
For a complete list please see the osgeo website: menu > projects > community projects.
  
* '''Adult''': This project has a usable and user friendly deliverable, like an executable program or a stable and well-deocumented programming library.  The project is supporting users and programmers with communication tools, trackers, and documentation. It has started the initial phases of incubation. This includes addressing issues of copyright, licensing, and project governance. The project also has a marketing and community growth plan and has started to implement the plan.
+
The following projects were added to the OSGeo Community program from the earlier [[Category:OSGeo Labs|osgeo labs]] program:
  
== Member Projects ==
+
* [[Geoinformatica]]
* [[OSGeo Technology Project: Geoinformatica]]
+
* [[GeoWebCache]]
* [[OSGeo Technology Project: pgRouting]]
+
* [[MapProxy]]
* [[OSGeo Technology Project: PAGC]]
+
* [[pgRouting]]
* [[OSGeo Technology Project: MapProxy]]
+
* [http://portablegis.xyz Portable GIS]
* [[OSGeo Technology Project: pycsw]]
+
* [[Postal Address Geo-Coder]]
* [[OSGeo Technology Project: Virtual Terrain Project]]
+
* [[Proj4php]]
* [[OSGeo Technology Project: PyWPS]]
+
* [https://github.com/ahhz/raster Pronto Raster]
* [[OSGeo Technology Project: OSGeo Certification]]
+
* [[Virtual Terrain Project]]
 +
* [https://github.com/AstunTechnology/Loader Loader]
  
== Archive ==
+
The following projects have now graduated from incubation:
 +
* [[pycsw]]
  
 
There is an archive of the old OSGeo Technology Projects page at [[OSGeo Labs Page Archive]].
 
There is an archive of the old OSGeo Technology Projects page at [[OSGeo Labs Page Archive]].

Latest revision as of 21:08, 16 October 2019

This wiki page is a scratchpad of ideas forming the osgeo community program. To see how these ideas have been realized please see our website page.

Purpose

The purpose of *OSGeo Community* projects is help foster innovation and include more project teams in the Open Source Geospatial Foundation.

OSGeo support for project teams

If you would like your software project to listed on the website, or apply to become an OSGeo community project, please send a description of your project to the OSGeo Incubation Committee Mailing List. We look forward to helping you!

About OSGeo Website Project List

To be listed on the OSGeo website:

  1. Be geospatial
    • Confirm by checking README or project description
  2. Have a free license or open source license
    • The license must be OSI approved
  3. 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.

About OSGeo Community Projects

In addition to being listed on the website, projects applying to the *OSGeo Community* program are asked to:

  1. 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
  2. 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
  3. 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 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.

OSGeo provides code of conduct guidance, many projects selecting contribution covenant).

About OSGeo Projects

To be recognized as an *OSGeo Project* we ask that project teams excel in each of areas mentioned above, see graduation checklist for more detail.

The *OSGeo Project* designation is intended to recognize established projects with a diverse community 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.

Comparison

As shown below there is some overlap requirements for an OSGeo projects (as defined by the incubation process graduation checklist).

Responsibility Website Listing OSGeo Community OSGeo Project
Geospatial

- README or project description

X X X
Geospatial

- User guide or quickstart

X X
Free or Open Source License

- See LICENSE.md

X X X
Free or Open Source License

- Check headers

X X
Free or Open Source License

- Providence Review

X
Participatory

- See CONTRIBUTING.md

X X X
Participatory

- History of pull requests or patches

X X
Participatory

- Code of conduct

X X
Open Community

- communication channel
- decision making process

X
Active Healthy Community

- user and developer collaboration
- long term viability

X
Development Process

- version control
- issue tracker
- leadership open to new members
- transparent decision making

X
Documentation

- user documentation
- developer documentation

X
Release Procedure

- release process
- documented testing process

X
Foundation Resources Website Listing OSGeo Community OSGeo Project
website project list X X X
website choose-a-project X X X
OSGeo Live X X X
Marketing Collateral X X
Representation project officer
infrastructure and facilities X X
promotion & marketing X X
budget osgeo board project budget
fundraising X X

Activities with the OSGeoLive project or Marketing committee can be pursed at any time.

The incubation process establishes a project as a full fledged OSGeo committee, with a project project officer, with direct access to OSGeo treasurer, and reporting to the board during annual general meeting. While Community projects are not recognized as a committee, the OSGeo board maintains an "OSGeo Community" initiative with budget to support your activities. Attend one of the OSGeo board monthly meetings, or ask on the board mailing list, if your project has an activity that can benefit from financial support. For more information see osgeo_financial_guidence.pdf

Available branding:

Community Project
OSGeo Community Project OSGeo Project

Community Projects

For a complete list please see the osgeo website: menu > projects > community projects.

The following projects were added to the OSGeo Community program from the earlier program:

The following projects have now graduated from incubation:

There is an archive of the old OSGeo Technology Projects page at OSGeo Labs Page Archive.