As discussed at the contributor summit, I am totally in favor of opening the GitHub issues a bit more, and maybe even making it default for new plugins. Thanks Tim for starting thus thread!
Regarding the implementation, my proposal would be to firstly add explicit issue tracker links on the plugin site. Maven metadata already supports it, we just need to expose it in the update center. Then we could, for example, keep components and use a Jira bot when an issue is misreported. Just removing a component will have limited impact, because many components are often not reported to a right component anyway (triage is needed, or users just report it wrongly). Removing components is likely to encourage people to take another random component or _unsorted -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/fb498730-4b7c-498e-9f09-46bd6e95805b%40googlegroups.com.
