> 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'.
https://github.com/jenkinsci/ant-plugin BTW, there're some core-related issues, hence I propose to use the "Untriaged" state to review issues 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 agree, the GitHub repos renaming is not a part of the thread. Just an off-topic... The renaming was a non-recommended operation on GitHub for a long time, but seems it works well now. "In addition to redirecting web traffic, all git clone, git fetch, or git push operations targeting the previous location will continue to function as if made on the new location" ( https://help.github.com/articles/renaming-a-repository). Seems that renaming is safe for users and automation flows. We could try the renaming on several unpopular plugins like *junit-realtime-test-reporter*. We could also fork a repo according to comments from Alex, but all user forks will reference the initial repo => there will be additional efforts to adjust the security and to handle pull-requests to legacy repositories. The renaming seems to be preferable if it works well. 2014-06-10 1:16 GMT+04:00 Daniel Beck <m...@beckweb.net>: > 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 a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/luOqm4Qj4sc/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > jenkinsci-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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. For more options, visit https://groups.google.com/d/optout.
