Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Joe Doss <joe@solidadmin.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Dealing with list volume
Date: Fri, 8 Dec 2017 03:33:05 +0100	[thread overview]
Message-ID: <CAHmME9r4tqFcVXQMaH-sfiNZZEjHjR2PyYbomWOCBObJ6E2+uw@mail.gmail.com> (raw)
In-Reply-To: <1463e6b8-2aff-b5f6-4375-dbce686f66c2@solidadmin.com>

Hi Joe,

On Thu, Dec 7, 2017 at 5:34 PM, Joe Doss <joe@solidadmin.com> wrote:
> We do need a place for users to communicate that isn't going to collide with
> devel chatter. https://www.discourse.org/ is pretty great for users, easy to
> use and not terrible to self host. I think it would be good to give users a
> non mailing list place to self help on their problems.

That's what IRC is for, I think. #wireguard is where people should go
to chat usually.

> I would be willing to donate the server needed to run one for WireGuard and
> the time/energy to set it up and keep it running.

Thanks for your offer to host something, but I've got more than enough
stable infrastructure for hosting new gadgets, as they occur to us.
I'm also very hesitant toward introducing a new platform, when IRC
should cut it.

> If you want to keep things
> in email, set up a wg-users list and call it a day.

I've recently been vortexing people who need super basic help toward
#wireguard, in order to leave this list for discussion of all sorts,
whether it's discussion of interesting user related things ("how do I
do this new and interesting thing I couldn't find any documentation
about?") or development things or bikeshedding or whatever else.

I wish we had some better documentation for getting people acquainted
with the basics. I don't like having to tell people, "did you read
these 6 webpages and the man pages and piece it together yet
yourself?", since the response is invariably, "ugh."

Jason

  reply	other threads:[~2017-12-08  2:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-30 13:03 Jason A. Donenfeld
2017-11-30 13:59 ` Mytril
2017-11-30 14:03   ` Jason A. Donenfeld
2017-12-01 23:01     ` Ferris Ellis
2017-12-03 14:03       ` Jason A. Donenfeld
2017-12-07 16:34 ` Joe Doss
2017-12-08  2:33   ` Jason A. Donenfeld [this message]
2017-12-08  9:02     ` David Woodhouse
2017-12-08 16:44     ` Joe Doss
2017-12-08 17:56       ` Daniel Kahn Gillmor
2017-12-08 18:09         ` Joe Doss

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=CAHmME9r4tqFcVXQMaH-sfiNZZEjHjR2PyYbomWOCBObJ6E2+uw@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=joe@solidadmin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).