Add triage.md based off of security #1888
Conversation
jmazanec15
requested review from
heemin32,
navneet1v,
VijayanB,
vamshin,
naveentatikonda,
junqiu-lei,
martin-gaievski,
ryanbogan and
luyuncheng
as code owners
| @@ -0,0 +1,89 @@ | |||
| <img src="https://opensearch.org/assets/img/opensearch-logo-themed.svg" height="64px"> | |||
|
|
|||
| The maintainers of the k-NN/neural-search Repo's seek to promote an inclusive and engaged community of contributors. In | |||
There was a problem hiding this comment.
Can we separate meetings between k-NN and neural-search? I think more focused meeting for each repo could be more efficient. Two groups has different maintainers and different interests I believe.
There was a problem hiding this comment.
Mentioning of triaging issue neural-search repo in k-NN repo sounds a bit weird. Not sure what others think.
How can we handle if there are many issues in knn and we use most of the time on knn issue only? Should we divide it like 8:00AM to 8:30AM to knn and 8:30AM to 9:00AM to neural? Some people might only have interest in one of repo but not both and to save their time clear separation might be good.
There was a problem hiding this comment.
Makes sense. How about we focus every alternate week for each plugin? Not sure if 30 min is enough
There was a problem hiding this comment.
If we want to separate the meetings, we can decide the frequency and length of the meetings on a per-repo basis. I agree that 30 minutes might not be enough.
There was a problem hiding this comment.
We had a discussion with the team and everyone said to have 1 bi-weekly meeting for the 2 repos. I think we should start out with this plan and then adjust as we see fit in the future.
Signed-off-by: John Mazanec <[email protected]>
jmazanec15
force-pushed
the
triage-meeting
branch
from
2ba23af to
a1475fb
Compare
Signed-off-by: John Mazanec <[email protected]> (cherry picked from commit 7981406)
Description
Adds a triaging markdown file for a new triage meeting we are proposing for k-NN and neural search bi-weekly (please help check if I missed any copy/paste errors).
See security for details: https://github.com/opensearch-project/security/blob/main/TRIAGING.md
Highlights:
Feedback is welcome. Whatever process decided upon is not set in stone forever and can be adjusted as we go.
Will open up a similar PR in neural-search
Check List
--signoff.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.