Hi,
Here comes yet another status report from the project of converting to
GPLv3 or later.
There are two lists of files below. The first list contains all files
that are in an undecided state. Please inspect: Do we need to do anything
with them. If so what?
The second list contains all files that we can leave untouched and the
reason for that. Please inspect: Are all reasons OK and correct?
Are we getting close to the were an inspection of the xemacs-gplv3
repository could be performed? With the intent that it that is OK we
could merge back to trunk and go GPLv3 or later?
----------------------------------------------------------------------
"CHANGES-beta"
"ChangeLog"
"PROBLEMS"
"README"
"README.GPLv3"
"etc/ChangeLog"
"etc/Emacs.ad"
"etc/InstallGuide"
"etc/NEWS"
"etc/ONEWS"
"etc/OONEWS"
"etc/README"
"etc/editclient.sh"
"etc/emacskeys.sco"
"etc/emacsstrs.sco"
"etc/gtkrc"
"etc/package-index.LATEST.gpg"
"etc/sample.Xresources"
"etc/xemacs.1"
"lib-src/ChangeLog"
"lib-src/README"
"lisp/ChangeLog"
"lisp/README"
"lisp/mule/mule-locale.txt"
"man/ChangeLog"
"man/README"
"modules/ChangeLog"
"modules/base64/Makefile"
"modules/common/configure-post.ac"
"modules/common/configure-pre.ac"
"modules/zlib/Makefile"
"nt/ChangeLog"
"nt/Emacs.ad.h"
"nt/Installation.el"
"nt/README"
"nt/Win32.cf"
"nt/lisp.ico"
"nt/site.def"
"nt/xemacs.dsp"
"nt/xemacs.dsw"
"src/ChangeLog"
"src/README"
"src/README.kkcc"
"src/m/README"
"src/s/README"
"src/s/freebsd.h"
"src/s/irix6-0.h"
"src/s/netbsd.h"
"src/s/sol2.h"
"tests/ChangeLog"
"tests/Dnd/README"
"tests/automated/README"
"version.sh.in"
----------------------------------------------------------------------
These files below are the files that we might be able to leave as
they are. The reason for why they need not to be changed is listed
after each file: (Some reasons are taken verbatim from private
communication or the "GPL version 3 source survey")
----------------------------------------------------------------------
"INSTALL" -> old FSF Documentation license
"config.guess" -> Part of config which is still GPLv2 or later. See "http://savannah.gnu.org/projects/config"
"config.sub" -> Part of config which is still GPLv2 or later. See "http://savannah.gnu.org/projects/config"
"etc/ETAGS.ChangeLog" -> BSD and GPL v2 or later
"etc/VEGETABLES" -> Not copyrightable.
"etc/XKeysymDB" -> MIT
"etc/ctags.1" -> Part of the etags distribution, which is not part of XEmacs.
"etc/custom/example-themes/ex-custom-file" -> Generated(!?) or GPL V2 or later?
"etc/etags.1" -> Part of the etags distribution, which is not part of XEmacs.
"etc/gnuattach.1" -> simple man link to gnuserv.1
"etc/gnuclient.1" -> simple man link to gnuserv.1
"etc/gnudoit.1" -> simple man link to gnuserv.1
"etc/refcard.ps.gz" -> Generated from refcard..tex
"etc/sample.Xdefaults" -> It is deprecated, so it can be removed but is only a three line reference to .Xresources
"etc/xemacs-X.ico" -> GPLv2 or later but there is not meta data for the file where this can be documented.
"info/dir" -> Generated(?)
"install-sh" -> MIT-style "no advertising" license
"lib-src/b2m.c" -> This is the version from GNU Emacs, so should be OK.
"lib-src/config.values.in" -> Generated.
"lib-src/emacs.csh" -> I don't think this even works with XEmacs ("emacsclient"), so I believe we can just delete it.
"lib-src/insert-data-in-exec.c" -> Compatible license.
"lib-src/mmencode.c" -> Compatible license.
"lisp/dump-paths.el" -> Empty file. Not copyrightable.
"lisp/term/bobcat.el" -> Emacs version has no explicit license declaration
"lisp/term/vt102.el" -> Emacs version has no explicit license declaration
"lisp/term/vt125.el" -> Emacs version has no explicit license declaration
"lisp/term/vt200.el" -> Emacs version has no explicit license declaration
"lisp/term/vt201.el" -> Emacs version has no explicit license declaration
"lisp/term/vt220.el" -> Emacs version has no explicit license declaration
"lisp/term/vt240.el" -> Emacs version has no explicit license declaration
"lisp/term/vt300.el" -> Emacs version has no explicit license declaration
"lisp/term/vt320.el" -> Emacs version has no explicit license declaration
"lisp/term/vt400.el" -> Emacs version has no explicit license declaration
"lisp/term/vt420.el" -> Emacs version has no explicit license declaration
"lock/.precious" -> Not copyrightable.
"modules/canna/install-sh" -> MIT
"modules/ldap/install-sh" -> MIT
"modules/postgresql/install-sh" -> MIT
"modules/sample/external/install-sh" -> MIT
"modules/sample/internal/install-sh" -> MIT
"move-if-change" -> Identical to GPLv3 or later Emacs version
"nt/Xmd.patch" -> GPLv2 or later but only a few lines
"nt/file.ico" -> MIT
"nt/minitar.c" -> Public domain
"nt/paths.h" -> Generated
"nt/xemacs.ico" -> GPLv2 or later but there is not meta data for the file where this can be documented.
"src/alloca.c" -> Public domain.
"src/depend" -> Generated
"src/emacs-marshals.c" -> Generated.
"src/emacs-widget-accessors.c" -> Generated.
"src/intl-auto-encap-win32.c" -> Generated.
"src/intl-auto-encap-win32.h" -> Generated.
"src/libsst.c" -> Compatible license.
"src/libsst.h" -> Compatible license.
"src/libst.h" -> Compatible copyright.
"src/linuxplay.c" -> Compatible license. (MIT-like)
"src/miscplay.c" -> Compatible license. (MIT-like)
"src/miscplay.h" -> Compatible license. (MIT-like)
"src/nas.c" -> Compatible license. (MIT-like)
"src/paths.h.in" -> Generated.
"src/s/openbsd.h" -> Too short. (< 10 lines)
"src/s/usg5-4-2.h" -> Too short. (< 10 lines)
"src/sunplay.c" -> Compatible copyright.
"tests/gtk/UNIMPLEMENTED" -> Does notes need a license?
"tests/tooltalk/beeps.el" -> Too short. (< 10 lines)
----------------------------------------------------------------------
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
After the discussion here, I think I've decided to move Gnus development
to Emacs and Emacsify the code for greater readability.
If {S,}XEmacs wants to keep tracking Gnus development, this
unfortunately means that the onus is on the {S,}XEmacs maintainers to
add an ever-growing number of Emacs compat functions, and expand
function call lists to keep up with Emacs function call lists.
(As well as adding seq/map/cllib/etc.)
The major stumbling block is, of course, lexical binding, but we'll see
how much of that creeps into Gnus after a while. Gnus is quite async in
some respects, and having proper closures makes that a lot more
readable, but on the other hand, Gnus (ab)uses dynamic scope
extensively, so...
I wrote up the decision here, with added images:
http://lars.ingebrigtsen.no/2016/01/01/its-about-ethics-in-gnus-development/
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
ACTIVITY SUMMARY (2016-01-19 - 2016-01-26)
XEmacs Issue Tracking System at http://tracker.xemacs.org/XEmacs/its/
To view or respond to any of the issues listed below, click on the issue
number. Do NOT respond to this message.
573 open ( +0) / 319 closed ( +0) / 892 total ( +0)
Open issues with patches: 13
Average duration of open issues: 2313 days.
Median duration of open issues: 2510 days.
Open Issues Breakdown
new 265 ( +0)
deferred 6 ( +0)
napping 3 ( +0)
verified 58 ( +0)
assigned 145 ( +0)
committed 19 ( +0)
documented 3 ( +0)
done/needs work 15 ( +0)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
ACTIVITY SUMMARY (2016-01-12 - 2016-01-19)
XEmacs Issue Tracking System at http://tracker.xemacs.org/XEmacs/its/
To view or respond to any of the issues listed below, click on the issue
number. Do NOT respond to this message.
573 open ( +0) / 319 closed ( +0) / 892 total ( +0)
Open issues with patches: 13
Average duration of open issues: 2306 days.
Median duration of open issues: 2503 days.
Open Issues Breakdown
new 265 ( +0)
deferred 6 ( +0)
napping 3 ( +0)
verified 58 ( +0)
assigned 145 ( +0)
committed 19 ( +0)
documented 3 ( +0)
done/needs work 15 ( +0)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
To Ian's family and the Debian community,
The XEmacs developers, testers, and user community offer our
condolences on the passing of Ian Murdock. His spirit and leadership
will be missed especially in the Debian Project, of course, but his
contributions to the ideology of free software, to theory and practice
of community building in software development, and to the practical
management of distributions will live on as a fitting memorial to the
man.
Though I don't know of any of the XEmacs core developers who
interacted with Ian personally, XEmacs as a project owes much to Linux
distributions, and the many distributions in turn owe much to Debian,
which now has some very famous "children" (eg, Ubuntu) and even
"grandchildren" (Mint) among the popular distributions. Surely this
is a testament to the great ideas of the founders of the Debian
distribution, and especially Ian himself. A large share of the
development of XEmacs (and later, our sister project SXEmacs) takes
place on Linux-based systems, and I am sure I'm not the only one who
uses Debian. Certainly developers and users are Ubuntu-based, and
thus owe much of the development of their systems to the volunteers of
Debian. And even those XEmacs developers whose primary interest was
our Windows port would often use Linux as well to develop "generic
code" that they found useful, though I don't know if any used Debian
or derived distributions.
I myself started with Slackware and BOGUS Linux in late 1994, but soon
moved to Debian GNU/Linux. My first presentation to the Tokyo Linux
Users Group in 1996 or 1997 was on the advantages of the Debian
dependency resolution system in a point/counterpoint presentation with
an RPM advocate. My mail and web hosts (including tracker.xemacs.org,
which I host and admin) have run Debian ever since. Though I have
experimented with other distributions, one reason I was comfortable
doing that was the knowledge that Debian would always be available for
"production" hosts and as a competent alternative in any application.
Though its software distribution has been the basis for development
platforms, user environments, and business, of course Debian is much
more than a bag of bytes. Ian's vision of a community-developed
distribution has borne much fruit. It's not the only way to develop
free software, and Debian was not the only pioneer, but Debian's
decentralized but democratic governance has been a model for many
projects, and I daresay it has influenced the conduct of all free and
open source software projects, including those that happen to be
managed by business firms. It certainly has informed my own activity
as an XEmacs Review Board member. The Debian Free Software Guidelines
are as important a reference for advocates of free and open source
software as the definitions published by the FSF and the OSI. While
distribution management is now a component of many languages as well
as operating systems, Debian has been a leader and model in both
theory and practice of distributing complex component systems for over
two decades.
XEmacs, like many free software projects, owes much to the
availability of free operating systems like Debian. Even those of us
who did not or do not use Debian directly are in debt for Debian's
contributions to distribution development (even one of the earliest
free software distributions for the Macintosh platform was based on
dpkg), and for the many contributions of Debian and Debian-based
developers to the libraries and operating environments we depend on
both as developers and users.
Software distributions are often likened to living things, and
certainly the Debian GNU/Linux distribution is among the most vibrant
and vivacious of distros. I pray for the consolation of Ian's family
and friends, knowing that his ideas and his work live on in the
distribution he founded.
Thank you, Ian! Long live Debian!
for the XEmacs Review Board and the community of XEmacs developers and users
Stephen J. Turnbull
Tsukuba, Japan
January 16, 2016
_______________________________________________
XEmacs-Announce mailing list
XEmacs-Announce(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-announce
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
ACTIVITY SUMMARY (2016-01-05 - 2016-01-12)
XEmacs Issue Tracking System at http://tracker.xemacs.org/XEmacs/its/
To view or respond to any of the issues listed below, click on the issue
number. Do NOT respond to this message.
573 open ( +0) / 319 closed ( +0) / 892 total ( +0)
Open issues with patches: 13
Average duration of open issues: 2299 days.
Median duration of open issues: 2496 days.
Open Issues Breakdown
new 265 ( +0)
deferred 6 ( +0)
napping 3 ( +0)
verified 58 ( +0)
assigned 145 ( +0)
committed 19 ( +0)
documented 3 ( +0)
done/needs work 15 ( +0)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta