I see! Fair enough, it was more of a curiosity question to be honest. It's always nicer to have more people participate on a VOTE regardless of binding/non-binding.
Cheers. On Tue, Oct 20, 2015 at 5:47 PM, Marko Rodriguez <[email protected]> wrote: > Hi, > > PR "binders" = committers + PMC. > Release "binders" = PMC. > > However, Dylan, as a non-committer/PMC, VOTEing on PRs and releases is > helpful as it helps the "binders" know another set of eyes tested/reviewed > the code. > > Marko. > > http://markorodriguez.com > > On Oct 20, 2015, at 9:36 AM, Dylan Millikin <[email protected]> > wrote: > > > I have a quick question regarding voting. I know that as far as releases > go > > there are binding and non binding votes. Does this carry over to PR votes > > and other [VOTE] threads or is it solely for the purpose of releasing > > (legal binding)? > > > > On Tue, Oct 20, 2015 at 5:28 PM, Marko Rodriguez <[email protected]> > > wrote: > > > >> Hello people, > >> > >> TinkerPop has transitioned to a new plateau where all JIRA tickets are > >> open to [DISCUSS] and VOTE. This is a great thing in many respects -- > >> however, with great power, comes great responsibility. > >> > >> Please note how many emails I write a day to keep up with the policy > >> requirements. Every email I write is time that takes me away from being > a > >> "worker" to being a "manager." You can do the "workers" of TinkerPop a > >> great favor by ensuring you don't abuse your powers and become a pure > >> "manager." What do I mean by that? > >> > >> 1. Being "engaged" doesn't mean asking questions so someone has > to > >> answer just to keep a discussion going. > >> 2. Being "engaged" doesn't mean having an opinion on every topic > >> just for the sake of saying something. > >> > >> For me, engagement means doing work. This is the difference between > being > >> a person who "talks" (manager) and a person who "does" (worker). If you > >> want to help TinkerPop, think about: > >> > >> 1. Writing a tutorial, blog post, article, etc. > >> 2. Finding a ticket you can work on and doing it well. > >> 3. Finding your niche in the codebase and dominating on it --- > >> documentation, tests, etc. > >> 4. Going through the pull requests and VOTEing. > >> 5. Answering questions on the mailing list. > >> 6. Studying the codebase and learning how it works so you can > >> answer your own questions. > >> > >> In general, use your time effectively. And at minimal, don't casually > >> spend the attention/time of the people who are "working." This doesn't > mean > >> that we don't DISCUSS and we don't VOTE, it means, be strategic in your > use > >> of other people's time --- and best of all, your own time! > >> > >> Thank you, > >> Marko. > >> > >> http://markorodriguez.com > >> > >> P.S. I know there is a sense of "we have to show the mentors we are > doing > >> stuff so I will reply to emails and JIRA tickets and have nick nack > >> comments on every pull request." Don't be fake. If you do that, you will > >> find nothing at the end of that road save for a brain full of other > >> people's thoughts and that is useless to that which is, and always has > been > >> -- The TinkerPop. > >
