Add contribex-comms blog shadow guide #7890
Conversation
Correcting grammar and avoiding repetition of same word in a line.
Update blogging-shadow-guide.md
k8s-ci-robot
added
the
cncf-cla: yes
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fsmunoz 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 |
k8s-ci-robot
added
the
approved
k8s-ci-robot
added
area/community-management
size/M
|
/area contributor-comms |
communication/contributor-comms/blogging-resources/blogging-shadow-guide.md
Outdated
Show resolved
Hide resolved
…adow-guide.md Co-authored-by: Arvind <[email protected]>
|
/lgtm |
k8s-ci-robot
added
the
lgtm
|
/hold |
k8s-ci-robot
added
the
do-not-merge/hold
|
Added a hold because I realized it already has the approved label, since it was created by a lead with approver privileges. Soft requirement on the additional lgtm, but I think it would be good to have. |
There was a problem hiding this comment.
Would love to hear from current shadows if this content seems helpful to them.
It does! I gave the article a read again as a new contributor and I found some areas that could benefit from a little more information. Would love to hear your thoughts about it.
Just a few suggestions, let me know if they're helpful or not, and I'd be happy to go ahead and add the additional lgtm @kaslin :)
|
|
||
| * Knowledge of git and GitHub (issues, PRs, reviews, merges, etc) | ||
| * Knowledge of the existing blogging standards, including the ones | ||
| external to SIG Contribex Comms (like the SIG Docs standards) |
There was a problem hiding this comment.
| external to SIG Contribex Comms (like the SIG Docs standards) | |
| external to SIG Contribex Comms (like the [SIG Docs standards](https://kubernetes.io/docs/contribute/style/style-guide/)) |
New contributors might not know about the existing blogging standards. Should we add a link here to the Documentation style guide?
Also, are there any other blogging standards that I'm not aware of?
|
|
||
| In terms of time requirements, this is a very flexible programme since | ||
| writing articles is something that can be done asynchronously. The | ||
| following provides a minimal guideline: |
There was a problem hiding this comment.
Probably a nit, but should we mention that the mentioned time requirements are on a per week basis?
| involvement: | ||
|
|
||
| * Write an interview script. | ||
| * Open an Issue and a PR. |
There was a problem hiding this comment.
While giving this a read, it sounded a bit unclear.
| * Open an Issue and a PR. | |
| * Open an Issue and a PR to publish the completed article. |
| * Carry an article from inception to publication, updating the project | ||
| board and Slack channel. |
There was a problem hiding this comment.
First-timers could misinterpret this as updating the Slack channel in some way. I know we mean keeping the SIG informed about the progress on Slack, and it's probably a nit, but putting it out there to see if it's confusing to someone else too. If not, totally good to go 👍🏻
Initial version of the Contribex Comms blogging shadowing guide.
Fixes #7875