The full description of the Community WG and its responsibilities are here.
To create one of the largest communities and ecosystems in Open Source.
- IPFS must be easy to learn to use
- IPFS must be easy to create libraries on top of
- IPFS must be easy to contribute to
- People need to know about IPFS and how it can solve their problems
-
Create great entry points for people to learn IPFS
- Project: ProtoSchool
- Project: Documentation Iteration
- Project: Use Case Specific Quickstarts
- Measuring Success:
- # unique developers that use a resource each month
- % growth of this metric over time
-
Create a great new contributor experience that grows outside contributions
- Project: First Commit Events
- Project: Automated Workflow Enhancements
- Measuring Success:
- # new contributors each month
- average time to land every pull request
- % retention of new contributors
- % growth of PRs from external (non-PL paid) contributors
- % growth of unique people commenting on GH issues and PRs
-
Evangelize IPFS
- Project: Deploy to IPFS GitHub Automation
- Measuring Success:
- % growth of projects that depend on IPFS
- % growth of unique people commenting on all projects that depend on or use IPFS
- % growth of media regarding IPFS
ProtoSchool is an entry point for people with little to no prior knowledge of decentralized technologies, blockchain, content addressing, etc.
Note: ProtoSchool is being bootstrapped in the IPFS Community WG but will eventually be spun out into its own project as it will tackle more than just IPFS.
- Milestone #1 (Q4 2018): 1.0 Release
- Milestone #2 (Q1 2019): Public Launch
- Milestone #3 (Q1 2019): ProtoSchool Roadmap
- Measuring Success:
- Unique site visitors per month
- Average % completeness of each workshop
- # of local chapters
The Community WG is in the early research phase of how to best improve the documentation of IPFS. You can see and contribute to that conversation here.
- Milestone #1 (Q1 2019): Documentation Roadmap
The Community WG is planning to create starter kits which help people build on top of IPFS right away, like Truffle Boxes.
- Milestone #1 (Q4 2018): Identify first set of use cases.
- Measuring Success:
- # of uses of each quickstart
These are in-person events designed to guide every participant through landing a pull request on IPFS.
The Community WG is in the early learning phase, documenting the key challenges of contributing to IPFS by working through process by hand as well as running some early events in order to learn from the experience of the attendees.
If you have points of friction you've experienced contributing to IPFS please let us know here.
- Milestone #1 (Q4 2018): Run one “First Commit” event and document learnings
The Community WG is conducting a review of existing GitHub automation tools to consider adding to the IPFS org. If there's some GitHub based automation you've used in the past that you particularly liked please tell us about it here
- Milestone #1 (Q1 2019): Review existing Probot and GitHub Actions
- Milestone #1 (Q4 2018): Define project and dependencies for implementation in 2019