[Bioperl-l] Important! Redmine issue migration

Fields, Christopher J cjfields at illinois.edu
Wed Oct 7 19:57:48 UTC 2015

Just an update: I’m working on the final migration now.  I’ve enabled user name mapping to github IDs for the original bug reports (but not the comments, which should cut down on noise).  Once this is finished I’ll reassign the redmine issues repo over to the bioperl organization. I’ll also check the bioperl-run and other bioperl-* repos on redmine to see how many tickets are left.


On Sep 28, 2015, at 9:25 PM, Fields, Christopher J <cjfields at illinois.edu<mailto:cjfields at illinois.edu>> wrote:

The move will have to be iterative; I seem to have hit a submission limit which forbids sending more than a few hundred queries/updates.  Not sure why, as it’s done via OAuth key.  Not a big problem, just will be in 2-3 batches.

I may do a quick test run to see whether the submitter alone is mapped to the Github ID or if it’s also commenter IDs.  If someone is being pinged for every mention of their name in comments it might get loud :)


On Sep 25, 2015, at 7:03 AM, Hilmar Lapp <hlapp at drycafe.net<mailto:hlapp at drycafe.net>> wrote:

That's fantastic Chris! Long awaited that someone take this on. I agree that tagging the original submitters suffices. Though perhaps that's what you're arguing _not_ to do?

I do think it's a reasonable assumption that someone who submits an issue by default wants to stay in the loop about its resolution. Tagging the submitter's GitHub account would accomplish that.


Sent from away

On Sep 24, 2015, at 11:39 PM, Fields, Christopher J <cjfields at illinois.edu<mailto:cjfields at illinois.edu>> wrote:

I (finally!) have a set of tools working to migrate Bioperl issues from the old bug report system (https://redmine.open-bio.org<https://urldefense.proofpoint.com/v2/url?u=https-3A__redmine.open-2Dbio.org&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=fbHa8Njtvh9VmSnzJxiEUTW9NWDwMMwQAzhgZDO41GQ&m=20fYC3_35S5yKLXyC6tlEbaD7sxvyFW4wGjAVL1CoZE&s=ZRd_d1DWn-pzAPvtf_18nwYIiEX96UiROAhsksNIZWQ&e=>) to Github Issues.  You can see a test run of this here:


Note this points back to the original Redmine repo.  We’ll keep that operational since it has attachments present for some tickets, but for any future work the link will become read-only (and may go away in the future as we phase out the Redmine repo).

As for the migrated issues, we’ll likely keep this as a separate (empty) repository for the time being (I will change the ownership to 'bioperl' once it looks fine).  This is primarily to ensure we don’t clutter or munge up the main bioperl-live repo Issues already in place, since we can’t delete Github issues once they are created.  I will be adding a placeholder ticket pointing to them within the bioperl-live ticket system for the time being.

The important part: once the test run is finished, we could implement the user map; however, old bioperl users/contributors may see a flood of Github emails if you submitted or replied to any ticket in the past.  We do not have to implement this functionality, in fact I’m reluctant to spam past contributors unless we see an overwhelming need to do so (particularly since we can simply add their Github user ID to a comment if needed).  So my official position is that we won’t map Github users to tickets, except manually via comments and only when necessary.  Welcome to any dissenting opinions.



Bioperl-l mailing list
Bioperl-l at mailman.open-bio.org<mailto:Bioperl-l at mailman.open-bio.org>

Bioperl-l mailing list
Bioperl-l at mailman.open-bio.org<mailto:Bioperl-l at mailman.open-bio.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.open-bio.org/pipermail/bioperl-l/attachments/20151007/88a270ee/attachment.html>

More information about the Bioperl-l mailing list