Some Thoughts On Community

[chipbennett]

Been needing to get this off my chest. Tried to write it as objectively as possible.

Here's just a teaser (the conclusion):

This is no way to build a community.

All of these actions, behaviors, and attitudes are damaging to the WordPress community. Because of them, would-be community members are driven away, less code that might benefit the community is contributed, and WordPress users are left exposed to security vulnerabilities. Because of them, new and non-expert developers are discouraged from attempting to contribute. Because of them, opportunities to reach out and to bring others into both the WordPress community and the free-software philosophy are squandered.

Free software projects (and the communities built upon and around them) are best-served by attracting to the community all who would participate – whether that participation is contributing code, just using the software, or somewhere in-between – by encouraging contributions from all who would contribute, and by displaying patience, understanding, and a willingness to help such contributors when they make mistakes as they are learning how to contribute.

Rather than close-mindedness, display acceptance, understanding, and tolerance. Rather than arrogance and condescension, display respect, humility, and a willingness to forgive. Rather than hypocrisy, display openness and truth. It is in an environment that displays such attitudes that a free-software community can best thrive, and in which the most noble and well-intentioned principles of free-software philosophy are exemplified and promoted.

[Jeffro]

Well done post summarizing the events of the past three weeks, especially with those plugin authors. It was an enjoyable read and I couldn't agree more with your conclusion.

[MiroslavGlavic]

I am 101% completely against you trying to defend the guy who forced people into subscription into his marketing e-mail list, which some got daily e-mails. The majority of marketing lists ARE spam. Daily marketing e-mails ARE spam.

People who downloaded their plugins did not want the e-mails, specially the ones who got them daily.

People who force users to subscribe to their website/e-mail lists, force users to add links on their sites to the author's site shouldn't be on the community.

Also people who put base64/code64 crap.

I choose to keep the link on the theme that I am using on my sites.

So according to you this guy should be let back in, even though he did something bad.
What about those base64/code64 authors? How would you feel if you download a plugin that has some encrypted crap that will randomly post links on your sidebar to the author?

The arrogance is you who is trying to defend this guy for what he did. In more than just this thread.

[andreasnrb]

I am 101% completely against you trying to defend the guy who forced people into subscription into his marketing e-mail list, which some got daily e-mails. The majority of marketing lists ARE spam. Daily marketing e-mails ARE spam.

He has never defended what he did and hes not really defending him either. You really don't get it do you? And you show complete lack of knowledge of what constitutes spam. Its not spam because you don't like the email. Spam is unsolicited bulc emails.

People who downloaded their plugins did not want the e-mails, specially the ones who got them daily.

There was a unsubscribe link at it was double optin. He did not violate the CAN-SPAM Act
They knew perfectly well that they were signing up for a list when they got the email. He used AWeber I think and they are very strict.

People who force users to subscribe to their website/e-mail lists, force users to add links on their sites to the author's site shouldn't be on the community.

Also people who put base64/code64 crap.

No one was actually forced. You couldn't use the plugin if you didn't signup but that is hardly forcing. Its more like paying for the plugin.
All the current issues could easily have been prevented by having a easy to understand checklist that plugin/theme authors can check and agree too before adding their plugin to the directory. But this is for some reason to hard to do and a couple of years is not enough time to accomplish this.

I choose to keep the link on the theme that I am using on my sites.

Most people are not given a choice. They probably think they have to keep it.

The arrogance is you who is trying to defend this guy for what he did. In more than just this thread.

He has never defended what he did. Read again. No one has defended what he did really. Your behavior is exactly what hes writing about.


And if you only focus on the guy with the optin plugin you really really don't get it. What about Alden whos plugin was removed for being insecure but the original plugins stayed? You should look beyond your dislike for marketers and see the bigger picture.

[Jeffro]

And you show complete lack of knowledge of what constitutes spam.

The arrogance is you who is trying to defend this guy for what he did. In more than just this thread.

Come on, do we really have to travel down those roads? Let's leave personal jibes out of this. Too much of this going on in the forum lately. It's no way to hold a conversation.

I agree that no one is defending what the Max Blog Press author did. BUT, based on what is public knowledge, I believe the Max Blog Press guy received an unfair shake. Also, let's keep in mind that the plugin existed on the repository prior to being taken down so at some point, the plugin was accepted into the repository despite whatever the guidelines said at the time. Who knows, maybe the first version was completely within the guidelines.

At any rate, the unfair shake is that the MaxBlogPress plugins were removed and from what we know, he was not given a chance to make the corrections/changes in order to be compliant with the guidelines in respect to the mailing list activities. Also, after the reasons were explained to him as to why the plugin was removed, he went ahead and changed the plugin to not only please those who were complaining about it in the forum, but to allow the plugin to be reinstated on the repository. However, he was told that despite his changes, his plugins were banned from being hosted on the repository. This situation is why I've been asking how hany strikes plugin authors receive before the ban hammer is dropped. The other two plugin authors that Chip summarizes in his post were able to communicate with MarkR and others in order to rectify their situation. However, MaxBlogPress received a ban hammer even after making the necessary changes.

This has me wondering whether we don't know an additional piece to the puzzle. One that would explain why he got the ban hammer but the other two plugin authors did not. Is one broken guideline more severe than another? If I have some free time, I'll try to pop in IRC to ask Mark R these questions to see what he says.

As for SPAM. Spam has a definition but it is not concrete. For example, if I set up the WPTavern forum to have email notifications of threads enabled by default, registered users would be receiving a bunch of emails and not have any clue as to why that is. They very well could consider that Spam. So I see spam as subjective and it's usually on a case by case basis. What the plugin author was doing was wrong, everyone agrees with that point. But the focus is on why that plugin author was banned after making the necessary changes.

[MiroslavGlavic]

Bingo, different people define spam differently. I define it as daily marketing e-mails.

The fact that he has an issue with the guy not being let again is sort of defending him. That's the way I interpreted. Would you give the base64 another chance? I do believe that once a spammer always a spammer.

By the way, if other plugin authors did the same thing as maxblogpress guy. I would be saying the same thing.

It could be that one staff/moderator/whatever interprets the rules more strict than others.

Just like many themes get deleted, yet the twitter/facebook look a likes that I pointed out are not.

I find it disgusting and against the spirit of the community to ask for your e-mail to activate a plugin.

None of us have all the pieces of this story by the way.

[Jeffro]

Would you give the base64 another chance?

He WAS given another chance and is now happily hosted within the plugin repository.

[andreasnrb]

Come on, do we really have to travel down those roads? Let's leave personal jibes out of this. Too much of this going on in the forum lately. It's no way to hold a conversation.

Yeah that was a little rude. I apologize. Usually keep a cool head.

Bingo, different people define spam differently. I define it as daily marketing e-mails.

There is a most used definition if we stick to it we all know what we are talking about. The primary tell on spam is that it is unsolicited.
That you don't like daily marketing emails is one thing but don't go around calling it spam when it ain't. It causes confusion, dislike and what not.

I find it disgusting and against the spirit of the community to ask for your e-mail to activate a plugin.

Try to keep things like "spirit" out of the discussion and lobby for stricter rules and better terms of service on wp.org instead and indiscriminate actions if someone violates them. Spirit is to fuzzy and undefined. These last weeks has brought forth a number of criterias that was unknown before. It would be great if they were added to a easy to read list on the add you plugin page on wp.org.

[MiroslavGlavic]

He WAS given another chance and is now happily hosted within the plugin repository.

He = maxguy?

[Jeffro]

No. KnxDT

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