A new home for basho/cuttlefish

Christopher Meiklejohn christopher.meiklejohn at gmail.com
Thu Sep 28 10:42:24 EDT 2017


These repositories also have a notable distinction that many are Erlang 19+
only now, and do not maintain perfect backwards compatibility with earlier
versions of Erlang.

[...and, used by Antidote, Lasp, and some others.]

Christopher

On Wed, Sep 27, 2017 at 9:46 PM Heinz N. Gies <heinz at licenser.net> wrote:

> 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.
>
> Cheers,
> Heinz
>
> > 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 -
> >
> > https://github.com/Kyorai/cuttlefish
> >
> > Thanks again!
> > Luke
> >
> > 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
> >>
> >> Bryan
> >>
> >>
> >>> 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 [0] 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.
> >>>
> >>> Thanks,
> >>> Luke Bakken
> >>>
> >>> [0] - https://github.com/rabbitmq/cuttlefish
> >
> > _______________________________________________
> > riak-users mailing list
> > riak-users at lists.basho.com
> > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>
> _______________________________________________
> riak-users mailing list
> riak-users at lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.basho.com/pipermail/riak-users_lists.basho.com/attachments/20170928/2d2b3cf4/attachment-0002.html>


More information about the riak-users mailing list