Erick Tryzelaar

We've partially figured out our offline story. Some of our plans are documented [here](https://fuchsia.dev/fuchsia-src/concepts/packages/package_update). Fuchsia packages really are just a listing of a file path to a list of content...

I recently learned of another attempt at a canonicalization scheme in the draft IETF spec [rundgren-json-canonicalization-scheme](https://datatracker.ietf.org/doc/draft-rundgren-json-canonicalization-scheme/). It doesn't have the same issue where strings may contain invalid JSON characters. It's...

We need exact target lengths in bytes for Fuchsia. We use a content addressed file system on Fuchsia called `blobfs`, where each file (we call them `blob`s at this point)...

I just read through README.rst, and it looks like I was supposed to submit this against the `draft` branch. However that branch hasn't been touched since 2019. Should I change...

For a real-world example - On Fuchsia, we support a single executor and runtime [fuchsia_async](https://cs.opensource.google/fuchsia/fuchsia/+/master:src/lib/fuchsia-async) library. However, in order to more easily share libraries across host and target, we've partially...

I agree with @afetisov. If I remember correctly, I added `unwrap_or_default` a long time before 1.0, back when we were just feeling out how APIs would work with traits. Nowadays...

It looks like we also got some test failures. I'd also like the `additional_fields` to have some tests too. It might be better to factor that out into a separate...

FYI I did find a bug in rust-tuf's delegation https://github.com/theupdateframework/rust-tuf/issues/381.

I just realized that switching our metadata generation to building metadata with the spec_version of `1.0.0` would cause old clients to reject the now spec-conformant metadata, so we need to...

Yeah, although I saw and landed a patch that removed a number of unnecessary trait bounds. It might be that inheriting `Send` might not be necessary anymore.