Features community expects from Weekly Digest

[abhijeetps]

Hey all! 👋

This summer, I am planning to work on Weekly Digest and get application ready to be installed!

This thread is to share and discuss the set of features and ideas you would love to expect from Weekly Digest. 😄

Some example of ideas and your thoughts on it:

• How the weekly digest should be published?
• What GitHub events need to be considered?
• Should there be any priority for the same?

Please share your ideas here. Any other ideas are welcomed. 😇

[abhijeetps]

Additional discussion of weekly digest happened here: probot/ideas#24
😄

[bkeepers]

How the weekly digest should be published?

I'd personally love a weekly email.

What GitHub events need to be considered?

Everything from pulse would be a good start.

[steveoh]

I think

1. Number of visitors to repo
2. Number of contributors
3. Number of new issues/pr's
4. Average time to close issues/pr's
5. Lines of code added/removed
6. Number of builds run
7. average time of build
8. test report metrics
9. % pass % fail
10. code coverage metrics

It would be nice to compare to last week similar to facebook org digest

[zeke]

Sourceranks could be handy: https://docs.libraries.io/overview#sourcerank

I'd like to be notified of new modules by module authors whose packages I frequently use in my projects. Might be out of scope but just an idea!

Overview

Documentation for contributors to the Libraries.io project.

[wilhelmklopp]

Personally I think that I would find a weekly digest that highlights the most important activity that occurred in a repo more valuable compared to one that tries to include an abundance of different stats which could make it quite hard to digest. As such I feel like:

1. Prioritisation will be important
2. It would be cool if every statistic this digest intends to include addresses a clearly identified use case from the perspective of a maintainer/contributor/admin

So approaching it slightly more from the 'What would I as a maintainer/contributor find valuable to see in a weekly digest?' perspective as opposed to the 'Which GitHub events are the most important to include?' perspective, the things that come to mind are:

• Which major features shipped over the past week?
• What progress was made on features that haven't yet shipped?
• How healthy was our community over the past week?
  • How well are we responding to newly created issues?
  • Do we review PRs from outside contributors?
• Are there any new collaborators or new integrations?

(intentionally phrasing them vaguely to stay away from implementation for now)

Maybe these could be grouped by category like feature progress, community, administration, etc?

As @steveoh already mentioned I feel like a week by week comparison and deviations from the general trend would be valuable to call out. Although potentially out of scope for an initial ship?

[abhijeetps]

I would like to add here the idea of the tweet by Andy Fowler (https://twitter.com/andyfowler) in this tweet: https://twitter.com/andyfowler/status/991052478421483520
Noisiest PRs, stale PRs, changiest PRs, and PRs (opened & merges) per team member!

Andy Fowler (@andyfowler) | Twitter

The latest Tweets from Andy Fowler (@andyfowler). cofounder, @Nutshell. ❤️ airplanes, beagles, bicycles, and great software. Ann Arbor, MI

Twitter

Andy Fowler on Twitter

“@bkeepers Noisiest PRs, stale PRs, changiest PRs, and PRs (opened & merges) per team member!”