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
This handbook outlines expectations and responsibilities for Blog coordinator as well as Contributor Comms team members who wish to contribute to blogging activities.
3
+
This handbook outlines expectations and responsibilities for Blog
4
+
coordinator as well as Contributor Comms team members who wish to
5
+
contribute to blogging activities.
4
6
5
-
Writing and sharing articles is one of the ways through which Kubernetes contributors add to the community, and the Blog Coordinator role exists to
7
+
Writing and sharing articles is one of the ways through which
8
+
Kubernetes contributors add to the community, and the Blog Coordinator
9
+
role exists to
6
10
7
11
1. Serve as an initial point of contact for content suggestions
8
12
2. Help contributors to navigate the existing publishing processes
9
13
3. Assist in determining the final publishing targets of the content.
10
-
4. Coordinate with SIG-Docs in the publishing process, namely by following and improving the Blogging Guidelines.
11
-
5. Coordinate with the rest of the Contributor Comms team, and specifically the Social Media Coordinator, in the best ways to broaden external awareness of published content.
12
-
13
-
The [Kubernetes Contributor Blog](https://www.kubernetes.dev/blog/) is one of the most direct points of entry for those that want to share with a wider audience. The role of the Blog Coordinator is to guide those that want to contribute in the best way to do so, while coordinating with the rest of the team (including other Contributor Comms team members) to assign editors, reviewers and other roles to new submissions.
14
-
15
-
The Blog Coordinator has an active involvement in defining, with others, the [Blogging Guidelines](https://hackmd.io/@fsm/blog-guidelines), and should constantly seek to improve them, with an eye on the improvement of the contributor experience.
14
+
4. Coordinate with SIG-Docs in the publishing process, namely by
15
+
following and improving the Blogging Guidelines.
16
+
5. Coordinate with the rest of the Contributor Comms team, and
17
+
specifically the Social Media Coordinator, in the best ways to
18
+
broaden external awareness of published content.
19
+
20
+
The [Kubernetes Contributor Blog](https://www.kubernetes.dev/blog/) is
21
+
one of the most direct points of entry for those that want to share
22
+
with a wider audience. The role of the Blog Coordinator is to guide
23
+
those that want to contribute in the best way to do so, while
24
+
coordinating with the rest of the team (including other Contributor
25
+
Comms team members) to assign editors, reviewers and other roles to
26
+
new submissions.
27
+
28
+
The Blog Coordinator has an active involvement in defining, with
29
+
others, the [Blogging
30
+
Guidelines](https://hackmd.io/@fsm/blog-guidelines), and should
31
+
constantly seek to improve them, with an eye on the improvement of the
32
+
contributor experience.
16
33
17
34
18
35
### Minimum Skills and Requirements
19
36
20
37
Those in this role should ideally:
21
38
22
-
* Be a member of the [Kubernetes GitHub Org](https://github.com/kubernetes/)
23
-
* Have some familiarity with blogging platforms and editing tools; specific knowledge of Markdown, GitHub and Hugo is a plus.
24
-
* Be available to either attend regular Contributor Comms meetings or collaborate asynchronously via the #sig-contribex-comms channel in the Kubernetes Slack
39
+
* Be a member of the [Kubernetes GitHub
40
+
Org](https://github.com/kubernetes/)
41
+
* Have some familiarity with blogging platforms and editing tools;
42
+
specific knowledge of Markdown and Hugo is a plus.
43
+
* Have some familiarity with Git and GitHub-based workflows; these are
44
+
extensively used in the Kubernetes project, and specifically in both
45
+
the contributor site and the main website.
46
+
* Be available to either attend regular Contributor Comms meetings or
47
+
collaborate asynchronously via the #sig-contribex-comms channel in
48
+
the Kubernetes Slack.
49
+
* Have reasonable working knowledge of English, particularly in the
50
+
written form.
51
+
* Have an interest in interacting with others; blogging is almost
52
+
always a group effort that involves working with authors to achieve
53
+
a commonly agreed result.
25
54
26
55
#### Expected time commitment
27
56
@@ -31,18 +60,69 @@ Those in this role should ideally:
31
60
### General Expectations
32
61
33
62
1. Be ready to help those wanting to contribute to the blogs.
34
-
2. Understand the Blogging Guidelines and assist contributors in following them.
35
-
3. Help in determining applicability of the proposed content, with the rest of the team: this includes discussion in the Slack channel or regular meeting.
63
+
2. Understand the Blogging Guidelines and assist contributors in
64
+
following them.
65
+
3. Help in determining applicability of the proposed content, with the
66
+
rest of the team: this includes discussion in the Slack channel or
67
+
regular meeting.
36
68
4. Identify team members that can review blog submissions.
37
-
5. Discuss with SIG-Docs, when needed, for possible publication in the main Kubernetes site.
69
+
5. Discuss with SIG-Docs, when needed, for possible publication in the
70
+
main Kubernetes site.
38
71
6. Review blog submissions.
39
-
7. Open the blog submission PR (with the author as Co-author), or find someone that can assist in this tasks within the Contributor Comms team.
72
+
7. Open the blog submission PR (with the author as Co-author), or find
73
+
someone that can assist in this tasks within the Contributor Comms
74
+
team.
40
75
8. Follow up submitted PRs and help with the approval process.
41
76
42
77
### Associates Overview (Shadow)
43
78
44
-
Team members who which to become Blogging Leads should express their desire to the current lead; leads should work with shadows to understand their capacity to take on the needs of the lead role and work with the shadow on a plan to take on responsibility, including:
45
-
46
-
* Become a reviewer of new submitted content.
47
-
* Open the PRs and follow them through.
48
-
* Provide assistance to new contributors that are asking how to submit content.
79
+
#### Description and eligibility
80
+
81
+
Anyone that is interested in helping the blogging team, and that
82
+
finds the general expectations and requirements acceptable, can start
83
+
working in the team and have their contributions to the project
84
+
recognised. Additionally, some will feel that they want to make a step
85
+
towards becoming Blogging Leads themselves.
86
+
87
+
Becoming a shadow is something that should come as a result of
88
+
existing involvement in the team, and not as a starting point; to be
89
+
eligible to shadow for this role you will need to:
90
+
91
+
* Be a regular member of the Comms team, by following the
92
+
activities and the regular meetings.
93
+
* Have demonstrated knowledge of the blogging process and guidelines,
94
+
namely by having been actively involved in the publishing process of
95
+
articles.
96
+
97
+
Team members who want to become Blogging Leads _should express their
98
+
desire to the current lead_; leads should work with shadows to
99
+
understand their capacity to take on the needs of the lead role and
100
+
work with the shadow on a plan to take on the necessary
101
+
responsibility.
102
+
103
+
#### Expected contributions
104
+
105
+
Some of the identified requirements for blogging shadows are:
106
+
107
+
***Become a reviewer of new submitted content**, by leading communication
108
+
with content creators and guiding them through the publishing
109
+
process.
110
+
***Open the PRs and follow them through**, helping content creators
111
+
in the more processual aspects of publishing, keeping them informed
112
+
of the necessary steps and following the process untul completion.
113
+
***Provide assistance to new contributors that are asking how to
114
+
submit content**, by monitoring the Slack channel, Github, and other
115
+
sources.
116
+
***Make status updates in the SIG Contribex Comms meetings**, keeping
117
+
the status of the relevant projects up-to-date (e.g., in the project
118
+
board) and having a broad understanding of the different ongoing tasks.
119
+
120
+
This requirements are aligned with the general expectations described
121
+
above, but in the context of shadowing they follow a more structured
122
+
approach. The acting Blogging Lead will discuss the steps that need to
123
+
be taken to make the shadowing programme helpful and achieve the desired result.
124
+
125
+
Changes in roles are done by the SIG Contribex Comms subproject team
126
+
based on different inputs and needs, but having shadows that are ready
127
+
to assume a leading position is an important part of what makes it
0 commit comments