kubernetes
added wg-policy-spotlight blog
Welcome @arujjval!
It looks like this is your first PR to kubernetes/contributor-site 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.
You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.
You can also check if kubernetes/contributor-site has its own contribution guidelines.
You may want to refer to our testing guide if you run into trouble with your tests not passing.
If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!
Thank you, and welcome to Kubernetes. :smiley:
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.
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.
It's OK to put draft: true in front matter on these BTW.
@sftim so I have to make a similar PR at here?
Also, need to discuss the date it needs to get published.
Correct, @arujjval, that's the right place. We would want to copy it there and set the canonical URL to the contributor-site URL. In that PR for the website repo, state that reviews are taking place in the contributor-site pull request and to request edits on this PR
@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.
@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.
@arujjval You have a publishing date! Check out the new edits and approve them so this can go out on time.
@kaslin @sftim I have made changes and updated the website PR as per suggestions.
Looks good to merge as draft.
Thanks for the work that went into this. I'll also get it scheduled & published.
/LGTM /approve
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
This is painful to do, but this needs to go back to content before we publish; WG-Policy has concluded its work and disbanded, and as such this blog post needs to be edited to reflect that new status. The blog needs to turn into a retro of "this is what Policy accomplished".
@jberkus I guess the content needs to be the same, just need to do some editing on the grammar?
@jberkus & @arujjval reminder to work out how to modify this blog since the WG disbanded.
This is painful to do, but this needs to go back to content before we publish; WG-Policy has concluded its work and disbanded, and as such this blog post needs to be edited to reflect that new status. The blog needs to turn into a retro of "this is what Policy accomplished".
I have made changes according to this. So, the blog is up for review again.
/lgtm /approve
We can merge this, as an unpublished draft. Next step is to copy that updated text into a PR against k/website, and once that has merged we can set a publication date. Soon is good.
[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
- ~~OWNERS~~ [jberkus,lmktfy]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment