I strongly recognize both that I share the "community-centric view" and that I disagree with the "maintainer view"https://medium.com/@mikeal/maintainer-vs-community-97edc28387ad …
-
-
the more flexibility you have to spend on pure community work the more compelled you are to grease the squeaky wheels nobody else can.
-
yeah. My biggest mistakes on OSS have been under-investing in community empowerment. No amount of community empowerment is too much ime.
-
mine is similar but basically the same, not realizing when i needed to intervene to empower people to take on leadership.
-
I find that setting up 'quests' where maintainers write down the details of doing some small-but-annoying task pays massive dividends.
-
that's a very good idea, i'm going to steal that :)
-
I call them "quest issues" https://www.google.com/search?q=ember+quest+issue&rlz=1C1CHBF_enUS725US726&oq=ember+quest+issue&aqs=chrome..69i57j69i59j69i60l3j69i65.1656j0j7&sourceid=chrome&ie=UTF-8 … the original: https://github.com/emberjs/ember.js/issues/13127 … ; one from Rust: http://www.jonathanturner.org/2016/08/helping-out-with-rust-errors.html …
-
the key is finding issues that are outside the scope of automation, but which people think "the community can't do" because of some 1/
-
some quality control that, if you think about it, can be written down. Writing it down is good anyway, and the dividends are huge. 2/2
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.