RDCIST-3750: inner sourcing docs

Author: OS-katherinebatista

docs/CODE_OF_CONDUCT.md

@@ -0,0 +1,107 @@
+# Code of Conduct
+
+## Our Commitment
+
+The **mcp-python-sdk** repository is maintained by the **Data Fabric Clients Team** and welcomes contributions from across OutSystems. We're committed to fostering an open, collaborative, and respectful environment where everyone can contribute effectively to our shared mission of building exceptional software.
+
+This Code of Conduct outlines our expectations for all contributors and participants in this inner source project.
+
+## Our Standards
+
+We encourage behaviors that contribute to a positive and productive environment:
+
+### Positive Behaviors ✓
+
+- **Be Respectful**: Treat all contributors with courtesy and professionalism, valuing diverse perspectives and experiences
+- **Communicate Constructively**: Provide thoughtful feedback, ask clarifying questions, and engage in discussions with a solutions-oriented mindset
+- **Collaborate Openly**: Share knowledge, offer help to fellow contributors, and work together towards common goals
+- **Stay Professional**: Maintain a high standard of professionalism in all interactions, whether in code reviews, issues, or discussions
+- **Accept Feedback Gracefully**: View feedback as an opportunity to improve and learn, recognizing that code reviews strengthen our collective output
+- **Give Credit**: Acknowledge the contributions and ideas of others appropriately
+
+### Unacceptable Behaviors ✗
+
+- Personal attacks, insults, or derogatory comments
+- Harassment of any kind, including unwelcome attention or inappropriate conduct
+- Publishing others' private information without explicit permission
+- Disruptive or trolling behavior in discussions, issues, or pull requests
+- Other conduct that would reasonably be considered inappropriate in a professional setting
+
+## Contribution Guidelines
+
+### Maintainer Authority
+
+The **Data Fabric Clients Team** serves as the maintainer and owner of this repository. As such:
+
+- **The Data Fabric Clients Team makes final decisions** on all contributions, including whether to accept, reject, or request modifications to pull requests
+- All architectural decisions, coding standards, and project direction are determined by the Data Fabric Clients Team
+- Contributors are expected to respect the team's decisions, even when they may differ from personal preferences
+- The Data Fabric Clients Team reserves the right to close or decline contributions that don't align with the project's goals, architecture, or quality standards
+
+### Before Contributing
+
+We encourage you to:
+
+1. **Review existing documentation**: Familiarize yourself with the project's README, architecture, and contribution guidelines
+2. **Discuss significant changes**: For major features or architectural changes, open an issue or reach out to the Data Fabric Clients Team *before* investing significant effort
+3. **Follow coding standards**: Adhere to the established coding conventions, styles, and patterns used throughout the repository
+
+### Pull Request Expectations
+
+When submitting a pull request:
+
+- Provide a clear description of the problem being solved and your approach
+- Include relevant tests and documentation
+- Ensure all CI/CD checks pass
+- Respond promptly and constructively to review feedback and questions
+- Understand that the Data Fabric Clients Team may request changes, suggest alternative approaches, or decline the contribution if it doesn't align with the project's needs
+
+### Response Times
+
+The Data Fabric Clients Team will make reasonable efforts to review contributions in a timely manner. However:
+
+- Review times may vary based on team capacity, priorities, and the complexity of the contribution
+- Contributors should be patient and understand that the team has multiple responsibilities
+- If you haven't received feedback within a reasonable timeframe, a polite reminder is acceptable
+
+## Scope
+
+This Code of Conduct applies to all spaces related to this repository, including:
+
+- GitHub repository (code, issues, pull requests, discussions)
+- Code reviews and comments
+- Related communication channels (Slack, email, meetings, Jira, Confluence)
+- Any other forums or spaces where project-related discussions occur
+
+## Enforcement
+
+### Reporting Issues
+
+If you experience or witness behavior that violates this Code of Conduct:
+
+1. Contact the **Data Fabric Clients Team** directly through appropriate OutSystems channels
+2. Provide as much detail as possible, including dates, links, and context
+3. Reports will be handled with discretion and confidentiality
+
+### Consequences
+
+The Data Fabric Clients Team will review all reports and may take action including:
+
+- Warning the individual about inappropriate behavior
+- Temporary or permanent ban from contributing to the repository
+- Escalation to OutSystems management or HR as appropriate
+- Other actions deemed necessary to maintain a healthy project environment
+
+The Data Fabric Clients Team reserves the right to remove, edit, or reject comments, commits, code, issues, and other contributions that violate this Code of Conduct.
+
+## Questions and Clarifications
+
+If you have questions about this Code of Conduct or need clarification on any aspect of contributing to this repository, please reach out to the Data Fabric Clients Team.
+
+## Acknowledgment
+
+By contributing to this repository, you acknowledge that you have read, understood, and agree to abide by this Code of Conduct, and you recognize the Data Fabric Clients Team's authority as the final decision-maker for all contributions.
+
+---
+
+**Thank you for contributing to mcp-python-sdk!** We appreciate your interest in making this project better and look forward to collaborating with you.

README.md docs/README.mdREADME.md renamed to docs/README.md

@@ -1056,7 +1056,7 @@ For a complete example with separate Authorization Server and Resource Server im
 - **Resource Server (RS)**: Your MCP server that validates tokens and serves protected resources
 - **Client**: Discovers AS through RFC 9728, obtains tokens, and uses them with the MCP server
 
-See [TokenVerifier](src/mcp/server/auth/provider.py) for more details on implementing token validation.
+See [TokenVerifier](../src/mcp/server/auth/provider.py) for more details on implementing token validation.
 
 ### FastMCP Properties
 
@@ -2099,7 +2099,7 @@ _Full example: [examples/snippets/clients/pagination_client.py](https://github.c
 - **Backward compatible** - clients that don't support pagination will still work (they'll just get the first page)
 - **Flexible page sizes** - Each endpoint can define its own page size based on data characteristics
 
-See the [simple-pagination example](examples/servers/simple-pagination) for a complete implementation.
+See the [simple-pagination example](../examples/servers/simple-pagination) for a complete implementation.
 
 ### Writing MCP Clients