awesome-ipfs

awesome-ipfs copied to clipboard

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.

• [x] 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.

• [x] This PR includes only one addition, removal, or edit.
• [x] I edited the /data directory instead of the README.md.
• [x] I reviewed the content policy and the and the IPFS Community Code of Conduct to ensure my submission meets the requirements.
• [x] I have followed the CONTRIBUTING.md guidelines.

Additional details

Is there anything else we should know about this PR?

For new additions: What is your project's current size/reach?

For new additions: What is your project's potential size/reach?

For new additions: How critical is IPFS to your project?

• [x] Essential
• [ ] Somewhat critical
• [ ] Useful, but not critical

For new additions: What core goal(s) does your project address?

• [ ] Big-data solutions
• [ ] Freedom from corporate/government interference
• [ ] Data integrity
• [x] Dev tools or other ways to enable developers
• [ ] Disaster resilience/recovery
• [x] File storage/retrieval
• [ ] File streaming
• [ ] Permanent archiving
• [ ] Self-sovereign identity
• [ ] Platforms that utilize consensus, reputation, or incentivization
• [ ] Other (please list)

Is anything about IPFS blocking your project?

Thank you for submitting this PR! A maintainer will be here shortly to review it. We are super grateful, but we are also overloaded! Help us by making sure that:

• The context for this PR is clear, with relevant discussion, decisions and stakeholders linked/mentioned.

• Your contribution itself is clear (code comments, self-review for the rest) and in its best form. Follow the code contribution guidelines if they apply.

Getting other community members to do a review would be great help too on complex PRs (you can ask in the chats/forums). If you are unsure about something, just leave us a comment. Next steps:

• A maintainer will triage and assign priority to this PR, commenting on any missing things and potentially assigning a reviewer for high priority items.

• The PR gets reviews, discussed and approvals as needed.

• The PR is merged by maintainers when it has been approved and comments addressed.

We currently aim to provide initial feedback/triaging within two business days. Please keep an eye on any labelling actions, as these will indicate priorities and status of your contribution. We are very grateful for your contribution!

@alexbakers if you remove the changes you made to the README and ensure the PR is up to date (resolve conflicts) I can merge this

	Fails
:no_entry_sign:	Please do not edit the README directly. It is generated from the data in the data/ directory.

	Messages
:book:	YAML data files were edited.

Generated by :no_entry_sign: dangerJS against 83dca1c3dbf18792ab8f1b970fba6656b72f4b89