Skip to content

docs: add issue ownership guidelines #1794

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
spzala wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: add issue ownership guidelines #1794

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ Contribute to the Mellea core, standard library, or fix bugs. This includes:
- Documentation and examples
- Tests and CI/CD improvements

**Process:** See the [Pull Request Process](#pull-request-process) section below for detailed steps.
**Process:** See the [Issue Ownership Guidelines](#issue-ownership-guidelines) and the [Pull Request Process](#pull-request-process) sections for detailed development steps.

### 2. Applications & Libraries
Build tools and applications using Mellea. These can be hosted in your own repository. For observability, use a `mellea-` prefix.
Expand Down Expand Up @@ -115,6 +115,16 @@ uv run pytest -m "not qualitative"
| `test/` | All tests (run from repo root) |
| `docs/` | Documentation, examples, tutorials |

## Issue Ownership Guidelines

To ensure issues remain available to active contributors, assigned issues may be reassigned when no progress is being made. Maintainers may reassign inactive issues after a reasonable period of inactivity.

When an issue is assigned:
- You should provide a progress update within 7 days. A progress update may be a draft PR, a comment describing ongoing work, or an update about any blockers.
- If a maintainer requests an update, please respond within 3 days. For high-priority issues (for example, P1 issues) or possible bot-based ownership, maintainers may request a faster response.
- If there is no response to a maintainer's request, or no visible activity for 7 days, maintainers may remove the assignment and make the issue available to others.
- If you need more time, simply leave a comment. Active communication is generally sufficient to retain an assignment.

## Coding Standards

### Type Annotations
Expand Down
Loading