AKA #BugSmasher Initiative
Back on August 21st 2015 we reported on the start of the Operational Support Team initiative driven by @LaughingTrendy, a player-supported bug reporting and dev-managed application process. What sets this apart from previous efforts is that the developers are actively experiencing and watching the issues as they happen, while the reporting players have been given access to a formal reporting process and private blog.
The effort is very horizontal impacting players from role players to the DPS crowd. And it’s something every player wants to know more about.
In our initial report, we saw rapid changes and a few role-backs. Since that time the Bugsmasher teams have been relatively quiet, and the process has been protected (for many reasons) behind a private forum. @LaughingTrendy took the time to answer a few questions to bring us up to speed on their process.
Q1: Looking back over the last month, how would you characterize the status of the project in terms of identifying issues?
The entire Operational Support team really was something that not only I was excited about, but also QueenVaccine (STO’s Lead QA). We’ve been working together to craft the initiative and it has paid off. We’ve made it efficient, which has lead to some really awesome player/dev interactions to hunt down bugs. I’ve gotten to see bugs reported by players in the Operational Support team get checked in, worked on, and had fixes that have already hit Tribble. I’m thrilled.
Q2: How many players are now part of the process? Can you talk about a few of the standout participants?
We have a few dozen players that are part of the initiative. I’ve definitely seen some participants that have lead the charge, even helping refine the process further.
Q3: In terms of visible changes, can you give examples driven by the initiative that should be visible to the player-base?
Laughing and I chatted for a bit, and her response is best summed up by this weeks Tribble Patch notes.
Q4: How has the collaborative process worked in terms in identifying issues?
Originally the process was a very standardized set of issues that members would report in and we’d confirm or try to seek out more details. It’s organically evolved to include other members helping add data to bugs that are reported, clarify repro steps, and shine more light on it. It’s now not just a collaborative player-developer process, but a player-player process.
Q5: Has the new initiative presented any challenges?
Not really challenges necessarily. As I’ve never constructed something like this before, I did need to spend some time going through iterations and defining it. It wasn’t hard, but it did take time and due diligence to make sure it would work right.
We chatted about the initiatives and the extra time it’s taken to get it off the ground: Normally when I integrate a project, I go through these iterations in a standardized process. This was something I burned some midnight oil on to make happen as quickly as it did, because this was something I really felt the community wanted to see. I’m glad I did.
Q6.1: In the absence of updates some vocal players feel left out, references to Secret Societies hidden behind password protected forums leads some to question “what’s happening?”. Identifying new exploits aside , a obvious reason why you don’t socialize this type of information, can you speak to the necessity for keeping the process restricted to trusted partners?
Exploits is the large reason. We’ve had exploits reported in from our group already, which is why I decided to make it a private initiative. The group is a very tight-knit set of people that work together on hunting these bugs down, and I want to afford them their own space to make that happen.
Q6.2 Communication is key. Given that the initiative is a work in progress, do you plan to provide scheduled updates?
I’ll probably be speaking more about it as it continues to grow. I’m not sure about regularly scheduled updates, but if the community wants to know more about it (besides exploits) I’m happy to talk more!
Q7: How do you see this initiative scaling moving forward? and are you still looking for a few good testers?
Right now I haven’t been scaling it up any bit because now that we have the process pretty refined, we’re getting into a rhythm for it. I want to give some time for people to (become) veterans and (develop) efficiency before I bring in new people.
Are these players being primed as mentors for new testors at some point?
Primed? Not formally. But these Bug Hunters are really big on peer mentor-ship already, so I want to give them some time to develop before I throw in more greenies. 😛
I want to thank Morrigan (@LaughingTrendy) for taking the time to update us on the progress.