Difference between revisions of "OSGeo Community Projects"

From OSGeo

Revision as of 14:57, 10 September 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.

Member Project History

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.

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 Project List

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

About OSGeo Community Projects

We ask that *OSGeo Community* projects go further:

Be geospatial
- Confirm by checking README or project description
- 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
Code of Conduct
- OSGeo has supplied some guidance for projects many of which select contribution covenant

To be recognized as an *OSGeo Project* we ask that project teams excel in each of these three aspects, see the graduation checklist for more detail.

How OSGeo Community Projects Are Related To OSGeo Incubation

There are two ways for an open source software project to join OSGeo. The first way is through the regular incubation process. This is best for projects that already have an established community of developers and users. (This community should be diverse. This means that developers should come from more than one organization or group.)

If a project doesn't yet have an active and diverse community, it can join OSGeo as an OSGeo Community Project. OSGeo Community Projects get help from the incubation committee with things like choosing an open source license, setting up project governance, promoting the project, and building the project community).

The same volunteers that help software projects through the OSGeo Incubation Process also help OSGeo Community Projects.

Purpose

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

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 Projects	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	Technology	Project
Representation			project officer
infrastructure and facilities		X	X
promotion & marketing		X	X
budget		osgeo board	project budget
fundraising		X	X

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

Community Projects

The following projects are listed with the community projects:

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

Retrieved from "http://wiki.osgeo.org/w/index.php?title=OSGeo_Community_Projects&oldid=121748"

Category:

OSGeo Labs

@@ Line 1: / Line 1: @@
 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].
-== Community Projects ==
-The following projects are listed with the community projects [[Category:OSGeo Labs|program]]:
-* [[Geoinformatica]]
-* [[GeoWebCache]]
-* [[MapProxy]]
-* [[pgRouting]]
-* [http://portablegis.xyz Portable GIS]
-* [[Postal Address Geo-Coder]]
-* [[Proj4php]]
-* [https://github.com/ahhz/raster Pronto Raster]
-* [[Virtual Terrain Project]]
-* [https://github.com/AstunTechnology/Loader Loader]
-For a complete list please see the osgeo website: menu > projects > community projects.
 ==Member Project History==
@@ Line 25: / Line 8: @@
 There is an archive of the old OSGeo Technology Projects page at [[OSGeo Labs Page Archive]].
-== About OSGeo Community Projects==
+= 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 [http://lists.osgeo.org/mailman/listinfo/incubator OSGeo Incubation Committee Mailing List]. We look forward to helping you!
+== About OSGeo Project List ==
 To be listed on the OSGeo website:
@@ Line 35: / Line 22: @@
 # Welcome participation and new contributors.
 #* We look for a clear contribution policy
+== About OSGeo Community Projects==
 We ask that *OSGeo Community* projects go further:
@@ Line 53: / Line 42: @@
 ==How OSGeo Community Projects Are Related To OSGeo Incubation==
 There are two ways for an open source software project to join OSGeo. The first way is through the regular incubation process. This is best for projects that already have an established community of developers and users. (This community should be diverse. This means that developers should come from more than one organization or group.)
@@ Line 61: / Line 51: @@
 == Purpose ==
-The purpose of OSGeo Community Projects is to provide a home at OSGeo for projects that don't qualify for our normal incubation process. This allows them to get help from the volunteers on the OSGeo Incubation Committee and to become familiar with the guidelines and operation of OSGeo as an organization. Most OSGeo Community Projects are working to qualify for the normal incubation process, but this isn't a requirement.
+The purpose of *OSGeo Community* projects is help foster innovation and include more project teams in the Open Source Geospatial Foundation.
-The normal OSGeo incubation process requires that software projects meet a high standard for things like project governance. Working through the normal incubation process can involve a lot of work. in contrast, we want the process to become and OSGeo Community Project to be as painless as possible. That allows projects to build community strength before they enter incubation.
-==Qualifying As An OSGeo Community Project==
-We would like to make joining OSGeo as an OSGeo Community Project as simple and painless as possible. If you would like your software project 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].
-Your software project needs to meet the following criteria to be an OSGeo Community Project:
-# The technology in your software project should be geospatial (or directly support geospatial applications).
-# Your project should be open source and welcomes new contributions. If you don't have a license selected, we can help with that.
+=== Comparison ===
-=== Comparison with Incubation and OSGeo website ===
 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).
@@ Line 217: / Line 195: @@
 |}
-==Getting Started==
+== Community Projects ==
-Once your software project has been accepted as an OSGeo Community Project, the Incubation Committee will assign you personal mentor. This mentor will help your project withcommunity building and other tasks. First steps for an OSGeo Community Project include:
-# Creation a home page for the project. The OSGeo wiki is recommended for this page.
+The following projects are listed with the community projects [[Category:OSGeo Labs|program]]:
-# Selection of an open source license (if the project hasn't already done this).
-# Announcement and discussion of the project on the [http://lists.osgeo.org/mailman/listinfo/discuss OSGeo Discuss] OSGeo Discussion mailing list.
-# Set-up of project infrastructure (mailing list, source code repository, doc repository).
-# Creation of plans for software development, marketing and documentation.
-== Volunteers Needed ==
+* [[Geoinformatica]]
-Please let us know on the [https://lists.osgeo.org/mailman/listinfo/incubator Incubation Committee Mailing List] if you would like to help with OSGeo Community Projects. Here is the type of help we need:
+* [[GeoWebCache]]
-* Project marketing.
+* [[MapProxy]]
-* Development of user and programmer communities.
+* [[pgRouting]]
-* Establishment of programs and policies for project documentation, copyright assignment, and licensing.
+* [http://portablegis.xyz Portable GIS]
-* 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.
+* [[Postal Address Geo-Coder]]
-* Establishment of project governance programs and policies.
+* [[Proj4php]]
-* Collaboration on technical standards, data formats, and code sharing with other open source geospatial software projects.
+* [https://github.com/ahhz/raster Pronto Raster]
-* Utilization of software development infrastructure like mailing lists, bug trackers, version control software/hosting, and web hosting.
+* [[Virtual Terrain Project]]
+* [https://github.com/AstunTechnology/Loader Loader]
-== OSGeo Community Projects Checklist ==
+For a complete list please see the osgeo website: menu > projects > community projects.
-This will be coming soon!
-== OSGeo Community Project Stages==
-OSGeo Comminity Projects are assigned a "stage" that helps interested developers and users understand their maturity. Here are the different stages, in a profession from least mature to most mature:
-* '''Research Project''': 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.
-* '''New Project''': 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.
-* '''Stable Project''': 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.
-* '''Established Project''': 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.
-==Available Branding==
-Once they are approved by the Incubation Committee, OSGeo Community Projects can use the following logo:
-https://wiki.osgeo.org/wiki/File:OSGeo_community.png