forked from DevinoSolutions/upup
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request DevinoSolutions#245 from amjedidiah/docs/add-opens…
…ource-documentation chore(docs): added other essential open source documentation files
- Loading branch information
Showing
8 changed files
with
233 additions
and
19 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,34 @@ | ||
--- | ||
name: Bug report | ||
about: Create a report to help us improve | ||
title: '' | ||
labels: bug | ||
assignees: '' | ||
|
||
--- | ||
|
||
**Describe the bug** | ||
A clear and concise description of what the bug is. | ||
|
||
**To Reproduce** | ||
Steps to reproduce the behaviour: | ||
|
||
1. Go to '...' | ||
2. Click on '....' | ||
3. See error | ||
|
||
**Expected behaviour** | ||
A clear and concise description of what you expected to happen. | ||
|
||
**Screenshots** | ||
If applicable, add screenshots to help explain your problem. | ||
|
||
**Environment:** | ||
|
||
- OS: [e.g. iOS] | ||
- Browser: [e.g. chrome, safari] | ||
- Version: [e.g. 22] | ||
- Commit Hash: [e.g. abc1234] | ||
|
||
**Additional context** | ||
Add any other context about the problem here. |
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,20 @@ | ||
--- | ||
name: Feature request | ||
about: Suggest an idea for this project | ||
title: '' | ||
labels: enhancement | ||
assignees: '' | ||
|
||
--- | ||
|
||
**Is your feature request related to a problem? Please describe.** | ||
A clear and concise description of what the problem is. | ||
|
||
**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. |
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,25 @@ | ||
# Upup Pull Request Template | ||
|
||
## Description | ||
|
||
<!-- TODO: Please include a summary of the change and which issue is fixed. Include relevant motivation and context. --> | ||
|
||
Fixes # (issue) | ||
|
||
## Type of change | ||
|
||
<!-- TODO: Please delete options that are not relevant. --> | ||
|
||
- [ ] Bug fix (non-breaking change which fixes an issue) | ||
- [ ] New feature (non-breaking change which adds functionality) | ||
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) | ||
- [ ] Documentation update | ||
|
||
## Checklist | ||
|
||
- [ ] My code follows the style guidelines of this project | ||
- [ ] I have performed a self-review of my own code | ||
- [ ] I have made corresponding changes to the documentation | ||
- [ ] My changes generate no new warnings | ||
- [ ] I have added tests that prove my fix is effective or that my feature works | ||
- [ ] I have updated the CHANGELOG.md file |
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 |
---|---|---|
|
@@ -17,3 +17,5 @@ storybook-static | |
# public folder temp files | ||
public | ||
/stories/Uploader.stories.js | ||
|
||
.vscode |
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,53 @@ | ||
# Contributor Covenant 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. | ||
|
||
## Our Standards | ||
|
||
Examples of behaviour that contributes to a positive environment: | ||
|
||
- 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 behaviour: | ||
|
||
- The use of sexualized language or imagery | ||
- Trolling, insulting/derogatory comments, and personal or political attacks | ||
- Public or private harassment | ||
- Publishing others' private information without explicit permission | ||
- Other conduct which could reasonably be considered inappropriate | ||
|
||
## Enforcement Responsibilities | ||
|
||
Project maintainers are responsible for clarifying and enforcing our standards of | ||
acceptable behaviour and will take appropriate and fair corrective action in | ||
response to any behaviour that they deem inappropriate, threatening, offensive, | ||
or harmful. | ||
|
||
## Scope | ||
|
||
This Code of Conduct applies within all community spaces, and also applies when | ||
an individual is officially representing the community in public spaces. | ||
|
||
## Enforcement | ||
|
||
Instances of abusive, harassing, or otherwise unacceptable behaviour may be | ||
reported to the community leaders responsible for enforcement at | ||
[hello@devino.com](mailto:hello@devino.com). | ||
All complaints will be reviewed and investigated promptly and fairly. | ||
|
||
## Attribution | ||
|
||
This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/), | ||
version 2.0, available at | ||
<https://www.contributor-covenant.org/version/2/0/code_of_conduct.html>. |
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,51 @@ | ||
# Contributing to Upup | ||
|
||
We love your input! We want to make contributing to Upup as easy and transparent as possible, whether it's: | ||
|
||
- Reporting a bug | ||
- Discussing the current state of the code | ||
- Submitting a fix | ||
- Proposing new features | ||
- Becoming a maintainer | ||
|
||
## Development Process | ||
|
||
1. Fork the repo and create your branch from `master` | ||
2. Install dependencies using `pnpm install` or whatever package manager you use | ||
3. Make your changes | ||
4. Run `pnpm run prettier-check` to ensure code style | ||
5. Run `pnpm run lint` to ensure code quality | ||
6. Run `pnpm run test` to ensure everything works as expected | ||
7. Run `pnpm run build` to ensure everything builds properly | ||
8. Create a pull request! | ||
|
||
## Pull Request Process | ||
|
||
1. Update the README.md with details of changes if needed | ||
2. The PR will be merged once you have the sign-off of at least one maintainer | ||
|
||
## Any contributions you make will be under the MIT Software License | ||
|
||
When you submit code changes, your submissions are understood to be under the same [MIT License](LICENSE) that covers the project. | ||
|
||
## Report bugs using Github's [issue tracker](https://github.com/DevinoSolutions/upup/issues) | ||
|
||
We use GitHub issues to track public bugs. | ||
|
||
## Write bug reports with detail, background, and sample code | ||
|
||
**Great Bug Reports** tend to have: | ||
|
||
- A quick summary and/or background | ||
- Steps to reproduce | ||
- What you expected would happen | ||
- What actually happens | ||
- Notes (possibly including why you think this might be happening) | ||
|
||
## License | ||
|
||
By contributing, you agree that your contributions will be licensed under its MIT License. | ||
|
||
## References | ||
|
||
This document was adapted from the open-source contribution guidelines for [Facebook's Draft](https://github.com/facebook/draft-js/blob/master/CONTRIBUTING.md). |
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,23 @@ | ||
# Security Policy | ||
|
||
## Supported Versions | ||
|
||
| Version | Supported | | ||
| ------- | ------------------ | | ||
| 2.4.x | :white_check_mark: | | ||
| 2.3.x | :white_check_mark: | | ||
| < 2.3 | :x: | | ||
|
||
## Reporting a Vulnerability | ||
|
||
If you discover a security vulnerability within Upup, please send an email to [hello@devino.com](mailto:hello@devino.com). All security vulnerabilities will be promptly addressed. | ||
|
||
Please do not publicly disclose the issue until it has been addressed by the team. | ||
|
||
## Security Update Process | ||
|
||
1. The vulnerability is received and assigned to a primary handler | ||
2. The problem is confirmed and a list of affected versions is determined | ||
3. Code is audited to find any similar problems | ||
4. Fixes are prepared for all supported releases | ||
5. New versions are released and the vulnerability is publicly announced |