Skip to content
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.

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

Maintainer Areas of Responsibility #296

Closed
geekygirldawn opened this issue Apr 16, 2021 · 1 comment
Closed

Maintainer Areas of Responsibility #296

geekygirldawn opened this issue Apr 16, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@geekygirldawn
Copy link
Contributor

It would be great if we could also add people's areas of responsibilities to the new MAINTAINERS file. This helps people understand which of these maintainers is responsible for a particular area. We could add this as a new column to the existing table or as a separate section of the file. I'm happy to do if someone wanted to let me know which people are responsible for what.

Here's an example.

The motivation for my suggestion is to help the rest of us outside of Amazon better understand the maintainers and what they are likely to be working on. The key here is likely and not exclusively. Having a bit more info helps the rest of us:

  • understand who to talk to if we need to escalate a PR if it gets neglected for a long time or if something urgent comes up.
  • learn about potential gaps that we could fill - maybe no one from Amazon is focused in a particular area that one of us has expertise in.
  • we're all individuals interacting with each other, and if we all know a bit more about the people in leadership positions, it can help the rest of us understand where you're coming from.
@geekygirldawn geekygirldawn added the enhancement New feature or request label Apr 16, 2021
@boktorbb
Copy link
Contributor

boktorbb commented May 3, 2021

I think that this topic was adequately covered in this issue over in the OpenSearch repo:

https://github.com/opensearch-project/OpenSearch/issues/537

On the dashboards side, we also haven't had the chance to particularly specialize into any roles and as alpha/beta releases keep moving forward we want to maintain an open process to allow for any available person to tackle what needs to be done at any given time.

We are currently working on a process that will help address some of the issues you bring up, such as PR escalation.

@boktorbb boktorbb closed this as completed May 3, 2021
SuZhou-Joe added a commit to SuZhou-Joe/OpenSearch-Dashboards that referenced this issue Mar 15, 2024
* fix: authInfo destructure



* fix: unit test error



---------

Signed-off-by: SuZhou-Joe <[email protected]>
SuZhou-Joe added a commit to SuZhou-Joe/OpenSearch-Dashboards that referenced this issue Mar 18, 2024
* fix: authInfo destructure



* fix: unit test error



---------

Signed-off-by: SuZhou-Joe <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants