I'll try to rename the repo tomorrow. I realized that IRC bot does not 
provide such command, so I'll ask somebody with proper permissions on the 
GitHub org.

среда, 2 сентября 2015 г., 22:33:40 UTC+3 пользователь Andrey Stroilov 
написал:
>
> Hi Oleg,
>
> Sorry, I wasn't sufficiently specific - with the git-notes plugin, we 
> would prefer to maintain the "google-" prefix. Can we add that to the repo 
> name?
> I received the invite; I'll begin transferring the code. Thanks!
>
> On Wednesday, September 2, 2015 at 1:48:11 AM UTC-7, Oleg Nenashev wrote:
>>
>> Hi Andrey,
>>
>> 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. 
>>
>>
>> From my POV "cloud" is related to the Google Cloud service, with which 
>> the plugins are being integrated. I agree that the name may have a double 
>> meaning, but hopefully the documentation will clarify it.
>>
>> According to your comment, I'm going to proceed with the "cloud" prefix.  
>> BTW we can rename repos before the release if we decide to do it..
>>
>> Would you like us to update code before or after the new repos are 
>>> created?
>>
>>
>> You can do it later before the release. New repos are: 
>>
>>    - https://github.com/jenkinsci/google-cloud-health-check-plugin 
>>    - https://github.com/jenkinsci/google-cloud-backup-plugin
>>    - https://github.com/jenkinsci/git-notes-publisher-plugin
>>    - https://github.com/jenkinsci/google-analytics-usage-reporter-plugin
>>    
>> You should get an invitation to the jenkinsci organization to your inbox.
>>
>> Best regards,
>> Oleg
>>  
>>
>> 2015-09-02 1:50 GMT+03:00 Andrey Stroilov <[email protected]>:
>>
>>> 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 a topic in the 
>>> Google Groups "Jenkins Developers" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/jenkinsci-dev/lAk9JsXWQL0/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> [email protected].
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/ebd57461-c5f0-4e1b-9699-30b189ac77dd%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/ebd57461-c5f0-4e1b-9699-30b189ac77dd%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>> 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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/b2b983ad-ad4d-40de-a3aa-6e237cdc2f65%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to