From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH] doc: minor updates to design notes
Date: Mon, 26 Dec 2016 21:41:58 +0000 [thread overview]
Message-ID: <20161226214158.14141-1-e@80x24.org> (raw)
ssoma is not worth marketing, but perhaps our mirror of
the git mailing list archives is...
---
Documentation/design_notes.txt | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/Documentation/design_notes.txt b/Documentation/design_notes.txt
index c7a8b26..c637302 100644
--- a/Documentation/design_notes.txt
+++ b/Documentation/design_notes.txt
@@ -56,7 +56,8 @@ Why email?
* git, one of the most widely-used version control systems, includes many
tools for for email, including: git-format-patch(1), git-send-email(1),
git-am(1), git-imap-send(1). Furthermore, the development of git itself
- is based on the git mailing list.
+ is based on the git mailing list: https://public-inbox.org/git/
+ (or http://hjrcffqmbrq6wope.onion/git/ for Tor users)
* Email is already the de-facto form of communication in many Free Software
communities..
@@ -86,6 +87,11 @@ Why perl 5?
* git and SpamAssassin both use it, so it should be one less thing for
admins to install and waste disk space with.
+* Distributing compiled binaries has higher costs for storage/cache
+ space is required for each architecture. Having a runnable,
+ source-only distribution means any user already has access to all
+ of our source.
+
Laziness
--------
@@ -112,12 +118,11 @@ Laziness
* Avoids bikeshedding about web UI decisions, GUI-lovers can write their
own GUI-friendly interfaces (HTML or native) based on public archives.
- Maybe one day integrated MUAs will feature built-in git protocol support!
Web notes
---------
-* Getting users to install/run ssoma (or any new tool) is difficult.
+* Getting users to install/run any new tool is difficult.
The web views must be easily read/cache/mirror-able.
* There may also be a significant number of webmail users without
--
EW
reply other threads:[~2016-12-26 21:41 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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161226214158.14141-1-e@80x24.org \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).