Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.If it isn't obvious... I haven't been devoting much time to maintaining this module lately. I need to find someone to take over as maintainer. I may be willing to stay on as a co-maintainer (to review patches, answer questions, etc.), but I may not be able to help much since my availability for contrib time is limited and will become more sporadic going forward.
Tasks that have been neglected:
a) Fix existing issues
b) Port the module to Drupal 8
If interested, please leave a comment here, or contact me via IRC or my Drupal.org contact form to discuss. Thanks!
Comments
Comment #1
jhodgdonSee also https://www.drupal.org/node/314492 (a few links about what it means to maintain a project)
Comment #2
w van casteren commentedMaybe i would be willing to spare some time.
Comment #3
jhodgdonThanks for your interest!
From your profile, it looks like you are new to contributing to Drupal -- welcome to the project! It would be good if you got some more Drupal contributing experience before you take on maintainership or co-maintainership of this or any other project on drupal.org, to make sure you're familiar with the way we do things in Drupal-land (issues, patches, and constructive patch reviews). Also, before being ready to maintain any particular project, you would need to demonstrate that you are familiar with the code in that project, as well as Drupal coding standards. Right now, you don't have much of a record of contributing on Drupal.org to look at... I did take a look at the one other post you've made to date on drupal.org, and the patch you submitted isn't following our coding standards (at first glance, there were a lot of whitespace problems).
So... We have some resources for getting into patch reviewing, coding standards, and the like. Check out:
https://www.drupal.org/contributor-tasks/programmers
The pages listed there have instructions for the various ways programmers can contribute to the project, and resources for learning about our coding standards, checking your code for standards, etc. I would particularly suggest that you seek out the Coder project (which checks your code against our coding standards), and Dreditor (which is a browser plugin for reviewing patches).
After you've made a few more patches and done some patch reviews (in this or any other project, but including at least one or two here in this project), that would be the time to come back and we can discuss making you a maintainer. Thanks!
Comment #4
jhodgdonUm... Someone seems to have been given my module, not sure why!!!
Comment #5
jhodgdonOh sorry, user name changed. This is fixed.