[Incubator] cleaning up "osgeo community" page

[Jody Garnett]

For discussion: I like having only 3 aspects of a project to consider and
would like to figure out...

a) Making the website a requirement for "OSGeo community" project
application is sensible as we need the page created before we can announce.
- RECOMMEND add this under "be geospatial" as it is focused on community
outreach ...

b) Where does "Code of conduct" best fit?
- RECOMMEND: "Welcome participation and new contributors" as this is inward
facing about the running of the projects community in a fair/welcoming
fashion
- DISCUSSION: "Be geospatial" it could also fit here as it is a requirement
from OSGeo....

Any suggestionion/agree/discussion/dissagree please reply...
--
Jody Garnett


On Mon, 23 Sep 2019 at 20:41, Jody Garnett <jody.garnett at gmail.com> wrote:

> After the code sprint (and many questions at foss4g) the following page is
> updated to better describe what we are doing with the program.
>
> https://wiki.osgeo.org/wiki/OSGeo_Community_Projects
>
> The page had been complicated over time with a lot of draft idea,
> discussion of mutations, and descriptions of prior attend (to set up a
> "osgeo labs" area for new projects).
>
> Of particular importance is the table of requirements to be listed on the
> website, join the osgeo community program, or be recognized as an osgeo
> project.
>
> CRITIAL - the list of what we expect of applicants has has expanded to
> include "code of conduct". I have also done a better job explaining that we
> ask a little more in each category (be geospatial, check headers,
> demonstrate collaboration)...
>
> *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*
>       - *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*
>    4. *Code of Conduct*
>       - *OSGeo has supplied some guidance for projects
>       <https://www.osgeo.org/code_of_conduct/>many of which select contribution
>       covenant <https://www.contributor-covenant.org/>*
>
>
> aside: If you are describing what we offer project teams I encourage the
> use of incubation page
> <https://www.osgeo.org/about/committees/incubation/> on the website.
> --
> Jody Garnett
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/incubator/attachments/20190929/e98a2ee0/attachment.html>