That Jason asked Cloud Flare to contribute to an actual sanctioned Rust port of WireGuard --- important to Jason because the current userland implementation is Go, and thus not as fast as it could possibly be, which is a priority for Jason --- and they refused and built their own instead. Also, WireGuard-the-protocol is not a collaborative effort, and so Jason's presumably a bit concerned about a divergent fork this early in the process of getting WireGuard fielded. Particularly because Jason is just one dude working on this with a couple volunteers, and Cloud Flare is, well, yeah.

It was a pretty weird move on Cloud Flare's part. I'm not saying it was "bad", just, weird.