Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Reorganize top-level folders #1533

Open
shu-mutou opened this issue Nov 18, 2024 · 5 comments
Open

Reorganize top-level folders #1533

shu-mutou opened this issue Nov 18, 2024 · 5 comments
Assignees
@jberkus @cblecker @kaslin @nikhita
Labels
sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience.

Comments

@shu-mutou
Copy link
Contributor

shu-mutou commented Nov 18, 2024 •
edited
Loading

I suggest organizing top-level folders as follows:

  • Keep the remote folder for on-demand self-study and the exercises folder for teaching materials as they are.
  • Create /local-community/ folder and move the folder with the OWNERS file managed by the local community as they are.
    • aotearoa
    • brazil
    • india
    • japan
  • Create a /events/ folder for past events such as NCW and move them under that.
    • barcelona -> rename to ncw-2019-barcelona
    • bay-area-kube-day -> rename to bay-area-kube-day-2019
    • denver -> rename to gophercon-2018-denver
    • oscon-2019
    • paris -> rename to ossummit-2018-paris
    • presentations/README.md -> rename to ncw-2018-seattle/presentasions.md
    • sandiego -> rename to ncw-2019-sandiego
    • seattle -> rename to ncw-2018-seattle
    • shanghai -> rename to ncw-shanghai
  • If there is no OWNERS file and the folders are considered to have no administrator, the contents of the folders will be moved to the remote folder
    • australia
    • austria
    • morocco
  • If there is no OWNERS file and no new contributor files, the folders will be deleted
    • beijing
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Nov 18, 2024
@shu-mutou
Copy link
Contributor Author

shu-mutou commented Nov 18, 2024 •
edited
Loading

/sig contributor-experience

@k8s-ci-robot
Copy link
Contributor

@shu-mutou: The label(s) sig/contrib-ex cannot be applied, because the repository doesn't have them.

In response to this:

/sig contrib-ex

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
Copy link
Contributor

@shu-mutou: The label(s) sig/[contributor-experience](https://github.com/kubernetes/kubernetes/labels/sig%2fcontributor-experience) cannot be applied, because the repository doesn't have them.

In response to this:

/sig contributor-experience

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.

@shu-mutou
Copy link
Contributor Author

/sig contributor-experience

@k8s-ci-robot k8s-ci-robot added sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Nov 18, 2024
@shu-mutou
Copy link
Contributor Author

/assign cblecker jberkus kaslin nikhita

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jberkus jberkus

@cblecker cblecker

@kaslin kaslin

@nikhita nikhita

Labels
sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@jberkus @cblecker @kaslin @shu-mutou @nikhita @k8s-ci-robot