Generally speaking, whether or not we put in the "cloud" prefix, those names would be fine. Would you like us to update code before or after the new repos are created?
On Tuesday, September 1, 2015 at 1:45:39 PM UTC-7, Andrey Stroilov wrote: > > On Sunday, August 30, 2015 at 2:58:33 AM UTC-7, Oleg Nenashev wrote: >> >> I think that all plugins should be renamed to make them self-describable. >> I would update prefixes in order to reference the product. Examples: >> >> - google-cloud-health-check >> - google-cloud-backup >> - (google-?) git-notes-publisher (seems to be unrelated to Google, >> but sometimes companies use such approach for branding) >> - google-analytics-usage-reporter >> >> >> > Hi Oleg, > > For the first two plugins: while they're designed to work well with the > Cloud platform, they are not strictly cloud-only plugins; for example, > someone could use the backup plugin on a local jenkins instance. Do you > still think it should have the "cloud" prefix in the name when it's not > restricted to those use cases? > -- 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/ebd57461-c5f0-4e1b-9699-30b189ac77dd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
