<div dir="ltr"><div>+1 to these changes. Thank you for proposing/coordinating them.<br></div><div><br></div><div>We track website issues here [0], and I made an issue to add the /conduct/ page to <a href="http://pulpproject.org">pulpproject.org</a> here [1]. Historically we don't put website issues through sprint planning. I can review/test the changes if that is helpful.<br></div><div><br></div><div>As an aside, if the language of PUP-4 needs updating, a diff can be approved via lazy consensus (I think).<br></div><div><br></div><div>[0]: <a href="https://github.com/pulp/pulpproject.org/issues/">https://github.com/pulp/pulpproject.org/issues/</a></div><div>[1]: <a href="https://github.com/pulp/pulpproject.org/issues/134">https://github.com/pulp/pulpproject.org/issues/134</a></div><div><br></div><div>-Brian</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jun 22, 2018 at 4:58 PM, David Davis <span dir="ltr"><<a href="mailto:daviddavis@redhat.com" target="_blank">daviddavis@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">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:<div><br></div><div><a href="https://www.djangoproject.com/conduct/" target="_blank">https://www.djangoproject.com/<wbr>conduct/</a></div><div><br></div><div><a href="https://www.djangoproject.com/conduct/" target="_blank"></a>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).</div><div><br></div><div>So +1 to putting our CoC on our website and linking to it from a CODE_OF_CONDUCT.md file.<br clear="all"><div><div dir="ltr" class="m_-3275819450949958088gmail-m_-3962094087048074375gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><br></div><div>David<br></div></div></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div><div class="h5"><div dir="ltr">On Fri, Jun 22, 2018 at 4:37 PM Dana Walker <<a href="mailto:dawalker@redhat.com" target="_blank">dawalker@redhat.com</a>> wrote:<br></div></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div>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]<br></div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>This would bring us in line with the GitHub Community Standards. [1][2]</div><div><br></div><div>Please respond with comments, questions, or preferences regarding this proposed update.</div><div><br></div><div>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.</div><div> <br></div><div>[0] <a href="https://github.com/pulp/pups/blob/master/pup-0004.md" target="_blank">https://github.com/pulp/pups/<wbr>blob/master/pup-0004.md</a><br></div><div>[1] <a href="https://pulp.plan.io/issues/3599" target="_blank">https://pulp.plan.io/issues/<wbr>3599</a><br></div><div>[2] <a href="https://github.com/pulp/pulp/community" target="_blank">https://github.com/pulp/pulp/<wbr>community</a><br></div><div><br></div><div>Thanks,</div><div><br></div><div>--Dana<br></div><div><br></div><div><br></div><div><div class="m_-3275819450949958088m_-3962094087048074375m_2345971389333342911gmail_signature"><div dir="ltr"><div>
<p style="font-weight:bold;margin:0px;padding:0px;font-size:14px;text-transform:uppercase"><span>Dana</span> <span>Walker</span></p>
<p style="font-weight:normal;font-size:10px;margin:0px 0px 4px;text-transform:uppercase"><span>Associate Software Engineer</span><span style="font-weight:normal;color:rgb(170,170,170);margin:0px"></span></p>
<p style="font-weight:normal;margin:0px;font-size:10px;color:rgb(153,153,153)"><a style="color:rgb(0,136,206);font-size:10px;margin:0px;text-decoration:none;font-family:"overpass",sans-serif" href="https://www.redhat.com" target="_blank">Red Hat <span><br><br></span></a></p>
<table border="0"><tbody><tr><td width="100px"><a href="https://red.ht/sig" target="_blank"> <img src="https://www.redhat.com/files/brand/email/sig-redhat.png" width="90" height="auto"></a> </td>
</tr></tbody></table>
</div></div></div></div>
</div></div></div>
______________________________<wbr>_________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/pulp-dev</a><br>
</blockquote></div>
<br>______________________________<wbr>_________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/pulp-dev</a><br>
<br></blockquote></div><br></div>