From: Uwe Brauer <oub@mat.ucm.es>
To: GNU Emacs <emacs-devel@gnu.org>
Subject: matlab in ELPA (or tree) part II: are all requirements fulfilled?
Date: Sun, 19 Dec 2021 10:53:45 +0100 [thread overview]
Message-ID: <87v8zk539y.fsf@mat.ucm.es> (raw)
[-- Attachment #1: Type: text/plain, Size: 2405 bytes --]
Hello
A couple of weeks ago I asked whether it is possible to include matlab
mode in ELPA or in the Emacs tree.
After some discussion RMS approved it, if, of course all required copyright
assignments are done.
Since then I tried to investigate this issue, by:
1. Running git blame
2. Checking whether the authors of commits.
a. Signed the papers.
b. Or if not, their corresponding contribution is too small
c. Their contribution has been removed.
3. I repeated this procedure by checking the git logs and our old
ChangeLog files. Then if a patch was mentioned, I generated a
patch file by running diff comparing that particular commit with
the commit before and repeating the steps above.
I pushed my findings to a new branch to our
repository at sourceforge:
git://git.code.sf.net/p/matlab-emacs/src matlab-emacs-src
The branch is called copyright. It contains a file
copyright.org with a table of patches and their state of art.
That branch also includes a directory called copyright-patches, that
contains all patches I could reconstruct.
Could someone, who is acquainted with these issues, please check and
tell me whether the requirements are satisfied, please??
Before doing this an important issue which needs a clarification.
Matlab goes back to 1991 when Matt Wette wrote the first version. In
around 2000 he sent his code to Eric Ludlam, who ever since has been the
main contributor and maintainer. The package dwelled in CVS and was
finally converted to git.
The first git commit is from December first 2005 and my findings only
cover all commits starting from 2005.
Eric told me that he is sure that there are no traces left in matlab
mode from the pre 2005 epoch, but I simply don't know how to verify
this.
GNU emacs is even older, but somehow its git repositories has quiet old
entries for example the first commit is
◍ changeset: 0:9bbf4f770ef3
Branch: default
Author: Jim Blandy <jimb@redhat.com>
Date: Thu, 18 Apr 1985 00:48:29 +0000
Phase: public
Summary: entered into RCS
Although truth being told, that is a bit of a fake entry, since redhat
as we all know was founded much later (in 1993).
So please could some wise person tell me what to do?
Thanks and regards
Uwe Brauer
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next reply other threads:[~2021-12-19 9:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-19 9:53 Uwe Brauer [this message]
2021-12-19 13:56 ` matlab in ELPA (or tree) part II: are all requirements fulfilled? Eli Zaretskii
2021-12-19 16:50 ` Uwe Brauer
2021-12-19 17:03 ` Eli Zaretskii
2021-12-19 17:08 ` Uwe Brauer
2021-12-19 17:29 ` Eli Zaretskii
2021-12-20 4:43 ` Richard Stallman
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8zk539y.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=emacs-devel@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.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).