From: tsd@tsdye.com (Thomas S. Dye)
To: "W. Greenhouse"
<public-wgreenhouse-sGOZH3hwPm2sTnJN9+BGXg@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org,
public-emacs-devel-mXXj517/zsQ@plane.gmane.org
Subject: Re: A proposal (ox-html.el/ox-odt.el)
Date: Tue, 12 Mar 2013 08:38:15 -1000 [thread overview]
Message-ID: <m1ip4wpip4.fsf__48709.4213291586$1363185328$gmane$org@tsdye.com> (raw)
In-Reply-To: <87ppz4r1pu.fsf@riseup.net> (W. Greenhouse's message of "Tue, 12 Mar 2013 17:02:05 +0000")
Aloha all,
wgreenhouse-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org (W. Greenhouse)
writes:
> Jambunathan,
>
> Jambunathan K <kjambunathan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
>> People are disregarding my "moral rights" over my work and pushing me in
>> a corner to act a certain way to serve their own interests. This I feel
>> is plain wrong and an act of snatching or appropriation.
>>
>> Jambunathan K.
>
> Moral right and copyright are unrelated concepts. In the jurisdictions
> that recognize "author's moral right" or "droit moral" (much of the EU
> and other civil-code countries), such right is non-assignable and would
> not even be affected by the FSF papers. However, in the jurisdictions
> where copyright is assignable, it has nothing to do with author's moral
> right.
>
> If we're going to discuss "moral right" in the less legalistic and more
> broad sense of your rights in an ethical society as a person with
> agency, I think you're disregarding the rights of prior contributors to
> the ox-html program, of which you were but one of many. Those
> contributors did intend the code to become part of Emacs, and, morally
> as well as legally, you entered into an agreement to further that aim
> when you decided to work on it. If you really do intend to take your
> ball and go home, do please call a fork a fork--and also do please
> recognize that you are the one "snatching" or "appropriating" a joint
> work out of your own sense of pique.
>
>> I want to fork ox-html.el and ox-odt.el (as it stands today in Org repo)
>> to GNU ELPA repo. I request that Emacs maintainers recognize the GNU
>> ELPA version (maintained by me) as the authoritative official versions
>> of these files that gets bundled with SUMO Emacs.
>
> ...
>
>>
>> Jambunathan
>> +---------------+
>> | ox-html.el +--- push Emacs maintainer
>> | ox-odt.el | \-----
>> | GNU ELPA | \----- +--------------------+
>> | | \-->| |
>> +---------------+ | lisp/org/ox-html.el|
>> ^ Push | lisp/org/ox-odt.el |
>> | | |
>> | +--------------------+
>> | | Other org files |
>> +------+---------+ /->| |
>> | | /--- | |
>> | Org repo | /---- | |
>> | | /--- +--------------------+
>> | +-- push
>> | |
>> | |
>> +----------------+
>> Org maintainer
>
>
> This makes no sense at all. It is needless busywork for the Emacs
> maintainer to integrate code from one particular contributor who is unable
> to cooperate with the maintainer of the project to which he
> contributes. It also unnecessarily inconveniences ordinary Emacs/Org
> users, who would now face a further obstacle to simply using the
> software. They already have to go elsewhere to get contrib/ programs
> or to use the latest version of Org; now you want to make it so that
> even the release version of Org is fractured and schismed. That is
> totally unacceptable.
If this analysis is correct, then Jambunathan's proposal furthers his
stated purpose "to delay the release [of Org] or cause confusion".
I am concerned (perhaps out of ignorance) that Jambunathan's ability to
contribute code to Org might be used to the same effect.
Because I am keen to know that my investment in Org is being suitably
protected, could someone assure me either that my concern is unfounded,
i.e., that code contributed by Jambunathan can be successfully vetted so
that it doesn't delay development or cause confusion, or that
appropriate steps have been taken to ensure that future code
contributions from Jambunathan will not become part of Org?
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
prev parent reply other threads:[~2013-03-12 18:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ober717z.fsf@gmail.com>
2013-03-11 10:09 ` Copyright/Distribution questions (Emacs/Orgmode) Christian Egli
[not found] ` <874ngitfh9.fsf__7395.48305650732$1362996921$gmane$org@sbs.ch>
2013-03-11 14:13 ` Jambunathan K
[not found] ` <jwvtxoi4qyq.fsf-monnier+emacs@gnu.org>
[not found] ` <E1UF6zR-0006De-El@fencepost.gnu.org>
[not found] ` <87mwu9iwcp.fsf@gmail.com>
[not found] ` <CAKKEbDvz=QundLsy47cuHS7CPqogm2vnb6ujYH7yBks9MXVdSw@mail.gmail.com>
[not found] ` <87mwu9fiu0.fsf@uwakimon.sk.tsukuba.ac.jp>
[not found] ` <D291D82C-4FB7-4D8F-A7AD-E6072359DCBF@gmail.com>
2013-03-12 6:23 ` A proposal (ox-html.el/ox-odt.el) Jambunathan K
2013-03-12 17:02 ` W. Greenhouse
2013-03-12 18:38 ` Thomas S. Dye [this message]
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='m1ip4wpip4.fsf__48709.4213291586$1363185328$gmane$org@tsdye.com' \
--to=tsd@tsdye.com \
--cc=public-emacs-devel-mXXj517/zsQ@plane.gmane.org \
--cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
--cc=public-wgreenhouse-sGOZH3hwPm2sTnJN9+BGXg@plane.gmane.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).