-
Notifications
You must be signed in to change notification settings - Fork 34
docs(coc.md): add Code of Conduct for Austin Hackers Association #197
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
base: main
Are you sure you want to change the base?
Conversation
style(README.md): improve readability of local server URL The title formatting was updated to use the more common Markdown syntax for headers, which improves readability and consistency with other Markdown files. A website status badge was added to provide quick access to the live site and indicate its current status. The local server URL was also updated to be a clickable link, improving usability for those reading the README.
The copyright year was updated to reflect the current year, ensuring that the website's footer information is up-to-date.
The .tool-versions and .envrc files are added to the .gitignore file to prevent them from being tracked by Git. These files typically contain local development settings that should not be shared with the team or included in the repository.
The .tool-versions file was removed because it was no longer necessary. The project no longer relies on a specific version of Ruby, making the file redundant.
Introduce a Code of Conduct document to establish guidelines for behavior within the Austin Hackers Association (AHA!). This document outlines the expected conduct, including treating others with respect, avoiding harassment, and being accountable for one's actions. It also details the steps for handling violations, ensuring a safe and inclusive environment for all participants. The addition of this document aims to foster a community where everyone can enjoy and participate without fear of discrimination or harassment.
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.
There are a couple references to organizers but it's not quite clear who the organizers are and there are plenty of meetings where it is just as unclear. Maybe worthwhile to have a list of people that can be contacted?
coc.md
Outdated
|
||
#### Roast the Ideas, Not the Person | ||
|
||
>> Got a hot take? Bring it. Got a dumb take? Expect to hear about it. But keep it fun. Don’t be a dick to the person; they’re here to learn and blow off steam just like you. |
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.
nit: I think these render slightly better if it's just a single >
or maybe none at all but no strong feelings about it
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.
It looks like trash and I will happily accept any and all format changes.
(I'm actually working on the #148 ticket for this reason)
Thank you. I did remove a bunch of those references but clearly not all. But providing some contact direction would be good. |
… process Introduce the 'Mob Rule' section to emphasize collective responsibility and the absence of a hierarchical leadership structure. This addition clarifies that everyone is accountable and has a voice in maintaining the community's standards. Improve the clarity of the confidential reporting process by specifying a contact method, ensuring members know how to report issues discreetly. These changes aim to foster a more inclusive and self-regulating community environment.
\x27 and \x22 for life
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.
LGTM, +1 on the cone hat idea
LGTM |
Here is a CoC from SecKC for reference/example |
Introduce a Code of Conduct document to establish guidelines for behavior
within the Austin Hackers Association (AHA!). This document outlines the
expected conduct, including treating others with respect, avoiding harassment,
and being accountable for one's actions. It also details the steps for handling
violations, ensuring a safe and inclusive environment for all participants.
The addition of this document aims to foster a community where everyone can
enjoy and participate without fear of discrimination or harassment.