Document our implicit rule about minimizing coding languages.
Change-Id: I60f4def267077064cbd55bdb43661f544905eeba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2507889 Commit-Queue: Peter Kasting <pkasting@chromium.org> Commit-Queue: Darin Fisher <darin@chromium.org> Reviewed-by: Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#822261}
This commit is contained in:
@ -353,6 +353,14 @@ general rules of thumb can be helpful in navigating how to structure changes:
|
||||
that future changes will be less likely to regress functionality. Protect
|
||||
your code with tests!
|
||||
|
||||
- **Stick to the current set of supported languages as described in the
|
||||
[styleguide][cr-styleguide].** While there is likely always a slightly better
|
||||
tool for any particular job, maintainability of the codebase is paramount.
|
||||
Reducing the number of languages eases toolchain and infrastructure
|
||||
requirements, and minimizes the learning hurdles for developers to be
|
||||
successful contributing across the codebase. Additions of new languages must
|
||||
be approved by [//ENG_REVIEW_OWNERS](../ENG_REVIEW_OWNERS).
|
||||
|
||||
## Tips
|
||||
|
||||
### Review etiquette
|
||||
|
Reference in New Issue
Block a user