Sounds great! Thanks
On Fri, Jun 18, 2021 at 9:29 AM Jorge Cardoso Leitão
wrote:
>
> Hi Wes,
>
> Yes, on ASF Slack, #arrow-rust. Andy advertised it here some time ago.
>
> Most relevant topics there end up either as a github issue or over
> this mailing list. On this note, hat tip to Andrew, who
Hi Wes,
Yes, on ASF Slack, #arrow-rust. Andy advertised it here some time ago.
Most relevant topics there end up either as a github issue or over
this mailing list. On this note, hat tip to Andrew, who has been doing
a lot of the curation.
There are other informal discussions, more about Rust
hi Jorge — there is a Rust Slack channel? On that, I would just say to
be vigilant about what communication takes place there (since Slack is
semi-private) versus on channels that are being archived / mirrored to
mailing lists. It's useful for coordination and quick questions but
not a place to
Hi,
I agree that the communication improved a lot with moving the issues
to Github and slack, which made the sync call less relevant.
Best,
Jorge
On Thu, Jun 17, 2021 at 11:55 PM Andrew Lamb wrote:
>
> I think dropping back from the Rust sync call and using the regular Arrow
> Sync call
I think dropping back from the Rust sync call and using the regular Arrow
Sync call should that be necessary is a good idea
Andrew
On Thu, Jun 17, 2021 at 12:27 PM Andy Grove wrote:
> I would like to propose canceling the bi-weekly Rust sync call, at least in
> its current form.
>
> The call
I would like to propose canceling the bi-weekly Rust sync call, at least in
its current form.
The call has not been very active since we moved to the new GitHub
repositories and implemented some changes to the development process. It
seems that the Rust community is communicating well without the
