From: Jeff Horn <jrhorn424@gmail.com>
To: Dan Davison <dandavison7@gmail.com>
Cc: Bastien <bzg@altern.org>, emacs-orgmode@gnu.org
Subject: Re: Let's stick to one list for now
Date: Mon, 28 Feb 2011 15:23:19 -0500 [thread overview]
Message-ID: <AANLkTi=cjEOMCSvm1b_nwzgQQgP1s6E1F6Y8OtxM43jB@mail.gmail.com> (raw)
In-Reply-To: <m17hckrqpt.fsf@gmail.com>
On Mon, Feb 28, 2011 at 12:53 PM, Dan Davison <dandavison7@gmail.com> wrote:
> Julien Danjou <julien@danjou.info> writes:
>
>> On Mon, Feb 28 2011, Bastien wrote:
>>
>> The point is that there's no gain in telling people to add "[DEV]" since
>> they will forget (I will), and there is _no_ lose by splitting a list. I
>
> Hi Julien,
>
> No, I disagree with that. The two lists would have distinct compositions of the
> reader audience and that does have downsides. For example,
I would also like to re-emphasize my disagreement with Julien's
opinion. There is something to lose by splitting the list, as I
mentioned in the main thread: the mixture was entirely useful for me,
and *quite* pedagogical. I think the readership would be asymmetric in
the case of a split list. Research in behavioral economics suggests
people should be given sane defaults to prevent a harmful status quo
bias. I don't think most users ever attempt to read devel lists.
I'd also like to register a theory as to why users don't read devel
lists, and why this works for some other software: devs condescend to
handle user issues. Most open source software is created by people who
need the tool for personal use. They aren't necessarily interested in
your corner cases. For org-mode, this isn't the case; I've never felt
anything but welcomed by the people who usually develop. A split list
might also hurt this natural connection devs have with org-mode users.
Relationships are *especially* important where there aren't market
forces (read: price) to discipline developers into listening to users
demands. That's the truth about any platform (two-sided) market with a
zero price.
This may sound admittedly contrived, and a bit pumped up in regard to
the size of the effect. But there is a difference between small,
noticeable, and highly personal changes and a "_no_ lose" scenario.
Top-down policies have to be made with these small effects in mind,
with an eye toward unintended consequences of a change.
(Strawman alert. Begging Julien's pardon...)
"But," Julien might say, "my concerns count just as much as yours, and
I don't really like managing all this user mail." That is true. But
you are a power user and have many tools at your disposal to automate
mail handling. There is a relatively easy end solution. A top-down
change messes with the community ecosystem. Future users' concerns
should count for something, even if not a full measure.
--
Jeffrey Horn
http://www.failuretorefrain.com/jeff/
next prev parent reply other threads:[~2011-02-28 20:23 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-27 10:30 Splitting mailing list Julien Danjou
2011-02-27 11:43 ` Bastien
2011-02-27 14:09 ` Julien Danjou
2011-02-27 14:19 ` Gour
2011-02-27 14:22 ` Matthew Sauer
2011-02-27 20:49 ` Alan L Tyree
2011-02-27 22:53 ` Andrew J. Korty
2011-02-28 0:15 ` Alan L Tyree
2011-02-28 0:21 ` Matthew Sauer
2011-02-28 20:43 ` Eric S Fraga
2011-02-28 8:48 ` Julien Danjou
2011-02-28 9:48 ` Alan Tyree
2011-02-28 2:38 ` Nick Dokos
2011-02-28 10:46 ` Bastien
2011-02-28 12:12 ` Julien Danjou
2011-02-28 12:44 ` Bastien
2011-02-28 12:58 ` Jambunathan K
2011-02-28 14:14 ` Julien Danjou
2011-02-28 16:14 ` Nick Dokos
2011-02-28 17:12 ` John Hendy
2011-03-01 11:50 ` Bastien
2011-02-27 21:20 ` Jeff Horn
2011-02-27 21:26 ` Jeff Horn
2011-02-27 22:20 ` Samuel Wales
2011-02-28 10:49 ` Bastien
2011-02-28 15:03 ` Ian Barton
2011-02-28 17:05 ` Samuel Wales
2011-02-28 20:17 ` Konrad Hinsen
2011-02-27 16:23 ` Chris Thompson
2011-02-27 16:56 ` Julien Danjou
2011-02-28 9:50 ` Torsten Wagner
2011-02-28 11:02 ` Let's stick to one list for now (was: Splitting mailing list) Bastien
2011-02-28 11:34 ` Let's stick to one list for now Julien Danjou
2011-02-28 17:06 ` Eric Schulte
2011-02-28 17:09 ` Automatic Org-mode mailing list signature -- Was: [O] " Eric Schulte
2011-02-28 18:14 ` Automatic Org-mode mailing list signature -- Was: " Nicolas
2011-02-28 18:58 ` Eric Schulte
2011-03-01 4:30 ` Automatic Org-mode mailing list signature -- Was: [O] " theo
2011-03-02 17:35 ` Bastien
2011-03-02 17:54 ` Eric Schulte
2011-03-02 18:22 ` Automatic Org-mode mailing list signature -- Was: " Nicolas
2011-03-02 18:51 ` theo
2011-03-03 8:25 ` Bastien
2011-03-03 8:36 ` Gregor Zattler
2011-03-03 13:49 ` Eric S Fraga
2011-03-03 14:01 ` Bernt Hansen
2011-03-03 15:09 ` Julien Danjou
2011-03-03 15:12 ` Carsten Dominik
2011-03-03 16:33 ` Bastien
2011-03-03 17:02 ` Achim Gratz
2011-03-03 17:53 ` Nick Dokos
2011-03-04 9:57 ` Julien Danjou
2011-03-02 21:44 ` Automatic Org-mode mailing list signature -- Was: [O] " Achim Gratz
2011-03-02 22:59 ` suvayu ali
2011-03-03 8:23 ` Bastien
2011-02-28 17:53 ` Dan Davison
2011-02-28 18:10 ` Jambunathan K
2011-02-28 20:23 ` Jeff Horn [this message]
2011-03-01 11:55 ` Bastien
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://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTi=cjEOMCSvm1b_nwzgQQgP1s6E1F6Y8OtxM43jB@mail.gmail.com' \
--to=jrhorn424@gmail.com \
--cc=bzg@altern.org \
--cc=dandavison7@gmail.com \
--cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).