This project is maintained by Newt, checkout out our website for details about the Newt Community with instructions for joining and getting involed
Newt welcomes contributions in all areas: code, ideas, documentation, marketing, and anything else to help the community grow and thrive
A list of tasks can be found on the Newt homepage under the Task List section.
Contributions will mainly be coordinated through the project Discord channel #tokenized-time-nfts. Technical contributions also be coordinated through the GitHub issues tab
To report a bug, create a new issue with bug label. When submitting a bug, please check that issue does not already exist, and provide all relevant details to for reproducing the bug
To submit a feature request, whether you plan to build it yourself or not, it's usually best to get feedback in order to scope the task requirements. To get feedback, create a new issue with the feedback label with the feature details, and also reach out in the Discord working channel #tokenized-time-nfts.
Some questions to address:
- Will this change require a modification to the smart contracts?
- A good idea would be to check the subgraph playground to see if the required data fields already exist
- Will a design be required for frontend changes?
Here is the branch layout for a new feature requiring a change accross multiple packages:
feature/add-field-subgraph \
feature/add-field-contracts -> feature/add-field -> staging -> main
feature/add-field-frontend /
All pull requests to main require approval from at least 2 members of the Newt core team