Spotlight: SIG Scheduling #508
Assignees
Comments
|
/assign @ArvindParekh |
|
@mfahlandt: GitHub didn't allow me to assign the following users: ArvindParekh. Note that only kubernetes members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
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. |
|
/assign |
|
Hackmd revisions within the comms team are underway. PR should be created soon. |
This was referenced Jul 26, 2024
fsmunoz
added a commit
to fsmunoz/contributor-site
that referenced
this issue
Aug 2, 2024
Closes: kubernetes#519 kubernetes#508 Co-authored-by: Arvind Parekh <aruparekh@gmail.com>
fsmunoz
added a commit
to fsmunoz/contributor-site
that referenced
this issue
Aug 2, 2024
Closes: kubernetes#519 kubernetes#508 Co-authored-by: Arvind Parekh <aruparekh@gmail.com>
11 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Got a contact in SIG Scheduling to start moving forward. Owned by: @ArvindParekh
17-May-2024: Questions are being answered, will check in.
24-May-2024: Last few questions are on hold temporarily as SIG Lead changes companies
07-June-2024: Questions are answered draft in markdown can start
The text was updated successfully, but these errors were encountered: