Hey there, I meant to remove the issues section at top and replace with the
one in the community health section but forgot to remove the top part. I
just submitted with the removed top part. Let me know if people want me to
further edit.
Thanks
On Thu, Oct 10, 2019 at 1:54 PM Antoine Pitrou
Antoine, is my synopsis fair?
On Thu, Oct 10, 2019 at 12:53 PM Wes McKinney wrote:
> +1
>
> On Thu, Oct 10, 2019, 2:12 PM Jacques Nadeau wrote:
>
> > Proposed report update below. LMK your thoughts.
> >
> > ## Description:
> > The mission of Apache Arrow is the creation and maintenance of
+1
On Thu, Oct 10, 2019, 2:12 PM Jacques Nadeau wrote:
> Proposed report update below. LMK your thoughts.
>
> ## Description:
> The mission of Apache Arrow is the creation and maintenance of software
> related to columnar in-memory processing and data interchange
>
> ## Issues:
>
> * We are
Proposed report update below. LMK your thoughts.
## Description:
The mission of Apache Arrow is the creation and maintenance of software
related to columnar in-memory processing and data interchange
## Issues:
* We are struggling with Continuous Integration scalability as the project
has
Arg... accidental send before ready.
What do think about the statement below for community health? Does it
fairly capture the concerns/perspective?
On Thu, Oct 10, 2019 at 10:24 AM Jacques Nadeau wrote:
> Many contributors are struggling with the slowness of pre-commit CI. Arrow
> has a large
Many contributors are struggling with the slowness of pre-commit CI. Arrow
has a large number of different platforms and components and a complex
build matrix. As new commits come in, they frequently take a long time to
complete. The community is trying several ways to solve this. Some of those
Here is a rejection of CircleCI more than 18 months ago
https://issues.apache.org/jira/browse/INFRA-15964
On Thu, Oct 10, 2019 at 4:33 AM Antoine Pitrou wrote:
>
>
> For the record, here is the ticket for Azure Pipelines integration:
> https://issues.apache.org/jira/browse/INFRA-17030
>
> I
For the record, here is the ticket for Azure Pipelines integration:
https://issues.apache.org/jira/browse/INFRA-17030
I opened an issue back in May about the Travis-CI capacity situation:
https://issues.apache.org/jira/browse/INFRA-18533
Apparently CI capacity has been a "hot topic as of
On Thu, Oct 10, 2019 at 12:22 AM Jacques Nadeau wrote:
>
> I'm not dismissing the there are issues but I also don't feel like there
> has been constant discussion for months on the list that INFRA is not being
> responsive to Arrow community requests. It seems like you might be saying a
> couple
I'm not dismissing the there are issues but I also don't feel like there
has been constant discussion for months on the list that INFRA is not being
responsive to Arrow community requests. It seems like you might be saying a
couple different things one of two things (or both?)?
1) The Arrow
hi Jacques,
I think we need to share the concerns that many PMC members have over
the constraints that INFRA is placing on us. Can we rephrase the
concern in a way that is more helpful?
Firstly, I respect and appreciate the ASF's desire to limit write
access to committers only from an IP
I think we need to more direct in listing issues for the board.
What have we done? What do we want them to do?
In general, any large org is going to be slow to add new deep integrations
into GitHub. I don't think we should expect Apache to be any different (it
took several years before we could
New draft
## Description:
The mission of Apache Arrow is the creation and maintenance of software related
to columnar in-memory processing and data interchange
## Issues:
* We are struggling with Continuous Integration scalability as the project has
definitely outgrown what Travis CI and
Yes, I agree with raising the issue to the board.
On Tue, Oct 8, 2019 at 8:31 AM Antoine Pitrou wrote:
>
>
> I agree. Especially given that the constraints imposed by Infra don't
> help solving the problem.
>
> Regards
>
> Antoine.
>
>
> Le 08/10/2019 à 15:02, Uwe L. Korn a écrit :
> > I'm not
I agree. Especially given that the constraints imposed by Infra don't
help solving the problem.
Regards
Antoine.
Le 08/10/2019 à 15:02, Uwe L. Korn a écrit :
> I'm not sure what qualifies for "board attention" but it seems that CI is a
> critical problem in Apache projects, not just Arrow.
I'm not sure what qualifies for "board attention" but it seems that CI is a
critical problem in Apache projects, not just Arrow. Should we raise that?
Uwe
On Tue, Oct 8, 2019, at 12:00 AM, Wes McKinney wrote:
> Here is a start for our Q3 board report
>
> ## Description:
> The mission of Apache
Here is a start for our Q3 board report
## Description:
The mission of Apache Arrow is the creation and maintenance of software related
to columnar in-memory processing and data interchange
## Issues:
There are no issues requiring board attention at this time
## Membership Data:
* Apache Arrow
17 matches
Mail list logo
