Open BigLep opened 1 year ago
Summarizing Tasks:
NPM docs like don't link back to the top-level helia REAME which has all the info (see npmjs.com/package/helia ). The API links from within are broken.
I think a more fleshed out Documentation
section in each package would be good here? Something similar to the version in the helia examples.
I'm going to finetune this but here are some things coming to mind when looking at this again with fresh eyes. I know I need to check in on the other comments above. I'm still working here but wanted to get out some initial notes that was seeing.
@achingbrain :
NPM docs like don't link back to the top-level helia REAME which has all the info (see npmjs.com/package/helia ). The API links from within are broken.
The point I'm trying to make is that we're going to invest a lot in https://github.com/ipfs/helia. That is the landing page. I think we should have the bare minimum text under each of the packages under https://github.com/ipfs/helia/tree/main/packages by provide a big/bold link back to https://github.com/ipfs/helia. (I assume we still need to keep the licensing text copy/pasted, but stuff about contributing, docs, support, etc. should all be in one place.). This prevents copy/paste and helps extract more value out of the work we're putting into the top-level project readme. Does that make sense?
I did some more readme updates for some of the items above: https://github.com/ipfs/helia/pull/83
Thanks @whizzzkid for your contributions here and getting more task tracking going. I know I piled some more tasks on with some of my comments. I have gone through and attempted to coalese all the tasks in the top-level issue description. Feel free to modify. We can let that be our source of truth for how this endeavor is progressing.
I think there are two tiers of work. There are easier things that can be completed pretty independently. Thanks for seeing and jumping on those @whizzzkid. Please keep plugging away as able.
Then there are the bigger items around the project's relationship to other projects and direction. I think this is the most important area to focus on @achingbrain . This is items like the manifest updates and describing how the project relates to js-ipfs. I want someone to come to the project and after a quick read to get why we're building Helia and where it fits. I would then role to the developer/contributor guide stuff. Let me know if it's helpful to talk more specifically on priorities here.
Below are items that stuck out when coming to https://github.com/ipfs/helia with fresh eyes imagining what it's like for someone who hears about Helia, wants to learn more, and wants to contribute potentially:
README Items
Manifesto Items
Other specific things to do
General thoughts