Wysc is an open project always looking for contributors!
🎉 The Wysc experience would not be possible without the many user contributions and services we have come to rely on:
If you’re a Seed or Sprout, you can help by sharing Wysc with your friends! Knowing that we can be helpful not only to you, but also your friends, is a grand honor.
See more info by typing ,bump in #bots-spam
Our social media accounts are not maintained right now. If you’re in Contributor Hub, let us know if you’d like to help run them!
The most popular way for those Treeling rank and above to help contribute to Wysc is by suggesting feature updates, bug fixes, and commenting on new features before they release to the public!
Some contributors may be invited to become a Pond and contribute to behind-the-scenes administrative Wysc decisions.
To join Contributor Hub, you need to be at least Sapling rank. #ch-info will then appear, which lets you join!
If you know how GitHub works, feel free to directly help by making pull requests! Our documentation is written in Markdown.
Here are some things we’re always looking for help on:
For bigger contributions, we recommend you contact us first, either in Contributor Hub or #support. GitHub Issues are monitored, but may have a delayed response.
Our site’s a bit barebones at the moment, but we do have some APIs if you ever feel like playing with them:
Contributions are generally governed by our default Partner License, which allows us to use your contributions productively while still allowing you to retain ownership rights over your contributions. Special partner licenses may be arranged on a case-by-case basis.
All contributions on GitHub are attributed by your GitHub user.
We are working on a way to incorporate user contributions into the Credits page, and will update this page when we have more updates.