Ant is not in a plugin, so renaming 'ant' to 'ant-plugin' would just be confusing. The same applies to 'cli' -- they are both (currently) part of jenkins.war, so should probably be merged into 'core'.
>> - I added a list of plugin components missing the usual comment to indicate >> they're a plugin. This might well be obsolete with the "-plugin" rename, in >> which case all plugin components should have their (then redundant) >> descriptions removed to keep the components list clean (and a description >> should be mandatory for all components that aren't plugins). > Thanks! Unfortunately, we cannot just rename GitHub repositories That's about Jira, not Github. It seems that plugin component names in Jira by convention have a description containing 'plugin', see https://issues.jenkins-ci.org/browse/JENKINS#selectedTab=com.atlassian.jira.plugin.system.project%3Acomponents-panel -- but some are exceptions, and that's what that is about. Also, GitHub repos can be renamed -- I've done it. Is there a restriction (e.g. only repos that are not yet an certain age, or not too popular, ...) or why do you write we cannot do that? > I think the "Untriaged" state part needs more explanation and attention, > .... This is a metric we can track to identify plugins that need love, > and measure how far behind we've fallen in the core. We should also look into changing the description, as it specifically refers to security issues (as does 'Fix Prepared'). No idea whether this is configurable. > * IRC Bot (?): Ensure that new plugin repositories have the "-plugin" > suffix Probably sufficient to add a note on http://wiki.jenkins-ci.org/display/JENKINS/IRC+Bot how to name plugin repos. -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
