Repo Hygiene

.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -0,0 +1,85 @@
+name: Bug Report
+description: Report a bug or an unexpected behavior
+labels: ["bug", "needs-triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to file a bug report!
+        Please read the [Contributing Guidelines](CONTRIBUTING.md) before submitting.
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: A clear and concise description of what the bug is.
+      placeholder: Describe the bug here.
+    validations:
+      required: true
+  - type: textarea
+    id: reproduction-steps
+    attributes:
+      label: Steps to Reproduce
+      description: |
+        Provide clear steps to reproduce the behavior.
+        Please include code snippets, configurations, or detailed commands if relevant.
+      placeholder: |
+        1. Go to '...'
+        2. Run cmd '....'
+        3. View file '....'
+        4. See error
+    validations:
+      required: true
+  - type: textarea
+    id: expected-behavior
+    attributes:
+      label: Expected Behavior
+      description: A clear and concise description of what you expected to happen.
+      placeholder: What did you expect to happen?
+    validations:
+      required: true
+  - type: textarea
+    id: actual-behavior
+    attributes:
+      label: Actual Behavior
+      description: A clear and concise description of what actually happened.
+      placeholder: What actually happened?
+    validations:
+      required: true
+  - type: textarea
+    id: environment
+    attributes:
+      label: Environment
+      description: Provide details about your environment.
+      value: |
+        - **OS:** [e.g. macOS, Windows, Linux] (and version)
+        - **mcpd Version:** [e.g. v0.0.2] (mcpd --version)
+        - **mcpd Python SDK Version:** [e.g. 0.0.1]
+        - **Other relevant libraries/versions:**
+      render: markdown
+    validations:
+      required: false
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant Log Output
+      description: |
+        If applicable, paste any relevant log and terminal output, error messages, or screenshots.
+        Please wrap code blocks in triple backticks (```).
+      render: shell
+    validations:
+      required: false
+  - type: checkboxes
+    id: self-checklist
+    attributes:
+      label: Self-Checklist
+      options:
+        - label: I have read the [Contributing Guidelines](CONTRIBUTING.md).
+          required: true
+        - label: I have searched the existing issues and found no duplicate.
+          required: true
+        - label: I have provided a clear and concise description of the bug.
+          required: true
+        - label: I have provided clear steps to reproduce the bug.
+          required: true
+        - label: I have provided details about my environment.
+          required: true

.github/ISSUE_TEMPLATE/config.yaml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Report a security vulnerability
+    url: https://github.com/mozilla-ai/mcpd-sdk-python/security/policy
+    about: Please report security vulnerabilities responsibly.

.github/ISSUE_TEMPLATE/feature_request.yaml

@@ -0,0 +1,54 @@
+name: Feature Request
+description: Suggest an idea or enhancement for the project.
+labels: ["enhancement", "needs-triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for suggesting an idea!
+        Please read the [Contributing Guidelines](CONTRIBUTING.md) before submitting.
+  - type: textarea
+    id: problem-description
+    attributes:
+      label: Is your feature request related to a problem? Please describe.
+      description: A clear and concise description of the problem you're trying to solve. e.g. "I'm always frustrated when [...]"
+      placeholder: Describe the problem.
+    validations:
+      required: true
+  - type: textarea
+    id: solution-description
+    attributes:
+      label: Describe the solution you'd like
+      description: A clear and concise description of what you want to happen.
+      placeholder: Describe the solution.
+    validations:
+      required: true
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Describe alternatives you've considered
+      description: A clear and concise description of any alternative solutions or features you've considered.
+      placeholder: Describe alternatives.
+    validations:
+      required: false
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional Context
+      description: Add any other context or screenshots about the feature request here.
+      placeholder: Any additional information.
+    validations:
+      required: false
+  - type: checkboxes
+    id: self-checklist
+    attributes:
+      label: Self-Checklist
+      options:
+        - label: I have read the [Contributing Guidelines](CONTRIBUTING.md).
+          required: true
+        - label: I have searched the existing issues and found no duplicate.
+          required: true
+        - label: I have provided a clear and concise description of the problem.
+          required: true
+        - label: I have provided a clear and concise description of the proposed solution.
+          required: true

.pre-commit-config.yaml

@@ -13,7 +13,7 @@ repos:
 
   - repo: https://github.com/astral-sh/ruff-pre-commit
     # Ruff version.
-    rev: v0.11.6
+    rev: "v0.12.4"
     hooks:
       # Run the linter.
       - id: ruff
@@ -24,7 +24,7 @@ repos:
 
   - repo: https://github.com/astral-sh/uv-pre-commit
     # uv version.
-    rev: 0.6.14
+    rev: 0.8.0
     hooks:
       # Update the uv lockfile
       - id: uv-lock

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, 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.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* 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 by participants 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. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the team at mozilla.ai. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and 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][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,60 @@
+# Contributing to Mozilla.ai `mcpd-sdk-python`
+
+Thank you for your interest in contributing to the `mcpd` project! This project supports the mozilla.ai goal of empowering developers to integrate AI capabilities into their projects using open-source tools and models.
+
+We welcome all kinds of contributions, from improving customization, to extending capabilities, to fixing bugs. Whether you’re an experienced developer or just starting out, your support is highly appreciated.
+
+By contributing to this project, you agree to abide by our [Code of Conduct](CODE_OF_CONDUCT.md).
+
+---
+
+## **How to Contribute**
+
+### **Customize for your use-case or Extend It** 🔧
+- Fork this repo and customize it for your own use-case or even extend its capabilities.
+- We'd love to see what you've built!
+
+### **Browse Existing Issues** 🔍
+- Check the Issues page to see if there are any tasks you'd like to tackle.
+- Look for issues labeled **`good first issue`** if you're new to the project—they're a great place to start.
+
+### **Report Issues** 🐛
+- Found a bug? Open a Bug Report by clicking on 'New Issue'
+- Provide as much detail as possible, including the steps to reproduce the issue and expected vs. actual behavior
+
+### **Suggest Features** 🚀
+- Have an idea for improving the project? Open a Feature Request by clicking on 'New Issue'
+- Share why the feature is important and any alternative solutions you’ve considered.
+
+### **Submit Pull Requests** 💻
+- Fork the repository and create a new branch for your changes.
+- Install [pre-commit](https://pre-commit.com/) to ensure the code is formatted and standardized correctly, by running `uv sync --group lint` and then `pre-commit install`.
+- Ensure your branch is up-to-date with the main branch before submitting the PR
+- Please follow the PR template, adding as much detail as possible, including how to test the changes
+
+---
+
+### **Guidelines for Contributions**
+
+**Coding Standards**
+- Follow PEP 8 for Python formatting.
+- Use clear variable and function names and add comments to improve readability.
+
+**Testing**
+- Test changes locally to ensure functionality.
+- Install the package using development dependencies before testing: `uv sync --group dev`
+
+**Documentation**
+- Update docs for changes to functionality and maintain consistency with existing docs.
+
+---
+
+## Security Vulnerabilities
+
+If you discover a security vulnerability, please **DO NOT** open a public issue. Report it responsibly by following our [Security Policy](SECURITY.md).
+
+---
+
+## License
+
+By contributing, you agree that your contributions will be licensed as described in [LICENSE](LICENSE.md).