Contribution Guideline

contributions to treejer protocol could come in different forms some contribute code changes, others contribute docs, others help answer questions from users, help keep the infrastructure running, we welcome all contributions from folks who are willing to work in good faith with the community no contribution is too small and all contributions are valued discussions and general help as treejer is still at its early stages, drop by on discord https //discord gg/u2yustz and say hi to know what's next / to get your answers cleared up also you can find answers to many frequently asked questions (faqs) on our discussion forum our community members typically answer questions within days feedback, bugs and issues issues in treejer's github repositaries are the primary means by which bug reports, feedback and general discussions are made a contributor is invited to create an issue, discuss, and provide a fix if needed https //github com/treejer/contract https //github com/treejer/contract https //github com/treejer/web https //github com/treejer/web https //github com/treejer/mobile https //github com/treejer/mobile before opening an issue, check to see if there are any current issues with similar key words this helps us cut down on duplicate tickets when you open an issue, you'll notice three templates (bug, custom, feature) with the user story format we like for our issue reports when starting a new issue, please do your best to be as detailed and specific as possible bug report use this to create a bug report to help us improve gitcoin feature request use this to suggest a project idea custom report use this to report an issue that doesn't fall under any other category building and pull requests pull requests are the way in which concrete changes are made to the code and documentation we'll update this section with a pull request guideline after our public beta launches writing documentation the treejer ecosystem is expanding and, as a result, so is the need for documentation you can find the "official" treejer documentation here — which provides high level overviews and technical documentation whether its writing how to guides, video demos or creating diagrams on how the protocol ties together, there is something for everyone if you speak another language, translations could help as well join our discord and share your insights, so we can help you get started design we invite designers, animators, artists, and more to share your skills with the treejer ecosystem! if you're interested in creating graphics that describe treejer's systems, creating video explainers, fixing treejer's ui/ux, or any other combination of things — hop into our discord