search

RDruzinsky / feedontology

Automatically exported from code.google.com/p/feedontology
1 stars 1 forks source link

Add obofoundry topic to repo metadata #2

Open cthoyt opened 3 years ago

cthoyt commented 3 years ago

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 https://github.com/OBOFoundry/OBOFoundry.github.io/issues/1538 in case you want some more context or to join the larger discussion.

cthoyt commented 1 year ago

Hi @RDruzinsky, 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 https://github.com/OBOFoundry/OBOFoundry.github.io/issues/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.

hlapp commented 1 year ago

Hi @cthoyt – it's probably fair to say that the ontology is not currently under active development. But it's not orphaned, nor unresponsive.

Personally, although I'm quite sympathetic to what seems to be the goal (reporting the current maintenance status of ontologies), I'm not sure it's quite fair to infer orphaned or unresponsive status simply from not implementing something that in my understanding is a mere suggestion. Or is there now a set of required repository tags for OBO ontologies? (But perhaps I should post this to the issue thread you're linking above.)

cthoyt commented 1 year ago

@hlapp thanks for the note. You're totally right that it's the case that it's not a requirement for OBO Foundry ontologies to add specific tags on GitHub. I would be perfectly happy if the answer were "no" and we can also close this issue.

However, the fact that this issue went without response for two years (and has not been touched since 2015) seems like a good indicator that we should reconsider its status. Of the 176 ontologies I pinged two years ago, 132 were able to respond (whether positive or not), leaving only a small minority that did not respond, which is what I meant by "unresponsive".

Do you know if @RDruzinsky is still able to respond to messages? If not, do you think that you would be an appropriate alternative to be the contact person for this repository?

hlapp commented 1 year ago

However, the fact that this issue went without response for two years (and has not been touched since 2015) seems like a good indicator that we should reconsider its status. [...] Do you know if @RDruzinsky is still able to respond to messages?

I'll have to leave the answer to that to Robert. However, issues posted here are seen by multiple people. Not everyone can act on everything, but there are people here (such as myself 😎) who can respond to ontology maintenance issues if necessary.

cthoyt commented 1 year ago

I emailed Robert on October 19th, 2023 at druzinsk@uic.edu (listed on OBO Foundry) to ask about this

RDruzinsky commented 1 year ago

Hi, Sadly, I do not believe that anyone is using or maintaining the Feed ontology anymore. Robert

On Thu, Oct 19, 2023, 5:10 AM Charles Tapley Hoyt @.***> wrote:

I emailed Robert on October 19th, 2023 at @.*** (listed on OBO Foundry) to ask about this

— Reply to this email directly, view it on GitHub https://github.com/RDruzinsky/feedontology/issues/2#issuecomment-1770497715, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABASAOBN5QE2EE2RS3RCUFLYAD4B7AVCNFSM46J2XEJKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCNZXGA2DSNZXGE2Q . You are receiving this because you were mentioned.Message ID: @.***>