mirror of https://github.com/mue/mue.git
chore: remove unneeded files
This commit is contained in:
David Ralph
parent
177e4fdcdc
commit
29171bce5d
6
.babelrc
6
.babelrc
|
|
@ -1,6 +0,0 @@
|
|||
{
|
||||
"presets": ["@babel/preset-env", "@babel/preset-react"],
|
||||
"plugins": ["@babel/plugin-proposal-class-properties", ["@babel/transform-runtime", {
|
||||
"regenerator": true
|
||||
}]]
|
||||
}
|
||||
3
.env
3
.env
|
|
@ -1,3 +0,0 @@
|
|||
GENERATE_SOURCEMAP=false
|
||||
INLINE_RUNTIME_CHUNK=false
|
||||
SKIP_PREFLIGHT_CHECK=true
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
github: ohlookitsderpy
|
||||
patreon: ohlookitsderpy
|
||||
ko_fi: ohlookitsderpy
|
||||
|
|
@ -1,14 +0,0 @@
|
|||
---
|
||||
name: Feature Request
|
||||
about: Suggest an idea for Mue
|
||||
title: "[Feature Request]"
|
||||
labels: enhancement
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
**Description**
|
||||
A clear and concise description of what you want in this new feature.
|
||||
|
||||
**Additional context**
|
||||
Add any other context or screenshots about the feature request here.
|
||||
|
|
@ -1,76 +0,0 @@
|
|||
# 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, sex characteristics, gender identity and expression,
|
||||
level of experience, education, socio-economic status, 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 hello@muetab.com. 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 https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
|
||||
|
||||
[homepage]: https://www.contributor-covenant.org
|
||||
|
||||
For answers to common questions about this code of conduct, see
|
||||
https://www.contributor-covenant.org/faq
|
||||
|
|
@ -1,37 +0,0 @@
|
|||
# Contributing
|
||||
All contributions are welcome! However, there are some things you need to take note of before starting your contribution to the Mue project.
|
||||
|
||||
By contributing to Mue, you agree that:
|
||||
* None of the work submitted is plagiarised
|
||||
* Your contribution will be distributed under the [BSD-3-Clause License](LICENSE) after it has been merged or implemented otherwise.
|
||||
|
||||
## General
|
||||
Test *everything*. That's right - make sure every feature still works depending on the change you just implemented. If it's a translation, check if all strings are translated.
|
||||
A bug fix? See if it has fixed the issue fully on both Chromium and Firefox. For features, make sure that everything else still works fine and is compatible with what you
|
||||
implemented.
|
||||
|
||||
### Translations
|
||||
Please don't use Google Translate. When submitting new translations, we'd prefer it if you waited until it's finished before pull requesting or if you opened it as a draft.
|
||||
All translation work should be done by copying the ``en-GB.json`` file to a file with your language code as the name, e.g ``fr.json``.
|
||||
|
||||
## Development
|
||||
### Code
|
||||
Here's some quick bullet points as to what your code should be like on Mue:
|
||||
* Follow the general codestyle of the project (unless you can make it more optimised)
|
||||
* Fix any React or JS errors/warnings created
|
||||
* Use as few external dependencies as possible
|
||||
|
||||
### Features
|
||||
We prefer it if you implement features from our [projects board](https://github.com/mue/mue/projects). However, if you have an idea feel free to let us know first via a GitHub
|
||||
issue or our Discord server (see README for invite). Here's a quick list of things to look out for:
|
||||
* External APIs - Please refrain from requesting to servers not on the ``muetab.com``, ``unsplash.com``, ``backblazeb2.com`` or ``duckduckgo.com`` domains. Whenever possible, try to create
|
||||
a "proxy" API service for requests to go through. Pull requests involving paid APIs or heavily limited free plans will be denied.
|
||||
* Clones - Please don't go blatantly copying features from the alternative extensions out there unless you have written permission from the original author of the project.
|
||||
Inspired features are fine.
|
||||
* Removed Features - If a feature has been removed by us don't add it back again without asking us about it first for the reasons as to why it was removed in the first place.
|
||||
|
||||
### Bug Fixes
|
||||
See the note in general.
|
||||
|
||||
## Final Note
|
||||
Contact us before doing anything if you don't want to have to change 1000 things and/or have your pull request closed.
|
||||
Loading…
Reference in New Issue