damccorm opened a new issue, #26906:
URL: https://github.com/apache/beam/issues/26906

   ### What would you like to happen?
   
   Between GitHub actions and APIs, there's some good community metrics out 
there that we don't yet expose in a super useful way to the community. A couple 
examples:
   
   1. With a GitHub action, I was able to generate a PR summary on 
https://github.com/damccorm/playground/pull/29 (using my fork of the main 
https://github.com/flowwer-dev/pull-request-stats action - 
https://github.com/damccorm/playground/blob/main/.github/workflows/pr-stats.yml 
with a fix patched in). Unfortunately, that doesn't yet support exporting the 
summary direct to email, so we'd need to add that or figure out a different way 
to integrate stats
   2. GitHub insights provides a dashboard on page traffic - 
https://github.com/apache/beam/graphs/traffic
   
![image](https://github.com/apache/beam/assets/42773683/4dbcb42a-3272-4d5c-98ab-ced771f93be1)
   
   Non-committers can't see this though. We could expose it using GitHub's rest 
api - https://docs.github.com/en/rest/metrics/traffic?apiVersion=2022-11-28 - 
or using something like 
https://github.com/marketplace/actions/repository-traffic (not sure how well it 
works yet).
   
   It would be awesome if we sent an email to the devlist on some frequency 
(maybe 30 days) highlighting these stats.
   
   
   ### Issue Priority
   
   Priority: 2 (default / most feature requests should be filed as P2)
   
   ### Issue Components
   
   - [ ] Component: Python SDK
   - [ ] Component: Java SDK
   - [ ] Component: Go SDK
   - [ ] Component: Typescript SDK
   - [ ] Component: IO connector
   - [ ] Component: Beam examples
   - [ ] Component: Beam playground
   - [ ] Component: Beam katas
   - [ ] Component: Website
   - [ ] Component: Spark Runner
   - [ ] Component: Flink Runner
   - [ ] Component: Samza Runner
   - [ ] Component: Twister2 Runner
   - [ ] Component: Hazelcast Jet Runner
   - [ ] Component: Google Cloud Dataflow Runner


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to