Re: New package for Sweden: package-header.el - was Re: Interacting with minibuffer

[Jean Louis <bugs@gnu.support>]

* Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> [2021-05-23 03:21]:
>   https://dataswamp.org/~incal/emacs-packs/buc.el
> 
> not done, how to make a pack of more than one file?

Read: (info "(elisp) Multi-file Packages")

> But these
> 
>   https://dataswamp.org/~incal/emacs-packs/caps-back.el
Cannot be installed, lacks file header

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

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

Also add information on how to contact you by electronic and paper mail.

  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.

> are done?
> 
> also, check out other potential packs here:
> 
>   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.


-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

Sign an open letter in support of Richard M. Stallman
https://stallmansupport.org/