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

Adding a readiness matrix of the various first party Backends #6912

Open
wants to merge 8 commits into
base: main
Choose a base branch
from

Conversation

zeryx
Copy link

@zeryx zeryx commented Feb 23, 2024

This PR adds a support matrix of the various first-party Triton backends, and indicates which are the "recommended path" for new developers looking to explore Triton.

The table also links to the backends themselves, along with an end-to-end example showcasing how to "get started" with that backend.

@zeryx zeryx changed the title Adding a readiness matrix of the various first party Backends [FEEDBACK_REQUESTED][WIP] Adding a readiness matrix of the various first party Backends [WIP] Feb 23, 2024
@zeryx zeryx changed the title Adding a readiness matrix of the various first party Backends [WIP] Adding a readiness matrix of the various first party Backends Feb 26, 2024
@rmccorm4 rmccorm4 self-requested a review February 26, 2024 15:02
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
@nnshah1
Copy link
Contributor

nnshah1 commented Feb 29, 2024

@zeryx - a table of supported backends is a great idea. we are in the process of updating our docs to be able to pull in information from the backends into the generated html. as well. As it stands we'll have to review more and be thoughtful in the designations of quality and recommendation. Since we don't have documented standards (yet) - I'd want to hold off on merging something like this in order to avoid giving a false impression. I would first like us to document what recommended / alpha / ready / etc. mean

Migrated OpenVINO to "Beta"

Signed-off-by: zeryx <1892175+zeryx@users.noreply.github.com>
@zeryx
Copy link
Author

zeryx commented Feb 29, 2024

@zeryx - a table of supported backends is a great idea. we are in the process of updating our docs to be able to pull in information from the backends into the generated html. as well. As it stands we'll have to review more and be thoughtful in the designations of quality and recommendation. Since we don't have documented standards (yet) - I'd want to hold off on merging something like this in order to avoid giving a false impression. I would first like us to document what recommended / alpha / ready / etc. mean

hey @nnshah1 that's great to hear. And fully agreed on what we should be declaring ready or recommended - I've updated to only contain "recommended" and "ready" for now. Let me know if you'd like to chat more about it!

README.md Outdated Show resolved Hide resolved
…ilities matrix.

Signed-off-by: zeryx <1892175+zeryx@users.noreply.github.com>
…hub markdown)

Signed-off-by: zeryx <1892175+zeryx@users.noreply.github.com>
Signed-off-by: zeryx <1892175+zeryx@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants