Another plugin removed from WP.org extend directory [Me too]

[KnxDT]

More changes:

I removed any kind of link to my site. There's only one link and it's disabled by default now.

Even better: There's no links to my site anymore. I don't want problems... I removed my credit link... In fact, I'll remove any kind of face-front link in this moment.

[Ryan]

Even better: There's no links to my site anymore. I don't want problems... I removed my credit link... In fact, I'll remove any kind of face-front link in this moment.

Don't worry. You are clearly not a spammer and are one of the good guys :)

That became blindingly obvious not long after this topic started.

[KnxDT]

Don't worry. You are clearly not a spammer and are one of the good guys :)

That became blindingly obvious not long after this topic started.

Thank you, Ryan, I really needed a little support. Thanks to all the WPTavern's users that helped me with this problem.

I can understand that the people that doesn't know me could think that I'm like the devil or a lame-dirty-noisy spammer, but I just needed to know what was wrong... Then I tried to do the necesary changes, but it seems to be not enough.

PS: Thanks to Chip support (via Twitter) also.

[Ryan]

I think a lot of good will come out of a few of these hiccups that have occurred recently. It's all good and well for someone to jump up and down by themselves ranting that their plugin should be allowed in and whining about problems, but without others such as Chip, Jeff and others agreeing and taking those developers concerns to the powers that be, those concerns have likely been dismissed out of hand in the past. So hopefully some action will be taken now to ensure that this situation is improved.

[markjaquith]

How to get your plugin removed from the directory

You can use this as a "I got rejected and I don't know why" cheat-sheet!

[Ryan]

Awesome. Thanks Mark :)

[chipbennett]

I'm curious, reading through today's irclogs, how I could have been construed to have "rushed" to defend him. In fact, I didn't even publish my blog post until after he had resolved his situation with MarkR.

In fact, KnxDT had resolved his situation with Mark around 1:30 Tuesday afternoon, and I didn't publish my blog post until Tuesday evening.

And, further, the point of my blog post was not to "rush" to anyone's defense, but rather to bring attention to the inconsistency regarding plugin license disclosure and to suggest a solution to resolve that inconsistency.

The first time I actually came to KnxDT's defense was yesterday (Wednesday) evening - a day and a half after he had already resolved his plugin situation. And I rushed to his defense against a baseless accusation of being a "dirty spammer" - not about his plugin situation.

Or, perhaps I am lumped into the group Matt describes as "good arguments made in bad ways (the asshole problem)" - though, again, I question being associated in that way.

Did I post a somewhat sensational tweet, regarding percentage of plugins by Matt et al that disclose license information? Yes.

But the point was to drive traffic to my article, so that people would read what I wrote - and what I wrote was not an attack of anyone, but rather a suggestion for how to improve the system. Did I make "a good argument in [a] bad [way]"? I don't think so. I'm not sure how I could have more clearly illustrated the inconsistency I was discussing.

I never claimed that MarkR was a bad person for removing plugins from the directory. I never claimed that Matt et al were bad people for not explicitly disclosing the license for their plugins. I simply pointed out that plugin authors were at a disadvantage in being able to comply with the de facto guideline being enforced, and suggested a means to remedy that disadvantage.

I'm just highly confused by the whole situation.

[Jeffro]

I am as well. That's why I've taken Aleve and called it a night.

At this point, you might want to just send an email to matt with your confusion post and see if he can help you out by suggesting other recourses of action you could have taken?

[Ryan]

They're just not reading things through as they're too busy doing other things.

You might find it better to approach them in a different way. I guess some of them see your comments as an attack, even though they're obviously not.

[andreasnrb]

The reactions are perfectly inline with behaviors in the past. Just take the whole privacy , core plugin debacle.

They're just not reading things through as they're too busy doing other things.

I have a good solution for this. If you don't know what you're talking about keep quiet =). Community can rant all they want, the leadership should not.

Or, perhaps I am lumped into the group Matt describes as "good arguments made in bad ways (the asshole problem)" - though, again, I question being associated in that way.

I would guess they think I'm part of the asshole brigade also . I've been lumped together with a much worse crowd than you Chip in the past .