Hi, I have been using this module for many sites now, and I read the notice that you are in need of a new maintainer.

I have been doing Drupal work since 2 years now, but since I am a student, I decided to dump all client nonsense, and am concentrating full time on increasing Drupal awesomeness. I am also a d.o site maintainer and a Doc team member. I haven't yet found a way to contribute in terms of code, and I think maintaining a module which I have used so much, would be a great honor for me.

I have checked out a HEAD version of the code, and am taking it apart to see what makes it tick :-) I hope to release a 6.x version of the module (ASAP) if given the chance.

Comments

frjo’s picture

frjo commented
Status: Fixed » Postponed (maintainer needs more info)

Great to here!

Send in e.g. a Drupal 6 update patch (don't need to be complete) so I know you are serious. Then I will happily transfer the project to you.

I would recommend that you make use of views and cck for the Drupal 6 version, that would make Vote up/down a lot more useful och modern.

If you dont' already have an account on Drupal cvs you can apply for one here:

http://drupal.org/node/59

I need to know your cvs username to make you a co-maintainer.

mcurry’s picture

mcurry commented
Assigned: Unassigned » frjo
Category: support » task
Priority: Critical » Normal
Status: Active » Postponed (maintainer needs more info)

*subscribe*

fiLi’s picture

fiLi commented

*subscribe*

presscue’s picture

presscue commented

Further to my email, I too would like to help maintain this valuable module, perhaps as lut4rp's co-maintainer. I can probably work on the views integration part.

I have already requested a CVS account.

rob c’s picture

rob c commented

i can also do some work on this mod

testing / patching

this module is to darn important to just let go, it realy fits Dsix (and my site :) )

i've already tested Romka's 6.x version @ http://drupal.org/node/305839
it works, but not 100%, but it's a darn good start
i've already started to get some issues out of the way of his version, but i will hold until we have a new maintainer, a real 6-x.-dev start and a good plan for the 6.x release (and the future?)

f.e. using views / etc etc

keep it up !

Rob

frjo’s picture

frjo commented

I still have not received cvs account information from any of the persones who showed interest in maintaining Vote up/down.

AjK’s picture

AjK commented

cvs account for lut4rp approved.

Btw, please don't send people to http://drupal.org/cvs-account to apply for a CVS account. I've spent countless hours looking for any references to that URL on teh drupal.org site and changing them to http://drupal.org/node/59

So I'd love to know why so many people are bypassing reading node/59 and applying for an account without reading the CVS applications guidelines.

frjo’s picture

frjo commented
Status: Postponed (maintainer needs more info) » Fixed

I have added lut4rp as a cvs maintainer of this project.

And I will be sure to use http://drupal.org/node/59 in the future.

moshe weitzman’s picture

moshe weitzman commented
Status: Postponed (maintainer needs more info) » Fixed

@Ajk - maybe just change the alias to point to node/59 and be done with it.

chadchandler’s picture

chadchandler commented

I've looked heavily into this module , and the extra voting forms module, as well as Drigg and you guys are so close to having the same thing it's crazy.

Really, The Drigg module guy spends so much time on Drigg when really 60% of the work he did was already done here.

Recently I had to create a site that needed a module like this and I went the traditional CCK/Views Route and only used the voting widget portion of this module (not the storylink).

I then, wrote a custom hook that validated the CCK Link Field was unique (like storylink does).

I'm happy to help where I can.

lut4rp’s picture

lut4rp commented
Status: Fixed » Closed (fixed)

Everyone please note: The current HEAD code of the module has the partially unstable code that has been ported to Drupal 6. Please get that code, test it out and help us weed out any issues.
Unless normal issues related to the port aren't fished out, we can't release the 6.x version of the module, let alone work on the newer features that are in the pipeline. Those interested - get to work!

thanks :)