Ecosystem issues and a corresponding dev

[AlexDaniel]

There are three tickets related to the ecosystem that are currently labeled with fallback (a label for tickets that don't fall into any other existing category):

• Metadata licenses should be required before adding new modules to ecosystem #19
• Ecosystem: should we strive for integration with MetaCPAN #26
• Ecosystem content, quality and fragmentation issues. #39

As I mentioned before, I think we need a new label ecosystem as well as a dev who will be looking after the tickets and driving the progress in that area (current list).

Personally I think @ugexe is the best candidate, and I highly recommend them to apply. Meanwhile others can also do so if they feel strongly about it.

[ugexe]

I will do it. But I'm also busy and lazy and thus don't know when I'll feel like writing up an application. If someone wants to do that for me it will leave me more time for digesting and responding to the issues.

[AlexDaniel]

@ugexe Good! Can you file a PR adding yourself to the list? (example). It doesn't mean that you should do all the work, rather that there's a defined person who is knowledgeable enough to help and guide others when needed. If there are any specific things (e.g. projects) you want to get done but can't due to your time restrictions, please file separate tickets here. Either someone will pick it up, or we'd at least have a nice list of things to work on for the next GSoC.

After the PR is merged we'd be able to label a few tickets appropriately (I prefer not to have orphaned labels).