A pm-cli workspace preset for open source project maintainers. Prioritizes low friction for community contributions — no ownership enforcement, community-friendly templates, and core metadata so maint
pm oss-setup
{
"id_prefix": "oss-",
"author_default": "",
"governance": {
"preset": "default",
"ownership_enforcement": "off",
"create_mode_default": "progressive",
"close_validation_default": "warn",
"metadata_profile": "core"
},
"validation": {
"sprint_release_format": "warn",
"parent_reference": "warn"
},
"item_types": {
"definitions": [
{
"name": "Feature",
"description": "A new capability requested by the community"
},
{
"name": "Issue",
"description": "A defect or unintended behavior"
},
{
"name": "Task",
"description": "Maintenance, refactor, or contributor onboarding work"
}
]
},
"testing": {
"record_results_to_items": true
},
"search": {
"mode": "keyword"
},
"calendar": {
"default_view": "agenda",
"first_day_of_week": 1
},
"telemetry": {
"enabled": false
}
}
A pm-cli workspace preset for open source project maintainers. Prioritizes low friction for community contributions — no ownership enforcement, community-friendly templates, and core metadata so maintainers have enough context to triage and review.
settings.json)| Setting | Value | Rationale |
|---|---|---|
id_prefix |
oss- |
Makes item IDs identifiable in changelogs and PR references |
governance.preset |
default |
Reasonable structure without blocking async contributors |
governance.ownership_enforcement |
none |
Community items are unassigned by default; no warnings |
governance.close_validation_default |
warn |
Encourages completeness when closing, but doesn't block |
governance.metadata_profile |
core |
Captures enough context for async triage |
validation.sprint_release_format |
warn |
Milestones are flexible; only warns on format issues |
validation.parent_reference |
warn |
Community issues often stand alone; parent not required |
| Template | Type | Purpose |
|---|---|---|
feature-request |
Feature | Community-submitted feature proposals |
bug-report |
Issue | User-submitted bug with repro steps and environment info |
good-first-issue |
Task | Curated beginner-friendly tasks with mentorship context |
Incoming community issue
├── Triage → apply feature-request or bug-report template
├── Label good-first-issue → apply good-first-issue template
└── Assign milestone → link to release
pm create --template bug-report or pm create --template feature-request.upstream_issue_url metadata field to link back to the GitHub/GitLab issue.good-first-issue using pm create --template good-first-issue.pm close — a warning fires if reproduction steps or expected behavior are missing.Run the setup script from your repository root after running pm init:
bash .agents/pm/presets/open-source/setup.sh
Or copy files manually:
cp presets/open-source/settings.json .agents/pm/settings.json
cp presets/open-source/templates/*.json .agents/pm/templates/
triage_label metadata field to templates if your project uses a labeling system.author_default to your bot username if you auto-create items from webhook events.ownership_enforcement to warn once the project grows and you want to track who owns each item.