forked from DigiLive/mushroom-strategy
Ferry Cools
a5ec18823d
Adds: - Strategy: - SceneCard: Support for Stateful scenes. Closes #190. - ValveCard: A card to control an entity of the valve domain. Closes #192. - LockView: A view for entities of the lock domain. Closes #171. - Modules: - RegistryFilter: Advanced filtering and sorting of Home Assistant registries. - Auxiliaries: Generic utility functions. - Debug: Centralized logging and debug level management. - Tooling: - ESLint configuration for linting. - Prettier configuration for code formatting. Removes: - Redundant types and interface annotations. - Redundant legacy and unused modules. - Localization constant from the `Helper` module in favor of a new `localize` utility. Refactors: - References regarding change of repository owner. - Auxiliary functions are moved from the `Helper` module to `Auxiliaries` module. - `Helper` module is renamed to `Registry` for centralized state and registry management. - `ControllerCard` is renamed to `HeaderCard`. - Doc-blocks and comments are updated for clarity and consistency. - The file tree is restructured for improved clarity, modularity, and scalability. - Third party type definitions are updated and cleaned up. - Issue and Pull Request templates. Optimizations: - Parallelization of dynamic imports for views and cards. - Improved error handling and logging throughout the codebase. - Sanitization of HASS registries after import. - Enforced stricter and simplified types and interfaces. - Localization now available at global scope. Fixes: - Wrong type in configuration of `HeaderCard`. - Translation files: Resolved key inconsistencies. - Removed unnecessary namespaces from types. - Typos and Grammar. - Explicit use of `any` types. - Turn off all entities of a domain with a chip tap action. - Rendering too small HASS area cards. - Count of active vacuums. Bumps: - Mushroom Strategy - home-assistant-js-websocket - superstruct - ts-loader - ts-node - typescript - webpack - webpack-cli
95 lines
4.8 KiB
Markdown
95 lines
4.8 KiB
Markdown
# Code of Conduct—Mushroom Strategy
|
|
|
|
## Our Pledge
|
|
|
|
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make
|
|
participation in our project and our community a harassment-free experience for everyone.
|
|
This is regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression,
|
|
level of experience, education, socioeconomic status, nationality, personal appearance, race, religion, or
|
|
sexual identity and orientation.
|
|
|
|
## Our Standards
|
|
|
|
Examples of behavior that contributes to a positive environment for our community include:
|
|
|
|
* Demonstrating empathy and kindness toward other people.
|
|
* Being respectful of differing opinions, viewpoints, and experiences.
|
|
* Giving and gracefully accepting constructive feedback.
|
|
* Accepting responsibility and apologizing to those affected by our mistakes and learning from the experience.
|
|
* Focusing on what is best not just for us as individuals, but for the overall community.
|
|
|
|
Examples of unacceptable behavior include:
|
|
|
|
* The use of sexualized language or imagery, and sexual attention or advances.
|
|
* Trolling, insulting or derogatory comments, and personal or political attacks.
|
|
* Public or private harassment.
|
|
* Publishing private information of others, such as a physical or email address, without their explicit permission.
|
|
* Another conduct which could reasonably be considered inappropriate in a professional setting.
|
|
|
|
## Our Responsibilities
|
|
|
|
Project maintainers are responsible for clarifying and enforcing our standards of acceptable behavior and will take
|
|
appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive,
|
|
or harmful.
|
|
|
|
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits,
|
|
issues, and other contributions that are not aligned to this Code of Conduct and will communicate reasons for moderation
|
|
decisions when appropriate.
|
|
|
|
## Scope
|
|
|
|
This Code of Conduct applies within all community spaces and also applies when an individual is officially representing
|
|
the community in public spaces. Examples of representing our community include using an official e-mail address, posting
|
|
via an official social media account, or acting as an appointed representative at an online or offline event.
|
|
|
|
## Enforcement
|
|
|
|
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible
|
|
for enforcement. All complaints will be reviewed and investigated promptly and fairly.
|
|
|
|
All community leaders are obligated to respect the reporter's privacy and security of any incident.
|
|
|
|
## Enforcement Guidelines
|
|
|
|
Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem
|
|
in violation of this Code of Conduct:
|
|
|
|
### 1. Correction
|
|
|
|
**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the
|
|
community.
|
|
|
|
**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation
|
|
and an explanation of why the behavior was inappropriate. A public apology may be requested.
|
|
|
|
### 2. Warning
|
|
|
|
**Community Impact**: A violation through a single incident or series of actions.
|
|
|
|
**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including
|
|
unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding
|
|
interactions in community spaces as well as external channels like social media. Violating these terms may lead to a
|
|
temporary or permanent ban.
|
|
|
|
### 3. Temporary Ban
|
|
|
|
**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
|
|
|
|
**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified
|
|
period of time. No public or private interaction with the people involved, including unsolicited interaction with those
|
|
enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
|
|
|
|
### 4. Permanent Ban
|
|
|
|
**Community Impact**: Demonstrating violations of community standards, including sustained inappropriate
|
|
behavior, harassment of an individual, or aggression toward or disparagement of their class.
|
|
|
|
**Consequence**: A permanent ban from any sort of public interaction within the community.
|
|
|
|
## Attribution
|
|
|
|
This Code of Conduct is adapted from the [Contributor Covenant](https://contributor-covenant.org/), version
|
|
[1.4](https://www.contributor-covenant.org/version/1/4/code-of-conduct/code_of_conduct.md) and
|
|
[2.0](https://www.contributor-covenant.org/version/2/0/code_of_conduct/code_of_conduct.md),
|
|
and was generated by [contributing-gen](https://github.com/bttger/contributing-gen).
|