-
Notifications
You must be signed in to change notification settings - Fork 529
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify policy around content/data - "built with" vs "published on" #323
Comments
I think we should reevaluate the categories: -Services build with IPFS somewhere in the background, as 'honorable mention', like Filecoin, Cloudflare-IPFS-Gateway etc. -Open Source Applications/Services you can run yourself and extend the functionality of IPFS. -Datasets you can help to provide, which are explained to be static -Collab-Clusters which you can help to spread, which are explained to be dynamic -Ressources like Videos, How-Tos, Guides, Documentations, Toolsets etc. -News Articles (of third parties) covering IPFS directly or a specific service/application running with IPFS in the background. |
And we should add a hint that everything found not working for 4 weeks will be removed again. On software: No development activity for 6 month while no stable has been released. We have definitely an issue with old stuff collecting in the index. |
Thanks @RubenKelevra for the feedback - those should be part of different issues however. Feel free to file separately. This is solely for the built-with vs content question. |
Thanks, I've created #330 :) |
This has been filed separately as #325 |
I'm going to close this and move the discussion into #367 -- that issue is focusing on what questions go into a "submit your thing" form, and the issue of built with/published on essentially starts there. |
In #150 we landed a policy for evaluating submissions for what will be added to the site.
While the language makes a clear distinction between IPFS vs other projects (libp2p, Filecoin, etc), it doesn't make a distinction between content published on IPFS vs things built with IPFS.
While significant and large datasets seem ok, I'm less sure about the value of individual pieces of media being listed only because they are published on IPFS.
Thoughts?
The text was updated successfully, but these errors were encountered: