2018-05-11 15:32:19 +00:00
|
|
|
# Design review process
|
2017-12-13 08:41:43 +00:00
|
|
|
|
2018-05-14 15:32:14 +00:00
|
|
|
The Corda design review process defines a means of collaborating approving Corda design thinking in a consistent,
|
|
|
|
|
structured, easily accessible and open manner.
|
|
|
|
|
|
|
|
|
|
The process has several steps:
|
|
|
|
|
|
|
|
|
|
1. High level discussion with the community and developers on corda-dev.
|
|
|
|
|
2. Writing a design doc and submitting it for review via a PR to this directory. See other design docs and the
|
|
|
|
|
design doc template (below).
|
|
|
|
|
3. Respond to feedback on the github discussion.
|
|
|
|
|
4. You may be invited to a design review board meeting. This is a video conference in which design may be debated in
|
|
|
|
|
real time. Notes will be sent afterwards to corda-dev.
|
|
|
|
|
5. When the design is settled it will be approved and can be merged as normal.
|
|
|
|
|
|
2017-12-13 08:41:43 +00:00
|
|
|
The following diagram illustrates the process flow:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-05-14 15:32:14 +00:00
|
|
|
At least some of the following people will take part in a DRB meeting:
|
|
|
|
|
|
2017-12-13 08:41:43 +00:00
|
|
|
* Richard G Brown (CTO)
|
|
|
|
|
* James Carlyle (Chief Engineer)
|
|
|
|
|
* Mike Hearn (Lead Platform Engineer)
|
|
|
|
|
* Mark Oldfield (Lead Platform Architect)
|
|
|
|
|
* Jonathan Sartin (Information Security manager)
|
|
|
|
|
* Select external key contributors (directly involved in design process)
|
|
|
|
|
|
2018-05-14 15:32:14 +00:00
|
|
|
The Corda Technical Advisory Committee may also be asked to review a design.
|
2017-12-13 08:41:43 +00:00
|
|
|
|
2018-05-14 15:32:14 +00:00
|
|
|
Here's the outline of the design doc template:
|
2017-12-13 08:41:43 +00:00
|
|
|
|
2018-05-14 15:32:14 +00:00
|
|
|
.. toctree::
|
2017-12-13 08:41:43 +00:00
|
|
|
|
2018-05-14 15:32:14 +00:00
|
|
|
template/design.md
|
