Hello Everyone / Fellow Jenkins Core-/Plugin-developers! What are your thoughts on Jenkins, GitHub and Gerrit? I've been discussing Gerrit to GitHub: Ideas and Actions with the Gerrit community at https://groups.google.com/forum/#!msg/repo-discuss/rersrCtdEiY/usAodLofFo8J
Since Gerrit workflows often need Jenkins, I thought more about ecosystems of Jenkins, GitHub and Gerrit... For example, my personal feeling of the unintentional irony(?) that our gerrit-trigger-plugin is using Github pull requests instead of Gerrit? +CC Robert Sandell and Tomas Westling because I'm referencing a plugin that they co-maintain, and they may have thoughts on this. In a big picture view, I believe GitHub pull requests are working well for our Jenkins community -- because we've come to value: - People over Process - Actions over Plans - Continuous over Discrete Staging - Distributed/Forking over Centralization/Federalization - Plugins over Core Interestingly, our Jenkins community seems to adhere to several values in the Manifesto for Agile Software Development at http://agilemanifesto.org/ As of today (May 31, 2012) I'm not foreseeing significant value proposition nor positive return on investment in using Gerrit (in spite of its features) in lively open source projects and communities such as our Jenkins, especially when GitHub pull requests (distributed/forking) with periodic reminders on this mailing list (centralization/federalization) are working well for us. Of course, I could be missing a piece of a larger puzzle, hence I'm asking you these questions: Would each of you agree with me? What are your thoughts and/or opinions? Thank you, Lloyd
