<div dir="ltr">Hi<br><div><div class="gmail_extra"><br>> Additionally, there is some history to Bugzappers as a separate project<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
which was before my time, but as Johann has explained it to me, it was<br>
something of a 'I'm taking my ball and going home!' thing that led to it<br>
being set up as a separate sub-project outside of QA<br></blockquote><div><br></div><div>.IIRC Bugzappers as a group existed years before "QA" as a project existed but that isn't really important now. <br><br>
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Put those together, and it seems sensible to at the minimum drop the<br>
Bugzappers onboarding process. We can probably look at moving the useful<br>
content from the Bugzappers wiki space back into the QA space at some<br>
future point<br></blockquote><div><br></div><div>Yeah. When we originally setup Bugzappers, we had quite a few members actively triaging, creating scripts and so on for a while and I believe it did improve the overall quality of the project and provided a way for people to do some drive by contributions. We might want to revive this effort again at some point. Matej Cepl and others had some scripts, browser extensions etc to help out. <br>
<br></div><div>Rahul<br> </div></div></div></div></div>