Any plans for a D7 version? I'd certainly find it useful.

Comments

rdeboer’s picture

Maybe it should be part of Workflow itself or the Workflow Extensions module....

bfdi533’s picture

Agreed. But, since it is not part of workflow, can a D7 version please be made available?

kurkuma’s picture

Check out Workflow import.

rdeboer’s picture

@kurkuma,
I believe it is common Drupal practice to contact the maintainer offering a patch or extension to an existing module or to talk about working together rather than duplicating it and confusing everybody.
Rik

kurkuma’s picture

Fair enough. As it changed the philosophy of the module regarding the user interface and admin approach I developed a separate one. I will have no problem to create a patch form the existing code and merge efforts. Also I wanted to just do importing of workflows, and your module has an open end functionality to other post install tasks.
Just let me know.

rdeboer’s picture

I would have been happy to give you Git commit rights (and still am) if you had just contacted me.
The damage is kind of done now in that the confusion has been created with similar functionality now in two projects.
But I'm happy to put a link on the "Workflow post-install" page to your project page to clarify things for people finding one but not the other module.
Are you going to do a D6 version of your "Workflow Import"?
Rik

kurkuma’s picture

Not at all, no D6 version planned.
One of the problems with the creation of the module is the sponsorship. That is the main reason to have a separate project.
If we opt for keeping things as they are we could put links referencing each others module.

rdeboer’s picture

... the sponsorship... is the main reason to have a separate project

I am not impressed with this argument.

Basically you are saying that you've used my D6 original and deliberately created a new project for a D7 version, when you could have offered your code as a patch/extension to the existing project. This is not according to Drupal practices.

But worse is the reason you did it: so that you and you alone could make money out of extensions to my code.

Is that in the spirit of Drupal and Open Source?

kurkuma’s picture

So, you will keep arguing for the sake of it. I have agreed with you, I have given you my reasons (like them or not, but valid), and I do not mind to merge. And yes, there was extra work beyond porting it to D7. If you want to make something positive from this just let me know. I am up for that. What I do not have time is to endlesly engage in petty discussions for the sake of it. This is not taking us anywhere.

achbed’s picture

How ironic. I was looking to do a very similar thing to the D6 version as the installation I need it for is not upgraded to 7 yet. In fact, my latest patch/rewrite of the D6 version is in preparation for that. So instead of having one module that we're all working on, we now have forked versions everywhere.

rdeboer’s picture

Status: Active » Closed (won't fix)

@achbed, #10: Hear, hear ...