[Pulp-dev] Fwd: Community Standards

Dana Walker dawalker at redhat.com
Fri Sep 21 16:19:29 UTC 2018

Yeah, agreed, not sure it's worth the effort and not sure that would even
work depending on exactly what markers they're looking for like in their
own templates.  Not sure how many community members would check the
Insights tab before looking at our actual repo or website and get the wrong
idea.  I'm guessing not enough right now, and if we get feedback otherwise,
we can duplicate the text.


Dana Walker

Associate Software Engineer

Red Hat


On Fri, Sep 21, 2018 at 12:15 PM, David Davis <daviddavis at redhat.com> wrote:

> Thanks for reaching out to Github. I noticed this issue too. I wonder if
> copying our Code of Conduct to CODE_OF_CONDUCT.md would fix the problem.
> I’m not sure what sort of check they’re using but I guess we can try it and
> find out. Personally though, I am not sure what the tool detecting our code
> of conduct buys us so I’m leaning towards option A.
> David
> On Fri, Sep 21, 2018 at 12:06 PM Dana Walker <dawalker at redhat.com> wrote:
>> Are we ok with GitHub's automation not detecting our Code of Conduct?
>> See forwarded message below.  I am, especially since it's a known issue
>> they have a ticket open to improve, but wanted to ask the rest of you.
>> Options:
>> A) Leave as is, so we only have to maintain it in one place (our website)
>> and link to it from our CODE_OF_CONDUCT.md file even though GitHub doesn't
>> detect this.
>> B) Duplicate the text into the CODE_OF_CONDUCT.md file to get detected
>> properly by Community Standards automation in GitHub.
>> --Dana
>> Dana Walker
>> Associate Software Engineer
>> Red Hat
>> <https://www.redhat.com>
>> <https://red.ht/sig>
>> ---------- Forwarded message ----------
>> From: GitHub Staff <support at github.com>
>> Date: Fri, Sep 21, 2018 at 12:00 AM
>> Subject: Re: Community Standards
>> To: Dana Walker <dawalker at redhat.com>
>> Hey Dana,
>> Thanks for reaching out to GitHub Support!
>> Currently, the tool will only check specifically for code of conduct
>> files that we recognize, not just the existence of a CODE_OF_CONDUCT.md.
>> This was an intentional choice made to avoid giving folks a checkmark if
>> they've got a file full of content that is not actually a code of conduct.
>> That said, we do have an issue open about improving this behavior & I've
>> added your report there.
>> In the meantime, if you'd like your code of conduct recognized, you could
>> switch to one of the ones we provide via our code of conduct tool:
>> https://help.github.com/articles/adding-a-code-of-
>> conduct-to-your-project/#adding-a-code-of-conduct-using-a-template
>> That would guarantee you're using a specific code that we recognize. I
>> hope this helps, and just let us know if you have any other questions!
>> Best regards,
>> Tiara
>> GitHub Support
>> 👉Find support and come learn with other GitHub users in our new GitHub
>> Community Forum
>> <https://github.community/?utm_source=halp&utm_medium=email>.
>> Hi,
>> We've been trying to get the Pulp Project up to community standards,
>> adding a Code of Conduct, a pull request template, contributing guide, etc.
>> It still says we have no Code of Conduct even though the CODE_OF_CONDUCT.md
>> file is in the main directory with the README and everything else that it
>> is detecting. (See https://github.com/pulp/pulp and
>> https://github.com/pulp/pulp/community) I was wondering if it's because
>> we are linking externally to our site? We are trying to have only one place
>> to maintain the file, but we do want to be compliant so that we are
>> welcoming to new members of the community. Please let us know if the
>> automated check just misses this kind of link out or if we have to do
>> something else.
>> Thanks!
>> _______________________________________________
>> Pulp-dev mailing list
>> Pulp-dev at redhat.com
>> https://www.redhat.com/mailman/listinfo/pulp-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20180921/45b63f22/attachment.htm>

More information about the Pulp-dev mailing list