Proposal for a SIG for model signing and transparency #10
Comments
|
We have voted during the WG meeting and we got 15 "Yes" votes and 0 "No" votes |
|
Is there a link to the deck presented at monday's meeting that could be added to this issue? How can individuals beyond the initial three identified become involved in this? |
|
I'll ask for the slides. To get involved, I think we'll do post a calendar + zoom invite to this issue first and notify the working group and then the meetings will be happening periodically. I need to handle a few more processes for the launch of the SIG and then I'll notify here. |
|
The slides presented during the meeting are available here Thanks again for the support and looking forward to making strides on the project! |
|
Hi, I would be interested in writing documentation for this. Thanks. |
|
To update, the first meeting of the SIG will be on May 15th at 8 AM Pacific time after which it will repeat every other week. The event is now added to the OpenSSF calendar. Hope to see everyone at the SIG meeting |
|
|
|
The first meeting occurred today. The agenda is at https://docs.google.com/document/d/18oAsfhfKJurH-YTUFe520CAZS3lkORX1WnZmBv4Llkc/edit |
|
Thanks reviewing now. |
|
Closing this one since the SIG (soon to be project, see ossf/tac#347) is formed and already had several meetings. There's nothing remaining to be done here |
We have a working group that meets for model signing work, as part of ossf/ai-ml-security#10. Since this working group helps in developing https://github.com/sigstore/model-transparency and building standards around it, it needs to be officially a project, not a WG. We add the project at a sandbox stage. Please note that there are 2 repos invovled here: - https://github.com/sigstore/model-transparency which will be owned by Sigstore and is just the implementation work for the library for model signing - a new repository to be created under https://github.com/ossf to represent standard documents, as outputs of this project These two repositories should work in unison to achieve a common goal. Signed-off-by: Mihai Maruseac <mihaimaruseac@google.com>
We have a working group that meets for model signing work, as part of ossf/ai-ml-security#10. Since this working group helps in developing https://github.com/sigstore/model-transparency and building standards around it, it needs to be officially a project, not a WG. We add the project at a sandbox stage. Please note that there are 2 repos invovled here: - https://github.com/sigstore/model-transparency which will be owned by Sigstore and is just the implementation work for the library for model signing - a new repository to be created under https://github.com/ossf to represent standard documents, as outputs of this project These two repositories should work in unison to achieve a common goal. Signed-off-by: Mihai Maruseac <mihaimaruseac@google.com>
We have a working group that meets for model signing work, as part of ossf/ai-ml-security#10. Since this working group helps in developing https://github.com/sigstore/model-transparency and building standards around it, it needs to be officially a project, not a WG. We add the project at a sandbox stage. Please note that there are 2 repos invovled here: - https://github.com/sigstore/model-transparency which will be owned by Sigstore and is just the implementation work for the library for model signing - a new repository to be created under https://github.com/ossf to represent standard documents, as outputs of this project These two repositories should work in unison to achieve a common goal. Signed-off-by: Mihai Maruseac <mihaimaruseac@google.com>
Purpose: Create a cryptographic signing specification for artificial intelligence and machine learning models, addressing challenges such as very large models that can be used separately, and the signing of multiple disparate file formats held within a directory. This specification may have wider applicability to signing directories of multiple arbitrary file formats. This specification may later be proposed as a formal standard.
Initial participants:
The text was updated successfully, but these errors were encountered: