We will start by defining the code owners for our smart contract.

Ideally, in a large consortium, the code owners should not be the same group as the one that modifies the code. Remember, these steps are meant to reinforce the trust in the network.

Code owners are defined in a file called CODEOWNERS, which can reside either in the root directory or the .Github directory. GitHub allows us to define different code owners depending on file patterns, so while we could get very creative, we will focus on a few artifacts from our Hyperledger composer project:

• package.json: As it controls the build and packaging process, this represents a key file to control.
• header.txt: This contains the license. As such, you may want a specific set of people who have oversight on this one (think lawyers).
• JavaScript files: This contains the core logic of the smart contracts. Depending on the complexity, this could be further broken down depending on the files, but we will keep it at a high level.
• *.cto files: This should be aligned to the owners of the JavaScript.
• *.acl files: This should be aligned to the owners of the JavaScript.
• *.qry files: This should be aligned to the owners of the JavaScript.
• *.md files: This represents the documentation of your smart contract. Depending on the scope, this could be aligned to the same owners as the JavaScript or a different set of people.