Different ways to lead an open source project
Just a few lines, to trigger the discussion... to describe my point, I will pick two projects I have contributed (and I want to contribute even more):
Some months ago, Brian Granger, a core developer from the
IPython project gave a talk at
SciPy 2013 where he said:
Make features fight hard to be accepted and implemented. Communicate to the community and developers that the default answer to new feature requests is no (it's not personal!). Don't even consider implementation until the much of the community is crying "we absolutely must have this."
Some days ago, Roberto Alsina, a core developer from the
Nikola project made a blog post where he said:
If you propose something you are getting heard and I am giving the proposal a fair shake. I may reject it, but not out of hand, but instead after some thought. And if I am unsure, it’s accepted. I would rather get something I am not fond of than drive out a contributor because I may change my mind, but a contributor that’s gone is not coming back.
Both projects are very successful, however they seems to go in opposite directions in the way they deal with features and contributors.
Probably they are living in different "times"... I mean, I see a "pattern" here:
Nikola, the younger, is toward the "left" side, embracing the "radical" view of the “universe”, whereas
IPython, the older, is toward the "right" side, embracing the "conservative" view...
Let me be clear, I am not saying anything about the political ideas of those developers, I do not even know their political ideas... I just described a pattern I saw before with people, but it seems to be also relevant for open source projects.
I will probably write more about that, but I would like to know you ideas ;-)
Like I said at the beginning, just a few lines, to trigger the discussion...
Don't forget this blog post is an ipynb file itself! So, you can download it from the "Source" link at the top of the post if you want to play with it ;-)Comments powered by Disqus