<div dir="ltr">Markus,<div><br></div><div>I agree we should have a category or tag for issues transferred to GitHub. For now, I have closed issues that have been resolved in GitHub and changed the Redmine Issue's URL to the relevant GitHub commit/pull request/issue. For issues that are still open I plan to just migrate the discussion (if any) and open a new issue on GitHub (see <a href="https://github.com/biopython/biopython/issues/879">this issue I just made</a>).</div><div><br></div><div>-Travis</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 20, 2016 at 12:16 PM, Markus Piotrowski <span dir="ltr"><<a href="mailto:Markus.Piotrowski@ruhr-uni-bochum.de" target="_blank">Markus.Piotrowski@ruhr-uni-bochum.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
I would also volunteer but I'm unsure what exactly is the job?<br>
Should there be a special tag to put to the title of a transferred
issue?<br>
How to delete the issues on RedMine or mark them as transferred?<br>
Copy the whole RedMine issue including its discussion into the
GitHub issue?<span class="HOEnZb"><font color="#888888"><br>
<br>
-Markus <br></font></span><div><div class="h5">
<br>
<div>Am 20.07.2016 um 20:19 schrieb Travis
Wrightsman:<br>
</div>
<blockquote type="cite">
<div dir="ltr"><span style="font-size:12.8px">I should be able to
donate some time to this. Will the volunteers be reading
through each issue to see if it was solved and creating new
issues on the GitHub repository if it's still an open issue?</span>
<div style="font-size:12.8px"><br>
</div>
<div style="font-size:12.8px">-Travis</div>
<div style="font-size:12.8px"><br>
</div>
<div style="font-size:12.8px">(First one didn't reply to all)</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Jul 20, 2016 at 3:59 AM,
Peter Cock <span dir="ltr"><<a href="mailto:p.j.a.cock@googlemail.com" target="_blank">p.j.a.cock@googlemail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello
Biopythoneers,<br>
<br>
After we moved our code repository to GitHub, we started
using<br>
their issue track which integrates with pull requests etc:<br>
<br>
<a href="https://github.com/biopython/biopython/issues" rel="noreferrer" target="_blank">https://github.com/biopython/biopython/issues</a><br>
<br>
Prior to that we were using an OBF hosted RedMine instance<br>
(itself migrated from an even older Bugzilla server):<br>
<br>
<a href="https://redmine.open-bio.org/projects/biopython" rel="noreferrer" target="_blank">https://redmine.open-bio.org/projects/biopython</a><br>
<br>
Once you click though any annoying certificate warning,
you'll<br>
see there are still about 90 open issues and 20 feature
requests.<br>
<br>
The OBF would like to shut down the RedMine server since
no<br>
one is actively using it any more, and it is costing us
money<br>
in AWS fees.<br>
<br>
Several years ago we talked about manually triaging these,
i.e.<br>
refiling and cross referencing any relevant issues on
GitHub,<br>
and closing irrelevant issues:<br>
<br>
<a href="http://lists.open-bio.org/pipermail/biopython-dev/2013-August/019939.html" rel="noreferrer" target="_blank">http://lists.open-bio.org/pipermail/biopython-dev/2013-August/019939.html</a><br>
<br>
Do we have any volunteers to help with this?<br>
<br>
In the absence of any volunteers to review the old RedMine<br>
issues, Plan B is to follow BioPerl's lead and do an
automated<br>
migration to a dedicated GitHub repository just for the
old<br>
issues:<br>
<br>
<a href="https://github.com/bioperl/bioperl-live-redmine" rel="noreferrer" target="_blank">https://github.com/bioperl/bioperl-live-redmine</a><br>
<br>
Who can help out?<br>
<br>
Thank you,<br>
<br>
Peter<br>
<br>
(Speaking here primarily as a Biopython developer, but I
am<br>
also secretary for the Open Bioinformatics Foundation
board)<br>
_______________________________________________<br>
Biopython-dev mailing list<br>
<a href="mailto:Biopython-dev@mailman.open-bio.org" target="_blank">Biopython-dev@mailman.open-bio.org</a><br>
<a href="http://mailman.open-bio.org/mailman/listinfo/biopython-dev" rel="noreferrer" target="_blank">http://mailman.open-bio.org/mailman/listinfo/biopython-dev</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div data-smartmail="gmail_signature">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">Travis Wrightsman
<div>University of California, Riverside</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Biopython-dev mailing list
<a href="mailto:Biopython-dev@mailman.open-bio.org" target="_blank">Biopython-dev@mailman.open-bio.org</a>
<a href="http://mailman.open-bio.org/mailman/listinfo/biopython-dev" target="_blank">http://mailman.open-bio.org/mailman/listinfo/biopython-dev</a></pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
Biopython-dev mailing list<br>
<a href="mailto:Biopython-dev@mailman.open-bio.org">Biopython-dev@mailman.open-bio.org</a><br>
<a href="http://mailman.open-bio.org/mailman/listinfo/biopython-dev" rel="noreferrer" target="_blank">http://mailman.open-bio.org/mailman/listinfo/biopython-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">Travis Wrightsman<div>University of California, Riverside</div></div></div></div></div></div></div>
</div></div>