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

Release Candidate Comments (New Contributors Closing Issues) #190

Open
klumb opened this issue Dec 30, 2019 · 9 comments
Open

Release Candidate Comments (New Contributors Closing Issues) #190

klumb opened this issue Dec 30, 2019 · 9 comments
Assignees
Labels
Metrics Candidate Release Revisiting Metric Previously released metric that is being revisited and updated

Comments

@klumb
Copy link
Member

klumb commented Dec 30, 2019

This issue was created to collect comments about the upcoming metrics release.

This thread is for comments about New Contributors Closing Issues

GitHub location: https://github.com/chaoss/wg-evolution/blob/master/metrics/New_Contributor_Closing_Issues.md

See all release candidates of metrics are at:
https://chaoss.community/metrics-202001/

@foundjem
Copy link

I have this minor concern other wise LGTM

During implementation should we consider both types of contributors “especially for contributors who are not also committers?”

Signed-off-by: Foundjem foundjem@ieee.org

@klumb
Copy link
Member Author

klumb commented Dec 30, 2019

@foundjem, what do you mean by "both types of contributors"?

@bproffitt
Copy link
Collaborator

Wondering if the title for this is correct. These are not new contributors, so much as contributors closing issues for the first time on a given project.

Also this metric feels incomplete. Are there no tool implementations?

@jgbarah
Copy link

jgbarah commented Jan 10, 2020

I agree with you, @bproffitt. The idea was to keep a general name "New Contributors", and then a "category name" (Closing Issues), which would read as "new contributors in closing issues" or more clearly "persons closing issues for the first time". I don't know if it is better to keep all kinds of "new contributors" with a common name, or it is better to write it in the form which is easier to understand.

@ccarterlandis ccarterlandis self-assigned this Jan 14, 2020
@klumb
Copy link
Member Author

klumb commented Jan 14, 2020

It would be nice to have common naming conventions for the metrics but I don't think we have been able to develop a usable structure so I would agree with @jgbarah and @bproffitt we should probably go with what is easiest to understand.

@klumb
Copy link
Member Author

klumb commented Jan 25, 2020

Is this metric ready for release?

@ccarterlandis
Copy link
Contributor

@tommens has a PR still open for this metric (#297), do we want to wait just a little longer in case others have suggestions for the name, or go ahead and merge?

@GeorgLink
Copy link
Member

PR was merged and is part of the release. Closing issue to get everything ready for release.

@ElizabethN
Copy link
Member

This metric could use a refresh. It basically reads well, but there may be more context we want to give for getting this data. We don't mention Augur or GrimoireLab at all.

@ElizabethN ElizabethN reopened this Apr 8, 2022
@ElizabethN ElizabethN added the Revisiting Metric Previously released metric that is being revisited and updated label Apr 8, 2022
@ElizabethN ElizabethN transferred this issue from chaoss/wg-evolution Apr 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Metrics Candidate Release Revisiting Metric Previously released metric that is being revisited and updated
Projects
None yet
Development

No branches or pull requests

7 participants