I was just checking the status of my sites all of which use WYSIWYG image upload and was shocked to find that it is not supported due to a political issue (with no explanation of what it's all about, not that it matters). I'm surprised that's even possible, but it is surely not acceptable. I use this module on many sites on which I base my income, so you need to understand that this is causing me and thousands of others, a major unnecessary headache and is costing us money. If I pull this module I have to find another way of uploading images, and retrain my clients. That is a major embarrassment for my firm and for Drupal.

If you have some problems with the way Drupal is governed, why do you have to make others pay the price? Why don't you hand over the responsibility for future management of the module to someone else and just walk away?

The work you did on this is very much appreciated and it's a great module, so to see this happen is a terrible shame.

Comments

EugenMayer’s picture

EugenMayer CreditAttribution: EugenMayer commented

Just to sum it up, you basically tell me that:
I owe you something / am responsible for your buissiness because you downloaded this module?

Or in other words, i put hours and hours in this stuff, which you simply downloaded and used. When it comes to the fact, that you need to download the module from a different place then drupal.org, you come arround and punish me / make me responsible for you being not compfortable with the situation.

You want a maintainer to:
- do the work, work on issues, work on features
- take any beatings on this road
- be in place when SA arrives, stop anything else to secure your sites running up and fine
- the maintainer should not have any feelings, rather act as a machine
- the maintainer should always act on the behalf of the community, no matter what

Basically, you ask me to be your slave. Slaves have work under similar conditions, while getting paid zero money.

The work you did on this is very much appreciated and it's a great module, so to see this happen is a terrible shame.

Or in other words: "I dont care about you at all, all i want is this module to do its job. Period"

Seriously, why the heck should i ever contribute anything into this community....

bohz’s picture

bohz CreditAttribution: bohz commented

Can someone help me understand if the development of this module is still active (and where) or if I have to replace this module with something else?
Thanks a lot in advance

EDIT: OK, I checked the google cache for the project page (d.o. is somewhat down atm) and I learned the project is active on github.
It's a pity that things went this way, really.

Thanks

EugenMayer’s picture

EugenMayer CreditAttribution: EugenMayer commented

@bohz: I will setup a fserver/ project page, were you can simply download the relase. With the "update-url" syntax in the info file you will be notified about updates the same way as you used to with drupal.org

alexbk66-’s picture

alexbk66- CreditAttribution: alexbk66- commented

It's a great module and I do "respect the will of the author to not further distribute on drupal.org", but I wonder if it's possible to sort out your issues and return back to normal? Why almost 3000 users should suffer and get "Project not supported" red messages in their Status Update?

EugenMayer’s picture

EugenMayer CreditAttribution: EugenMayer commented

@alex: this case is absolutely closed. I dont have any developer-access to drupa.org anymore, and actually i wont need.

There is in addition no need to distribute to drupal.org. This module is not gone, the place to download just changed. I have no idea why people start having such heavy feelings about exactly that fact.

druplicate’s picture

druplicate CreditAttribution: druplicate commented

Those so-called "heavy feelings" amount to this:

Major inconvenience to a few thousand developers because you've got a bug up your a** about how Drupal is run. None of us could give a rat's a** about your political issues. So it appears you've decided to punish the Drupal project by taking your toys and leaving the playground, which as far as I can see was totally unnecessary. All you had to do was solicit another maintainer and walk away.

Having the project code hosted elsewhere is a pain because we can't use Drush to maintain it, and it's another detail we have to deal with and catalog somewhere. Drupal doesn't tell us when the code has been upgraded - I would have to periodically check your site.

Many of my clients have policies that don't permit using unsupported code (as does my firm), so as soon as they see those red warnings, they freak out. And try as I might to explain that the code will continue to be managed elsewhere, they are right to question that scenario because if you get hit by a bus tomorrow, there's no way anyone within Drupal could pick up the pieces and continue on.

If you intended to give the Drupal project a little bit of a black eye, you may yet succeed, so I would hope that someone higher up will disallow maintainers from pulling their code in this fashion in the future. It's frankly hard to believe such safeguards aren't already in place to prevent this from happening. Suppose this was the Views project, for example - Armageddon for sure.

But you've really only managed to shoot yourself in the foot, as your name is now pretty much mud in many circles.

EugenMayer’s picture

EugenMayer CreditAttribution: EugenMayer commented
Status: Active » Closed (fixed)

You are talking about Drupal as a product. Until you dont pay a cent - you cannot judge it like that and you cannot expect others to jump into the responsibilities _you_ have against your customers. I dont frankly care about your customers, as you will not care about my customers either. And we dont need to do this as commercial entities.

I dont have any relationsship as any kind of service provider, nor drupal.org has and you should start to realize that.

I could have simply broken the module into small pieces, stop maintaining it or even just refuse to fix any issues at all. That would be one of the alternatives i would have a developer and NOT as CEO and not at all as a contracted service provider of you ( which iam not ). If you would have loved to see that happen, so simply blocking the module, not maintaining it anymore, well i have to say, iam not sure thats the better alternative.

I have taken the code to maintain it somewere else. If you dont feel compfotable with this decision for something you dont have any warranty for, you did not pay anything and which is build on my free time, you just go forward and chose any alternative.

You seem to be one of those who just take and not giving back anything, not even feeling thankful at all.

To finish it, i don`t care, as a developer, that the SA team member dont here my name with a smile anymore, or 1000 of people i dont know ( and who dont know me ). I dont have anything in specific of hosting on drupal.org, i dont have anything of giving you this project for download.
I did this in return for what i got, drupal. And what did you in the mean time?

By the way, the code is still on d.o, it cannot be removed and it has not been removed by me. It has just been virtually moved, means the last checking removed the files and that can be reverted on the SCM level. But whom i telling, you wont know anything about this anyway, your on the sales team, placing claims on places of where the personal credits and voluntary and freedome is the only "charge" you have.

this ticket is closed, no need to waste my time with those arguments.

alexbk66-’s picture

alexbk66- CreditAttribution: alexbk66- commented

@EugenMayer - you really behave like you are having a PMT or just a bad day. Seriously, this is pretty childish, thousands of developers contributed to the Drupal development and nobody asked for appreciation.

alexbk66-’s picture

alexbk66- CreditAttribution: alexbk66- commented

Can somebody just become a new maintainer of the module and continue on d.o.? And let EugenMayer do whatever he wants wherever he wants?

EugenMayer’s picture

EugenMayer CreditAttribution: EugenMayer commented

What about you guys, stop talking, stop telling others to do something you want and finally

maintain the module yourself?

You are just talking, giving others tips for how to behave, how to be a good maintainer and what is best for everybody. Why dont you both prove yourself your tricks work out in the reality?

So basically do, what you seem to have is pretty good practice in maintaining, as you seem to have a lot of tips left for others: So maintain

ascii122’s picture

ascii122 CreditAttribution: ascii122 commented

The module kicks ass regardless of politics or whatnot. Thanks for writing it man.