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

Principle #13 "Notification" - NEW PROPOSED PRINCIPLE #1715

Closed
nataled opened this issue Dec 21, 2021 · 10 comments
Closed

Principle #13 "Notification" - NEW PROPOSED PRINCIPLE #1715

nataled opened this issue Dec 21, 2021 · 10 comments
Assignees
Labels
attn: Editorial WG Issues pertinent to editorial activities, such as ontology reviews and principles attn: Operations Committee Issues pertinent to broad Foundry activities, such as policies and guidelines principles Issues related to Foundry principles

Comments

@nataled
Copy link
Contributor

nataled commented Dec 21, 2021

Draft text has been uploaded in a new pull request #1714

Please comment on the text as a whole and on specific areas for change.

The EWG believes there is the possibility for automating this, though doing so would likely require narrowing the scope of allowable mechanisms for notification. Automation would involve ascertaining the date of announcement as it compares to date of implementation.

@nataled nataled added attn: Operations Committee Issues pertinent to broad Foundry activities, such as policies and guidelines attn: Editorial WG Issues pertinent to editorial activities, such as ontology reviews and principles principles Issues related to Foundry principles attn: OFOC call Issue to discuss on fortnightly OBO Operations meeting labels Dec 21, 2021
@nataled nataled self-assigned this Dec 21, 2021
@nataled
Copy link
Contributor Author

nataled commented Feb 8, 2022

From @matentzn:

Wow this is some principle.. :) I love this, but this will put a huge burden on ontology developers.. If they use GitHub, maybe we can promote an ongoing diff report that is published at some predefined purl location like /diff.txt or some such.. It will also be massively complex otherwise to automatically test this. I am not against it, just.. worried its quite a tough one to meet!

@nataled
Copy link
Contributor Author

nataled commented Feb 8, 2022

This principle was moved forward during the Operations call of 30-Nov-2021, so the principle itself is set. There was, however, general agreement during the call that this could be a burden, which is why we went with "should" instead of "must". I agree with your sentiment regarding automated testing. However, (1) we have so far one other principle with no testing; and (2) most checks done by the dashboard only approximate the principle anyway (though the EWG is working on ways to diminish that).

@nlharris
Copy link
Contributor

Where are we at with this?

@nataled
Copy link
Contributor Author

nataled commented Jul 25, 2022

Awaits refinement of wording by EWG. We typically do so when the person who wrote the original draft is available, but I was recently informed that this person is no longer available for meetings. Will be taken up again when manpower allows.

@nlharris
Copy link
Contributor

Who was the person who wrote the original draft? It shows up as being by you.

@nlharris nlharris removed the attn: OFOC call Issue to discuss on fortnightly OBO Operations meeting label Jul 25, 2022
@nataled
Copy link
Contributor Author

nataled commented Jul 25, 2022

I'm the one that wrote the ticket on github. The draft was by Krishna Udaiwal.

@nataled
Copy link
Contributor Author

nataled commented Dec 20, 2022

Writing is done, page is ready, awaiting review by OFOC and linking on main site. To review: https://obofoundry.org/principles/fp-013-notification.html

@nataled nataled added the attn: OFOC call Issue to discuss on fortnightly OBO Operations meeting label Dec 20, 2022
@matentzn
Copy link
Contributor

matentzn commented Mar 6, 2023

Action items (from last call)

  • Ask for feedback on obo-discuss
  • Ask feedback on Slack’s #general channel
  • When feedback is in, add back on OFOC agenda.

@matentzn matentzn removed the attn: OFOC call Issue to discuss on fortnightly OBO Operations meeting label Mar 6, 2023
@nataled
Copy link
Contributor Author

nataled commented Mar 14, 2023

Barring any feedback that scuttles the whole thing or that requires major revision, this principle will become official as of 2023-03-28.

@nataled
Copy link
Contributor Author

nataled commented Apr 17, 2023

Closing since Principle 13 has now gone "live"

@nataled nataled closed this as completed Apr 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
attn: Editorial WG Issues pertinent to editorial activities, such as ontology reviews and principles attn: Operations Committee Issues pertinent to broad Foundry activities, such as policies and guidelines principles Issues related to Foundry principles
Projects
None yet
Development

No branches or pull requests

4 participants