I submitted the PR[0] for PUP 4. Please continue to provide feedback on the PR or on this thread.
[0] https://github.com/pulp/pups/pull/6 On Thu, Nov 30, 2017 at 1:06 PM, Daniel Alley <[email protected]> wrote: > +1 to option F > > On Wed, Nov 29, 2017 at 4:47 PM, Brian Bouterse <[email protected]> > wrote: > >> +1 to option F. It starts a CONTRIBUTING.md and also shows off the CoC on >> the website. We can easily make a CoC page on the website and link to that. >> >> For the email, we probably need to make a private mailing list like >> [email protected] and have 2-3 people subscribed as a start. Is there >> a better name? Who would want to subscribe to something like this? Overall >> I think the Django enforcement manual [7] is a decent manual to handle >> these types of things. I'm not suggesting we formally adopt it, just that >> it's pretty useful. >> >> [7]: https://www.djangoproject.com/conduct/enforcement-manual/ >> >> >> >> >> On Wed, Nov 29, 2017 at 4:06 PM, David Davis <[email protected]> >> wrote: >> >>> +1 to option F. >>> >>> I reviewed the code of conduct and it looks like a great starting point. >>> There’s a space for email address though ("[INSERT EMAIL ADDRESS]”) in the >>> CoC. >>> >>> >>> David >>> >>> On Mon, Nov 27, 2017 at 4:51 PM, Dennis Kliban <[email protected]> >>> wrote: >>> >>>> Pulp should adopt the Contributor Covenant Code of Conduct[0] as it's >>>> code of conduct. >>>> >>>> I have looked at other projects that have adopted this CoC and have >>>> discovered that we have a few options for how to publish the CoC. >>>> >>>> a) Add a CODE_OF_CONDUCT.md to root of repo and refer to it from >>>> pulpproject.org[1] >>>> >>>> b) Append the CoC to the contributing guide in CONTRIBUTING.md[2]. >>>> >>>> c) Add a CODE_OF_CONDUCT.md to root of repo and link to the Contributor >>>> Covenant site.[3] >>>> >>>> d) Add a CoC page to pulpproject.org and link to it from >>>> CODE_OF_CONDUCT.md[4] >>>> >>>> e) Include the CoC in the PUP. Add a CODE_OF_CONDUCT.md and link to the >>>> PUP on GitHub or an HTML version of the PUP on the website. >>>> >>>> f) Include the CoC in the PUP. Add a CoC section to CONTRIBUTING.md and >>>> link to the PUP on GitHub or an HTML version of the PUP on the website. >>>> >>>> >>>> I prefer option F, but if we do this work before we add >>>> CONTRIBUTING.md[5], I am ok with option E. >>>> >>>> >>>> We should adopt it verbatim. If anyone wants to adopt a modified >>>> version, please add your revisions here[6] and notify the list when your >>>> changes are ready to review. >>>> >>>> >>>> >>>> [0] https://www.contributor-covenant.org/version/1/4/code-of-con >>>> duct.html >>>> [1] https://github.com/rom-rb/rom/blob/master/CODE_OF_CONDUCT.md >>>> [2] https://github.com/gitlabhq/gitlabhq/blob/master/CONTRIBUTIN >>>> G.md#code-of-conduct >>>> [3] https://github.com/patternfly/patternfly/blob/master/CODE_OF >>>> _CONDUCT.md >>>> [4] https://github.com/rails/rails/blob/master/CODE_OF_CONDUCT.md >>>> [5] https://pulp.plan.io/issues/3150 >>>> [6] http://pad-theforeman.rhcloud.com/p/Pulp-CoC >>>> >>>> _______________________________________________ >>>> Pulp-dev mailing list >>>> [email protected] >>>> https://www.redhat.com/mailman/listinfo/pulp-dev >>>> >>>> >>> >>> _______________________________________________ >>> Pulp-dev mailing list >>> [email protected] >>> https://www.redhat.com/mailman/listinfo/pulp-dev >>> >>> >> >> _______________________________________________ >> Pulp-dev mailing list >> [email protected] >> https://www.redhat.com/mailman/listinfo/pulp-dev >> >> > > _______________________________________________ > Pulp-dev mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/pulp-dev > >
_______________________________________________ Pulp-dev mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-dev
