-
Notifications
You must be signed in to change notification settings - Fork 113
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
Suggestions from the CK survey #132
Comments
Fixed broken release: https://github.com/ctuning/ck/releases/tag/V1.55.0 |
Some notes about the new development methodology: https://groups.google.com/g/collective-knowledge/c/0cGOPNM1Uvw |
Forgot to mention CLA: #135 |
We relicensed to Apache 2.0 |
We work with the community to revise, test, reproduce and stabilize MLPerf workflows: https://github.com/ctuning/ck/blob/master/docs/mlperf-automation/README.md |
Many of these suggestions were implemented in the latest version of the CK prototype. CK is stable and has been successfully used by different companies and organizations to automate MLPerf inference submissions. That is why we have decided not to touch it anymore expect bug fixes in the CK kernel and existing MLOps components. Instead, we are developing a new CK2 framework based on user feedback. I close this issue. |
Here are some suggestions from our CK survey:
changing license to Apache 2.0dropping support for Python 2 and keeping support for Python 3.6+including CK modules to the CK core to ensure the stability of shared workflowscontinue automating MLPerf: https://github.com/ctuning/ck/blob/master/docs/mlperf-automation/README.mdcollecting all CK components in one GitHub repositoryThe text was updated successfully, but these errors were encountered: