Initial commit

.github/ACKNOWLEDGMENTS.md

@@ -0,0 +1 @@
+<!-- This file explains relevant related work, such as other projects that are dependencies, or libraries, or modules, or have their own copyrights or licenses that you want to include in your project. -->

.github/AUTHORS.md

@@ -0,0 +1 @@
+<!-- This file lists people who are significant authors of the project, such as the people who are legally related to the work. The GNU project states "Only the contributions that are legally significant for copyright purposes (see Legally Significant) need to be listed. Small contributions, bug reports, ideas, etc., can be omitted." -->

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @thepurplebubble/innerbubble

.github/CONTRIBUTORS.md

@@ -0,0 +1 @@
+<!-- This file explains who has contributed to the project. When we use a CONTRIBUTORS file in our projects, we ask people how they want to be listed, such as by their name, handle, email address, website link, etc. -->

.github/FUNDING.yml

@@ -0,0 +1 @@
+custom: https://hcb.hackclub.com/donations/start/purplebubble

.github/ISSUE_TEMPLATE/bugreport.yml

@@ -0,0 +1,42 @@
+name: Bug report
+description: Create a report to help us address an error.
+title: "[BUG] - "
+labels: ["🛠 goal: fix", "🔒 staff only", "🚦 status: awaiting triage", "🧹 status: ticket work required"]
+projects: ["thepurplebubble/1"]
+assignees:
+  - jdogcoder
+body:
+  - type: markdown
+    attributes:
+      value: '# Bug report'
+  - type: textarea
+    id: bugdescription
+    attributes:
+      label: What bug did you encounter?
+      description: |
+        Please provide a clear description of the bug.
+
+        Include the steps you took to cause the bug, and an explanation of what occurred.
+    validations:
+      required: true
+  - type: textarea
+    id: behaviour
+    attributes:
+      label: What did you expect to happen?
+      description: What did you expect to happen instead of the current behaviour?
+    validations:
+      required: true
+  - type: textarea
+    id: screenshots
+    attributes:
+      label: Screenshots
+      description: Attach any relevant screenshots here.
+    validations:
+      required: false
+  - type: textarea
+    id: extrainformation
+    attributes:
+      label: Additional information
+      description: Is there anything else we should know about this bug?
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/chore.yml

@@ -0,0 +1,25 @@
+name: Chore
+description: For requesting chores, such as cleaning up code.
+title: "[CHORE] - "
+labels: ["🔒 staff only", "🚦 status: awaiting triage", "🧹 status: ticket work required"]
+projects: ["thepurplebubble/1"]
+assignees:
+  - jdogcoder
+body:
+  - type: markdown
+    attributes:
+      value: "# Chore request"
+  - type: textarea
+    id: description
+    attributes:
+      label: What work needs to be performed?
+      description: Provide a clear and concise explanation of the work to be performed.
+    validations:
+      required: true
+  - type: textarea
+    id: extrainfo
+    attributes:
+      label: Additional information
+      description: Is there anything else we should know about this chore?
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/ISSUE_TEMPLATE/documentation.yml

@@ -0,0 +1,32 @@
+name: Documentation
+description: Request an update to invalid/outdated documentation
+title: "[DOC] - "
+labels: ["🔒 staff only", "🚦 status: awaiting triage", "🧹 status: ticket work required", "📄 aspect: text"]
+projects: ["thepurplebubble/1"]
+assignees:
+  - jdogcoder
+body:
+  - type: markdown
+    attributes:
+      value: "# Incorrect Documentation"
+  - type: textarea
+    id: docerrordescription
+    attributes:
+      label: What is incorrect in the documentation?
+      description: Please explain the information that is incorrect in the documentation, and why you think it needs to be updated.
+    validations:
+      required: true
+  - type: textarea
+    id: expectedinformation
+    attributes:
+      label: What should that text say?
+      description: Provide the information that the documentation should actually contain instead of the incorrect content.
+    validations:
+      required: true
+  - type: textarea
+    id: extrainfo
+    attributes:
+      label: Additional information
+      description: Is there anything else we should know about this inaccuracy?
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,23 @@
+name: Feature request
+description: Suggest an idea for this project
+title: "[FEAT] - "
+labels: ["🔒 staff only", "🚦 status: awaiting triage", "🧹 status: ticket work required", "⭐ goal: addition"]
+projects: ["thepurplebubble/1"]
+assignees:
+  - jdogcoder
+body:
+  - type: markdown
+    attributes:
+      value: "# Feature request"
+  - type: textarea
+    id: feature
+    attributes:
+      label: What feature would you like to see?
+      description: Be as detailed as possible here. What would you like this application to do? How should you, as a user, interact with this feature?
+  - type: textarea
+    id: extrainfo
+    attributes:
+      label: Additional information
+      description: Is there anything else we should know about this feature?
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/other.yml

@@ -0,0 +1,25 @@
+name: Other
+description: Use this for any other issues. PLEASE do not create blank issues
+title: "[OTHER] - "
+labels: ["🔒 staff only", "🚦 status: awaiting triage", "🧹 status: ticket work required"]
+projects: ["thepurplebubble/1"]
+assignees:
+  - jdogcoder
+body:
+  - type: markdown
+    attributes:
+      value: "# Other issue"
+  - type: textarea
+    id: issuedescription
+    attributes:
+      label: What would you like to share?
+      description: Provide a clear and concise explanation of your issue.
+    validations:
+      required: true
+  - type: textarea
+    id: extrainfo
+    attributes:
+      label: Additional information
+      description: Is there anything else we should know about this issue?
+    validations:
+      required: false

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,13 @@
+# Pull Request
+
+<!--Before contributing, please read our contributing guidelines-->
+
+## Description:
+
+<!--A brief description of what your pull request does.-->
+
+## Related Issue:
+
+<!--Is this related to an issue? Does it close one? If so, replace the XXXXX below with the issue number.-->
+
+Closes #XXXXX

.github/SECURITY.md

@@ -0,0 +1,9 @@
+# Reporting Security Issues
+
+The PurpleBubble team and community take security bugs in any PurpleBubble project seriously. We appreciate your efforts to responsibly disclose your findings, and will make every effort to acknowledge your contributions.
+
+To report a security issue, please use the GitHub Security Advisory ["Report a Vulnerability"](https://github.com/hackPurpleBubble/REPONAMEHERE/security/advisories/new) tab.
+
+The team will send a response indicating the next steps in handling your report. After the initial reply to your report, the security team will keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance.
+
+Report security bugs in third-party modules to the person or team maintaining the module. You can also report a vulnerability through the [npm contact form](https://www.npmjs.com/support) by selecting "I'm reporting a security vulnerability".

.github/workflows/fsync.yaml

@@ -0,0 +1,19 @@
+name: fsync
+
+on:
+  push:
+    branches:
+      - main
+  schedule:
+    - cron: '*/30 * * * *' # Runs every 30 minutes
+
+jobs:
+  file_sync:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout Repository
+        uses: actions/checkout@v2
+        with:
+          token: ${{ secrets.PBB_TOKEN }}
+      - name: gh_fsync
+        uses: gleich/gh_fsync@master

CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Purple Bubble Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders 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, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+team@purplebubble.org.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.