Hi Julian,

Congratulations! There is huge value in fixing the "small things”.
I know that core maintainers often just “suck it up” and do these things
in their personal time.

Who decides which work gets done?
Is there a governance issue that the PMC needs to worry about?

Thanks for asking. The grant is designed to fund 11 different work packages
(see list at the end of this message). Each work package is defined sufficiently
broadly that it can adapt to community needs and priorities. Raul and I have our
own idea of what needs to be done in each work package, but the individual tasks
can be adapted.

Our plan is to sollicit the community's input into each work package's contents,
and to make sure we spend time on the tasks that would bring the most returns
to the community.

QuantStack has no predefined interests here (we have, separately, clients
who fund specific developments on Arrow, but the STF-funded work is entirely
disjoint). Of course, our involvement will still be guided and constrained by
the limits of our own technological expertise.

So I would say this is no immediate topic for the PMC. That said, I think it's
generally a good thing for the PMC to worry about the project's sustainability
and its governance equilibrium.

Regards

Antoine.


PS: Summary list of work packages:

WP1: Improve Release Process
WP2: Improve Continuous Integration
WP3: Improve Fuzz Testing
WP4: Supply Chain Security
WP5: Improve C++ Build System
WP6: Improve modularity of C++ libraries
WP7: Improve Python Build System
WP8: Improve modularity of Python libraries
WP9: Deliver Arrow releases
WP10: Arrow CI operational maintenance
WP11: Community Management


Le 09/10/2025 à 22:53, Julian Hyde a écrit :
Congratulations! There is huge value in fixing the "small things”. I know that 
core maintainers often just “suck it up” and do these things in their personal time.

Who decides which work gets done?

Is there a governance issue that the PMC needs to worry about?

Julian

Reply via email to