Move Contributing to a separate file

[xmulligan]

Moving the developing and contributing sections out of the main README into a separate file like most projects

[joestringer]

The "trigger CI runs" aspect is not relevant to pwru, pwru has a simpler CI that just runs when you submit a PR.

[xmulligan]

I've made some suggestions about making it broader about benefits across the project ecosystem. What do you think?

[joestringer]

The developer guide link here has a lot of content, and it is all tailored towards developing on cilium/cilium. I'm not sure whether new contributors for pwru without cilium background would have a good chance of finding the relevant info here. I agree in principle the coding standards & best practices are likely well aligned between the subprojects, but I'm not sure which parts of the linked contributing guide are relevant for pwru.

[joestringer]

Something like https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#how-to-contribute is probably more practical, but there's still a few steps that aren't necessary for pwru, such as steps 7, 9-13.

[joestringer]

Overall the ideal is probably more that we enforce the "coding standards and best practices" via GitHub workflows so they apply automatically rather than just documenting them and hoping contributors will follow. But that would involve more work on the GHA side in this repo. I'm thinking stuff like adding golangci-lint to lint for common errors for instance.

[joestringer]

Broken link, did you mean https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#getting-a-pull-request-merged ?

[xmulligan]

Suggested change

Cilium has a well-defined [contributor ladder](https://github.com/cilium/community/blob/main/CONTRIBUTOR-LADDER.md) to help community members grow both responsibilities and privileges in the ecosystem. This ladder outlines the path from an occasional contributor to a committer, detailing expectations at each stage. Most contributors start at the community level and progress as they become more engaged in the project. We encourage you to take an active role, and the community is here to support you on this journey.

The Cilium project has a well-defined [contributor ladder](https://github.com/cilium/community/blob/main/CONTRIBUTOR-LADDER.md) to help community members grow both responsibilities and privileges in the project ecosystem. This ladder outlines the path from an occasional contributor to a committer, detailing expectations at each stage. Most contributors start at the community level in a sub-project and progress as they become more engaged in the project ecosystem. We encourage you to take an active role, and the community is here to support you on this journey.

[xmulligan]

Suggested change

Becoming a [Cilium organization member](https://github.com/cilium/community/blob/main/CONTRIBUTOR-LADDER.md#organization-member) grants you additional privileges, such as the ability to trigger CI runs. If you're contributing regularly to `pwru`, consider joining the [pwru team](https://github.com/cilium/community/blob/main/ladder/teams/pwru.yaml) to help review code and accelerate development. Your contributions play a vital role in improving the project, and we'd love to have you more involved!

Becoming a [Cilium organization member](https://github.com/cilium/community/blob/main/CONTRIBUTOR-LADDER.md#organization-member) grants you additional privileges across the project ecosystem, such as the ability to leave reviews on a PR or trigger CI runs. If you're contributing regularly to `pwru`, consider joining the [pwru team](https://github.com/cilium/community/blob/main/ladder/teams/pwru.yaml) to help review code and accelerate development. Your contributions play a vital role in improving the project, and we'd love to have you more involved!