Hi Ismaël, > Avro at this point is a mature and real open source project and the agenda and > priorities is driven mostly by volunteers and it is up to us for the health of > the community to be more responsive with new contributions as you point out, > and > also we should produce more comprehensive and nicer material (don't even let > me > get started talking about the poor user experience of our website or the lack > of > documentation of the Avro APIs in less popular languages).
Correct. I think we should design a resilience organization for Avro. organization = structures + processes IMHO, we can have: - structures: grant freedom & responsibilities for individual Avro Components to a quorum of reviewers/committers. - processes: I think we should have an OKR plan for Avro and cry for helps. Such plan is crucial to co-ordinate/concentrate the power of communities > Anyone interested can get an invite to the ASF slack here > http://s.apache.org/slack-invite Gonna try :D Thank you. On 2020/05/05 21:11:54, Ismaël Mejía <ieme...@gmail.com> wrote: > Thanks Andy for pointing this out. It is important that we are more responsive > to contributors. I have my good dose of mea culpa on this recently but please > do > not forget that even if Avro is a crucial piece of the Big Data ecosystem, at > this point there is not a single person up to my knowledge who is paid to > maintain Avro full time and few companies encourage employees to work on it, > and also many people have less time available because of covid. > > Avro at this point is a mature and real open source project and the agenda and > priorities is driven mostly by volunteers and it is up to us for the health of > the community to be more responsive with new contributions as you point out, > and > also we should produce more comprehensive and nicer material (don't even let > me > get started talking about the poor user experience of our website or the lack > of > documentation of the Avro APIs in less popular languages). > > In any case contributions are welcome! > > I have seen in other projects dashboards of time to merge and other stats, > those > could prove practical but I am not sure if we would even have someone with the > extra time/will to work on those and in my opinion I would prefer that we > tackle > more important end user issues like improving Avro's website among others. > > Maybe 'chat-like' conversation is a way to make the contribution process > quicker. I would suggest maybe that we use The Apache Software Foundation > Slack > Avro slack channel for this purpose. But let's not forget that the source of > truth in every Apache project is always the mailing list so important subjects > should be treated here and consensus should be reached also via the ML. > > Anyone interested can get an invite to the ASF slack here > http://s.apache.org/slack-invite > > And then join the #avro channel there, we are not many but we are willing to > help and discuss all things Avro. I have not thought about promoting this in > our website but if others agree I can add a mention to it. > > On Tue, May 5, 2020 at 10:09 PM Sean Busbey <bus...@apache.org> wrote: > > > > 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. > > > >>> > > > >>> > > > >>> > > > >>> > > > >>> > > > >> > > > > > > >
