From: James Harkins < jamshark70@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Org Community
Date: Mon, 11 Mar 2013 02:45:48 +0000 (UTC) [thread overview]
Message-ID: <loom.20130311T034238-232@post.gmane.org> (raw)
In-Reply-To: 513CBC82.4000600@gmail.com
Scott Randby <srandby <at> gmail.com> writes:
> 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.
I'm inclined to agree with this.
I don't feel like hesitating to name names. Jambunathan: Whatever offense was
done to you, it remains true that ego-validation often (perhaps even usually)
does not go along with accomplishing goals. I would like to be sympathetic to
the injustice you feel. This is difficult when your approach to the problem
is to hold your ego to be more important than the goal.
So what is the point here? If the point is to have well-functioning HTML, ODT
and freemind exporters (and, secondarily, to enjoy knowing that you made, or
helped to make, that happen), I think that's a worthy goal which the org
community should support. If this is your goal, surely it can't be lost on
you that your actions are impeding that goal.
If, on the other hand, your goal is to prove that you are an Important Person
(and secondarily to contribute to org), then your actions are consistent with
that goal. However, I think the org community would not be well-served by
catering to your ego demands.
I contribute code and documentation to SuperCollider (an audio programming
language). When I check in new content, I consider it a way to thank other
developers who wrote code that I'm glad I didn't have to write myself. I
don't expect credit and I don't expect my contributions to be inviolable
entities that nobody should touch. It's not about ownership. It's about
making a software environment that works better for people. The org community
functions on the same principle, and I think it's correct that this community
should not cave in to a diva's temper tantrums.
hjh
next prev parent reply other threads:[~2013-03-11 2:46 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 [this message]
2013-03-11 18:18 ` Ivan Kanis
2013-03-11 19:34 ` Samuel Wales
2013-03-11 20:54 ` Loyall, David
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=loom.20130311T034238-232@post.gmane.org \
--to=jamshark70@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).