ExternalVendorCode/corda
1
0
Fork 0
mirror of https://github.com/corda/corda.git synced 2024-12-24 07:06:44 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Update contributing-philosophy.rst (#6044)

Browse Source
This commit is contained in:
Joel Dudley 2020-03-09 15:11:53 +00:00 committed by GitHub
parent 3a13e8ab31
commit 3973fe46f2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/source/contributing-philosophy.rst
View File

@ -11,8 +11,7 @@ modern business transactions. It is unique in its aim to build a platform for b
retaining strict privacy. Corda provides an implementation of this vision in a code base which others are free to build on, contribute to retaining strict privacy. Corda provides an implementation of this vision in a code base which others are free to build on, contribute to
or innovate around. The mission of Corda is further detailed in the `Corda introductory white paper`_. or innovate around. The mission of Corda is further detailed in the `Corda introductory white paper`_.
The project is supported and maintained by the `R3 Alliance <https://www.r3.com>`_, or R3 for short, which consists of over two hundred firms The project is supported and maintained by `R3 <https://www.r3.com>`_.
working together to build and maintain this open source enterprise-grade blockchain platform.
Community Locations Community Locations
------------------- -------------------
@ -44,12 +43,12 @@ Community maintainers
^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^
Current community maintainers: Current community maintainers:
* `Joel Dudley <https://github.com/joeldudleyr3>`_ - Contact me: * `Rick Parker <https://github.com/rick-r3>`_ - Contact me:
* On the `Corda Slack team <http://slack.corda.net/>`_, either in the ``#community`` channel or by direct message using the handle * On the `Corda Slack team <http://slack.corda.net/>`_, either in the ``#community`` channel or by direct message using the handle
``@joel`` ``@parkri``
* By email: joel.dudley at r3.com * By email: rick.parker at r3.com
We anticipate additional maintainers joining the project in the future from across the community. We anticipate additional maintainers joining the project in the future from across the community.
@ -60,13 +59,12 @@ Over two hundred individuals have contributed to the development of Corda. You c
Transparency and Conflict Policy Transparency and Conflict Policy
-------------------------------- --------------------------------
The project is supported and maintained by the `R3 Alliance <https://www.r3.com>`_, which consists of over two hundred firms working together The project is supported and maintained by `R3 <https://www.r3.com>`_. We develop in the open and publish our
to build and maintain this open source enterprise-grade blockchain platform. We develop in the open and publish our
`Jira <https://r3-cev.atlassian.net/projects/CORDA/summary>`_ to give everyone visibility. R3 also maintains and distributes a commercial `Jira <https://r3-cev.atlassian.net/projects/CORDA/summary>`_ to give everyone visibility. R3 also maintains and distributes a commercial
distribution of Corda. Our vision is that distributions of Corda be compatible and interoperable, and our contribution and code review distribution of Corda. Our vision is that distributions of Corda be compatible and interoperable, and our contribution and code review
guidelines are designed in part to enable this. guidelines are designed in part to enable this.
As the R3 Alliance is maintainer of the project and also develops a commercial distribution of Corda, what happens if a member of the As R3 is maintainer of the project and also develops a commercial distribution of Corda, what happens if a member of the
community contributes a feature which the R3 team have implemented only in their commercial product? How is this apparent conflict managed? community contributes a feature which the R3 team have implemented only in their commercial product? How is this apparent conflict managed?
Our approach is simple: if the contribution meets the standards for the project (see above), then the existence of a competing commercial Our approach is simple: if the contribution meets the standards for the project (see above), then the existence of a competing commercial
implementation will not be used as a reason to reject it. In other words, it is our policy that should a community feature be contributed implementation will not be used as a reason to reject it. In other words, it is our policy that should a community feature be contributed