Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: add a CODEOWNERS file #5177

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: add a CODEOWNERS file #5177

wants to merge 1 commit into from

Conversation

lengau
Copy link
Contributor

@lengau lengau commented Dec 12, 2024

This file follows the standard Starcraft ownership model, but there might be more nuances for snapcraft. For example, should there be additional owners on things like the gnome extension?

  • Have you followed the guidelines for contributing?
  • Have you signed the CLA?
  • Have you successfully run tox run -m lint?
  • Have you successfully run tox run -e test-py310? (supported versions: py39, py310, py311, py312)

Signed-off-by: Alex Lowe <alex.lowe@canonical.com>
@lengau lengau requested review from sergiusens and mr-cal December 12, 2024 00:24
Copy link
Collaborator

@mr-cal mr-cal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think adding codeowners outside our team is a great idea, here's what I can think of:

  • extensions/ros*, snapcraft/extensions/*ros*, snapcraft/parts/plugins/[colcon_plugin,_ros] - @artivis
  • extensions/desktop/[kde*,common], snapcraft/extensions/kde* - @ScarlettGatelyMoore
  • snapcraft/extensions/env_injector.py - @farshidtz or @locnnil
  • snapcraft/parts/plugins/matter_sdk_plugin - @farshidtz
  • snapcraft/parts/plugins/kernel_plugin, snapcraft_legacy/plugins/v2/*kernel* - @kubiko
  • extensions/desktop/[command-chain,common,gnome,src], snapcraft/extensions/gnome - I'm not sure, possibly @seb128?

Note to anyone I tagged - the implication of the CODEOWNERS file is that if someone submits a PR to change the code in one of these files, you will be notified and requested to review.

/docs/ @medubelko @mr-cal

# Finally, all CODEOWNERS changes need to be approved by The Man, Himself.
/.github/CODEOWNERS @sergiusens
Copy link
Contributor

@locnnil locnnil Dec 12, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can give env_injector to me:

Suggested change
/.github/CODEOWNERS @sergiusens
/.github/CODEOWNERS @sergiusens
/snapcraft/extensions/env_injector.py @locnnil @farshidtz
/tests/spread/extensions/env-injector @locnnil @farshidtz

Edit: I'm letting also @farshidtz taking care of this because he promised to be nice. 😄

@artivis
Copy link
Contributor

artivis commented Dec 12, 2024

  • extensions/ros*, snapcraft/extensions/*ros*, snapcraft/parts/plugins/[colcon_plugin,_ros] - @artivis

May I request that, additionally to myself, you add @canonical/robotics (or alternatively canonical-robotics-community-group@canonical.com) as well?

@farshidtz
Copy link
Member

farshidtz commented Dec 12, 2024

  • extensions/ros*, snapcraft/extensions/*ros*, snapcraft/parts/plugins/[colcon_plugin,_ros] - @artivis

May I request that, additionally to myself, you add @canonical/robotics (or alternatively canonical-robotics-community-group@canonical.com) as well?

That's actually a great idea, so someone else from the team can respond when an individual isn't available. It should also make the maintenance of the code owner list easier, in case the team members change.

If possible please use @canonical/industrial as code owner for the matter and env-injector plugins.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants