Awesome-Mirrors/awesome-ipfs
1
0
Fork 0
mirror of https://github.com/ipfs/awesome-ipfs.git synced 2024-12-26 15:59:33 -05:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #322 from jessicaschilling/patch-1

Browse Source 
Update pull_request_template.md
This commit is contained in:
Andrew Nesbitt 2020-02-25 19:07:57 +00:00 committed by GitHub
commit fb3b98d7d0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 42 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

52
pull_request_template.md
View File

@ -1,20 +1,52 @@
## What kind of change is it?
## What kind of PR is this?
**Select only one** *to speed up review/approval; i.e., don't lump an addition and a removal into a single PR.*
- [ ] Addition
- [ ] Removal
- [ ] Edit
- [ ] Other
- [ ] **Adding** something new to awesome-ipfs
- [ ] **Editing** something already listed on awesome-ipfs
- [ ] **Removing** something from awesome-ipfs
- [ ] **Something else** *(if so, please explain in the "Additional details" section below)*
<!-- If your change is not listed above, please remove the checklist bellow. -->
### Checklist
## Pre-submit checklist
**Please confirm ALL of the following** before submitting your PR.
- [ ] This PR includes only one addition, removal, or edit.
- [ ] I edited the `/data` directory instead of the [README.md](https://github.com/ipfs/awesome-ipfs/blob/master/README.md).
- [ ] This PR includes only one addition/removal/edit.
- [ ] I ran the `make build` command following my edits to the `/data` directory.
- [ ] I reviewed the [content policy](https://github.com/ipfs/awesome-ipfs/blob/master/POLICY.md) to ensure my submission meets the requirements.
- [ ] I reviewed the [content policy](https://github.com/ipfs/awesome-ipfs/blob/master/POLICY.md) and the and the [IPFS Community Code of Conduct](https://github.com/ipfs/community/blob/master/code-of-conduct.md) to ensure my submission meets the requirements.
- [ ] I have followed the [CONTRIBUTING.md guidelines](https://github.com/ipfs/awesome-ipfs/blob/master/CONTRIBUTING.md).
## Details
## Additional details
Provide details of your changes here.
### Is there anything else we should know about this PR?
<!-- If you've checked "Something else" above, or just want to provide additional info or clarification, please do so here. -->
### For new additions: What is your project's *current* size/reach?
<!--This could be number of users, number of integrations, frequency of use, or any other key metrics. If your PR isn't for a new addition to awesome-ipfs, or you don't know these numbers, you can leave this out.-->
### For new additions: What is your project's *potential* size/reach?
<!--This could be number of users, number of integrations, frequency of use, or any other key metrics. If your PR isn't for a new addition to awesome-ipfs, or you don't know these numbers, you can leave this out.-->
### For new additions: How critical is IPFS to your project?
<!--Choose one. If your PR isn't for a new addition to awesome-ipfs, you can leave this out.-->
- [ ] Essential
- [ ] Somewhat critical
- [ ] Useful, but not critical
### For new additions: What core goal(s) does your project address?
<!--Choose as many as apply. If your PR isn't for a new addition to awesome-ipfs, you can leave this out.-->
- [ ] Big-data solutions
- [ ] Freedom from corporate/government interference
- [ ] Data integrity
- [ ] Dev tools or other ways to enable developers
- [ ] Disaster resilience/recovery
- [ ] File storage/retrieval
- [ ] File streaming
- [ ] Permanent archiving
- [ ] Self-sovereign idenity
- [ ] Platforms that utilize consensus, reputation, or incentivization
- [ ] Other *(please list)*
### Is anything about IPFS blocking your project?
<!--If aspects of IPFS are hindering your project's progress, please elaborate here.-->