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

OBO Foundry Newsletter Q1 2023 #2272

Closed
matentzn opened this issue Jan 26, 2023 · 7 comments
Closed

OBO Foundry Newsletter Q1 2023 #2272

matentzn opened this issue Jan 26, 2023 · 7 comments
Assignees
Labels
documentation Issues related to documentation presented on the website or relevant to Foundry-provided tools

Comments

@matentzn
Copy link
Contributor

For now we can use this ticket to collect issues for the first great OBO Q1 newsletter!

COB

@nlharris nlharris changed the title OBO Newsletter Q1 OBO Foundry Newsletter Q1 2023 Jan 26, 2023
@nlharris nlharris added the documentation Issues related to documentation presented on the website or relevant to Foundry-provided tools label Jan 26, 2023
@nlharris
Copy link
Contributor

nlharris commented Jan 26, 2023

OBO Operations Committee meeting notes now publicly viewable: https://docs.google.com/document/d/1qhLFQL5IzTMUIBOtxJ5AqaEHcOCOQgNeXfvAb5O5P0A/edit (see #2048)

@nlharris
Copy link
Contributor

Statement about why OBO Ops meetings are not open to the public (as requested by @cthoyt)

@cthoyt
Copy link
Collaborator

cthoyt commented Jan 26, 2023

Statement about why OBO Ops meetings are not open to the public (as requested by @cthoyt)

You mean "now" and not "not", right ;)

@nlharris
Copy link
Contributor

nlharris commented Jan 26, 2023

Haha, no, I mean "not", but I realize the phrasing is confusing. I meant that you requested a statement, not that you requested the meetings not be open. 🤪

The meeting NOTES are open to the public. The meetings themselves are not. (BTW, this is not the place to discuss this.)

@cthoyt
Copy link
Collaborator

cthoyt commented Jan 26, 2023

Oops, I misread this. I think both an explanation of:

  1. Why meeting notes must be open to the public for OBO Operations Committee to be trustworthy and accountable
  2. Why meetings themselves are not open

are both important to include. For now, I agree with both of these choices as they are a nice compromise.

@nlharris
Copy link
Contributor

Yes. I meant that both of those should be included in the newsletter. Sorry to be unclear.

@matentzn
Copy link
Contributor Author

Past newsletter

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Issues related to documentation presented on the website or relevant to Foundry-provided tools
Projects
None yet
Development

No branches or pull requests

4 participants