From: Jambunathan K <kjambunathan@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: I have terminated my assignment
Date: Wed, 03 Apr 2013 14:07:55 +0530 [thread overview]
Message-ID: <87obdwm2l8.fsf@gmail.com> (raw)
In-Reply-To: <933E4B38-1594-4300-BCA6-F781B2615DE5@gmail.com> (Carsten Dominik's message of "Wed, 3 Apr 2013 10:07:50 +0200")
> It is known that your intent has now changed,
Correct.
> but the original intent was plain to you and others
Yes.
> and has caused others to rely on the code, to add and invest.
Code is GPL.
Nicolas Goaziou has already grown in respect by committing a fix to the
ODT exporter in a manner that makes Christian Moe happy. I am happy.
I will not mention how much Bastien invested in a fix for the problem
and how his fix fared when it was put to test. This pattern of Bastien
playing to the gallery is not merely anecdotal but has repeated more or
less regularly for the last 3 years or so.
The truth of the matter is Bastien has been unwilling to spend
substantial time maintaing Orgmode since he took over. I am unwilling
to trust my work in the hands of someone whose sole purpose is to please
the crowd but runs of shy of taking hard considered decisions or
actually supporting the ongoing work. To my eyes, his maintainership is
ceremonial. The unwanted side-effect is that he is having an influence
that is incommensurate with the responsibility he is shouldering.
> This is why I am helping to protect the code. Not to pry it away from
> you[1], but to protect users of and contributors to Org-mode. If we
> cannot trust that code contributed to a project like Org-mode can be
> used and built upon, then the letter and spirit of free software is
> endangered. Even if you try to paint yourself into the victim role,
> you are quite the opposite in this situation.
Fair enough.
> [1] What would I have to gain from that? I would have more
> fun rewriting it than I have writing this mail, but I do
> what I consider necessary.
Actions speak louder than words. That's where Nicolas Goaziou has
scored very consistently.
Bottomline: I will co-operate but not under current maintainer who has
never acted in a way to win my trust. I am speaking of a 3 year horizon
here.
Jambunathan K.
next prev parent reply other threads:[~2013-04-03 8:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 8:42 I have terminated my assignment Jambunathan K
2013-04-02 22:16 ` Christian Moe
2013-04-02 22:25 ` John Hendy
2013-04-03 5:38 ` Andreas Röhler
2013-04-03 14:49 ` Christian Moe
2013-04-03 4:15 ` Carsten Dominik
2013-04-03 5:52 ` Jambunathan K
2013-04-03 8:07 ` Carsten Dominik
2013-04-03 8:37 ` Jambunathan K [this message]
2013-04-03 9:14 ` Jambunathan K
2013-04-03 6:10 ` Bastien
2013-04-03 7:50 ` Jambunathan K
2013-04-03 13:22 ` Eric Schulte
2013-04-04 10:11 ` Vikas Rawal
2013-04-05 15:58 ` Christopher Allan Webber
2013-04-03 17:32 ` Eli Zaretskii
2013-04-03 17:51 ` Jambunathan K
2013-04-03 18:14 ` Eli Zaretskii
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=87obdwm2l8.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=carsten.dominik@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).