[Open-scap] Migrate Trac to Github Issues

[Martin Preisler]

----- Original Message -----
> From: "Šimon Lukašík" <slukasik at redhat.com>
> To: "Martin Preisler" <mpreisle at redhat.com>
> Cc: "open-scap-list" <open-scap-list at redhat.com>
> Sent: Tuesday, September 8, 2015 1:41:57 PM
> Subject: Re: [Open-scap] Migrate Trac to Github Issues
> 
> [snip]
> 
> I cannot take the extra load of maintaining two milestones.

Ok, acknowledged.

> What are the roadblocks to migrate all the trac to github now?

0) lack of engineering time
   The transition has to be done right because the issues cannot be
   removed once they are added. It is not as simple an effort as I
   would expect.

1) github doesn't allow us to create tickets in other people's names
   This has several partial solutions we discussed before.

2) github API is rate limited and can fail at any point
   The dirty script I used to migrate SCAP Workbench tickets expects
   everything to be reliable. This can be solved but requires effort.

3) github issues have slightly different structure from trac tickets.
   Some info inevitably gets lost.

The reason behind this email is not to argue against migrating all
the tickets, that can surely be done. My point is that it's not
happening even though we talked about this many months ago.
The proposed solution is a significantly lower time investment.

OpenSCAP is the last project that doesn't have issue tracking on
GitHub. I think tracking issues on fedorahosted behind FAS hinders
community engagement.

-- 
Martin Preisler
Security Technologies | Red Hat, Inc.
http://martin.preisler.me