-
Notifications
You must be signed in to change notification settings - Fork 210
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
Formalizing code owners #346
Comments
No objections -maybe discuss in the meeting? |
I also have no objections. Unfortunately I'm again not able to participate to the meeting today. 😞 If it's discussed I'll give feedback afterwards 😉 |
We discussed it during the meeting, and we would be okay to try this. |
This issue was automatically considered stale due to lack of activity. Please update it and/or join our slack channels to promote it, before it automatically closes (in 7 days). |
I guess the next steps would be to decide who owns what.... Any volunteers? :) |
I can do the helm-stuff 😉 |
Our team is oriented with ppl in some knowledge in an area, and less in others, so it might be worth formalizing this under the form of codeowners. Codeowners would allow us to ping the right person automatically on code reviews, and make it easier for community members to know what they own or what are the areas that deserve more love.
WDYT?
The text was updated successfully, but these errors were encountered: