It appears that no updates have been actively made through CVS at this time. I would like to request that I be allowed CVS access to this project to update the project with the latest patch and create an official Drupal 6 release of the module on the project page. I am not a developer at this point, but wouldn't mind cutting my teeth a bit with this project. I have begun to learn PHP, and there is a patch already available, which I have tested (using on a production site), that makes this module work well for Drupal 6. If there is someone more suited to maintain this, please let me know. In the meantime, I am willing to put myself forward as a maintainer of this module. If you are the current developer, please let me know for sure whether you have abandoned development of this module. Thank you! The patch for the Drupal 6 release is here: http://drupal.org/node/260090
Thanks to Hutch for creating this patch and keeping this project alive!
Comments
Comment #1
bomarmonk commentedComment #2
hutch commented+1 for bomarmonk to be maintainer of this project
Comment #3
HS commentedIt's embarrassing that this module does not have a D6 version yet and even more embarrassing that an individual wants be a co-maintainer but two months have passed and Drupal posse haven't given him access to take the module forward.
Comment #4
HS commentedthis is not a first either. Someone else applied to take over this module in 2009! See: http://drupal.org/node/260090#comment-2187998
Comment #5
bomarmonk commentedI believe I followed all of the instructions to take this over; at the very least, I could post an official 6.x version (I just wanted to learn how this whole development process works, etc.). I haven't heard anything back...
Comment #6
dawehnerDid you asked the maintainer via mail? If he didn't answered i guess you can open an issue in the webmaster queue.
Comment #7
bomarmonk commentedI did e-mail the previous maintainer and heard nothing back... so I'll try the webmaster queue.
Comment #8
yesct commentedsub
Comment #9
nathanjo commentedsub
Comment #10
yesct commented#822942: Offering to maintain Views Ticker looks hopeful this will be resolved soon.
Comment #11
avpadernoThe ownership has been changed as per http://drupal.org/node/822942.
Comment #12
hutch commented@bomarmonk
Looks like you're there ;-)
Time to bone up on CVS, you will want to create a Branch DRUPAL-6--1, make sure it's sticky, put the D6 version in and commit. Then create a project page for it in do.org and release.
Enjoy!
Comment #13
bomarmonk commentedOkay, I tried "Adding a new release" from the project page, but I get the message "Access Denied." Am I supposed to be able to do this, or do I have to add the release a different way?
Comment #14
avpaderno@bomarmonk: You don't have a CVS account; without doing that, you cannot commit code to CVS, nor create new releases.
See http://drupal.org/cvs-application/requirements to apply for a CVS account; add a link to this issue, when you apply for a CVS account.
Comment #15
yesct commentedyou might, maybe have to provide them with the code you are about to commit so they can do a security, doc, coding style review ... kind of like what people who are trying to put up their first module do. It's my understanding they like to do something to make sure maintainers understand those aspects.
Comment #16
hutch commented@YesCT, this is a takeover of existing code so there should not be a problem.
@bomarmonk, when you have a cvs account sorted grab a tool off the 'net, wincvs, lincvs, smartcvs or if you really want to get serious download Eclipse with the PHP plugin. see http://drupal.org/node/765098
Comment #17
bomarmonk commentedI will be working on my CVS skills and knowledge in the coming weeks, so thank you for your patience. Expect an official 6.x release is August.