Hi Dor, If you show a history of excellent contributions in terms of pull requests, code reviews, JIRA entry and collaboration, Wiki edits, newsgroup participation, and evangelism of Geode, the PPMC will nominate and vote in committer role for you. BTW - you can do all this today without being a committer.
We are about to announce a new committer who has been working with us in a very collaborative way since last August This email encrypted by tiny buttons & fat thumbs, beta voice recognition, and autocorrect on my iPhone. > On Mar 7, 2016, at 8:02 AM, Dor Ben Dov <[email protected]> wrote: > > Thank you Jens. > > By means of all that, the aka committers, how can one be one of them ? > > Dor > > From: Jens Deppe [mailto:[email protected]] > Sent: יום ב 07 מרץ 2016 17:55 > To: [email protected] > Subject: Re: Geode github commits > > Hello Dor, > > If you haven't already, I'd suggest reading through the relevant Wiki pages > [1] > > Generally, if the change you're wanting to make is fairly invasive or maybe a > new feature then a discussion on the [email protected] would be > appropriate. This is where you would present your change and solicit feedback > from the community. This mailing list goes out to both committers and > non-committers so you would reach everyone who has an interest in Geode. > > If the change is relatively straight forward, (and you feel doesn't require > any discussion; perhaps because it's already covered by an existing Jira > ticket [2]), then simply submitting a github pull request would be > appropriate. Once submitted, the committers can review the request and > suggest any further changes as they see fit. > > --Jens > > [1] - https://cwiki.apache.org/confluence/display/GEODE/How+to+Contribute > [2] - https://issues.apache.org/jira/browse/GEODE > > > On Mon, Mar 7, 2016 at 7:26 AM, Dor Ben Dov <[email protected]> wrote: > Hi, > > Currently who are the ones responsible on approving new features or bug fixes > ? > > Is it possible and how, joining this group ? > > > Dor > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, you may review at > http://www.amdocs.com/email_disclaimer.asp >
