Repository navigation
Questions for Contribute #39170
Replies: 3 comments 2 replies
|
Absolutely! You can create an issue if you identify a genuine, reproducible bug or a clearly defined improvement that hasn't already been reported. Before opening one, search existing issues and PRs to avoid duplicates. For new operator support or broader enhancements, start a [GitHub Discussion](https://github.com/openvinotoolkit/openvino/discussions) to confirm the scope with maintainers before investing time in implementation. Documentation improvements are also welcome. See the [OpenVINO Contribution Guidelines](https://github.com/openvinotoolkit/openvino/blob/master/CONTRIBUTING.md) for details. My recommendation: Since you've already submitted a PR, ask maintainers which component needs attention most. This helps you choose a useful, appropriately scoped contribution. |
|
Thank you so much for the guidance, @beenish-majeed! I have comfortable experience with Python bindings, C++, and frontends (such as PyTorch / ONNX). Which specific component or area currently has the highest need or priority where I could best focus my efforts? or I didnt any discord community .can kindly provide me community discord ,slack link? |

Uh oh!
There was an error while loading. Please reload this page.
Hi everyone! 👋
I'm eager to contribute to OpenVINO. I have set up my local build environment and submitted a fix for Issue #39165 (PR #39169).
I checked the Good First Issues board, but all current tickets are already assigned or have active PRs. Could any mentors or maintainers recommend an unassigned bug, documentation task, or operator enablement that I could tackle next? or can I create issue ?
Thanks for your guidance!
All reactions