From: Emanuel Berg <moasenwood@zoho.eu>
To: help-gnu-emacs@gnu.org
Subject: license and where to safely store all code (was: Re: todo-did.el complete rewrite)
Date: Mon, 25 Mar 2019 19:25:47 +0100 [thread overview]
Message-ID: <86zhpizu8k.fsf_-_@zoho.eu> (raw)
In-Reply-To: m236nba1au.fsf@scratch.space
Van L wrote:
>> The last couple of days I have posted tons
>> of code (of various degrees of advancedness,
>> this is probably the most advanced) - the
>> last couple of days I have posted tons of
>> code and not received a single comment :(
>
> You've posted more than 15 LoC and not
> specified a licens
Is that where the shoe hurts?
OK, so how does it work to add a license? Do you
just type/yank it as a comment first thing in
the source file?
I have by now ~116 Elisp files! [1] A couple of
them should probably be thrown away as they are
either unaware-of duplicates of what is already
in Emacs, or just plain bad ideas. And many are
just configs with no originality/creativity to
them - well, not in terms of the code anyway :)
So it'll be a smaller number of files, for
sure. Still, surely I don't have to put
I license block in every single one of them?
Is is enough with a LICENSE file in the
same directory?
As for me, the license might as well be "Here is
a bunch of code, do whatever you want with it,
but the author would very much appreciate
comments (mails) on how to improve it or just
a note if you found it useful."
And speaking of files, anyone has a good idea
where to dump all this Elisp? I don't know how
long the university will allow my student (ha!)
home page to remain untouched on their SunOS!
BTW this is a general "problem" for me, I also
have probably as much zsh, some other code
[stats from 2015: 3], my home page...
Where do you guys put all your stuff?
[1] $ ls -1 ~/.emacs.d/emacs-init/**/*.el | wc -l
116
[2] http://user.it.uu.se/~embe8573/emacs-init/
[3] http://user.it.uu.se/~embe8573/code.txt
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2019-03-25 18:25 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 5:12 todo-did.el complete rewrite Emanuel Berg
2019-03-25 6:57 ` Van L
2019-03-25 18:25 ` Emanuel Berg [this message]
2019-03-25 18:50 ` [OFF TOPIC] Re: license and where to safely store all code (was: Re: todo-did.el complete rewrite) Emanuel Berg
2019-03-25 20:04 ` todo-did.el complete rewrite Ralph Seichter
2019-03-26 0:07 ` where to put files (was: Re: todo-did.el complete rewrite) Emanuel Berg
2019-03-26 0:53 ` where to put files Ralph Seichter
2019-03-26 2:48 ` Emanuel Berg
2019-03-26 17:15 ` Robert Thorpe
2019-03-26 8:36 ` Van L
2019-03-25 20:45 ` todo-did.el complete rewrite Stefan Monnier
2019-03-25 23:41 ` Emanuel Berg
2019-03-26 17:35 ` Stefan Monnier
2019-03-27 0:37 ` Emanuel Berg
2019-03-27 1:42 ` Amin Bandali
2019-03-27 13:12 ` what I should do, and the "Emacs News Ezine" (was: Re: todo-did.el complete rewrite) Emanuel Berg
2019-03-27 13:40 ` what I should do, and the "Emacs News Ezine" Michael Albinus
2019-03-29 9:16 ` Marcin Borkowski
2019-03-29 12:49 ` Óscar Fuentes
2019-04-01 22:07 ` Emanuel Berg
2019-03-27 14:40 ` Amin Bandali
2019-03-28 0:05 ` Van L
2019-03-29 1:38 ` Amin Bandali
2019-03-29 6:27 ` Emanuel Berg
2019-04-27 14:58 ` Van L
2019-04-27 21:09 ` Emanuel Berg
2019-03-29 5:27 ` Sacha Chua
2019-03-29 14:44 ` Drew Adams
2019-04-01 22:11 ` Emanuel Berg
2019-04-26 7:04 ` Van L
2019-04-26 7:39 ` Emanuel Berg
2019-04-27 13:07 ` Van L
2019-04-27 21:07 ` Emanuel Berg
2019-04-26 7:47 ` tomas
2019-04-27 21:10 ` Emanuel Berg
2019-04-29 3:32 ` Van L
2019-04-04 4:18 ` Xavier Maillard
2019-04-04 3:31 ` Emanuel Berg
2019-04-17 0:39 ` Sacha Chua
2019-04-17 1:53 ` Emanuel Berg
2019-04-17 11:02 ` Van L
2019-04-17 19:07 ` Emanuel Berg
2019-04-01 13:07 ` Emanuel Berg
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86zhpizu8k.fsf_-_@zoho.eu \
--to=moasenwood@zoho.eu \
--cc=help-gnu-emacs@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.