<div class="socmaildefaultfont" dir="ltr" style="font-family:Arial, Helvetica, sans-serif;font-size:10.5pt" ><div dir="ltr" >Good discussion topic, Andrew.</div>
<div dir="ltr" > </div>
<div dir="ltr" >My thoughts:</div>
<div dir="ltr" >==========</div>
<div dir="ltr" > </div>
<div dir="ltr" >First of all, bug should be associate with SLA/some kind of metrics on how quickly it gets resolved.</div>
<div dir="ltr" > </div>
<div dir="ltr" >Bug submitter is already started donating/contributing to the community by pointing the issue in the code,</div>
<div dir="ltr" >when bug submitter opens an issue.</div>
<div dir="ltr" > </div>
<div dir="ltr" >It is the maintainer (other assigned person) responsibility to accept (fix the bug) or prove it is not in their</div>
<div dir="ltr" >area and pointed out the issue/bug to the other repository with details. (From the horse's mouth)</div>
<div dir="ltr" > </div>
<div dir="ltr" >If the ownership of moving/closing bug to the submitter, I feel the point of isolating the bug may not happen accurately.</div>
<div dir="ltr" > </div>
<div dir="ltr" >Second point (back to SLA), If the submitter owns it then SLA/Metrics may not be accurate. This will be totally different than what normally industry follows, I guess.</div>
<div dir="ltr" > </div>
<div dir="ltr" >Real Life Scenario:</div>
<div dir="ltr" >===============</div>
<div dir="ltr" >For eg. if person A points out issue/bug in person B shirt, Can person A responsible to change person B shirt?</div>
<div dir="ltr" > </div>
<div dir="ltr" > </div>
<div dir="ltr" > </div>
<div dir="ltr" ><div class="socmaildefaultfont" dir="ltr" style="font-family:Arial;font-size:10.5pt" ><div class="socmaildefaultfont" dir="ltr" style="font-family:Arial;font-size:10.5pt" ><div class="socmaildefaultfont" dir="ltr" style="font-family:Arial;font-size:10.5pt" ><div class="socmaildefaultfont" dir="ltr" style="font-family:Arial;font-size:10.5pt" ><div class="socmaildefaultfont" dir="ltr" style="font-family:Arial;font-size:10.5pt" ><div dir="ltr" style="margin-top: 20px;" ><div style="font-size: 12pt; font-weight: bold; font-family: sans-serif; color: #7C7C5F;" >Sivas R. S</div>
<div style="font-size: 8pt; font-family: sans-serif; margin-top: 10px;" ><div><span style="font-weight: bold; color: #336699;" >E-mail: </span><a href="mailto:sivas.srr@in.ibm.com" style="color: #555" >sivas.srr@in.ibm.com</a></div>
<div>E2E FSP Test Architecture, OpenBMC Test Lead, Lab Management</div>
<div>Automation is good, Identifying Defect earlier is better always</div>
<div>9902233500</div>
<div>08046678273</div></div></div></div></div></div></div></div></div>
<div dir="ltr" > </div>
<div dir="ltr" > </div>
<blockquote data-history-content-modified="1" dir="ltr" style="border-left:solid #aaaaaa 2px; margin-left:5px; padding-left:5px; direction:ltr; margin-right:0px" >----- Original message -----<br>From: Andrew Geissler <geissonator@gmail.com><br>Sent by: "openbmc" <openbmc-bounces+sivas.srr=in.ibm.com@lists.ozlabs.org><br>To: Adriana Kobylak <anoo@linux.vnet.ibm.com>, OpenBMC Maillist <openbmc@lists.ozlabs.org><br>Cc:<br>Subject: openbmc bug management<br>Date: Mon, Aug 13, 2018 9:34 PM<br> <br><tt><font size="3" face="" >Currently we mostly open bugs against openbmc/openbmc. This is nice</font></tt><br><tt><font size="3" face="" >in that it provides a single location to search for all bugs related</font></tt><br><tt><font size="3" face="" >to openbmc, but it doesn't provide any clear ownership for someone to</font></tt><br><tt><font size="3" face="" >drive the bug, and it becomes more and more unmanageable as the</font></tt><br><tt><font size="3" face="" >openbmc project continues to grow.</font></tt><br><br><tt><font size="3" face="" >Per the community call topic today, we'd like to start having bugs</font></tt><br><tt><font size="3" face="" >assigned to the specific repo that will provide the fix to the bug.</font></tt><br><tt><font size="3" face="" >The main concern with this is that if someone is unsure on where the</font></tt><br><tt><font size="3" face="" >bug should go and takes a best guess, if the guess is wrong, how do we</font></tt><br><tt><font size="3" face="" >ensure the bug gets routed correctly? The idea was that it's the</font></tt><br><tt><font size="3" face="" >responsibility of the creator of the bug, so the repo owner says</font></tt><br><tt><font size="3" face="" >something to the affect of "not my problem" (with some guidance on</font></tt><br><tt><font size="3" face="" >who's it is if they know) and the bug submitter will then use the</font></tt><br><tt><font size="3" face="" >zenhub option "Move Issue" to close it in the current repo and copy it</font></tt><br><tt><font size="3" face="" >over to the new repo.</font></tt><br><br><tt><font size="3" face="" >Thoughts or concerns?</font></tt><br><tt><font size="3" face="" >Andrew</font></tt></blockquote>
<div dir="ltr" > </div></div><BR>