logo
  • Home
  • About
  • Plugins

Subscribe to Articles

What’s the point of community

Author: andrew Category: General Tags: Themery

Wednesday
Dec 17, 2008

The hoo hah about themes and GPL and community is still ongoing. I’ve been having a discussion about charging for WordPress themes over at XFEP, but I thought I should explain my point of view. So here it is.

I aim to be very logical and direct in most cases; therefore I will first attempt to consider what I think are the relevant points.

Question one: What is WordPress.org?

WordPress.org refers to:

  • the WordPress software;
  • the open source WordPress project;
  • the community centred around the open source WordPress project; and
  • the domain that gives a home to the open source WordPress project.

Question two: What is the open source WordPress project?

The project consists of the management of contributions to the WordPress core code that make up the free (as in money) WordPress software. These contributions are provided by a wide range of individuals who contribute to the project either in their spare time, or as part of their employment with firms that generate an income from WordPress related products or services.

Question three: What is the community centred around the WordPress project?

This is where things start to get tricky, and why this post is titled as it is. This is where people will begin to disagree.

I think we can all agree that: The community is a group of individuals who share an interest in the WordPress project.

I think we can also all agree that: An individual’s interest in the project may be intellectual, personal, professional, or financial.

I have excluded commercial deliberately as I do not believe anyone can have commercial interest in (i.e. own part of) the WordPress project. Note that when I refer to the project I am still referring to WordPress the software, and not the general contributions of the community.

I think it is reasonable to divide the community into two here in order to differentiate between the directly engaged community, that is, the people who blog about WordPress, and contribute to the repositories, and forums, and the wider WordPress community that use it, sell it (such as web designers that base sites on it), or develop based on it. This division is important for my view, but, even though you may disagree with my view, I think this step is reasonable.

So far then I have explained the community, in reference to other parts of the project, in the way shown by this diagram:

wordpresscommunity

For the rest of my discussion about the community I want to exclude the wider community and focus on the directly engaged community (The Community).

Question four: What is The Community?

Here I need to examine what it is that I think any community is. Not just this community, but any community. It is a little theoretical so I hope you will excuse me.

In 1986 McMillan & Chavis put forward a theory of Pshycological Sense of Community. They defined it briefly as:

a feeling that members have of belonging, a feeling that members matter to one another and to the group, and a shared faith that members’ needs will be met through their commitment to be together.

More specifically they attributed community to four central elements:

  1. Membership
  2. Influence
  3. Integration and fulfillment of needs
  4. Shared emotional connection

You can read more about the paper and the follow-up here.

So what does this mean?

It means that The Community is, as all communities are, a group of people with similar needs that contribute to the whole in order to benefit from the contributions of others. They give influence over others in proportion to their contributions and likewise expect to have a level of influence that is proportionate to their own contributions. Receiving influence is in some ways compensation for taking less than their contributions.

Within The Community each person expects others to be considerate to them as they are considerate to others; however, this consideration is a matter of faith and so once shaken can result in severe consequences such as significant disillusionment, a feeling that the community no longer supports them, and a desire to retaliate.

The Community is about the balance of give and take. This I think is the crux of the matter.

Question five: What does this have to do with anything?

If you are a member of the community what is it that you value?

Depending on how you view the WordPress community, what you value, and what you view as a contribution will determine whether you think excluding items from a repository for reason X is a good thing or a bad thing. You are likely to feel very strongly about it either way. For example:

Do you agree that: A person that makes a plugin freely available is appropriately compensated by the thousands of other plugins and themes that are available to him for free?

Do you agree that: A person that makes a plugin freely available is appropriately compensated by including a link back to his website on every website that uses the plugin in addition to the thousands of other plugins and themes that are available to him for free?

Do you agree that: A person that makes a plugin freely available is appropriately compensated by including a link back to his website on every website that uses the plugin if he is using that to advertise a paid product or service, in addition to the thousands of other plugins and themes that are available to him for free?

Do you agree that: A person who makes a theme freely available is appropriately compensated by the thousands of plugins and themes that are available to him for free?

Do you agree that: A theme author who makes a theme available is only appropriately compensated by the community by having those individuals that want to use the theme pay for using it, despite the availability of the thousands of free themes and plugins that are available to him?

Do you agree that: A theme author who makes a theme available is only appropriately compensated by the community by having those individuals that want to use the theme pay for using it, and by using the community website as a platform to advertise, despite the availability of the thousands of free themes and plugins that are available to them?

Do you agree that: A theme author who makes a theme available is only appropriately compensated by the community by having those individuals that want to use the theme pay for using it, and by using the community website as a platform to advertise, and by including a link on the website of every person that uses the theme to link back to their own website despite the availability of the thousands of free themes and plugins that are available to them?

Do you agree that: The community receives fair compensation from an individual who releases a theme for free, that puts a link on every page of every website that uses the theme, where that link links back to a website promoting a product or service that the individual will be paid for, despite the availability to that individual of thousands of themes and plugins offered for free by the members of the community?

What I take from this

There are a lot of situations and questions there. They are intended to stir thought, not make a point. My point is simply what I think.

I think premium theme authors, who have put more resource into creating a theme than they can support through spare time alone, deserve to be compensated for that effort above and beyond the content that the community provides, assuming the content provided by the community represents only that spare time, i.e. is of a lesser value than the premium theme author can recoup from the community. They should be able to sell their themes for an appropriate cost to recoup the difference between what the community provides and the extra they have put in. Capitalism will decide how much is fair.

I think that releasing free themes to the community with the intent to advertise, via a link to a website that offers paid services, is reasonable provided the creation of the theme expended sufficient additional resource to equal the value of the advertising provided by the community. Given that this is very complicated and cannot be policed I do not think it should be permitted (from the community repository, but from their own website they can do as they please).

I think that premium theme authors are a valued part of the community and so should be permitted advertising space in order to advertise to the community, but, not as part of any product that is provided through the community, and clearly marked. Theme prices should be lowered accordingly to reflect the value of the advertising that the community is providing.

Summation

These are views I have come to by thinking through the principles. I have excluded any reference to the individual’s involved in the premium theme market, the repository, or any other aspect and I have very explicitly excluded any reference to the GPL as I think it is a sofa sized red herring in the whole debate.

Obviously the answers I have come up with a very theoretical as well and certainly wouldn’t be usable in the real world, but by coming up with these answers I understand better where I stand and why it is that I felt that the decision to remove themes that link back to sites offering paid services was a reasonable one in the first place (assuming that that was the intention).


Share:
image image image image image

Comments

David Peralty (http://brandingdavid.com)

December 17th, 2008 at 11:48 pm

I guess we will just have to agree to disagree on this. I don't see things in this matter even close to the same as you regarding how themes and plugins should be managed on community sites. I think that denying premium themes access to the features that have been implemented in WordPress though not allowing them to put their theme on WordPress.org's plugin and theme repositories is a bad thing. I think that the fact that Automattic makes HUGE money on WordPress, and works on ways to limit or deny other contributors the same opportunities is horrible. I agree with many others that a company that is generating profit shouldn't be leading an open source community because they will always make movements to secure their profits. And this goes double for a company that is partially supported by VC money.

This is just my two cents that could be part of a much longer, and well thought out post on this topic. You bring up some great points, but I think you've totally avoided the business issues in this conversation which are only important because they are the motivations behind the movements that Automattic is taking with the company and as such, the project and software.

Andrew Rickmann (http://www.wp-fun.co.uk)

December 18th, 2008 at 12:01 am

Interesting. I have not avoided those issues I just think I see a very clear separation between Automattic and WordPress.org; although, I have argued in the past that there is a conflict of interest, even if they don't act on it, because of this kind of thing. Interestingly few people agreed with me then.

I honestly think that everything that has happened with the repository has been because a member of the community (who just happens to be employed, or own, Automattic) thinks it is genuinely in the best interests of the community. I also think that Automattic is suggesting people do exactly as they do, that is, give away the code for free and charge for services.

As you say though we can agree to disagree. I don't feel particularly strongly about this issue as I am a big fan of most of the premium theme authors and personally find the repository useless, but I do feel that this issue has really lacked a considered and unemotional view. Hence why I tried to produce it.

I understand Jeff is interviewing Matt on WordPress Weekly Tomorrow though, so we can see what he says.

Monika (http://www.texto.de/)

December 18th, 2008 at 1:25 am

Auttomatic is the business behind WordPress - I can't understand why one business is better than another. wordpress.com is a big business market place - Matt is the chief of both - I'm a webdesigner- and I'm a WP professional woman- I earn money with WP - not so much as Auttomatic but I do ;) -

in your logic no webdesigner is allowed to link back to its website - if he spent a WP Theme back to the WP community.
in your logic no link from wordpress.org to wordpress.com - and so on..

GPL doesn't mean : you are not allowed to earn money - but this days I have to realized : big business yes - small business no …

my english isn't the best , and if I hear Matt I can't understand him very well - (british english is much better to understand :-))
so I have to wait for translation - thanks for the discussion

Nathan Rice (http://www.nathanrice.net/)

December 18th, 2008 at 5:19 am

Andrew,
I actually think you've got some great ideas here. Assuming things are the way we all perceive them to be, I think you've suggested some good compromises.

However, I agree with David … I think there is an inherent conflict of interest between WP.org and Automattic. Automattic is a business with VC investments. They have to make profits. Matt runs Automattic. Matt also runs (evidently unilaterally) WordPress.org and the WordPress project. I'm not saying that he does this, but it would make perfect sense for him to make decisions for WP.org that benefit Automattic and WP.com. I'm not saying he's ever done that. I'm just saying the temptation is there, and because the temptation is there, we can't just assume that he won't give in.

For his sake, and for the sake of the community, he really shouldn't have that much power.

Andrew Rickmann (http://www.wp-fun.co.uk)

December 18th, 2008 at 7:35 am

Nathan, you have summed up my thoughts on Automattic quite nicely there. There is a conflict of interest, I complete agree with that, but, on this particular occasion I don't see what benefit Automattic would get from removing themes from the community repository. That is why I think this is genuinely a community driven thing, even though a lot of people disagree.

Taking the psychological theory of community though you can argue that he has that much power because he has contributed the most.

Andrew Rickmann (http://www.wp-fun.co.uk)

December 18th, 2008 at 7:39 am

The problem with links is that they are now worth something. There needs to be a line somewhere. The question is where?

For example, is it OK for a web designer to link back to their site, it should be, but then why not let a gambling website release a theme with links back to their website? is that still OK? How about adult sites? As long as they produced the theme, or paid for it to be produced by someone else, there isn't really a difference. But I would not like the second two.

Monika (http://www.texto.de/)

December 18th, 2008 at 1:17 pm

“…………. I don't see what benefit Automattic would get from removing themes from the community repository”

1idea ..a market place for wp themes - xyz% to Auttomatic /theme

..it is thinkable ..

Nathan Rice (http://www.nathanrice.net/)

December 18th, 2008 at 4:28 pm

Again, I'm not saying this is a fact. But it is a possible scenario in which Automattic could benefit from this move.

It's a competitive market. And in this competitive market, WordPress.com needs to take advantage of people who are either lazy, or web-illiterate. That's their target audience. I can say that with confidence because both my mother and my wife have WordPress.com blogs, and neither of them have enough know-how to run a self-hosted WP blog.

However, premium theme developers are aiming to change that. We make extremely easy to use themes, offer support all along the way, and even help people find hosting, install WordPress, and get their theme activated.

WordPress.com and Premium theme developers rely on significant numbers of the same target audience. If the self-hosted version of WordPress becomes more attractive than the hosted alternative, the WordPress.com loses market share, which would be unacceptable to the Automattic investors.

Bottom line … Premium theme developers make the self-hosted version of WordPress more attractive to novice users. And that is a threat to the WordPress.com business model. On the flip-side, if premium themes were GPL, WordPress.com could take and use them on WordPress.com, giving WordPress.com the advantage (because users don't have to pay for hosting).

Again, I'm not saying this is the motivation behind the move. I'm just saying it's one possible scenario where the conflict of interest could manifest itself.

Andrew Rickmann (http://www.wp-fun.co.uk)

December 18th, 2008 at 6:35 pm

Well, there are clearly lots of ways in which a conflict of interest could be manifested, but, I think, of all the ideas I have heard, that there are as many reasons if not more why they would not work or would not be practical, as there are reasons why there would be a benefit.

I will need to see something very persuasive to see where there are significant benefits to Automattic messing with the WordPress community.

Wayne Smallman (http://www.blahblahtech.com/)

December 18th, 2008 at 9:25 pm

“Capitalism will decide how much is fair.”

Ultimately, that's the great leveler. No matter what the premium content producer thinks they can charge, the market decides, because if they're charging too much, the market won't buy, and if what they're offering is mostly indistinguishable from what's free, very few will buy.

I've written a Plugin (Socialize Me!) and I've written an ebook, both of which are free. However, my reimbursement has been and continues to be the exposure my skills and expertise enjoy as a result of people using and sharing my products, which is an extension of my knowledge.

At some point, your knowledge is compensated further by people recognizing those talents and choosing engage with you in a project they feel your knowledge and know-how will be suited to.

Thaya Kareeson (http://omninoggin.com)

December 18th, 2008 at 10:30 pm

Great analytical writeup Andrew. I enjoy your “Question five” section as I never thought about the WordPress community in this way before.

When I first started developing WordPress plugins out of my free time, I gave them away for free. As support requests increased, my free time got eaten up so quickly that I started losing sleep to support the plugins. By then I had to choice but to add donation options and backlinks to my site to feel properly compensated. Who knows what will happen if support becomes too heavy of a burden in the future? Maybe I need to start a members-only forum that lets me attend to paying users' needs before free users.

I guess what I'm saying is that, you're dead-on right about the definition of the community. I feel like I've been adhering to your guidelines naturally without even thinking about it. But as you said, in the real world, nothing stops people from just jumping to reap all the rewards (cost per download, support fees, back links, entry in repository) before they pay their dues.

ringmaster (http://asymptomatic.net)

December 18th, 2008 at 11:00 pm

“I think premium theme authors, [...] deserve to be compensated for that effort above and beyond the content that the community provides”

I agree completely, and I largely agree with many of your other impressions. It's simply a shame that premium theme developers chose to participate in a community where the necessary licensing of their themes would not only exclude them from profit in the way they typically seek it, but exclude them from being listed due to policies in how the wordpress.org site is run.

Whether it's in the best interest for the community or not might factor into the decision, but ultimately what is allowed in the repository should ultimately be decided by the site owner, not the community. What would be ideal is if the community owned the site and, perhaps more importantly, the brand, which it most certainly does not. In either case, I'd still argue that omitting non-GPL plugins/themes from the repo is good for the project. Leading by example is always best.

improvingtheweb

December 20th, 2008 at 8:10 pm

They are free to omit them, but in the case of plugins, I would really like it so that even plugins that aren't in the plugin repository could benefit from the automatic upgrading.

That's a huuge disadvantage for these types of plugins.

Jamie (http://www.idealienstudios.com)

December 22nd, 2008 at 2:51 am

“I think that premium theme authors are a valued part of the community and so should be permitted advertising space in order to advertise to the community, but, not as part of any product that is provided through the community, and clearly marked.” I agree with this with the caveat that the licensing which the themes are sold under is agreeable to the GPL licensing of the product on which they are a derivative of. You might push that further to suggest that anyone is free to use Wordpress to practice capitalism as long as they are willing to acknolwedge they are benefitting from the socialistic tendencies on which it is based.

Jamie (http://www.idealienstudios.com)

December 22nd, 2008 at 3:05 am

The way the world is going, I think changing peoples approach to “profit in the way they typically seek it” is a very good thing. While I'm not suggesting premium theme developers are anywhere on par with insurance companies, health care R&D drug labs or patent trolls, it is possible to build a sustainable business model based around Wordpress in which you can still support the open source ideals that allowed Wordpress to grow in the first place.

wildhunt (http://www.wildejagd.org)

January 5th, 2009 at 1:21 pm

Your argument would hold stake, if there were charges or mandatory links back to wp.org or Automattic involved in WordPress. There aren't. WP demonstrates, rather clearly, that an Open Source project can be financially successful without charging for the code involved or including mandatory links.

Automattic's immediate success as a Open Source centered business stems from its established ability to create valuable software. Having proven this, business is attracted not through mandatory links or a direct revenue stream, but through a third channel - Open Source as a means of portfolio. I do believe, that the benefits of exposure to hundreds of thousands of potential users via the Plugin repository alone, is worth its pageviews in gold in this scenario, giving authors not only a huge boost by open association with a wildly successful project, but also a means to show openly their craftsmanship. Revenue - and I know this to be the case in my business - can be created from this placement and association without using my users as link bait providers or charging for my Open Source work directly.

Ajay (http://techtites.com)

January 5th, 2009 at 2:40 pm

@Improving the Web,
I don't see how it will be possible. You need a single place to check for updates.

Plugin authors should add their plugins to the repository.

Chris J. Davis (http://chrisjdavis.org)

January 5th, 2009 at 3:56 pm

It certainly is possible. Habari, the project I am involved with, has built an update/installation method that isn't tied to any one point. Every Linux distro follows the same path. There is nothing technologically based that stops this from working in the WordPress space.

Nothing.

Andrew Rickmann (http://www.wp-fun.co.uk)

January 5th, 2009 at 6:39 pm

I am sure I read that someone was writing a plugin to allow plugins to specify an update location for precisely this reason.

wildhunt (http://www.wildejagd.org)

January 5th, 2009 at 8:04 pm

How about an apt/dpkg based upgrade path? I am using something like this locally for my own Drupal and Wordpress installs, and it works like a charm. I don't think it'd be too much of a hassle expanding it and writing a web frontend for it.

t31os

February 5th, 2009 at 2:56 pm

Spot on!….


Monday Poll Results: How many plugins that create settings pages do you have
Friday Fun: I can has code?

Recommended

WP Remix Banner

Archives

  • June 2009
  • May 2009
  • April 2009
  • March 2009
  • February 2009
  • January 2009
  • December 2008
  • November 2008
  • October 2008
  • September 2008
  • August 2008
  • July 2008
  • June 2008
  • May 2008
  • April 2008
  • March 2008
  • February 2008
  • January 2008
  • December 2007
  • November 2007
  • October 2007

Tags

2.7 2.8 Admin Advertising Air Blogging blogs Cache Cliche Coding Comments Content Types CSS Curry Death development Disqus Features Habari image Interview Licensing Modes Monday Poll New Features Organisation Personal Platform Plugin Plugin-Practices plugins Plugin update Poll premium Readers Reviews Search Simplification Snippets Spam Themery Themes tools User Interface Widgets WLTC

Copyright 2009 Fun with WordPress - All Rights reserved.

Wordpress theme by: WPUnlimited