Looking for co-maintainers

Posted by zzolo on September 10, 2011 at 5:43pm

Issue Summary

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

#1

Posted by akash87 on September 23, 2011 at 7:38am

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..

#2

Posted by Brandonian on September 25, 2011 at 11:26am

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.

#3

Posted by zzolo on September 26, 2011 at 3:30am

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.

#4

Posted by nod_ on November 19, 2011 at 1:50am

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 :)

#5

Posted by zzolo on November 26, 2011 at 4:27am

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