Add the asdf-community information to the README about asdf-plugins HOT 4 CLOSED

@imbsky I'm am fine with that, so long as it is clear that it's not a responsibility of the core team and that plugins made available don't necessarily comply with all of the core teams guidelines for plugins.

from asdf-plugins.

closed in #180

I will also note here that I really dislike the whole plugin repo mechanism of asdf and would love to remove the asdf plugin add <name> shorthand functionality. asdf plugin add <name> <git-ref> with search built into the core is a much better solution. I will propose a solution in the core.

from asdf-plugins.

I'm honestly not a huge fan of the asdf-plugins repository (and the associated plugin-add function that pulls from it), simply because it has created additional work for us on the core team. I'm all for having independent indexes/repos of plugins maintained and curated by asdf-users as that will reduce our responsibilities.

from asdf-plugins.

Thank you. Yes, I have the exact same opinion. Since I'm both an OCaml programmer and a Void Linux user, I'm going to give some examples related to them, it's definitely better to manage plugins in a way like opam-repository and void-packages. I thoguht it difficult to do in asdf because of the historical problems, so I started a community project, which would be the great if it could be managed in those ways.

from asdf-plugins.