Repo for an AI experiment

[ameukam]

Describe the issue

We will like to get a new GitHub repository to host the codebase for an experimental tool that aims to improve the maintainer experience using Deep Learning techniques. This tool will leverage different AI tools to automate and enhance various aspects of repository maintenance, such as issue triaging, pull request review, and possibly documentation generation.

/assign @justinsb @ameukam

[ameukam]

/sig contribex

[k8s-ci-robot]

@ameukam: The label(s) sig/contribex cannot be applied, because the repository doesn't have them.

In response to this:

/sig contribex

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.

[ameukam]

/sig contributor-experience

[ameukam]

cc @kubernetes/sig-contributor-experience-leads
We reached out the different leads for feedback. Hopefully we will get consensus to open file a request for repo creation.

[palnabarun]

Thinking out aloud, how about using kubernetes-sigs/maintainers for this? You wouldn't need a separate repo then. The said repo has some existing tooling to help maintainers maintain the OWNERS files.

[dims]

works @palnabarun ! (or hydrophone repo is fine as well )

[ameukam]

Thinking out aloud, how about using kubernetes-sigs/maintainers for this? You wouldn't need a separate repo then. The said repo has some existing tooling to help maintainers maintain the OWNERS files.

We're mostly looking for autonomy in terms of PR approvals and CI setup. We don't have a proper definition of success for this experiment so I don't know how complex the code base will look like in the future. An existing repo is fine but I don't want to confuse any new contributor.

[palnabarun]

kubernetes-sigs/maintainers seems to be a nice option then. Both tools (maintainers and the one you are proposing) have similar reasons to exist.

[ameukam]

SGTM. I guess we need to wait for the other TLs to chime in ?

[Priyankasaggu11929]

Hello folks (sorry I was out last week, just catching up & continuing the discussions from Jan, 2025 ContribEx meetings.)

Not blocking on the request for using k-sigs/maintainers repo, but I'm still trying to understand the scope of the overall request, since we have 2 parallel ongoing conversations (which seems similar or converging, but @ameukam you mentioned they're not - so want to check the status at this point):

• request for new repo for AI experiments, by @ameukam
• new maintainers-tool working group proposal, by @justinsb
  • @justinsb, checking if the discussions within this thread, around using kubernetes-sigs/maintainers repo, also aligns with your proposal for new maintainers-tool working group?
  • If we're agreeing to use kubernetes-sigs/maintainers (I'm assuming yes, considering PR k-sigs/maintainers#26), do you still plan to create the new working group? Or that's no longer needed?

---

Also some umbrella questions regarding the scope of AI experiments within the repo:

We don't have a proper definition of success for this experiment so I don't know how complex the code base will look like in the future.

Can we define the "out of scope" items for the moment?
(It's ok to keep revising the list, but to give some boundaries to the experimentation for all current & future folks to be involved?)

---

(further, following up from the contribex meetings notes)
@mfahlandt – did you have any other discussions with k8s-infra group about this?
@ameukam – I remember you mentioning this is a standalone project by you (with not your k8s-infra chair hat on), so checking if there is any third conversation happening as well within k8s-infra group?

[ameukam]

I remember you mentioning this is a standalone project by you (with not your k8s-infra chair hat on), so checking if there is any third conversation happening as well within k8s-infra group?

@Priyankasaggu11929 This is out of scope for the Infra SIG. so we don't currently have any conversation regarding this within the SIG.

[mfahlandt]

There was a discussion about this in the Meeting of SIG k8s infra.
In this meeting it was pointed out SIG Testing have a similar place called experiments https://github.com/kubernetes/test-infra/tree/master/experiment

I would like to align if this is already a good place to be and if SIG Testing want to be the host or if we want to open up a new central place under SIG ContribEx