Hi,

I'm wondering if OpenLayers Proximity is still being actively maintained as indicated on the project page. I'm asking since:

  • It has been 39 weeks since the most recent commit.
  • There is no stable, recommended release, only a development snapshot.
  • A fully-working Drupal 7 port is available on github, with jpstrikesback volunteering to (co-)maintain it. It would be far better for the community not to have to resort to github for this.
  • Seemingly trivial community-tested patches linger in NR or RTBC without being committed (for example http://drupal.org/node/1004680)

Could you update the maintenance and development status on the project's landing page? If you'd like to have some additional hands on board, you can indicate that you are looking for (co-)maintainers there too. If you just do not have the time to keep maintaining the module, you can also officially abandon it.

Comments

philippejadin’s picture

Component: Miscellaneous » Code
Priority: Normal » Critical

Pushing this. It seems that :

- module is not maintained
- people use the unofficial Drupal 7 port available at https://github.com/jpstrikesback/proximity

Could the author give some signs about wether this (great) module is still maintained?

Thank you in advance

philippejadin’s picture

Title: Is OpenLayers Proximity still being maintained? » OpenLayers Proximity seems unmaintained
Project: OpenLayers Proximity » Drupal.org site moderators
Version: 6.x-2.x-dev »
Component: Code » Project problem

As per http://drupal.org/node/251466

And given the fact that we got no answer from the maintainer, I think we can assume this project is unmaintained.

Original project page is here : http://drupal.org/project/openlayers_proximity

jpstrikesback (http://drupal.org/user/105210 ) offered to maintain it here : http://drupal.org/node/1013450#comment-4664436

The implementation provided in the git repository of jpstrikesback (can be found here : http://drupal.org/sandbox/jpstrikesback/1367194 )is curently working on Drupal 7 and is being used. It would be better to have this version available directly on d.o

WorldFallz’s picture

Status: Active » Postponed

You can't really apply for maintainership for someone else. jpstrikesback's offer of maintainership was almost a year ago. he/she (or anyone else for that matter) will need to apply to take over the project for themselves.

jpstrikesback’s picture

Hey All, I'll update this issue with my position in a day or so. I'm about to make a bunch of changes to my sandbox that should be good jump off. At this point (or for D7) it no longer makes sense to call the project openlayers_proximity (as it no longer needs openlayers) so any suggestions on process for that if I do go for maintainer of the ship would be appreciated.

Cheers,
JP

jpstrikesback’s picture

I'm ready to take over maintenance of the project and place it in maintenance mode. I'd be glad to test/apply submitted patches etc and release the 7.x branch as an alpha. The goal wouldn't be to take the current project much further (See http://drupal.org/node/1013450#comment-6148236) but to provide support as listed, testing & applying RTBC patches for the sites that have installed what is in my sandbox. I'll go thru the docs on taking over a project and make sure I've done everything required, Antoniodemarco the current maintainer may actually still be interested.

WorldFallz’s picture

Component: Project problem » Project ownership

fixing the component

sreynen’s picture

Priority: Critical » Normal
Status: Postponed » Fixed

I've made jpstrikesback the owner of the project. Process-wise, pointing users to the new, more active project is good. Creating an upgrade path that moves user data to the new module would be great, though maybe not worthwhile given the number of users.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Project: Drupal.org site moderators » Drupal.org project ownership
Component: Project ownership » Ownership transfer