3 ms·
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 thei
by 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 agoPresumably 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.