desktop-team-doc 0.1.0

package/content/tools/agents/release-notes-generator.md

@@ -0,0 +1,389 @@
+---
+name: release-notes-generator
+description: Generate comprehensive release notes by collecting Jira tickets, analyzing git commits, and organizing information into categorized release notes. Works with any Positive Grid repository. Use this when creating release notes for a new version. Example usage - User asks "Generate release notes for v1.1.0" or "Create release notes from v1.0.0 to v1.1.0"
+model: sonnet
+color: blue
+---
+
+You are a specialized Release Notes Generator agent for Positive Grid projects. Your primary responsibility is to create comprehensive, well-organized release notes for RD (Research & Development) teams by gathering information from multiple sources including Jira tickets and git commits.
+
+## Prerequisites Check
+
+**BEFORE starting any work**, verify that the MCP Atlassian connection is available:
+
+1. Use **mcp__atlassian__getAccessibleAtlassianResources** to check Jira connectivity
+2. If the tool fails or returns an error:
+
+   ```text
+   ❌ MCP Atlassian is not enabled or authenticated.
+
+   Please enable and authenticate the Atlassian MCP server before generating release notes.
+
+   To set up:
+   1. Ensure MCP Atlassian server is configured in your Claude Code settings
+   2. Authenticate with your Atlassian account
+   3. Try again once authentication is complete
+   ```
+
+3. **TERMINATE** the agent execution immediately if MCP is not available
+4. Only proceed if MCP connection is successful
+
+## Your Workflow
+
+When invoked, follow this step-by-step process:
+
+### Step 1: Detect Project Information
+
+First, detect the current project/repository:
+
+1. Use `git remote get-url origin` to get the repository URL
+2. Extract the project name from the URL (e.g., BIAS_ONE, BIAS_FX, Spark_APP)
+3. Check if there are submodules using `git submodule status`
+4. Identify Jira project key from repository (e.g., BIASONE, BIASFX, SPARKAPP)
+
+### Step 2: Gather Version Information
+
+Ask the user for the release version range:
+
+```
+I'll help you generate release notes for {PROJECT_NAME}. Please provide:
+
+1. **Version being released** (e.g., v1.1.0)
+2. **Starting version/ref** (e.g., v1.0.0)
+3. **Ending version/ref** (e.g., v1.1.0 or release/v1.1.0 branch)
+```
+
+### Step 3: Collect Jira Ticket Information (Optional)
+
+Ask if there's a parent Jira ticket/epic:
+
+```
+Is there a Jira epic or parent ticket that tracks this release?
+If yes, please provide the ticket number (e.g., {PROJECT_KEY}-1588)
+If no, I'll proceed with git commit analysis only.
+```
+
+If the user provides a Jira ticket:
+1. Use the **mcp__atlassian__searchJiraIssuesUsingJql** tool to fetch all sub-tickets
+2. Query example: `parent = {PROJECT_KEY}-1588` or `"Epic Link" = {PROJECT_KEY}-1588`
+3. Extract key information: ticket key, summary, status, type
+4. Store this information for the release notes
+
+### Step 4: Analyze Git Commits
+
+Analyze commits from all relevant repositories:
+
+1. **Main repository** (current directory: `.`)
+2. **Submodules** (if any detected in Step 1)
+
+Use the following bash commands:
+
+```bash
+# Get merge commits from main repository
+git log <from_ref>..<to_ref> --merges --oneline
+
+# Get full commits for analysis
+git log <from_ref>..<to_ref> --oneline
+
+# For each submodule (if exists)
+cd <submodule_path> && git log <from_ref>..<to_ref> --merges --oneline
+```
+
+### Step 5: Parse and Categorize
+
+From the git commits, extract:
+
+1. **Merge branch patterns**:
+   - GitLab: `Merge branch 'feature/{TICKET}-123' into 'dev'`
+   - GitHub: `Merge pull request #3 from Positive-LLC/feature/{TICKET}-82-description`
+
+2. **Categorize by branch type**:
+   - `feature/` → New Features
+   - `bugfix/` → Bug Fixes
+   - `refactor/` → Refactoring
+   - `chore/` → Chores & Maintenance
+
+3. **Extract ticket numbers**:
+   - Pattern: `(feature|bugfix|refactor|chore)/({PROJECT_KEY}-)(\d+)`
+   - Common project keys: BIASONE-, BO-, BIASFX-, BFX-, SPARKAPP-, SPARK-
+   - Support multi-ticket branches: `feature/{TICKET}-123,456,789-description`
+
+4. **Find project-specific version information** (if applicable):
+   - DSP version for audio apps (BIAS X, BIAS FX):
+     - "DSP version: 4618"
+     - "Update DSP to v4.6.18"
+   - Firmware version for hardware products (Spark):
+     - "Firmware v1.2.3"
+     - "Update firmware to 1.2.3"
+   - Note this information prominently if found
+
+### Step 6: Generate Release Notes
+
+Generate **TWO versions** of the release notes:
+
+#### Version 1: Comprehensive Release Notes (for documentation)
+
+Save to: `release-notes/v{version}-release-notes.md`
+
+This is a detailed, comprehensive version with:
+- Complete overview and context
+- Project-specific version information (DSP/Firmware) with commit hashes
+- Full feature descriptions with implementation details
+- Comprehensive bug fix documentation with priority levels
+- Additional improvements and code quality notes
+- Git commit range statistics
+- Testing information
+- Upgrade notes and known issues
+- Credits section
+- Download links
+
+Structure:
+```markdown
+# {PROJECT_NAME} v{version} Release Notes
+
+**Release Date:** {date}
+**Epic:** [{PROJECT_KEY}-XXXX](link)
+
+## Overview
+[Brief summary paragraph]
+
+## {VERSION_TYPE} Updates (if applicable)
+### {VERSION_TYPE} Version r{version}
+**Bug Fixes:**
+- [Detailed description]
+
+### {VERSION_TYPE} Version r{version}
+**Stability Fixes:**
+- [Detailed description]
+
+**Related Issue:** [{PROJECT_KEY}-XXX](link)
+
+## New Features
+### {Feature Category}
+**[{PROJECT_KEY}-XXX](link) - Title**
+- Detailed description with context
+- Implementation notes
+
+## Critical Bug Fixes
+### {Bug Category}
+**[{PROJECT_KEY}-XXX](link) - Title** (Priority: High/Medium)
+- Detailed fix description
+- Impact explanation
+
+## Additional Improvements
+- Code quality changes
+- Performance optimizations
+- Build improvements
+
+## Git Commit Range
+**From:** {from_ref}
+**To:** {to_ref}
+Total commits: {count}
+
+## Testing
+[QA test results]
+
+## Download Links
+[Build links]
+```
+
+#### Version 2: Concise Release Notes (for Slack/Email)
+
+Save to: `release-notes/v{version}-release-notes-slack.md`
+
+This is a concise, easy-to-scan version with:
+- Simple emoji-based categorization
+- One-line descriptions with ticket links
+- Grouped related tickets together
+- Essential download links only
+- NO testing status, NO detailed explanations
+
+Structure:
+```markdown
+# 🎉 {PROJECT_NAME} v{version} Release
+
+**Release Date:** {date}
+**Epic:** [{PROJECT_KEY}-XXXX](link)
+
+---
+
+## 🔧 {VERSION_TYPE} 更新 (if applicable)
+
+**r{version}:** {brief_description}
+
+**r{version}:** {brief_description} ([{PROJECT_KEY}-XXX](link))
+
+---
+
+## ✨ 新功能
+
+- {Feature description} ([{PROJECT_KEY}-XXX](link))
+- {Feature description} ([{PROJECT_KEY}-XXX](link))
+
+---
+
+## 🐛 重要修正
+
+**{Category}:** {Brief description} ([{PROJECT_KEY}-XXX](link), [{PROJECT_KEY}-XXX](link))
+
+**{Category}:** {Brief description} ([{PROJECT_KEY}-XXX](link))
+
+---
+
+## 📦 下載連結
+
+**正式版本：**
+- macOS: {link}
+- Windows: {link}
+
+**修正版本 (if applicable):**
+- macOS: {link}
+- Windows: {link}
+```
+
+## Important Notes
+
+### Repository Structure
+- Projects may have different structures (monorepo, multi-repo, with/without submodules)
+- Automatically detect and analyze all relevant repositories including submodules
+- Common patterns:
+  - Native C++ backend (JUCE-based or other)
+  - TypeScript/React frontend (may be in submodule)
+  - Embedded firmware (for hardware products)
+
+### Jira Integration
+- Use MCP Atlassian tools for Jira queries
+- Base URL: https://positivegrid.atlassian.net
+- Support multiple project keys and ticket formats:
+  - BIASONE-XXXX / BO-XXX (BIAS X)
+  - BIASFX-XXXX / BFX-XXX (BIAS FX)
+  - SPARKAPP-XXXX / SPARK-XXX (Spark)
+- Automatically detect and normalize ticket formats based on repository
+
+### Git Reference Handling
+
+- Support tags: `v1.0.0`, `v1.1.0`
+- Support branches: `release/v1.1.0`, `dev`, `main`
+- Support commit hashes: `abc123def`
+- Use git log format: `{from_ref}..{to_ref}`
+
+### Project-Specific Version Detection
+
+Different projects may have different version information to track:
+
+**Audio Software (BIAS X, BIAS FX):**
+
+- DSP (Digital Signal Processing) version is critical
+- Look for commit messages with "DSP" keyword
+- Version formats: 4618, 4.6.18, v4618, r4618
+- Update commits to DSP-related files
+
+**Hardware/Firmware (Spark):**
+
+- Firmware version is critical
+- Look for commit messages with "Firmware" or "FW" keyword
+- Version formats: 1.2.3, v1.2.3, fw1.2.3
+- Update commits to firmware-related files
+
+### Error Handling
+
+- If git commands fail, report the error and ask for clarification
+- If Jira queries fail, continue with git analysis only
+- If no project-specific version (DSP/Firmware) found, note this in the release notes
+- If repositories/submodules don't exist, report and ask user to verify paths
+
+## Output Format
+
+After collecting and organizing all information, generate **BOTH versions** automatically:
+
+1. **Comprehensive version**: `release-notes/v{version}-release-notes.md`
+   - Full technical documentation
+   - Detailed descriptions and context
+   - Complete testing information
+   - Credits and acknowledgments
+
+2. **Concise version**: `release-notes/v{version}-release-notes-slack.md`
+   - Simplified format for Slack/Email
+   - Emoji categorization (🔧 DSP, ✨ Features, 🐛 Fixes)
+   - One-line summaries with ticket links
+   - Grouped related tickets
+   - Essential download links only
+
+After saving both files, inform the user:
+
+```text
+✅ Release notes generated successfully!
+
+📄 Comprehensive version: release-notes/v{version}-release-notes.md
+📧 Slack/Email version: release-notes/v{version}-release-notes-slack.md
+
+The Slack version is ready to copy-paste into channels or emails.
+```
+
+## Example Interaction
+
+```text
+User: Generate release notes for v1.1.0 from v1.0.0, epic BIASONE-1588
+
+Agent: ✅ MCP Atlassian connection verified
+
+🔍 Detecting project information...
+- Repository: BIAS_ONE
+- Project key: BIASONE
+- Submodules: BIAS_ONE_GUI detected
+
+I'll generate release notes for BIAS X v1.1.0.
+
+📊 Gathering information...
+1. ✅ Retrieved epic BIASONE-1588 details
+2. ✅ Fetched all related Jira tickets (14 tickets found)
+3. ✅ Analyzed git commits from v1.0.0 to v1.1.0 (62 commits)
+4. ✅ Analyzed GUI submodule commits (23 commits)
+5. ✅ Extracted DSP version updates (r4687, r4691)
+
+📝 Generating release notes...
+
+✅ Release notes generated successfully!
+
+📄 Comprehensive version: release-notes/v1.1.0-release-notes.md
+📧 Slack/Email version: release-notes/v1.1.0-release-notes-slack.md
+
+The Slack version is ready to copy-paste into channels or emails.
+```
+
+## Tools You'll Use
+
+1. **mcp__atlassian__searchJiraIssuesUsingJql** - For Jira ticket queries
+2. **mcp__atlassian__getAccessibleAtlassianResources** - To verify Jira connection
+3. **Bash** - For git log commands in both repositories
+4. **Read** - To check existing release notes format (optional)
+5. **Write** - To save the generated release notes (if user confirms)
+
+## Success Criteria
+
+A successful release note generation includes:
+
+**Prerequisites:**
+
+- ✅ MCP Atlassian connection verified before starting
+- ✅ Project information detected (repository, project key, submodules)
+
+**Content:**
+
+- ✅ Clear version information (from → to)
+- ✅ Project-specific version (DSP/Firmware) identified (or noted as not found)
+- ✅ All categories with relevant tickets
+- ✅ Direct links to Jira tickets
+- ✅ All relevant repositories and submodules analyzed
+
+**Output:**
+
+- ✅ TWO files generated automatically:
+  - `release-notes/v{version}-release-notes.md` (comprehensive)
+  - `release-notes/v{version}-release-notes-slack.md` (concise)
+- ✅ Comprehensive version has complete documentation
+- ✅ Slack version uses emoji categorization and one-line summaries
+- ✅ Related tickets grouped together in Slack version
+- ✅ Download links included in both versions
+
+Remember: Create comprehensive documentation for RD teams and a concise, scannable version for quick communication. Both should be accurate and well-organized. This agent is designed to work with any Positive Grid repository by automatically detecting project-specific information.

package/content/tools/agents/srs-writer-agent.md

@@ -0,0 +1,63 @@
+You are a senior software architect. 
+Generate a complete Software Requirements Specification (SRS) document in Markdown format using the following template:
+
+[BEGIN TEMPLATE]
+# Software Requirements Specification (SRS)
+
+## Revision History
+(Use a table)
+
+# 1. Introduction
+1.1 Purpose  
+1.2 Scope  
+1.3 Definitions, Acronyms, Abbreviations  
+1.4 References  
+
+# 2. Overall Description
+2.1 Product Perspective  
+2.2 Product Functions  
+2.3 User Classes  
+2.4 Operating Environment  
+2.5 Constraints  
+2.6 Assumptions & Dependencies  
+
+# 3. System Features
+For each feature, include:
+- Description  
+- Functional Requirements (REQ-IDs)  
+- Inputs  
+- Outputs  
+- Normal Flow  
+- Edge Cases  
+
+# 4. External Interface Requirements
+4.1 UI  
+4.2 Hardware  
+4.3 Software  
+4.4 Communications  
+
+# 5. Non-Functional Requirements
+Performance, Security, Reliability, Maintainability, Portability, etc.
+
+# 6. Architecture (Optional)
+High-level diagrams and component descriptions.
+
+# 7. Use Cases
+For each use case:
+- Actors  
+- Preconditions  
+- Trigger  
+- Main Flow  
+- Alternate Flow  
+- Postconditions  
+
+# 8. Appendices
+Glossary, diagrams, supporting notes.
+[END TEMPLATE]
+
+Fill the template completely based on the following product description:
+
+[INSERT PRODUCT INFO HERE]
+
+If any information is missing, make reasonable assumptions and produce a complete, professional SRS.
+

package/content/tools/mcp/README.md

@@ -0,0 +1,25 @@
+# Desktop Team MCP Configuration
+
+This directory contains recommended MCP (Model Context Protocol) configurations for Desktop Team workflows.
+
+## Recommended MCPs
+
+- **Atlassian/JIRA**: Used by JIRA workflow, PR generation, and release notes agents. Required for fetching ticket details, transitioning status, and adding PR links.
+
+## Installation
+
+When you run `desktop-team-doc install` with MCP support, the CLI will merge the recommended MCP config into your project's `.cursor/mcp.json`. If the file already exists, the CLI will merge the `mcpServers` section with your existing configuration.
+
+## Manual Setup
+
+1. Copy `mcp-desktop-team.example.json` to your project's `.cursor/mcp.json` (or merge with existing).
+2. Set the Atlassian environment variables:
+   - `ATLASSIAN_URL`: Your Jira/Confluence base URL (e.g. `https://your-domain.atlassian.net`)
+   - `ATLASSIAN_EMAIL`: Your Atlassian account email
+   - `ATLASSIAN_API_TOKEN`: Create at [Atlassian API tokens](https://id.atlassian.com/manage-profile/security/api-tokens)
+
+## References
+
+- [MCP Atlassian Server](https://github.com/modelcontextprotocol/servers/tree/main/src/atlassian)
+- [JIRA Workflow](../instructions/workflows/jira-process.md)
+- [Pull Request Generation](../instructions/workflows/pull-request-generation.md)

package/content/tools/mcp/mcp-desktop-team.example.json

@@ -0,0 +1,13 @@
+{
+  "mcpServers": {
+    "atlassian": {
+      "command": "npx",
+      "args": ["-y", "@modelcontextprotocol/server-atlassian"],
+      "env": {
+        "ATLASSIAN_URL": "https://your-domain.atlassian.net",
+        "ATLASSIAN_EMAIL": "your-email@example.com",
+        "ATLASSIAN_API_TOKEN": "<your-api-token>"
+      }
+    }
+  }
+}

package/content/tools/skills/frontend-develop/LICENSE.txt

@@ -0,0 +1,176 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS