-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add obofoundry topic to repo metadata #9
Comments
Hi @jrsjrs, this is an automated message. On June 8th, 2021 (almost 2 years ago), I posted this issue using another automated script in hopes that someone would be responsive on this repository and then be able to add a tag to this repository's metadata. This is regarding OBOFoundry/OBOFoundry.github.io#1538. Because it's been so long without addressing the issue, I am concerned that this repository is no longer responsive/being maintained. Can you please let me know if that's the case? In a few months, if this follow-up message goes unanswered, I will recommend to the OBO Foundry to change the status of this ontology to either "inactive" or "orphaned", meaning that the nominal contact person is no longer responsive and/or the repository is no longer maintained. Given one of the OBO Foundry's principles is about responsiveness (see https://obofoundry.org/principles/fp-020-responsiveness.html), it is important that we are transparent to the community about the status of each resource so potential users can make the best choice of which resources to use. Finally, please let me know if there are any questions about how to add the "obofoundry" topic tag to this repository. |
obofoundry topic added! |
@tutajm are you now the responsible person for this ontology? Should we update the OBO Foundry metadata about it? |
The OBO Foundry has recently created a topics page at https://github.com/topics/obofoundry. It would be great if you could add the
obofoundry
topic to your repository, since it's currently listed as active in the OBO Foundry. If you're not sure how to do that, follow the instructions here. The main issue for this task is at OBOFoundry/OBOFoundry.github.io#1538 in case you want some more context or to join the larger discussion.The text was updated successfully, but these errors were encountered: