training_policies
training_policies copied to clipboard
Allow available software to be released before publication, not submission
For 0.7 to mitigate the schedule compression (from 4 months to 3) and the variation in different submitter's QA burden/cycle time, proposal is to allow for a submission to be considered "available" if the software is made generally available by publication time, rather than submission time.
This assumes the software stack is made available to all auditors.
The intention is to allow for some of the QA cycle that goes with a software release to happen between submission and publication, which gives a bit more schedule slack for companies intending to submit under "available"
See proposed language change: https://github.com/mlperf/policies/pull/22
Let's revisit this next week in context of the 2 week push; and the possibility of beta. It could be an option for a v0.7 if necessary.
SWG:
Good discussion to have. This round we're not making changes.