[Repository Request] New GitHub repository named opensearch-dev-tools

[peterzhuamazon]

Are you requesting a new GitHub Repository within opensearch-project GitHub Organization?

yes

GitHub Repository Proposal

Sample RFC: opensearch-project/OpenSearch#19035 More to come.

GitHub Repository Additional Information

1. What is the new GitHub repository name?
   opensearch-dev-tools
2. Project description and community value?
   This repository is aimed to hold multiple opensearch related development tools. Including but not limited to opensearch query profiler, profiler visualization, cluster tool, and more. This is a centralized location to host dev related tools and welcome new contributions to the collection.
3. What user problem are you trying to solve with this new repository?
   Right now, several community related tools are located in individual repositories and hard to explorer and list by users. We want to follow similar practice like mcp/servers so that community can register their tools officially in the opensearch-project org and invite reviews from broader audiences.
4. Why do we create a new repo at this time?
   Because we are seeing more tools contributed to the community and feels like a good time to start a new repository for this.
5. Is there any existing projects that is similar to your proposal?
   Not in opensearch-project.
6. Should this project be in OpenSearch Core/OpenSearch Dashboards Core? If no, why not? Or, shall we combine this project to an existing repo source code in opensearch-project GitHub Org?
   No, this are dev tools not a plugin. We can, however, have similar features implemented in existing plugins, but that is another different topic.
7. Is this project an OpenSearch/OpenSearch Dashboards plugin to be included as part of the OpenSearch release?
   No

GitHub Repository Owners

1. Who will be supporting this repo going forward?
   Individual tool maintainers from different teams.
2. What is your plan (including staffing) to be responsive to the community (at a minimum, this should include reviewing PRs, responding to issues, answering forum questions?)
   OpenSearch Engineering Effectiveness team will work with individual owners together.
3. Initial Maintainers List (max 3 users, provide GitHub aliases):
   @getsaurabh02 @peterzhuamazon @gaiksaya

GitHub Repository Source Code / License / Libraries

1. Please provide the URL to the source code.
   https://github.com/aayush-bharti/opensearch-cluster-dev-tool
   https://github.com/aswath86/opensearch-query-profiler
   https://github.com/shreyah963/query-profile-visualizer
   More to come......
2. What is the license for the source code?
   Apache2.0
3. Does the source code include any third-party code that is not compliant with the Apache License 2.0?
   No

What is the publication target(s)?

You can choose multiple targets from the list.

Others

Notes (DO NOT CHANGE)

Next Steps:

• If this is about creating a new GitHub Repository

  • Build Interest Group (BIG) and its members will review your proposal and provide feedback
    • Review of Proposal, asking questions, adding comments
    • If there is any concern regarding the naming / IP, additional IP review will be requested
    • Involve Subject Matter Experts from other repositories on the proposed topics
    • Ensure new repositories align with the foundation’s charter
    • Review the provided source code if any
    • Send final feedback and recommendations to the Technical Steering Committee
  • Technical Steering Committee (TSC) will have a vote based on BIG feedback, and reply back the vote as a comment in this issue by a TSC member
  • At least three positive (+1) TSC members' votes are necessary, and no vetoes (-1) after a one week period, then Admin Team will open a repo creation ticket with Linux Foundation
  • Linux Foundation verify the votes and create repo
  • Admin Team setup automations on repo settings, secrets, scanning, add initial maintainers, and more
  • Repository delivered to the original requester

• If you already have a GitHub repo and just want to add new publication target(s)

  • Admin Team will review your request and follow up

Track the progress of your request here: Engineering Effectiveness Board (view).
Member of @opensearch-project/admin will take a look at the request soon.
Thanks!

[peterzhuamazon]

Hi @getsaurabh02 @msfroh @bugmakerrrrrr @virajsanghvi could you please give your thoughts and votes here?

Thanks.

[getsaurabh02]

Thanks @peterzhuamazon - looks good to me. This will help people contribute their custom tools and utilities back to the main project, which will benefit the broader community.

[msfroh]

Sorry I dropped the ball on this one -- I was around on August 15th, but on vacation a week later. I'm going to blame my neglect on looking forward to vacation. 😁 🌴

Anyway, normally I tend to nitpick over repository names being too specific (limiting future scope) or too generic (causing confusion and "stealing" names from potential future projects).

In this case, I think opensearch-dev-tools is pretty good. I guess the only risk for possible confusion is that it might imply that they're tools for developers who contribute to OpenSearch. That tends to be a smaller group, better connected to the project, so I think I'm okay with them being a little bit confused. (Honestly, most of us are confused a lot of the time anyway.)

So, it's a +1 from me.

[peterzhuamazon]

Thanks @msfroh @getsaurabh02 .

Hi @virajsanghvi @bugmakerrrrrr, could you also give your vote as well?

Thanks!