jrockway / eproject

file grouping ("project") extension for emacs
161 stars 41 forks source link

Please provide LICENSE or COPYRIGHT file #70

Open sten0 opened 6 years ago

sten0 commented 6 years ago

Dear eproject maintainer,

Thank you for maintaining this package. I would like to package eproject for Debian, but the absence of a LICENSE or COPYRIGHT file blocks inclusion into the archive.

Cheers, Nicholas

sten0 commented 6 years ago

Also, please consider tagging a stable release :-) At the moment the best I can do is provide a Debian-specific "upstream/1.5+git20180312.068218d-1" version, but updating eproject.el to "Version: 1.6" and tagging is strongly preferred.

andyleejordan commented 5 years ago

@sten0 This project is licensed. The license is in the typical location for Emacs Lisp packages (as part of each .el file's header).

sten0 commented 5 years ago

Hi @andschwa, I read these :-) which was why I was able to begin work on packaging eproject for Debian, and why I'm confident in PR #71 (which is GPL-3+ @ the second commit).

I believe that the Emacs library conventions were probably written before best practises including a full-text copy of the license emerged, and additionally I wonder if Emacs library conventions are written from the point of view that the most useful libraries should eventually end up as part of the Emacs project itself--which has a full-text copy of the license.

A GNU document on the topic is here https://www.gnu.org/licenses/gpl-howto.en.html "All programs, whether they are released under the GPL or LGPL, should include the [full] text version of the GPL. In GNU programs we conventionally put the license in a file called COPYING."

Please provide a full-text copy of the GPL-3+ license. In good faith I went ahead and examined every file in eproject with a fine-toothed comb, wrote the Debian copyright file (log/analysis) and packaged an untagged snapshot. Luckily an ftp-master did not reject the upload, but instead conditionally accepted it with a note to pursue clarification of eproject-as-a-whole license...also in good faith, even more so because packaging git snapshots are not considered best practise in Debian.

BTW, this one still asserts GPL-2+ https://github.com/jrockway/eproject/blob/068218d2cf2138cb2e8fc29b57e773a0097a7e8b/eproject.el#L16 in conflict with https://github.com/jrockway/eproject/blob/068218d2cf2138cb2e8fc29b57e773a0097a7e8b/contrib/README#L8