The last week has seen some movement on a couple of the open source projects I’ve been involved with in the past couple of years. I’ve already spoken about the first one but now I’m going to talk about the other project that I had such high hopes for which have been washed away and effectively thrown back into the faces of those that actually devoted their time into producing the goods, I am of course talking about Shuttle.
For those in the dark I’ll give a brief history of the WordPress Shuttle project. The idea first came to me after I had just finished my work on the Manji theme. I had so much fun collaborating with people online and producing something that could be used by other people (and thus giving back to the software that runs my site), that I really wanted to get back into the game straight away. I talked to Joshua and the Chris, both of whom I have the greatest amount of respect for, both of which were completely up for the project. By sheer luck Michael was having thoughts about this of his own as well. He was more than happy to join the team and in doing so brought Matt’s (Lead WordPress developer and Automattic head honcho) attention. The endeavour was now considered more than just hot air. In a very shrewd move Michael brought in Joen and thus the initial Shuttle team began work. Because a picture paints a thousand words, this is the screen shot of what we had to work with when we first started:
)
If you’re interested to see more, you can have a look at a Carthik’s screenshots for WordPress version 1.5.
We started work in earnest and the emails began flying between us. We were talking about everything and anything that came to our minds. We did research of all the existing blogging software tools (and the time those that hadn’t been released yet). We talked about usability, advanced users, novice users how things should work, how things should not work, what areas we should concentrate on. Seeing as we’re all bloggers we decided to give the call out to people to find out what they thought as well:
- http://www.brokenkode.com/archives/shuttle-development/
- http://binarybonsai.com/archives/2005/02/01/wordpress-shuttle/
- http://www.brokenkode.com/archives/shuttle-workshop-01-dashboard/
- http://www.chrisjdavis.org/2005/01/31/the-cat-she-is-out-of-the-bag/
My initial thinking was heading towards something completely radical to what we had. Just strip the walls down and start implementing things in a completely different way. I don’t know if I can find the very initial mockups I started flirting with but you can check out the image set to show a lot of the initial design development. This is where working in a team is paramount. I remember Joen distinctly pointing out that the fundamental structure of WordPress was fine and that we shouldn’t be rocking the boat for the sake of it but rather finding what works and what doesn’t. Making things simple for the user. I’m completely paraphrasing probably a couple of weeks worth emails beings fired between the ENTIRE design team, which of course included Matt at every step of the way (we didn’t have a mailing list until Matt set one up for us). It was agreed that we wouldn’t move to anything radical unless we felt it served a specific purpose.
I should have seen the writing on the wall to be honest. As the design went forward Matt seemed to implement things he liked and not bother with things he didn’t. So the blue hues made it into the design, as did the pods on the side, but little else. To be fair to him at this stage we really hadn’t moved every single aspect forward as you see it in the final mock ups.
The days went by and action on Shuttle was sporadic at best. We’d go through these massive bursts of creativity and energy and information sharing. Every once in a while one of us would prod the team to get it’s finger out and continue with this project. You might think it should be easy but people have lives and many things to do get in the way and it’s not like any of us didn’t have other projects on at the time.
Lets make one thing clear here. I am a finisher. I complete the projects I’ve actively put my name down for. I’m not in the business of making a claim for something and not going through with it. I’ve proven this time and time again. Even when things get tough, even when it seems like it’s not even worth it, I will continue to plough forward even if it’s only me, with the hopes that those around me will feel good enough for them to contribute as and when they seem fit. Contributing to Open Source should never feel like a chore. It should be fun, it should be something you actually want to contribute towards.
So in a last attempt before I completely gave up on the project I dived into the designs. For two weeks straight I would come in from work and spend 4-5 hours implementing the designs. I tried hard to keep with EVERYTHING we’d discussed in the past. The dos and dont. I tried to find solutions to design aspects we hadn’t really covered. I’ve not had that massive creative burst of energy in years (and this was done on the back end of creating the FOFRedux redesigned UI). I tried taking into consideration things that although I didn’t agree with I had to make concessions to allow for.
A prime example is the dashboard. We were told not to go too far with this because lots of discussions were going on in the hackers mailing list and it would probably be the one place that we didn’t have much say in. This is all well and good, so I tried to come up with a solution I could at least stomach. It’s easily my least favourite page of the entire design.
Once the mock ups had been completed I left them with the rest of the team for comments to be put on the table for them to change whatever everyone felt worked and didn’t work. We then proceeded to discuss how we were going to implement the designs. Matt was NEVER truly forthcoming about how this was all going to be implemented. We discussed the issue further, but once again he was as elusive as ever. When a response finally came back I didn’t know how to react. Thankfully other members of the team did. The designs were not some chicken to pick and choose at what you like and what you don’t like. They present a certain level of uniformity across the pages. They follow a specific design thought, and a great deal of thought and attention to detail has gone into them.
After we talked about it a bit more, and we were promised by Matt that things would get incorporated into the WordPress core, however it would take some time and it was mainly to make sure that people didn’t get jarred with the changes in one go, this was a solution I could honestly live with. The design wouldn’t be hacked but implemented gradually. So I went forward and released the mockups because they were the culmination of our active involvement in the project as things would now begin to get integrated into the core code. Of course things would change or be tweaked as the design was implemented but by and large it would remain the same.
Any which way you cut it that’s why Shuttle never made it into the design of WordPress. It has nothing to do with us being lazy or that we couldn’t be bothered to do anything but the photoshop files. Joshua had begun implementing the design on his own machine, we were discussing the logistics of how this project would be implemented into the code. However as it turns out there doesn’t seem like there was/is any commitment from the WordPress Dev team to incorporate these designs. If there was a commitment it would take 3 guys 4 weeks TOPS to deal with it all. There are well over 100,000 WordPress users, many of which are pretty capable with both CSS/PHP/JS. Hell there are people out there that are already implementing this off their own backs.
It doesn’t seem like the WordPress development team (and by definition Automattic team) are keeping to their word because the latest addition to the Automattic team is now going back to square one to start over, asking people the same questions we did when we first started the project.
Bryan joined the shuttle team late in the game and in some ways I think he didn’t feel as comfortable jumping into the design. He’s a fine addition to the Automattic team, and more importantly I like the guy, so none of this is aimed at him. He has been given new directions by the powers that be. Strip it down, build it up again from the ground if we have to. Why is it called Shuttle:Atlantis? Maybe because Matt didn’t like the first one? That’s what it boils down to to be honest. The alarm bells started going off when I read the first things to come from Bryan over of the WordPress.com blog.
... see that Shuttle finally makes its debut in whatever form we as a team see fit.
So I’d like to address those that didn’t like the Shuttle mockups. You (the collective you) got 5 people (plus 1) devoting a massive amount of their time to make your blogging experience more enjoyable; more usable; more fun. We didn’t ask for compensation and we didn’t ask for anything in return. We didn’t rush into this and we certainly didn’t hack through the designs. We did this because we believed in the sotfware. We believed in the people behind it and the people using it. None of us on the team are new to open source contribution. Michael’s contribution doesn’t need much introduction (Kubrick and K2), similarly with Chris (whose contributions extend far into the past of WordPress, Persian, plugins galore, K2), Joen does this for a living and has contributed for the admin panel on Zenphoto (including the default theme) and his wordpress theme Fauna. I have given the open source world Manji & Rin and contributed in the redesign of the FOFRedux UI. Joshua has answered enough support questions to make my head dizzy. Bryan has contributed to the world ChaoticSoul.
Open source is great because you can contribute to the source in a positive way, otherwise none of us would be actively giving to it so freely. That however is not the universal truth. At least that doesn’t seem to be the case in the WordPress world. This is a shame because part of WordPress’s success is the people involved with the world it surrounds. I have said many times before that is one of the things that elevates it above other open source initiatives.
It’s a shame really. Has WordPress really gotten so big that those in charge of implementing it no longer care for those that devote their time? As long as you’re creating a theme or a plugin that’s great, just don’t even bother thinking about contributing to the final product in any way. That kind of contribution is obviously not welcomed. There was a time when the Shuttle mockups, created exclusively for making WordPress prettier, would have been taken in with grateful arms. It seems that time for WordPress has passed.
Compare the current admin panel with those presented in the Shuttle mockups. Once you’ve done that go back to the top and compare it with Version 1.5.
Do you see something different. One was designed and thought through. The other is an ad hoc implementation of core ideas. I could go on at length to discuss the design decisions to be honest with you however I tend to allow the work speak for itself.
Ultimately I’m extremely proud of the work we did in TRYING to make the WordPress admin a better looking more usable place. The online friendships I’ve forged with the Shuttle team are thanks enough, even though the work we did was ultimately not appreciated. This is probably the very last time that I talk about Shuttle, unless of course someone implements the design aspects of the work we created as a plugin or in another way.