change community files

CODE_OF_CONDUCT.md

@@ -1,60 +1,3 @@
 # Code of Conduct
 
-## 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, 
-regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, 
-personal appearance, race, religion, or sexual identity and orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment include:
-
-- Being respectful of differing viewpoints and experiences
-- Gracefully accepting constructive criticism
-- Focusing on what is best for the community
-- Showing empathy towards other community members
-
-Examples of unacceptable behavior include:
-
-- The use of sexualized language or imagery, and unwelcome sexual attention or advances
-- Trolling, insulting/derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others' private information, such as a physical or electronic address, without explicit permission
-- Other conduct which could reasonably be considered inappropriate in a professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected 
-to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
-
-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, 
-or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. 
-Examples of representing a project or community include using an official project 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 by contacting the project team 
-at [[email protected]](mailto:[email protected]). 
-The project team will review and investigate all complaints and will respond in a way that it deems appropriate to the circumstances. 
-The project team is obligated to maintain confidentiality with regard to the reporter of an incident. 
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent 
-repercussions as determined by other members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), 
-version 1.4, available 
-at [https://www.contributor-covenant.org/version/1/4/code-of-conduct.html](https://www.contributor-covenant.org/version/1/4/code-of-conduct.html)
-
-For answers to common questions about this code of conduct, 
-see [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq)
+FindSimilar [Code Of Conduct](https://github.com/findsimilar/community/blob/main/CODE_OF_CONDUCT.md)

GOVERNANCE.md

@@ -1,20 +1,3 @@
 # Governance
 
-## Project Roles
-
-- **Maintainers**: Individuals responsible for overseeing the project's development, 
-merging contributions, and ensuring adherence to project standards.
-- **Contributors**: Individuals who actively participate in the project by submitting code, documentation, 
-or other valuable contributions.
-- **Community Managers**: Individuals responsible for community engagement, handling issues, organizing events, 
-and fostering a positive environment.
-- **Reviewers**: Individuals responsible for code reviews, ensuring the quality and adherence to project 
-standards before merging contributions.
-
-## Decision-Making Processes
-
-- **Consensus-Based Decision-Making**: Major decisions are made through discussion, and consensus is reached 
-among maintainers and contributors.
-- **Voting**: Certain decisions might involve voting among project members, with a majority determining the outcome.
-- **Benevolent Dictatorship**: A single individual (usually the project founder) makes final decisions, 
-often with input from the community.
+FindSimilar [Governance](https://github.com/findsimilar/community/blob/main/GOVERNANCE.md)

SECURITY.md

@@ -1,8 +1,3 @@
 # Security Policy
 
-## Vulnerability Reporting
-We provide a clear process for reporting security vulnerabilities. 
-
-If you discover a security issue, please **do not** create an issue on GitHub.
-Instead, please email us at [[email protected]](mailto:[email protected]). 
-We will acknowledge your report, conduct an investigation, and work on a resolution.
+FindSimilar [Security](https://github.com/findsimilar/community/blob/main/SECURITY.md)

SUPPORT.md

@@ -1,27 +1,3 @@
 # Support
 
-## Financial Contributions
-
-- **One-Time Donations**: Individuals can make a one-time financial contribution to support the project.
-- **Recurring Donations**: Setting up monthly or yearly donations to provide ongoing support.
-- **Crowdfunding Campaigns**: Organizing campaigns on platforms like Kickstarter or Patreon to fund specific project goals.
-
-## Non-Monetary Support
-
-- **Volunteering**: Offering time and skills to help with coding, documentation, design, or other project needs.
-- **Advocacy**: Spreading the word about the project through social media, blogs, or presentations.
-- **Bug Reporting**: Actively testing the project and reporting bugs or issues.
-- **Answering Questions**: Providing support by answering questions on forums, mailing lists, or community platforms.
-- **Translation**: Translating project documentation or content into different languages to broaden its reach.
-
-## Technical Expertise:
-
-- **Code Contributions**: Writing code, fixing bugs, or adding new features to the project.
-- **Code Reviews**: Conducting thorough code reviews to maintain code quality and adherence to project standards.
-- **Security Audits**: Assisting in identifying and resolving security vulnerabilities within the project.
-
-## Community Building:
-
-- **Organizing Events**: Hosting meetups, webinars, or conferences to bring the community together.
-- **Mentorship: Providing**: mentorship to newcomers and guiding them through the project's intricacies.
-- **Documentation**: Writing and improving project documentation to make it more accessible and user-friendly.
+FindSimilar [Support](https://github.com/findsimilar/community/blob/main/SUPPORT.md)