The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Hello,
I have recently been working on a module very similar to this, and I am willing to develop this module for my website, as well as getting a release out for all the other users who are eagerly waiting for this module to be worked on.
I suspect, given the lack of a development snapshot release and the issues in the project, that this project has been effectively abandoned.
In following with Drupal guidelines (http://drupal.org/node/251466), I am opening an issue to request to take over the maintenance of the project.
I have also sent a private message to rizzo. Looking forward to a response so I can get this project off the ground.
In the meantime, if I get my module code to a degree of completion, I will upload it here so others looking for a module with the functionality described can use something.
Thanks
Al
Comments
Comment #1
Alun commentedNote: Contrary to the above, I actually haven't sent a message to rizzo, as he does not have a contact form on his profile page.
Comment #2
ericpfeifer commentedwonderful! I would be willing to donate to the project (both in QA'ing and monetary) if someone was interested in continuing the work as I have a client who is very interested in having this functionality.
Comment #3
Alun commentedThanks for your support.
I have managed to get hold of rizzos email address, so I have fired off an email to him. Obviously, being the festive season it is, I'm not expecting a quick reply, but I will keep you informed on any developments.
Comment #4
ericpfeifer commentedAlsum,
Great to hear it! Thanks for the update and if there's any help we can give we'll be happy to do what we can.
have a great holiday!
Comment #5
toma commentedAny news i am looking for the same module, i can donate
Comment #6
Alun commentedHi Toma, thanks for your comment. In following with Drupal guidelines there is a wait of two weeks to allow rizzo to respond to the request. I am hoping rizzo is able to respond within this time, which means we can move on quickly. Otherwise if there is no repsonse in two weeks, I have to notify the Drupal administrators to allow me to take over development of the module. Given the process this needs to go through, I would expect I can get a useable release sometime in January - feature requests can then be looked at after the initial release.
Comment #7
Alun commentedHi guys, I've added a forum topic to continue the discussion of development of the module, as the main point of this issue is to help with development.
I will also post up code for the work I have done so far there. It will be available in a few hours I hope.
Find the forum post here - http://drupal.org/node/668234
Comment #8
avpadernoI sent an email to the current maintainer using his contact form.
Comment #9
Alun commentedMoving this thread to the webmasters.
I have not heard anything from rizzo regarding the development of this module, after allowing 14 days to respond.
Please let me know the next step in applying to become co-maintainer of this module.
Thanks
Alun
Comment #10
dave reidNote this didn't really follow the abandoned module process. Asking to help co-maintain is one thing, asking if someone is still intending to maintain a module or if its abandoned is another.
Comment #11
avpadernoThe title of the issue was changed by me; Alun is willing to take over the module, not to mark the project as abandoned.
In the email I sent to rizzo, I specified that somebody was willing to be co-maintainer or maintainer of the project.
Comment #12
dave reidBy moving this issue to the webmasters queue like #9 did, this essentially became an 'abandoned module' issue. With that we can either transfer the project to someone willing to maintain it, or mark the module as abandoned. I'm saying that this process that we would normally do hasn't really been followed. No one's really asked the important question if the current maintainer is still intending to maintain the module.
Comment #13
avpadernoReading the page about dealing with abandoned projects, I read the support request should state the request to take over maintainership (point #1 listed after ); after 14 days without an answer, the support request can be moved to the webmasters' queue (point #3).
The page doesn't report to ask if the project is still maintained, in the case who opens the support request is a developer, and
the support request has not been re-titled . It seems to me that the procedure to follow in the case somebody wants to take over a project has been followed correctly.
Comment #14
dave reid@Kiam: Thanks for the clarification. I just know if I was the maintainer I'd probably respond to something like 'Your project might be transferred if you don't respond.' much faster than 'I want to help co-maintain your module.'. (In reality, I'd respond to both, but one has a more serious tone than the other).
Comment #15
avpadernoLet's do this: I change the title of this report to make it more explicit, send it back to the project queue (to make possible for the current maintainer to see this support request, in the case he checks his project queue), and send another email to the current maintainer, stating that in the case he doesn't reply the ownership of the project will be transferred.
Comment #16
avpadernoI sent another email to rizzo.
Comment #17
ericpfeifer commentedsounds like a good plan as I'm anxious to get the module up to speed as the sports season is coming up quick and we need a solution soon!
Comment #18
Alun commentedHi Dave,
Thanks for your response.
My issue initially was opened in order to get in touch with Rizzo and essentially take over module development. By requesting this, I was hoping I could get a response from rizzo regarding his willingness to continue developing for the module.
I took the instructions of filing my issue from the guidance of 'Dealing with abandoned projects' (http://drupal.org/node/251466)
In this, it does state to follow the instructions for projects that appear to be abandoned.
On the relevant project page, there are no development releases, and the last recorded activity on the page from rizzo was 49 weeks ago. from this, and the lack of response from the maintainer in the issue queue, I decided that the project fell into the category of appearing to be abandoned. If the wrong procedure has been followed, then I apologise, but I believe the steps that I have taken have been fair in establishing that the current maintainer is not active on Drupal, and therefore is not intending to maintain the module.
Thanks for your time in dealing with this.
Comment #19
Alun commentedsorry, i was typing a response when you changed the issue details, I will read your responses now.
Comment #20
Alun commentedOK, cool, I guess I'll be back in a week! Do I keep the issue here in a week, or move back to the webmasters issue queue?!
Comment #21
avpaderno@Alun: You can keep the report here; just write a comment after a week, and I will notice it in my track page.
Comment #22
Alun commentedA week has passed. I will file a CVS application to go with this thread.
Thanks.
Alun
Comment #23
avpadernoI passed the ownership of the module to Alun; rizzo still have CVS access as it is normally done in Drupal.org.
Comment #25
rizzo commentedHi everyone. Sorry about not responding and abandoning the project (yes, I admit it). First I had a problem of an out-of-control inbox so I was ignoring all but a few emails.
Second I abandoned this project last year after I learned how to use CCK, so I used that for my site rather than coding more basic node types with very little time to do so.
Thanks to Alun for taking over.
Don (rizzo)