chore(maintainers): mark @lllamnyp as Core Maintainer

[tym83]

What this PR does

Updates @lllamnyp's responsibility in MAINTAINERS.md from Etcd-operator Lead to Core Maintainer.

The etcd-operator is hosted in the separate aenix-io/etcd-operator repository — its leadership scope is tracked there. In cozystack/cozystack, @lllamnyp's role is a project-level Core Maintainer, which this change reflects.

Release note

​release-note NONE ​

Summary by CodeRabbit

• Documentation
  • Updated maintainers list to reflect current team roles and responsibilities.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: a51774dc-5c4c-43a2-9cdd-0b25c62c5b45

📥 Commits

Reviewing files that changed from the base of the PR and between cd5b4d0 and 5da0052.

📒 Files selected for processing (1)

• MAINTAINERS.md

---

📝 Walkthrough

Walkthrough

Timofei Larkin's listed responsibility in the Active Maintainers table is updated from "Etcd-operator Lead" to "Core Maintainer", reflecting a broader maintenance scope.

Changes

Maintainer Role Update

Layer / File(s)	Summary
Timofei Larkin's role update MAINTAINERS.md	Timofei Larkin's responsibility is updated from "Etcd-operator Lead" to "Core Maintainer" in the Active Maintainers table.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• cozystack/cozystack#2717: Modifies MAINTAINERS.md to update Timofei Larkin's entry in the maintainers table.

Suggested labels

size/S

Suggested reviewers

• lexfrei
• androndo
• sircthulhu
• kvaps

Poem

🐰 From operator lead to guardian broad,
Timofei takes the wider road,
Core Maintainer now wears his crown,
Cozystack's trusted cornerstone.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/maintainers-lllamnyp-responsibility

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the project's maintainer documentation to correctly reflect the current leadership role of @lllamnyp within the cozystack repository.

Highlights

• Maintainer Role Update: Updated the role of @lllamnyp in the MAINTAINERS.md file from 'Etcd-operator Lead' to 'Core Maintainer' to accurately reflect their project-level responsibilities.

New Features

🧠 You can now enable Memory (public preview) to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the MAINTAINERS.md file to promote Timofei Larkin to the role of Core Maintainer. The review feedback indicates that the pull request title currently uses an invalid scope according to the repository's style guide for conventional commits; it is recommended to update the scope to a valid one, such as docs.

[gemini-code-assist]

The PR title uses the scope maintainers, which is not listed as a valid scope in the repository style guide (Rules 40-45). Please update the PR title to use a valid scope, such as docs (e.g., chore(docs): mark @lllamnyp as Core Maintainer), to adhere to the Conventional Commits format required by the project.

References

1. The repository style guide defines a specific list of valid scopes for conventional commits. 'maintainers' is not in that list. ^(link)