cncf
/
toc
mirror of https://github.com/cncf/toc.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

* updating with feedback from @dims 

Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>
This commit is contained in:
Emily Fox 2024-01-03 17:01:45 -05:00
parent beeef4c7b7
commit ea9572850e
Failed to extract signature
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
operations/onboarding.md
View File

@ -88,7 +88,7 @@ The TOC primarily votes in one of two mechanisms, gitvote or on the mailing list
## Lobbying and Direct Messages
Historically, the TOC has had a problem with “lobbying”, e.g. a project approaching individual TOC members for feedback / comment, often moving on to another TOC member if they didn’t get the answer they wanted. This was particularly true for the old Sandbox model and was a key reason for changing from sponsorship to a voting model. With this in mind, TOC members should disclose to the rest of the TOC if they have been approached by a project or individual within the community. It is acceptable and expected that projects or community members will reach out to the TOC for advice, however to maintain consistency in expectations, *all TOC members should be made aware of those discussions, with the opportunity to provide additional information or recommendations*. This ensures the TOC maintains a strong, clear voice to our technical communtiy, consistent with our processes, [values](https://github.com/cncf/foundation/blob/main/charter.md#3-values), [principles](../PRINCIPLES.md), and the Charter.
Historically, the TOC has had a problem with “lobbying”, e.g. a project approaching individual TOC members for feedback / comment, often moving on to another TOC member if they didn’t get the answer they wanted. This was particularly true for the old Sandbox model and was a key reason for changing from sponsorship to a voting model. With this in mind, TOC members should disclose to the rest of the TOC if they have been approached by a project or individual within the community or have any hard or soft conflicts of interest. It is acceptable and expected that projects or community members will reach out to the TOC for advice, however to maintain consistency in expectations, *all TOC members should be made aware of those discussions, with the opportunity to provide additional information or recommendations*. This ensures the TOC maintains a strong, clear voice to our technical communtiy, consistent with our processes, [values](https://github.com/cncf/foundation/blob/main/charter.md#3-values), [principles](../PRINCIPLES.md), and the Charter.
As the TOC continues to work through updating our documentation on the repo, older references to "seeking sponsorship" may result in projects reaching out to TOC members directly to "sponsor" their project for moving levels. When this occurs, kindly direct them to the Moving Levels resources which details how projects are recommended for promotion to the next level. The TOC strives to pick up projects from the backlog in the order which they are recommended for promotion, while balancing alignment of TOC member expertise, liaisoning assignment, and availability of our members.

2
operations/toc-chair.md
View File

@ -14,7 +14,7 @@ The Chair is expected to perform a variety of functions and can often be thought
* Coordinate TOC activities
* Ensure Liaisons are assigned and engaged for each TAG
* Coordinate overarching TAG activities
* Represent the TOC to the Governing Board
* Serve on the Governing Board in the TOC Seat and represent the TOC to the Governing Board
* Co-present CNCF technical strategy at Governing Board strategy sessions
* Support onboarding new TOC members as needed
* Ensure notes and actions are documented and issued for TOC meetings with follow-up