[WIP] Propose updates to the SIG ContribEx Charter #3526
Conversation
- Explicitly add Kubernetes Gsuite as a responsibility - Explicitly add CNCF as the lead owner of Zoom, YouTube, and Slack accounts - Begin to document responsibilities around contributor summits between this SIG and the CNCF - Explicitly remove moderation of social properties as a responsility - Explicitly remove closing down working groups as a responsibility - Explicitly remove SIG Calendar, lists, YouTube playlists, and Zoom settings as a responsibility Signed-off-by: Jorge O. Castro <jorgec@vmware.com>
k8s-ci-robot
added
do-not-merge/work-in-progress
| @@ -76,14 +70,29 @@ CNCF in many of the noted cases above, contributes funding to our platforms, pro | |||
| - Code for the testing and CI infrastructure - that’s SIG Testing | |||
| - [kubernetes/community] ownership of folders for KEPs and Design Proposals. Members are to follow those folders owners files and SIG leadership for the specific issue/PR in question. | |||
| - User community management. We hold office hours because contributors are a large portion of the volunteers that run that program. | |||
| - Slack or YouTube moderation (This should be a new SIG or another group) | |||
There was a problem hiding this comment.
@michelleN @philips - We should delegate explicit ownership & mgmt to a CNCF group.
/hold
for steering feedback to make certain we fine ownership of these things.
There was a problem hiding this comment.
our youtube channel is primarily contributor use though and will be happy to have it stay with us - we also stream and would be a roadblock to have another owner here
slack is not contributor majority and should indeed be owned by another body
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: castrojo, timothysc The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
| - [discuss.kubernetes.io] | ||
| - [GitHub Management] | ||
| - [Mailing lists] / Google groups for the project as a whole (eg: kubernetes-dev@googlegroups.com) and for individual sigs and wgs where the Chairs have provided us ownership | ||
| - [Slack] |
There was a problem hiding this comment.
slack is definitely out of our scope but no one wants to own it
| - [Zoom] | ||
| - Establish and staff teams responsible for the administration and moderation of these platforms | ||
| - Teams must be staffed by trusted contributors spanning time zones, see [moderation] for more detail | ||
| - They are authorized to take immediate action when dealing with code of conduct issues, see [moderators] for the full list |
There was a problem hiding this comment.
this should stay - whatever platforms we decide we own, they should be staffed and take action
There was a problem hiding this comment.
This seems like Jorge is proposing that Contribex not be responsible for ANY of the platforms.
| @@ -12,21 +12,15 @@ We do this by listening - whether it’s through our roadshows to SIG meetings, | |||
|
|
|||
| #### Code, Binaries and Services | |||
|
|
|||
| - Establish policies, standards and procedures for the use, [moderation], and management of all public platforms officially used by the project, including but not limited to: | |||
There was a problem hiding this comment.
any platform that contributors are the majority, we should have operational responsibilities
There was a problem hiding this comment.
these are the transparency tools of the project that steering works out in governance docs and should have operational responsibility with contributor experience. in the case where users are the majority, there needs to be some shared ownership, if not complete control and operational responsibility changed to them.
There was a problem hiding this comment.
them = a body that has end user community at its mission
| - Maintenance of the Kubernetes Gsuite | ||
| - Managing @kubernetes.io aliases for project usage | ||
| - Managing the Kubernetes Community Calendar | ||
| - Content and Format of the [Contributor Summit(s)] |
There was a problem hiding this comment.
and running the meetings and providing project management
| @@ -76,14 +70,29 @@ CNCF in many of the noted cases above, contributes funding to our platforms, pro | |||
| - Code for the testing and CI infrastructure - that’s SIG Testing | |||
| - [kubernetes/community] ownership of folders for KEPs and Design Proposals. Members are to follow those folders owners files and SIG leadership for the specific issue/PR in question. | |||
| - User community management. We hold office hours because contributors are a large portion of the volunteers that run that program. | |||
| - Slack or YouTube moderation (This should be a new SIG or another group) | |||
There was a problem hiding this comment.
our youtube channel is primarily contributor use though and will be happy to have it stay with us - we also stream and would be a roadblock to have another owner here
slack is not contributor majority and should indeed be owned by another body
| - We are not the [code of conduct committee] and therefore do not control incident management reporting or decisions; however, our moderation guidelines allow us to act swiftly if there is a clear violation of terms of either our code of conduct or one of our supported platforms terms of service. If there is an action that the committee needs to take that involves one of these platforms (example: the removal of someone from GitHub), we will carry that out if none of the committee members have access. | ||
| - SIG Properties | ||
| - SIG Calendars and their settings |
There was a problem hiding this comment.
we are responsible for the upkeep of the shared calendar and making sure that is working
There was a problem hiding this comment.
we also advise on settings and best practices in order to display on shared calendar or wherever
| - We are not the [code of conduct committee] and therefore do not control incident management reporting or decisions; however, our moderation guidelines allow us to act swiftly if there is a clear violation of terms of either our code of conduct or one of our supported platforms terms of service. If there is an action that the committee needs to take that involves one of these platforms (example: the removal of someone from GitHub), we will carry that out if none of the committee members have access. | ||
| - SIG Properties | ||
| - SIG Calendars and their settings | ||
| - SIG Mailing List permissions, moderation, and maintenance |
There was a problem hiding this comment.
we advise on this and come up with guidelines
| - SIG Calendars and their settings | ||
| - SIG Mailing List permissions, moderation, and maintenance | ||
| - SIG YouTube playlist videos | ||
| - SIG settings on their Zoom account |
There was a problem hiding this comment.
we advise and set up guidelines
| - SIG Properties | ||
| - SIG Calendars and their settings | ||
| - SIG Mailing List permissions, moderation, and maintenance | ||
| - SIG YouTube playlist videos |
There was a problem hiding this comment.
we advise and set up guidelines
for ownership, moderation, and administration. Signed-off-by: Jorge O. Castro <jorgec@vmware.com>
|
@parispittman ok PTAL, I've restructured it so we explicitly split setting policy (which should be contribex) and then the list of all the properties, and then having the matching list in the out-of-scope section. |
|
I beleive this should cover most of your comments where ContribEx should have policy control of the properties. |
order of importance Signed-off-by: Jorge O. Castro <jorgec@vmware.com>
| @@ -1,51 +1,45 @@ | |||
| # Contributor Experience Special Interest Group Charter | |||
|
|
|||
| This charter adheres to the conventions described in the [Kubernetes Charter README] and uses the Roles and Organization Management outlined in [sig-governance]. | |||
There was a problem hiding this comment.
why did you remove this? this is a part of the charter template.
There was a problem hiding this comment.
agree with @parispittman's comment
| - User community management. We hold office hours because contributors are a large portion of the volunteers that run that program. | ||
| - The contributor experience for repos not included in the Kubernetes associated repositories list found in the [GitHub Management] subproject README. | ||
| - Steering committee election policy updates and maintenance. | ||
| - [kubernetes/community] Members are to follow those folders owners files and SIG leadership for the specific issue/PR in question. |
There was a problem hiding this comment.
what is those folders?
There was a problem hiding this comment.
The original text has "kubernetes/community ownership of folders for KEPs and Design Proposals. Members are to follow those folders owners files and SIG leadership for the specific issue/PR in question." but neither KEPs or Designs Proposals live in k/community anymore. Perhaps I should just cut out the entire bullet?
There was a problem hiding this comment.
Design proposals technically still live in k/community. They haven't been migrated to k/enhancements yet, but that is the intended home AFAIK.
There was a problem hiding this comment.
The intention of this is describing the fact that we own the repo as a whole, and the operational processes around the repo, but we delegate certain subfolders to other sigs/parts of the project. For example, we own the sig docs generator and the root, but we don't own the steering committee folder, or the the various sig folders. If we delegate it, we don't own it.
| - [Group Mentoring - WIP] | ||
| - [The 1:1 Hour - WIP] | ||
| - Speed Mentoring sessions at selected KubeCon/CloundNativeCon's | ||
| - Help onboard new and current contributors into the culture, workflow, and CI of our contributor experience through the [contributor guide], other related documentation, [contributor summits] and programs tailored to onboarding. |
| - [The 1:1 Hour - WIP] | ||
| - Speed Mentoring sessions at selected KubeCon/CloundNativeCon's | ||
| - Help onboard new and current contributors into the culture, workflow, and CI of our contributor experience through the [contributor guide], other related documentation, [contributor summits] and programs tailored to onboarding. | ||
| - Perform issue triage on and maintain the [kubernetes/community] repository. |
| - Perform issue triage on and maintain the [kubernetes/community] repository. | ||
| - Help SIGs with being as transparent and open as possible through creating best practices, guidelines, and general administration of YouTube, Zoom, and our mailing lists where applicable | ||
| - Assist SIGs/WG Chairs and Technical Leads with organizational management operations as laid out in the [sig-governance] doc | ||
| - Distribute contributor related news on various Kubernetes channels, including Cloud Native Compute Foundation ([CNCF]) for posting blogs, social media, and other platforms as needed. |
There was a problem hiding this comment.
this seems relevant - why are we removing this?
| - Help SIGs with being as transparent and open as possible through creating best practices, guidelines, and general administration of YouTube, Zoom, and our mailing lists where applicable | ||
| - Assist SIGs/WG Chairs and Technical Leads with organizational management operations as laid out in the [sig-governance] doc | ||
| - Distribute contributor related news on various Kubernetes channels, including Cloud Native Compute Foundation ([CNCF]) for posting blogs, social media, and other platforms as needed. | ||
| - Establish and share metrics to measure project health, community health, and general trends, including: |
There was a problem hiding this comment.
For your last three comments: It shows as removed in the diff because I shuffled around the order, you have to switch to viewing the whole document to see the new order.
Signed-off-by: Jorge O. Castro <jorgec@vmware.com>
|
i brought up moving moderation to the code of conduct committee to get folks thoughts. we have a meeting next week. maybe a temp move until something else is found? unsure - wip thoughts. |
Signed-off-by: Jorge O. Castro <jorgec@vmware.com>
k8s-ci-robot
added
size/L
|
@castrojo: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
Ok I've added fixes based on the comments I've resolved so far and made it more clear where we need a new SIG instead of just "CNCF". |
|
👍 |
| @@ -1,51 +1,45 @@ | |||
| # Contributor Experience Special Interest Group Charter | |||
|
|
|||
| This charter adheres to the conventions described in the [Kubernetes Charter README] and uses the Roles and Organization Management outlined in [sig-governance]. | |||
There was a problem hiding this comment.
agree with @parispittman's comment
| - User community management. We hold office hours because contributors are a large portion of the volunteers that run that program. | ||
| - The contributor experience for repos not included in the Kubernetes associated repositories list found in the [GitHub Management] subproject README. | ||
| - Steering committee election policy updates and maintenance. | ||
| - [kubernetes/community] Members are to follow those folders owners files and SIG leadership for the specific issue/PR in question. |
There was a problem hiding this comment.
The intention of this is describing the fact that we own the repo as a whole, and the operational processes around the repo, but we delegate certain subfolders to other sigs/parts of the project. For example, we own the sig docs generator and the root, but we don't own the steering committee folder, or the the various sig folders. If we delegate it, we don't own it.
| - [discuss.kubernetes.io] | ||
| - [GitHub Management] | ||
| - [GitHub Project Organizational Management] |
|
Jorge: Can you spell out why you think we should remove each item, whether because:
It might even be helpful if we break out the big question (moderating/owning community channels) from the other incidental responsibilities (WG, calendar, youtube). Also, won't questions around mailing list ownership change if we get a community-controlled GSuite? |
|
/close After IRL discussions at kubecon we're going to table this for now. |
|
@castrojo: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This is a work in progress and needs community discussion.
Things that end up not belonging to anyone end up being owned by Contrib Ex. This is a first draft at nailing down exactly what we should be responsible for and what we should not be responsible for.
Note that this effectively removes ContribEx as the default moderator of all the kubernetes properties. The project will still need this work to get done, so where appropriate I've moved that back to the SIGs, and for everything else it will require discussion or perhaps a new community structure to manage those things.
Changes:
accounts
this SIG and the CNCF
settings as a responsibility
/hold
/sig contributor-experience