Something else to consider is what to do with priorities. It might make sense to set one when confirming bugs, it's hard to get right without spending a lot of time really but maybe helpful for contributors even if not very accurate.<br>
<br>On Thursday, 10 April 2014, Daniel Narvaez <<a href="mailto:dwnarvaez@gmail.com">dwnarvaez@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br><br>On Thursday, 10 April 2014, Gonzalo Odiard <<a href="javascript:_e(%7B%7D,'cvml','godiard@sugarlabs.org');" target="_blank">godiard@sugarlabs.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Apr 9, 2014 at 7:29 PM, Daniel Narvaez <span dir="ltr"><<a>dwnarvaez@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>On Wednesday, 9 April 2014, Gonzalo Odiard <<a>godiard@sugarlabs.org</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 9, 2014 at 11:53 AM, Daniel Narvaez <span dir="ltr"><<a>dwnarvaez@gmail.com</a>></span> wrote:<br>
<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">This is an interesting blog post with a paragraph about GNOME triaging<div>
<br></div><div><a href="http://afaikblog.wordpress.com/2014/04/09/enabling-participation/" target="_blank">http://afaikblog.wordpress.com/2014/04/09/enabling-participation/</a></div>
<div><br></div><div>Interestingly it's pretty much exactly the same approach I followed with the triaging I had done with 0.100. It would be good to have a simple set of rule like that written down before the meeting. I think the way we triage has a huge impact on lowering contribution barriers,<div>
<br></div></div></blockquote><div><br></div><div>+1</div><div><br></div><div>We need at least verify all the "Unconfirmed" tickets. We can start now, don't need wait until the triage meeting.</div><div>I assume, if the bug is confirmed, we should set:</div>
<div>Milestone = 0.102</div><div>Status = New</div></div></div></div></blockquote><div><br></div></div><div>I wonder about Milestone. It seems like it would only be useful if we assign different milestones to tickets and I'm not sure we can do that without being able to allocate resources to fix them. It's also a time consuming task.</div>
</blockquote><div><br></div><div>True.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>or close them if are not longer present.</div>
<div><br></div><div>Would be good if we can reset all the priorities to "Unassigned", </div><div>
in all the tickets with module=Sugar,the field content does not have any sense right now.</div></div></div></div></blockquote><div><br></div></div><div>Do we want to use the field? Otherwise maybe there is a way to just get rid of it.</div>
<span><font color="#888888">
<br><br></font></span></blockquote><div><br></div><div>Just to mark they have been triaged, and based in the querys used in <a href="http://bugs.sugarlabs.org" target="_blank">bugs.sugarlabs.org</a> home.</div><div>Do you propose doing in another way?</div>
</div></div></div></blockquote><div><br></div><div>The home queries uses status == unconfirmed for untriaged. The tickets I set status = new (not that many left) have been confirmed. I had reset everything to unconfirmed before starting to triage.</div>
<br><br>-- <br>Daniel Narvaez<br><br>
</blockquote><br><br>-- <br>Daniel Narvaez<br><br>