Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Operate First Community Metrics EDA notebook #80

Merged
merged 1 commit into from
Sep 1, 2021

Conversation

hemajv
Copy link
Member

@hemajv hemajv commented Aug 27, 2021

Initial notebook to fetch and visualize the GitHub metrics for the Operate First community.

Related Issues:
#22
AICoE/data-driven-development#4

@sesheta sesheta added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 27, 2021
@sesheta sesheta requested review from oindrillac and tumido August 27, 2021 19:48
@sesheta sesheta added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Aug 27, 2021
@durandom
Copy link
Member

@hemajv can we just keep the alerts repo out of the graphs?

@durandom
Copy link
Member

and can you run the same notebook on the 2021-09-01 and have the graphs display just months until August?

@hemajv hemajv force-pushed the opf-community-nb branch 3 times, most recently from 587aca1 to 4405685 Compare August 31, 2021 17:25
@hemajv hemajv changed the title [WIP] Operate First Community Metrics EDA notebook Operate First Community Metrics EDA notebook Aug 31, 2021
@hemajv hemajv removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 31, 2021
Co-authored-by: Shrey <shanand@redhat.com>
Co-authored-by: Hema Veeradhi <hveeradh@redhat.com>
@hemajv hemajv requested review from durandom and quaid August 31, 2021 21:08
Copy link
Member

@quaid quaid left a comment

Choose a reason for hiding this comment

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

I don't know enough yet to comment on the Jupyter notebook itself, but the overall approach and what is being looked at are great bits of first-order metrics to capture. I could maybe see putting some roadmap parts on here e.g. mailing list analysis, but we can add those later.
/lgtm
/approve

Copy link
Member

@durandom durandom left a comment

Choose a reason for hiding this comment

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

👏 great start. Thanks @hemajv @Shreyanand @cdolfi

@sesheta
Copy link
Member

sesheta commented Sep 1, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: durandom, quaid

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@sesheta sesheta added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 1, 2021
@durandom durandom merged commit ae35190 into operate-first:main Sep 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants