[Open-scap] Migrate Trac to Github Issues

[Šimon Lukašík]

On 09/08/2015 01:40 PM, Martin Preisler wrote:
> ----- Original Message -----
>> From: "Šimon Lukašík" <slukasik at redhat.com>
>> To: "Martin Preisler" <mpreisle at redhat.com>, "open-scap-list" <open-scap-list at redhat.com>
>> Sent: Tuesday, September 8, 2015 1:26:45 PM
>> Subject: Re: [Open-scap] Migrate Trac to Github Issues
>>
>> On 09/08/2015 01:02 PM, Martin Preisler wrote:
>>> Hi,
>>>
>>> we have migrated most of our development infrastructure to Github.
>>> Issue tracking is one of the few things remaining. We have discussed
>>> it in the past and even researched it but we have hit roadblocks
>>> when trying to migrate all the tickets - reporter and commenter
>>> info can be lost, github rate limits API access, ...
>>>
>>> I propose a pragmatic solution. Let's disable creating new tickets
>>> on Trac from now on and only create them on github. We can still
>>> discuss old issues on Trac and all of them will remain public.
>>> This way we can move OpenSCAP to Github Issues over time.
>>>
>>> Thoughts? I am volunteering to make this happen if we have
>>> a consensus.
>>>
>>
>> How would the tracking progress work in this set-up?
>>
>> ~š.
>
> We would have 2 milestones in the interim for a single goal, which
> arguably sucks. I envision that in a few months we would only track
> progress on github via milestones.
>

I cannot take the extra load of maintaining two milestones.

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

~š.