Re: Request for Comment: Jenkins Code of Conduct

[Christopher Orr]

Hi there,

Thanks for the update!

While the Contributor Covenant seems reasonable, it also appears to be a
pretty generic template, and I find it leaves a lot of ambiguity that
could be expanded upon.

>From the first sentence, the Code of Conduct applies to "this project" —
which I would assume means Jenkins core, and I guess also its
infrastructure.  But that's not clear to me and, given that a large part
of Jenkins is its plugin ecosystem, I don't know where plugins, their
maintainers, and contributors fit into this.

"Project maintainers have the right and responsibility to ... ban
temporarily or permanently any contributor for other behaviors that they
deem inappropriate" — this reads as if any Jenkins core developer can
unilaterally ban somebody at any point based on their subjective opinion?

This seems out of place — I would expect only the board to have this
power, having followed the "Reporting" and "Handling of violations"
procedures mentioned later.

Similarly, "project spaces" is not further expanded upon — all jenkinsci
repos? jenkins-infra? plugin repos/wikis/websites?


I find the recently published Go Code of Conduct @
https://golang.org/conduct to be very clear about these points, as well
as approaching the entire topic from a more positive standpoint —
focussing more on the motivations, and the project's desired goals,
rather than sounding almost entirely negative.

In particular, I find the "Gopher values" are very well put, and cover
many of the topics that have come up on the Jenkins developers' mailing
list this year regarding being patient, thoughtful, and staying
constructive with criticism.

There is also a clear definition of what "project spaces" are, including
GitHub organisations, code review tools, a list of mailing lists and IRC
channels.  The statement about external groups and conferences is also
helpful, and would be useful for Jenkins given the growth of Jenkins
Area Meetups.

Reporting is covered slightly more in more depth, or at least the
timeline is a bit clearer than what we have at the moment, though the
Jenkins version does a good job about being clear on the possible
outcomes.  The change proposal process and summary at the end are also nice.

Anyway, for the Jenkins project, progress is certainly being made, and
thanks to Tyler for doing this! :)

Regards,
Chris


On 05/12/15 02:08, R. Tyler Croy wrote:
> As the Jenkins community has grown, it has become clear that we need to write
> down what behaviors  we welcome in our community, but more importantly, what 
> is
> not welcome.
> 
> I would like to invite you all to review and provide feedback on the following
> wiki page: 
> 
> 
> I take responsibility for the board dragging their feet on this topic and wish
> to remedy that as soon as possible. I cannot stress the importance of this
> topic enough and while I hope that we do not find ourselves in a position 
> which
> needs addressing, I believe it is critical to the long-term health of the
> Jenkins community that this be defined.
> 
> 
> If you have questions or concerns that you do not wish to advertise publicly,
> please email me off-list.
> 
> 
> 
> Cheers
> - R. Tyler Croy
> 
> --
>  Code: 
>   Chatter: 
> 
>   % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
> --
> 

-- 
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/5663013D.1080309%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: request hosting for plugin: meister

[Daniel Beck]

Given how generic the name is, could we rename the plugin (artifactId) to 
openmake-release-engineer, and the repo to openmake-release-engineer-plugin?

Additionally, the plugin description in the POM needs to be improved to 
actually explain what the plugin does.

On 05.12.2015, at 08:29, Baptiste Mathus  wrote:

> Done, welcome again!
> 
> As said before, again: beware to create the associated and compulsory wiki 
> page.
> 
> I'd also advise to update the README on the repo root to make it clearer it 
> contains a Jenkins plugin, and so on. There will an automated link from the 
> wiki page to that repo and people might get lost. It's generally also seen to 
> put there a link to the wiki page to make the bidirectional navigation easier.
> 
> See https://github.com/jenkinsci/meister-plugin
> 
> Cheers
> 
> 2015-12-04 20:54 GMT+01:00 Steve Taylor :
> Git Repository: https://github.com/OpenMake-Software/Meister.git
> 
> Plugin Directory under Git Repo:  jenkins/meister
> 
> Github UserName: sbtaylor15
> 
> Jenkins-CI UserName: sbtaylor15
> 
> Description:
> 
> Build Automation with integrated Continuous Integration
> 
> OpenMake Meister® delivers a highly reusable and accelerated build solution 
> that can quickly adapt to changing development demands. 
> It gives you control over the logic that drives your compile/link/archive 
> process and eliminates the need for one-off scripts that are brittle and 
> error prone. 
> It accelerates builds, relieves congestion, stores binaries and gathers 
> critical dependency information that can be used for release packaging. 
> OpenMake Meister can improve the functionality of any Continuous Integration 
> process and includes OpenMake Mojo. It supports incremental builds that 
> creates smaller, 
> less risky releases. Meister supports over 200 languages including Java, 
> .Net, C, C++, and database objects.
> 
> The Meister Jenkins Plugin will enable Jenkins to interact with OpenMake 
> Meister Workflows.  This interaction extends Jenkins to perform Builds on 
> Remote Server 
> Pools that include Load Balancing and on-demand provisioning.
> 
> -- 
> 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/cfac47ad-a32a-4d9d-a0be-1cde5dabf695%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
> 
> 
> 
> -- 
> Baptiste  MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
> 
> -- 
> 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/CANWgJS7cj7He1_Z-mG8%3DU13VD6X1Q-pGkfnPpaQDgw9YOmtkPw%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/E03D5BBD-9194-49C8-ACB3-D95394FD9720%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: request hosting for plugin: meister

[Baptiste Mathus]

+1 indeed, shoud've done that in the first place. Gonna rename just now.
Maybe meister is a bit less generic, but having the same issue.

2015-12-05 15:11 GMT+01:00 Daniel Beck :

> Given how generic the name is, could we rename the plugin (artifactId) to
> openmake-release-engineer, and the repo to openmake-release-engineer-plugin?
>
> Additionally, the plugin description in the POM needs to be improved to
> actually explain what the plugin does.
>
> On 05.12.2015, at 08:29, Baptiste Mathus  wrote:
>
> > Done, welcome again!
> >
> > As said before, again: beware to create the associated and compulsory
> wiki page.
> >
> > I'd also advise to update the README on the repo root to make it clearer
> it contains a Jenkins plugin, and so on. There will an automated link from
> the wiki page to that repo and people might get lost. It's generally also
> seen to put there a link to the wiki page to make the bidirectional
> navigation easier.
> >
> > See https://github.com/jenkinsci/meister-plugin
> >
> > Cheers
> >
> > 2015-12-04 20:54 GMT+01:00 Steve Taylor <
> steve.tay...@openmakesoftware.com>:
> > Git Repository: https://github.com/OpenMake-Software/Meister.git
> >
> > Plugin Directory under Git Repo:  jenkins/meister
> >
> > Github UserName: sbtaylor15
> >
> > Jenkins-CI UserName: sbtaylor15
> >
> > Description:
> >
> > Build Automation with integrated Continuous Integration
> >
> > OpenMake Meister® delivers a highly reusable and accelerated build
> solution that can quickly adapt to changing development demands.
> > It gives you control over the logic that drives your
> compile/link/archive process and eliminates the need for one-off scripts
> that are brittle and error prone.
> > It accelerates builds, relieves congestion, stores binaries and gathers
> critical dependency information that can be used for release packaging.
> > OpenMake Meister can improve the functionality of any Continuous
> Integration process and includes OpenMake Mojo. It supports incremental
> builds that creates smaller,
> > less risky releases. Meister supports over 200 languages including Java,
> .Net, C, C++, and database objects.
> >
> > The Meister Jenkins Plugin will enable Jenkins to interact with OpenMake
> Meister Workflows.  This interaction extends Jenkins to perform Builds on
> Remote Server
> > Pools that include Load Balancing and on-demand provisioning.
> >
> > --
> > 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/cfac47ad-a32a-4d9d-a0be-1cde5dabf695%40googlegroups.com
> .
> > For more options, visit https://groups.google.com/d/optout.
> >
> >
> >
> > --
> > Baptiste  MATHUS - http://batmat.net
> > Sauvez un arbre,
> > Mangez un castor !
> >
> > --
> > 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/CANWgJS7cj7He1_Z-mG8%3DU13VD6X1Q-pGkfnPpaQDgw9YOmtkPw%40mail.gmail.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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/E03D5BBD-9194-49C8-ACB3-D95394FD9720%40beckweb.net
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Baptiste  MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

-- 
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/CANWgJS5fSyVuLFDeTYxNurHmpzk%3DB61Qa9Bp%2BVGpiGNZBb0swg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request for Comment: Jenkins Code of Conduct

[Christopher Orr]

On 05/12/15 16:22, Christopher Orr wrote:
> Similarly, "project spaces" is not further expanded upon — all jenkinsci
> repos? jenkins-infra? plugin repos/wikis/websites?

My previous email was a bit long, so I wanted to try and list the spaces
that I could think of, where it seems that adherence to a Code of
Conduct should probably be encouraged for participants:

Source control
- GitHub commits, PRs, issues, wikis
  - jenkinsci
- i.e. core, misc repos, plus all hosted plugins
  - jenkins-infra
  - jenkinsci-cert
- SVN commits [assuming SVN isn't read-only]
  - svn.jenkins-ci.org

Websites
- Everything hosted on jenkins-ci.org and its subdomains, including:
  - Issue tracker
  - Wiki page content
  - Wiki comments (we could simplify by finally disabling this ;)
  - Blog post comments

Mailing lists
- https://jenkins-ci.org/content/mailing-lists
- http://lists.jenkins-ci.org/mailman/listinfo

IRC channels
- #jenkins
- #jenkins-meeting
- #jenkins-infra
- #jenkins-community

Online events, e.g. Hangouts
- Office Hours


The Jenkins project is pretty big! :)

Regards,
Chris

-- 
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/566308BC.3050400%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: request hosting for plugin: copado-jenkins-plugin

[Federico Larsen]

please ignore may previous email. I do have commit access.
sorry for the confusion.
kind regards.-

On Sat, Dec 5, 2015 at 11:20 AM, Federico Larsen  wrote:

> Hi Baptise,
>
> I didn't get commit access to the repo. My github id is: larsenfed
>
> Thanks in advance for your help.
> Kind regards.
> Done: https://github.com/jenkinsci/copado-plugin
>
> Beware to create the associated wiki page + update the pom.xml/url tag to
> point to it.
> Plugins without a wiki are very soon gonna be made invisible from the
> update center.
>
> Welcome aboard!
>
> 2015-12-04 20:21 GMT+01:00 Federico Larsen :
>
>> Hi there,
>>
>> Please find the requested plugin information below.
>>
>>
>>- The URL to your finished plugin repository on GitHub:
>>https://github.com/CopadoSolutions/copado-jenkins-plugin
>>- Your personal GitHub username: larsenfed
>>- Your jenkins-ci.org: larsenfed
>>- With this plugin you can add a build step to your Jenkins project
>>that executes a Copado job, using the Copado Webhook API
>>. This is the only plugin for Copado.
>>(Copado is the leading Salesforce.com deployment tool. see
>>http://www.copa.do)
>>
>> Many thanks in advance for your help.
>>
>> --
>> 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/b53a26ea-c5ee-424c-ae84-605c880ba7c3%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Baptiste  MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
>
> --
> 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/CANWgJS4m%2BDsGQTYsLx9rkJqxge3Oot4BKuVEQingKmFa5vTXnA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Federico Larsen
www.copa.do

-- 
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/CANAmHvnvdwsF_oKJbxK_Y0ywZ8-eCcfy0O8P5nBmxnj0%2B75yfQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fail to get updates from http://updates.jenkins-ci.org/update-center.json

[Christoph Obexer]

In case anyone considers working on this please also consider 
https://issues.jenkins-ci.org/browse/JENKINS-26231 :)

Thanks! Br,
Christoph

On Friday, December 4, 2015 at 10:04:39 PM UTC+1, Richard Bywater wrote:
>
> Can I suggest we change the content type to application/javascript then at 
> least so at least one part is correct? :) (if it doesn't break anything 
> obviously)
>
> Richard 
>
> On Sat, 5 Dec 2015 5:04 am 'Jesse Glick' via Jenkins Developers <
> jenkin...@googlegroups.com > wrote:
>
>> On Fri, Dec 4, 2015 at 4:48 AM, Richard Bywater > > wrote:
>> > is it documented why it advertises itself as JSON but actually isn't?
>>
>> It is JSONP. Yes it should have been named `update-center.js` to
>> match, but existing Jenkins installations expect JSONP from this URL
>> so it is too late to change it.
>>
>> (BTW the use of JSONP is actually doubly obsolete. First we deprecated
>> that URL; `update-center.json.html` is an HTML wrapper using
>> `window.postback`, the more modern way of doing this. Then we stopped
>> downloading UC content from the browser by default anyway—now unless
>> you configure otherwise, the Jenkins master does the download, and
>> just strips out the JSONP header and footer. Ideally we would
>> introduce a *third* URL that was actually JSON, for use with current
>> releases, but all the moving parts in various implementations of the
>> update center backend make this a painful task.)
>>
>> --
>> 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-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3jX7nTCuuLsHGjqgJdykspTzFGwLsgDwv5VOeqiYg%2BVA%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/76506cee-4031-4be6-9afc-c6f897915760%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: request hosting for plugin: copado-jenkins-plugin

[Federico Larsen]

Hi Baptise,

I didn't get commit access to the repo. My github id is: larsenfed

Thanks in advance for your help.
Kind regards.
Done: https://github.com/jenkinsci/copado-plugin

Beware to create the associated wiki page + update the pom.xml/url tag to
point to it.
Plugins without a wiki are very soon gonna be made invisible from the
update center.

Welcome aboard!

2015-12-04 20:21 GMT+01:00 Federico Larsen :

> Hi there,
>
> Please find the requested plugin information below.
>
>
>- The URL to your finished plugin repository on GitHub:
>https://github.com/CopadoSolutions/copado-jenkins-plugin
>- Your personal GitHub username: larsenfed
>- Your jenkins-ci.org: larsenfed
>- With this plugin you can add a build step to your Jenkins project
>that executes a Copado job, using the Copado Webhook API
>. This is the only plugin for Copado.
>(Copado is the leading Salesforce.com deployment tool. see
>http://www.copa.do)
>
> Many thanks in advance for your help.
>
> --
> 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/b53a26ea-c5ee-424c-ae84-605c880ba7c3%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Baptiste  MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

-- 
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/CANWgJS4m%2BDsGQTYsLx9rkJqxge3Oot4BKuVEQingKmFa5vTXnA%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANAmHvmc76PMcsB_08M3f%3DGER7DZ4n2Ys8ufJyRj1jCwqtTEVA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

New plugin hosting request

[Sanketh P B]

Dear Team, 

Please find the new plugin details below. 

GitHub url: https://github.com/sankethpb/assemblyInfo-updater 
Name of plugin: assemblyInfo-updater 
GitHub username and jenkins-ci.org user name: sankethpb 
Description: Provides a build step to update file version, product version and 
copyright info for AssemblyInfo.cpp , AssemblyInfo.cs and resource files. 

Kindly provide the required access to host this plugin. 

Thanks, 
Sanketh 

-- 
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/832cd113-7113-4db9-a26c-dd58a1260539%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.