s/making a release before/making a release, before/
On Thu, Jun 2, 2016 at 1:50 PM, Julian Hyde <jh...@apache.org> wrote: > I'd like to see some concrete progress in (a) building a community, > (b) making a release before the next report. Right now, I can tell > that you're all about code. Quite frankly, we don't give a hoot about > code. Build a community, and the code will happen. Quickstep needs to > start building a community. > > Julian > > > On Thu, Jun 2, 2016 at 1:41 PM, Jignesh Patel <jipa...@pivotal.io> wrote: >> Thanks Julian! Adding this to the list to work on. >> >> Neat tips! >> >> Cheers, >> Jignesh >> >>> On Jun 2, 2016, at 3:40 PM, Julian Hyde <jh...@apache.org> wrote: >>> >>> You, as a PMC, should decide what are the criteria & process for >>> making someone a committer. There are some guidelines[1], but they are >>> only guidelines. >>> >>> In my opinion, you should err on setting the bar too low rather than >>> too high. Making someone a committer early will tend to draw them into >>> the community. And, remember that code is not the only kind of >>> contribution. >>> >>> The Quickstep community should also have a broader discussion: how do >>> you intend to meet your goal of "Acquire early adopters". Electing >>> committers is a consequence of a successful strategy for growing >>> community, and helps further that growth. >>> >>> Julian >>> >>> [1] http://community.apache.org/newcommitter.html >>> >>> On Thu, Jun 2, 2016 at 1:29 PM, Jignesh Patel <jipa...@pivotal.io> wrote: >>>> Thanks Julian! >>>> >>>> What are the guidelines for election? We would love to welcome new >>>> committers who are starting to make serious contributions. >>>> >>>> Cheers, >>>> Jignesh >>>> >>>> On Jun 2, 2016, at 3:28 PM, Julian Hyde <jh...@apache.org> wrote: >>>> >>>> The key word here is "elected", as opposed to "showed up in his >>>> congressional office for the first time". :) >>>> >>>> >>
