Most of the folks got committer status through multiple contributions to the project. Given where Xerces is at I'd be supportive of a lower bar but would generally hope that potential new committers have an interest beyond one release or just a specific bug fix. It hasn't really improved the overall health of the project if those people immediately disappear.
Thanks. Michael Glavassevich XML Technologies and WAS Development IBM Toronto Lab E-mail: mrgla...@ca.ibm.com E-mail: mrgla...@apache.org David Costanzo <david_costa...@yahoo.com> wrote on 08/24/2016 09:19:59 AM: > From: David Costanzo <david_costa...@yahoo.com> > To: "j-dev@xerces.apache.org" <j-dev@xerces.apache.org>, Michael > Glavassevich/Toronto/IBM@IBMCA > Cc: "tstel...@scharp.org" <tstel...@scharp.org> > Date: 08/24/2016 09:20 AM > Subject: Re: changed various Jira issues to be releasing for 2.12.0 release > > Michael Glavassevich wrote: > > > I would be very happy to see new committers who would take a more active > > role. That's a call to action for anyone out there. If you're interested, > > we're interested in hearing from you. > > Thank you for the clarification, Michael. As I've mentioned before, > my organization has a specific interest in XERCESJ-1670 being fixed > and released. A colleague named Tobin has some time to volunteer to > commit the fix and do whatever is needed to make an official > release. I've CC'd him so that he can reply to this thread. To be > clear up-front, he's not looking to become a long-term Xerces > developer, just to help with one release. Does Xerces accept > committers on a short-term basis? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: j-dev-unsubscr...@xerces.apache.org > For additional commands, e-mail: j-dev-h...@xerces.apache.org
