On 2/20/2017 7:33 PM, Digimer wrote:

On 20/02/17 01:26 PM, Michael Jones wrote:

...

On Github.com, searching for "kronosnet" turns up two repositories:

https://github.com/kronosnet/kronosnet

and

https://github.com/fabbione/kronosnet

Which is the correct repository? Why have two? Can one be decommissioned?

Keep using /fabbione/ for now.

Would it be worth standardizing under Clusterlabs?

No, knet is not just about clusters. It has other use cases too.

Michele and I started to transition it under /kronosnet/ umbrella, but we never got to complete it for one reason or another and somehow it got lost in the noise of important bug fixes.

Once we move to /kronosnet/ we will remove /fabbione/ and announce it.

Fabio

On 2/21/2017 6:01 PM, Michael Jones wrote:

On Tue, Feb 21, 2017 at 1:40 AM, Fabio M. Di Nitto <fabbione@fabbione.net mailto:fabbione@fabbione.net> wrote:

On 2/20/2017 7:33 PM, Digimer wrote:
> On 20/02/17 01:26 PM, Michael Jones wrote:
>> On Github.com, searching for "kronosnet" turns up two repositories:
>>
>> https://github.com/kronosnet/kronosnet
<https://github.com/kronosnet/kronosnet>
>>
>> and
>>
>> https://github.com/fabbione/kronosnet
<https://github.com/fabbione/kronosnet>
>>
>> Which is the correct repository? Why have two? Can one be decommissioned?

Keep using /fabbione/ for now.

>
> Would it be worth standardizing under Clusterlabs?
>

No, knet is not just about clusters. It has other use cases too.

Michele and I started to transition it under /kronosnet/ umbrella, but
we never got to complete it for one reason or another and somehow it got
lost in the noise of important bug fixes.

Once we move to /kronosnet/ we will remove /fabbione/ and announce it.

Fabio

Thank you for the guidance

The repos has moved to /kronosnet/ now, but there is no need to update anything in your git config or checkouts. github does automatically redirect you to the right place.

Cheers Fabio