#2531: Code of conduct
-------------------------+-----------------------
Reporter: jgrocha | Owner: warmerdam
Type: enhancement | Status: new
Priority: normal | Milestone: Unplanned
Component: Board | Keywords:
-------------------------+-----------------------
Hi,
We have:
* https://www.osgeo.org/resources/osgeo-code-of-conduct/
* https://www.osgeo.org/code_of_conduct/
Can this be reduced to just one?
This duplication was raised on GDAL's mailing list
https://lists.osgeo.org/pipermail/gdal-dev/2020-November/thread.html#53055
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2531>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2531: Code of conduct
-------------------------+------------------------
Reporter: jgrocha | Owner: warmerdam
Type: enhancement | Status: new
Priority: normal | Milestone: Unplanned
Component: Board | Resolution:
Keywords: |
-------------------------+------------------------
Comment (by rouault):
The first page points to coc@osgeo.org and the second one to conduct-
report@osgeo.org for reporting issues . Are both valid aliases ?
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2531#comment:1>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2531: Code of conduct
-------------------------+------------------------
Reporter: jgrocha | Owner: warmerdam
Type: enhancement | Status: new
Priority: normal | Milestone: Unplanned
Component: Board | Resolution:
Keywords: |
-------------------------+------------------------
Comment (by cvvergara):
Will Check with Code of Conduct
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2531#comment:2>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2531: Code of conduct
-------------------------+------------------------
Reporter: jgrocha | Owner: warmerdam
Type: enhancement | Status: new
Priority: normal | Milestone: Unplanned
Component: Board | Resolution:
Keywords: |
-------------------------+------------------------
Comment (by cvvergara):
https://lists.osgeo.org/pipermail/coc-discuss/2020-November/000073.html
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2531#comment:3>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2531: Code of conduct
-------------------------+------------------------
Reporter: jgrocha | Owner: warmerdam
Type: enhancement | Status: new
Priority: normal | Milestone: Unplanned
Component: Board | Resolution:
Keywords: |
-------------------------+------------------------
Comment (by cvvergara):
Valid email:
conduct-report@osgeo.org
The other one we want to remove it as the pronunciation in Spanish in
English ears is not nice
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2531#comment:4>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2531: Code of conduct
-------------------------+------------------------
Reporter: jgrocha | Owner: cvvergara
Type: enhancement | Status: new
Priority: normal | Milestone: Unplanned
Component: Board | Resolution:
Keywords: |
-------------------------+------------------------
Changes (by robe):
* owner: warmerdam => cvvergara
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2531#comment:5>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2531: Code of conduct
-------------------------+------------------------
Reporter: jgrocha | Owner: cvvergara
Type: enhancement | Status: new
Priority: normal | Milestone: Unplanned
Component: Board | Resolution:
Keywords: |
-------------------------+------------------------
Comment (by jive):
I think I can explain, the website
(https://www.osgeo.org/code_of_conduct/) has a statement where we indicate
all our projects, committees and events have a code of conduct. This is
similar to stating that all our open source projects are distributed using
an open source license.
We do not tell projects, committees, or events which code of conduct to
select (just like we do not demand a specific open source license). We are
an outreach organization and part of the fun is encouraging each group to
discuss their priorities and make a decision.
We have two live documents that we recommend (as may parties do not want
to maintain a code-of-conduct on their own)
1) https://berlincodeofconduct.org/ is an example of a code of conduct
put together for an event or online community
2)
https://www.contributor-covenant.org/ is an example of a code of conduct
used by open source projec
OSGeo also have a static document, our prior code of conduct
(https://www.osgeo.org/resources/osgeo-code-of-conduct/) which we do not
recommend as it is not maintained. It needs to remain published, it is a
versioned document which is still in active use.
To make this easier we could moe the static version 1.0 document to the
examples section at the end of the page.
I will do so now.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2531#comment:6>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2531: Code of conduct
-------------------------+------------------------
Reporter: jgrocha | Owner: cvvergara
Type: enhancement | Status: new
Priority: normal | Milestone: Unplanned
Component: Board | Resolution:
Keywords: |
-------------------------+------------------------
Comment (by jive):
I have updated both pages, clearly indicating that the osgeo code of
conduct version 1.0 is no longer maintained.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2531#comment:7>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2531: Code of conduct
-------------------------+----------------------------------------
Reporter: jgrocha | Owner: cvvergara
Type: enhancement | Status: closed
Priority: normal | Milestone: Sysadmin Contract 2023-II
Component: Board | Resolution: fixed
Keywords: |
-------------------------+----------------------------------------
Changes (by cvvergara):
* status: new => closed
* resolution: => fixed
* milestone: Unplanned => Sysadmin Contract 2023-II
Comment:
The GDAL team's decision:
https://lists.osgeo.org/pipermail/gdal-dev/2020-November/053062.html
The change by jive where is "no longer maintained" shows.
Closing
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2531#comment:8>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.