When contributing to Chrome DevTools, please follow the process explained in this document. This is to reach a clear agreement on proposals, while involving all relevant stakeholders and decision makers.
This process puts the IC in charge, but also requires Chrome DevTools' leaders to help the IC navigate the decision process. It includes an escalation path in case of disagreement. The overhead of this process should be proportionate to the scope of the proposal.
Important:
LGTM: N/A
This person is the creator of the feature and the creator of the design documentation.
LGTM: Required. May delegate.
The Chrome DevTools TL is Danil Somsikov (dsv@chromium.org). The TL ensures architectural consistency and good coverage by the right set of LGTM providers, and is required to sign off on the design. They may however explicitly delegate to other LGTM providers.
In the absence of the TL, an EnReOw can act in their stead.
LGTM: Required. May delegate.
This is a person that is required to give LGTM. These are usually ICs with significant knowledge about the areas in question.
LGTM: Not required.
This is somebody who reviews and comments on the proposal. Their input should be considered, although their LGTM is not required.
LGTM: Not required. However, LGTM or non-LGTM is binding.
Stuck proposals can be escalated to the ENG_REVIEW_OWNERS. Potential use cases of such an escalation:
The EnReOw can overrule non-LGTMs or LGTMs.
It is always useful to have a design document. Its length can vary depending on the scope of the proposed change.
As soon as possible so that a wide range of opinions can be taken into consideration. If you share your idea or prototype at a later stage, you risk having to redo the work because you missed a constraint.
Some pointers when people should be added to the list of LGTM providers:
Here.
Make sure you still have the LGTMs e.g. by pinging the LGTM providers.
In this case you can follow this path of escalation:
Review the design document. If you think there are other people who should take a look, add them as LGTM providers or as reviewers. If you don't think you are the right person, remove yourself as LGTM provider.
If you agree with the design, add an LGTM to the table. If you have blocking concerns, add “Not LGTM, because ” to the table. Be prepared to re-review the design after another iteration.
The Chromium DevTools Design Review Guidelines complement Chromium’s feature launch process. If you are launching a new Web platform feature, please follow the Chromium launch process. It likely makes sense to have all the LGTMs gathered at the point in time you would send an Intent to Implement.