-
Notifications
You must be signed in to change notification settings - Fork 205
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
Encourage repositories to add obofoundry
topic
#1538
Comments
Sorry, I should know that, but could you please clarify this sentence: |
@mbrochhausen GitHub rightly protects itself and its users from abuse by looking for fishy people like me who are opening lots of issues programatically in very quick succession. After 15 or 20 issues posted, it started returning a warning that I was abusing the API and should try later. After I initially posted the comment you're referring to, I realized I could just add a simple rate limit by using |
Thanks! I appreciate the clarification. |
We (OFOC call today) decided to mandate this softly as part of best practices which are collected here: #1579 Thanks for the suggestion! Great. |
@matentzn excellent |
As of right now, 43 of the repositories that I originally pinged two years ago have not responded. I just pinged all 43, tagging their responsible people (this is now possible since in the last two years, I have convinced the OBO community that having the GitHub handle easily accessible for each active ontology is valuable). I suggest that in a few months, we review who remains unresponsive and begin marking ontologies as orphaned/inactive accordingly. |
You can always initiate a process like this, but not dealing with a specific issue does not all by itself constitute "inactivity" |
True, but most of the remaining haven’t committed in the last 3-5 years and haven’t addressed any of the issues or PRs. I would be keen on having a more concrete definition of “inactive” and would hope that it includes any repository that hasn’t committed or responded to issues in the last X years (pick whatever x feels most comfortable) |
After completing #1493, it's now time to do a bit of outreach to the community and ask all of the different members to add the
obofoundry
topic to their repos. It's pretty simple through the main page for the repository, but in case it's not obvious there's a tutorial here: https://docs.github.com/en/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics.Methods
I've used the following script https://gist.github.com/cthoyt/95694a05190fc23b997fae62f12f96f1 which generates this table as a summary and also automatically created issues on all of the repos (which get linked back to this one). Note, after a while this triggers the abuse detection in the GitHub API 😆, so I added in a
time.sleep(2)
to calm it downFull Table, created at the time of filing the issue
The text was updated successfully, but these errors were encountered: