[DRIVERS-116] Driver projects should have developer guides Created: 20/Aug/13 Updated: 15/Apr/19 Resolved: 22/Jun/16 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Bernie Hackett | Assignee: | Barrie Segal |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||
| Driver Compliance: |
|
||||||||||||||||||||||||||||||||
| Description |
|
A few of our driver projects have extensive documentation about getting started as a new developer (best practices, style guides, how to do code reviews, tools to use, etc.). All of the driver projects should have similar developer guides. This is important to not lose institutional knowledge when developers leave, and helps with interns and new grad engineering rotations. |