-
Notifications
You must be signed in to change notification settings - Fork 6
Improve dat-awesome page #68
Comments
Hi @joehand I created a draft of how a new Awesome list could look like. It should also clarify the relation of the various ecosystem projects to the Dat Project. Done some first paragraphs to get an impression. If you like it, I'll continue and PR. See: |
@clkao hey i wonder if you have any time to look into this for a second? it might be as easy as deleting your repo if you don't feel like maintaining it anymore. |
I think that would be best. Having 2 awesome's around is confusing. The one that exists in datproject org is most logical one to maintain. |
versus for
@Karissa I would also remove |
@Karissa @joehand the new awesome list is ready: https://github.com/aschrijver/awesome-dat/blob/fresh/awesome/readme.md Took quite a bit of time, but I looked up all repositories to see if descriptions were accurate, etc. Tried to make it as less confusing as possible :) There are some similar-looking, overlapping modules. |
Sure, I can remove my outdated one. Actually it might be better if I update the README to point to the up-to-date one. Should the one under datproject or the one @aschrijver created be canonical? |
Hi @clkao thanks. Its the datproject list that is the real thing. My PR has just been merged on that one and i will remove the fork. |
PS i would remove the entire repo. Better than outdated one with a redirect link.. |
https://github.com/datproject/awesome-dat is now updated and I detached it from the fork, closing. |
(NOTE This proposal is part 1b of Positioning, vision and future direction of the Dat Project)
If I am correct the Dat Project uses the official awesome-dat page to introduce people to the ecosystem and community projects.
Yet this page is a fork of the unmaintained https://github.com/clkao/awesome-dat, is itself not updated for 7 months and has a 6 month old PR that is not responded to.
In other issues we talked about the Dat ecosystem being hard to discover for newcomers. Having a good, up-to-date awesome page is a great tool to help with that, imho.
I would:
Next part: Improving the dat project repository organization
The text was updated successfully, but these errors were encountered: