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

Potential entries based on up-for-grabber tool #1273

Open
SeanKilleen opened this issue Jun 30, 2019 · 6 comments
Open

Potential entries based on up-for-grabber tool #1273

SeanKilleen opened this issue Jun 30, 2019 · 6 comments
Assignees
Labels
discussion open-ended issues that haven't yet defined what needs to be worked on hacktoberfest Issues that need help from new contributors

Comments

@SeanKilleen
Copy link
Contributor

(Following up on #1028 now that I've built out a tool.)

Hey all -- I built a tool that can surface potential projects across an org for up-for-grabber.

I did this for the microsoft org and looked for Repos that had 25+ issues with up-for-grabs style labels where the most recent occurrence was < 90 days ago.

What I found:

* `microsoft/terminal` has 47925 stars. It has 523 open issues, 156 of which exist across 1 up-for-grabs style labels. The most recent up-for-grabs issue was on 2019-06-30T21:51:49.0000000+00:00, 0 days ago.
* `microsoft/azure-pipelines-image-generation` has 444 stars. It has 158 open issues, 61 of which exist across 1 up-for-grabs style labels. The most recent up-for-grabs issue was on 2019-06-27T20:08:56.0000000+00:00, 3 days ago.
* `microsoft/LightGBM` has 9021 stars. It has 90 open issues, 68 of which exist across 1 up-for-grabs style labels. The most recent up-for-grabs issue was on 2019-06-01T22:09:30.0000000+00:00, 28 days ago.
* `microsoft/web-build-tools` has 854 stars. It has 160 open issues, 96 of which exist across 2 up-for-grabs style labels. The most recent up-for-grabs issue was on 2019-06-28T01:42:20.0000000+00:00, 2 days ago.
* `microsoft/vscode-vsce` has 181 stars. It has 47 open issues, 37 of which exist across 1 up-for-grabs style labels. The most recent up-for-grabs issue was on 2019-06-28T11:25:53.0000000+00:00, 2 days ago.
* `microsoft/tslint-microsoft-contrib` has 610 stars. It has 106 open issues, 105 of which exist across 3 up-for-grabs style labels. The most recent up-for-grabs issue was on 2019-06-18T07:58:03.0000000+00:00, 12 days ago.
* `microsoft/Git-Credential-Manager-for-Windows` has 2078 stars. It has 51 open issues, 27 of which exist across 1 up-for-grabs style labels. The most recent up-for-grabs issue was on 2019-05-28T09:52:55.0000000+00:00, 33 days ago.
* `microsoft/PTVS` has 2180 stars. It has 579 open issues, 45 of which exist across 1 up-for-grabs style labels. The most recent up-for-grabs issue was on 2019-06-28T22:51:23.0000000+00:00, 1 days ago.
* `microsoft/msbuild` has 3956 stars. It has 1090 open issues, 119 of which exist across 1 up-for-grabs style labels. The most recent up-for-grabs issue was on 2019-06-27T15:03:50.0000000+00:00, 3 days ago.

My question for the maintainers is on how to proceed. Should I:

  • Submit these PRs for repos that don't currently exist in up-for-grabs?
  • Or should I ask the maintainers of those repos to consider adding it, by filing an issue etc.?
@SeanKilleen
Copy link
Contributor Author

SeanKilleen commented Jun 30, 2019

/cc @ritwik12 since they'd responded positively to #1028.

@SeanKilleen SeanKilleen changed the title Potential entries based on up-for-grabber tool. Potential entries based on up-for-grabber tool Jun 30, 2019
@ritwik12 ritwik12 added the discussion open-ended issues that haven't yet defined what needs to be worked on label Jun 30, 2019
@ritwik12
Copy link
Collaborator

Hey @SeanKilleen, Thanks for this. That's good work and pretty nice results you are getting. My opinion is that you can submit PRs for the repos which are owned by organizations who are not owned by a single person or small group and are for everyone. Such as: Google, Microsoft, Mozilla, Apache, or any big Open source organizations.

But I will prefer creating an issue for the repos that are owned by individuals or small group of people as they might not want their repo at up-for-grabs and I think it will not be good to spam or hurt anyone.

@shiftkey can add more insights on this to help better.

@stale

This comment has been minimized.

@stale stale bot added the wontfix label Oct 16, 2019
@shiftkey shiftkey removed the wontfix label Oct 16, 2019
@SeanKilleen
Copy link
Contributor Author

@ritwik12 @shiftkey any insights on this? It was marked stale but I'm happy to submit these items above based on the tool I created. Per @ritwik12's recommendation I'm happy to submit just the org-based items.

@shiftkey shiftkey self-assigned this Oct 16, 2019
@shiftkey
Copy link
Member

@SeanKilleen i still haven't really thought about this. Give me a couple of days to catch up.

The stale bot wasn't meant to touch issues, but instead kicked off it's default behaviour - see #1561 for context.

@SeanKilleen
Copy link
Contributor Author

👍 No worries and no rush. I want to support the project but only if the tooling is valuable and doesn't add more noise than signal.

@ritwik12 ritwik12 added the hacktoberfest Issues that need help from new contributors label Sep 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion open-ended issues that haven't yet defined what needs to be worked on hacktoberfest Issues that need help from new contributors
Projects
None yet
Development

No branches or pull requests

3 participants