Archive for free beer fundamentalists

back into the shade

Somebody help me out here. Why exactly are we meant to be jumping for joy at the ‘news’ that the wordpress trademark has been taken out of the hands of Automattic and back into the hands of… um, Matt? I mean, yeah, obviously we didn’t want Google or whoever to get their mitts on it if Automattic gets acquired, but it’s not like it’s been gifted to the community or anything. If there is any evidence that anyone is involved in this mysterious Foundation thing other than Matt and whatever lawyer or accountant helped him fill in the forms, then Google isn’t giving it up without a fight. Jane wrote a couple of blog posts for it so maybe she’s involved in some capacity, but, really, everything is so hopelessly vague that there’s no telling, and when there’s no telling it’s generally because Matt has sole control and doesn’t think it’s worth his time to explain.

Where’s the accountability? How do we know that the ‘foundation’ isn’t going to use trademark violation as a weapon in the GPL jihad, using it as an excuse to shut down anyone promoting non-GPL code or documentation? We had a reasonable expectation that Automattic wouldn’t do that because they’re an actual legitimate business, with a board of directors and all that jazz, and the money men might have a shot at keeping Matt’s weirder impulses in check, but now nobody else gets a say in how the trademark’s used or how abuses (real or imagined) are handled. And somehow this gets spun as a great day for open source. Awesome.

Comments (22)

cutthroat

You thought all was forgiven now Chris Pearson finally got bullied into split-licensing Thesis? No, of course you didn’t. So here you go, more grudgewank:

Cutline was sold a few years ago and had a more restrictive license placed on it. The original author of the Cutline theme has gone on to produce other themes with more restrictive licenses. Using Cutline has been seen as a promotion of that work and that’s not something we want to do–so, we made something better: Coraline!

So yeah, by the sounds of it they’ve tarted up Cutline with some code from the new default, changed a couple of letters in the name and are calling it a new theme.

Stay classy, guys.

I’m not really sure why they chose the theme in the first place if it’s such ‘junk’, and I fail to see why existing users have to be screwed around. If you hate it so much, couldn’t you just deprecate it by making it unselectable as a new theme? Come to that, why do we still have three versions of Sandbox cluttering up the place? I can’t see what’s so difficult about hiding a theme option without removing it from existing blogs. All you would have to do is add a BIG WARNING to the theme description saying that the theme is deprecated, it is recommended that you upgrade, and if you do change themes, you will not be able to get the old one back. Simples! And then I would no longer be troubled by the continuing existence of Sweet Blossoms.

[ETA: unsurprisingly, though it was a surprise for them since evidently not all Cutline users lurk in the CSS customisation forum, existing users are not massively pleased about the whole being screwed around thing.

If I were the person whose theme changed halfway through a presentation, or I were having to fend off emails from my boss about why the company blog suddenly looked weird, and then I found out the only reason this happened was because some guy had a vendetta going against some other guy because of a disagreement over SOFTWARE LICENCES… wow. I don’t know how I’d even begin to compute that level of estrangement from reality.]

Comments (20)

commentary

I appear to have become one of those people who does their blogging in other people’s comments threads. Oops.

So, here am I on putting the P into wOrDpReSs: 1, 2 and 3 (bonus link to camelcasers needing to get out more).

And whipping the dead horse of GPL just to make sure it will never rise again (oh, it just did):

All this debate does is make Thesis sound better and more important than every other theme that exists.

I feel sort of disappointed that this has sunk to the level of personal attacks. (On re-reading, I’ve decided I was a little harsh on Jane here. What actually irritates me about this post is the focus on how loud and aggressive and generally ignorant Chris is in comparison to gentlemanly Matt and sweet, altruistic Jane. He might be mean and you might be lovely, but it doesn’t follow that he’s wrong and you’re right. I hate to break it to you guys, but copyright law doesn’t care whether you’re nice.)

I wish somebody could build a time machine and tell Michel Valdrighi what a mess his decision was going to make years down the line.

and for the obligatory wordpress.com slant:

Seems harsh to get rid of wordpress.com themes purely on ideological grounds (no, I don’t know why permalinks to comments on Matt’s blog are broken either. Probably something to do with SEO).

I wish people would quit pretending this is a legal issue rather than an ideological one. Hands up who believes that a judge’s decision that themes did not have to abide by GPL would change Matt’s position, and that he would immediately throw open the doors of wordpress.org to non-GPL themes and quit badmouthing non-GPL developers? Nobody involved in this actually cares about the law, any more than the law cares about whether they are nice or not. Chris wants the power to licence his work as he chooses and Matt wants everyone else to licence their work as he chooses. And the GPL is obscure enough that it is possible to interpret it either way. Can we stop squeaking now? Thanks.

Comments (12)

on the founding of the founderation

Let’s have a Q & A session on the vaporware Wordpress Foundation! Here is Andreas Nurbo with the questions:

1) Any plans to make all the people involved at decision level with the foundation and their role public?
Yes. It is Matt. Next question.

1a) Will documentation of decisions, meetings be made public and easily accessible?
Matt is a busy man and cannot be expected to chronicle his thought processes in public, however I am sure that if he has any foundation-related ideas he will post them on a blog somewhere.

2) You write that you will support projects and ensure that stuff lives on.
2a) Who decides what gets support and what does that mean exactly?

Matt decides. If he likes you, he may give you money. Or a T-shirt. Or a mug. Or, if he’s feeling especially generous, a link in his blog.

2b) Which projects are suppose[d] to be “owned”, if any, by the foundation?
Wordpress. Duh. Well, not Wordpress the software, since the code is jointly owned by all the contributors and can be taken and messed about with by anyone, but the Wordpress trademark. That seems to be about it. Now the community gets the opportunity to contribute to the legal and administrative costs when Matt wants to take a WP-related domain off someone. Oh happy day!

2c) What will the foundation control, if anything, in terms of projects? Projectroles, websites, servers etc.
Nothing, unless at some point it proves financially advantageous to do so. You know as well as I do that setting up a non-profit is mostly done for tax purposes. Handing the wordpress.org website over to the foundation would hardly amount to relinquishing personal control, but changing the name on the domain registration seems an unnecessary formality if there is nothing more concrete to be gained by it than community goodwill.

2d) Will the foundation put up any rules for openness of the organization and decisions in the projects it decides to support?
Matt’s always been pretty clear about the projects he’s willing to support; their work may not be released under any licence other than GPL (other open-source licences are apparently a no-no, which seems offputtingly, well, religious), they should not be overly enthusiastic in the pursuit of profit, and they should respect his authoritah. As the plan seems to be to dole most of it out to Wordcamps, these demands should not be too onerous. Also, it would be kind of rich for an organisation administered inside one person’s head to demand openness and accountability from its beneficiaries, don’t you think?

I do not understand why even the most dedicated fanboy would be jumping up and down over this non-event. Are we meant to be excited about the revelation that Matt still runs everything and plans to subsidise selected Wordcamps? Seriously? And did anyone actually believe that this foundation would be some kind of committee that would administer wordpress.org for the benefit of the community? If they did, they obviously haven’t been around Wordpress for very long.

Comments (18)

sandboxing

@eksith: there are a whole bunch of sandbox skins at http://sndbx.org, though they’re a couple of years old and might require tweaking to work with the latest version of the theme. I have a few more oldish ones (including sandbox versions of other people’s themes) at http://ntuat.wordpress.com and devblog does them at http://sandboxskins.wordpress.com. If anyone knows any other sources, please let me know.

@Noel: are there any plans to deprecate older versions of Sandbox at any point? On the one hand I am lazy and want to keep my 0.6.1 skins up indefinitely (I like the ability to pick your layout through the admin panel, which later versions lack), but on the other I can see that having four or five versions of the same theme could be confusing for users. Also, could you possibly give us some idea of what has changed/improved between 1.1 and 1.6.1? Is there any added functionality, or is this just a functional upgrade to ensure compatibility with the latest version of WP?

Can anybody explain why this comment is deemed too offensive to appear on the news blog? I have a couple of ideas but none of them seem adequate:

  1. self-promotion. OK, but the fellow commenter was asking for examples of what could be done with sandbox and so I was providing some. I was trying to be helpful. I know, I know, Automattic have made it perfectly clear that they do not want my help, but eksith had made no such stipulation and it’s not really up to Automattic to make that decision on his behalf.
  2. asking of questions. I know we are not meant to ask questions in announcement posts, but nor am I allowed to ask questions on the forum, and frankly it does not seem urgent enough to pester Support with. If you have a major problem with my asking what has been changed and whether older versions will be deprecated, then please say so in your reply, rather than just pretending I never asked. (I don’t know exactly why anyone would have issues with my asking these things, unless of course they didn’t know the answers, in which case there seems little point in asking Support since they won’t know either.)
  3. it is official company policy not to allow any comments by me to appear on the news blog. That would be vaguely flattering but to be honest I don’t think I’m that important. They’re already compromising their professionalism enough by refusing me access to forum support.

This is why I don’t make many Sandbox skins anymore. I don’t mind having new versions sprung upon me with zero notice, but I would like to know how they differ from the one I’ve been working with, to save me and every other person who deals with custom stylesheets from having to examine the code independently and deduce for themselves what the differences are (and if there aren’t any, wow, thank you so much for wasting our time). It would be nice to know whether the older versions will ever be made unselectable for new users, so I know whether it is worth my time converting older skins. I’m providing a service for fellow users here; I don’t want thanks or recognition but a little bit of civility and the occasional smidgeon of help would be nice.

Seriously, I’m this close to taking http://ntuat.wordpress.com down altogether. It can’t be good for my blood pressure to keep banging my head against brick walls like this. I keep thinking of Brian Gardner’s point about the inadvisability of building a business on a platform that is actively hostile towards your aims. Obviously I am not stupid enough to try building a business upon custom CSS, but the same point stands. Automattic have done a superb job of killing any potential market there might have been for custom stylesheets, mainly by dint of drilling support staff and volunteers that users must on no account be advised to purchase the upgrade if they are not already fully-fledged code mavens. Which is odd, since people on blogger and livejournal appear to have no problems applying cut-and-paste templates without such expertise, nor in understanding that any support issues with said templates are best referred to the designer rather than to blogger or livejournal.

No: the real fear here is that people having already spent their $15 on the ability to customise their blog would be willing to hand over even more wonga to a third party willing to do it for them. Automattic are fond of protesting that they welcome people making money off the back of wordpress.org, but you don’t hear them saying they want anyone other than themselves profiting from wordpress.com. If they encouraged people to make and distribute free sandbox skins, sooner or later somebody would produce a ‘premium’ skin, or start offering custom designs, and, since CSS and images are officially not covered by the GPL, Automattic couldn’t stop them from releasing them under whatever licence they chose. I’m the thin end of the wedge. I know that.

OK, I appear to have answered my own question. Comments referring to the existence of third-party sandbox skins cannot be allowed to appear on the official blog, since this would raise awareness of their existence and other people might start making them. Of course, my skins are all impeccably GPL and I have never considered charging a penny for them, but since when has that made a difference? If theme designers are scum, then skin designers — mere parasites upon the greatness that is wp.com! — must be the lowest of the low and extinguished at all costs.

Like I say. I’m this close to giving up on wordpress.com and concentrating on platforms such as livejournal and dreamwidth which actually encourage users to create and share their own stylesheets. Sure, you could read that as exploitation (though no worse than Automattic have done for years with their commandeering of amateur-created themes) but it feels a lot more healthy and constructive to me than the weirdness going on here.

Comments (16)

gifts

[long sigh]

OK people, censored comment on this post. (No, I don’t know why people blog if they don’t welcome comments either. You’d have to ask them. Just don’t go expecting an answer.)

Of course, if people have been ripping off CC-licenced images and CSS, this judgement clarifies that the original creators are well within their rights to pursue the offenders; and nine times out of ten those are the elements of the theme people are interested in stealing, not the fairly generic PHP files. I know Automattic doesn’t believe there’s any distinction between functional, not-visible-to-end-users PHP and creative artwork, but it’s sad that you’re still living in denial even when your internet lawyers have conceded the point.

One of my friends is a successful livejournal designer who has had some of her templates converted by a third party (without her permission, by the way) to wordpress themes. I’m not sure it’s actually legal to relicence someone else’s creative work as GPL, whether you’re lifting it wholesale from another platform or merely using CC-licenced images or resources, but if these people were to upload these templates to wordpress.org that’s what the situation would be. You’re obviously cool with that. I, equally obviously, am not.

WP is GPL because of a decision Michel Valdrighi made several years ago. It doesn’t make coders morally superior that they abide by the licencing terms they’re lumbered with, and it doesn’t make designers bad people to want to be credited and compensated for their creative work. Sure, you can force people to embrace GPL by blackmailing them or encouraging others to relicence their content on their behalf, but I still don’t believe that’s how open source should operate. A gift that isn’t given freely isn’t really a gift at all.

Mostly. I’m disappointed with the lack of any denial that stealing and relicensing other people’s stuff is OK with Automattic. We all knew that was the case anyway, but it’s depressing to have it confirmed again.

Comments (9)

it is what it is

Even though graphics and CSS aren’t required to be GPL legally, the lack thereof is pretty limiting. Can you imagine WordPress without any CSS or javascript? So as before, we will only promote and host things on WordPress.org that are 100% GPL or compatible. .

Wow. Disingenuous, much? Your internet lawyers just admitted that the only elements of a theme covered by GPL are the PHP files, but you’re going to go ahead and insist on everything else being GPL anyway.

(What happens, by the way, if I give all the WP functions their own files within the theme, separating them from the html and calling them with a common-or-garden php include? Would index.php catch GPL merely by virtue of calling files that calls WP functions? OK, so nobody in their right mind is going to attempt this, but still.)

Actually this is pretty reassuring for anyone still clinging on to CC — they can protect their CSS and images if they choose to do so, freeing them to use third-party CC content such as icons, photos, brushes or backgrounds. HTML generally isn’t special enough to be worth protecting anyway. They can’t submit the resulting themes to wordpress.org — Automattic don’t have the resources to moderate them — but nobody really suffers from that apart from users who are too lazy to look beyond its heavily limited selection; it’s not like there’s a shortage of alternative directories.

Meanwhile, I feel vaguely sorry for the saps who bought multi-use licences for hundreds of dollars from the various premium theme developers, only to discover within months (or weeks, or even days) that those who only bought a single-use package are now getting exactly the same deal, and that anyone who downloaded a pirate copy for nothing has officially done nothing wrong. But they don’t seem to be complaining too much (or maybe their comments are being censored, or maybe they’re too ashamed to admit to their stupidity in public, who knows?)

I can see that the developers were pushed into a corner here; you can’t risk being ostracised by the company who own your platform, because without official backing people won’t trust you enough to do business with you. It was OK while everyone was in the wilderness together, but as soon as one sucked it up and toed the GPL line they all had to, or he was going to get the monopoly. If you make iPhone apps you’re at the mercy of Apple, if you build a business around wordpress themes you’re at the mercy of Automattic. It’s just the price you have to pay. I still don’t believe that the GPL was conceived with the intention of being used to protect the interests of big corporations and manipulate the little guys, but it is what it is.

Comments (17)

boring stuff for no pay

Yeah, ok, we get that Matt Thomas doesn’t need any notice whatsoever to do WordPress design projects, but has it crossed your mind that this may be because it is his JOB?

Anyway, the way I read it, the issue with the has-patch marathon was not so much that people had no notice, it was that wp-hackers didn’t get a heads-up before the rest of the world thus making it uncomfortably clear exactly how unimportant they are. It’s partly this perception of their own irrelevance, of course, which necessitates these events in the first place; if your experience of submitting patches is that they get ignored or dismissed then you don’t have much incentive to keep doing it. It’s all very well to say they don’t need a deadline to contribute, but, hello, we’re talking about geeks here. They appreciate structure and measurable goals, not to mention reassurance that their efforts will actually be noticed.

I cannot shake the suspicion that this drive to get designers involved with the development process is an attempt to divert them from theme production. (We have enough troublesome theme developers already; the last thing Automattic wants is to encourage them.) Also, if boring things such as tweaking the user interface can be outsourced to students working for nothing, that frees up the inhouse design team to work on fun stuff like themes. .com users are always bitching about not having enough themes; why hire outsiders to produce them when you already have designers on the payroll?

The flaw in this plan? Well, I sort of wonder whether doing boring stuff for no pay is going to be quite as appealing to the community as doing fun stuff for no pay. We’ll see.

Comments (6)

i <3 blogger

Hands up who’s in love with the fact that the corporate sponsors of wordpress.com’s first LJ-style competition host their own blog on blogspot?

Sadly, since the contest requires the use of expensive proprietary software (needless to say, I am not the only person to have noticed the incongruity here) there has not been a huge response from the freeloaders of .com and Automattic have had to resort to plugging it on ma.tt.

Looking at his new bloated uberheader, I’d say cod Dali is probably the way to win the hearts of the judges. Also, if you were wondering why there’s no linklove for the guy who converted the comps into code, it’s probably because he’s using a theme by somebody else and that’s never good for one’s credibility. And I’m really, really sorry, but I cannot resist pointing out its utter failure to validate. You know I would never normally be sufficiently assholish to mention that but hey, glass houses.

Comments (7)

assorted cheap shots at lj

You want to provide asylum for lj-ers? That’s beautiful, but be prepared for:

  1. complaints that they only get two icons
  2. outrage at the censoring of porn artistic work with adult content from global tags
  3. I have to PAY to have more than 35 people on my flist???!!!!1111!!!
  4. why does my picture of a nipple get rated X on Gravatar?

I think the corporate culture at wordpress.com is probably an even worse fit for your average LJ-er than Six Apart’s was; arbitrary suspensions are an everyday occurence, not a cause for scandal, and there’s more pressure to keep things PG purely because there are so many kids. I’ve had a couple of people on my flist attempt the switch to wordpress.com already, but they find there’s no community here and get tempted back to livejournal. I don’t know why there’s no sense of community here, since most of the architecture is in place. It’s an organic thing. It either happens or it doesn’t. And of course there’s always been this underlying sense that wordpress.com is a stepping stone to when you get your own real wordpress blog, and it’s hard to make people passionate about a site that they’re just passing through on their way to somewhere better.

I don’t write anything like as much about wordpress as I used to because I don’t care about it anymore. I don’t care about the new interface that will be gone the way of all the others come 3.0. I don’t care what struggling little minnows Automattic swallow on their way up, or what empty promises they made to tempt investors. I see the same old wars being fought over the GPL and I might still find them interesting if they were still about freedom and authority, but they’re not. They’re about money.

Comments (9)

Older Posts »