training_policies icon indicating copy to clipboard operation
training_policies copied to clipboard

Allow available software to be released before publication, not submission

Open jonathan-cohen-nvidia opened this issue 5 years ago • 3 comments

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"

jonathan-cohen-nvidia avatar Feb 12 '20 17:02 jonathan-cohen-nvidia

See proposed language change: https://github.com/mlperf/policies/pull/22

jonathan-cohen-nvidia avatar Feb 12 '20 17:02 jonathan-cohen-nvidia

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.

bitfort avatar Feb 13 '20 17:02 bitfort

SWG:

Good discussion to have. This round we're not making changes.

bitfort avatar Jun 11 '20 16:06 bitfort