New version of the Checklist and a question

Following up on the discussion Moving the Checklist to v1.0, MOF and Mozilla' Framework we incorporated the comments received and published an updated version of the Checklist.

This document needs to be interpreted as a learning tool, useful to further develop the answer to the question “How can I recognize an Open Source AI” in the context of the co-design process.

The Checklist came out of the Validation phase, it’s a tool to test the Open Source AI Definition, rather than testing AI systems.

We welcome ideas of how to develop this further into a more general-purpose operating manual. We have time to think about this properly, collect ideas from various stakeholders. The thread has some proposals already. @gvlx and @shujisado you seem to have some interest in this topic, would you be interested in coordinating a call for proposals to develop a general-purpose checklist?

First, a comment on the checklist. I think it’s honest to include the “Known issues.” Having the “Subject to interpretation” part in particular will likely provide reassurance to some.

This weekend, I plan to translate the FAQ into Japanese and prepare for any confusion that might arise in Japan afterward. Next week, I’m sure inaccurate translation articles related to the ATO event will end up bothering me. Additionally, I plan to hold a meeting soon to provide a detailed explanation of OSAID, and I’ve already started preparing for it. So, I’m a bit pressed for time.

1 Like