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 (6)

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)

hating on netscape, those were the days

OK, who took their eye off the ball and let Matt post in the forums? You know he only ends up antagonising people.

Did anyone else look at the ‘acquisition’ of blo.gs and think of our old friend BrowseHappy, i.e. third party finds itself with domain it can’t be bothered to maintain and offloads it onto Matt so he can put backlinks on it? True, it’s only a PR6 at the moment — the site is so neglected it’s dissing Netscape 4 rather than IE — but that’s easily taken care of.

eta: turns out the stats issues were down to a code overhaul of which Matt was obviously unaware. Not in itself a problem — nobody expects him to be heavily involved in the day-to-day running of this place nowadays, any more than they expect him to read wp-hackers or write his own blog posts. The trouble is, when you post as staff that gives your answers the appearance of being authoritative, even when you have no more idea what’s going on than the average volunteer. I think that’s one reason why support staff prefer not to post on the forums if it can be avoided.

Comments (2)

more of the same

Reasons why I am glad I can no longer participate in the car wreck that is the wordpress.com forums:

  1. Sticky threads for spammers. How come this guy gets to have a URL signature when anybody else trying that particular way of cirumventing no-follow gets slapped on the wrists? Are forum stickies the latest way of promoting commercial partners who aren’t spending enough to get a link from ma.tt or the news blog? I thought the purpose of the support forums was supposed to be support?
  2. oh, wait, no, sorry, the purpose of the support forums is to sail in every couple of months and deliver the smackdown to the poor saps who are actually trying to do support, as opposed to plugging your sites. If this guy wanted a Polldaddy poll, he’d have implemented a Polldaddy poll. What he’s trying to do is a women’s-magazine-style quiz in which each answer carries a certain number of points, and if Polldaddy’s capable of that they really need to publicise it better because it’s news to me.
  3. Global tags redux. There is no point trying to argue about this, because the forces of logic are powerless against the might of the Google dollar. The suggestion of adding one’s username to tags to render them unique is a decent workaround, though.

The penguins are quieter nowadays, though. Do you think they’ve all gone to Twitter like everyone else?

Comments (4)

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)

rip codex. oh, sorry, i meant R.I.P. codex.

So, according to Lorelle, Codex is officially dead and being superceded by the WordPress HandBook. Lorelle being Lorelle, she doesn’t admit that Codex is officially dead, but nor does she provide any coherent explanation of how and why two ‘online manuals’ sharing much of the same content can operate side by side. (She can’t seriously believe that Codex will still have a role as ‘a highly technical and historical guide to WordPress’. Firstly, the techies wouldn’t touch Codex with a bargepole, they’re all about the PHPXref. Secondly, a historical online manual is about as much use as a chocolate teapot, otherwise we’d still be directing people to wiki.wordpress.org so they could read about how to get the best out of 1.2.)

Obviously, switching from mediawiki to XML and SVN is going to effectively debar all but the most dedicated from contributing (for which, read Lorelle and people on the Automattic payroll), but that’s not a bad thing, since a) Codex was not exactly overwhelmed with volunteers, the docs project being a proud part of the long-standing WP tradition of treating volunteers like crap, and b) community-written documentation is next to impossible to keep up-to-date, especially when pursuing a quarterly release schedule. Bringing it under the Automattic umbrella at least means that it will be updated, even if it does constitute another step in the process of taking the community out of wordpress and wordpress away from the community.

It’s nice that Automattic have decided to focus on documentation this cycle — it was about time — but I can’t help wondering how much cross-referencing will be going on between the new written documentation and the new proprietary traffic-building ad-carrying video stuff…

Comments (14)

spinner

More proof, if proof were in fact needed, that ma.tt long ago ceased to be a proper blog and is now a corporate mouthpiece. (I’d have linked to the actual comment, but no, we can not has permalinks.)

wordpress.tv itself is, exactly as you would expect, a wordpress.com blog with a bunch of videos, aimed at getting Automattic a monopoly on video tutorials and driving its rival purveyors of ’spammy promotional videos’ out of business. (At the time of writing, wordpresstutorials.com is still top of Google for ‘wordpress video tutorials‘ — why else do you think Automattic are linking to this new blog so assiduously? Look at the wp.com version of the announcement and its eight links to the target site, it’s like SEO 101.)

Since I can read faster than most people can speak and am not a raving fanboy, I am not the target audience. Naturally, the only community-produced content is the wordcamp stuff (enough to keep the fanboys happy) and the instructional videos are all produced inhouse so there’s no risk of anyone promoting any themes or plugins that aren’t. I don’t know how much they’ll make out of the Adsense on this one but as many of the users will be totally new to WP and looking for all the information they can find on the topic, I imagine it will be quite the moneyspinner.

Comments (12)

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)

here we go again

Late to this one (Christmas shopping, meh), but, yeah, if you didn’t already hear, Matt has, unilaterally and without prior notice, purged extend/themes of over a quarter of its content. As well as targeting premium theme sites, this allegedly includes any theme linking to a site which carries an affiliate link to WooThemes. Whether this ban also encompasses affiliate links to theme sites other than Adii’s, I do not know (though affiliate links to Revolution are presumably kosher, seeing as how wordpress.org was carrying one till they were called on it). How Joseph felt about his theme-vetting skills being publically dissed in such a way, I do not know. What the hell was going through Matt’s brain at the time, I also do not know, but it’s December again so we can’t go expecting too much in the way of rationality.

Somebody in the sacred inner circle really needs to point out to Matt that if he doesn’t let go of his obsession with persecuting theme designers it’s going to start seriously hurting the community. For a start, it should have been apparent to anyone with half a brain that premium themers were going to release freebies and submit them to wordpress.org as a promotional tool; partly for the linkage, partly to showcase their skills. If Matt didn’t want people doing that it should have been made clear at the outset.

Of course, there is no logical reason why he should not want them doing that. A GPL theme is a GPL theme, regardless of who designed it or the motives behind its release. And if it’s been made to persuade you to invest in the designer’s other work, it needs to be a decent one. Free themes by premium designers? What is so terrible about this, exactly? Nobody is forcing people to buy whatever other themes the designer or his/her affiliates has on offer. Nobody is even forcing anyone to keep the link to a profit-making site. The whole concept of GPL is that you can’t enforce these things, that it doesn’t much matter who originally created the code, and that you can take it and make of it what you will. Refusing to distribute a GPL theme (or plugin, for that matter) because you personally dislike what the developer has done with their website pretty much flies in the face of that spirit of openness. The code is rejected because of who made it, rather than judged on its own merits; and end-users are deprived of a free theme.

(Still, let’s face it, it’s a very long time since anyone involved in this endless GPL jihad bothered to think about the poor bloody users.)

People stipulating that you can’t remove their links? Also to be expected by anyone with half a brain. I mean, Michael Heilemann tried that with Kubrick, and that was apparently GPL enough to make it into core. If designers can’t be bothered to ascertain what the licence you’re imposing upon them actually entails, that’s their lookout. My understanding was that in submitting your theme to .org you render your theme GPL, because that’s what you agreed to when you uploaded it. And at this point it ceases to matter what you want people to do (or not do) with your theme. If you still care about things like being credited for your work, and you don’t want your free labour commercially exploited, then the only way to clarify your terms of use is to CC-licence your content and keep the hell away from wordpress.org. Come to that, it would be prudent to steer clear of designing for WordPress entirely and focus your efforts upon a platform that allows you to distribute your work under whichever terms you see fit.

I fully expect that the next offensive will be to ban links to non-WordPress sites entirely, as was proposed for the abortive Marketplace. That could probably be handled on an automated level, and would prevent chucking the baby out with the bathwater and junking a perfectly good theme because of an iffy footer link. It would also prevent people from gaining any extra traffic or pagerank from designing a successful theme, not to mention preventing end users from following up on a theme they see on someone else’s blog. But then, SEO spamming is Serious Business and should be left to those with multiple PR8 and 9 sites at their disposal.

Comments (12)

change lightly

We don’t take change lightly, but the good news is that this redesign provides a solid foundation that we’ll be able to build on for the next 5 years of WordPress, just like the last one was basically the same for 5 years.

Years? Don’t you mean ‘months’? It is eight of those, by my reckoning, since the last ‘new dashboard design’ post. You have to love how 2.5 is being erased from the official history before 2.7 is even out of the door. (Also, of course, wordpress.com hasn’t been around for five years, which would make it difficult for its dashboard to have been the same for all that time, though if last April was five years ago in the WP universe I suppose it is feasible enough.)

I had to switch colour schemes to escape the default icons (something about them screams ‘barebones Linux distro’, which was only to be expected given their genesis) but I’m not about to get too angry with or attached to something which will inevitably be superceded come 3.0.

Meanwhile, I want to know who came up with the name ‘blavatar’ and whether they have been punished yet. I was initially baffled by the decision to make people upload new images rather than just using the 16×16 version of their current avatar, but then I remembered — multiple blogs. This way you can vary your favicon from blog to blog. I have no idea why this wasn’t explained in the post. Maybe it was covered in the video, but I don’t bother with videos because I can read.

Comments (16)

Older Posts »