Add SIG CLI Spotlight blog article

[fsmunoz]

SIG CLI Spotlight article.

[fsmunoz]

Please review and confirm, especially because while editing I've added some small changes like the links to the GitHub profiles, maybe you prefer to link to Twitter or somewhere else.

/cc @KnVerey @soltysh

[fsmunoz]

/cc @arpitjindal97

[k8s-ci-robot]

@fsmunoz: GitHub didn't allow me to request PR reviews from the following users: arpitjindal97.

Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @arpitjindal97

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[arpitjindal97]

You guys tagged wrong Arpit 😆

[fsmunoz]

@arpitjindal97 apologies, will correct the commit, thanks for the heads-up!

[fsmunoz]

/uncc @arpitjindal97

[sftim]

It would be nice to have a PR against k/website ready so that we mirror this article there (with this one as canonical)

See other articles in this series for hints about how we've done that.

[sftim]

/retitle Add SIG CLI Spotlight blog article

[fsmunoz]

@sftim sure, added kubernetes/website#41973 for the website.

[fsmunoz]

Going to change the publishing date header if no updates during the day .

[sftim]

I expected that kubernetes/website#41973 would be filled in a lot more. I'd prefer to wait until both are ready to go.

/hold

How about bumping these both back 7 days, and filling in kubernetes/website#41973 so that it previews OK? Have a look at other SIG spotlight article PRs in k/website to see how this is done.

OK to unhold once the other PR is reviewable.

[fsmunoz]

Hi @sftim, thanks for the comments. I kept it empty on purpose, for two reasons:

• If we are doing the review here until it's ready, it would be a waste of time to replicate each change to the other one. Since I had no indication that this one was already completely reviewed, I didn't update the other one.
• In previous SIG Spotlight articles (like Add SIG Storage Spotlight website#35084 ), it was explicitly mentioned that it should first be approved here, and then "copied" to the other - which makes sense and avoids work, but my understanding of this was to push a placeholder there and wait for the document to be ready here before doing the "copying"

I can easily push a commit to the other one right now, with the existing content, and changing the publishing date as suggested. We should then better document the process (I can update the blogging guidelines we have in Comms).

[sftim]

I can easily push a commit to the other one right now, with the existing content, and changing the publishing date as suggested. We should then better document the process (I can update the blogging guidelines we have in Comms).

Cool, let's do that.

[fsmunoz]

Changed date, rebased, updated kubernetes/website#41973 with existing content, as discussed!

[sftim]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fsmunoz, sftim

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:

• OWNERS [sftim]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sftim]

/hold cancel