From: "Johnny Bergström" <johnny@joonix.se>
To: wireguard@lists.zx2c4.com
Subject: a couple of unrelated questions
Date: Thu, 21 Mar 2019 17:50:56 +0100 [thread overview]
Message-ID: <16381132-7BBB-43B3-AF62-EBB055B79015@joonix.se> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1206 bytes --]
Hello,
I’m currently developing a couple of services which will use Wireguard as its core enabler.
While looking for somewhere to ask questions or post issues I found this list, so here it goes:
1. Why not enable issue tracking on Github (and preferably not "only a mirror")? It would be much easier for someone like me to follow known problems and questions as most other open source projects are on the same platform. I would expect more contributions to your project would be the result.
2.1 Why block building with Go on linux like this: https://github.com/WireGuard/wireguard-go/blob/master/donotuseon_linux.go <https://github.com/WireGuard/wireguard-go/blob/master/donotuseon_linux.go>
Kernel module is preferred, but there are still use cases where you want the Go version even when it’s linux behind the scenes.
2.2 Would you accept a pull request for refactoring the Go version to become a re-usable module? E.g. not have everything in package main.
3. Are there plans on a custom URL handler for the Android and iOS for easily importing a config?
As opposed to the steps involved in first then going into the app and importing.
Thank you for a great project!
Johnny
[-- Attachment #1.2: Type: text/html, Size: 1796 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
reply other threads:[~2019-03-23 0:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=16381132-7BBB-43B3-AF62-EBB055B79015@joonix.se \
--to=johnny@joonix.se \
--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).