From: "Loyall, David" <david.loyall@nebraska.gov>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Org Community
Date: Mon, 11 Mar 2013 20:54:38 +0000 [thread overview]
Message-ID: <FCEE4469EE8B234199968ECA9B0661E208702146@STNEEX10MB02.stone.ne.gov> (raw)
In-Reply-To: <513CBC82.4000600@gmail.com>
FWIW, I believe that the org-mode community should do what we can to oblige Jambunathan's request, even if/when we're not legally required to do so. I think that we should do the same for any human who wants to withdraw from an endeavor. (Don't each of you feel that your code is a part of you?)
Supposing that the group agrees that the code should be removed somehow, then at that point we can think about the most orderly way to do it. What happens, technically, if we mark it all as deprecated?
I hope this helps,
Dave Loyall
-----Original Message-----
From: emacs-orgmode-bounces+david.loyall=nebraska.gov@gnu.org [mailto:emacs-orgmode-bounces+david.loyall=nebraska.gov@gnu.org] On Behalf Of Scott Randby
Sent: Sunday, March 10, 2013 12:02 PM
To: emacs-orgmode@gnu.org
Subject: [O] Org Community
Last September, I attended a talk given by the lead developers of a prominent free software project. One of the developers spoke about the importance of maintaining a friendly community that does not drive people away. In particular, the developer emphasized that the community is more important than the code.
The org community has been wonderful since I've started using org. My questions on even the most basic matters have been answered with respect and clarity. Even though I'm a mere user of org, I've never hesitated to participate in a discussion on the mailing list.
However, I am concerned about the future of org. There is one individual who is poisoning the atmosphere by engaging in unfair and unfounded name calling that simply should not be included in messages to this list. Now this person wants to take some of their contributions out of org. The developer of the talk I attended called this tactic "hostage taking" and said that it is better for the community to let hostage takers go their own way. The project and community are more important than the code. The code can be written by others, or the community can decide to go in a different direction. Giving in to hostage takers leads to more hostage taking and the decline of the project.
Many of the users of org find it to be irreplaceable. We don't want to see org fall apart because of dissension in the community. I'm not saying that we shouldn't have dissent and disagreement. No, those are essential for a vigorous and healthy project. It is hateful and untruthful personal attacks that we should not accept no matter how significant the code contributions of those making the attacks.
Scott Randby
next prev parent reply other threads:[~2013-03-11 21:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-10 17:01 Org Community Scott Randby
2013-03-11 2:45 ` James Harkins
2013-03-11 18:18 ` Ivan Kanis
2013-03-11 19:34 ` Samuel Wales
2013-03-11 20:54 ` Loyall, David [this message]
2013-03-12 0:42 ` François Pinard
2013-03-15 15:08 ` J. David Boyd
2013-03-11 21:15 ` François Pinard
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=FCEE4469EE8B234199968ECA9B0661E208702146@STNEEX10MB02.stone.ne.gov \
--to=david.loyall@nebraska.gov \
--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).