<div dir="ltr">it's hard to make the project more reliable, when people don't report troubles anywhere - we have a bugzilla for that<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Feb 4, 2013 at 3:39 PM, Petr Bena <span dir="ltr"><<a href="mailto:benapetr@gmail.com" target="_blank">benapetr@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Can you move your bot to bots-bnr1 and report any packages to install via bugzilla, if any? That will prevent any troubles.<br>
<br>All bots-N instances are for testing only<br></div><div class="gmail_extra">
<br><br><div class="gmail_quote"><div><div class="h5">On Mon, Feb 4, 2013 at 3:28 PM, Ryan Lane <span dir="ltr"><<a href="mailto:rlane@wikimedia.org" target="_blank">rlane@wikimedia.org</a>></span> wrote:<br></div>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
<div dir="ltr"><div>On Mon, Feb 4, 2013 at 4:22 AM, Sumana Harihareswara <span dir="ltr"><<a href="mailto:sumanah@wikimedia.org" target="_blank">sumanah@wikimedia.org</a>></span> wrote:<br></div><div class="gmail_extra">
<div class="gmail_quote"><div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br>
It'd be good if there were a clear list of what the most serious issues<br>
are, so I started looking in Bugzilla.<br>
<br>
I see that we have about 106 open issues in Bugzilla against various<br>
components in Labs[0], including 43 non-enhancement bugs against<br>
Infrastructure/General/Other[1]. Are those prioritized right now in<br>
about the right priority, reflecting what Ryan and Andrew want to be<br>
working on next? Does the list need bug triage? Since some of the bug<br>
reports are several months old, would it be useful for someone to go<br>
through and check old ones for reproducibility?<br>
<br></blockquote><div><br></div></div><div>We don't have a documented priority list, currently. Since it's only Andrew, Mike and myself and our general skillsets cover different things, we've been handling this on the fly.</div>
<div><br></div><div>Mike has been doing bug wrangling, shell requests, project requests, etc. Andrew has been handling labsconsole interface bugs and general usability bugs as of late. I've been working on stabilization and performance improvements as of the last couple weeks.</div>
<div><br></div><div><div>I've begun organizing bugs into projects:</div><div><br></div><div><<a href="http://www.mediawiki.org/wiki/Wikimedia_Labs/Account_creation_improvement_project" target="_blank">http://www.mediawiki.org/wiki/Wikimedia_Labs/Account_creation_improvement_project</a>><br>
</div><div><<a href="http://www.mediawiki.org/wiki/Wikimedia_Labs/Instance_creation_improvement_project" target="_blank">http://www.mediawiki.org/wiki/Wikimedia_Labs/Instance_creation_improvement_project</a>><br></div>
<div><<a href="http://www.mediawiki.org/wiki/Wikimedia_Labs/Interface_usability_improvement_project" target="_blank">http://www.mediawiki.org/wiki/Wikimedia_Labs/Interface_usability_improvement_project</a>> </div>
<div><br></div><div>In general we determine priority of the tasks ourselves and tackle the ones we think will have the most impact.</div></div><div><br></div><div>Since we'll be adding a number of people into the mix soon, we should have a weekly meeting and start handling ticket triage in a saner way. I'm a fan of letting people determine priority themselves. If anyone has a concern that a specific bug isn't being addressed they should be raising a flag on the list and we'll discuss re-prioritization there, in-between meetings.</div>
<div><br></div><div>For meetings themselves, I'd like to have open google+ hangouts, with the ability for all volunteers to join in and raise concerns.</div><div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
(And btw, when should we be reporting issues in the "General" component<br>
versus "Infrastructure"?)<br>
<br></blockquote><div><br></div></div><div>General should be used if people don't know where to put a ticket. Infrastructure is for reporting bugs against things that affect all projects, like glusterfs or LDAP issues. A bug for adding replicated DB support, for instance, would go under Infrastructure.</div>
<div><br></div><div>For bugs specific to bots or tool labs that don't affect other projects we should have a component for those bugs.</div><span><font color="#888888"><div><br></div><div>- Ryan</div></font></span></div>
</div></div>
<br></div></div><div class="im">_______________________________________________<br>
Labs-l mailing list<br>
<a href="mailto:Labs-l@lists.wikimedia.org" target="_blank">Labs-l@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/labs-l" target="_blank">https://lists.wikimedia.org/mailman/listinfo/labs-l</a><br>
<br></div></blockquote></div><br></div>
</blockquote></div><br></div>