Skip to content
This repository has been archived by the owner on Feb 24, 2021. It is now read-only.

Can we add a CODE_OF_CONDUCT.md to a repository #337

Closed
johlju opened this issue Dec 7, 2017 · 11 comments
Closed

Can we add a CODE_OF_CONDUCT.md to a repository #337

johlju opened this issue Dec 7, 2017 · 11 comments

Comments

@johlju
Copy link
Contributor

johlju commented Dec 7, 2017

To use the recommended community standards a CODE_OF_CONDUCT.md file should be present in the root of the repository. See https://github.com/PowerShell/DscResources/community.

I suggest we add a CODE_OF_CONDUCT.md with the same information as in the README.md. But is it okay to remove the code of conduct information from the README.md in favor of the CODE_OF_CONDUCT.md? Or, in the README.md point to the CODE_OF_CONDUCT.md?

Update: Change the link to point to this repository community page.

@johlju
Copy link
Contributor Author

johlju commented Dec 7, 2017

@zjalexander could you please look into this?

@zjalexander
Copy link
Contributor

heads up, i do have to coordinate this with the microsoft oss team. they want us to be "consistent" "across repos" for some reason :) not sure if this is already part of their guidance or not, so a bit of investigation is needed on my end

@johlju
Copy link
Contributor Author

johlju commented Dec 7, 2017

@zjalexander Absolutely I guessed as much. But thought it would be more of a legal issue. 😄 But I will await your answer. :)

@johlju
Copy link
Contributor Author

johlju commented Jan 6, 2018

@zjalexander Did you have a chance to contact the Microsoft OSS team before the holidays?

@johlju
Copy link
Contributor Author

johlju commented Mar 17, 2018

@zjalexander any updates on this? Not sure you are working on Dsc Resource Kit any longer. If not, then maybe @kwirkykat can see if the above is "allowed" by the OSS Team?

@zjalexander
Copy link
Contributor

@mgreenegit is the contact for the resource kit now, thanks for your patience on this issue

@johlju johlju added the discussion The issue is a discussion. label Apr 20, 2018
@stale
Copy link

stale bot commented Jun 8, 2018

This issue has been automatically marked as needs more information because it has not had activity from the community in the last 30 days. It will be closed if no further activity occurs within 10 days. If the issue is labelled with any of the work labels (e.g bug, enhancement, documentation, or tests) then the issue will not auto-close.

@stale stale bot added the needs more information The issue needs more information from the author or the community. label Jun 8, 2018
@johlju
Copy link
Contributor Author

johlju commented Jun 8, 2018

See PR dsccommunity/SqlServerDsc#940 - that proposes to move the Code of conduct from the README.md to a separate file CODE_OF_CONDUCT.md - this is to use the "GitHub standard" by adding a file for code of coduct. That resolves the check here; https://github.com/PowerShell/DscResources/community

I'm okay by both, keeping it in the README.md or moving it out to a separate file - but above Zachary lifted the question that maybe the Open Source team want to keep this information consistent across all repos. I will lift the question to the Open Source team.

@stale stale bot removed the needs more information The issue needs more information from the author or the community. label Jun 8, 2018
@johlju
Copy link
Contributor Author

johlju commented Jun 8, 2018

I talked to MS Open Source Team and they provided this link; https://opensource.microsoft.com/codeofconduct/faq/#howadopt. They also said they aren't enforcing a specific location of the text, and if we want the check mark to be green we could "improvise" (my word, not theirs).

So I propose this, to be compliant with the previous link, and also get the green check mark I suggest we replace the text in the README.md with something like This project has adopted [this code of conduct](\CODE_OF_CONDUCT.md)..

Also suggest that this is up to the maintainers to decide if they want to do. We don't add a guideline for this.

I leave this open and let Stale auto-close this one if there are not more comments.

@PlagueHO
Copy link
Contributor

PlagueHO commented Jun 8, 2018

I think I'll look at adding this to the repos I maintain. It is fine with me if this isn't an enforced guideline.

@johlju
Copy link
Contributor Author

johlju commented Jul 4, 2018

Closing this issue at this time.

@johlju johlju closed this as completed Jul 4, 2018
@johlju johlju removed the discussion The issue is a discussion. label Jul 4, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants