Back on August 23 there was a WordPress theme review meeting that included a discussion (and vote?!) about restricting the number of new themes an author can submit to the WordPress theme repository. Current guidelines/rules make that a limit of one. Yes, a single theme (although supposedly updates to approved themes do not count)!!
I apparently missed that meeting (although I did go back and “vote” against the rule earlier today); and, I opened a discussion related to it on the WordPress #themereview Slack channel (it’s a long read now).
Hopefully I got my point across about it not being a good idea but there does not seem to be many, if any, supporters for changing it now (even if it was meant as a three month trial); although the idea to remove it when the queue is only a couple of weeks long was suggested. Unfortunately my schedule does not readily allow for midday meetings when the theme review team meets to discuss their latest ideas, or review past decisions … and using the rule as a queue shortener?! Really?
Little did I know all those years ago when a friend expressed his concerns for creating guidelines related to theme submissions that they would come to fruition. Even though I am no longer directly involved with the theme review team admins (or whatever appeasement title they choose to be known as) I can only hope that finding the time today to start the discussion will keep it fresh enough for the next theme review team meeting.
In the meantime, I am going back to developing my “new” theme; and, wondering where to publish it. Since the WordPress theme directory/repository and its myriad guidelines/rules may be making it not the best place to do so anymore (again?!!) I will have to start looking elsewhere.
Day 0: The Flight, Pre-Registration, and Long Walks
I was up at the usual time and ready and waiting for the Aeroport Limo service to arrive at 9:00 AM … the flight was at 11:45 and I wanted to ensure I would be at the airport in plenty of time. Aside from some minor turbulence, the flight itself was rather uneventful … and the California Roll Sushi for lunch in flight on Air Canada 755 was actually pretty good, too.
I rolled into the hotel right at check-in, the flight was early so this was a timely good fortune.
I got settled in, unpacked, and called my wife on FaceTime. We chatted for a little while then I headed off to the Automattic Head Quarters for pre-registrations and volunteer orientation. I was scheduled as a “Casual Runner”.
On my way into Automattic, I ran into Kim … a down-to-earth lady and very much the same person offline as on; something I noticed with almost every person I met that I had previously only known via social networking and/or various interactions on forums, mailing lists and IRC chats.
Once inside and registered I met with several more online people (Emil, Jose, James, Mike and Tyler to name a few).
Afterwards, I walked back to the hotel and then wandered up 8th Street to the Harvest Urban Market to pick up some fresh fruit (and, as it happens, my favorite beer Stella Artois).
Day 1:
Saturday, first thing came early … I needed to be at the Mission Bay Conference Center by 7:00 AM. I set my alarm for 5:30 AM. Got myself organized and headed out the hotel door just after 6:30 AM. Although still before dawn, it was a beautiful walk down 7th Street with a jog over to Owen and finishing up at “Mission Bay” right at 7:00 AM.
Once I got myself organized and sorted out Andy (the volunteer organizer) asked me to help Nick with getting the Swag Store set up. With the help of Nowell, Jenny, Courtney, Marko and a few others we managed to get everything taken care of and ready to role well before the 9:00 AM “opening” time. To finish up everything, I made the first purchase at the Swag Store to ensure the “connections” were all working correctly.
During the rest of my volunteer shift I met Aaron, Andrea R, and Andrea M as well as many more. The Lipinski brothers from CyberChimps, Guillermo Rauch (who presented Socket.IO) and I had an interesting discussion related to theme review guidelines as well.
To end my shift, I helped Michael with the vegan/vegetarian/gluton-free special dietary table prior to lunch being served.
This left me with the afternoon free which I more or less spent in the upstairs presentation room. Mark Jaquith‘s talk on using Backbone.js was quite notable and left me with some ideas to consider for future projects, too.
Day 2:
I started the day a bit earlier than strictly needed. I planned to have breakfast at Rocco’s Cafe but it did open until 8:00 AM. I walked back to the hotel and decided I would wait until they opened and while I waited I downloaded the Uber app … an adventure after breakfast to get to Sunday’s kickoff by 9:00 AM.
Rocco’s Ham, Cheese and Mushroom Omelette ordered, I enjoyed a very good cup of coffee.
The Uber ride was interesting with a small tour of the area around the Mission Bay Center before being dropped off at the doors.
I wandered for a bit then settled in with the Support team. The group consisted, for the most part, of James, Jan, Mika, Sarah (the Living Child-Theme), Marius and Keith. I was also promoted in the forums while I sat with them, and my forum title was adjusted to read: Theme Review Team Admin, The JellyBeen Man (possibly only a temporary thing).
The current Support team also gave me a crash course in some of the “administrator” duties and functionalities that followed with the promotion.
Some of the most fun at WordCamp San Francisco came form sitting and chatting and laughing out loud with the Support team and those that wandered in and about the area we were sitting in.
There are no words for this …
I sat in the Theme Reviewers’ quick talk at 2:00 PM done by Tammy, but returned to more fun and games with the Support Team, especially some of the ribbing we were giving Marius about WordPress testing the Slack service as an alternative to IRC.
Probably one of the most interesting and memorable quotes from the afternoon came from the quick-witted Mika, “on a scale of one to firemen, where is this folks?” as some anonymous person’s car was announced would be towed away momentarily. This is really more an inside joke but in reference to a first at WordCamp San Francisco … a full building evacuation due to (at least as far as I know) some unknown “emergency”.
As the afternoon wore on so did my energy levels, and I thought it best to choose to return to the hotel and prepare for the following days. Tomorrow is expected to be essentially a sequestered day long session known as the Community Summit; no ‘net, no phones … no kidding?! Something to consider on my walk back to the hotel.
I have met many people over the last few days and look forward to the next few days working closely with some and meeting even more … if we met and I did not happen to make note of you specifically, please feel free to remind me in the comments below.
PS: For anyone counting, I only collected seven T-shirts during this WordCamp. There were more available but I had to keep in mind the limited space I have for packing things to return home with.
I write WordPress Themes and Plugins and often contribute them to the WordPress community by submitting them to the relevant WordPress Extend repository. This provides an extensive distribution venue and allows these themes and plugins to be available to millions of users all over the world … all at no charge. Let me repeat that, with emphasis, no charge!
Now, let’s have a look at that idea. I have spent in some cases quite a bit of time developing a theme or plugin; and, I take pride in the work I do. I have spent many hours debugging and improving my themes and plugins with every intent to make sure they are of the best quality every time I release a new version. So, if an end-user points out something I’ve missed then by all means I note the issue and address it at no charge. Let me repeat that, again with emphasis, no charge!
Also, if an end-user of one of my themes or plugins offers an idea I feel would provide “greater good” benefit I make note of it; I review what would be involved to implement the idea; and more often than not I add it to the theme or plugin; and, yes, I do it at no charge. Let’s repeat that one more time, with feeling … no charge!
So, when someone expects me to provide “free support” for one of my contributions to the WordPress community I look at what I already offer and weigh if what the end-user is asking fits into the above ideals, or is more suitable to a chargeable customization … or if it’s just a Five-Minute-Fix:
The five minutes is purely subjective and completely based on my personal opinion. If I believe a project should take five minutes then that is how long the project will take. If it takes five hours, or five days, the cost will still be the same: free!
Be that as it may, I fully understand if an end-user expects “free support” for a “free product” downloaded from a “free source” and in many cases I also agree with their “reasonable” expectations as I still to this day have not been able to assign a value to the free advertising and exposure provided by the WordPress repositories.
Even though I agree with providing free support on items with “reasonable” expectations, I do not agree with nor do I offer support for unreasonable requests or outlandish ideas. If an end-user wants a specific customization, or requests a specific feature, that is not currently scheduled or under consideration to be added the end-user can just as reasonably expect their request to not be no charge.
If the end-user has modified the code in the theme or plugin; finds it no longer works as expected; and, then requests free support … really? seriously?! Why would that be no charge?
After an interesting discussion on twitter with @curtismchale, @ericmann, @mikeschenkel, and @rarst I have decided its time to have another look at “local development”.
The basics so far have been the following downloads:
Tortoise SVN and Git are for the version control aspects of this project; WampServer (since I am testing on a Windows PC) is for the “local” environment; and PhpStorm is a recently discovered IDE that ties all of these together.
The next step was choosing a plugin and theme as well as setting up WordPress, my preferred CMS for development. I chose to go with the Nightly Builds version of WordPress, keeping it up to date via the core subversion access.
The plugin and theme are respectively ‘BNS Theme Add-Ins’ and ‘NoNa’. The first, a new WordPress plugin I recently released; and the second, one of my WordPress Themes due to be updated. To test the version control aspects these are now being maintained via github.
Although it has been a bit of a stumbling, grumbling affair I am finding the mix of these tools to have some interesting potential. I have been doing most of my current development work on “live” test servers (all I need is access to the Internet) and have always found everything goes quite well.
Transferring an existing project into the new process goes along these lines:
Download existing project via FTP into the local environment folder.
Share the new plugin/theme with GitHub.
Develop and test in local environment.
Deploy to a test server for online testing.
Commit/push changes to GitHub.
Repeat steps 3 through 5 as needed.
Release to the appropriate WordPress repository.
Starting a new project would work in a similar fashion … maybe.
The discussions on twitter gave me reason to reconsider local development so I will give this some time, namely the 30 day demonstration period attached to PhpStorm. If all works out I may just spend the $99 for the application and make this my new workflow.
I write plugins for many reasons. Sometimes there is a need; sometimes it’s a Mallory-Everest exercise but every time it is with the full intention of releasing the plugin to the WordPress Extend repository. Currently I have eight plugins freely available and hosted at WordPress, and one more (which is a minor modification of another author’s plugin) hosted at BuyNowShop.com.
Although my schedule has been filled with my WordPress Theme Review Team activities of late, I still make every effort to maintain the plugins in the repository at a “current” level relevant to the current stable release of WordPress itself. I also make every effort to insure the plugins are relatively future-proof so I do not have to drop everything to update them with each new release.
I also work with feedback from end-users to add additional functionality as well. If I feel the new functionality would have widespread appeal then I add it to the plugin’s TO-DO list; if it seems unique or what I expect to be a rarely implemented idea I will suggest the end-user attempt to modify the plugin (sometimes with the necessary code changes as well); or, I may offer to make the modifications for a fee. This of course is also dependent on the end-user’s request and where they want to implement the plugin … I have been known to provide my services pro-bono if the cause is right.
I have received some donations related to my works, both themes and plugins, and I find it to be a great reward. I don’t look at the monetary value; I look at it as a reward of recognition. A donation tells me someone liked one of my plugins (or themes) well enough to express their gratitude with their hard-earned money. A simple thank-you comment or email is great, but I recognize and appreciate the extra efforts it takes to give monies, or other gifts, too.
I’d like to take this opportunity to thank all the people that have made donations, both to myself and to all the other designers and developers that keep the lifeblood of WordPress flowing.
BuyNowShop: Shades 1.6 – The free WordPress Theme Shades version 1.6 is now live as of September 14, 2010.
Rattitude: H2 – … aka Aramis, one of our three boys from the Toronto Humane Society is this week’s Rat of the Week.
A short interlude of space and time can always be filled with substance from another place.
Is it a benefit or detriment to write on more than one site?
Some might argue the case it is splitting your readership to post on several sites while others may put forward the thought that each site represents a distinct content set.
I agree with the latter idea, but I can understand the merits to the first camp’s premise of keeping your readers focused on one site to better maintain their interest. It is under that same premise that I generally separate my content so my readers are able to focus on like content aside from it all being from the same author.
If you write on multiple sites, how do you separate your post ideas?
