-
Notifications
You must be signed in to change notification settings - Fork 462
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Update code of conduct #2821
Update code of conduct #2821
Conversation
Response to the first item at #2819
This change requires general project consensus. Is this a PMC or Committers vote? |
No, this change hasn't voted. I just proposed an idea, to move a more standardized, but very similar code of conduct that we have. |
This would require a PMC vote for approval, but I would like to have a majority of committers indicate their support of this as well as a good discussion of it before taking it before the PMC. |
Since @TheAspens requested comments from committers, I am responding. I don't have strong opinions about these changes one way or the other, but I do feel that the sections to be deleted have some worthwhile wording that should perhaps be retained. I don't have the time or inclination to go into further detail about this. |
I don't think we gain anything by using the github template. If I recall, that template (among others) was used as a starting point for the BOINC code of conduct and ideas from different resources were melded together into what we have. If there are specific shortcomings, it makes sense to address them, but I'd view this move as unnecessary and maybe even a step backwards in terms of readability (I may just be missing the specifics in the diff). |
Feel free to close if you think it's unnecessary. |
I had a brief look at the proposed changes. Before I dive any deeper I'd like to understand the motivation for those changes:
|
I thought a standardized version of the COC is easier to understand, more people familiar with it, because of its standardized nature. That's it, nothing fancy. |
Thanks, I see your point Adam. I don't have a strong opinion on this: I'm neither sure the COC represents such a standard, nor do I think we stray far from any COC as they're all structured similarly, while still representing each project's specifics. Again, I'm neutral on this as I mostly care about the content and its clear communication and not so much about a perceived standardization. Up to the PMC... |
I'm going to close this issue, because the trouble bigger with it, then the expected gain. |
Response to the first item at #2819