On Tue, Jun 25, 2013 at 11:28 PM, Brett Walker
<brett.wal...@geometryit.com>wrote:
> Thanks Chris for your questions.****
>
> ** **
>
> I’m interested to learn more about image sources as it would complement my
> experience in database sources (JDBCC) such as Oracle and PostgreSQL. Keen
> to get my teeth in the DB2 module also.****
>
> **
>
Awesome. I think image sources are where we've traditionally been a bit
weaker, but the geosolutions crew has been turning that around for years
now, and the new grid coverage stuff landing soon is going to be a big step
forward. I suspect they can come up with some cool ways to help out there.
One idea I had (though I've not thought it through a lot so someone may
shoot it down) is to do a 'directory of image files', just like we have a
'directory of shapefiles' on the vector side. I think this has not been
possible because of our old architecture, but with the new work landing I
think it might be something nice to add. It's a pain now to select every
image file - would be much better to just point at a directory and have it
find everything. I think there are some importers that help with this, but
logically I believe it'd make more sense to have few 'coverage stores' -
have them be directories with coverages of all the images in them. I
believe the directory of image files might help get you up to speed, and
then open up a lot more interesting directions to make it far easier to
configure image sources. We've got all the power to do amazing stuff, but
it's not at the point where you can just point geoserver at a directory of
random sources and have it do the right thing, or even be super easily
configured for the right thing.
DB2 usually can use some love. We've had a few people come in and do great
work on it, but I don't think it's had a long term consistent maintainer.
So there's probably some updates and optimizations to be done there.
> **
>
> My more immediate areas of interest are around the build process.
> Upgrading dependencies, plugins. Full support for Maven3 and JDK7.****
>
> **
>
Awesome, that's definitely thankless work that I'm sure will be appreciated.
> **
>
> Documentation needs attention also.****
>
> **
>
As are docs, definitely would be great to get GeoTools better there, help
reveal more of its power to newer users.
> **
>
> PR#208 is one I have submitted that has been sitting around for a while.
> PR#217 and PR#18 submitted by others seems good. I have a concern that
> PR#217 might break backwards compatibility.****
>
> **
>
Cool, I'll let the real devs comment on those :)
Chris
> **
>
> Brett****
>
> ** **
>
> *From:* chol...@openplans.org [mailto:chol...@openplans.org] *On Behalf
> Of *Chris Holmes
> *Sent:* Wednesday, 26 June 2013 1:17 PM
> *To:* Brett Walker
> *Cc:* geotools-devel@lists.sourceforge.net
>
> *Subject:* Re: [Geotools-devel] Pull Request Policy****
>
> ** **
>
> Welcome Brett! ****
>
> ** **
>
> As you can tell we get too many requests from people who aren't actually
> interested in joining up and helping out. When I first read your message I
> actually suspected you might be up for contributing, but I can see how it
> was ambiguous. Would have been good to mention the pull request you made,
> since it looks like a couple core devs were excited about it. I'm glad
> you're up for the gift economy that is open source.****
>
> ** **
>
> I think our unofficial rule is (or at least was, it's been way too long
> since I've committed to GeoTools) to have at least two or three solid,
> reasonably sized patches before commit access. I see your PR at
> https://github.com/geotools/geotools/pull/208, would be good to link to
> the patches you've done in the past.****
>
>
> But now that everyone knows you're interested in becoming a committer and
> helping out I'd guess someone will be inclined to review your PR much
> sooner. So I'd say just poke people on your PR's, with offers to help out
> on issues they wish were done. And when you make new PR's just poke the
> list with what it's about.****
>
> ** **
>
> Sounds like you have great experience for GeoTools though, so will be
> really great to have you aboard. I'm also curious about what areas of
> GeoTools you're interested in. Is it just the parts you have experience in?
> Or are there newer topics you're interested in diving in to? There are
> definitely some key areas of GeoTools where we only have one or two expert,
> so would be great if you're interested in some of those.****
>
> ** **
>
> Chris****
>
> ** **
>
> On Tue, Jun 25, 2013 at 11:02 PM, Brett Walker <
> brett.wal...@geometryit.com> 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****
>
> ** **
>
>
> ------------------------------------------------------------------------------
> 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
