+1 to these changes. Thank you for proposing/coordinating them. We track website issues here [0], and I made an issue to add the /conduct/ page to pulpproject.org here [1]. Historically we don't put website issues through sprint planning. I can review/test the changes if that is helpful.
As an aside, if the language of PUP-4 needs updating, a diff can be approved via lazy consensus (I think). [0]: https://github.com/pulp/pulpproject.org/issues/ [1]: https://github.com/pulp/pulpproject.org/issues/134 -Brian On Fri, Jun 22, 2018 at 4:58 PM, David Davis <[email protected]> wrote: > Thanks for starting this discussion. Personally, I think the best place > for our Code of Conduct is on our website. To use another project as an > example, Django’s CoC is easily accessible on their website: > > https://www.djangoproject.com/conduct/ > > <https://www.djangoproject.com/conduct/>I feel like our Code of Conduct > shouldn’t live on Github as it applies to all members of our community—not > just developers (and Github is developer-centric). > > So +1 to putting our CoC on our website and linking to it from > a CODE_OF_CONDUCT.md file. > > David > > > On Fri, Jun 22, 2018 at 4:37 PM Dana Walker <[email protected]> wrote: > >> PUP-4 proposed Pulp adopt a Code of Conduct as we previously had none. >> This proposal was accepted in December 2017. At the time, it was decided >> to link to the PUP itself in CONTRIBUTING.md. [0] >> >> In creating that file today for another issue [1], it became apparent >> that linking to the PUP means linking to a document that has several >> paragraphs of "should we do this" unfinished sounding language from the >> proposal before we get to the actionable code we want a community member to >> read. >> >> I propose that, as we did for the CCRC in PUP-5, we actually house the >> Code of Conduct itself on 1) our website, and link to it from a >> CODE_OF_CONDUCT.md file in our base directory, or 2) house the document in >> a CODE_OF_CONDUCT.md file directly. >> >> This would bring us in line with the GitHub Community Standards. [1][2] >> >> Please respond with comments, questions, or preferences regarding this >> proposed update. >> >> In absence of any -1's we will be moving forward with one of the two >> proposed changes to the display location no later than Monday July 9. >> >> [0] https://github.com/pulp/pups/blob/master/pup-0004.md >> [1] https://pulp.plan.io/issues/3599 >> [2] https://github.com/pulp/pulp/community >> >> Thanks, >> >> --Dana >> >> >> Dana Walker >> >> Associate Software Engineer >> >> Red Hat >> >> <https://www.redhat.com> >> <https://red.ht/sig> >> _______________________________________________ >> 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
