+1. I changed the title to attract attention. You need three +1 votes. See also: http://docs.geotools.org/latest/developer/roles/commit.html
You will still need permission from module maintainers before committing. An agenda driven by company needs is not incompatible with project participation, as long as it is does not conflict with the community. Many project participants work for commercial or government entities with their own agendas; we come here to collaborate for the benefit of all. Individual contributors are most welcome. Here is the app-schema issue for which Brett provided patches (thoroughly unit-tested, and survived review by Rini): https://jira.codehaus.org/browse/GEOT-4117 https://jira.codehaus.org/secure/attachment/59630/ImprovedSelectPropertyNameWithGmlIdAttribute.patch https://jira.codehaus.org/secure/attachment/59629/SelectPropertyNameWithGmlIdAttribute.patch Kind regards, Ben. On 26/06/13 11:02, Brett Walker wrote: > Hi Jody, > > I take this as an invitation to request commit access. May I have commit > access please? > > A bit about myself. > > My name is Brett Walker from Hobart, Tasmania. I work for Geometry > (http://www.geometryit.com/) that has an expertise in spatial applications, > for nearly 10 years. I have be a using Java, much longer, almost twenty > years. And I have experience with other languages such as assembly, C/C++ & > .NET. > > Geometry developed a product called Exposure that is very similar to > GeoServer. Our reliance on Exposure for spatial solution has diminished as > Geometry has turned towards GeoServer and Geotools for providing solutions. > I have contributed small patches to GeoTools in the past. > > I have had exposure to a number of Web Service Technologies and various > Database technologies, particular Oracle and PostgreSQL. > > I would be helping GeoTools outside of company time and not constrained by > copyright/licence agreements with Geometry. I have no agenda driven by > company needs or other concerns. > > This is an offer of assistance in the spirit of the Open Source community. I > want to help. I would like to be come just a committer and, not at the > moment, have additional responsibilities such as a module maintainer. > > GeoTools is a large body of work. I have lots to learn but am very willing. > > While this is brief, I am open to further queries. > > Please consider my request for commit access, > Brett > > -----Original Message----- > From: Jody Garnett [mailto:jody.garn...@gmail.com] > Sent: Wednesday, 26 June 2013 8:09 AM > To: Brett Walker > Cc: Geotools-Devel list > Subject: Re: [Geotools-devel] Pull Request Policy > > Same as a patch in Jira - should have a test case, subject to volunteer time, > etc... > > Pull request coming in via our change control procedure are planned during > our bi-weekly meeting, and in the case of GeoSolutions API change the subject > of scheduling. In this case geotools is entering lockdown shortly, so as a > volunteer I want to see any API changed done *now* so it does not wait 6 > months. > > We have a small number of active participants, if your organization needs > more timely service consider taking part in the project (as a module > maintainer or obtaining commit access). Some groups that have restrictions on > programming in public go the commercial support option. > > We're there any pull requests in particular you were concerned with? > > -- > Jody Garnett > > On 26/06/2013, at 7:39 AM, Brett Walker <brett.wal...@geometryit.com> wrote: > >> Hi, >> >> What is the policy/procedure/expectation for pull requests that have been >> submitted for more than a couple of weeks? >> >> There are a number of pull requests that have been sitting 'dormant' for a >> while. Do they sit forever open with no feedback, or should they be closed, >> with comment, if not found suitable. >> >> It seems that pull requests from developers with commit access have >> preference with daylight second. >> >> Ignoring worthwhile patches could appear to give the cold shoulder to the >> wider community. >> >> Your thoughts please, >> Brett >> >> Sent from my iPad >> ---------------------------------------------------------------------- >> -------- This SF.net email is sponsored by Windows: >> >> Build for Windows Store. >> >> http://p.sf.net/sfu/windows-dev2dev >> _______________________________________________ >> GeoTools-Devel mailing list >> GeoTools-Devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geotools-devel > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > GeoTools-Devel mailing list > GeoTools-Devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geotools-devel > > -- Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au> Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
