Merge branch 'main' of https://github.com/Open-Model-Initiative/OMI-D…

…ata-Pipeline into 138-create-cdk-deployment-pipeline

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,44 @@
+---
+name: Bug Report
+about: Create a report to help us improve Open Model Initiative Data Repository
+title: "[BUG] "
+labels: bug
+assignees: ''
+---
+
+### Describe the bug
+
+A clear and concise description of what the bug is.
+
+### Steps to Reproduce
+
+Steps to reproduce the behavior:
+
+1. **Step One:** Describe what to do first.
+2. **Step Two:** Describe the next step.
+3. **Step Three:** Continue with details.
+4. **Step Four:** And so on...
+
+### Expected Behavior
+
+Describe what you expected to happen.
+
+### Actual Behavior
+
+Describe what actually happened, including any error messages or screenshots.
+
+### Screenshots (if applicable)
+
+If applicable, add screenshots to help explain your problem.
+
+### Environment
+
+Please complete the following information:
+
+- **OS:** e.g., Windows 10, macOS Monterey, Ubuntu 20.04
+- **Browser/Platform:** if applicable
+- **Version:** if applicable
+- **Other Relevant Info:** any other details that might help
+
+### Additional Context
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/cicd_issue.md

@@ -0,0 +1,33 @@
+---
+name: CI/CD Issue
+about: Report issues or suggest improvements for the CI/CD pipeline
+title: "[CI/CD] "
+labels: ci-cd
+assignees: ''
+---
+
+### Describe the Issue
+
+Provide a clear description of the CI/CD issue or improvement suggestion.
+
+### Pipeline Details
+
+- **Workflow:** (e.g., main.yml, release.yml)
+- **Job/Step:** (specific job or step where issue occurs)
+- **Environment:** (if applicable)
+
+### Current Behavior
+
+Describe what's happening now (include build logs if relevant).
+
+### Expected Behavior
+
+Describe what should happen instead.
+
+### Proposed Changes
+
+If suggesting an improvement, describe your proposed changes to the pipeline.
+
+### Additional Context
+
+Add any other context, logs, or screenshots about the CI/CD issue here.

.github/ISSUE_TEMPLATE/design_request.md

@@ -0,0 +1,23 @@
+---
+name: Design/UX Enhancement
+about: Suggest an improvement to the design or user experience of Open Model Initiative Data Repository
+title: "[DESIGN] "
+labels: enhancement, design
+assignees: ''
+---
+
+### Describe the Issue
+
+Explain what design or UX issue you’re experiencing or observing.
+
+### Proposed Enhancement
+
+Describe your suggested improvement or alternative design. Include sketches, mockups, or links to design inspirations if available.
+
+### Impact on Users
+
+Explain how this change could improve the user experience or solve current usability issues.
+
+### Additional Context
+
+Any additional information, context, or examples that could help us understand the proposal.

.github/ISSUE_TEMPLATE/doc_issue.md

@@ -0,0 +1,23 @@
+---
+name: Documentation Issue
+about: Report an issue or suggest improvements to the Open Model Initiative Data Repository documentation
+title: "[DOC] "
+labels: documentation
+assignees: ''
+---
+
+### Describe the issue
+
+Explain what is unclear, missing, or incorrect in the documentation.
+
+### Location of the issue
+
+Provide a URL or file path where the issue occurs.
+
+### Suggested Improvement
+
+If possible, describe how you think the documentation should be improved or fixed.
+
+### Additional Context
+
+Include any screenshots or additional context that might help us understand the issue better.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,23 @@
+---
+name: Feature Request
+about: Suggest an idea for Open Model Initiative Data Repository
+title: "[FEATURE] "
+labels: enhancement
+assignees: ''
+---
+
+### Is your feature request related to a problem?
+
+A clear and concise description of what the problem is. For example, “I wish Open Model Initiative Data Repository could do [X] because [Y].”
+
+### Describe the solution you'd like
+
+A clear and concise description of what you want to happen. Describe the feature, how it should work, and any user interactions involved.
+
+### Alternatives Considered
+
+Describe any alternative solutions or features you’ve considered.
+
+### Additional Context
+
+Add any other context, screenshots, or examples related to the feature request.

.github/ISSUE_TEMPLATE/security_issue.md

@@ -0,0 +1,19 @@
+---
+name: Security Vulnerability Report
+about: Report a potential security vulnerability in Open Model Initiative Data Repository
+title: "[SECURITY] "
+labels: security
+assignees: ''
+---
+
+### Describe the Vulnerability
+
+Provide a clear and detailed description of the potential security issue.
+
+### Steps to Reproduce
+
+List the steps someone could take to observe the vulnerability (if safe to share publicly).
+
+### Impact Assessment
+
+Explain the potential impact or risk associated with the vulnerability.

.github/ISSUE_TEMPLATE/support_request.md

@@ -0,0 +1,25 @@
+---
+name: Support Request
+about: Use this template to ask for help with using Open Model Initiative Data Repository
+title: "[SUPPORT] "
+labels: question
+assignees: ''
+---
+
+### Describe your issue
+
+Provide a clear and concise description of your question or the support you need.
+
+### What have you tried?
+
+List any steps, configurations, or troubleshooting measures you’ve already attempted.
+
+### Environment Details
+
+- **OS:** e.g., Windows 11, macOS Monterey, Ubuntu 22.04
+- **Version:** if applicable
+- **Other Relevant Info:** e.g., browser version, terminal output, etc.
+
+### Additional Context
+
+Add any other information or screenshots that might help us better understand your issue.

.github/ISSUE_TEMPLATE/task.md

@@ -0,0 +1,21 @@
+---
+name: Task/Management
+about: Create a general task, management item, or project planning issue
+title: "[TASK] "
+labels: task
+assignees: ''
+---
+
+### Task Description
+
+Provide a clear and concise description of the task or management item.
+
+### Objectives
+
+List the specific objectives or deliverables:
+
+- [ ] Objective 1
+- [ ] Objective 2
+- [ ] Objective 3
+
+Add any other context, references, or notes about the task here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,30 @@
+# Description
+
+Please include a summary of the changes and the related issue.
+Fixes # (issue)
+
+## Type of Change
+
+- [ ] Bug fix
+- [ ] New feature
+- [ ] Documentation update
+- [ ] Refactoring
+- [ ] CI/CD updates
+- [ ] Other (please describe):
+
+## How Has This Been Tested?
+
+Describe the tests that you ran to verify your changes. Include details on your testing environment if applicable.
+
+## Checklist
+
+- [ ] My code follows the style guidelines of this project
+- [ ] I have performed a self-review of my code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have made corresponding changes to the documentation
+- [ ] My changes generate no new warnings
+- [ ] I have added or updated tests that prove my fix is effective or my feature works
+
+## Additional Context
+
+Add any additional information that might be helpful for the review.

.github/workflows/documentation.yml

@@ -0,0 +1,37 @@
+# SPDX-License-Identifier: Apache-2.0
+# .github/workflows/documentation.yml
+# -----------------------------------------------------------------------------
+
+name: documentation
+on:
+  workflow_dispatch:
+  push:
+    branches: [ "main", "doc_sandbox"]
+    paths:
+      - 'doc/**'
+      - '.github/workflows/documentation.yml'
+
+permissions:
+    pages: write
+    contents: write
+
+jobs:
+  docs:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+      - name: Install dependencies
+        run: |
+          pip install sphinx pydata-sphinx-theme myst_parser
+      - name: Sphinx build
+        run: |
+          sphinx-build doc _build
+      - name: Deploy to GitHub Pages
+        uses: peaceiris/actions-gh-pages@v3
+        if: ${{ (github.ref == 'refs/heads/main' || github.ref == 'refs/heads/doc_sandbox') }}
+        with:
+          publish_branch: gh-pages
+          github_token: ${{ secrets.GITHUB_TOKEN }}
+          publish_dir: _build/
+          force_orphan: true

CODEOWNERS.md

@@ -1,4 +1,4 @@
 # Repo Committers as defined and approved by the Technical Steering Committee
 # Additional committers to be voted on by the committers in this repository as need and scope of involvement warrants.
 # Please reach out the the OMI Technical Steering Committee for information on committer proposals.
-*       @hiphipsterusername  @comfyanonymous @takoyaro
+*       @hipsterusername  @Padge91 @takoyaro

CONTRIBUTING.md

@@ -11,8 +11,7 @@ Contributions come in the form of code submissions, writing documentation, curat
 The Technical Steering Committee (the “TSC”) will be responsible for all technical oversight of the open source Project. TSC voting members are initially the Project’s Committers listed below:
 
 - Kent Keirsey - Invoke
-- comfyanonymous - Comfy Org
-- Justin Maier - Civitai
+- Nick Padgett - Spawning.ai
 
 The TSC may choose an alternative approach for determining the voting members of the TSC, and any such alternative approach will be documented in this file. Any meetings of the Technical Steering Committee are intended to be open to the public, and can be conducted electronically, via teleconference, Discord, or in person.
 

Taskfile.yml

@@ -9,7 +9,6 @@ includes:
   frontend: ./modules/odr_frontend/Taskfile.yml
   api-test: ./modules/odr_api/tests/Taskfile.api.test.yml
   monitoring: ./modules/odr_monitoring/Taskfile.yml
-  caption: ./modules/odr_caption/Taskfile.caption.yml
 
 dotenv: ['.env', '{{.ENV}}/.env', '{{.HOME}}/.env']
 vars: