Hi everyone. I am currently the only actie developer on this project, and even my time is fairly minimal. I would love some active co-maintainers for this project.

If you are interested, it would be good if you linked to some patches you have submitted or projects you have worked on.

Comments

akash87’s picture

akash87 CreditAttribution: akash87 commented

Hey i can help you out!

I'm no drupal expert, as i started off learning it only from D7, but i know it pretty darn well. I also read that you were looking for someone with JS knowledge.

So temme what i can do..

Brandonian’s picture

Brandonian CreditAttribution: Brandonian commented

zzolo, I could probably help out. My current working knowledge of Openlayers 2.11 is pretty limited, but I'm pretty familiar with the library overall, and have done some work with this module. As the semi-maintainer of GeoField, having some access to the Openlayers module repo would be helpful.

zzolo’s picture

zzolo CreditAttribution: zzolo commented

Hi @akash87It would be nice to see a couple patches in the queue just to get a sense of your ability.

@Brandonian, great work with Geofield by the way. I have given you commit access. If you are going to do any architectural or API changes, please open an issue first. Overall, most commits should have an issue with them, but this is not always the case. Hit me up on IRC when you have a chance and we can talk about the direction of the project.

nod_’s picture

nod_
Primary language French
Location Lille
CreditAttribution: nod_ commented

Guess i'll formally apply now that I know i'll be using it extensively at work but really it's just interesting to work on :)

zzolo’s picture

zzolo CreditAttribution: zzolo commented

Hi @nod_. I have given you commit access. I have also started the 3.x branch, mostly so that you can do your work there. See #1353122: 3.x Goals

It would be really helpful if you updated the issues regularly on your progress, as I won't have time to just look at your code (and just looking at code is not that affective always). Architectural changes need discussion. Feel free to utilizes patches or branches to get review on things before committing.

Also, please try to make your changes very small and discreet. This is important both for being able to understand the changes, as well as merging code from 2.x or to 3.x will be a lot easier if you don't fix the white space issues through out the code.

Please write documentation as you go. It doesn't need to be perfect, but it will me (and others) understand things as they changed. You can writing things in the issue, or I have start a 3.x dec section: http://drupal.org/node/1353130

nod_’s picture

nod_
Primary language French
Location Lille
CreditAttribution: nod_ commented

Thank you very much :)

I will keep my work reviewable and documented. I'd rather stay in the 3.x branch too, don't want to break important things.

Pol’s picture

Pol
the/that
Location Brussels
CreditAttribution: Pol commented

Yup, if you need help, don't hesitate :-)

cloudbull’s picture

cloudbull CreditAttribution: cloudbull commented

--deleted

jankocvirn’s picture

jankocvirn CreditAttribution: jankocvirn commented

Hi ,

would like to help ,I have experiance with Openlayers ,Geoserver etc...

zzolo’s picture

zzolo CreditAttribution: zzolo commented
Title: Looking for co-maintainers » Looking for (co-)maintainers

So, it's pretty clear to me that I just don't have time for this module as much as I want to, and keep trying to make tie for it, it's just not happening. And as I was the last significant developer on this project, we are officially looking for a full-time maintainer on this module.

To become a maintainer or co-maintainer, there's got to be some evidence that you know what you are doing with Drupal, OpenLayers, and this module. More than likely this will be helping in the issue queue and providing/reviewing patches in the queue. Other modules, commits, patches for different modules could be enough evidence. It is definitely a subjective decision, but it is the best we have.

Any help in the issue queue and documentation does not require that you are a maintainer, so feel free to help out there as much as you want.

zzolo’s picture

zzolo CreditAttribution: zzolo commented

@jankocvirn. Thanks for the offer. It looks like you are brand new to Drupal (or at least your Drupal.org membership is pretty new). So, there is no real evidence that you have experience working with Drupal, this module in particular, or contributing to Drupal at all. It would be nice to see work you have done with just OpenLayers, but keep in mind that this module tries to be a very thin integration with OpenLayers and is more Drupal heavy than anything else.

As pointed out above, you can start by helping out in the issue queue, reviewing/providing patches, or with documentation. You do not need any special status to do this.

Pol’s picture

Pol
the/that
Location Brussels
CreditAttribution: Pol commented

I'm ok to maintain the module if you need.

Mapping, Openstreetmap & Drupal are my favorites stuff to do online so and I have few hours to spend so I think I can help :-)

Thanks!

Aurlin’s picture

Aurlin CreditAttribution: Aurlin commented

If you still need help, i can help you.

Actually, i'm working on a project who use this module (i can send you url if you want), and we fix bugs inside the module.

I have time because i'm working everyday on it :)

Thanks

dasjo’s picture

dasjo
he/him
Primary language German
Location Zurich
CreditAttribution: dasjo commented

there is also a helpful documentation page available on the topic:
Best practices for co-maintaining projects

steinmb’s picture

steinmb CreditAttribution: steinmb commented

@Ol and @Aurlin both accepted to step up and help out maintaining this module. Did you get accepted?

zzolo’s picture

zzolo CreditAttribution: zzolo commented

Well, as I had mentioned before, I am reluctant to give anyone (co)maintainer status unless they have demonstrated that they know how manage code on Drupal.org and do releases and all that jazz.

@Pol, I have made you a co-maintainer.

@steinmb, I noticed you have been helping out in the queue a lot and I would love to make you a co-maintainer as well, but I don't see that you have really released any modules on Drupal.org so I am a little reluctant. If you feel you have a full grasp of releasing code and Git on Drupal.org, then I can give you that access.

Pol’s picture

Pol
the/that
Location Brussels
CreditAttribution: Pol commented

Thanks @zzolo !

@steinmb, I'm often on IRC, don't hesitate to ping me if you need :)

steinmb’s picture

steinmb CreditAttribution: steinmb commented

I have for the last two weeks been a maintainer of http://drupal.org/project/openlayers_geocoder, cleaning up and committing and fixing old bugs. Not sure if I have much spare time until after Drupalcon to work on OL, though there are bugs/changes in OL Geocoder that prob. are depending on changes in the old OL 6.x branch, that today is mostly without and TLC (if I'm not mistaking?), so joining up with you before DC might make sense.

zzolo’s picture

zzolo CreditAttribution: zzolo commented

@steinmb, you now have access. Please coordinate with @Pol and anyone else who is significantly working on the module (there are a lot of co-maintainers) before releasing.

I would strongly suggest making new issues around releases and what needs to be done before a release.

becw’s picture

becw CreditAttribution: becw commented

Hey @zzolo, I already have commit access, but I'm potentially interested in being more active here.

@Pol, @steinmb, and other co-maintainers: is it ok if I jump in and fix some bugs once in a while? I'm also happy to help other OL maintainers if anyone has questions about using git, drupal.org's release system, the OpenLayers js api, etc. You can find me on IRC in #drupal-contribute.

Pol’s picture

Pol
the/that
Location Brussels
CreditAttribution: Pol commented

You're welcome @becw :)

Most of Openlayers guys are on #drupal-geo, I'll try to stick around on #drupal-contribute too, my nick is drupol.

steinmb’s picture

steinmb CreditAttribution: steinmb commented

@becw feel free to jump in :) Like I wrote in #18 do I have limited time up until after Drupalcon. My nick - steinmb, and you will find me in the both mention IRC channels, though #drupal-geo is where we should try to group.

joshua1234511’s picture

joshua1234511
Primary language English
Location Goa
CreditAttribution: joshua1234511 as a volunteer and for Salsa Digital commented
Issue summary: View changes

Would like to take over this project maintenance, and have it moved to openlayers V6. Have some sites using this module and need so features added.
First will need this to be able to use v6,

steinmb’s picture

steinmb CreditAttribution: steinmb as a volunteer commented
Version: 7.x-2.x-dev » 7.x-3.x-dev
Category: Support request » Task
Status: Active » Postponed (maintainer needs more info)

Wow, this issue was a blast from the past. @joshua1234511 did anyone get back to you regarding the role as co-maintainer?

BTW. I have not seen you very active in the issue queue, and I am sure the current active maintainer would love help following up old issues, and for that, you do not need any special maintainer privilege. I will also prove your knowledge to the module, bugs and current state.

ken-g’s picture

ken-g CreditAttribution: ken-g as a volunteer and commented
Status: Postponed (maintainer needs more info) » Fixed

Hi All,
I took over the maintenance of this module about a year ago, after a period of six years inactivity, and over ten years since this issue was raised.

I have concentrated on fixing as many of the 7.x-3.x bugs as I could, and brought the whole module up to date to use PHP 8 and Openlayers 7.

I am happy being the sole maintainer on this module for the remaining life of D7, but would obviously welcome patches or solutions for any remaining issues that are still regarded as important after all this time.

On the above basis, I am setting this issue to 'Fixed'.

Status: Fixed » Closed (fixed)

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