| jam | 2928b5dc | 2017-05-30 16:33:38 | [diff] [blame] | 1 | # Policy for Adding a New Port |
| 2 | |
| 3 | Since every new port for Chromium has a maintenance cost, here are some guidelines for when the project will accept a new port. |
| 4 | |
| 5 | ## Expectations |
| 6 | |
| 7 | * Ports should represent a significant ongoing investment to established platforms, rather than hobby or experimental code. |
| 8 | * These will not have bots on Google-run waterfalls (even FYI). |
| 9 | * Chromium engineers are not expected to maintain them. |
| 10 | * As much as possible, try to use existing branches/ifdefs. |
| Mostyn Bramley-Moore | 0731f15 | 2017-11-20 19:55:39 | [diff] [blame] | 11 | * While changes in src/base are unavoidable, higher level directories shouldn't have to change. i.e. existing porting APIs should be used. We would not accept new rendering pipelines as an example. |
| 12 | * Send an email to [src/OWNERS](https://chromium.googlesource.com/chromium/src/+/master/ENG_REVIEW_OWNERS) for approval. |
