Closed nitishfy closed 6 months ago
Update: Ready for the next set of review.
Update: Ready for the next set of review.
There are still some unresolved suggestions. Some are open to further debate, others are about clerical errors (like the one pointed out by @sftim above) which are more straightforward - so much so that if you agree with the changes, it would be simpler in the future to accept the suggestions on GitHub since that provides an easier way to track them (not now, since they were marked out of date), and would've resolved this particular one - additionally, it updates the commit authors with those reviewing, something which is also possible when you do the final squash but doing it "by hand" is harder.
Apart from that, the images are a nice touch and I think the interview is quite interesting, so I think that with the open points resolved this is good to go, great work!
@nitishfy , I have added suggestions, one of them is due to new content, the other is to address the spelling of one word (already discussed). Please go through the open comments, there's one on the need for 100 char limit as well. All discussion points should be resolved (not necessarily changed). We're getting there though!
@nitishfy , I have added suggestions, one of them is due to new content, the other is to address the spelling of one word (already discussed). Please go through the open comments, there's one on the need for 100 char limit as well. All discussion points should be resolved (not necessarily changed). We're getting there though!
I'm afraid why doesn't the preview show this blog? :(
I'm afraid why doesn't the preview show this blog? :(
Does this preview OK locally? (run make container-server
and then visit http://localhost:1313/blog/ to see the preview)
Not sure why the changes are not getting reflected.
cc: @fsmunoz @sftim
Ready for the next set of reviews.
This PR is ready for the next set of reviews, here are a few points that I'd like to mention:
cc: @fsmunoz
@nitishfy thank you for taking care of the comments. IMO, wrapping at 100 is a guideline that when followed strictly can result in requests for change (e.g., when it breaks the markdown link syntax in different lines), so as long as the general idea of wrapping it for facilitate reviews is adopted, I don't think there is a rigid requirement for keeping everything at exactly 100. I would mark that one resolved as well.
Once the comments from https://github.com/kubernetes/contributor-site/pull/424#pullrequestreview-1774138786 are fixed, I'll get a mirror PR opened against the main Kubernetes blog.
Once the comments from #424 (review) are fixed, I'll get a mirror PR opened against the main Kubernetes blog.
we already have an ordered list in the form of questions.
we already have an ordered list in the form of questions.
Sorry, I may be missing something. That sentence doesn't make any sense to me in the context.
Can you explain what you mean @nitishfy ?
we already have an ordered list in the form of questions.
Sorry, I may be missing something. That sentence doesn't make any sense to me in the context.
Can you explain what you mean @nitishfy ?
Could you explain what you mean here to number sections? If we are mentioning about numbering the questions that have been asked, it has already been marked.
Squashed the commits.
I think we're ready to merge this PR now
Thanks for the PR.
/lgtm /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: nitishfy, sftim
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/hold cancel
FYI, we need to add a PR under k/website
as well, correct?
Spotlight blog for the SIG-Release - Release Team Subproject.