If we'd like an alternative to the dev@avro mailing list, there is a growing amount of infra support for using slack. in particular there is a bot for making sure you can send stuff to a mailing list for those who want a record.
Andy, what kind of response would you see as proper? Is your concern time to merge, time to being in a release? Guidance on what it takes for a PR to get accepted? Something else? On Tue, May 5, 2020 at 8:03 AM Zoltan Farkas <zolyfar...@yahoo.com.invalid> wrote: > Should we start using a chat product (like Gitter or similar?) > For example, this discussion was classified as Junk by the email tooling I > use… > > cheers > > —Z > > > On May 5, 2020, at 5:03 AM, Driesprong, Fokko <fo...@driesprong.frl> > wrote: > > > > For the releases, the information is on Github: > > https://github.com/apache/avro/releases. For the fine details, Jira is > the > > way to go. You can select which tickets are merged in which version. This > > is also how we generate the changelog, we condense it and put it on > Github. > > Maybe we should add a link from the docs website to Github. > > > > There is some traction around .Net, Ruby, Python, and especially Java. > > However, implementation such as Perl, C(++) is not happening a lot. Also, > > the original contributors aren't that active anymore. I like the idea of > > splitting the different languages to different repositories. For Parquet, > > the each repository contains also one language. This is also what Ryan > > suggested in the other thread. For more fundamental changes, there is > this > > concept of Avro Enhancement Proposals: > > > https://cwiki.apache.org/confluence/display/AVRO/Avro+Enhancement+Proposals > > This > > is a confluence section where you can create a proposal, to get consensus > > in the community, and then implement it. > > > > Hope this helps! > > > > Cheers, Fokko > > > > > > > > Op di 5 mei 2020 om 10:56 schreef Andy Le <anhl...@gmail.com>: > > > >> I've checked Avro release notes [1] and found them containing vague > >> information about each release. There's also a lack of documentation for > >> other programming languages. > >> > >> My question: should we carefully lay out what to do, opening dedicated > >> issues to call for contributions? > >> > >> Thanks & best regards. > >> > >> [1] > >> > https://avro.apache.org/releases.html#12+February+2020%3A+Avro+1.9.2+Released > >> > >> On 2020/05/03 07:07:46, Andy Le <anhl...@gmail.com> wrote: > >>> Hi guys, > >>> > >>> I'm starting this thread to discuss about my issue about our community: > >>> > >>>> Recently I've seen so many Jira issues and Github PRs having no proper > >> responses from committers. > >>> > >>> I think responsive answers from members will create a better Avro > >> community. > >>> > >>> How can we resolve the issue? Glad that I can help any thing. > >>> > >>> Thanks. > >>> > >>> > >>> > >>> > >>> > >> > >
