Team Code

View code

Open Source is at it's core, a set of values. This is the standard we hold ourselves to.

If you want to be part of this effort and you agree with the following, dive in!

Our Goals

  • Deliver a clean, fast and excellent implementation of the Blaze CSS 2 components as Riot tags
  • Document the use of the tags well and clearly to speed your use of the code
  • Make the API, code, defaults, etc. as logical and simple as possible so you write less code.
  • Update dependencies, such as ChartJS reasonably regularly (there is a balance between updates and forcing changes in your code if those updates require that)

Keep Promises

Open Source is a community effort. We firmly believe in software by contract. This means that if we promise a feature it should work to the very best that it can. It also means that in every case possible, we will be backwards compatible, unless there is a damn good reason to break that promise. The only really good reason, in our view, is to improve the service the software offers you, or take advantage of new technologies.

Integrity

  • Acknowledge other sources and licenses, accurately link to the correct information
  • Provide as good a set of docs as we can to help the developer kick off faster
  • If something is broken we will say so, along with an estimate of a fix, if possible.

Our Values

Orginal version of this has been inspired by Open Code of Conduct

This code of conduct outlines our expectations for participants within the RiotGear2 community. We are committed to providing a welcoming and inspiring community for all and expect our team code to be honored.

Our open source community strives to:

  • Be friendly and patient.
  • Be welcoming: We strive to be a community that welcomes and supports people of all backgrounds and identities without exception.
  • Be considerate: Your work will be used by other people, and you in turn will depend on the work of others. Any decision you take will affect users and colleagues, and you should take those consequences into account when making decisions.
  • Remember that we’re a world-wide community, so you might not be communicating in someone else’s primary language.
  • Be respectful: Not all of us will agree all the time, but disagreement is no excuse for poor behavior and poor manners.
  • Be careful in the words that we choose: we are a community of professionals, and we conduct ourselves professionally. Be kind to others. Always.
  • Try to understand why we disagree: Disagreements, both social and technical, happen all the time. It is important that we resolve disagreements and differing views constructively.

What We Will Never Accept Here

  • Gossiping about other members: we are here to deliver a software project
  • Offensive comments related to gender, gender identity and expression, sexual orientation, disability, mental illness, neuro(a)typicality, physical appearance, body size, race, age, regional discrimination, political or religious affiliation
  • Unwelcome comments regarding a person’s lifestyle choices and practices, including those related to food, sexual preference, health, parenting, drugs, and employment
  • Physical contact and simulated physical contact (eg, textual descriptions like “hug” or “backrub”) without consent or after a request to stop
  • Threats of violence, both physical and psychological
  • Incitement of violence towards any individual, group, race, or religion
  • Sustained disruption of discussion
  • Unwelcome sexual attention, including gratuitous or off-topic sexual images or behaviour
  • Pattern of inappropriate social contact, such as requesting/assuming inappropriate levels of intimacy with others
  • Continued one-on-one communication after requests to cease

If we find our members breaking our team code repeatedly, we reserve the right to remove them from contributing.

Suggestions

If you'd like to suggest new components or enhancements to existing ones please raise an issue or talk about them in the forum.