Submitted by christ66 on Thu, 2014-06-05 18:35
Let me start by introducing myself, my name is Steven Christou. Many of you might know me on IRC as schristou, my github id as christ66, or my twitter handle @schristou88. In Jenkins, I am currently working on some significant improvements to the subversion-plugin, along with various random bug fixes. I am also the current maintainer of Cobertura, an open source code coverage tool for java. Prior to working on Jenkins, I was working on Hudson at the Eclipse Foundation.
Only a few weeks until our Jenkins User Conference US East kicks off in Boston on June 18. Right now more than 300 people have registered and we’ve had to release more tickets! If you will be anywhere near New England on June 18, sign up fast so you don’t miss the fun.
Jenkins won SDTimes 100, 2014
For the 5th year in a row, Jenkins project won SDTimes 100, 2014 this year under DevOps and SCM categories, along with other open-source projects like Chef, Docker, Git, LLVM, and Puppet.
I'd like to take this opportunity to once again thank the community for keeing us going strong. There's a lot of interesting efforts going on in the project, as always, so expect more stuff to come out from us in the coming days!
Today on IRC, I was asked how someone new to the project can get started working on Jenkins, when s/he has no particular preference or pet-peeve.
This is a good question for which the project should have a canned answer ready, so here is one approach — adopt a plugin!
Often, a Jenkins plugin gets developed by someone to scratch his own itch. That person shares the plugin with the community, and since it does everything he needs, he moves on to work on something else. Then another person starts using that plugin, comes up with an idea for improvement, implements that, and then moves on. Given that we have more than 900 plugins today, there are a plenty of plugins that are currently co-maintained by the community, which could really use a focused loving caregiver.