-
Notifications
You must be signed in to change notification settings - Fork 162
added wg-policy-spotlight blog #534
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Welcome @arujjval! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about moving the answers to the questions onto a new line to improve readability?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was going through this again and found some nits :)
Co-authored-by: Arvind <[email protected]>
Co-authored-by: Arvind <[email protected]>
@ArvindParekh updated as per your comments. |
Please update the date. After that, I'll lgtm and approve and we'll get this published. |
/hold We'd usually mirror this kind of article to the main blog. Are we happy to hold off to allow for that? OK to unhold if we don't want mirroring. |
Yes, we should mirror (thank you, vacation brain is real). |
Do we need to do anything in particular for the mirroring? @arujjval we need to get a new publish date for this, right? |
Needs a contributor to open a k/website PR that mirrors this one. |
Ping, any updates here @arujjval? Help needed? |
@kaslin been a little busy lately. Have we decided on which date this should be posted? |
I suggest aiming for publication in late February, because SIG Docs is struggling with blog team capacity (it's mostly me). |
@sftim sure. Please update me about the day chosen. I will make changes to the publication date. |
@arujjval checking in on this. Looks like there are some comments to address. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@arujjval great piece!
I reviewed the article and left some comments about formatting and improving readibility.
@graz-dev for reported speech, we don't suggest rewordings unless there are obvious problems or we think the original speaker may have been misquoted. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just some minor cleanup. Also, please edit per @graz-dev review comments as well.
@graz-dev good work on copy-edit review! |
Sorry for the delay. I have made changes as per the suggestions above. |
@arujjval You have a publishing date! Check out the new edits and approve them so this can go out on time. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The key thing I hope we get right is to mark this as a draft, because that fits with how the blog team (for the main blog) plan to work.
See https://github.com/kubernetes/contributor-site/pull/534/files#r2094645018
However, I also suggested a few little tweaks that I think are worth making.
@sftim, all your suggested changes have been made. |
Looks good to merge as draft. Thanks for the work that went into this. I'll also get it scheduled & published. /LGTM |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: arujjval, bashlion, jberkus, lmktfy 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 |
Looks like this is good to go whenever we're ready to release the hold. Here's a reminder that this exists in case that's useful. Thank you all for your work on this! @sftim |
closes #533