laurentsimon

> Oh, you're thinking from the point of view of the CLI usage. I was thinking from the point of view of a ML training pipeline that needs to orchestrate...

> > Can you provide more details about the requirements for this? What are the constraints? How are models stored between runs? Where does [#160 (comment)](https://github.com/sigstore/model-transparency/issues/160#issuecomment-2110785159) fail for this use...

> With a `recompute_files` we need to scan the directory tree and then we need to compare with the entire manifest (i.e., traversing every key in a dictionary) to compute...

@mihaimaruseac what do you think of making these the prio for v1?

> I think #157 might also be good to have in the release Good call. Added to the list. Thanks!

This was discussed in the SIG meeting of 12 June 24. We would like to also support private PKI for this release. (We don't need to support all possible features,...

> I'm not convinced that you must be the owner of a certificate to upload it to your repository; usage of a non-owned model could definitely be legit, e.g. a...

We also need documentation for the API. Note: I've created a tracking issue for auto-generation / update of docs https://github.com/sigstore/model-transparency/issues/209

This is now working with https://github.com/sigstore/sigstore-python/pull/962 High-level: - clone sigstore-python and use branch from https://github.com/sigstore/sigstore-python/pull/962 - make dev - source env/bin/activate - python3 -m pip install psutil==5.9.8 - clone this...

ah, good catch. I've assigned the issue to you. @mihaimaruseac wrote some benchmark code in Python a while back. @mihaimaruseac would you be able to share?