-
Notifications
You must be signed in to change notification settings - Fork 24
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Revamp README and stuff for Mozilla Open Leadership
- Loading branch information
1 parent
9713406
commit 8917c0c
Showing
4 changed files
with
186 additions
and
17 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| .DS_Store |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,74 @@ | ||
| # Contributor Covenant Code of Conduct | ||
|
|
||
| ## Our Pledge | ||
|
|
||
| In the interest of fostering an open and welcoming environment, we as | ||
| contributors and maintainers pledge to making participation in our project and | ||
| our community a harassment-free experience for everyone, regardless of age, body | ||
| size, disability, ethnicity, gender identity and expression, level of experience, | ||
| nationality, personal appearance, race, religion, or sexual identity and | ||
| orientation. | ||
|
|
||
| ## Our Standards | ||
|
|
||
| Examples of behavior that contributes to creating a positive environment | ||
| include: | ||
|
|
||
| * Using welcoming and inclusive language | ||
| * Being respectful of differing viewpoints and experiences | ||
| * Gracefully accepting constructive criticism | ||
| * Focusing on what is best for the community | ||
| * Showing empathy towards other community members | ||
|
|
||
| Examples of unacceptable behavior by participants include: | ||
|
|
||
| * The use of sexualized language or imagery and unwelcome sexual attention or | ||
| advances | ||
| * Trolling, insulting/derogatory comments, and personal or political attacks | ||
| * Public or private harassment | ||
| * Publishing others' private information, such as a physical or electronic | ||
| address, without explicit permission | ||
| * Other conduct which could reasonably be considered inappropriate in a | ||
| professional setting | ||
|
|
||
| ## Our Responsibilities | ||
|
|
||
| Project maintainers are responsible for clarifying the standards of acceptable | ||
| behavior and are expected to take appropriate and fair corrective action in | ||
| response to any instances of unacceptable behavior. | ||
|
|
||
| Project maintainers have the right and responsibility to remove, edit, or | ||
| reject comments, commits, code, wiki edits, issues, and other contributions | ||
| that are not aligned to this Code of Conduct, or to ban temporarily or | ||
| permanently any contributor for other behaviors that they deem inappropriate, | ||
| threatening, offensive, or harmful. | ||
|
|
||
| ## Scope | ||
|
|
||
| This Code of Conduct applies both within project spaces and in public spaces | ||
| when an individual is representing the project or its community. Examples of | ||
| representing a project or community include using an official project e-mail | ||
| address, posting via an official social media account, or acting as an appointed | ||
| representative at an online or offline event. Representation of a project may be | ||
| further defined and clarified by project maintainers. | ||
|
|
||
| ## Enforcement | ||
|
|
||
| Instances of abusive, harassing, or otherwise unacceptable behavior may be | ||
| reported by contacting the project team at info {at} open-austin {dot} org. All | ||
| complaints will be reviewed and investigated and will result in a response that | ||
| is deemed necessary and appropriate to the circumstances. The project team is | ||
| obligated to maintain confidentiality with regard to the reporter of an incident. | ||
| Further details of specific enforcement policies may be posted separately. | ||
|
|
||
| Project maintainers who do not follow or enforce the Code of Conduct in good | ||
| faith may face temporary or permanent repercussions as determined by other | ||
| members of the project's leadership. | ||
|
|
||
| ## Attribution | ||
|
|
||
| This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, | ||
| available at [http://contributor-covenant.org/version/1/4][version] | ||
|
|
||
| [homepage]: http://contributor-covenant.org | ||
| [version]: http://contributor-covenant.org/version/1/4/ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,39 @@ | ||
| # Contributing to Budget Party | ||
|
|
||
| :+1: :tada: First off, thanks for taking the time to contribute! :tada: :+1: | ||
|
|
||
| This project has received contributions from some wonderful volunteers. Our goal is to make it easy for you to jump in and help. | ||
|
|
||
| ## What should I know before I get started? | ||
|
|
||
| ### Code of Conduct | ||
| This project adheres to the Contributor Covenant [code of conduct](CONTRIBUTING.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to info {at} open-austin {dot} org. | ||
|
|
||
| ### README | ||
| Our [README](README.md) is the first place you should go, if you haven't already. If you have questions about the goals or purpose of the project, we'd be happy to clarify. [Create an issue](https://github.com/open-austin/budgetparty/issues/new) and mark it with the "question" label. | ||
|
|
||
| ### Roadmap | ||
| Our [roadmap](README.md/#roadmap) is written to give you an idea of the current status of the project. Check it out to see what we are planning to include in the next release and if there are any target dates for upcoming releases. | ||
|
|
||
| ### Communication | ||
| We communicate in a couple different ways: | ||
| 1. Github - You can [open an issue](https://github.com/open-austin/budgetparty/issues/new) to start a discussion here within Github. The project leads will get an email with your message and we will do our best to respond promptly. | ||
| 2. Slack - [Invite yourself](https://slack.open-austin.org/) to the Open Austin Slack Channel and join the [#budgetparty channel](https://open-austin.slack.com/messages/budgetparty). | ||
| 3. IRL - Come to an Open Austin Civic Hack Night and let's chat in person. | ||
|
|
||
| ## How can I help? | ||
|
|
||
| Over the course of this project, we will have (or have had) opportunities to help with design, development, QA & testing, writing, and more. To contribute, you can: | ||
|
|
||
| - Report a bug or request a feature by opening a new issue. | ||
| - Review [open issues](https://github.com/open-austin/budgetparty/issues) and leave a comment if you'd like to help or if you need more information. | ||
|
|
||
| ### Design | ||
|
|
||
| Here is a link to our [design assets and documentation](./design). Here are [open issues labeled "Design"](https://github.com/open-austin/hack-the-budget/issues?q=is%3Aissue+is%3Aopen+label%3Adesign) where you can discuss, provide feedback or volunteer to help. | ||
|
|
||
| ### Development | ||
|
|
||
| [Issues marked with the code label](stin/budgetparty/issues?q=is%3Aissue+is%3Aopen+label%3Acode) are bugs or features that require some knowledge of CSS, React, Javascript, or Firebase. | ||
|
|
||
| Issues with the help wanted label indicate where the best place to start are, but contributions are welcome on any open issue. Please leave a comment before you start working in case work is underway from another contributor. |