Port to Drupal 6 ---- Drupal-5 support

No, D5 support should last a bit longer than just 3 to 4 months. Have you noticed 4.7 is still downloadable on the main page, and for how long D4.7 has been around now?

Going for 3-4 months Drupal 5.x TTL ("time to live") means: 5.x was only a short intermezzo. A lot of people will need to upgrade from 4.7 to 6 directly!

Any suggestions?

drooppi

To me 3-4 month sounds short as well, but more than anything it depends on how much we and others are willing to contribute pathes to an old release. At best I think we should support it until Drupal 7 comes out, but I'm not willing to promise anything, this is after all contrib, not core - even though it's good karma being a perfect maintainer.

Also, depending on how the release of Drupal 6 and the following port of contributed modules turns out, I can see myself focusing on improving the 5.x release of Advpoll the coming moths, not 6.x. I don't see that as a big problem as pathes can be ported to a newer release as well.

It's worth noting that votingAPI 2 (for drupal 6) is currently in CVS, though not officially released. One of the big dilemmas at the moment is figuring out whether the improvements and changes in it are useful and effective for modules that need to use the API. Perhaps we can chat about this? There are definitely API changes in how VotingAPI is used, though they're mostly syntactical and intended to support more efficient queries, cleaner interoperation between voting modules, and API-level anonymous voting.

Any updates on the progress of this port? Also, is there any chance that the updated D6 version of advanced polls will take advantage of the drag and drop functionality in the core jquery library?

Subscribing so I can keep an eye on this module. :)

Subscribe. Thanks

Subscribing as well - hope to see Advance Poll in Drupal 6 soon :)

subscribe.

It appears that voting API has a 6.x-beta which should hopefully make this easier having a solid base to work from.

Subscribing

subscribing... hope we can get a beta soon!

subscribing too...

waiting impatiently for a release for D6. Advanced poll has no alternatives currently

subscribing

Subscribing.

subscribe

same here, subscribing ;)

I don't have the bandwidth to work directly on the port of this module, but is there any information or assistance I can offer about the D5 to D6 changes in VotingAPI?

subscribing

Subscribing

Subscribing.

Is there any update on the port to D6?

Thanks,

Any news would be helpful. I couldn't possibly upgrade to 6 without Advanced Poll.

subscribing

subscribing

subscribing, too. Looks like you'll have lots of testers. :)

subscribing ....
any news when v6?

subscribing.

subscribing

subscribing

Eh, what the hell. I'll subscribe too. :-)

I've got no experience in module development, but would be happy to help in any way I can with porting to Drupal 6; this module would be incredibly useful for me to be able to use.

So… subscribing.
:o)

... subscribe...

subscribing...

Subscribing :)

Subscribing...

Is this project stalled? Many people have subscribed, yet there is little to no indication of progress since last year. Although I don't know anything about module development, maybe I can help in some way.

Subscribing :)

At this point I would say that yes, the project has stalled. If anyone has interest but no coding capabilities I suggest you create reverse bounty (e.g. by saying "I'll pay anyone who fixes this $50") and then hopefully others will agree and add more amounts and motivate someone to do it.

If anyone has interest and coding capabilities...you should feel definitely empowered to begin working on a port ;)

http://drupal.org/project/deadwood and http://drupal.org/project/coder can reduce the effort involved, though with a module that uses a custom API like votingAPI those modules won't do everything...

Subscribe. I am ready to move to D6 but waiting for advpoll!

Thanks

subscribing.
re #42, I have $50. anyone else?

Same. I'll toss in $50.

subscribing

Our team intrested in porting same of this module functionality to drupal 6. If you wanna donate, we can fully port this module.

You can contact me at nikita.hrybaleu@corp.adsl.by

Perhaps the use of chipin or similar reverse bounty things might be a good idea?

susbcribe

Subscribe and willing to contribute $50

@Electronick, #47 --

If you are serious about porting this module, please set up a ChipIn and link it here. From a business standpoint, I would like to know how much your team wants for the port.

i tried to contact Electonick but my email bounced.

Looks like there is $150 in the pot so far.

Hi Advpoll users!

I hope you do not mind the intrusion, but I have an important announcement to make and this seems to be a proper place. Apologies if you feel this is misplaced.

I have worked on porting the Decisions module to Drupal 6 and the port is mostly complete. For those who do not know that story, Advpoll is a fork of Decisions, so the modules are almost compatible from a database-schema point of view. It would probably be possible to migrate from advpoll to decisions (see #339377) but the "how" remains to be seen.

Advpoll has seen a lot of development after the fork from decisions, however, so do not expect all the bells and whistles to be there. Decisions is a lot more 'basic' than advpoll, but most of the basic features are there and currently pretty solid (apart from the broken preview), so we're still in beta.

I welcome all the advpoll users to try out decisions. We (at Koumbit) are opened to help advpoll users find an upgrade path to Drupal 6, and given the amount of bounty here, I guess it could be done in a fairly short amount of time. We're also opened to implement the features from advpoll missing from decisions, of course, and welcome patches.

We understand the tensions that have happened during the project that led to the fork and are sorry this happened. We hope to better maintain the project in the future to not let this happen again.

In solidarity,

Antoine Beaupré
Koumbit

Wau!
this is such great story for this morning!
Thanks Chris, it will be awesome.

Igorik
http://www.somvprahe.sk

Just saw this and thought i'd leave my comment.
So the same day the forked module's owners says he is inviting everyone back to the original code branch, the new module's owner promptly reacts and says that wouldn't be neccessary because he will start porting his code too right now...
Why don't you both overcome your egos (that is YOU, Chris and Antoine) and try to come up with a fused polling module that contains the advantages of both modules and has an update path for each? Because duplication of code is such a waste of time and resources... and it's annoying to see stuff like this happen, too. Efficiency over pride, guys. You can do it.

I generally agree with #56. We should try to merge the projects back together. Right now, the differences between the modules are subtle but significant: decisions has decision modes as modules where they are ".inc" files in advpoll. Advpoll has seen better developpment in the AJAX support and caches properly borda count results, and there are probably other features in advpoll missing from decisions.

We have decided to port decisions forward the answer the expressed need of a client, and also because we knew the codebase better. We didn't want to compete with advpoll and have long tried to keep decisions in sync with the changes made in advpoll (see SYNC.txt in our codebase), but have gave up after a while, due to lack of available time.

I think that Chris, you still has CVS access to decisions, and you are more than welcome back into the project if you so desire. I think that while the codebase between the two modules diverged and some work is still required to get decisions out of beta, it's still a good base to start from. I wouldn't recommend spending another 10h on advpoll just to get it to D6 while I've already done that on decisions. Then again, I will not tell you what to do with advpoll, of course, you are free to do as you wish. :) I just think that working on decisions at this point would probably make more sense, but I would fully understand if you do not share that perspective.

If advpoll is to be ported to D6 too, then Koumbit will seriously reconsider completely dropping decisions and may start pushing patches to advpoll instead, because we think having such a module functional is important to the Drupal community. I hope some openness will be displayed for our patches, if they come...

Thanks, and sorry again if my posts here were inappropriate.

Chris,

The fact that you have a personal preference for advpoll is normal, but do you have any specific feedback to offer with respect to Antoine's description of the differences between the two projects? e.g. "decisions has decision modes as modules where they are '.inc' files in advpoll. ".

Moreover, as was the case for you when you started working on Decisions way back when, we (Koumbit) would want to have CVS access in order to consider dropping Decisions in favor of advpoll.

By the way, when do you plan to have a production-ready module?

Omar

Chris,

Having not heard back from you, I am pretty confident that you simply aren't interested in merging the two projects.

However, just in case my last message wasn't clear enough I'll re-iterate the key point/question: Are you willing to give Koumbit CVS access to advpoll in exchange for us dropping decisions?

Either way, no big deal. We are happy to continue on our own. We just wanted to give the idea an honest good-faith effort out of respect for the community and the principles of open-source collaboration.

Omar