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
Hi Sean,
> 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?
Yep, I concern about:
- Timely responses (replies on Jira issues, reviews on Github). I opened
Hi Fokko,
> Maybe we should add a link from the docs website to Github...
+1 for this.
So there's an incompatibility with our homepage and Github about release
information. May we customize the release page to only contain latest version
and a link to Github page? I think it will be less
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
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
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 wrote:
>
> For the releases, the information is on Github:
>
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
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
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?
