Doug Tangren

I totally get that. What I'm trying to gain a sense of is how nesessary docker builds are now that host configured builds ar exposed. Here's a snippet of the...

Im going to go ahead and close this, I was able to unblock myself to testing with another gmail account. feel free to close this

This problem https://github.com/jonhoo/rust-imap/issues/106, something was up with my google account that caused this library to be unable to parse the imap responses. I timeboxed investigating that then ended up just...

I see there's a 'kv_unstable' feature flag in the latest version of the `log` crate but it's unclear how to interface with in from an application. Is this not something...

I found [this commit](https://github.com/rust-lang/log/commit/c3a9a14c580e57840d6cf0861774681def5805c5) which seems like it reverted an interface users could leverage is https://docs.rs/kv-log-macro the crate users should be guided towards?

What's the story for the kv visitor trait and serde. It seems today the visit api gives you a access to a [Key and Value](https://github.com/rust-lang/log/blob/813b6ce4793b50d4a60aa28c057f79902c8dfbe0/src/kv/source.rs#L191). You can get the `&str`...

@KodrAus that's awesome! Is anyone actively working on this? I'd love to help but am not caught up on all the current and prior discussion.

This sounds great. I'll be sure to drop a note here if I start anything.

Could some of this now be handled with log's builtin structured logging interfaces?

The latter seems to keep the surface area small. `error!("whoops", { error: e })` you get the reuse the same syntax for the same semantic purpose, annotating a log message...