<commit_before># Mailing list guidelines

The Kubernetes Mailing list or Google Groups functions as the primary means of
asynchronous communication for the project's
[Special Interest Groups (SIG)][sig-list] and [Working Groups (WG)][sig-list].

### ATTENTION: SIG/WG Mailing list owners

If you are currently a moderator of a SIG or WG Mailing List. See the new policy
requirements here:

- [Mailing list annual review](#annual-permissions-review)
- [Mailing list moderation queue](#new-user-posting-queue)
  - [Creating moderation queue](#create-moderation-queue)


## Code of conduct

The Kubernetes project adheres to the community [Code of Conduct] throughout all
platforms and includes all communication mediums.

## Admins

Check the [centralized list of administrators][admins] for contact information.

To connect: Reach out to one of the listed moderators,[Mailing list owners],
the [sig contributor experience Mailing list] or the `#sig-contribex` slack
channel.

### Mailing list owners

Mailing list owners should include the Chairs for your [SIG or WG][sig-list] and
the below contacts:

- <EMAIL>

---

## Moderation

SIG and Working Group Mailing lists should have the [Mailing list owners] as
co-owners to the list so that administrative functions can be managed centrally
across the project.

Moderation of the SIG/WG lists is up to that individual SIG/WG. The admins
are there to help facilitate leadership changes, or various other administrative
functions.

Users who are violating the [Code of Conduct] or other negative activities
(like spamming) should be moderated.
- [Lock the thread immediately] so that people cannot reply to the thread.
- [Delete the post].
- In some cases you might need to ban a user from the group, follow
  [these instructions] on how stop a member from being able to post to the group.
  For more technical help on how to use Google Groups, check the [Groups Help]
  page.


### Moderator expectations and guidelines

Moderators should adhere to the general Kubernetes project
[moderation guidelines].


#### New user posting queue

New members who post to the Mailing list will automatically have their messages
put in the [moderation queue]. Moderators of the list will receive a
notification of their message and should process them accordingly.


#### Annual permissions review

SIG and WG Moderators must establish an annual review of their Mailing lists
to ensure their Moderator list is current and includes [Mailing List owners].
Many of the SIG and WG Mailing lists pre-date current communication policy and
an annual review ensures ownership is up to date.

This review does not need to occur at a specific recurring date and can be
combined with other actions such as SIG/WG leadership changes or sub-project
additions.


---

## Mailing list creation

Create a Google Group at https://groups.google.com/forum/#!creategroup,
following the below procedure:
- Each SIG must have two discussion groups with the following settings.
  - `kubernetes-sig-<foo>` (the discussion group):
    - Group type: Email list
    - Group visibility: Anyone on the web
    - View topics: Anyone on the web
    - Post: Owners of the group, Managers of the group, All members of the group. Ensure that "Anyone on the web" is NOT selected here. 
    - Join the group: Anyone can ask
  - `kubernetes-sig-<foo>-leads` (list for the leads, to be used with Zoom and
    Calendars)
    - Group type: Email list
    - Group visibility: All members of the group
    - View topics: All members of the group
    - Post: Owners of the group, Managers of the group, All members of the group. Ensure that "Anyone on the web" is NOT selected here. 
    - Join the group: Only invited users
    
- Groups should be created as e-mail lists with at least three owners and must
  include the [Mailing list owners](#mailing-list-owners).
-  To add the owners, visit the **Group Settings** (drop-down menu on the right
   side), select **Members**, then **Direct Add Members** on the left side and add them via their email address (with a suitable welcome message). Do NOT forget to invite <EMAIL> in addition to your leads.
- In **Members/All Members** select the [Mailing list owners] and assign them<commit_msg>Update mailing list permissions guidelines<commit_after># Mailing list guidelines

The Kubernetes Mailing list or Google Groups functions as the primary means of
asynchronous communication for the project's
[Special Interest Groups (SIG)][sig-list] and [Working Groups (WG)][sig-list].

### ATTENTION: SIG/WG Mailing list owners

If you are currently a moderator of a SIG or WG Mailing List. See the new policy
requirements here:

- [Mailing list annual review](#annual-permissions-review)
- [Mailing list moderation queue](#new-user-posting-queue)
  - [Creating moderation queue](#create-moderation-queue)


## Code of conduct

The Kubernetes project adheres to the community [Code of Conduct] throughout all
platforms and includes all communication mediums.

## Admins

Check the [centralized list of administrators][admins] for contact information.

To connect: Reach out to one of the listed moderators,[Mailing list owners],
the [sig contributor experience Mailing list] or the `#sig-contribex` slack
channel.

### Mailing list owners

Mailing list owners should include the Chairs for your [SIG or WG][sig-list] and
the below contacts:

- <EMAIL>

---

## Moderation

SIG and Working Group Mailing lists should have the [Mailing list owners] as
co-owners to the list so that administrative functions can be managed centrally
across the project.

Moderation of the SIG/WG lists is up to that individual SIG/WG. The admins
are there to help facilitate leadership changes, or various other administrative
functions.

Users who are violating the [Code of Conduct] or other negative activities
(like spamming) should be moderated.
- [Lock the thread immediately] so that people cannot reply to the thread.
- [Delete the post].
- In some cases you might need to ban a user from the group, follow
  [these instructions] on how stop a member from being able to post to the group.
  For more technical help on how to use Google Groups, check the [Groups Help]
  page.


### Moderator expectations and guidelines

Moderators should adhere to the general Kubernetes project
[moderation guidelines].


#### New user posting queue

New members who post to the Mailing list will automatically have their messages
put in the [moderation queue]. Moderators of the list will receive a
notification of their message and should process them accordingly.


#### Annual permissions review

SIG and WG Moderators must establish an annual review of their Mailing lists
to ensure their Moderator list is current and includes [Mailing List owners].
Many of the SIG and WG Mailing lists pre-date current communication policy and
an annual review ensures ownership is up to date.

This review does not need to occur at a specific recurring date and can be
combined with other actions such as SIG/WG leadership changes or sub-project
additions.


---

## Mailing list creation

Create a Google Group at https://groups.google.com/forum/#!creategroup,
following the below procedure:
- Each SIG must have two discussion groups with the following settings.
  - `kubernetes-sig-<foo>` (the discussion group):
    - Group type: Email list
    - Group visibility: Anyone on the web
    - View topics: Anyone on the web
    - Post: Owners of the group, Managers of the group, All members of the group. Ensure that "Anyone on the web" is NOT selected here. 
    - Join the group: Anyone on the web
  - `kubernetes-sig-<foo>-leads` (list for the leads, to be used with Zoom and
    Calendars)
    - Group type: Email list
    - Group visibility: All members of the group
    - View topics: All members of the group
    - Post: Owners of the group, Managers of the group, All members of the group. Ensure that "Anyone on the web" is NOT selected here. 
    - Join the group: Only invited users
    
- Groups should be created as e-mail lists with at least three owners and must
  include the [Mailing list owners](#mailing-list-owners).
-  To add the owners, visit the **Group Settings** (drop-down menu on the right
   side), select **Members**, then **Direct Add Members** on the left side and add them via their email address (with a suitable welcome message). Do NOT forget to invite <EMAIL> in addition to your leads.
- In **Members/All Members** select the [Mailing list owners] and assign them
{'fraction_non_alphanumeric': 0.062103034580098804, 'fraction_numerical': 0.0, 'mean_word_length': 4.0855263157894735, 'pattern_counts': {'":': 0, '<': 11, '<?xml version=': 0, '>': 11, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3734478', 'n_tokens_mistral': 2247, 'n_tokens_neox': 2139, 'n_words': 1224}