unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Amin Bandali <bandali@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: todo-did.el complete rewrite
Date: Tue, 26 Mar 2019 21:42:48 -0400	[thread overview]
Message-ID: <871s2tytwn.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <865zs7bkqx.fsf@zoho.eu>

Hi,

> Ain't it cool stuff? :) Please comment!

I think it’s neat, kudos :)

> 
> 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
> :( Very disappointing is my honest sensation.
>

Sorry to hear you’re feeling disappointed.  I’ve personally saved links
to several of your scripts posted here over the course of time, and I
plan to have a closer look at them in the near future.

I guess there could be multiple reasons for lack of comments, namely

- Considering the “name” of this list (help-gnu-emacs), I wonder if most
  users think of it as a mostly ‘help’-oriented list rather than a more
  general-purpose list as the list description perhaps hints at: “Users
  list for the GNU Emacs text editor”.

- People are likely quite busy, including myself, and may not currently
  have enough time on their hands to quickly and thoroughly read new
  posts to the list and reply.

- License is a valid concern as raised by others in the thread.  In the
  spirit of GNU Emacs, I’d recommend the GPLv3+, but you can of course
  choose other free software licenses as well.

  To license your file(s) under GPLv3+, you

  1. add a license header to each of your files (example [0]), and
  2. add a file named COPYING or LICENSE with the full text of the
     license (see [1] below) to the root directory of your project.

[0]: https://git.sr.ht/~bandali/dotfiles/tree/891c482a8f41de3002a361efce155ab0b0704a79/init.org#L108-121
[1]: https://www.gnu.org/licenses/gpl-3.0.txt

Lastly, as to where you could host your elisp files, as someone else
mentioned, sdf.org is a good choice, which provides free (gratis) shell
accounts with a limited storage 20 MB which can be upgraded to 150 MB
for a one-time $36 fee.  See [2,3] for more info.

[2]: https://sdf.org/?faq?MEMBERS?01
[3]: https://sdf.org/?faq?WEB?01

A better option for hosting source code may be using a source revision
control system.  Git is a popular choice these days.  There are a number
of freedom-respecting software forges for hosting your git repositories,
such as GNU’s own Savannah [4], sourcehut [5], and NotABug [6].  If you
decide to use git, Magit [7] is a wonderful piece of software for doing
everything git-related from inside Emacs.

[4]: https://savannah.gnu.org
[5]: https://sourcehut.org
[6]: https://notabug.org
[7]: https://magit.vc

Cheers,

-- 
Amin Bandali
https://aminb.org



  parent reply	other threads:[~2019-03-27  1:42 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   ` license and where to safely store all code (was: Re: todo-did.el complete rewrite) Emanuel Berg
2019-03-25 18:50     ` [OFF TOPIC] " 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 [this message]
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

  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=871s2tytwn.fsf@fencepost.gnu.org \
    --to=bandali@gnu.org \
    --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.
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).