We don’t want to “clutter” this repo with code anymore. Authors should maintain the code in their own repos and publish them to the Cordova Plugin Registry.

Having the plugins in separate repos also enables less clutter for pull requests and bugs, with it all being in one repo it is hard to get attention for an issue since that can be buried. I know that I like to fix some of my plugins, but it’s hard with it all lumped in there with other unrelated plugin issues.

In an ideal world, we would migrate them all, but that is not feasible. Firstly, the code is contributed – and tracking down all the authors to either release them under Apache v2 license etc is just a thing that we don’t want to do. We just don’t have the people for this, doing it for each plugin. What is feasible is — and we need the community to respond — targeting the few plugins that the community really uses, and migrate those, and handle all the overhead needed before “taking it as our own” (whether Apache, or Adobe, etc).

Lastly, owning the code is a big responsibility in testing (with multiple iOS, Android versions) and maintenance, and is not a something with zero cost — what with all the core committers etc busy with maintaining the core code and core plugins as well.

Is there a quick and dirty method of adding a signpost to the repo for a plugin (similar to how we used the README in the old repo)?

The Plugman interface seems like a learning curve which I don’t currently have the time to understand. With the old repo now depreciated, I assume I need to register the Plugin into the Cordova registry otherwise no-one is ever going to find the Plugin again – thus I’m looking for the simplest path to achieve that.