aside: While having a code of conduct is important, many teams did not want to put in the effort to define and maintain their own, in true open source fashion a couple shared documents have been produced by the wider open source community.
Enacting one of these for your repository does require some though with respect to a contact person. I would recommend the project’s osgeo officer as they already have a formal relationship with the foundation.
aside: While having a code of conduct is important, many teams did not want to put in the effort to define and maintain their own, in true open source fashion a couple shared documents have been produced by the wider open source community.
Enacting one of these for your repository does require some though with respect to a contact person. I would recommend the project’s osgeo officer as they already have a formal relationship with the foundation.
There is a button in the github user interface to make the default CODE_OF_CONDUCT.md.
This is a case where a PSC member needs to act (I cannot do it for you). Please do so before the September 10th OSGeo AGM meeting (or it would be one of the things the board would bring up).
There is a button in the github user interface to make the default CODE_OF_CONDUCT.md.
This is a case where a PSC member needs to act (I cannot do it for you). Please do so before the September 10th OSGeo AGM meeting (or it would be one of the things the board would bring up).
aside: While having a code of conduct is important, many teams did not want to put in the effort to define and maintain their own, in true open source fashion a couple shared documents have been produced by the wider open source community.
Enacting one of these for your repository does require some though with respect to a contact person. I would recommend the project’s osgeo officer as they already have a formal relationship with the foundation.
There is a button in the github user interface to make the default CODE_OF_CONDUCT.md.
This is a case where a PSC member needs to act (I cannot do it for you). Please do so before the September 10th OSGeo AGM meeting (or it would be one of the things the board would bring up).
aside: While having a code of conduct is important, many teams did not want to put in the effort to define and maintain their own, in true open source fashion a couple shared documents have been produced by the wider open source community.
Enacting one of these for your repository does require some though with respect to a contact person. I would recommend the project’s osgeo officer as they already have a formal relationship with the foundation.