Move artifacts from k/community to k/sig-security

[PushkarJ]

What?

Create the following set of directory structure:

k/sig-security:

• sig-security-docs:
  • Refactor this to here: https://github.com/kubernetes/community/blob/master/sig-security/sig-security-docs/OWNERS
• sig-security-external-audit:
  • Move all of this here: https://github.com/kubernetes/community/tree/master/sig-security/sig-security-external-audit
  • Move all of this here: https://github.com/kubernetes/community/tree/master/sig-security/security-audit-2019
  • Move all of this here: https://github.com/kubernetes/community/tree/master/sig-security/security-audit-2021
• sig-security-tooling:
  • Move this to here: https://github.com/kubernetes/community/blob/master/sig-security/sig-security-tooling/OWNERS

How?
This will need two set of PRs, one to remove stuff from k/community and one to add the same stuff to k/sig-security

Why do this?
This will unblock following PRs: kubernetes/community#6140 and kubernetes/community#5853. More importantly, it will allow allow sig-security artifacts to have a single landing page.

Anything else you would like to add @tabbysable @IanColdwater @reylejano @savitharaghunathan ?

/sig security
/kind cleanup
/label good first issue
/label help wanted

[PushkarJ]

/help
/good-first-issue

(trying again)

[k8s-ci-robot]

@PushkarJ:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/help
/good-first-issue

(trying again)

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.

[chetak123]

/assign @chetak123

[tabbysable]

@PushkarJ when I was reviewing #12 I asked for the directory structure to be matched to the old one from k/community, but now I see here you requested it specifically. So, I wanna bring this up so that @chetak123 isn't getting mixed messages.

I think that because our subproject names are fairly general terms on their own (docs and tooling especially) that it could be a little misleading to have the directory names as just those short words. Therefore, I like the old names that match the slack channel names better.

I don't want to dictate that, though-- WDYT about my idea of keeping the directory names the same as before?

[PushkarJ]

Hi Tabby, thank you for reviewing!! I did not think about mapping the directory names to channel names for consistency earlier but I like the idea. Changed the original description as per your suggestion now.

@chetak123 please go ahead and make the renaming changes @tabbysable suggested in the PR for adding new files and then we should be good to go

[PushkarJ]

With #12 and kubernetes/community#6176 merged, closing this ticket. Thank you again @chetak123 for working on this!!