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
Hi Ismaël,
Yep, I think it's a little bit noisy for our mailing list with such
notifications. But it's fun to see what other people are working on.
IMHO, in addition to a new mailing list, we should have a better label
mechanism for easily routing/filtering messages.
Thank you.
On
Hello,
Some of you have probably noticed that we are receiving a LOT of extra
notifications that were not active in the past. This is happening because
Apache INFRA installed a new way to map notifications into mailing lists for its
projects and the default configuration right now is sending all
iemejia opened a new pull request #873:
URL: https://github.com/apache/avro/pull/873
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go
Ismaël Mejía created AVRO-2826:
--
Summary: Add .asf.yaml file to configure github notifications
Key: AVRO-2826
URL: https://issues.apache.org/jira/browse/AVRO-2826
Project: Apache Avro
Issue
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
zolyfarkas commented on pull request #864:
URL: https://github.com/apache/avro/pull/864#issuecomment-624052220
@iemejia what do you think?
This is an automated message from the Apache Git Service.
To respond to the message,
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:
>
kojiromike commented on pull request #847:
URL: https://github.com/apache/avro/pull/847#issuecomment-624029597
Looks good to me. Thanks for contributing!
This is an automated message from the Apache Git Service.
To respond
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
14 matches
Mail list logo
