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
SIG and Working Group Mailing lists should have the [Mailing list owners] as
42
-
co-owners to the list so that administrative functions can be managed centrally
43
-
across the project.
57
+
SIG, Working Group, and subproject mailing lists should have the
58
+
[mailing list owners] as co-owners to the list so that administrative functions
59
+
can be managed centrally across the project.
44
60
45
-
Moderation of the SIG/WG lists is up to that individual SIG/WG. The admins
46
-
are there to help facilitate leadership changes, or various other administrative
47
-
functions.
61
+
Moderation of the SIG/WG/subproject lists is up to that individual
62
+
SIG/WG/subproject. The admins are there to help facilitate leadership changes,
63
+
or various other administrative functions.
48
64
49
65
Users who are violating the [Code of Conduct] or other negative activities
50
66
(like spamming) should be moderated.
51
67
-[Lock the thread immediately] so that people cannot reply to the thread.
52
68
-[Delete the post].
53
69
- In some cases you might need to ban a user from the group, follow
54
-
[these instructions] on how stop a member from being able to post to the group.
70
+
[these instructions] on how stop a member from being able to post to the
71
+
group.
55
72
For more technical help on how to use Google Groups, check the [Groups Help]
56
73
page.
57
74
@@ -64,50 +81,60 @@ Moderators should adhere to the general Kubernetes project
64
81
65
82
#### New user posting queue
66
83
67
-
New members who post to the Mailing list will automatically have their messages
84
+
New members who post to the mailing list will automatically have their messages
68
85
put in the [moderation queue]. Moderators of the list will receive a
69
86
notification of their message and should process them accordingly.
70
87
71
88
72
89
#### Annual permissions review
73
90
74
-
SIGand WG Moderators must establish an annual review of their Mailing lists
75
-
to ensure their Moderator list is current and includes [Mailing List owners].
76
-
Many of the SIG and WG Mailing lists pre-date current communication policy and
77
-
an annual review ensures ownership is up to date.
91
+
SIG, WG, and subproject Moderators must establish an annual review of their
92
+
mailing lists to ensure their Moderator list is current and includes
93
+
[mailing list owners]. Many of the SIG and WG mailing lists pre-date current
94
+
communication policy and an annual review ensures ownership is up to date.
78
95
79
96
This review does not need to occur at a specific recurring date and can be
80
-
combined with other actions such as SIG/WG leadership changes or sub-project
81
-
additions.
97
+
combined with other actions such as SIG/WG/subproject leadership changes or
98
+
sub-project additions.
82
99
83
100
84
101
---
85
102
86
103
## Mailing list creation
87
104
88
-
All SIGs and WGs need two discussion groups: one for leads/chairs, and one for members.
105
+
All SIGs and WGs require two discussion groups: one for leads/chairs, and one
106
+
for members. Subprojects that opt to have a mailing list only require one for
107
+
members.
89
108
90
-
### Prerequisites
109
+
### Prerequisites for creating a mailing list
91
110
92
-
- An email account that can create google groups and add members external to your organization to a google group mailing list. **This might not be possible with your employer's email account**. You might need to use a personal email account.
93
-
- At least 3 mailing list owners (leads), in addition to [email protected]
94
-
- Familiarity with the [moderation guidelines] for the project and [moderation queue]s. Chairs should be cognizant that a new group will require
111
+
- An email account that can create Google Groups and add members external to
112
+
your organization to a Google Group mailing list. **This might not be possible
113
+
with your employer's email account**. You might need to use a personal email
114
+
account.
115
+
- At least 3 mailing list owners (leads), in addition to
> **Note:** You can add new owners to a mailing list at any time in the **People > Members** screen.
156
+
> **Note:** You can add new owners to a mailing list at any time in the
157
+
**People > Members** screen.
130
158
131
159
Leave all other fields as-is. Click **Next.**
132
160
133
-
4. Once the group is created, navigate to your group in the Google Groups UI and go to **Group settings** to continue setting up permissions. Set the following settings:
161
+
4. Once the group is created, navigate to your group in the Google Groups UI and
162
+
go to **Group settings** to continue setting up permissions. Set the following
163
+
settings:
134
164
135
165
**Member Privacy**
136
166
@@ -154,7 +184,7 @@ an initial time investment moderation-wise as the group establishes itself.
|**Email footer**| Include the standard Groups footer | Include the standard Groups footer |
159
189
|**Group email language**| English (or your group's default language) | English (or your group's default language) |
160
190
@@ -166,42 +196,51 @@ an initial time investment moderation-wise as the group establishes itself.
166
196
| **Who can adjust roles** | Group managers | Group managers
167
197
168
198
5. Click **Save changes**.
199
+
Once your mailing list is created, it should also be added to the [sigs.yaml]
200
+
file. For subprojects, it should be added like:
201
+
```yaml
202
+
- name: Foo
203
+
contact:
204
+
mailing_list: [link to Google Group]
205
+
```
169
206
170
-
171
-
172
-
173
-
174
207
## Set up shared calendars and meeting with a mailing list
175
208
176
209
Once you've set up your SIG/WG mailing list, you'll need to:
177
210
- Share a calendar with meeting invites on it with the mailing list
178
211
- Share a meeting notes google doc with the mailing list
179
212
180
-
### Prerequisites
213
+
### Prerequisites for sharing a calendar and meeting notes
181
214
182
-
- A member's google group.
215
+
- A member's Google Group.
183
216
- A shared calendar.
184
-
> **Note:** Like with mailing lists, your organization's permissions might not let you share calendars with the correct permissions. You might need to use a personal email address.
217
+
> **Note:** Like with mailing lists, your organization's permissions might not
218
+
let you share calendars with the correct permissions. You might need to use a
219
+
personal email address.
185
220
186
-
### Sharing the calendar with the google group
221
+
### Sharing the calendar with the Google Group
187
222
188
223
You must share the meeting calendar with the following people:
> **Note:** You need to add the member's mailing list as a guest to any meeting invites on the shared calendar for an invite to be sent to members of the group.
240
+
> **Note:** You need to add the member's mailing list as a guest to any meeting
241
+
invites on the shared calendar for an invite to be sent to members of the group.
203
242
204
-
## Sharing the meeting notes with the google group
243
+
### Sharing the meeting notes with the Google Group
205
244
206
245
- Create and share your _"meeting notes"_ Google doc with the following
207
246
permissions settings:
@@ -212,7 +251,7 @@ You must share the meeting calendar with the following people:
212
251
document should be copied over to an account without the restriction and
213
252
include the owner reference at the top of the document.
214
253
215
-
###Archive a mailing list
254
+
## Archive a mailing list
216
255
217
256
To archive a mailing list, use the below procedure.
218
257
@@ -249,4 +288,5 @@ To archive a mailing list, use the below procedure.
249
288
[lock the thread immediately]: https://support.google.com/groups/answer/2466386?hl=en#
250
289
[delete the post]: https://support.google.com/groups/answer/1046523?hl=en
0 commit comments