项目的一些说明文件 ​

# 版本更新

## v0.0.5

- 配置更新后筛选问题。
- 添加第一次安装会先配置背景一次，如果有相关配置。

## v0.0.4

- 解决一些 bug。
- 添加可视化配置页面。

## v0.0.3

- 使用文件保存背景样式。

## v0.0.2

- 优化 README 文档。
- 在取消激活插件时清理背景。

## v0.0.1

- 发布。

# Contributor Covenant Code of Conduct

## Our Pledge

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.

## 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 of any kind
- Trolling, insulting or derogatory comments, and personal or political attacks
- Public or private harassment
- Publishing others' private information, such as a physical or email address, without their explicit permission
- Other conduct which could reasonably be considered inappropriate in a professional setting

## Enforcement Responsibilities

Community leaders 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.

Community leaders 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 privacy and security of the reporter 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 a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.

**Consequence**: A permanent ban from any sort of public interaction within the community.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0, available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.

Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).

[homepage]: https://www.contributor-covenant.org

For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

# Contributing to [projectName]

We welcome contributions to our project. This guide will help you get started.

## Code of Conduct

Our project follows a Code of Conduct. Please review it before contributing.

## Getting Started

1. **Familiarize yourself with the project**: Read the README and any other documentation.
2. **Set up your development environment**: Follow the instructions in the README to install dependencies and get the project running locally.

## How to Contribute

### Reporting Bugs

1. **Check the issue tracker**: Make sure the bug hasn't already been reported.
2. **Isolate the problem**: Try to create a minimal, reproducible test case.
3. **Submit a detailed issue report**: Include the details of your environment, steps to reproduce, and the actual vs. expected outcomes.

### Suggesting Enhancements

1. **Check the issue tracker**: Make sure the enhancement hasn't already been suggested.
2. **Discuss your idea**: Open an issue to discuss the enhancement with the community and maintainers.
3. **Submit a detailed enhancement proposal**: Include use cases, benefits, and potential drawbacks.

### Your First Code Contribution

1. **Find a good first issue**: Look for issues labeled "good first issue" or "help wanted."
2. **Comment on the issue**: Let others know you're interested in working on it.
3. **Fork the repository**: Create your own copy of the project to work on.
4. **Make your changes**: Write code to address the issue.
5. **Test your changes**: Ensure your changes don't break existing functionality.
6. **Submit a pull request**: Push your changes to your fork and submit a pull request to the original repository.

### Pull Requests

1. **Follow the coding style**: Consistency is key.
2. **Document your code**: Include comments and update any relevant documentation.
3. **Write a clear commit message**: Describe what changes were made and why.
4. **Rebase your branch**: Keep your changes up-to-date with the main branch.
5. **Respond to feedback**: Be open to feedback and make changes as necessary.

### Code Reviews

1. **Be open to feedback**: Code reviews are an opportunity for improvement.
2. **Be respectful**: Treat all contributors with respect.
3. **Be thorough**: Review changes carefully to ensure they meet the project's standards.

Thank you for your interest in contributing to [projectName]!

BSD 2-Clause License

Copyright (c) [year], [userName]

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

# Security Policy

This document outlines the security policy for the project.

## Reporting a Vulnerability

We take the security of our project seriously. If you discover a security vulnerability, we appreciate your help in disclosing it to us in a responsible manner.

### How to Report

**Creat a isssue**: Include the following details in your report:

- A description of the vulnerability.
- Steps to reproduce the issue.
- Potential impact of the vulnerability.
- Any potential fixes or mitigations you have in mind.

## Supported Versions

| Version | Supported          |
| ------- | ------------------ |
| 0.0.5   | :white_check_mark: |
| 0.0.4   | :x:                |

## Security Update Policy

When a security vulnerability is reported and confirmed, we will:

1. **Verify the vulnerability**: Assess the impact and severity.
2. **Develop a fix**: Create a patch to address the vulnerability.
3. **Release the fix**: Publish the patch and update the affected versions.
4. **Notify users**: Inform users about the vulnerability and the available fix.

## Acknowledgments

We would like to thank the following individuals and organizations for reporting security vulnerabilities:

**Note**: This security policy may be updated at any time. Please check back regularly for updates.