From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: New package for Sweden: package-header.el - was Re: Interacting with minibuffer
Date: Sun, 23 May 2021 03:29:32 +0200 [thread overview]
Message-ID: <87zgwm1blv.fsf@zoho.eu> (raw)
In-Reply-To: YKmsQGxeNI3RJAuE@protected.localdomain
Jean Louis wrote:
>> But these
>>
>> https://dataswamp.org/~incal/emacs-packs/caps-back.el
> Cannot be installed, lacks file header
Maybe you got a cached version?
Try again:
https://dataswamp.org/~incal/emacs-init/caps-back.el
>> https://dataswamp.org/~incal/emacs-packs/isbn-verify.el
> Done
>
>> https://dataswamp.org/~incal/emacs-packs/issn-verify.el
> Done
>
>> https://dataswamp.org/~incal/emacs-packs/iterate-files.el
> Done
>
>> https://dataswamp.org/~incal/emacs-packs/moggle.el
> Done
>
>> https://dataswamp.org/~incal/emacs-packs/wrap-search.el
> Done
>
>> https://dataswamp.org/~incal/emacs-packs/xsel.el
> Done
>
> Keywords are often not proper in those.
Examples?
> In all your packages license is not properly referenced,
> label GPL3+ is not enough as label is not a license.
> You have to give more proper copyright notice. Example is in
> C-h C-c search for words "How to apply" but minimum I think,
> would be to provide a link to the license. Best would be to
> provide license along with the software especially if it is
> multie file package. Otherwise follow the guideline.
> There are people without Internet, GPL3+ as label means
> little. Benefiting people is best when you tell them:
>
> How to Apply These Terms to Your New Programs
>
> If you develop a new program, and you want it to be of the
> greatest possible use to the public, the best way to achieve
> this is to make it free software which everyone can
> redistribute and change under these terms.
>
> To do so, attach the following notices to the program. It is
> safest to attach them to the start of each source file to
> most effectively state the exclusion of warranty; and each
> file should have at least the "copyright" line and a pointer
> to where the full notice is found.
>
> <one line to give the program's name and a brief idea of what it does.>
> Copyright (C) <year> <name of author>
>
> This program is free software: you can redistribute it and/or modify
> it under the terms of the GNU General Public License as published by
> the Free Software Foundation, either version 3 of the License, or
> (at your option) any later version.
>
> This program is distributed in the hope that it will be useful,
> but WITHOUT ANY WARRANTY; without even the implied warranty of
> MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> GNU General Public License for more details.
>
> You should have received a copy of the GNU General Public License
> along with this program. If not, see <https://www.gnu.org/licenses/>.
If that is considered optional I think I'll stick with GPL3+,
everyone in the computer world understands that, like TCP or
HTTP or whatever that isn't explained or even expanded.
> Also add information on how to contact you by electronic and
> paper mail.
E-mail I do have! Paper mail - optional as well? Ha.
> If the program does terminal interaction, make it output
> a short notice like this when it starts in an interactive
> mode:
>
> <program> Copyright (C) <year> <name of author>
> This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
> This is free software, and you are welcome to redistribute it
> under certain conditions; type `show c' for details.
>
> You may look into so many other Emacs packages.
Again, if that's optional I don't really care about that.
>> https://dataswamp.org/~incal/emacs-init/
>> https://dataswamp.org/~incal/emacs-init/gnus/
>> https://dataswamp.org/~incal/emacs-init/ide/
>> https://dataswamp.org/~incal/emacs-init/w3m/
>
> Good.
>
> Not all files need to be "Emacs packages" in the sense they
> can be installed, they may be programs.
Yeah, but how do you identify those who should be?
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2021-05-23 1:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 18:45 Interacting with minibuffer Sébastien Le Callonnec
2021-05-22 20:21 ` Jean Louis
2021-05-22 20:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 21:55 ` New package for Sweden: package-header.el - was " Jean Louis
2021-05-22 22:01 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 22:08 ` Jean Louis
2021-05-22 22:14 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 22:28 ` Jean Louis
2021-05-22 22:39 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 22:56 ` Jean Louis
2021-05-22 23:58 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 22:03 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 22:13 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 22:44 ` Jean Louis
2021-05-22 22:54 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 22:20 ` Jean Louis
2021-05-22 22:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 22:51 ` Jean Louis
2021-05-22 22:57 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 23:10 ` Jean Louis
2021-05-23 0:20 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-23 0:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-23 1:13 ` Jean Louis
2021-05-23 1:29 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2021-05-23 1:42 ` Jean Louis
2021-05-23 1:48 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-23 1:49 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 22:36 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 22:11 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-22 21:20 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-05-23 6:38 ` 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.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=87zgwm1blv.fsf@zoho.eu \
--to=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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.
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).