awesome/ipfs
1
0
Fork 0
mirror of https://github.com/ipfs/awesome-ipfs.git synced 2024-11-20 11:28:35 -05:00
Code Activity
ipfs/pull_request_template.md
Jessica Schilling 8af78ae0da
Update pull_request_template.md 
First pass at an improved PR template for awesome-ipfs. @andrew -- we'll need to change the pre-submit checklist based on what you figure out surrounding the mechanisms of making a PR easier to make. In the meantime, please take a look at the remaining questions to see if they're useful for getting a bead on collabs.

cc @momack2 @autonome @renrutnnej
2020-02-24 14:23:22 -07:00

2.6 KiB
Raw Blame History

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.

  • 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)

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.
  • I ran the make build command following my edits to the /data directory.
  • I reviewed the content policy to ensure my submission meets the requirements.
  • I have followed the CONTRIBUTING.md guidelines.

Additional details

What are the changes that you've made in this PR?

Please provide details of your changes here.

Is anything about IPFS blocking your project?

If aspects of IPFS are hindering your project's progress, please elaborate 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, 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, 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