[ClusterLabs] Authoritative corosync's location

[Jan Pokorný]

On 22/09/16 09:05 +0200, Jan Friesse wrote:
> Jan Pokorný napsal(a):
>> On 21/09/16 09:16 +0200, Jan Friesse wrote:
>>> Thomas Lamprecht napsal(a):
>>>> I have also another, organizational question. I saw on the GitHub page from
>>>> corosync that pull request there are preferred, and also that the
>>> 
>>> True
>> 
>> At this point, it's worth noting that ClusterLabs/corosync is
>> currently a stale fork of corosync/corosync location at GitHub,
>> which may be a source of confusion.
> 
> Nice catch, I didn't even know it exists.
> 
>> 
>> It would make sense to settle on just a single one to be clearly
>> authoritative place to be in touch with (not sure what options
>> are -- aliasing/transfering?).
> 
> Sure. I don't know who created that fork but whoever it was please consider
> deleting it. It may be really confusing.

Even more so when it's occasionally updated;
https://github.com/ClusterLabs/corosync (at master branch) now says
"This branch is 3 commits behind corosync:master.".

That also means that there seems no satisfactory solution, yet.

-- 
Jan (Poki)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://clusterlabs.org/pipermail/users/attachments/20161107/9472914d/attachment.sig>