+1
I think it will be more accessible and searchable.
*Regards,*
*Rossi SUN*
Sutou Kouhei 于2025年3月13日 周四11:07写道:
> Hi,
>
> It seems that we can enable GitHub Discussions by .asf.yaml:
>
>
> https://github.com/apache/infrastructure-asfyaml/blob/main/README.md#repository-features
>
> Do we want
Hi folks,
Regarding our activity on the project and the adoption of Apache
Arrow, I would like to start a discussion about an Apache Arrow
Meetup, gathering contributors, users and enthusiasts about Arrow
generally speaking.
The idea is to have a community event, where a Selection Committee
(sele
Congrats JB. And welcome.
On Sun, Mar 9, 2025 at 11:05 PM Sutou Kouhei wrote:
>
> Hi,
>
> On behalf of the Arrow PMC, I'm happy to announce that
> Jean-Baptiste Onofré has accepted an invitation to become a
> committer on Apache Arrow. Welcome, and thank you for your
> contributions!
>
> Thanks,
+1
On Thu, Mar 6, 2025 at 5:41 PM Rok Mihevc wrote:
> +1 would attend and help with organisation.
>
> On Thu, Mar 6, 2025 at 5:57 PM Alenka Frim wrote:
>
>> +1 from me too, great idea - would definitely like to attend and help
>> with organisation!
>>
>> V V čet., 6. mar. 2025 ob 17:31 je oseba
Congratulations JB! Welcome!
El lun, 10 mar 2025 a las 8:24, David Li () escribió:
> Congrats JB! Your help has been much appreciated.
>
> On Mon, Mar 10, 2025, at 15:03, Sutou Kouhei wrote:
> > Hi,
> >
> > On behalf of the Arrow PMC, I'm happy to announce that
> > Jean-Baptiste Onofré has accept
+1
Also happy to help Curt with releases etc.
Am Fr., 14. März 2025 um 21:08 Uhr schrieb Bryce Mecum :
>
> Hi Kou, thanks for proposing this.
>
> I think it makes sense and sounds like a good thing to do. I'm happy
> to help with migration tasks and releases.
>
> On Wed, Mar 12, 2025 at 7:51 PM S
+1
For me the main argument is that the discoverability is much better than the ML.
A point to note, enabling discussions requires setting a ML that they
are mirrored to. So we could use users@ for that but that might be
confusing, so discussions@ or something might be better. For rust we
used gi
I think this is a good idea.
A possible reason for hesitation is that it provides us yet another
stream that requires maintainer attention. But it also occurs to me
that a new stream of information on GitHub may be significantly more
accessible than a stream on a mailing list or third-party websit
Hello Arrow Developers / Users,
We are discussing the policy for minimum supported Rust version[1]. Please
comment on the ticket if you would like to participate in the discussion
Thank you,
Andrew
[1]: https://github.com/apache/arrow-rs/issues/181