I can look into stats for project activity and community health. It's not totally clear to me what kind of Issues should be shared in this context, but I have two on my mind:
* The way INFRA crippled the CI for the most active parts of our project (Rust, C++) without warning on a holiday weekend, then ignored our request for help all week (https://issues.apache.org/jira/browse/INFRA-21239, still unresolved as of this writing), was disappointing. I recognize that maintaining the security of infrastructure is often a thankless job, but the apparent lack of empathy for the maintainers of the projects they serve doesn't help. I expect better from an organization whose mission is to support open source software development. * Our release process is too costly and is bottlenecked on a very small number of PMCs who might be able to perform it, and we haven't managed to do anything to improve this. (I suspect this is something for us to resolve, not something that the board necessarily cares to hear.) Neal On Tue, Jan 5, 2021 at 2:33 PM Wes McKinney <wesmck...@gmail.com> wrote: > It's time for our quarterly board report (due next Wednesday). Can > everyone help with completing the various sections? > > ## Description: > The mission of Apache Arrow is the creation and maintenance of software > related > to columnar in-memory processing and data interchange > > ## Issues: > [Insert your own data here] > > ## Membership Data: > Apache Arrow was founded 2016-01-19 (5 years ago) > There are currently 54 committers and 30 PMC members in this project. > The Committer-to-PMC ratio is 9:5. > > Community changes, past quarter: > - No new PMC members. Last addition was Francois Saint-Jacques on > 2020-03-04. > - Andrew Lamb was added as committer on 2020-11-06 > > ## Project Activity: > [Insert your own data here] > > ## Community Health: > [Insert your own data here] >
