KodaDot NFT gallery has plan to be community-owned. We are welcoming community contribution from you. Take a sneak peak on good first issues, comment and make PR. When everything went well, chances that you will be rewarded are high. For better coordination, feel free to join our Development channel -Anteriors- on Discord
Before you being:
- This site is powered by Node.js. Check to see if you're on the version of node we support.
- Have you read the code of conduct?
When you're done making changes and you'd like to propose them for review, use the pull request template to open your PR (pull request).
- Once you submit your PR, others from the Docs community will review it with you. The first thing you're going to want to do is a self review.
- After that, we may have questions, check back on your PR to keep up with the conversation.
- Did you have an issue, like a merge conflict? Check out our git tutorial on how to resolve merge conflicts and other issues.
Congratulations! The whole GitHub community thanks you. ✨
In way to scale our developemtn and operations, we prefer paid trial from start to get know developers more better, how they are fit to the team. More your PRs gets merged to main branch, more-likely you'll be part of inner team. On-demand, or part-time contributions are welcome as well and will be rewarded. Because KodaDot started on Kusama.network, we prefer pay out your work in KSM which is native cryptocurrency of Kusama network, canary network with value in Polkadot.network.
To create your KSM address in safely and long-term manner, we reccomend you to get Polkadot.js wallet browser extension. You can learn more about creating KSM address process at official Kusama Guide
During writing this, usual structure is per label on issue is
- $ - 50-100 USD
- $$ - 150-300 USD
- $$$ - 450-600 USD
You can check recent labels
After you've completed few PRs, which we're merged to the upstream, you will be eglible to join our closer team. We are happy to give you one-two long-term tasks to see how good is your talent on complicated, complex and more difficult issue. Process behind is to see if we click together as part of team in long-run. We are curious on your character, acting and helping out others if they have issue. From this phase we can guarantee you payroll, that we will private discuss based on your location, skillset, past experience and code quality delivered.
You can contribute to the GitHub Docs content and site in several ways. This repo is a place to discuss and collaborate on docs.github.com! Our small, but mighty 💪 docs team is maintaining this repo, to preserve our bandwidth, off topic conversations will be closed.
Issues are used to track tasks that contributors can help with. If an issue has a triage label, we haven't reviewed it yet and you shouldn't begin work on it.
If you've found something in the content or the website that should be updated, search open issues to see if someone else has reported the same thing. If it's something new, open an issue using a template. We'll use the issue to have a conversation about the problem you want to fix.
A pull request is a way to suggest changes in our repository.
When we merge those changes, they should be deployed to the live site within 24 hours. 🌍 To learn more about opening a pull request in this repo, see Opening a pull request below.
We are a small team working hard to keep up with the documentation demands of a continuously changing product. Unfortunately, we just can't help with support questions in this repository. If you are experiencing a problem with GitHub, unrelated to our documentation, please contact GitHub Support directly. Any issues, discussions, or pull requests opened here requesting support will be given information about how to contact GitHub Support, then closed and locked.
If you're having trouble with your GitHub account, contact Support.
Issues are very valuable to this project.
- Ideas are a valuable source of contributions others can make
- Problems show where this project is lacking
- With a question you show where contributors can improve the user experience
Thank you for creating them.
Labels can help you find an issue you'd like to help with.
The help wanted label is for problems or updates that anyone in the community can start working on. The good first issue label is for problems or updates we think are ideal for beginners.
Pull requests are, a great way to get your ideas into this repository.
When deciding if I merge in a pull request I look at the following things:
You should be clear which problem you're trying to solve with your contribution.
For example:
Add link to code of conduct in README.md
Doesn't tell me anything about why you're doing that
Add link to code of conduct in README.md because users don't always look in the CONTRIBUTING.md
Tells me the problem that you have found, and the pull request shows me the action you have taken to solve it.
$$
- There are no spelling mistakes
- It reads well
- For english language contributions: Has a good score on Grammarly or Hemingway App
We (usually the core team, sometimes KodaDot engineers or support too!) review every single PR. The purpose of reviews is to create the best content we can for people who use KodaDot
💛 Reviews are always respectful, acknowledging that everyone did the best possible job with the knowledge they had at the time.
💛 Reviews discuss content, not the person who created it.
💛 Reviews are constructive and start conversation around feedback.
You should always review your own PR first.
For content changes, make sure that you:
- Confirm that the changes address every part of the content design plan from your issue (if there are differences, explain them).
- Review the content for technical accuracy.
- Review the entire pull request using the localization checklist.
- Copy-edit the changes for grammar, spelling, and adherence to the style guide.
- Check new or updated Liquid statements to confirm that versioning is correct.
- Check that all of your changes render correctly in staging. Remember, that lists and tables can be tricky.
- If there are any failing checks in your PR, troubleshoot them until they're all passing.
When you open a pull request, you must fill out the "Ready for review" template before we can review your PR. This template helps reviewers understand your changes and the purpose of your pull request.
The aim of this repository is:
- To provide a README and assorted documents anyone can copy and paste, into their project
- The content is usable by someone who hasn't written something like this before
- Foster a culture of respect and gratitude in the open source community.
This repository has a code of conduct, This repository has a code of conduct, I will remove things that do not respect it.
Check best contributing.md