+1 initial motion Aside: The only "creativity" the boilerplate asks is how we "enforce":
*Before adopting the Contributor Covenant take the time to discuss and decide how to deal with problems as they emerge. Document the policy and procedure for enforcement, and add it to your README or in another visible, appropriate place. Consider if your project team has the willingness and maturity to follow through on your enforcement procedures.* One advantage of being an OSGeo project is our answer is easy, say by adding something like to our README. As part of the Open Source Geospatial Foundation commitment to projects being open an inclusive GeoTools has adopted the contributor convent, coordinating enforcement with OSGeo code-of-conduct committee. Or shorter: GeoTools has adopted the contributor covenant for community conduct. Enforcement is coordinated with the Open Source Geospatial code-of-conduct committee. -- Jody Garnett On Mon, 13 Jan 2020 at 11:22, Jody Garnett <jody.garn...@gmail.com> wrote: > Now that I am no longer a board member I am picking up a bit more as > project officer. Our budget request was sent out (have not heard how the > meting went). One thing we have not yet done for geotools is a code of > conduct for our repository / email list / etc... > > Motion: GeoTools adopt standard contributor covenant > <https://www.contributor-covenant.org/> for community interactions. > > The contributor covenant is easy to recommend, it is written for open > source projects (not events). It is well respected and we do not have to > maintain it. Indeed GitHub now has a shortcut to add it to a project just > like an open source licenses. > -- > Jody Garnett >
_______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
