That is, of course, in addition to Memorial Day. Today I’m activating the oldest theme I have that will work with this current version of WordPress, and when I roll it back, it will be to the new theme for the year (I redesign the blog annually.)

As for Memorial Day: in keeping with this holiday, don’t expect me to greet or wish anyone a “happy” Memorial Day. Yes, many of us use this long weekend to spend some time with family, to celebrate the unofficial start of the summer, or to do other stuff. Let’s not forget that this day is meant to commemorate those who have fallen in our military efforts, if but for a moment.

WordCamp Raleigh has come and gone, and everyone has a lesson or two they can take with them in the days ahead. Mine, however, is deeply personal. It’s one that I didn’t expect would happen at the event, but it was forthcoming.

I’ve been known in some small circles of the WordPress community as a very vocal critic of some decisions made by those whom we consider the leadership. I’ve written some zingers of analyses that have brought about ssome heated debate.

If it were only a matter of heated debate, I’d never have been led to writing this post. My recent response to some new guidelines on WordCamp organizing led to some very, very nasty discussions by others. Jane herself left a response in the comments and that was enough for me to close them. However, others took the post as inspiration to write even more unbelievably terrible commentary.

When I heard that Jane decided to show up at WordCamp Raleigh, I didn’t know what to think. I was hoping, however, for an encounter that led to a resolution for the better.

My conversation with Jane felt awkward, mostly because I was very ashamed that the conversation had to be had in the first place. A friend (who will remain nameless) had clued me in to the effects of my writing, no matter how “fair” or “intellectually honest” it could be. I was reminded that the developers aren’t really all that inaccessible.

I had to be reminded that there is a process to conflict resolution, and that motives really cannot be gleaned just on the basis of one’s actions. I’m very embarassed that I forgot about the three schools of moral evalution, especially since I wrote about them a while ago.

I’m moving on from the matters of GPL debates, and the conflicts between the “WordPress leadership” and other developers. I still commit to serve the truth, but the truth in this matter is that even my most fair and intellectually honest analyses will always be used as ammo by smaller minds.

No idea exists in a vacuum, and at this point, it’s better for me to channel my energy and ideas to other matters. I’ve asked Jane how I can help, and I’ve signed on to helping out with the UI/Design team. I requested no special treatment, and I fully intend to earn my keep.

This doesn’t mean I’ll be some shill with non-stop rah-rah “Automattic/WordPress/Matt/Jane/name-your-developer can do no wrong” cheerleading. Everyone makes mistakes, and I’ll hear and see things that I disagree with, but I know there are better means to address them, and taking it public should actually be the last, not the first, means of resolving an issue.

Finally, I must commend Jane for engaging her critics head on. She showed that she’s sporting a bigger pair than most of those who hide behind their computer screens. She spent a great deal of last Saturday engaging the prickliest of her critics, and have won over most of them, myself included.

UPDATE: Comments are closed. I appreciate Jane’s response at comment #9 and yes, I give her the benefit of the doubt. I didn’t write this looking for or spoiling for a fight and now that I got a response from Jane that is materially oomphy, comments are closed. Blog about it on your own sites if you wish to continue but in the service to the truth make a note that Jane has responded.

UPDATE 2: Following a real-life conversation with Jane, this post is considered moot and have written a follow-up. This issue is over and done.

The problem with blanket policies [a very acerbic clause was removed on the advice of a friend] is that you end up causing collateral damage beyond what is, in retrospect, necessary to achieve one’s goals. The same holds true for writing policy statements that have wide-ranging effects on a particular activity. This morning, Jane Wells drops a hydrogen bomb on the WordPress community. The first paragraph is pablum, the second is where the bodies start vaporizing. I will scrutinize in a rarely-used format in tech blogging, called “Fisking.” (All emphases are mine.) Here we go:

One thing that we didn’t used to spell out but has become necessary to codify is that WordCamps are meant to promote the philosophies behind WordPress itself. Lately there have been a number of WordCamps accepting speakers, sponsorships, door prizes, etc from people/companies acting in violation of the WordPress license (GPL v2) with regard to their themes/plugins.

What is the tolerance limit here? When you say “with regard to their themes/plugins,” how do you know? What’s the disqualifying standard? Is it: “all themes/plugins made by a speaker/sponsor/door prize provider have to be GPL v2,” or is it “some themes/plugins” or is it “at least one theme/plugin”?

It is the official policy of WordCamp that WordCamps not provide publicity/a platform for such individuals/businesses.

“WordCamp” is an entity now? I understand that Automattic might want to claim the name as a trademark long after the fact, the way a “tweet” has been filed as a trademark by Ev. Ambiguous language.

They are welcome to attend, but WordCamps may not have non-GPL-compliant people as organizers, sponsors, or speakers.

So, there goes Microsoft and their wads and wads of cash that they handed to WordCamp NYC. Too bad it would be nice to court their sponsorship with every WordCamp, but oh well.

Events that want to move forward and include such individuals in these roles may need to use a name other than WordCamp if the appropriate adjustments can’t be made.

This preemptive declaration of personae non gratae is disturbing.

This is because WordCamps are seen as the place to gather for the official word on all things WordPress; providing a public platform and publicity in an official capacity for people acting in direct opposition to the official word just causes confusion.

Individual WordCamps already warns sponsors and speakers that is not “pitch time.” What is this “official word,” and why does the presence of non-GPL “people” assume “direct opposition?” If a commercial, non-GPL plugin or theme developer wants to present at a WordCamp about something that gives them no additional exposure aside from their work being mentioned (e.g. said person wants to present about CSS, or an improved workflow, or wants to share about how WordPress changed their lives) does that make them unwelcome? By Jane Wells’ Standard As Of May Nineteenth In The Year Of Our Lord Two Thousand And Ten, Anil Dash would’ve been unwelcome for the keynote event in WordCamp MidAtlantic 2009.

I have no problem with the last paragraph so I’m leaving it out. Now, a message for Jane. This is going to be stern, but I’ll keep it professional. There is NO room in official policy for “common sense.” It’s for this reason that when you want the top brass of the strongest military in the world to spend a shit ton of money on your brownies, you have to follow a 26-page recipe (PDF) that spells out very specific policy, down to the last standard of what nuts may be used. Official policy statements are like that. Having worked in government sales, and having filled up immigration forms to legally enter this country, ambiguity is the enemy. Now that you are the official liaison for all WordCamp organizing, you’ll learn that while it would be nice to have your word as the Law Of The Land, there will be people like myself who will challenge you to make your statements clearer. I want to organize a WordCamp one day. I do 100% custom work, and the only “theme” I released to the wild is a palette-swap of Classic, back in 2003. I license all PHP in my work under GPL, but not the CSS and images, so my clients won’t turn around and give away a custom work I made for them. Does that disqualify me? Will I have to disqualify someone who made one commercial, non-GPL plugin?

Laying down the law never means having the last word. It means leaving oneself up open to questions. While I may be “just a guy” I know the questions I pose are fair and I would like to get an answer, preferably blogged by Jane on her own site, that more people will see her response.