I gave commit rights to someone I didn't know
jakewins.com
I gave commit rights to someone I didn't know
1–10 of 106 posts
Re: I gave commit rights to someone I didn't know
#2This is awesome!
seeing something stay alive live this and grow due to people liking it
Re: I gave commit rights to someone I didn't know
#3This concept awesome and already have a name. It's called Open Open Source: http://openopensource.org
It's especially essential when managing a high volume of open source projects on GitHub.
Re: I gave commit rights to someone I didn't know
#4Same thing happened to me: I wrote the module that does Microsoft Office files in Python. At the time, the solutions for doing it in Python were 'talk to some Java library' or 'talk to some .net library'. I read the openxml spec and made something which did basic creation, extracting text, modifying docs.
I totally didn't have time to maintain it, then Scanny took over. It's now hugely popular, the code handles non-Word OpenXML docs, and most of the code has been added or refactored under Scanny.
Re: I gave commit rights to someone I didn't know
#5> I don’t recall the author now, but the gist of the argument made was that we’re too protective of our code - if you give someone responsibility, show that you trust them, more often than not, your intuition about people abusing their freedom is way off.
Maybe it was some of Pieter Hintjens writing and/or the C4 process:
* https://rfc.zeromq.org/spec:42/C4/
* http://hintjens.com/blog:112
* http://hintjens.com/blog:106
Edit: oh, as the author mentions a blog post from 2012, it probably isn't any of the above posts (which are newer) but maybe something related to C4.
Re: I gave commit rights to someone I didn't know
#6[deleted]
Re: I gave commit rights to someone I didn't know
#7> I don’t recall the author now, but the gist of the argument made was that we’re too protective of our code - if you give someone responsibility, show that you trust them, more often than not, your intuition about people abusing their freedom is way off. Maybe it was some of Pieter Hintjens writing and/or the C4 process: * https://rfc.zeromq.org/spec:42/C4/ * http://hintjens.com/blog:112 * http://hintjens.com/blog:1…
Hentjens' "Social Architecture" book goes into the same topic in more detail, and is freely available here: https://hintjens.gitbooks.io/social-architecture/content/
Re: I gave commit rights to someone I didn't know
#8I did something similar with a project I lost interest in several years ago (https://github.com/dbfit/dbfit - table-oriented database unit testing). Just gave over commit rights, and there's a whole bunch of people writing code for it and maintaining it now, still going strong. I occasionally look at the github repo, and always end up amazed how much it's moved on.
Re: I gave commit rights to someone I didn't know
#9> I don’t recall the author now, but the gist of the argument made was that we’re too protective of our code - if you give someone responsibility, show that you trust them, more often than not, your intuition about people abusing their freedom is way off. Maybe it was some of Pieter Hintjens writing and/or the C4 process: * https://rfc.zeromq.org/spec:42/C4/ * http://hintjens.com/blog:112 * http://hintjens.com/blog:1…
Re: I gave commit rights to someone I didn't know
#10Yep, something similar happened to me - I released what is now https://github.com/punker76/gong-wpf-dragdrop on google code in 2009 (I think) then pretty much lost interest. Forward on a few years and @punker76 had uploaded it to github, and continued working on it. It was a strange feeling when I first became aware of the fork - like seeing an inanimate object come to life.