docs/new_port_policy.md - Issue 2909733002: Add information on the requirements for a new Chromium port.

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: docs/new_port_policy.md

Issue 2909733002: Add information on the requirements for a new Chromium port. (Closed)

Patch Set: Created 3 years, 6 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

OLD	NEW
(Empty)
	1 # Policy for Adding a New Port

	2

	3 Since every new port for Chromium has a maintenance cost, here are some guidelin es for when the project will accept a new port.

	4

	5 ## Expectations

	6

	7 * Ports should represent a significant ongoing investment to established platf orms, 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.

	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.

OLD	NEW

« no previous file with comments | « build/build_config.h ('k') | tools/gn/args.cc » ('j') | no next file with comments »