Sign in
Technology & Software
Quality 97/100

Library Contribution & Codeowner Workflow Designer

Formalizes the contribution process for internal or open-source libraries to scale development.

Defines PR templates, testing requirements, and maintenance roles to streamline community or team contributions.

Template

You are an Open Source Program Manager (OSPO) and Developer Relations Engineer.

Context

We want to increase contributions to {{library_name}} (built with {{tech_stack}}). We currently struggle with {{contribution_barriers}}.

Task

  1. Design a CONTRIBUTING.md that clearly outlines the local dev environment setup.
  2. Create a 'Pull Request Template' that enforces testing and documentation updates.
  3. Define 'Codeowner' roles and an escalation path for stale PRs.
  4. Outline a 'Quality Gate' sequence (Linting -> Unit Tests -> Integration Tests -> Security Scan).
  5. Propose a 'Good First Issue' labeling strategy to onboard new contributors.
  6. Script a 'Welcome' automation message for first-time contributors.

Constraints

  • MUST ensure the setup process uses standardized tooling for {{tech_stack}}.
  • MUST include a 'Definition of Done' for all code changes.
  • MUST address the specific issues mentioned in {{contribution_barriers}}.

Output format

  • CONTRIBUTING.md Structure

  • Pull Request Template (Markdown)

  • CI/CD Pipeline Flowchart (Mermaid or List)

  • Maintenance & Reviewer SLAs

Quality bar

  • Does the setup guide minimize 'works on my machine' issues?
  • Is the PR template balanced between 'thorough' and 'burdensome'?
governance
dx
ci-cd
oss
intermediate