! support for Youtube and Vimeo embedded videos -->
We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
Diversity is one of our huge strengths, but it can also lead to communication issues and unhappiness. To that end, we have a few ground rules that we ask people to adhere to. This code applies equally to Admins, moderators and anyone else seeking help and contribute.
This isn’t an exhaustive list of things that you can’t do. Rather, take it in the spirit in which it’s intended - a guide to make it easier to enrich all of us and the community in which we participate.
This code of conduct applies to all spaces managed by Sigma Draconis. This includes Discord, in game, the issue tracker, and any other forums created by the project team which the community uses for communication. In addition, violations of this code outside these spaces may affect a person's ability to participate within them.
If you believe someone is violating the code of conduct, we ask that you report it by Contacting an Administrator, or by emailing [email protected]
We view equity and inclusion as foundational elements to our culture, our success, and our ability to realize our purpose. We understand that:
We want to make people from all groups and backgrounds feel comfortable belonging to our team and community. You should understand that diversity is having a seat at the table, inclusion is having a voice, and belonging is having that voice be heard.
We prefer to build teams, not workgroups. A team has a small number of shared goals that team members work on together. This yields collaboration and focus, which helps us do higher-quality things faster. In contrast, a workgroup is a group of people who are each working on their own things.
As a team’s size and scope grows, it (unintentionally) tends to become a workgroup. Resist this by aggressively focusing, or by splitting it into smaller teams.
Everyone at Sigma Draconis has the power and the responsibility to improve Sigma Draconis as an organization and as a service. High Agency is a sense that the story given to you by other people about what you can/cannot do is just that - a story. And that you have control over the story. A person demonstrating high agency looks to bend reality to their will. They either find a way, or they make a way. A low agency person accepts the story that is given to them.
“Life can be much broader once you discover one simple fact: Everything around you that you call life was made up by people that were no smarter than you and you can change it, you can influence it, you can build your own things that other people can use. Once you learn that, you’ll never be the same again.” - Steve Jobs
With agency comes responsibility; teammates are expected to take initiative and engage in collaboration when exercising their agency. If you feel that something is important, then advocate for it! If you feel like you’re using the wrong tools for the job or doing the wrong thing, then you’re responsible for quickly voicing that concern, and engaging with your teammates to find the solution that is the best for the team. Do not ever assume or wait for top-down change. If something is broken for you or your team, then fix it for you or your team, and then share that fix in case other individuals or teams have the same problem.
This doesn’t mean that you should make unilateral decisions. As an open organization, we value open discussion on important topics, and think that collaboration should be a large part of making things better. It is not a bad outcome if your proposal is not accepted or replaced with a better solution, because you took the initiative, started the conversation, and either reaffirmed that our current solution is good, or implemented an even better one!
You are responsible for finding out what high-quality work looks like and delivering that high-quality work iteratively.
If we discover that we’ve produced something that does not meet our quality bar, we’ll roll it back (for example, revert a commit, roll back a release, or unpublish content) until we can make it high quality. If that’s not possible, we’ll prioritize improving it.
High-quality isn’t the opposite of iterative. You can keep quality high while still being iterative by narrowing the scope (for example, by solving a smaller problem at first, or by solving it only for certain players initially).