From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Ferris Ellis <ferris@ferrisellis.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Dealing with list volume
Date: Sun, 3 Dec 2017 15:03:41 +0100 [thread overview]
Message-ID: <CAHmME9oO2FMC+QJyAJtRnvS6Ey+91YTwVqCLNnU4Z2HR983__g@mail.gmail.com> (raw)
In-Reply-To: <EE5CC249-FD46-4984-8A0A-0CC583E3C3FA@ferrisellis.com>
On Sat, Dec 2, 2017 at 12:01 AM, Ferris Ellis <ferris@ferrisellis.com> wrot=
e:
> Wikis: As for wikis, I always have had mixed feelings about them. For lar=
ge
> projects like Gentoo or Arch they=E2=80=99re great, in my opinion, for co=
mmunity
> knowledge accumulation. But for smaller projects I=E2=80=99ve found havin=
g something
> to the effect of a community maintained `docs/` directory with markdown i=
s
> just simpler and easier. Plus you can always go back and generate some
> pretty webpages out of the `docs/` markdown files if you=E2=80=99ve reach=
ed the
> adoption level where people expect documentation to be in webpages.
This is what I currently have for the wireguard.com page. I should
really open source that repo. I could certainly use some more
documentation, but nobody has stepped up to create it.
next prev parent reply other threads:[~2017-12-03 13:57 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 [this message]
2017-12-07 16:34 ` Joe Doss
2017-12-08 2:33 ` Jason A. Donenfeld
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=CAHmME9oO2FMC+QJyAJtRnvS6Ey+91YTwVqCLNnU4Z2HR983__g@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=ferris@ferrisellis.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).