Quoted from the sheet's
Discussion and Development forum in case there are those who read this forum but not that and share these concerns.
|
Originally Posted by arfarfdoggybounce
I'm not sure if anyone knows but duffry hasn't killed Yogg on 10 or 25 man yet, and I'm not even sure bakka, or anyone approved of duffry taking over this project? Or can we at least know about your game experience and qualifications? I know A LOT of people rely on this spreadsheet.
Also, might want to stop making new spreadsheet versions every 2 days. Just wait until the bug reports and suggestions start to slow down and then release it then.
|
Since I am hosting this sheet, it's discussion and development forum and supporting wiki pages on my guild/community site it should be fairly easy for anyone to get an idea of my experience but since you asked so nicely I'll put down a condensed version.
I started playing WoW casually during Vanilla while the DMZ community (of which I'm a founder) were still focussed on the Battlefield games where we competed in Euro clan matches. The serious BF community was gasping it's last at the time so we were looking for something new and moved over to WoW shortly after TBC. I supported the guild through levelling to 70 and then organised and led raids from first steps into Karazhan. We have maintained a 'community > progress' attitude since the beginning but despite starting late in TBC we take our raiding seriously. We cleared all TBC bosses outside Sunwell before the pre-LK uber-nerf again with my organising and leading the raids. In Wrath I have continued to lead the raiding and (as you have seen) we have cleared content up to Yogg (25 man guild focus), with all T7 including TV and TZ. I have variously played all lock specs in PvE and tanked all the regulars (Leo, Cap, Illi) and void-tanked Sarth 10 & 25 and even Kalecgos in that crazy time while void threat was off the chart. The lock has been my main throughout all of that.
Outside of WoW I work in software development for an international consultancy firm and have experience within design, build, test, implementation and support phases of the project development lifecycle as well as some management experience.
If you were to look about on EJ and bakkadps.com you would see that I made numerous fruitless attempts to contact Bakka and made calls for anyone else interested in maintaining the sheet to step forward. Since it was silent on both counts I started looking closer at the sheet and what known issues there were with it. As a lot of people do use this sheet I was unhappy to see it undeveloped and so started to apply fixes and release updates. I don't see that the sheet has any owner, merely custodians. The sheet belongs to the community that uses it and as such anyone could develop and release their own changes. This could obviously become very chaotic very quickly, hence it is wise to have a custodian who can administer the development and co-ordinate releases.
I appreciate your suggestion about release scheduling however I think you might be exaggerating somewhat. I have no intention of releasing new versions every couple of days. However when a significant bug is detected and a fix is known it is no great bother to release it and no real benefit in not doing so. I'm keeping a clear and accurate changelog so anyone seeing that their current version is out of date can quickly check to see if the new changes are pertinent to them and decide if they need to upgrade. This changelog can be easily reached from the link on the info tab within the sheet itself.
I recognise your concern that 'just anyone' might have picked up development of a resource you rely on and that this person might be a total noob and ruin everything. I had the same concerns myself. I do not pretend to be the best theorycrafter, player, warlock or... well anything but I am prepared to look after this sheet and develop it for the better. I will be taking a more 'open to the community' approach than has been adopted in the past and (as you can see) I've started exposing the formulas and mechanics used to make them more accessible and easier to update (reuse of common components etc).
I hope this addresses your concerns and those of anyone that shares them. I didn't think I would have to essentially apply for the job since I seemed to be the only one volunteering to invest the time and commitment into doing it.