Hi,
Mario is right. Let me expand this a bit.
What I wrote a while ago [1] is still true: We are more than happy when
people are using Thrift actively, because that tells us we are doing
something right.
But what any project keeps it moving is the people who are willing to invest
a piece of their time to *maintain* the code. Especially with Thrift, hardly
anyone is an expert in all of the currently 20+ languages or language
dialects we are targeting. So if you feel you could do that for Erlang, that
would be totally awesome.
Of course, at the ASF everything is absolutely voluntary work. Even the
amount of time everyone spends or how deep one gets immersed into Thrift or
other ASF projects. Nobody forces you into anything.
What do you think? If you agree, just start with sending PRs. The rest will
come.
Have fun,
JensG
[1] https://www.mail-archive.com/dev@thrift.apache.org/msg48543.html
-----Ursprüngliche Nachricht-----
From: Mario Emmenlauer
Sent: Friday, December 4, 2020 8:21 PM
To: dev@thrift.apache.org ; Sergey Yelin ; Jens Geyer
Subject: Re: Erlang - dead or alive?
On 04.12.20 19:33, Sergey Yelin wrote:
I’ve fixed Erlang tests https://github.com/apache/thrift/pull/2290
<https://github.com/apache/thrift/pull/2290>
Great Sergey! Its highly appreciated.
You also mention you have more local changes. Do you want to try and
get them merged into master? I guess currently not many people can review
the changes thoroughly (at least I certainly can't). But especially if
they are bug fixes, or enhancements that you have thorough experience
with, it may be worth a shot?
All the best,
Mario
On 4 Dec 2020, at 11:26, Sergey Yelin <eli...@gmail.com> wrote:
Hello,
We are using Erlang Thrift but from our fork (we need some features which
are not in main stream yet).
So were I can look into CI results?
On 4 Dec 2020, at 11:14, Jens Geyer <je...@apache.org> wrote:
Morning,
are there any Erlang people interested in using and more importantly
maintaining the Thrift Erlang bindings?
Otherwise, if no interest is in it anymore, we may as well propose to
deprecate it. The CI fails on Erlang for months now, which is – sorry –
not acceptable.
Thank you,
JensG
