I suppose these numbers are nothing to brag about when we have folks from all the big projects in this conference, but for a project that somebody started without a corporate backing, with relatively niche user base, I think this is pretty good.
There’s all the usual things, but there’s something more, too. That’s what I wanted to talk about.
Lead in: so what are those key ingredients that we put into the Jenkins project? It starts with the realization that…
I mean, it takes some special mindset to love hacking code for free.
Heterogeneousness example:Bugs in bugzillaMedia objects in iTunesDocument types in Google DocsAnywhere where you see a list
Remember the question I asked earlier; now we are ready to answer this question
While silo is often talked as a bad example of everyone heads down into their little corner of the problem without a broad picture, but …
Those obstacles for more scalability become far more evident when you work on multiple modules, because they are no longer one-off problems. Because core developers also must work on modules, module developers’ pain point becomes core developers’ pain point.
But silo alone does not form a community. If everyone minds his own business and if that’s all they do, you don’t end up accumulating critical mass anywhere.A good example of this is custom Ant tasks. It’s done all over the places, and not much sharing and talking going on.
Someone please do IRC 2.0! Or maybe the barrier to entry is serving as a signal/noise filter. I dunno.