Aurelia Molzer

> Similar to [ciborium-io](https://crates.io/crates/ciborium-io), I have re-defined a subset of the std::io traits for use within image-gif. However, unlike ciborium-io, I do not blanket-implement the trait for all types implementing...

Does anyone feel knowledgeable enough about ffmpeg and/or imagemagick, to describe how their format support discovery mechanism works? If there is a form of dynamic loading then this is out-of-scope...

@fintelia I was also thinking we should make an issue template for format requests. Specifically, a template can be constructed as purely informational such that no issue can actually be...

> Overall we could probably do a better job encouraging folks to talk with us before opening PRs to check that the feature is something we want to implement and...

That's also been my thought. We only need a ThreadPool argument if the work should not happen transparently in-scope or if we would _internally_ create a new thread that we...

I can't comment as a maintainer of `serde_json` but as a maintainer of other crates, the best path of action is to _dramatically_ cut down the size and number of...

Writing exif is the same as writing `tiff` IFDs with a different but overlapping set of keys (`u16`) used in the kv-map. Several documents gives us an almost exhaustive list...

Definitely for sketch purposes and it is lightweight enough. The unsafe dependency needs some muster, I wonder what it is for. But should not hold up the implementation in principle...

I think we'd want a new buffer type that contains some tag's data as a `Vec` together with attributes for the byte order and tag-type it was stored in. Then...

I thought you'd be able to acknowledge and merge regardless (but yea, github does not let you self-review with anything but a comment).