Request to join organization

[fjfer...@cloudbees.com]

Hi all,

I am Francisco Javier Fernández González, currently engineer at CloudBees. During the last year I've been collaborating with some work of the community, becoming co-maintainer of the Jenkinsfile-runner project with Oleg Nenashev and Evaristo Gutiérrez, and maintainer of Folders plugin. I would like to continue collaborating in the maintenance of Jenkins and its ecosystem of plugins, and in terms of easing my collaborations and reviews, I would like to become a member of the organization getting the merge permissions for the core. Would it be possible?

Just in case you're interested in knowing more from me:

• My Jenkins JIRA user is fcojfernandez
• My github user is fcojfernandez
• My contributions to the jenkinsci organization: https://github.com/pulls?utf8=%E2%9C%93&q=is%3Apr+author%3Afcojfernandez+archived%3Afalse+user%3Ajenkinsci+
• Specific contributions to jenkins-core: https://github.com/jenkinsci/jenkins/pulls?utf8=%E2%9C%93&q=is%3Apr+author%3Afcojfernandez+

Best Regards!

[Baptiste Mathus]

+1 from me.

--
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/3a997e95-4d44-4933-bc9e-a92c1a574644%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jeff Thompson]

+1 from me.

Fran does good work and granting him the permissions will help get more productive stuff done in Jenkins.

Jeff Thompson

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS6mb7ztsLXZ4306XN%2B-%2BcOriAZqnZJ5-XdDoL-rs-cCMg%40mail.gmail.com.

[Daniel Beck]

I discussed this request with Fran out of band, and asked about some common issues causing problems in core maintenance, like ensuring new API is deliberate or @Restricted, or the need to keep binary (and to a lesser extent source) compatibility. With his background in preparing CloudBees product releases and ensuring tests run successfully (many of his past contributions) he's very familiar with the latter. The former should just be automated, but while we don't have that, I'll make sure he understands the requirements to not accidentally introduce new APIs.

I am in support of this request.