Re: [Proposal] Transfer of CloudBees-community/syslog-java-client to jenkinsci Github org

['Michaël Pailloncy' via Jenkins Developers]

Hi all - I'm checking this internally and will come back to you as soon as 
I have an answer. Thanks

On Thursday, March 31, 2022 at 9:25:00 AM UTC+2 cyrille...@elastic.co wrote:

> Keeping the same groupId would definitively be the best solution. Let's 
> see what's CloudBees' answer.
>
> Cyrille
> On Wednesday, March 30, 2022 at 8:02:43 AM UTC+2 m...@basilcrow.com wrote:
>
>> Hi Cyrille, 
>>
>> On Wed, Mar 23, 2022 at 3:39 AM 'Cyrille Le Clerc' via Jenkins 
>> Developers  wrote: 
>> > I would definitely be interested in publishing the syslog-java-client 
>> library to Maven Central from non Jenkins project to easily consume the 
>> library. 
>>
>> Great! 
>>
>> > My understanding of the Sonatype OSS publishing process is that one can 
>> only publish on a groupId he is legitimate for which probably means that 
>> the Jenkins Community will not been authorized to publish an artifact under 
>> the "com.cloudbees" groupId and will probably require to rename the groupId 
>> from "com.cloudbees" to "io.jenkins.***". 
>>
>> Based on my reading of the Sonatype documentation, I think your 
>> understanding is correct, but I would not necessarily assume that the 
>> use of the "com.cloudbees" namespace by the Jenkins project for such 
>> legacy libraries is forbidden. I think that is an open question that 
>> we could pose to CloudBees management, and in particular Michaël 
>> Pailloncy (who started this discussion). Non-technical matters aside, 
>> the technical cost to CloudBees would be small (assisting with 
>> Sonatype verification), while the technical benefit to users would be 
>> large (avoiding a migration of Maven group ID for all consumers of 
>> this library), so I think it is at least worth asking. If the answer 
>> is no, fine - we can switch the group ID to "io.jenkins", open a help 
>> desk ticket with the Jenkins infrastructure team to assist with the 
>> Sonatype verification, and ask all downstream consumers to change 
>> group IDs. I have no strong preference either way. 
>>
>> Best regards, 
>> Basil 
>>
>

-- 
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/503e3346-8d94-4b83-a63f-2b44f0aea618n%40googlegroups.com.

Re: [Proposal] Transfer of CloudBees-community/syslog-java-client to jenkinsci Github org

['Michaël Pailloncy' via Jenkins Developers]

Thanks all! 
FYI The repository has been 
transferred: https://github.com/jenkinsci/syslog-java-client

Michaël

On Wednesday, March 16, 2022 at 12:13:02 AM UTC+1 m...@basilcrow.com wrote:

> On Tue, Mar 15, 2022 at 11:00 AM 'Cyrille Le Clerc' via Jenkins 
> Developers  wrote: 
> > Did you consider publishing exclusively to Jenkins' own maven 
> repository? 
>
> I have configured the repositories we have transferred already, like 
> Mock JavaMail and File Leak Detector, to publish exclusively to the 
> Jenkins project's Artifactory server. This is the path of least 
> resistance, as it allows us to reuse existing infrastructure. Projects 
> that are only consumed by the Jenkins community will have no issue 
> with this. Projects that are consumed outside of the Jenkins community 
> need to adjust their build to add the Jenkins project's Artifactory 
> server. I think this is a reasonable burden to bear in exchange for 
> the infrastructure provided by the Jenkins project, but if somebody 
> feels strongly otherwise they can always set up releases to e.g. Maven 
> Central. My plan for syslog-java-client was to follow the existing 
> pattern and publish new releases exclusively to the Jenkins project's 
> Artifactory server. 
>

-- 
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/62da131b-2db7-42c8-bf06-1d6ad0575a2en%40googlegroups.com.

[Proposal] Transfer of CloudBees-community/syslog-java-client to jenkinsci Github org

['Michaël Pailloncy' via Jenkins Developers]

Hi all,

CloudBees would like to propose a transfer of 
CloudBees-community/syslog-java-client 
 to 
the jenkinsci Github organization.
This project is currently used by the following projects 
, 
including:

   - jenkinsci/audit-trail-plugin 
   
   - jenkinsci/logstash-plugin 
   
   - jenkinsci/configurationslicing-plugin 
   
   
The reasoning behind this proposal is to let this project benefit from the 
infrastructure and processes of the Jenkins project.   

Please let me know your thoughts on this, and if everyone agrees, how you 
would like to proceed.

Thanks
---
Michaël Pailloncy

-- 
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/137ae02a-6a38-4ec4-9e5d-62dcc728b623n%40googlegroups.com.