Skip to content

feat(org-tools): add DTC review pipeline and Community Spotlight engine - #85

Draft
damaz91 wants to merge 6 commits into
Universal-Commerce-Protocol:mainfrom
damaz91:feat/dtc-review-pipeline
Draft

damaz91 wants to merge 6 commits into
Universal-Commerce-Protocol:mainfrom
damaz91:feat/dtc-review-pipeline

Conversation

@damaz91

@damaz91 damaz91 commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

Description

Adds the DTC Review Pipeline & Community Spotlight Engine (org-tools/dtc-pipeline/) and supporting label and workflow definitions to Universal-Commerce-Protocol/.github:

  • Label Sync (org-tools/label-sync/labels/):
    • Registers gov:tc-meeting (#88B91E, replacing legacy TC review via aliases: ["TC review"]) and community-spotlight (#FBCA04) in triage-labels.yml.
  • DTC Review Pipeline Package (org-tools/dtc-pipeline/):
    • provision-project / configure-views: Provisions and configures the public organization-level 5-view DTC Review Pipeline GitHub Project v2 board (Shopping TC [label:area:shopping,area:common], Payments TC, Food TC, and Lodging TC Kanban boards with Next DTC Agenda column limit 7 + Community Spotlight Pool Table filtered by track:"Community Spotlight"), with 6 Status columns (Triage / Unscheduled, Next DTC Agenda, Approved, Follow-up / Revisions, Redirected / Declined, Closed / Merged), Track (General Track | Community Spotlight), Priority Score (NUMBER), native Milestone fields, and optional team role provisioning (ADMIN for @devops-maintainers, WRITER for Domain Technical Council teams).
    • sync-agenda-assignees: Resolves the Technical Council member who moved each card into Next DTC Agenda via ProjectV2ItemStatusChangedEvent timeline history (falling back to statusValue.creator), assigns them via addAssigneesToAssignable, and stamps Track = General Track on open gov:tc-meeting items added via GitHub Projects' built-in Auto-add to project workflow.
    • scan-spotlight: Evaluates the 3 automated Community Spotlight eligibility gates (external affiliation, governance scope, and baseline readiness/hygiene) and deterministic 100-point priority formula (Readiness 0-40 + Capped Traction 0-30 + Wait-Time Boost 0-30 - Cooldown 0 or 30), syncing Track = Community Spotlight and Priority Score directly onto Project v2 without applying repository labels on ucp (while preserving General Track on gov:tc-meeting items).
  • Workflows (.github/workflows/):
    • Adds .github/workflows/dtc-pipeline.yml to run sync-agenda-assignees every 15 minutes, refresh scan-spotlight daily at 06:00 UTC, and support manual workflow_dispatch.
    • Wires org-tools/dtc-pipeline/tests into .github/workflows/tests.yml.

Category (Required)

Please select one or more categories that apply to this change.

  • Core Protocol: Changes to the base communication layer, global context, or breaking refactors. (Requires Technical Council approval)
  • Governance/Contributing: Updates to GOVERNANCE.md, CONTRIBUTING.md, or CODEOWNERS. (Requires Governance Council approval)
  • Capability: New schemas (Discovery, Cart, etc.) or extensions. (Requires Maintainer approval)
  • Documentation: Updates to README, or documentations regarding schema or capabilities. (Requires Maintainer approval)
  • Infrastructure: CI/CD, Linters, or build scripts. (Requires DevOps Maintainer approval)
  • Maintenance: Version bumps, lockfile updates, or minor bug fixes. (Requires DevOps Maintainer approval)
  • SDK: Language-specific SDK updates and releases. (Requires DevOps Maintainer approval)
  • Samples / Conformance: Maintaining samples and the conformance suite. (Requires Maintainer approval)
  • UCP Schema: Changes to the ucp-schema tool (resolver, linter, validator). (Requires Maintainer approval)
  • Community Health (.github): Updates to templates, workflows, or org-level configs. (Requires DevOps Maintainer approval)

Related Issues

N/A

Checklist

  • I have followed the Contributing Guide (including Conventional Commits title requirements and ! for breaking changes).
  • I have updated the documentation (if applicable).
  • My changes pass all local linting and formatting checks.
  • I have added tests that prove my fix is effective or that my feature works.
  • New and existing unit tests pass locally with my changes.
  • (For Core/Capability) I have included/updated the relevant JSON schemas.
  • (For Breaking Schema Changes / Deprecations) I have used the transition annotation rather than changing field visibility or removing a field directly.
  • I have regenerated Python Pydantic models by running generate_models.sh under python_sdk.

Screenshots / Logs (if applicable)

$ python3 -m unittest discover -s org-tools/dtc-pipeline/tests -v
test_apply_spotlight_scan_syncs_project_without_applying_labels (test_dtc_pipeline.TestDtcPipeline.test_apply_spotlight_scan_syncs_project_without_applying_labels) ... ok
test_configure_project_collaborators_links_admin_and_writer_teams (test_dtc_pipeline.TestDtcPipeline.test_configure_project_collaborators_links_admin_and_writer_teams) ... ok
test_configure_project_views_five_views_single_board_per_vertical (test_dtc_pipeline.TestDtcPipeline.test_configure_project_views_five_views_single_board_per_vertical) ... ok
test_gate1_excludes_dtc_member_and_company_and_bot (test_dtc_pipeline.TestDtcPipeline.test_gate1_excludes_dtc_member_and_company_and_bot) ... ok
test_gate2_scope_pr_and_issue (test_dtc_pipeline.TestDtcPipeline.test_gate2_scope_pr_and_issue) ... ok
test_gate3_hygiene_and_blocked_exclusion (test_dtc_pipeline.TestDtcPipeline.test_gate3_hygiene_and_blocked_exclusion) ... ok
test_parse_maintainers_companies (test_dtc_pipeline.TestDtcPipeline.test_parse_maintainers_companies) ... ok
test_pending_cla_check_run_is_not_treated_as_passed (test_dtc_pipeline.TestDtcPipeline.test_pending_cla_check_run_is_not_treated_as_passed) ... ok
test_priority_score_and_cooldown (test_dtc_pipeline.TestDtcPipeline.test_priority_score_and_cooldown) ... ok
test_spotlight_score_is_milestone_blind (test_dtc_pipeline.TestDtcPipeline.test_spotlight_score_is_milestone_blind) ... ok
test_status_options_six_columns_with_next_dtc_agenda (test_dtc_pipeline.TestDtcPipeline.test_status_options_six_columns_with_next_dtc_agenda) ... ok
test_sync_agenda_assignees_auto_assigns_mover_to_next_dtc_agenda (test_dtc_pipeline.TestDtcPipeline.test_sync_agenda_assignees_auto_assigns_mover_to_next_dtc_agenda) ... ok

----------------------------------------------------------------------
Ran 12 tests in 0.002s

OK

@damaz91
damaz91 marked this pull request as draft October 30, 2026 08:28
@damaz91
damaz91 force-pushed the feat/dtc-review-pipeline branch from 15cd59b to 4bb4883 Compare November 17, 2026 10:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant