From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH] doc: add marketing guide
Date: Wed, 15 May 2019 09:04:13 +0000 [thread overview]
Message-ID: <20190515090413.31716-1-e@80x24.org> (raw)
Preventative measures; since marketing is almost always annoying
to me. And trying to avoid unintended consequences.
---
Documentation/include.mk | 1 +
Documentation/marketing.txt | 27 +++++++++++++++++++++++++++
MANIFEST | 1 +
3 files changed, 29 insertions(+)
create mode 100644 Documentation/marketing.txt
diff --git a/Documentation/include.mk b/Documentation/include.mk
index 2a02611..6415338 100644
--- a/Documentation/include.mk
+++ b/Documentation/include.mk
@@ -10,6 +10,7 @@ RSYNC = rsync
RSYNC_DEST = public-inbox.org:/srv/public-inbox/
txt := INSTALL README COPYING TODO HACKING
dtxt := design_notes.txt design_www.txt dc-dlvr-spam-flow.txt hosted.txt
+dtxt += marketing.txt
dtxt += standards.txt
dtxt := $(addprefix Documentation/, $(dtxt))
docs := $(txt) $(dtxt)
diff --git a/Documentation/marketing.txt b/Documentation/marketing.txt
new file mode 100644
index 0000000..385e517
--- /dev/null
+++ b/Documentation/marketing.txt
@@ -0,0 +1,27 @@
+marketing guide for public-inbox
+
+TL; DR: Don't market this.
+
+If you must: don't be pushy and annoying about it. Slow down.
+Please no superlatives, hype or BS.
+
+It's online and public, so it already markets itself.
+Being informative is not a bad thing, being insistent is.
+
+Chances are, you're preaching to the choir; or the folks you're
+trying to convince are not ready for everything our project
+represents to the resistance against centralization.
+
+Baby steps...
+
+There's never a need for anybody to migrate to using our
+software, or to use any particular instance of it. It's
+designed to coexist with other mail archives, especially
+other installations of public-inbox.
+
+Most importantly, we take victories even when our software
+doesn't get adopted. Freedom from lock-in is more important
+than the adoption of any software.
+
+Every time somebody recognizes and rejects various forms of
+lock-in and centralization is already a victory for us.
diff --git a/MANIFEST b/MANIFEST
index 1da40a9..2c356c6 100644
--- a/MANIFEST
+++ b/MANIFEST
@@ -7,6 +7,7 @@ Documentation/design_notes.txt
Documentation/design_www.txt
Documentation/hosted.txt
Documentation/include.mk
+Documentation/marketing.txt
Documentation/public-inbox-compact.pod
Documentation/public-inbox-config.pod
Documentation/public-inbox-convert.pod
--
EW
reply other threads:[~2019-05-15 9:04 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=20190515090413.31716-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).