[2021 Theme Proposal Summary] Improved developer experience

[JonasKruckenberg]

Note, this is part of the 2021 IPFS project planning process - feel free to add other potential 2021 themes for the IPFS project by opening a new issue or discuss this proposed theme in the comments, especially other example workstreams that could fit under this theme for 2021. Please also review others’ proposed themes and leave feedback here!

Theme description

A lot of current proposals ( while very valid in their own right ) focus on improving the experience of IPFS developers.
This proposal is intended to summarize their commonalities and provide actionable ideas.

Hypothesis

Improving the overall IPFS developer experience will provide more and better results faster.

Vision statement

A bigger interest in IPFS and it's core ideas will bring new developers to the community that build apps on IPFS, help with software in the stack and more financial investment as well.
Features can be implemented faster and a diverse set of developers represented in the community will lead to mature features.

Why focus this year

This has been a focus last year and it should stay a focus in 2021.

Example workstreams

DX proposals and issues over the last year boil down to four main areas of improvement:

1. APIs
   [2021 Theme Proposal] Composability of core implementations #62,[2021 Theme Proposal] Codify & Streamline InterPlanetary Stack #61 capture this idea pretty well, improving the APIs and architecture of IPFS implementations helps to onboard new developers and increase adoption.

2. Tooling
   [2021 Theme Proposal] Inter Planetary Playground #87 fits into this, as well as Add C/C++ API to Rust or Go IPFS #77 and especially [2021 Theme Proposal] Developer Tooling #63.
   Refer to each proposal for specifics, but in general this is awesome! Mature tooling would further adoption across the industry since no one likes working with arcane tech for a big project right?

3. Specifications
   This is another big one, we should work out specifications across the stack. This would make it easier for people to develop compliant implementations and also get the IPFS community aligned.
   This is especially pressing since we don't want to end up with a developer aristocracy where the stack has become so complicated and arcane that only a select few can work on the project.
   (Looking at you graphsync spec 🌚)

4. Talk about IPFS!
   Talk to your coworkers, friends and family about this! IPFS is awesome, let them know!
   Talking about IPFS also includes a bigger media presence( blog articles etc. ),
   as well as conventions ( at some point :| ) and encouraging people to become IPFS developer advocates in their communities.
   [2021 Theme Proposal] IPFS Africa Community #86 fits in here quite nicely.
   in short just keep the ecosystem WG around

Other content

Refer to all proposals mentioned above for their specific ideas

[welcome]

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

• "Priority" labels will show how urgent this is for the team.
• "Status" labels will show if this is ready to be worked on, blocked, or in progress.
• "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.