Some of you should know that we started releasing bug fixes for the problems you guys found.
Earlier this week we gave a hard look to the current state of things with software platform and drew main conclusions of how we should proceed with further development.
1) Enhancing current user experience – We are the first to gladly dump a good product for a great one. We observe users’ behavior on WackWall-powered sites, read their feedback, use the platform for our own projects and permanently look for ways to make users’ lives easier. Even if it requires dramatic changes.
2) New features – First things come first. We carefully plan what we do next, based on our experience in community site building, your feedback, and again monitoring how your audiences use your sites.
3) Bugs and stability issues – Find’n'kill. No prisoners.
We hate bugs as much as you do. Maybe even more. Basically we will strive to eliminate technical problems as soon as we read your report on the support boards. Same day. Hopefully, same hour. We owe it to you guys.
Of course, this is possible for things under our control. If Yahoo blocks our mail servers we can’t solve it right away. Server slowness and insufficient resources are also not a piece of cake. But if your site shows you software error message we can shoot a problem in the eye once we get sufficient details from you. Some bugs will require more time if database structure is involved but this is not the case with most software problems out there.
Currently we have about a dozen open bugs. We will solve them all first and then do everything so they don’t pile up. Our goal is normally not having a single open bug any day. With more and more functionality introduced and more people using WackWall this is going to be harder but still possible. OpenWack is the kind of a software platform that may allow it.
Think of it: every bug will be reported only once. Response that you get from us would typically be “thanks for report, fixed that.”
What you can do to help:
Provide sufficient bug reports, and… provide good bug reports. Did I mean providing well-written, detailed bug reports? Read this essay before you submit any problem. It is not about web-software in particular but it’s a good guideline to understand efficiency in report-fix chain. When we need less time to figure out problem details we have мore time to develop new features and enhance user experience.
Let’s see how we do it together.
Tags: bugfixes
[...] all the fun can now be tracked at WackWall you might find it interesting how we approach bug fixing at the [...]
[...] WackWall Blog All about creating your own social network « How we handle bug reports [...]
[...] bugfixes and security patches are still issued on discovery and without [...]
Well I may have encountered a BIG BUG then … Hope you can help and answer soon. Thanks for it.