Change project ownership of whizzywig module

The ownership of the project has been passed to drupal-id.com.

Hm. This is a bit unfortunate. #419142: Add a note to avoid confusion between Whizzywig and Wysiwyg was the agreed on way forward a long time ago.

Is there any particular reason why we need to duplicate efforts?

The ownership of the project has been changed upon request of the previous maintainer. I wonder why the previous maintainer agreed to mark the project as abandoned, and then decided to pass it to somebody else.

Hi,

Here's some explanation from my part:
drupal-id.com contacted me a few times with the request to take over the Whizzywig project. At first I replied that it would surely be better to join efforts and contribute towards the superior wysiwyg API project, but after drupal-id.com kept requesting to take ownership of the module I filed this ownership transfer request. It was pretty clear from the communication with drupal-id.com that he was not prepared to contribute to the wysiwyg API as an alternative, and if i'm not mistaken he was probably going to create a new project anyway if I should have been unresponsive to the handover request.

If I read correctly the Whizzywig Drupal module comes with an altered version of the Whizzywig javascript library, so I don't think a merge of efforts would be easily doable.

It's unfortunate that the notification that linked users to the WYSIWYG API module has been removed from the Whizzywig project page. Perhaps drupal-id.com can at least agree to add a link to the WYSIWYG API module.

the person or the collective known as drupal-id.com has had a rather difficult past WRT Drupal and JS based editors...

They are not able/interested in collaboration.

I apologize for this problem.
It was me to pass the ownership of the project, and I did it not knowing the report opened by sun (which was already closed when I made the change), and because the request came from the actual maintainer.

Maybe it was better to mark the module as abandoned, rather than keeping the ownership of the project to svendecabooter.

It is also my fault to not check if the project was reported as abandoned before to change its ownership. I checked if the user who agreed to change the ownership of the module was the current maintainer, but not what it was reported in the project page.

@sun: I apologize for my mistake; if I would have been more careful, I would not have done this mistake.

I marked the project as abandoned, and added the warning as required.

As the project was de facto abandoned, the previous maintainer could not have decided to whom pass the ownership of the module, especially in such case. It has been only my mistake to change the ownership of the project.

Sounds good -- as long as drupal-id agrees (who may not even know of this issue). ;)

The project maintainer info block says last commit 8 weeks ago, 192 commits in total, and it seems a couple of releases were created.

While I'd - of course - totally love if drupal-id would contribute to Wysiwyg instead, it seems we already passed the line where we cannot simply revoke already granted project ownership and maintenance. Sorry also from my side - I should have looked this up and followed up earlier.

Not sure what to do now. But I guess we need to revert the status of this issue but also the abandoning changes to the project...?

@sun: If you think that returning the ownership of the module to drupal-id (he already knows I marked the project as abandoned), then I will do it.

I am just trying to fix a mistake I have done, but clearly I reacted too late.

heh, I'm slightly confused now. :) If he already knows and actually agreed to abandoning the project, then I guess all is fine. If, however, he didn't really want to do this, then I think we cannot prevent him from maintaining the code, project, and releases he created in the meantime.

Last note: http://drupal.org/project/usage/whizzywig lists a usage higher than "almost no one", so at least the releases should probably stay published/visible. (Actually not sure whether that "Enable releases" checkbox also affects Update Status.)

I didn't say he agreed. ;-)

I changed things as they were before. Again, I am really sorry of my mistake.