nextcloud / nextcloud/desktop

Triage and Review Process: Our Commitment

Open
#7,778 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
3.9k
Forks
1k
Avg merge
1d 17h
Merged PRs (30d)
123

Description

We value community feedback and contributions to the desktop client. Your input is essential to improving the product, and we strive to interact and provide feedback in a timely manner.

![Image](https://github.com/user-attachments/assets/b3b70efb-76cc-4132-ba3f-64d376015761)

Steps:
1. The label [0. Needs triage](https://github.com/nextcloud/desktop/issues?q=is%3Aissue%20state%3Aopen%20label%3A%220.%20Needs%20triage%22) is automatically added when the issue is created.
2. When the issue is not clear, we need to ask questions, logs, steps to reproduce it.
3. Once we request the missing information, the [0. Needs triage](https://github.com/nextcloud/desktop/issues?q=is%3Aissue%20state%3Aopen%20label%3A%220.%20Needs%20triage%22) label is removed and [needs info](https://github.com/nextcloud/desktop/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22needs%20info%22) is added.
4. The [needs info](https://github.com/nextcloud/desktop/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22needs%20info%22) label is removed automatically once the issue is updated again by the community.
5. The person responsible for doing triage on the day will assign themselves to the ticket until the triaging process is completed: all necessary information is collected to confirm the [bug](https://github.com/nextcloud/desktop/issues?q=is%3Aissue%20state%3Aopen%20type%3ABug) or [feature request](https://github.com/nextcloud/desktop/issues?q=is%3Aissue%20state%3Aopen%20%20type%3AEnhancement%20).
6. The [1. to develop](https://github.com/nextcloud/desktop/issues?q=is%3Aissue%20state%3Aopen%20type%3ABug%20label%3A%221.%20to%20develop%22) label is added: the issue is confirmed and can be worked on by anyone.
> [!TIP]
> We also use the label [good first issue](https://github.com/nextcloud/desktop/issues?q=is%3Aissue%20state%3Aopen%20type%3ABug%20label%3A%221.%20to%20develop%22%20label%3A%22good%20first%20issue%22) to help newcomers to get familiar with the project.

Our targets:
- **Bug Reports**: Review and triage within 2 weeks.
- **Pull Requests**: Merge within 2 weeks.

Please note:
- These are targets, not guarantees.
- Topics that do not align with the product roadmap or strategy may not be merged.

We appreciate your understanding and continued support!

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.