OpenZeppelin / OpenZeppelin/compact-contracts
Document Development Process
Open
Nobody has claimed this yet.
documentation
- Dominant language
- TypeScript
- Stars
- 55
- Forks
- 29
- Avg merge
- 5d 7h
- Merged PRs (30d)
- 25
Description
Developers are expected to copy and paste contracts into their projects. This is a non-standard approach to smart contract development and should be documented in our repo.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or documentation entry point is named in the issue. Start by finding the repository’s existing documentation structure and guidance around copying contracts. Document the expected copy-and-paste workflow for smart contract development; done means developers can find and follow this process in the repo.
Written by the indexing model from the issue text.
Assessment
- Domain
- blockchain, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100