emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Robert Klein <roklein@roklein.de>
To: emacs-orgmode list <emacs-orgmode@gnu.org>
Subject: Authorship and copyright of derived exporters
Date: Fri, 03 Jan 2014 13:57:32 +0100	[thread overview]
Message-ID: <52C6B3BC.2080309@roklein.de> (raw)

Hi,

I've been wondering, whom to put on the copyright line and author: lines
in a derived exporter.

For example, I have an exporter derived from the LaTeX backend which
basically is:

- the (org-export-define-derived-backend ...) call
- a renamed copy of org-latex-template modified by adding
  - five lines of comment
  - five times three lines of code
- a copy of the end-user functions of the LaTeX exporter,
  - the functions renamed for the derived exporter
  - 'latex inside them replaced for the derived exporter
- a couple of comment lines explaining the derived exporter



On the other side, I have another derived exporter (from the HTML
backend, this time) with way more of I've written myself,  but still the
end-user functions of the html backend (-export-as-html,
-convert-regino-to-html, -export-to-html, and -publish-to-html) copied,
renamed and 'html replaced inside those functions.


Should I copy the authors of the backends I derived from into my
file(s)?  I'd rather not leave them out, but, on the other hand, maybe
they don't want to be associated with my sometimes paltry attempts at
coding.

Thank you very much for your advice.

Best regards
Robert

next             reply	other threads:[~2014-01-03 12:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03 12:57 Robert Klein [this message]
2014-01-03 13:11 ` Authorship and copyright of derived exporters vilibald
2014-01-03 15:47   ` Bastien
2014-01-03 18:49     ` vilibald
2014-01-04 10:49       ` Bastien
2014-01-03 15:46 ` Bastien

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=52C6B3BC.2080309@roklein.de \
    --to=roklein@roklein.de \
    --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

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