-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add CoC derived from Flatpak #6
Conversation
Signed-off-by: Jorge O. Castro <jorge.castro@gmail.com>
CODE_OF_CONDUCT.md
Outdated
|
||
The following behaviors are expected and requested of all community members: | ||
|
||
* Participate in an authentic and active way. In doing so, you contribute to the health and longevity of this community. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"authentic" is a new one for me and I don't really know what it would mean here. As in the opposite of "in bad faith"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok pushed with "Participate actively and in good faith." instead. Hopefully that will be clearer.
CODE_OF_CONDUCT.md
Outdated
|
||
If you are subject to or witness unacceptable behavior, or have any other concerns, please notify a community organizer as soon as possible: | ||
|
||
< To Be Determined> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Something along these lines might work:
- At events, there will always be an on-call contact for the event itself. This information will be posted along with any other event details.
- Outside of events, there is a reporting address coc@flathub.org which is handled by a group of volunteers. The current recipients of that address are documented on the flathut "who is on the code-of-conduct-committee" page.
(This kind of kicks the issue down the road to determine the whos and whats, but since it's an additional indirection, there is time to fill out the details outside of this CoC)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok pushed most of this, however I can't seem to find the "who is on the code-of-conduct-committee" page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aleix asked if I would have a look; just some nits and a suggestion to indirect the contact-information.
Signed-off-by: Jorge O. Castro <jorge.castro@gmail.com>
We could grit down in details for a very long time. As we usually say in my line of work "Good enough for now, safe enough to try". |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This covers most of the main points that a CoC needs to, and thus looks good enough for our immediate needs. 👍
Ok it's been long enough for review, merging this. |
This is the Flatpak CoC adapted for use with Flathub. I have made no behavioral changes.
Still needs a point of contact before merging, recommend that be the bootstrap folks for now.