-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Comments
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. |
This comment has been minimized.
This comment has been minimized.
@SeanKilleen i still haven't really thought about this. Give me a couple of days to catch up. The |
👍 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. |
(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:
My question for the maintainers is on how to proceed. Should I:
The text was updated successfully, but these errors were encountered: