Initial Import

Author: jessefreeman

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,93 @@
+# Citizen Code of Conduct
+
+## 1. Purpose
+
+A primary goal of Space Station 8 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).
+
+This code of conduct outlines our expectations for all those who participate in our community, as well as the consequences for unacceptable behavior.
+
+We invite all those who participate in Space Station 8 to help us create safe and positive experiences for everyone.
+
+## 2. Open [Source/Culture/Tech] Citizenship
+
+A supplemental goal of this Code of Conduct is to increase open [source/culture/tech] citizenship by encouraging participants to recognize and strengthen the relationships between our actions and their effects on our community.
+
+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.
+
+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.
+
+## 3. Expected Behavior
+
+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.
+ * Exercise consideration and respect in your speech and actions.
+ * Attempt collaboration before conflict.
+ * Refrain from demeaning, discriminatory, or harassing behavior and speech.
+ * 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.
+ * Remember that community event venues may be shared with members of the public; please be respectful to all patrons of these locations.
+
+## 4. Unacceptable Behavior
+
+The following behaviors are considered harassment and are unacceptable within our community:
+
+ * Violence, threats of violence or violent language directed against another person.
+ * Sexist, racist, homophobic, transphobic, ableist or otherwise discriminatory jokes and language.
+ * Posting or displaying sexually explicit or violent material.
+ * Posting or threatening to post other people's personally identifying information ("doxing").
+ * Personal insults, particularly those related to gender, sexual orientation, race, religion, or disability.
+ * Inappropriate photography or recording.
+ * Inappropriate physical contact. You should have someone's consent before touching them.
+ * Unwelcome sexual attention. This includes, sexualized comments or jokes; inappropriate touching, groping, and unwelcomed sexual advances.
+ * Deliberate intimidation, stalking or following (online or in person).
+ * Advocating for, or encouraging, any of the above behavior.
+ * Sustained disruption of community events, including talks and presentations.
+
+## 5. Weapons Policy
+
+No weapons will be allowed at Space Station 8 events, community spaces, or in other spaces covered by the scope of this Code of Conduct. Weapons include but are not limited to guns, explosives (including fireworks), and large knives such as those used for hunting or display, as well as any other item used for the purpose of causing injury or harm to others. Anyone seen in possession of one of these items will be asked to leave immediately, and will only be allowed to return without the weapon. Community members are further expected to comply with all state and local laws on this matter.
+
+## 6. Consequences of Unacceptable Behavior
+
+Unacceptable behavior from any community member, including sponsors and those with decision-making authority, will not be tolerated.
+
+Anyone asked to stop unacceptable behavior is expected to comply immediately.
+
+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).
+
+## 7. Reporting Guidelines
+
+If you are subject to or witness unacceptable behavior, or have any other concerns, please notify a community organizer as soon as possible at [email protected].
+
+
+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.
+
+## 8. Addressing Grievances
+
+If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify PixelVision8 with a concise description of your grievance. Your grievance will be handled in accordance with our existing governing policies. 
+
+
+
+## 9. Scope
+
+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.
+
+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.
+
+## 10. Contact info
+
+[email protected]
+
+## 11. License and attribution
+
+The Citizen Code of Conduct is distributed by [Stumptown Syndicate](http://stumptownsyndicate.org) under a [Creative Commons Attribution-ShareAlike license](http://creativecommons.org/licenses/by-sa/3.0/). 
+
+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).
+
+_Revision 2.3. Posted 6 March 2017._
+
+_Revision 2.2. Posted 4 February 2016._
+
+_Revision 2.1. Posted 23 June 2014._
+
+_Revision 2.0, adopted by the [Stumptown Syndicate](http://stumptownsyndicate.org) board on 10 January 2013. Posted 17 March 2013._

.github/CONTRIBUTING.md

@@ -0,0 +1,40 @@
+## Contributing
+
+:+1: Thanks for offering to contribute to this project. Every contribution is greatly appreciated.
+
+### Code of Conduct
+
+Everyone contributing to this project must adhere to the [Code of Conduct](./CODE_OF_CONDUCT.md).
+
+If you feel that someone is not upholding this code, please reach out via [email](mailto:[email protected]) to open a discussion.
+
+### Issues & Bounties
+
+You can help by search for an existing issue or opening a new issue to help find bugs that need to be fixed. If you are interested in working on a specific issue, reach out via [email](mailto:[email protected]) to be added to the repo and have the issue assigned to you. You can still work on an issue on your own but letting us know first helps avoid multiple people working on fixing the same bug.
+
+Do open issues for questions, feature requests, proposals, bug reports, etc. Please do not open an issue for typos or other simple fixes; open a pull request instead.
+
+Finally, we offer [bounties](https://github.com/PixelVision8/PixelVision8/labels/bounty) for specific issues we are unable to directly fix due to time or knowledge. Bounties have the following 3 rules:
+
+**1: All source code written is yours to keep.** This is NOT a [work for hire](https://en.wikipedia.org/wiki/Work_for_hire); you retain full copyright ownership of the code you write. All I am asking is that Pixel Vision 8 gets the right to use/publish that code under the license used by the project. For example, if you release your code under MIT, but Pixel Vision 8 uses MS-PL, the code you contribute goes into the main project under MS-PL with a credit to you as the original creator. The Pixel Vision 8 license may change in the future, so any contributed code adopts the new license where applicable. If you use open-source code with a different license, please make that clear so the correct license and contributor are included. In the end, you can do whatever you want with the code you create after it is accepted. Feel free to continue to work on it, release it under your license, or use it in proprietary projects.
+
+**2: You are free to work on the project however you like.** If you do a lot of programming on Twitch, for example, you can stream the whole process, and you can publish anything about the project you want, including technical write-ups and example projects. You can also work in whatever environment you want, as long as the final product works on the expected platforms with the expected languages/dependencies. Note, however, that the bounties state a schedule/timeline/budget and those are unlikely to change without a very detailed assessment explaining, for example, why a project could take longer than expected. If you contribute, feel free to put that contribution down on your resume or what have you. If we end up establishing a regular working relationship I am also happy to act as a professional reference for job applications.
+
+**3: You are responsible for taxable income made from these bounties.** This one's pretty obvious but for those who aren't familiar, this is effectively non-employee income, and you need to pay taxes (depending on where you live). In the United States, for example, this is simply ["Other Income" on line 21 of Form 1040](https://www.irs.gov/pub/irs-pdf/f1040.pdf). The exception to this rule is if you live in the United States and make more than $600 from my projects, at which point I need a [Form W-9](https://www.irs.gov/pub/irs-pdf/fw9.pdf) sent to me so I can send you a 1099-MISC next year.
+
+If you have any further questions, feel free to [email me](mailto:[email protected]).
+
+### Pull Requests
+
+All fixes and bounties should be submitted via pull requests. Each pull request should follow a few simple rules listed below:
+
+* The title must clearly define the work.
+  - This allows maintainers to prioritize pull requests at a high level
+  - This saves time because maintainers don't need to traverse the list of pull requests to read descriptions of the work
+  - **Caveat** Pull requests with vague titles may be closed without commit (e.g. Use `Fix typo of 'excldue'` rather than `Fix typo`)
+* The description should expand on the work if it is not clearly represented in the title.
+  - Linking to related issues and providing inputs/outputs of new behaviors helps maintainers and future users understand the contribution
+* Commit messages must be clear and concise, but not _too_ concise.
+  - Writing [good commit messages](https://thoughtbot.com/blog/5-useful-tips-for-a-better-commit-message) results in quality history in every repository
+  - Explain why the commit was created, how it functions at a high level, and who/what this may affect
+  - There are some times when a commit may be subject-only, but these are rare. Examples may include `Bump version to 1.0` or `Add X as contributor`

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,26 @@
+---
+name: Bug report
+about: Found a bug? Submit and issue and we'll look into it.
+title: ""
+labels: bug
+assignees: jessefreeman
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is, including version(s) affected.
+
+**To reproduce**
+Steps to reproduce the behavior:
+1.
+2.
+3.
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, [add screenshots from PV8](https://docs.pixelvision8.com/pixelvisionos/screenshots) to help explain your problem.
+
+**Additional notes**
+Add any other details about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: We'd love to hear any ideas you may have to help make Pixel Vision 8 better.
+title: ''
+labels: enhancement
+assignees: jessefreeman
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/new_map.md

@@ -0,0 +1,18 @@
+---
+name: Submit New Map
+about: Did you create a level that you'd like to have included with the source code?
+title: ''
+labels: map
+assignees: jessefreeman
+---
+
+**Who Created the level**
+Name: Jesse Freeman
+Website: https://jessefreeman.com
+Twitter: [@jessefreeman](https://twitter.com/jessefreeman)
+
+**Screenshots**
+Attach your map png, [add screenshots from PV8](https://docs.pixelvision8.com/pixelvisionos/screenshots) to be included in the game.
+
+**Additional information**
+Add any other context or screenshots about map you'd like to share.

.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,17 @@
+---
+name: Question
+about: Open an issue to ask a question
+title: ""
+labels: question
+assignees: jessefreeman
+
+---
+
+**What is your question?**
+Enter one or two sentences at most here. Provide details later.
+
+**Where did you look before asking here?**
+This helps to understand where documentation may be lacking.
+
+**Additional context**
+Add any other context about the problem here.

.github/changelog.json

@@ -0,0 +1,39 @@
+{
+    // "commits" or "prs", defaults to commits. "prs" will soon allow for resolving labels
+    // from pull requests
+    "resolve": "commits",
+  
+    // "asc" or "desc", determines the order of commits in the output
+    "sort": "asc",
+  
+    // GitHub user or org name
+    "owner": "jessefreeman",
+  
+    // Repository name
+    "repo": "changelog",
+  
+    // Enterprise GitHub base url
+    "enterprise": "https://ghe.example.com",
+  
+    // Path to custom template following Go Text template syntax
+    "template": "/path/to/your/template",
+  
+    // Group commits by headings based on patterns supporting Perl syntax regex or plain text
+    "groupings": [
+      { "name":  "Contributions", "patterns":  [ "(?i)\\bfeat\\b" ] }
+    ],
+  
+    // Exclude commits based on this set of patterns or texts
+    // (useful for common maintenance commit messages)
+    "exclude": [
+      "^(?i)release\\s+\\d+\\.\\d+\\.\\d+",
+      "^(?i)minor fix\\b",
+      "^(?i)wip\\b"
+    ],
+  
+    // Prefers local commits over API. Requires executing from within a Git repository.
+    "local": false,
+  
+    // Processes UP TO this many commits before processing exclusion/inclusion rules. Defaults to size returned from GitHub API.
+    "max_commits": 250
+  }

.github/labeler.yml

@@ -0,0 +1,29 @@
+# labeler "full" schema
+# See my other project, https://github.com/jimschubert/labeler-action
+enable:
+  issues: true
+  prs: true
+
+comments:
+  issues: |
+    Thanks for opening this issue!
+    I have applied any labels matching special text in your title and description.
+  prs: |
+    Thanks for the contribution!
+    I have applied any labels matching special text in your title and description.
+
+labels:
+  'bug':
+    include:
+      - '\bbug[s]?\b'
+      - '\bfix(es)?\b'
+    exclude: []
+  'help wanted':
+    include:
+      - '\bhelp( me)?\b'
+    exclude:
+      - '\b\[test(ing)?\]\b'
+  'enhancement':
+    include:
+      - '\bfeat\b'
+    exclude: []

.github/workflows/community.yml

@@ -0,0 +1,18 @@
+name: Community
+on: 
+  issues:
+    types: [opened, edited, milestoned]
+  pull_request:
+    types: [opened]
+
+jobs:
+
+  labeler:
+    runs-on: ubuntu-latest
+
+    steps:
+    - name: Check Labels
+      id: labeler
+      uses: jimschubert/labeler-action@v1
+      with:
+        GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}