Add sig-doc-automation Slack Channel

[allenfeng8]

Creating sig-doc-automation Slack channel

Which issue(s) this PR fixes:

Creating a communication channel for this conversation

[linux-foundation-easycla]

• ✅login: allenfeng8 / name: Allen Feng / (a477a06)

The committers listed above are authorized under a signed CLA.

[k8s-ci-robot]

Welcome @allenfeng8!

It looks like this is your first PR to kubernetes/community 🎉. 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/community 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. 😃

[k8s-ci-robot]

Hi @allenfeng8. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[lmktfy]

/ok-to-test

[lmktfy]

The idea behind this channel is to manage work for a nascent / informal subproject. People who want to help with the way that the docs automatically generate and build and publish.

This could cover (non exhaustive list):

• CVE / vulnerability feed
• Netlify automation
• Releases metadata and their transformation into current docs (eg, the download list)
• Reference docs generation
• Blog article publishing to a schedule

[lmktfy]

/LGTM
/approve

I'm no longer a tech lead for SIG Docs, so this is me approving as an individual member of the project.

[lmktfy]

/assign @salaxander

[singh1203]

/LGTM

Thank you! @allenfeng8

[k8s-ci-robot]

@singh1203: changing LGTM is restricted to collaborators

In response to this:

/LGTM

Thank you! @allenfeng8

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-sigs/prow repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: allenfeng8, lmktfy, singh1203
Once this PR has been reviewed and has the lgtm label, please ask for approval from salaxander. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• communication/slack-config/sig-docs/OWNERS

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

[natalisucks]

/hold
given there's been no discussion with SIG leads on this yet, and we're only now aligning on efforts around the reference docs and the LFX mentorship that is currently underway in parallel, i do not wish to have this channel created just yet until alignment is reached

[Okabe-Junya]

Thank you, I've also checked Slack and think this suggestion is so good :)

As Natali mentioned, I agree we should hold until the LFX mentorship progress and discussions with SIG TL/Chair are completed.

Quick question: Do you think it would be a good idea to work with/share information with other SIGs, such as SIG-contribex?

[Okabe-Junya]

Wait, my apologies. I seem to have missed another thread. It appears there's already a channel like sig-docs-tool.

c.f. https://kubernetes.slack.com/archives/C1J0BPD2M/p1757498792679489?thread_ts=1757329875.310429&cid=C1J0BPD2M

hey folks! i'm going to recommend that one of our existing channels, such as #sig-docs-tools be used, if you don't wish to discuss this topic in the main channel. similarly,

Rather than using this channel, it would be better to clarify the reasons for creating a new channel instead.

[reylejano]

SIG Docs co-chairs advised to use the #sig-docs-tools channel instead of creating a new Slack channel
/hold