Skip to content

Add Community Highlights 2025 blog post#768

Open
AlenkaF wants to merge 6 commits intoapache:mainfrom
AlenkaF:arrow-high-25
Open

Add Community Highlights 2025 blog post#768
AlenkaF wants to merge 6 commits intoapache:mainfrom
AlenkaF:arrow-high-25

Conversation

@AlenkaF
Copy link
Member

@AlenkaF AlenkaF commented Mar 4, 2026

No description provided.

@github-actions
Copy link

github-actions bot commented Mar 4, 2026

Preview URL: https://AlenkaF.github.io/arrow-site

If the preview URL doesn't work, you may forget to configure your fork repository for preview.
See https://github.com/apache/arrow-site/blob/main/README.md#forks how to configure.

@AlenkaF
Copy link
Member Author

AlenkaF commented Mar 4, 2026

Comment on lines +66 to +72
| Author | # of prs | # of comments on prs | # of pr reviews | # of line changes (+ and -) |
|---|---|---|---|---|
| alinaliBQ | 36 | 505 | 332 | 15754 |
| andishgar | 19 | 438 | 304 | 2926 |
| AntoinePrv | 8 | 440 | 318 | 79257 |
| rmnskb | 7 | 123 | 56 | 550 |
| justing-bq | 4 | 93 | 76 | 12607 |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems "# of pr reviews" is actually counting the number of PR review comments by others? I'm not sure that's relevant, but the column heading is misleading anyway (I don't think AntoinePrv did 300 PR reviews for example :-)).

(also, "# of comments on prs" counts comment by others on the author's PRs, so may be misleading as well)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At least for reviews, "# number of reviewed prs" would be more informative IMHO.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right I need to take a better look at this numbers. What I actually counted, though, are number of comments and number of reviews (that would probably mean number of comments as part of reviews) for the PRs the user authored. I wanted to get a better picture of the importance of the merged PRs and thought that bigger contributions include higher amount of comments and reviews.

Will double check anyways and remove the columns from the blog post. They can be viewed in the linked notebooks for reference anyways.

@pitrou
Copy link
Member

pitrou commented Mar 4, 2026


This blog post has been created as an effort to improve the value of
an individual contributor with recognition and visibility. As per
IEEE Software paper [^1] concrete evidence of our progress and
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for adding this reference!

Copy link
Member

@kou kou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for writing this!

| andishgar | 19 | 438 | 304 | 2926 |
| AntoinePrv | 8 | 440 | 318 | 79257 |
| rmnskb | 7 | 123 | 56 | 550 |
| justing-bq | 4 | 93 | 76 | 12607 |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"# of comments on prs" may not be a good metrics. Some comments may be important discussion but some comments may be not important minor contents (e.g. pointing out mismatch coding style). In general, the fewer the latter comments, the better..

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, that might be true. My general feeling in the apache repos is that bigger and important prs get more reviews and comments. But will trust you on this!

I have already removed the columns from the blog post. Will also see if removing them from the ranking in the notebooks changes anything and will update accordingly.

AlenkaF and others added 3 commits March 5, 2026 10:06
Co-authored-by: Raúl Cumplido <raulcumplido@gmail.com>
Co-authored-by: Antoine Pitrou <pitrou@free.fr>
IEEE Software paper [^1] concrete evidence of our progress and
accomplishments can help with motivation and better collaboration in
the open source community.

Copy link
Member

@thisisnic thisisnic Mar 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Love this! Had a mini rework to suggest for the opener, but it's good as it is, so feel free to leave it out.

As you may have read in a previous blog post, the Apache Arrow project recently turned 10 years old. We are grateful to everyone who helped us achieve this milestone, and we wanted to celebrate the community's accomplishments, by publishing our community highlights from 2025.

We were inspired by the research by Dr Cat Hicks et al [^1], who found that concrete evidence of progress and accomplishments is instrumental to motivation and collaboration in open source.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like it, thanks! Will add.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@thisisnic I am thinking to add a minor change at the end of the last sentence:

[...], who found that concrete evidence of progress and accomplishments is instrumental
to motivation and collaboration in developer teams. We think the same should hold for open source.

What do you think?


## Closing of Stale issues

[thisisnic](https://github.com/thisisnic) was working on closing of stale
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Aww, thanks for the shout out!

[raulcd](https://github.com/raulcd) and [pitrou](https://github.com/pitrou)
for organizing the event.

<!-- TODO: Would it be possible to add a group picture here? -->
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should 100% add a group picture, great idea! <3

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@raulcd do I remember correctly that you have the group photos? Would you share one with me so I can add it here?

Copy link
Member

@paleolimbot paleolimbot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome! Thank you for this summary!

AlenkaF and others added 2 commits March 6, 2026 08:37
Co-authored-by: Dewey Dunnington <dewey@dunnington.ca>
Co-authored-by: Nic Crane <thisisnic@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants