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

Automatically mark new ontology issues as stale when no recent interaction #1575

Closed
cthoyt opened this issue Aug 21, 2021 · 2 comments
Closed
Labels
attn: Operations Committee Issues pertinent to broad Foundry activities, such as policies and guidelines

Comments

@cthoyt
Copy link
Collaborator

cthoyt commented Aug 21, 2021

What is the status of this? Are we waiting for submitter action, or are they waiting for feedback from OBO Foundry?

Originally posted by @nlharris in #1508 (comment)

@nlharris has recently done an exemplary job of shepherding the community of new OBO ontology submitters, but there might be a technical solution to lessen the burden on her - https://github.com/actions/stale could be used to mark any issue tagged with "new ontology" as stale (e.g., add an additional label called "stale") after a given amount of time. Perhaps the best length would be 4-6 weeks but that's up for discussion. This doesn't close the issue (which would probably make submitters upset, or even worse, lead to duplicate threads) but rather is a mark so people can filter on this tag, and more specifically consider whether to dismiss abandoned discussions later.

@nlharris
Copy link
Contributor

@nlharris has recently done an exemplary job of shepherding the community of new OBO ontology submitters

Not just recently. 😉

I appreciate the thought, but honestly, I think we get few enough new ontology submissions that trying to automate the tagging is not necessary and is more likely to cause resentment from various parties. I like the general thought of using actions to automate some of our processes, though!

@nlharris nlharris added the attn: Operations Committee Issues pertinent to broad Foundry activities, such as policies and guidelines label Aug 21, 2021
@matentzn
Copy link
Contributor

I agree with @nlharris - there are too few NORs for this to be worth it - we can handle this manually.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
attn: Operations Committee Issues pertinent to broad Foundry activities, such as policies and guidelines
Projects
None yet
Development

No branches or pull requests

3 participants