search

stanford-ssi / sequoia-software

Sequoia flight software
MIT License
6 stars 1 forks source link

Add POCs for various software subsystems #14

Closed kevtan closed 4 years ago

kevtan commented 4 years ago

I think we should have a list somewhere (GitHub Wiki maybe) that lists who is the POC (Point Of Contact) for Sequoia's various software subsystems. For instance, we could make John Doe responsible for the flight controller or something. This way, when someone makes a pull request, they can easily figure out who should review their code. This also gives that person a higher stake in the quality of that subsystem, which (hopefully) leads to that subsystem being more reliable. Please let me know what you think!

polygnomial commented 4 years ago

Sure - probably best to put this on the Readme for the repository. Not Github wiki, SSI has a media wiki that we are switching to in order to stay aligned between teams: wiki here

lgnashold commented 4 years ago

This sounds good to me. It will probably end up being me for the FlightController/Pycubed and Modeling stuff, Moritz for payload/raspi stuff, and other people can add secondary reviews as needed.

lgnashold commented 4 years ago

Done, on wiki