Update CONTRIBUTING.md

[michi-covalent]

Document that we are planning to merge Cilium CLI code into cilium/cilium repository.

Ref: cilium/design-cfps#9

[michi-covalent]

cc @joestringer @aanm (i can't seem to @ cilium-maintainers team)

[joestringer]

@cilium/cilium-maintainers

[joestringer]

Is the intent to change the user experience for this too? For instance, expect users to download from cilium/cilium, release on a different cadence?

[michi-covalent]

Is the intent to change the user experience for this too? For instance, expect users to download from cilium/cilium, release on a different cadence?

the current proposal is to not change the user experience, at least in the short term. we'll continue to publish release artifacts in cilium/cilium-cli repo at its own release cadence independent of cilium/cilium release cycle:

https://github.com/cilium/design-cfps/blame/3b5b719b9fac007d2ea683b18aafe4b3cb62e1eb/cilium/CFP-25694-move-cilium-cli-to-cilium-repo.md#L77-L80

[joestringer]

OK, the reason I ask is that this is placing the warning right at the top as the first thing that users see. This looks like a warning for users to get ready to change the way they pull the tool.

Developer-focused warnings should probably be lower down in the readme in a section that's clearly about how you contribute.

[michi-covalent]

yeah makes sense. maybe i can update https://github.com/cilium/cilium-cli/blob/main/CONTRIBUTING.md instead 💭

[pchaigno]

Is it expected that cilium/cli is also an owner for the README? That doesn't make much sense for me.

[michi-covalent]

Is it expected that cilium/cli is also an owner for the README? That doesn't make much sense for me.

cilium/cli team is the default owner of this repo, so yeah i guess it is sort of expected https://github.com/cilium/cilium-cli/blob/main/CODEOWNERS#L17 do you have any particular team on your mind who should own README.md?

[pchaigno]

cilium-cli-maintainers? 😁 Or we split cli into cilium-cli and cilium's CLIs.

[michi-covalent]

Or we split cli into cilium-cli and cilium's CLIs.

this could be an option, i can go either way. maybe a good topic to bring up in the community meeting 💭 just as a reference cilium/cli team's responsibility is currently described as:

Provide user experience feedback on changes to Command-Line Interfaces.
These owners are a stand-in for the user community to bring a user
perspective to the review process. Consider how information is presented,
consistency of flags and options.

https://github.com/cilium/cilium/blob/4d0836b05cc25d19a2c767d5e508679e401c1d75/CODEOWNERS#L31-L35

[pchaigno]

Yeah, so we at least can agree that the description doesn't match the current role of fallback for all of cilium-cli.

[joestringer]

The reviewer group for CLI is currently documented as having a project-wide scope: https://docs.cilium.io/en/stable/contributing/development/reviewers_committers/review_process/#project-wide . We can of course revisit this and figure out if there is a better set of individuals who could take ownership of different components.

[michi-covalent]

#2710 should reduce the noise to the cli team during the cilium-cli release process 🚀 🙏