Proposing Steering Committee liaisons for the following groups:
- Code of Conduct Committee (Tim)
- Security Response Committee (Stephen)
Choosing Tim and Stephen here, because:
- they're newly-appointed SC members with a lighter liaison load
- they have served on (or [have] operate[d] in) the respective
committee's private spaces and are familiar with their processes
Signed-off-by: Stephen Augustus <foo@auggie.dev>
This is a straight rename (git mv) and addition of a tombstone link.
In the future ideally we'd use a shorturl like "transparency.k8s.io".
Signed-off-by: Tim Pepper <tpepper@vmware.com>
As CoCC collects information on an incident report it is important
that folks understand not just that this is done confidentially,
but also a little more about how it is done, eg: in which forums
and by which people.
Signed-off-by: Tim Pepper <tpepper@vmware.com>
We've added a public channel and also admin privileges within for CoCC
members. These privileges need rotated during transitions.
Signed-off-by: Tim Pepper <tpepper@vmware.com>
This updates wording in a few sections of our new incident-process
docs, adds a link to our new Slack channel in the README, and adds some
descriptions and a link to the incident-process doc to the README.
Signed-off-by: Aeva Black <806320+AevaOnline@users.noreply.github.com>
The bootstrapping document stated that the top 3 voted would get 2-year
terms and the bottom 2 would get 1-year terms.
See the bootstrap document: 3db34d4f6a/committee-code-of-conduct/bootstrapping-process.md
However when announced 2 people were stated for 2 year terms and 3 were
stated for 1 year terms. This fixes the announced result to comply with
the rules as written.
While we later said that any leak of personal information is inappropriete, this
sentence only specifically mentioned the right of privacy of the reporter. We believe
the reporter, anyone named in the report, anyone we talk to about the report, and
everyone involved should have their privacy respected. So this language is more
broad to make our intent more clear.
August 7th, 2018 was the date that we had all of the confirmations from
the members of the inaugural members of the CoCC and the welcome email
was sent.
* Update Code of Conduct page with new email
Now that we have a Code of Conduct Committee for Kubernetes, people should
contact our private email list going forward with any problems.
* Incorporate review feedback
cpanato