Taking a break from geocoder development

Sorry to see you go, @phayes, but definitely thankful for the time you've put in so far. We should try to wrangle in a few regular contributors during the mapping office hours this week.

In the meantime, can you give me full access? I have commit already, but I can act as a pseudo-maintainer until we get somebody(ies) in place longer term.

I've been looking for a project I could get more involved with and I've used geocoder a lot recently. I'd be happy to donate some of my time to maintaining the module.

Dean

Cheers, Phayes. I'd hoped to have been a little more active in the issue queue but got caught up at work these last few weeks. Things are back to normal now though so I'll hopefully get through some issues in the next couple of days.

I will give a hand if I can but do not give me commiter rights I will provide patches.

Yes, please add commit rights for me as well, I will be doing geocoding work in Q1 2013.

I can help test/review patches to dev and facilitate issue queue movement.

Are there news regarding maintainership of this module?
I currently count 5 RTBC, 6 NeedsReview and 6 Needs Work issues. I'm trying to do some triage, but is there somebody to commit patches if I manage to produce them or have them produced?

So, I did a bit of triage tonight.
Just to sum-up, and identify major concerns for users:

Miscellaneous RTBC issues:

• #1908428: Remove trailing spaces and CVS keywords
• #1911770: Typo: Get the geomtry of a GPX string or file
• #1515372: Caching Results

Regarding bulk-update:

• #1451942: Provide drush-command to re-geocode all empty values
• #1735046: Generate geocode info for existing nodes with address field (->Batch update)
• #1928280: Geocode existing nodes

Regarding preserving existing results in various cases:

• #1509988: Add flag to prevent geocoding
• #1686620: Skip Geocoding if values already exist
• #1493496: When programmatically creating many nodes, 10k+ is there a way to skip geocoding if it has already been geocoded?

Regarding geocoding accuracy (and especially country support):

• #1872086: "Casilla" doesn't geocode properly
• #1380570: Reject geocoding if accuracy requirements are not met
• #1748412: Geofield Mapquest Geocoder
• #1871962: Use Countries module to improve geocoding results

Additional services / settings support:

• #1542842: Bing Geocoding Handler
• #1580512: Google geocoding with a Google business enterprise account
• #1380570: Reject geocoding if accuracy requirements are not met
• #1549254: Google routing support
• #1914132: Entity property

@SG Thank you i am going through these issues and committing any minor code cleanup RTBC ones. Ill be more active in the issue queue in the next months as we have a new project utilizing the JS clientside side of this functionality as well. Any help is appreciated.

I think I've done all I can, I provided a few patches as well, but I'll need more time to dig deeper in the different APIs, and sadly I don't think I'll have it before a few months. Good luck in your issue queue cleaning spree ;-)

I'd love to help, at least to get in

• #1515372: Caching Results
• #2159925: Geocode from virtual fields/entity property instead of just real fields

@Brandonian stepped up to the plate, but perhaps we need more co-maintainers for this module.

Last release was 2012-Aug-27 but fortunately there has been some movement on the devel version. Sadly, Drupal's security infrastructure can't support changes in the devel version, so this really isn't a good long term solution.

This issue is about finding new maintainers. I set up a new one to look at putting out a new stable release - #2427979: Please Release a Geocoder 7.x-1.3

Would be great if we could do this in the next few months.

Sure. I plan to do a sprint during the Drupal Dev Days if I'm there. I'll take any help there is ;-)