Hi fellow V8 contributors,

TL;DR The V8 project is introducing Design Review Guidelines to facilitate
the design and decision making around major changes. More information can
be found here <https://v8.dev/docs/design-review-guidelines>.

The number of contributors to the V8 repository has grown over the course
of years. In order to accommodate that, we are introducing Design Review
Guidelines <https://v8.dev/docs/design-review-guidelines> with the
following goals:


   1.

   Make it clear to Individual Contributors (ICs) who the decision makers
   are and highlight what the path forward in the case that projects are not
   proceeding due to technical disagreement
   2.

   Create a forum to have straight-forward design discussions
   3.

   Ensure V8 Technical Leads (TL) are aware of all significant changes and
   have the opportunity to give their input on the Tech Lead (TL) layer
   4.

   Increase the involvement of all V8 contributors over the globe


At a glance the guidelines consist of 4 steps:

   -

   [Step 1] Gathering first feedback
   -

      The Individual Contributor (IC) writes an early design
      doc/explainer/one pager and asks a few people for input.
      -

      The Tech Lead (TL) of the main component your feature touches
      suggests people that need to provide an LGTM.
      1.

         If it is not clear who the TL is, please ask the V8 Eng Review
         Owners via [email protected].
         -

      The IC sends out the doc to [email protected].
      -

   [Step 2] Collecting LGTMs
   -

      The IC collects LGTMs from all stakeholders with the help of their TL.
      -

      If an LGTM provider doesn’t provide a  an LGTM, they are obligated to
      provide an explanation why
      -

   [Step 3] Optional: Escalation
   -

      If the "NOT LGTMs" can't be resolved, the IC and TL escalate to
      [email protected].
      -

      Together with the IC and TL the next steps to unblock the change are
      decided.
      -

   [Step 4] Implementation
   -

      The IC sends and email to [email protected] with a link
      to the design doc that informs the group that implementation starts.
      -

      The IC implements the change.


[image: V8 design reviews.png]


Googlers that work on V8 have been already internally dogfooding these
guidelines for half a year. You might have already seen a few documents
with the famous LGTM headers in your inbox.

More detail about this new process can be found on V8's public web page
<https://v8.dev/docs/design-review-guidelines>. Please have a look at the FAQ
section <https://v8.dev/docs/design-review-guidelines#faq> in particular.
If you have unanswered questions, please simply reply to this thread or
send me an email directly.

Thanks,

Michael

-- 
-- 
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
--- 
You received this message because you are subscribed to the Google Groups 
"v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/v8-dev/CAF2MX8i%3D86LVY8pzXuWoqdTNrudQ2SDPo58FPwrQ85B%3Dm98fTg%40mail.gmail.com.

Reply via email to