Skip to content

Commit 4e819e0

Browse files
dholmsdholms
committed
Initial commit
0 parents  commit 4e819e0

7 files changed

+1674
-0
lines changed

‎.github/CODE_OF_CONDUCT.md

+85
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,85 @@
1+
# Code of Conduct
2+
3+
## 1. Purpose
4+
5+
A primary goal of `FISSON` is to be inclusive to the largest number of contributors, with the most varied and diverse backgrounds possible. As such, we are committed to providing a friendly, safe and welcoming environment for all, regardless of gender, sexual orientation, ability, ethnicity, socioeconomic status, and religion (or lack thereof).
6+
7+
This code of conduct outlines our expectations for all those who participate in our community, as well as the consequences for unacceptable behavior.
8+
9+
We invite all those who participate in `FISSION` to help us create safe and positive experiences for everyone.
10+
11+
## 2. Open Source Citizenship
12+
13+
A supplemental goal of this Code of Conduct is to increase open source citizenship by encouraging participants to recognize and strengthen the relationships between our actions and their effects on our community.
14+
15+
Communities mirror the societies in which they exist and positive action is essential to counteract the many forms of inequality and abuses of power that exist in society.
16+
17+
If you see someone who is making an extra effort to ensure our community is welcoming, friendly, and encourages all participants to contribute to the fullest extent, we want to know.
18+
19+
## 3. Expected Behavior
20+
21+
The following behaviors are expected and requested of all community members:
22+
23+
* Participate in an authentic and active way. In doing so, you contribute to the health and longevity of this community.
24+
* Exercise consideration and respect in your speech and actions.
25+
* Attempt collaboration before conflict.
26+
* Refrain from demeaning, discriminatory, or harassing behavior and speech.
27+
* Be mindful of your surroundings and of your fellow participants. Alert community leaders if you notice a dangerous situation, someone in distress, or violations of this Code of Conduct, even if they seem inconsequential.
28+
* Remember that community event venues may be shared with members of the public; please be respectful to all patrons of these locations.
29+
30+
## 4. Unacceptable Behavior
31+
32+
The following behaviors are considered harassment and are unacceptable within our community:
33+
34+
* Violence, threats of violence or violent language directed against another person.
35+
* Sexist, racist, homophobic, transphobic, ableist or otherwise discriminatory jokes and language.
36+
* Posting or displaying sexually explicit or violent material.
37+
* Posting or threatening to post other people’s personally identifying information ("doxing").
38+
* Personal insults, particularly those related to gender, sexual orientation, race, religion, or disability.
39+
* Inappropriate photography or recording.
40+
* Inappropriate physical contact. You should have someone’s consent before touching them.
41+
* Unwelcome sexual attention. This includes, sexualized comments or jokes; inappropriate touching, groping, and unwelcomed sexual advances.
42+
* Deliberate intimidation, stalking or following (online or in person).
43+
* Advocating for, or encouraging, any of the above behavior.
44+
* Sustained disruption of community events, including talks and presentations.
45+
46+
## 5. Consequences of Unacceptable Behavior
47+
48+
Unacceptable behavior from any community member, including sponsors and those with decision-making authority, will not be tolerated.
49+
50+
Anyone asked to stop unacceptable behavior is expected to comply immediately.
51+
52+
If a community member engages in unacceptable behavior, the community organizers may take any action they deem appropriate, up to and including a temporary ban or permanent expulsion from the community without warning (and without refund in the case of a paid event).
53+
54+
## 6. Reporting Guidelines
55+
56+
If you are subject to or witness unacceptable behavior, or have any other concerns, please notify a community organizer as soon as possible. hello@brooklynzelenka.com.
57+
58+
59+
60+
Additionally, community organizers are available to help community members engage with local law enforcement or to otherwise help those experiencing unacceptable behavior feel safe. In the context of in-person events, organizers will also provide escorts as desired by the person experiencing distress.
61+
62+
## 7. Addressing Grievances
63+
64+
If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify the maintainers with a concise description of your grievance. Your grievance will be handled in accordance with our existing governing policies.
65+
66+
67+
68+
## 8. Scope
69+
70+
We expect all community participants (contributors, paid or otherwise; sponsors; and other guests) to abide by this Code of Conduct in all community venues–online and in-person–as well as in all one-on-one communications pertaining to community business.
71+
72+
This code of conduct and its related procedures also applies to unacceptable behavior occurring outside the scope of community activities when such behavior has the potential to adversely affect the safety and well-being of community members.
73+
74+
## 9. Contact info
75+
76+
hello@fission.codes
77+
78+
## 10. License and attribution
79+
80+
This Code of Conduct is distributed under a [Creative Commons Attribution-ShareAlike license](http://creativecommons.org/licenses/by-sa/3.0/).
81+
82+
Portions of text derived from the [Django Code of Conduct](https://www.djangoproject.com/conduct/) and the [Geek Feminism Anti-Harassment Policy](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy).
83+
84+
Retrieved on November 22, 2016 from [http://citizencodeofconduct.org/](http://citizencodeofconduct.org/)
85+

‎.github/ISSUE_TEMPLATE/bug_report.md

+54
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: ''
5+
labels: "\U0001F41B bug"
6+
assignees: ''
7+
8+
---
9+
10+
# Summary
11+
12+
## Problem
13+
14+
Describe the immediate problem
15+
16+
### Impact
17+
18+
The impact that this bug has
19+
20+
## Solution
21+
22+
Describe the sort of fix that would solve the issue
23+
24+
# Detail
25+
26+
**Describe the bug**
27+
A clear and concise description of what the bug is.
28+
29+
**To Reproduce**
30+
Steps to reproduce the behavior:
31+
1. Go to '...'
32+
2. Click on '....'
33+
3. Scroll down to '....'
34+
4. See error
35+
36+
**Expected behavior**
37+
A clear and concise description of what you expected to happen.
38+
39+
**Screenshots**
40+
If applicable, add screenshots to help explain your problem.
41+
42+
**Desktop (please complete the following information):**
43+
- OS: [e.g. iOS]
44+
- Browser [e.g. chrome, safari]
45+
- Version [e.g. 22]
46+
47+
**Smartphone (please complete the following information):**
48+
- Device: [e.g. iPhone6]
49+
- OS: [e.g. iOS8.1]
50+
- Browser [e.g. stock browser, safari]
51+
- Version [e.g. 22]
52+
53+
**Additional context**
54+
Add any other context about the problem here.

‎.github/ISSUE_TEMPLATE/feature_request.md

+38
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: ''
5+
labels: "\U0001F497 enhancement"
6+
assignees: ''
7+
8+
---
9+
10+
NB: Feature requests will only be considered if they solve a pain
11+
12+
# Summary
13+
14+
## Problem
15+
16+
Describe the pain that this feature will solve
17+
18+
### Impact
19+
20+
The impact of not having this feature
21+
22+
## Solution
23+
24+
Describe the solution
25+
26+
# Detail
27+
28+
**Is your feature request related to a problem? Please describe.**
29+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
30+
31+
**Describe the solution you'd like**
32+
A clear and concise description of what you want to happen.
33+
34+
**Describe alternatives you've considered**
35+
A clear and concise description of any alternative solutions or features you've considered.
36+
37+
**Additional context**
38+
Add any other context or screenshots about the feature request here.

‎.github/PULL_REQUEST_TEMPLATE.md

+41
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
A similar PR may already be submitted!
2+
Please search among the [Pull request](../) before creating one.
3+
4+
Thanks for submitting a pull request! Please provide enough information so that others can review your pull request:
5+
6+
For more information, see the `CONTRIBUTING` guide.
7+
8+
9+
## Summary
10+
<!-- Summary of the PR -->
11+
12+
This PR fixes/implements the following **bugs/features**
13+
14+
* [ ] Bug 1
15+
* [ ] Bug 2
16+
* [ ] Feature 1
17+
* [ ] Feature 2
18+
* [ ] Breaking changes
19+
20+
<!-- You can skip this if you're fixing a typo or adding an app to the Showcase. -->
21+
22+
Explain the **motivation** for making this change. What existing problem does the pull request solve?
23+
24+
<!-- Example: When "Adding a function to do X", explain why it is necessary to have a way to do X. -->
25+
26+
## Test plan (required)
27+
28+
Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes UI.
29+
30+
<!-- Make sure tests pass on Circle CI. -->
31+
32+
33+
## Closing issues
34+
35+
<!-- Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes (if such). -->
36+
Fixes #
37+
38+
## After Merge
39+
* [ ] Does this change invalidate any docs or tutorials? _If so ensure the changes needed are either made or recorded_
40+
* [ ] Does this change require a release to be made? Is so please create and deploy the release
41+

0 commit comments

Comments
 (0)