<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Feb 17, 2020 at 9:53 PM Amar Tumballi <<a href="mailto:amar@kadalu.io">amar@kadalu.io</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><br><div dir="ltr"><br><div class="gmail_quote"><br><div dir="ltr"><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"><br>> I did manually export the list of components from bugzilla to<br>
> <a href="https://lite.framacalc.org/9f29-glusterbugzilla" rel="noreferrer" target="_blank">https://lite.framacalc.org/9f29-glusterbugzilla</a><br>
><br>
<br></blockquote></div></div></div></div></div></div></blockquote><div><br></div><div>Went through the sheet, and added 2 columns. One for Currently open bugs for each component. Second, for every 'Gray' (not decided) cell, added options to migrate. With that data, we need to move 2 bugs to glusterdocs, and 1 bug for website. Otherwise, 51 bugs are project-infrastructure related (Its marked green, and I am assuming it will be taken care?). All other issues gets to glusterfs repo only.</div><div> </div><div>I will fine tune a script I got to pick a given bug, and migrate it to github. Here is my plan on how we can work on this (writing it again as I missed some communication before, happy to make changes if one feels).</div><div><br></div><div>1. Get a list of open bugs as CSV.</div><div>2. Remove 'project-infrastructure' and other 3 bugs mentioned above from the list.</div><div>3. Get a list of remaining OPEN bugs and feed as argument to a script. </div><div><br></div><div> - We can make all this automatic, but I would prefer to have a validation before hand.</div><div><br></div><div>Now what script does:</div><div><br></div><div>- pick a bug from the above list:</div><div> * Get complete public-data (I plan to use my ID, so I get only public information).</div><div> * Feed this to github API.</div><div> - bugzilla.subject + bugzilla.ID ~= github.issue.title</div><div> - bugzilla.description + Bugzilla Link ~= github.issue.body</div><div><div> - github.issue.labels = [ 'Type:Bug', 'MigratedFromBugzilla' ]</div></div><div> - github.issue.assignee ~= search_and_map(bugzilla.assignee)</div><div> * Get Github Newly created Issue ID/URL</div><div> * Update the github issue with bugzilla comments and other parameters like keywords / WhiteBoard etc.</div><div> * Update bugzilla with new github issue link. </div><div> * Update bugzilla status to CLOSED -> UPSTREAM. (Or decide on the Resolution).</div><div><br></div><div><br></div><div>Now, considering we would be CLOSING the bugs in the script itself, if any bugs got created during this process, we can still get that and feed it to the same script, after marking bugzilla product not to take new bugs.</div><div><br></div><div>Meantime, we need to change github issues template, so if someone goes to open an issue, it doesn't points to bugzilla :-D I believe the best time to do this is after running the first round script, and before marking bugzilla product not to accept new bugs.</div><div><br></div><div>Also we have to identify the documents which mention bugzilla workflow, and change it to Github Issues Workflow, and change them.</div><div><br></div><div>Regards,</div><div>Amar</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><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">
This is nifty. Thank you!<br>
<br>
@Amar Tumballi - I'd need some help to ensure that I'm doing the<br>
mapping (below) correctly<br>
<br></blockquote><div><br></div><div>Sure!</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
> So we do have a few that I do not know where to migrate:<br>
> - coreutils<br>
<br>
<a href="https://github.com/gluster/glusterfs-coreutils" rel="noreferrer" target="_blank">https://github.com/gluster/glusterfs-coreutils</a><br>
<br></blockquote><div><br></div><div>Correct</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
> - doc<br>
<br>
<a href="https://github.com/gluster/glusterdocs" rel="noreferrer" target="_blank">https://github.com/gluster/glusterdocs</a><br>
<br></blockquote><div><br></div><div>Correct (There are few which are part of glusterfs repo itself like manpages, but I guess we can cross link the issues within the org).</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
> - gluster-colonizer<br>
<br>
<a href="https://github.com/gluster/gluster-colonizer" rel="noreferrer" target="_blank">https://github.com/gluster/gluster-colonizer</a><br>
<br></blockquote><div><br></div><div>Correct</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
> - glusterd2<br>
<br>
<a href="https://github.com/gluster/glusterd2" rel="noreferrer" target="_blank">https://github.com/gluster/glusterd2</a><br>
<br></blockquote><div><br></div><div>Correct. But Ideally, if there is anything OPEN, we can close it with WONTFIX.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
> - glusterfind<br></blockquote><div><br></div><div>This is part of glusterfs repo itself - <a href="https://github.com/gluster/glusterfs/tree/master/tools/glusterfind" target="_blank">https://github.com/gluster/glusterfs/tree/master/tools/glusterfind</a></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
> - gluster-hadoop<br>
<br>
<a href="https://github.com/gluster/glusterfs-hadoop" rel="noreferrer" target="_blank">https://github.com/gluster/glusterfs-hadoop</a> (?)<br>
<br></blockquote><div><br></div><div>Correct. Again, if there is anything OPEN, we can close them with WONTFIX.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
> - gluster-hadoop-install<br>
> - HDFS<br>
</blockquote><div><br></div><div>All hadoop can be mapped to the same above repo, but again, we can close them all.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">> - nagios<br>
<br>
<a href="https://github.com/gluster/nagios-server-addons" rel="noreferrer" target="_blank">https://github.com/gluster/nagios-server-addons</a><br>
<a href="https://github.com/gluster/gluster-nagios-common" rel="noreferrer" target="_blank">https://github.com/gluster/gluster-nagios-common</a><br>
<a href="https://github.com/gluster/gluster-nagios-addons" rel="noreferrer" target="_blank">https://github.com/gluster/gluster-nagios-addons</a><br>
<br>
(I'm not sure which of the above is appropriate)<br></blockquote><div><br></div><div>I would pick `gluster-nagios-common`.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
> - nfs<br>
</blockquote><div><br></div><div>I would like to believe these are 'gNFS', which means, it is part of glusterfs.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">> - packaging<br></blockquote><div><br></div><div>While there are 2 repos (glusterfs-debian, glusterfs-SUSE), I would like to keep this as part of glusterfs itself, for now.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
> - puppet-gluster<br></blockquote><div><br></div><div>All bugs which are OPEN can get CLOSED (WONTFIX/TIMEOUT).</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
> - selinux<br>
<br>
<a href="https://github.com/gluster/glusterfs-selinux" rel="noreferrer" target="_blank">https://github.com/gluster/glusterfs-selinux</a><br>
<br></blockquote><div><br></div><div>Correct</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
><br>
> Some mention a upstream, some look like external repos.<br>
><br>
> If people have a opinion, please tell me in this thread.<br>
><br>
></blockquote><div><br></div><div>Looks like I am not part of gluster-infra ML. Hence missed some of these conversations. Joining now. </div></div></div>
</div><br clear="all"><div>-Amar</div></div></div></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">--<div><a href="https://kadalu.io" target="_blank">https://kadalu.io</a></div><div>Container Storage made easy!</div><div><br></div></div></div></div>