Plan 03: test_integration_hil.sh, power_profiling.sh Plan 07: .github/pull_request_template.md (spec link + AC checklist) Plan 08: check_emc_radio_lvd.py, setup_branch_protection.sh Plan 10: issue_to_pr_walkthrough.md, check_doc_links.sh, check_doc_commands.sh Plan 11: CODEOWNERS, compliance_gate_tests.py All 10 items closed across 5 plans. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
1.8 KiB
1.8 KiB
11) Plan de contribution & feedback
Objectif
Canaliser issues/PR, proposer des profils, enrichir les standards, et intégrer le feedback sans casser la sécurité.
Labels recommandés
type:process+ai:docs(ouai:plansi changements structure)
Étapes
1. Templates d’issues
- Feature — Delivered:
.github/ISSUE_TEMPLATE/systems-engineering.yml - Bug — Obsolete: no dedicated bug template, but
consulting-intake.ymlcovers it - Compliance/Release — Delivered:
.github/ISSUE_TEMPLATE/compliance-release.yml - Agentics update — Delivered:
.github/ISSUE_TEMPLATE/rnd-spike.yml
2. Process PR
- Labels
ai:*obligatoires — Delivered:.github/workflows/ci.yml - Scope guard doit passer — Delivered:
tools/scope_guard.py - Evidence pack minimal — Delivered:
.github/workflows/evidence_pack.yml - Review obligatoire sur paths sensibles — Delivered:
.github/CODEOWNERS(requires @electron review on .github/, tools/security/, compliance/, tools/ai/)
3. Proposer un profil compliance
- Ouvrir issue
type:compliance— Delivered:.github/ISSUE_TEMPLATE/compliance-release.yml - Fournir exigences et sources — Delivered:
docs/COMPLIANCE.md - Ajouter tests/gates — Delivered:
tools/compliance/compliance_gate_tests.py(CI-ready gate: profile, standards, plan, evidence, EMC/radio checks)
4. Boucle feedback
- Triage hebdo — Delivered:
tools/cockpit/render_daily_operator_summary.sh+render_weekly_refonte_summary.sh - “Decision log” (ADR) — Delivered:
docs/templates/ADR.md
Critère de sortie
✅ Contributions fluides, règles claires, aucun élargissement accidentel des privilèges.
Références
.github/ISSUE_TEMPLATE/*docs/LABELS.md