Hi Ilya, Basically one of committers who usually reviews and merges code should spot that it’s time to discuss a candidacy.
Anyway, if a contributor feels that committers don’t keep an eye on his/her progress the contributor can remind about personal existence by sending a message to @dev. ;) — Denis > On Dec 23, 2017, at 3:58 AM, Ilya Lantukh <[email protected]> wrote: > > Hi Denis, > Who should take the initiative in promotion? As a contributor who meets > those criteria, should I send my application to the PMC or just wait? > > On Fri, Dec 22, 2017 at 8:24 PM, Denis Magda <[email protected]> wrote: > >> Hi Vyacheslav, >> >> Some common sense, I presume. A committer who will be proposing a >> candidate can use JIRA to see a total number of resolved tickets and Git >> history to get insights on a complexity of every contribution. >> >> Do you have any suggestions on this? >> >> — >> Denis >> >>> On Dec 22, 2017, at 12:56 AM, Vyacheslav Daradur <[email protected]> >> wrote: >>> >>> Hi, Denis, how will the complexity of tasks be estimated? >>> >>> >>> On Fri, Dec 22, 2017 at 3:16 AM, Denis Magda <[email protected]> wrote: >>>> Igniters, >>>> >>>> We at Ignite PMC put together a page with rules-of-thumb on when it’s a >> right time to promote a contributor to a committer: >>>> https://cwiki.apache.org/confluence/display/IGNITE/ >> Committership+Bar+Guidance <https://cwiki.apache.org/ >> confluence/display/IGNITE/Committership+Bar+Guidance> >>>> >>>> It’s intended to make “contributor to committer” process more evident >> and simplify Ignite PMC voting process on this matter. >>>> >>>> Please use it as a reference, comments and suggestions are welcomed! >>>> >>>> — >>>> Denis >>> >>> >>> >>> -- >>> Best Regards, Vyacheslav D. >> >> > > > -- > Best regards, > Ilya
