All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Vladimir Matveev <dpx.infinity@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Rust implementation status
Date: Wed, 15 Mar 2017 08:59:42 -0700	[thread overview]
Message-ID: <CAHmME9oaJA6xTwATpc0q=h9NO_F=ae-NveccSQpw-M4i-cF5Sw@mail.gmail.com> (raw)
In-Reply-To: <1489486302.24652.2.camel@gmail.com>

On Tue, Mar 14, 2017 at 3:11 AM, Vladimir Matveev
<dpx.infinity@gmail.com> wrote:
> I see. I think that joining efforts would be nice, but, if I understand
> it correctly, that project is intended to provide a different
> interface, using WG as an underlying protocol. I personally think that
> it would be better to separate these layers, providing the connectivity
> daemon and higher-level features separately. I may be wrong though, it
> is quite possible that the combined approach will be more useful.

The objective of all wireguard implementations is to provide a simple
and uniform interface. Unity is very important. I have no interest
debating that point further. It is a stated project goal and a core
design consideration that drives discussion on this list forward.

> This is understandable, I think. But still, maybe doing development on
> Github and publishing the contents of the repository there to the main
> repository is possible? I believe that taking advantage of the issue
> tracker and the pull requests system there would be very useful and
> convenient.

The main repository is on git.zx2c4.com, but if people want to use PRs
and issues, and Sascha wants to review those, then that's of course
fine. Use whatever tools necessary. The important aspect is that the
canonical location for all WireGuard projects remains the same.

> I'm pretty sure that when WG get popuar, differences in behavior will
> be unavoidable.

You are so very wrong. If you start with this stupidity, sure, you'll
get brokenness. But if you actually attempt to carry out something
worthwhile, then each and every such difference will be squashed and
unified. I certainly intend to toil away to achieve this goal.

By the way, are you actually intending to contribute anything here, or
are you just on this list to bikeshed about procedural issues?

  reply	other threads:[~2017-03-15 15:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-05 11:42 Rust implementation status Sascha Grunert
2017-03-12 23:09 ` Vladimir Matveev
2017-03-13 16:58   ` Sascha Grunert
2017-03-14 10:11     ` Vladimir Matveev
2017-03-15 15:59       ` Jason A. Donenfeld [this message]
2017-03-15 16:51         ` Vladimir Matveev
2017-03-15 17:03           ` Jason A. Donenfeld
2017-03-13  7:04 ` sopium
     [not found]   ` <CAHmME9oFbpNBTszO_Q5m8EwiG0F0SH6BUd+1SFZGUDGH0wQ0gg@mail.gmail.com>
2017-03-13 14:39     ` Jason A. Donenfeld
2017-03-14 13:08       ` sopium
2017-03-14 16:29 ` sopium
2017-03-14 18:49   ` Sascha Grunert
2017-03-18 10:51     ` Sascha Grunert
2017-03-13 17:00 Sascha Grunert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHmME9oaJA6xTwATpc0q=h9NO_F=ae-NveccSQpw-M4i-cF5Sw@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=dpx.infinity@gmail.com \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.