First Impressions Last

After commenting on DosDawgs blog (Path to Dolphin 7.0.1 --> Modules Fail on Install Just wondering WHY?) and not wanting to drag it off topic, I've decided to post a bit more of my thought's on the latest release and it's public perception.

I did start to write a post similar to this shortly after 7.0.1 was released, but when I proof read it - it seemed a bit harsh, so I decided against publishing it. However, as I am now a little frustrated that I cannot efficiently access the forums, which is wasting lots of my time, and not wanting to shun visiting Unity completely, the only other option I can think of is to make some noise about the issue and hopefully provoke some kind of resolution or response.

I am a pretty busy person, and as such my time is very limited. I like to help out the web community (not just Boonex), and so the online time I can spare is shared between whatever online endeavors I'm currently involved in. Recently, every time that I visit the Unity forums, the spy cannot connect, this means that I have to waste time trawling through each forum - this is simply time that I do not have, and whilst I've made a decision to try and help others out, it's simply becoming impossible. But all of this aside, it is just one of the many issues that I believe is harming Boonex's reputation.

I will not criticise the software itself, we all know that it does still have issues, and there will always be conjecture about features, but it is working towards a goal, and that given there are probably limited resources, it's a pretty big job. I see that the real issue here is simply one of management.

It is the same issue that politicians face every day - there's 300 issues to address, but only enough cash to fix 20 of them, so which 20 issues do they fix? Easy - the 20 that will affect the opinion polls - the 20 that effect their majority following - They limit the damage by applying it to the minority. There will always be some collateral damage, as they cannot please everybody all of the time. This is known as damage limitation.

To apply this to what is happening here ate Boonex - it seems that all of the resources are pointed at the next release - this was certainly true of  7.0.1, and seems to be true at present. I believe that there are some issues that are more important than the software itself, After all what good is an excellent bit of software if no one wants to use it due to bad press / public opinion.

So this brings me back to my issue with the forum spy. I'm not the first to comment on it, and if I am having such a massive issue with it, you can bet that others are too. This is not a very good impression to someone visiting the site for the first time, after all, if the authors website code does not work, why on earth would you want to trust them to provide code with which to run your own website.

Epic Fail + Bad impression #1 - Authors website does not work

But this is not the only issue other than the code that leaves a bad impression. The latest release itself has issues with the installer, it does not work. It falls over on Step 1 as you cannot access the installer file. So given that there is an issue, what should be the course of action?? Pretty simple - fix the problem, update the installer, and re-release it with a different release number - 7.0.2. That's what release numbers are for - so that people can differentiate between packages - it does not matter that the core code is the same - the release number does not really apply to the code itself, but the package. (to preempt those that will disagree with this - you are probably getting confused with the build number).

The 6.1.6 release was a prime example of what NOT to do - the package was changed, but the release was not up-rev'd, this meant that there were a bunch of people (like me) who downloaded the earlier faulty package that were unaware that it contained an issue.

So what was Boonex's solution to the broken update script?? To publish some convoluted instructions and advise people via the release blog that they need to remove certain files, and do things in a different order, and stand on one foot and make sure that the wind is blowing in a certain direction... well perhaps not - but they might as well have done. Poor show guys. This is amateurism at it's best.

Epic Fail + Bad impression #2 - Installer does not work and software maintainer expects you to fix it yourself

So put off by a site that does not work, that charges you for the pleasure of using it and software you need to fix yourselves, you go digging a little deeper to find out if it's worth pursuing - and here's what you find. This a first impression that can easily be addressed

Epic Fail + Bad impression #3 - The last major release was a year late

Epic Fail + Bad impression #4 - When it was released, despite the fact that it took a year - it was released with over 300 bugs

Epic Fail + Bad impression #5 - It took 4 months to fix these bugs

Both issues #3 and #5 are related to the release cycle. There has already been a comment made that a monthly release cycle will be adopted - a good idea in my opinion,but Boonex is still missing something - the release date for the next release. As I commented in DosDawgs post - talking about it is one thing - doing it another. I say give us a date and then on that day release whatever you have fixed up - one bug or 20 - it doesn't matter - you just need to publish a schedule and stick to it.

The 300 or so bugs that were shipped with version 7.0.0 is something that should never have happened, and with shorter release cycles it should be more manageable to bugfix and beta test, but one thing that I disagree with is using the community to do this with. For those who do not understand product release cycles, they simply perceive it as unnecessary, and for those who simply look on without being involved, all they really see are lots of bugs and heated conversation about what features / bugs etc should / shouldn't be in / out of the next release.

As I touched on in DosDawgs blog post - this should really be carried out behind closed doors - in a private forum, away from public eyes. The correct way to do it is with a beta test team - volunteers from the community. There is enough of a cross-section of skills with the regulars here, most of which would jump at the opportunity to be involved - Not only to help out, but because there is also a certain status attained in being a part of something like that. This way you can carry out beta testing behind closed doors without everything hanging out for all to see. The only time you present a release to the public at large is when you have a release candidate. If this had been the case with 7.0.1 no one would even be aware that it took over 300 bug fixes to achieve. As the proverb goes - hindsight is wonderful thing - but only if used correctly

Epic Fail + Bad impression #6 - Despite improvements, there is still a serious lack of official support in the forums

This is still a big gripe, and whilst things have improved, there are still many posts that remain unanswered with a definitive official answer. I know that some of the regulars will take offense to this - and I am aware that they answer a majority of the posts, but sometimes the only answer is an official one. Unfortunately, the impression that you get is that there is no input from Boonex at all.

Whilst it's easy to criticise, it's also easy to fix. Give staff a 'Staff' tags instead of 'premium' or whatever status they are - this helps raise exposure - also - you need to relook at your mods scheme, even mods opinions have a little more acceptance from the general public, The only issue is that there is not really any benefit to being one - especially when everyone has the expectation that a mod can deal with certain issues, and in reality they can't as they have no power to do so - a lot of extra responsibility for no extra benefit. It seems to me that you have tried to address this issue in the past with pundits and mods and it's failed both times. The main reason that I can see is with both mods and pundits, you are trying to maintain a degree of separation between Boonex and the 'hired' help.

The easy fix is to make more people staff members - if you are a moderator - you are staff - paid or not - you already have the responsibility of being trusted with up-keeping Boonex's reputation, why not  give them a different badge and help get rid of the impression in the forums that Boonex does not care. And for those willing to be more than a moderator - to take on the role of an official forum support agent - why not offer memberships as payment.

Ie - you are a trusted regular in the forums - your opinion is already respected, and you answer most of the enquiries

This is of course simply spin - and every good politician and manager knows how to use it to their advantage. This brings me right back the importance of the role of the manager - and whilst some have already commented on my want to 'play at being a manager' here, I would just like to say that I have no intention of spending any more time here than I already do. Without sounding full of myself, I already run a successful software company, and I am simply trying to impart some of my knowledge and experience in the hope that it helps.

I think you should strongly consider putting in some additional procedures - especially surrounding releases and the way they are handled. I'm not saying that my solutions / suggestions are the only way of dealing with these issues, simply that there are issues that need addressing.

In summary - my advice is simply keep an eye on the bigger picture - do not forsake everything for the sake of the development.  Without the site / forums / support / reputation, the software is nothing.

/DM