4 ms·

Here's what I posted to our blog when this question came up: https://blog.cloudflare.com/boringtun-userspace-wireguard-rust/#comment-4401651800 https://blog.cl

Here's what I posted to our blog when this question came up: https://blog.cloudflare.com/boringtun-userspace-wireguard-rust/#comment-4401651800 https://blog.cloudflare.com/boringtun-userspace-wireguard-ru... We communicated with Jason throughout the process and have a ton of respect for him and the entire WireGuard community. In the short term, we need the flexibility to quickly update BoringTun's code base to support the project we built it for. That's harder when you need to coordinate with people outside Cloudflare and when we need to move as fast as we plan to. However, we really believe in Open Source and want the WireGuard community to thrive. We licensed the code very openly (3-paragraph BSD) and WireGuard may choose to fork it. If they do, we'll support it and plan to contribute any improvements in our own fork back. Over the long term, I think we're very open to merging this back into the upstream project.

StavrosK 8y ago
Oh, I missed that comment, thank you. That makes sense.
tw04 8y ago
I guess that doesn't make sense to me. If Jason offered you your own sub-project to run with, why can't you "move fast"? >I thought the invitation to put their engineers as the head of a WireGuard subproject was a cool invitation, but alas. https://lists.zx2c4.com/pipermail/wireguard/2019-March/004048.html https://lists.zx2c4.com/pipermail/wireguard/2019-March/00404... I mean no offense, but the response comes off as corporate approved PR. "We need to move fast" when you haven't actually even tried engaging with the parent project and have no idea whether or not it would prohibit "moving fast" is disingenuous IMO.
- deleted 8y ago
  [deleted]
- eridius 8y ago
  Presumably there’s still overhead involved in being part of the WireGuard organization, no? If there wasn’t, then the only difference between being in it and not is branding. More importantly, without having already tried it, it’s hard to predict how much overhead there will be. Since CloudFlare had a (self-imposed) deadline, working fast had to take priority over optics. After all, the project can always be folded into the WireGuard organization later.

StavrosK 8y ago

Oh, I missed that comment, thank you. That makes sense.

tw04 8y ago

I guess that doesn't make sense to me. If Jason offered you your own sub-project to run with, why can't you "move fast"? >I thought the invitation to put their engineers as the head of a WireGuard subproject was a cool invitation, but alas. https://lists.zx2c4.com/pipermail/wireguard/2019-March/004048.html https://lists.zx2c4.com/pipermail/wireguard/2019-March/00404... I mean no offense, but the response comes off as corporate approved PR. "We need to move fast" when you haven't actually even tried engaging with the parent project and have no idea whether or not it would prohibit "moving fast" is disingenuous IMO.

deleted 8y ago
[deleted]
eridius 8y ago
Presumably there’s still overhead involved in being part of the WireGuard organization, no? If there wasn’t, then the only difference between being in it and not is branding. More importantly, without having already tried it, it’s hard to predict how much overhead there will be. Since CloudFlare had a (self-imposed) deadline, working fast had to take priority over optics. After all, the project can always be folded into the WireGuard organization later.