Opened 4 years ago
Closed 18 months ago
#2531 closed enhancement (fixed)
Code of conduct
Reported by: | jgrocha | Owned by: | cvvergara |
---|---|---|---|
Priority: | normal | Milestone: | Sysadmin Contract 2023-II |
Component: | Board | Keywords: | |
Cc: |
Description
Hi,
We have:
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
Change History (8)
comment:1 by , 4 years ago
comment:4 by , 4 years ago
Valid email: conduct-report@… The other one we want to remove it as the pronunciation in Spanish in English ears is not nice
comment:5 by , 4 years ago
Owner: | changed from | to
---|
comment:6 by , 4 years ago
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.
comment:7 by , 4 years ago
I have updated both pages, clearly indicating that the osgeo code of conduct version 1.0 is no longer maintained.
comment:8 by , 18 months ago
Milestone: | Unplanned → Sysadmin Contract 2023-II |
---|---|
Resolution: | → fixed |
Status: | new → closed |
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
The first page points to coc@… and the second one to conduct-report@… for reporting issues . Are both valid aliases ?