emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: I have terminated my assignment
Date: Wed, 3 Apr 2013 10:07:50 +0200	[thread overview]
Message-ID: <933E4B38-1594-4300-BCA6-F781B2615DE5@gmail.com> (raw)
In-Reply-To: <87ehesb1on.fsf@gmail.com>

Jambunathan,

I am not entering a discussion here, based on some wildly
constructed examples.  What I am doing is countering the
impression you are lately trying to make, that these files
were never intended for release and Emacs.  You are trying
to imply this by insisting that they were "in contrib".
This is a false impression for two reasons, as I have shown
in my previous mail.

The copyright quotation is not about the year, but about
the fact that it says "FSF", not "Jambunathan".  This was
never changed, also not when you changed the author name
from "Nicolas Goaziou" (because the files was apparently
created by changing a copy org-e-latex.el) to your name.

http://orgmode.org/cgit.cgi/org-mode.git/commit/EXPERIMENTAL/org-e-html.el?id=fac58412f3c23a4c3cb03e050cd7809cfc8651fe

Org-mode is not a company.  It is an open source project,
and the complete project history is open to the world.
It's most important distribution channel is as git
repository - so it is published and republished after
each push to the main repository at orgmode.org. 
Introducing cuts like a tar ball release is artificial
for this discussion.  At each state it may contain bugs
and typos, but fact that the copyright notice was never
changed shows at the very least that you did not care,
and probably it shows that you, at the time, were
proud to contribute to the Org-mode and Emacs and
perfectly aware that the copyright was transferred to
the FSF.

It is known that your intent has now changed, but the
original intent was plain to you and others and has caused
others to rely on the code, to add and invest.  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.

- Carsten

[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.


On 3.4.2013, at 07:52, Jambunathan K <kjambunathan@gmail.com> wrote:

> 
> Carsten
> 
>> When this code first entered the Org-mode repository, it was not in
>> contrib/.  The code entered in EXPERIMENTAL/.  Both files where marked
>> "Copyright (C) 2011-2012 FSF" and "Copyright (C) 2010-2012 FSF" from
>> the first moment they entered into the repository, in agreement with
>> Jambunathan's standing assignment with the FSF at the time.
>> 
>> http://orgmode.org/cgit.cgi/org-mode.git/commit/EXPERIMENTAL/org-e-html.el?id=93ec2c7a5034944f5f6c77be6f37c49b4a697b72
>> 
>> http://orgmode.org/cgit.cgi/org-mode.git/commit/EXPERIMENTAL/org-e-odt.el?id=c2ea76e71034a161d875647b27cfbd72264b5d64
>> 
>> The files moved to contrib/ only in April of 2012, in a period when
>> the exporter structure was fleshed out and completed.  This move was
>> clearly a staging event for a later move into core, rather than a
>> change of copyright assignment.  While unassigned files are are only
>> allowed in contrib/, the reverse is not true and never was.
> 
> What does FSF record indicate?  
> 
> Last I checked, it indicates that Emacs contains no such files and these
> files are unknown to the Emacs product.  FSF email records also say that
> I have out of my own initiative refused to assign *my* rights to them.
> 
> ----------------------------------------------------------------
> 
> I haven't authorized Bastien to move contrib/lisp changes to lisp/.  I
> invite him to show a proof to that effect. 
> 
> ----------------------------------------------------------------
> 
> What you indicate is daily routine.  IMNSHO, they are good to know but
> not substantial to resolve the dispute.  
> 
> It is common knowledge that unreleased source is *known* to show wrong
> Copyright years prior to release.  Corporations securely back up - as in
> put in a locker - only released tar balls.
> 
> ----------------------------------------------------------------
> 
> What matters is the product (product here is Emacs) and a public release
> of product together with source tarball.
> 
> Org-8.0 is not released yet.  It is a work-in-progress and not known to
> public at large.  Org-8.0 is not in Emacs, it is merely a staging ground
> for Emacs and Emacs maintainers will do their own due diligence
> *independent* of the due diligence done by Org maintainer.
> 
> ----------------------------------------------------------------
> 
> Thought experiment: 
>   I steal my employer's code, slap my authorship and assign copyright to
>   FSF.  Does that mean the code is assigned to FSF? No.
> 
> ----------------------------------------------------------------
> 
> Bottomline: 
>   Intent to act is not the same as act itself.
> 
> Jambunathan K.

  reply	other threads:[~2013-04-03  8:07 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 [this message]
2013-04-03  8:37       ` Jambunathan K
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=933E4B38-1594-4300-BCA6-F781B2615DE5@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kjambunathan@gmail.com \
    /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).