TRIAGING.md

The OpenSearch Data Prepper maintainers seek to promote an inclusive and engaged community of contributors. In order to facilitate this, weekly triage meetings are open to all and attendance is encouraged for anyone who hopes to contribute, discuss an issue, or learn more about the project. To learn more about contributing to the OpenSearch Data Prepper project visit the Contributing documentation.

Do I need to attend for my issue to be addressed/triaged?

Attendance is not required for your issue to be triaged or addressed. All new issues are triaged weekly.

What happens if my issue does not get covered this time?

Each meeting we seek to address all new issues. However, should we run out of time before your issue is discussed, you are always welcome to attend the next meeting or to follow up on the issue post itself.

How do I join the triage meeting?

Meetings are hosted regularly Tuesdays at 2:30 PM US Central Time (12:30 PM Pacific Time) and can be joined via the links posted on the OpenSearch Meetup Group list of events. The event will be titled OpenSearch Data Prepper Triage Meeting.

After joining the video meeting, you can enable your video / voice to join the discussion. If you do not have a webcam or microphone available, you can still join in via the text chat.

If you have an issue you'd like to bring forth please consider getting a link to the issue so it can be presented to everyone in the meeting.

Is there an agenda for each week?

Meetings are 30 minutes and structured as follows:

1. Initial Gathering: As we gather, feel free to turn on video and engage in informal and open-to-all conversation. A volunteer OpenSearch Data Prepper maintainer will share the Data Prepper Tracking Board and proceed.
2. Announcements: We will make any announcements at the beginning, if necessary.
3. Untriaged issues: We will review all untriaged issues for the OpenSearch Data Prepper repository. If you have an item here, you may spend a few minutes to explain your request.
4. Member Requests: Opportunity for any meeting member to ask for consideration of an issue or pull request.
5. Release review: If time permits, and we find it necessary, we will review items for the current release.
6. Follow-up issues: If time permits, we will review the follow up items.
7. Open Discussion: If time permits, allow for members of the meeting to surface any topics without issues filed or pull request created.

Do I need to have already contributed to the project to attend a triage meeting?

No, all are welcome and encouraged to attend. Attending the triage meetings is a great way for a new contributor to learn about the project as well as explore different avenues of contribution.

What if I have follow-up questions on an issue?

If you have an existing issue you would like to discuss, you can always comment on the issue itself. Alternatively, you are welcome to come to the triage meeting to discuss.

Is this meeting a good place to get help using OpenSearch Data Prepper?

While we are always happy to help the community, the best resource for usage questions is the OpenSearch Data Prepper discussion forum on GitHub.

There you can find answers to many common questions as well as speak with implementation experts and OpenSearch Data Prepper maintainers.

What are the issue labels associated with triaging?

There are several labels that are particularly important for triaging in OpenSearch Data Prepper:

Label	When applied	Meaning
untriaged	When issues are created or re-opened.	Issues labeled as untriaged require the attention of the repository maintainers and may need to be prioritized for quicker resolution. It's crucial to keep the count of 'untriaged' labels low to ensure all potential security issues are addressed in a timely manner.
follow up	During triage meetings.	Issues labeled as follow up have been triaged. However, the maintainers may need to follow up further on it. This tag lets us triage an issue as not critical, but also be able to come back to it.
help wanted	Anytime.	Issues marked as help wanted signal that they are actionable and not the current focus of the project maintainers. Community contributions are especially encouraged for these issues.
good first issue	Anytime.	Issues labeled as good first issue are small in scope and can be resolved with a single pull request. These are recommended starting points for newcomers looking to make their first contributions.

Is this where I should bring up potential security vulnerabilities?

Due to the sensitive nature of security vulnerabilities, please report all potential vulnerabilities directly by following the steps outlined in the Security Issue Response Process.

Who should I contact if I have further questions?

You can always file an issue for any question you have about the project.