A meta issue to organize other issues planning 7.x-1.0.

Just to clarify, now that I have received so many times from so many channels: Vote Up/Down project is working on D7 using the vud_field module, that should cover almost all the basic needs, and it is working fine a long time ago. The reason I have never published the dev tarball is because I have not yet make an upgrade path, so people looking for installing the module starting from D7, it should be fine with current code.

7.x-1.x

It will contain the port of all vud submodules, but I will mark it as non-supported unless a co-maintainer would like to help with that. I will also try to add all the existing patches in the queue fixing things for them.

7.x-2.x

It will contain only vud and vud_field, which may replace all the others as I originally proposed, but the initial version will not migrate from vud submodules to to vud_field. Please notice the open issue #1363928: Upgrade paths from vud_{node,comment,term} to vud_field about that, patches welcome!

  • Try to include specific features from vud_{node,comment,term} in a generic way into vud_field if possible.
  • Bug fixing from previous release.

About D8, I posted a GSoC project to mentor, to bootstrap that, and hopefully it gets accepted, but general notes on the main issue about that and some related commits on the canonical issue #2843192: Port vote_up_down to D8.

Comments

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented
Title: [meta] Roadmap for 7.x-1.0 » [meta] Roadmap for 7.x-1.0 of Vote up/down

...less vague title for the dashboard.

Fidelix’s picture

Fidelix commented

marvil07, do you think it's possible to use the current vote up/down code in a project that's still being developed, but going to production on a few weeks?

marvil07’s picture

marvil07 commented

@Fidelix: If you are starting with D7 vud_field, it should work, but I will not release a beta1 until we have what's on the beta1 section. And yes, you are completely welcome to try it hard and find bugs :-). In the other side, I would appreciate if you can open new tickets for support questions.

Fidelix’s picture

Fidelix commented

Alright, sorry about that.
I won't need an upgrade path so I'll bet on it...

timcosgrove’s picture

timcosgrove commented

Hi there-

We're interested in using Up/Down on a couple of D7 projects. Are the 7.x issues things that you could use extra hands on, or are they things that need to be done by you, that you just need to find time to do? We can probably find some resources to throw at issues if that would be welcome.

Thanks,
Tim Cosgrove

marvil07’s picture

marvil07 commented

@tim.cosgrove: Hey, I am completely open to receive patches! :-), specially if they are on #1363928: Upgrade paths from vud_{node,comment,term} to vud_field ;-)

Yep, my problem is plain time allocation :-(

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented

@marvil07: Hey Marco, could you please consider opening a 2.x branch for the field way and leave the 1.x branch be more of a straight port of how things worked in 6.x? That would help #1194274: Port vud_node to D7 / #1402758: Remove user votes page in favour of views move on. This way, perhaps a 6.x to 7.x migration path could be possible in the future.

Thanx beforehand for considering ;)

MauPalantir’s picture

MauPalantir commented

Hello. We also have a project that would use VUD with Drupal 7 in a few weeks. So if you say it is more-or-less production-ready (with an eye on testing and willingness to find/fix bugs of course) then I am very happy and will post here if I get something.

MauPalantir’s picture

MauPalantir commented
Issue summary: View changes

Updated issue summary.

mxt’s picture

mxt
Primary language Italian
Location Milan
commented

The reason I have never published the dev tarball is because I have not yet make an upgrade path

I think is time to rethink your position: IMHO is better to release the D7 DEV on project page the encourage other developers/users start using this module and helping resolving issues.

Please give a CLEAR possibility for (increasing number of) people starting new projects in D7 to use your module: I think now most of them simply lands on your project page: can't see any D7 version, then abandon the page: you can't hope that everyone starts checking the issue queue to find that a DEV version is available.

For the unavailable upgrade path you simply can put in evidence an advice always in the project page (like others maintainers for others modules do in similar cases).

If you want a sprint, you have to reveal things, not hide them...

Just my 2 cents

NathanM’s picture

NathanM commented

I would agree. I landed on the issue queue because it now lists the D7 version as
"Project not supported: This project is no longer supported, and is no longer available for download. Disabling everything included by this project is strongly recommended!"

It is going to be very hard to attract developers to help fix the final issues if it appears that the project has been abandoned, (it hasn't been abandoned, has it?).

marvil07’s picture

marvil07 commented

@NathanM You have a good point on update status module, so I will be rolling the dev release pretty soon and updating the project page with relevant information.

bendygirl’s picture

bendygirl commented

@marvil07 I hate to be one of those people, but "pretty soon," can you tell me when that might be? I'd be happy to try and pull together a sprint to see if we can't get a few folks together to work on the bugs and help you out. So, if it's soon, and we're talking a week or two, can we do a sprint and see if we can help?

bendygirl’s picture

bendygirl commented
Issue summary: View changes

A big notice to, hopefully, stop people asking about a functional D7

marvil07’s picture

marvil07 commented

I have just released an alpha1, and make the dev tarball visible on project page(it was available from March 11, 2011).

@bendygirl, any help is welcome, I try to be open, so all my plans are on issue queue. You can find there what I am trying to do and please, help ;-)

marvil07’s picture

marvil07 commented
Issue summary: View changes

Updated issue summary about new released alpha1 for D7.

  • marvil07 committed 5de154e on 8.x-1.x authored by cpliakas 
    Issue #877392 by cpliakas, marvil07: Add a hook that allows modules to...
  • marvil07 committed 6e2a676 on 8.x-1.x
    Issue #847846 by mansspams, marvil07, jaydub, monotaga: Provide 'Reset...
marvil07’s picture

marvil07 commented
Title: [meta] Roadmap for 7.x-1.0 of Vote up/down » Roadmap for D7 of Vote up/down
Category: Task » Plan
Issue summary: View changes

@klonos et al: I should have taken your suggestion on just creating a new branch a long time ago.

Updating issue summary to reflect mainly the decision I made to do that.

  • marvil07 committed 5de154e on 7.x-2.x authored by cpliakas 
    Issue #877392 by cpliakas, marvil07: Add a hook that allows modules to...
  • marvil07 committed 6e2a676 on 7.x-2.x
    Issue #847846 by mansspams, marvil07, jaydub, monotaga: Provide 'Reset...
marvil07’s picture

marvil07 commented
Issue summary: View changes

Linking the right canonical issue about D8.

marvil07’s picture

marvil07 commented
Status: Active » Fixed

Closing this issue now that there is a stable.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.