A new home for basho/cuttlefish
deadzen at deadzen.com
Thu Sep 28 10:15:35 EDT 2017
Less forks the better, agree
On Thu, Sep 28, 2017 at 9:45 AM, Heinz N. Gies <heinz at licenser.net> wrote:
> I fully agree. We started the Kyorai org log before it was public knowledge that bet365 (or anyone) would buy the IP of basho and done under the assumption that the basho repository would either be deleted or end up rotting there. The goal was/is to prevent fragmentation and give the community still using the repos a home where they can come together.
> That said I think it’ll take some time getting everything back together. The repos there are currently the mirrors of what is on hex, and due to how hard it was to get changes merged to the basho repositories have all diverged to some degree or another. So there is work to be done to get it all back in sync. I can’t speak for the other people who maintain repos on Kyorai (so I suspect they feel the same) but I’d be eager to get it all back together and kill of forks.
>> On 28. Sep 2017, at 09:50, Martin.Cox at bet365.com wrote:
>> Whilst bet365 did buy the Basho IP, they have emphasised that the entire catalogue of repositories is to be handed over to the community and that they are not intending to be an overarching authority on decision making, but will steer the project just as much as any other involved parties would. So, from my perspective, it is not a decision for bet365 to take, but for the community as a whole.
>> Personally, I don't see a lot of merit in moving the repo away from its current home at this point in time. Once the legal processes have concluded and people have the facility to manage the repository configurations, anyone interested in contributing and maintaining can be added - enabling the RabbitMQ team to work on Cuttlefish without the upheaval of moving repositories around. When the dust has settled, then revisit the question of spinning the project out into its own org.
>> What's everyone else's thoughts on this?
>> Martin Cox
>> Software Developer
>> Hillside (Technology) Limited
>> m: +44(0) 7585 990614
>> t: +44(0) 8456 000 365
>> e: martin.cox at bet365.com
>> From: riak-users [riak-users-bounces at lists.basho.com] on behalf of Heinz N. Gies [heinz at licenser.net]
>> Sent: 27 September 2017 20:45
>> To: Luke Bakken
>> Cc: riak-users at lists.basho.com
>> Subject: Re: A new home for basho/cuttlefish
>> Hi Luke,
>> The Kyorai org is a collection of (ex)basho projects that have been forked and maintained outside of basho for a while now. While it was a bit of a scattered effort in the beginning the demise of basho ended up causing us to collect them in a central place.
>> How things go forward really depends a bit on how things go forward with riak and the basho PI, and the community around it.
>>> On 27. Sep 2017, at 20:44, Luke Bakken <luke at bakken.io> wrote:
>>> Hi again everyone -
>>> Apologies for not setting a subject in my first email.
>>> Of course this is Bet365's decision. The purpose of this message
>>> thread is to let people know that the RabbitMQ team is willing to
>>> maintain cuttlefish. I also found the following more-up-to-date fork
>>> and will be looking at the changes there -
>>> Thanks again!
>>> On Wed, Sep 27, 2017 at 11:27 AM, Bryan Hunt
>>> <bryan.hunt at erlang-solutions.com> wrote:
>>>> Hi Luke,
>>>> It’s for bet365 to make that decision.
>>>> For the good of the general population the following would be nice:
>>>> a) Upgrade to rebar3
>>>> b) Upgrade Erlang version support so it compiles under Erlang 20 (if it doesn’t already)
>>>> c) Package uploaded to hex.pm
>>>>> On 27 Sep 2017, at 18:59, Luke Bakken <luke at bakken.io> wrote:
>>>>> Hello Riak users -
>>>>> The next RabbitMQ release (3.7.0) will use cuttlefish for its
>>>>> configuration. I'm writing to express interest on behalf of the
>>>>> RabbitMQ team in taking over maintenance of the project. At the
>>>>> moment, we forked cuttlefish to the RabbitMQ organization  to fix a
>>>>> couple pressing issues. After that, it would be great if the
>>>>> repository could be transferred to either its own, new organization or
>>>>> to the RabbitMQ organization entirely. Basho transferred both
>>>>> Webmachine and Lager to their own independent organizations, for
>>>>> instance (github.com/webmachine, github.com/erlang-lager)
>>>>> Once transferred, GitHub will take care of all the necessary
>>>>> redirections from the Basho organization to cuttlefish's new home.
>>>>> Luke Bakken
>>>>>  - https://github.com/rabbitmq/cuttlefish
>>> riak-users mailing list
>>> riak-users at lists.basho.com
>> This email and any files transmitted with it are confidential and contain information which may be privileged or confidential and are intended solely to be for the use of the individual(s) or entity to which they are addressed. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information is strictly prohibited and may be illegal. If you have received this email in error, please notify us by telephone or email immediately and delete it from your system. Activity and use of our email system is monitored to secure its effective operation and for other lawful business purposes. Communications using this system will also be monitored and may be recorded to secure effective operation and for other lawful business purposes. Internet emails are not necessarily secure. We do not accept responsibility for changes made to this message after it was sent. You are advised to scan this message for viruses and we cannot accept liability for any loss or damage which may be caused as a result of any computer virus.
>> This email is sent by a bet365 group entity. The bet365 group includes the following entities: Hillside (Shared Services) Limited (registration no. 3958393), Hillside (Spain New Media) Plc (registration no. 07833226), bet365 Group Limited (registration no. 4241161), Hillside (Technology) Limited (registration no. 8273456), Hillside (Media Services) Limited (registration no. 9171710), Hillside (Trader Services) Limited (registration no. 9171598) each registered in England and Wales with a registered office address at bet365 House, Media Way, Stoke-on-Trent, ST1 5SZ, United Kingdom; Hillside (Gibraltar) Limited (registration no. 97927), Hillside (Sports) GP Limited (registration no. 111829) and Hillside (Gaming) GP Limited (registered no. 111830) each registered in Gibraltar with a registered office address at Unit 1.1, First Floor, Waterport Place, 2 Europort Avenue, Gibraltar; Hillside (UK Sports) LP (registration no. 117), Hillside (Sports) LP (registration no. 118), Hillside (International Sports) LP (registration no. 119), Hillside (Gaming) LP (registration no. 120) and Hillside (International Gaming) LP (registration no. 121) each registered in Gibraltar with a principal place of business at Unit 1.1, First Floor, Waterport Place, 2 Europort Avenue, Gibraltar; Hillside España Leisure S.A (CIF no. A86340270) registered in Spain with a registered office address at C/ Conde de Aranda nº20, 2º, 28001 Madrid, Spain; Hillside (Australia New Media) Pty Limited (registration no. 148 920 665) registered in Australia with a registered office address at Level 4, 90 Arthur Street, North Sydney, NSW 2060, Australia; Hillside (New Media Malta) Plc, (registration no c.66039) registered in Malta with a registered office address at Office 1/2373, Level G, Quantum House, 75 Abate Rigord Street, Ta’ Xbiex XBX 1120, Malta and Hillside (New Media Cyprus) Limited, (registration no. HE 361612) registered in Cyprus with a registered office address at Omrania Centre, 313, 28th October Avenue, 3105 Limassol, Cyprus. Hillside (Shared Services) Limited, Hillside (Spain New Media) Plc and Hillside (New Media Malta) Plc also have places of business at Unit 1.1, First Floor, Waterport Place, 2 Europort Avenue, Gibraltar. For residents of Greece, this email is sent on behalf of B2B Gaming Services (Malta) Limited (registration number C41936) organised under the laws of Malta with a registered office at Apartment 21, Suite 41, Charles Court, St. Luke's Road, Pietà, Malta.
> riak-users mailing list
> riak-users at lists.basho.com
More information about the riak-users