Software bugs are miserable things in any context.  But when you have a small project like music4dance where there are so many external dependencies, bugs can creep in even when nothing has changed in the project.  Add that to all of the normal avenues of bug creation and things can turn into a mess very rapidly.  I have to balance very limited amount of time on music4dance between creating content (like this blog post), curating content on the site, adding new features, testing and fixing bugs.  Not to mention adding automated testing and production logging.

Needless to say, this gets very complicated very fast and things slip through the cracks.  And then you end up with anywhere between a slightly annoying to a completely unusable experience.  This obviously not good for anybody and frustrating for all.

But there are thousands of you out there that visit music4dance regularly.  So if you report bugs as you see them, hopefully we can nip them in the bud and make the experience better for everyone.  I can’t promise to fix every bug that comes through but I’ll do my best to keep up so that everyone’s experience is improved.

And to sweeten the pot I’d like to offer a bug bounty for each unique bug reported.  Check out our Bug Report page for details.

As always, I’m interested in feedback beyond bug reports so feel free to respond to this post or use our feedback page.