<div dir="ltr"><div dir="ltr"> <a href="https://rpg.hamsterrepublic.com/bugzilla/">https://rpg.hamsterrepublic.com/bugzilla/</a> already exists (it's a redirect to the sf buglist, plus hosts <a href="https://rpg.hamsterrepublic.com/bugzilla/buglist.txt">https://rpg.hamsterrepublic.com/bugzilla/buglist.txt</a>). So I guess the logical URL to use is <a href="https://rpg.hamsterrepublic.com/bugzilla/old-attachments/">https://rpg.hamsterrepublic.com/bugzilla/old-attachments/</a></div><div dir="ltr"><a href="https://rpg.hamsterrepublic.com/old-bugzilla-attachments/" target="_blank"><br></a></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 7 Feb 2020 at 14:40, James Paige <<a href="mailto:Bob@hamsterrepublic.com">Bob@hamsterrepublic.com</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="auto"><div>Oops! Yes!<div dir="auto"><br></div><div dir="auto">How about putting them at <a href="https://rpg.hamsterrepublic.com/old-bugzilla-attachments/" target="_blank">https://rpg.hamsterrepublic.com/old-bugzilla-attachments/</a> ?</div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Feb 6, 2020, 5:53 PM Ralph Versteegen <<a href="mailto:teeemcee@gmail.com" target="_blank">teeemcee@gmail.com</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">Oh, right! The main reason I wrote that email was to ask about uploading the bug attachments somewhere. I see there are still various redirects and remnants of bugzilla left behind.<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 7 Feb 2020 at 02:47, Ralph Versteegen <<a href="mailto:teeemcee@gmail.com" rel="noreferrer" target="_blank">teeemcee@gmail.com</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></div><div>I agree that too many labels aren't helpful. Labels are most useful when you can't just do a text search (all crash bugs will be easily found with a search for "crash"), eg for bug priorities.<br></div><div>I think maybe I'll combine "cosmetic" and "minor" into a single "minor" tag, since we likely want that one anyway while "cosmetic" is too specific. Wait, how much difference is there between "minor" and "needs improvement"? Plenty of outright bugs are merely cosmetic. Argh!</div><div>Really, "bug" is a region of the continuum (nearly the whole continuum) from feature request to "needs improvement" to blocker.</div><div><br></div><div>But... major/high priority bugs is possible the most likely thing of all that we would want to categorise and search for. And they aren't necessarily going to be put on the todo list for the next release (milestone). So I guess I should map major/critical/blocker to "major". Although the categorisation of bug severities on bugzilla is pretty dubious, it is a useful starting point.<br></div><div><br></div><div><span style="font-family:sans-serif">7d344553-34f0-</span><span style="font-family:sans-serif">0310-a9b1-970ce8f1c3a2 is the "Repository UUID" you see when running "svn info".</span></div><div><span style="font-family:sans-serif">It's also possible to give git-svn a file with mapping from username to actual email, but that won't apply retroactively.<br></span></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 7 Feb 2020 at 02:08, James Paige <<a href="mailto:Bob@hamsterrepublic.com" rel="noreferrer" target="_blank">Bob@hamsterrepublic.com</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="auto"><div>Cool!</div><div dir="auto"><br></div><div dir="auto">I like the idea of rel: and resolved: prefixes.</div><div dir="auto"><br></div><div dir="auto">I vote for eliminating the "bug" tag completely. In general I say err on the side of fewer tags when the specific need for a tag is not obvious.</div><div dir="auto"><br></div><div dir="auto">That GitHub contributions trick is cool. I'll try it. Is <span style="font-family:sans-serif">7d344553-34f0-</span><span style="font-family:sans-serif">0310-a9b1-970ce8f1c3a2 the internal ID of our svn repo?</span><br><br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Thu, Feb 6, 2020, 8:04 AM Ralph Versteegen <<a href="mailto:teeemcee@gmail.com" rel="noreferrer" target="_blank">teeemcee@gmail.com</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 dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 7 Feb 2020 at 01:43, Ralph Versteegen <<a href="mailto:teeemcee@gmail.com" rel="noreferrer noreferrer" target="_blank">teeemcee@gmail.com</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>I've been putting this off for years (two years since my last attempt in fact) but I've finally managed to get bugzilla running locally and import the databases so that I can export the buglist as xml and use <a href="https://gist.github.com/Zimmi48/d923e52f64fe17c72852d9c148bfcdc6#file-bugzilla2github" rel="noreferrer noreferrer" target="_blank">this script</a> to import it into github.</div><div><br></div><div>I'm now in the process of customising the script and the mapping to labels.</div><div><div><br></div><div>Github doesn't have an API that allows attaching files to issue comments, so I suggest that we upload all the attachments to a directory on <a href="http://hamsterrepublic.com" rel="noreferrer noreferrer" target="_blank">hamsterrepublic.com</a> so that we can link to them.</div><div>(Unfortunately I first have to write a script to extract them out of the bugzilla DB.)</div></div><div><br></div><div>With all the labels for components, versions, severity, status, etc, we'll have a lot of labels. I think it makes sense to organise our labels a bit better. All version labels could be prefixed with "rel: ", like "rel: alectormancy". And maybe duplicate, wontfix, invalid, worksforme, tooconfusing<br></div><div>could be prefixed with "resolved:" or "closed:"?<br></div><div><br></div><div>I'm going to translate the "feature request", "cosmetic", "blocker" severities into labels. I think I'll leave behind "major", "minor", "normal" and "critical", and the priority levels. They (if not default value) will still be in the bug description.</div><div><br></div><div>There isn't really anything that corresponds closely to our gh "bug" and "needs improvement" labels. I wonder whether we should just remove the "bug" label, since although it's informative and useful in searches, it's already a nuisance to accurately tag all the bugs** and we'll get an extra 1000 bugs missing it. "bug" is basically the absense of numerous special categories like "new feature", "invalid" and "tracking".<br></div></div></blockquote><div>Or, I could just apply "bug" as a guess according to something like that simple rule, and we can fix up any mistakes. Will be looking through all the open imported bugs anyway.<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"><div dir="ltr"><div></div><div><br></div><div>**See <a href="https://github.com/ohrrpgce/ohrrpgce/issues?utf8=%E2%9C%93&q=-label%3Abug+-label%3A%22needs+improvement%22++-label%3A%22new+feature%22" rel="noreferrer noreferrer" target="_blank">https://github.com/ohrrpgce/ohrrpgce/issues?utf8=%E2%9C%93&q=-label%3Abug+-label%3A%22needs+improvement%22++-label%3A%22new+feature%22</a></div><div></div><div><br></div><div>Bugzilla hides people's email addresses (by stripping the domain) by default so user names will be something like "David Gowers <00ai99>". I think that's fine. I can (am planning to) also replace the username with a github @ mention (it shouldn't cause any notifications, because this is the mass import API), but the only people who I know the github username of are myself, James and Mike. Doesn't matter.</div><br><div><br></div><div>BTW, I found that it's possible to make svn commits copied to the git-svn mirror on github count towards your "contributions" shown on your github profile page. To do so, add a new email address to your github account with the form svncommitername@7d344553-34f0-0310-a9b1-970ce8f1c3a2, where svncommitername is e.g. teeemcee or james. The email can be private.<br></div></div>
</blockquote></div></div>
_______________________________________________<br>
Ohrrpgce mailing list<br>
<a href="mailto:ohrrpgce@lists.motherhamster.org" rel="noreferrer noreferrer" target="_blank">ohrrpgce@lists.motherhamster.org</a><br>
<a href="http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org" rel="noreferrer noreferrer noreferrer" target="_blank">http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org</a><br>
</blockquote></div></div></div>
_______________________________________________<br>
Ohrrpgce mailing list<br>
<a href="mailto:ohrrpgce@lists.motherhamster.org" rel="noreferrer" target="_blank">ohrrpgce@lists.motherhamster.org</a><br>
<a href="http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org" rel="noreferrer noreferrer" target="_blank">http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org</a><br>
</blockquote></div></div>
</blockquote></div>
_______________________________________________<br>
Ohrrpgce mailing list<br>
<a href="mailto:ohrrpgce@lists.motherhamster.org" rel="noreferrer" target="_blank">ohrrpgce@lists.motherhamster.org</a><br>
<a href="http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org" rel="noreferrer noreferrer" target="_blank">http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org</a><br>
</blockquote></div></div></div>
_______________________________________________<br>
Ohrrpgce mailing list<br>
<a href="mailto:ohrrpgce@lists.motherhamster.org" target="_blank">ohrrpgce@lists.motherhamster.org</a><br>
<a href="http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org" rel="noreferrer" target="_blank">http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org</a><br>
</blockquote></div></div>