Microsoft open source compliance: policy docs, license, and trademark notice

CODE_OF_CONDUCT.md

@@ -1,128 +1,10 @@
-# Contributor Covenant Code of Conduct
+# Microsoft Open Source Code of Conduct
 
-## Our Pledge
+This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
 
-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.
+Resources:
 
-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 by opening an issue
-in the repository labeled "Code of Conduct Violation".
-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.
+- [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/)
+- [Microsoft Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/)
+- Contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with questions or concerns
+- Employees can reach out at [aka.ms/opensource/moderation-support](https://aka.ms/opensource/moderation-support)

CONTRIBUTING.md

@@ -44,11 +44,11 @@ Enhancement suggestions are welcome! Please:
 ### Pull Request Process
 
 1. **Choose the appropriate PR template** for your change:
-   - **🚀 New Feature**: [Create Feature PR](https://github.com/danielmeppiel/apm/compare/main...HEAD?template=feature.md)
-   - **🐛 Bug Fix**: [Create Bug Fix PR](https://github.com/danielmeppiel/apm/compare/main...HEAD?template=bugfix.md)  
-   - **📖 Documentation**: [Create Docs PR](https://github.com/danielmeppiel/apm/compare/main...HEAD?template=documentation.md)
-   - **🔧 Maintenance**: [Create Maintenance PR](https://github.com/danielmeppiel/apm/compare/main...HEAD?template=maintenance.md)
-   - **Other**: [Create Standard PR](https://github.com/danielmeppiel/apm/compare/main...HEAD)
+   - **🚀 New Feature**: Use the `feature.md` template
+   - **🐛 Bug Fix**: Use the `bugfix.md` template
+   - **📖 Documentation**: Use the `documentation.md` template
+   - **🔧 Maintenance**: Use the `maintenance.md` template
+   - **Other**: Use the standard PR template
 
 2. **Apply the correct label** after creating your PR:
    - `enhancement` or `feature` - New functionality
@@ -70,8 +70,8 @@ This project uses uv to manage Python environments and dependencies:
 
 ```bash
 # Clone the repository
-git clone https://github.com/danielmeppiel/apm-cli.git
-cd apm-cli
+git clone <this-repo-url>
+cd apm
 
 # Create a virtual environment and install dependencies
 uv venv

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2025 Daniel Meppiel
+Copyright (c) Microsoft Corporation.
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

README.md

@@ -222,3 +222,7 @@ For private packages, Azure DevOps, or running prompts via AI runtimes:
 
 **Learn AI-Native Development** → [Awesome AI Native](https://danielmeppiel.github.io/awesome-ai-native)  
 A practical learning path for AI-Native Development, leveraging APM along the way.
+
+## Trademarks
+
+This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow [Microsoft's Trademark & Brand Guidelines](https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks/usage/general). Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.

SECURITY.md

@@ -1,42 +1,14 @@
-# Security Policy
+<!-- BEGIN MICROSOFT SECURITY.MD V1.0.0 BLOCK -->
 
-## Supported Versions
+## Security
 
-Currently supported versions with security updates:
+Microsoft takes the security of our software products and services seriously, which
+includes all source code repositories in our GitHub organizations.
 
-| Version | Supported          |
-| ------- | ------------------ |
-| 0.1.x   | :white_check_mark: |
+**Please do not report security vulnerabilities through public GitHub issues.**
 
-## Reporting a Vulnerability
+For security reporting information, locations, contact information, and policies,
+please review the latest guidance for Microsoft repositories at
+[https://aka.ms/SECURITY.md](https://aka.ms/SECURITY.md).
 
-We take security bugs seriously. We appreciate your efforts to responsibly disclose your findings.
-
-**Please use GitHub's Private Vulnerability Reporting:**
-
-1. Navigate to the **Security** tab of this repository
-2. Click **"Report a vulnerability"**
-3. Fill out the advisory form with:
-   - Vulnerability description and impact
-   - Steps to reproduce
-   - Your recommended fix (if any)
-4. Click **"Submit report"**
-
-Your report will be privately shared with the maintainers. We will:
-- Acknowledge receipt
-- Send a detailed response
-- Work with you to fix and coordinate disclosure
-
-**DO NOT** file public issues for security vulnerabilities.
-
-For more information, see [GitHub's Private Vulnerability Reporting documentation](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability).
-
-## Security Best Practices
-
-When using apm-cli:
-
-1. Keep your apm-cli installation up to date
-2. Review workflow files carefully before execution
-3. Use proper access controls for your MCP servers
-4. Validate all input parameters in your workflows
-5. Follow security best practices for Python package management
+<!-- END MICROSOFT SECURITY.MD BLOCK -->

scripts/test-integration.sh

@@ -258,9 +258,17 @@ install_test_dependencies() {
     # Check if uv is available, otherwise use pip
     if command -v uv >/dev/null 2>&1; then
         log_info "Using uv for dependency installation..."
-        uv venv --python 3.12 || uv venv  # Try 3.12 first, fallback to default
-        source .venv/bin/activate
-        uv pip install -e ".[dev]"
+
+        # Check if .venv already exists (CI mode where workflow already ran uv sync)
+        if [[ -d ".venv" ]]; then
+            log_info "Virtual environment already exists, activating it..."
+            source .venv/bin/activate
+        else
+            log_info "Creating new virtual environment..."
+            uv venv --python 3.12 || uv venv  # Try 3.12 first, fallback to default
+            source .venv/bin/activate
+            uv pip install -e ".[dev]"
+        fi
     else
         log_info "Using pip for dependency installation..."
         pip install -e ".[dev]"