Code Owner Designation

[Advay17]

In Github, Code Owner is a designation for someone who is very knowledgeable about a certain file or files. They are required to review all prs that modify these files, and are also a way of documenting who knows about certain parts of the code so that if anyone is ever curious about those parts of the code, they know who to ask.

How do we want to do code owner designation? Based on our current competencies, I propose the following:
Mechanisms-Kavin, Shreshta, and Rohit
Pathplanner Specific Files-Shreshta
LEDs-David and Kavin
Vision-Kavin, Aneesh, and Aeden
Sim Specific Files-Kavin
Drivetrain-Rohit
All other files: Common/Unowned, meaning that anyone from the team can perform the tasks of a code owner for these files.

This is subject to other changes based on everyone's thoughts. @VMFortress I didn't include you given that you are already known to be a resource for all parts of the code, and you have to verify all merges anyway.

If you want to volunteer to be a code owner for a file, make sure that file is something you are fully knowledgeable and competent with(as in, I could ask you anything about any part of that file, and you could tell me what it does, why it does it, how it does it, etc.)

[VMFortress]

This seems like a good idea to me. I'll leave it up to the experienced members to declare what they'd like to be an owner of.

I'll stay off of it and let this be a field for you all. I'll always be there to help on any part but it's best to have a student to own each piece.

[VMFortress]

@314PiGuy @Rohit1046 @ironon @shreshtaparthaje Can you provide your thoughts?

(Also I don't know Aeden's @ so if you know, please add him)

[Advay17]

@aedanmills