You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that I don't have access to read the meeting notes linked to from the Istio or the Knative TOC descriptions. It made me wonder why those notes are not publicly viewable. In the interest of transparency, they seem like an artifact we'd want the whole community to be able to read.
My initial opinion is that we should clarify that the meeting notes from the TOC should be viewable by all. It's possible there's some nuance I'm missing here that led Knative and Istio to decide to make their TOC notes private, and I'm curious to hear whether folks have reasons to support that decision.
The text was updated successfully, but these errors were encountered:
@jenspinney The Istio and I guess the Knative TOC meeting notes are viewable by anyone who joins the Istio and Knative Google Group (with the click of a button). That's the same for all technical design documents.
Oh, yeah, I'm in the Knative Google group myself and so didn't even notice there was a barrier.
+1 to making the CF TOC notes journal public, and to making sure that is stated explicitly in the committee mechanics section. Currently it says the meeting notes will be "published" but is not specific about the openness of access to that document.
I noticed that I don't have access to read the meeting notes linked to from the Istio or the Knative TOC descriptions. It made me wonder why those notes are not publicly viewable. In the interest of transparency, they seem like an artifact we'd want the whole community to be able to read.
My initial opinion is that we should clarify that the meeting notes from the TOC should be viewable by all. It's possible there's some nuance I'm missing here that led Knative and Istio to decide to make their TOC notes private, and I'm curious to hear whether folks have reasons to support that decision.
The text was updated successfully, but these errors were encountered: