Note: time / space is TBD. Sign up that you’re interested / want to attend and then we’ll update with the final date / time / room
The IPFS Awesome List needs rebooting!
From a thread with @lidel:
I’m putting this in as a placeholder session that is a call for participants. I want to scheme with @lidel about this, please join us / leave a comment / follow this post if you’re interesting in participating.
Time and place TBD as we figure out how to fit in ad hoc sessions into the schedule.
I’m interested in joining.
There is quite some overlap with ecosystem.ipfs.io (powered by an Airtable form > reviewed by IPFS team) so might be worth discussing that in the same conversation.
Awesome
IPFS Shipyard
Ecosystem → airtable?
Merge / integrate scheme between two systems?
Clearly articulate role of Awesome vs Ecosystem?
Github analytics on IPFS project activity?
Where do we want people promoting their awesome hackathon projects?
Content is only English
Can we improve this page?
Can we connect to rest of community? e.g. link to Discourse, Discord, Wikipedia
MAYBE also use Ecosystem / Awesome a source of new info
About Awesome Lists – awesome/awesome.md at main · sindresorhus/awesome · GitHub
Looks like lidel and andrew have commit access
Look at 0Data Apps as another example list of apps → https://0data.app/
Ecosystem → this will be “internally” PLN maintained @mosh
Awesome → have community take over
Some questions:
@boris will ask some other usual suspect PLN companies about contributing – have discussion here in the Discourse forum
The Community page in IPFS docs → Community | IPFS Docs – lists Awesome, but doesn’t list Ecosystem.
Generally, this community page needs updates.
Put Docs on the list for “call for add your stuff” from many different apps, companies, networks, and so on.
I appreciate the effort to reboot the awesome list.
I can understand the distinction between the ecosystem page and awesome, despite the overlap. Awesome lists are typically more open and community-directed in contrast to the ecosystem list which we curate.
The awesome-ipfs list has been around for a while and has a lot of stale submissions (unmaintained and non-functional, e.g. GitHub - fbaiodias/ipfs-chrome-station: Chrome extension that let's you access IPFS urls seamlessly from your local IPFS node, and take a look at its stats). Adding a stale category or status would definitely help.
I’ll create a PR to add a link to the ecosystem page too from the IPFS docs.
Yep. And unless someone objects, @mosh & @SgtPooki and I suggested focusing on code for Awesome List — so a link to the Source code would be the main focus, and then a project / demo / company / docs website if it exists.
Focusing on code for the awesome list makes a lot of sense and makes the distinction with Ecosystem even clearer.
I’ve got an issue where we’re tracking this in the awesome-ipfs repo. Please see Awesome IPFS isn't awesome · Issue #420 · ipfs/awesome-ipfs · GitHub
With regards to the ecosystem page, I made a meta proposal to simplify the submission process.
The goal is to reduce some of the burden on us and ease the process of iterating and providing feedback to submitters.
Just for everyone’s info, I’ve made some significant progress automating things for awesome-ipfs. I plan to clean up the open PRs and issues so that we have a more hospitable repo prior to IPFS Camp. Be sure to subscribe to Awesome IPFS isn't awesome · Issue #420 · ipfs/awesome-ipfs · GitHub if you want to keep track of the improvements.
Awesome.
I was going to hack on it this weekend. Including that … well, the current structure is too complicated.
Will do it as PRs and see where I get to.
