Discuss adding version and copyright info to each contract in OpenZeppelin Contracts

abcoathup · November 19, 2019, 10:51pm

github.com/OpenZeppelin/openzeppelin-contracts

Discuss adding version and copyright info to each contract

opened 10:39PM - 19 Nov 19 UTC

closed 10:18PM - 19 Oct 21 UTC

meta

**🧐 Motivation** More and more we see contracts being installed individually, i…nstead of as part of the npm package. A recent example is the VS code plugin extension by the Microsoft Azure blockchain team: this extension allows a user to choose a contract by name, and it just downloads the solidity file (and its dependencies) to a local folder. This has the problem that any project-wide information, such as copyright, license, or package version is lost. Though we could ask to every tool to add this information as they download the contracts, it may be easier to just add it at the source. **📝 Details** Add a comment header to every contract with something along the lines of: ```solidity /** * @openzeppelin/contracts@X.Y.Z * Copyright zOS Global Limited, licensed under MIT * See https://github.com/OpenZeppelin/openzeppelin-contracts/ */ ``` And modify the release script so the version identifier on each contract is automatically updated, possibly just by using `sed -i`.

Feel free to add to the discussion here or on GitHub.

Topic		Replies	Views
Does code comply with OpenZeppelin license and copyright terms? Contracts erc20	4	2091	November 25, 2020
Built with OpenZeppelin - share the love General	1	2733	March 2, 2020
OpenZeppelin coding standard Contracts	3	1429	March 15, 2021
Difference between OpenZeppelin Contracts and OpenZeppelin Contracts Ethereum Package SDK	2	2300	May 14, 2020
Quick version question Contracts erc20 , solidity	3	352	March 18, 2024

Discuss adding version and copyright info to each contract in OpenZeppelin Contracts

Related topics