Skip to content

sig-node: CONTRIBUTING.md updates #6611

Open
@endocrimes

Description

@endocrimes

/sig node
/kind documentation

The sig-node contributor documentation currently assumes a lot of existing knowledge about how the kubernetes project works. To help foster new contributions from people who don't necessarily have existing upstream contributor knowledge, or people within their organization who can train them we should update this document.

I think we probably need to focus on the following as a first step:

  • How do you get the code and build/test a kubelet change
    • e.g you likely need access to a linux machine/vm with containerd or cri-o installed, might not be obvious to a new contrib.
  • How do you make a good first contribution
    • How do you find issues?
    • How do you request feedback?

Something to think about in a future community meeting would be talking about how we can help foster these contributions. Reviewer/Approver capacity is low, but we can't fix that without new contributors long term.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/documentationCategorizes issue or PR as related to documentation.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.sig/nodeCategorizes an issue or PR as relevant to SIG Node.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions