Skip to main content
Glama

AnyDocs MCP Server

by funky1688
CODE_OF_CONDUCT.mdโ€ข12.8 kB
# 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, caste, color, 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 * Using welcoming and inclusive language * Being patient with newcomers and those learning * Sharing knowledge and helping others grow * Celebrating the success of others * Providing constructive criticism in a respectful manner 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 * Spamming or excessive self-promotion * Deliberately intimidating, stalking, or following * Advocating for, or encouraging, any of the above behavior * Repeated inappropriate contact after requests to cease * Making threats of violence or using violent language ## Community Guidelines ### Communication * **Be Clear and Concise**: Write clear, well-structured messages that are easy to understand * **Stay On Topic**: Keep discussions relevant to the project and community * **Use Appropriate Channels**: Use the right communication channel for your message * **Be Patient**: Remember that people are in different time zones and may not respond immediately * **Ask Good Questions**: Provide context, show what you've tried, and be specific ### Collaboration * **Share Knowledge**: Help others learn and grow by sharing your expertise * **Give Credit**: Acknowledge the contributions of others * **Be Open to Feedback**: Accept constructive criticism gracefully * **Collaborate Effectively**: Work together towards common goals * **Respect Different Perspectives**: Value diverse viewpoints and experiences ### Technical Discussions * **Focus on Technical Merit**: Evaluate ideas based on their technical value * **Provide Evidence**: Support your arguments with facts, data, or examples * **Be Constructive**: Offer solutions, not just criticism * **Admit Mistakes**: Everyone makes mistakes; learn from them and move on * **Stay Current**: Keep up with best practices and evolving standards ### Mentorship * **Welcome Newcomers**: Help new contributors feel welcome and supported * **Be Patient**: Remember that everyone was a beginner once * **Provide Guidance**: Offer helpful resources and direction * **Encourage Growth**: Support others in developing their skills * **Lead by Example**: Demonstrate the behavior you want to see ## 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. This includes: * **GitHub Repository**: Issues, pull requests, discussions, and code comments * **Communication Channels**: Any official communication platforms * **Events**: Conferences, meetups, and other community events * **Social Media**: When representing the project or community * **External Platforms**: When discussing the project on other platforms ## Reporting Guidelines ### How to Report Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at **conduct@anydocs-mcp.com**. All complaints will be reviewed and investigated promptly and fairly. ### What to Include When reporting an incident, please include: * **Your Contact Information**: So we can follow up with you * **Details of the Incident**: What happened, when, and where * **Additional Context**: Any relevant background information * **Evidence**: Screenshots, links, or other supporting materials * **Impact**: How the incident affected you or others * **Desired Outcome**: What resolution you're seeking ### Reporting Process 1. **Submit Report**: Send your report to conduct@anydocs-mcp.com 2. **Acknowledgment**: We'll acknowledge receipt within 24 hours 3. **Investigation**: We'll investigate the incident thoroughly 4. **Decision**: We'll make a decision based on our findings 5. **Communication**: We'll communicate the outcome to relevant parties 6. **Follow-up**: We'll follow up to ensure the issue is resolved ### Confidentiality All community leaders are obligated to respect the privacy and security of the reporter of any incident. We will: * **Keep Reports Confidential**: Only share information with those who need to know * **Protect Reporter Identity**: We won't reveal your identity without permission * **Secure Information**: Store reports securely and delete them when appropriate * **Respect Privacy**: Respect the privacy of all parties involved ## 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. ## Appeals Process If you believe you have been unfairly penalized, you may appeal the decision by: 1. **Submit Appeal**: Send an email to appeals@anydocs-mcp.com within 30 days 2. **Provide Information**: Include relevant details and new information 3. **Review Process**: An independent review will be conducted 4. **Decision**: A final decision will be communicated within 14 days ## Community Leadership ### Roles and Responsibilities **Project Maintainers**: * Enforce the Code of Conduct * Make final decisions on enforcement actions * Provide guidance to the community * Set the tone for community interactions **Community Moderators**: * Monitor community spaces for violations * Respond to reports of misconduct * Provide initial guidance and warnings * Escalate serious issues to maintainers **Community Members**: * Follow the Code of Conduct * Report violations when observed * Support and welcome newcomers * Contribute positively to the community ### Leadership Expectations Community leaders are expected to: * **Model Behavior**: Demonstrate the standards we expect from others * **Be Fair**: Apply rules consistently and without bias * **Be Transparent**: Communicate decisions and reasoning clearly * **Be Responsive**: Address issues promptly and effectively * **Be Accountable**: Take responsibility for their actions and decisions ## Positive Community Building ### Encouraging Participation * **Welcome New Contributors**: Make newcomers feel valued and supported * **Recognize Contributions**: Acknowledge and celebrate community contributions * **Provide Mentorship**: Help others develop their skills and knowledge * **Create Opportunities**: Offer ways for people to get involved * **Foster Inclusion**: Ensure everyone feels welcome and included ### Building Relationships * **Get to Know Each Other**: Take time to understand community members * **Show Appreciation**: Express gratitude for others' contributions * **Celebrate Success**: Acknowledge achievements and milestones * **Support During Challenges**: Offer help when others are struggling * **Build Trust**: Be reliable, honest, and consistent ### Knowledge Sharing * **Document Processes**: Make it easy for others to contribute * **Share Expertise**: Teach others what you know * **Ask Questions**: Don't be afraid to seek help or clarification * **Provide Resources**: Share helpful tools, links, and information * **Learn Together**: Embrace opportunities for mutual learning ## Resources ### Getting Help * **Documentation**: Comprehensive guides and references * **Community Discussions**: Ask questions and get help from others * **Issue Tracker**: Report bugs and request features * **Code of Conduct Team**: Contact us for conduct-related issues ### Educational Resources * [Inclusive Language Guide](https://inclusivenaming.org/) * [Ally Skills Workshop](https://frameshiftconsulting.com/ally-skills-workshop/) * [Open Source Diversity](https://opensourcediversity.org/) * [Community Building Resources](https://opensource.guide/building-community/) ### Support Organizations * [Open Source Diversity](https://opensourcediversity.org/) * [NumFOCUS DISC](https://numfocus.org/programs/diversity-inclusion) * [Outreachy](https://www.outreachy.org/) * [Google Summer of Code](https://summerofcode.withgoogle.com/) ## Acknowledgments This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1]. Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC]. For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations]. [homepage]: https://www.contributor-covenant.org [v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html [Mozilla CoC]: https://github.com/mozilla/diversity [FAQ]: https://www.contributor-covenant.org/faq [translations]: https://www.contributor-covenant.org/translations ## Contact Information * **Code of Conduct Team**: conduct@anydocs-mcp.com * **Appeals**: appeals@anydocs-mcp.com * **General Questions**: community@anydocs-mcp.com --- **Last Updated**: January 2024 **Version**: 2.1 This Code of Conduct is a living document and may be updated as our community grows and evolves.

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/funky1688/AnyDocs-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server