From: Dmitry Alexandrov <dag@gnui.org>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Starting a GNU Guile awesome list
Date: Tue, 14 Jul 2020 12:00:50 +0300 [thread overview]
Message-ID: <imeqqxml.dag@gnui.org> (raw)
In-Reply-To: <b9af8fee-cc10-9673-c230-10c0d1ffdb48@posteo.de> (Zelphir Kaltstahl's message of "Mon, 13 Jul 2020 23:19:50 +0200")
[-- Attachment #1: Type: text/plain, Size: 2878 bytes --]
Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> wrote:
> I ‹…› started creating an awesome list
> https://notabug.org/ZelphirKaltstahl/awesome-guile
+1!
However, even if you are not going to apply for inclusion¹ in meta-list <https://awesome.re> and therefore are free from complying with all rules that might come to the mind of a macboy in state of administrative ecstasy²; calling your list ‘an awesome list’ implies a certain format nonetheless.
And that format actually answers two of the there of your questions.
-
¹ In any case, I am not sure, whether they accept lists with the primary repository outside of github.com at all.
² E. g., recently he had broken local clones and invalidated all the pull-request backlog by renaming ‘master’ branch to ‘main’, and now require all the lists to follow his example.
> * Do you think each item should have a short description or not?
Thatʼs the key feature of ‘awesome lists’, number one in the ‘manifesto’ [1]:
| Comment on why something is awesome
|
| Apart from suggesting a particular item on your list, you should also inform your readers why it's on the list and how they will benefit from it.
[1] https://github.com/sindresorhus/awesome/blob/main/awesome.md
> * Do you think the rendered readme.md should be handwritten instead of exported from org-mode?
Again, ‘awesome list’ format implies [2] Markdown as a source format. Nobody says, though, that a source is something handtyped.
[2] https://github.com/sindresorhus/awesome/blob/main/pull_request_template.md
> (Perhaps I should not ask this question … the amount of markdown typing … my fingers hurt.)
??? The only thing where org-mode saves typing over markdown-mode is ToC generation. But there are lots ToC helpers for Markdown! (describe-package 'markdown-toc), for instance.
In the case you will stick with Org, there at least should be a runnable build recipe (i. e. a Makefile).
> * Do you think license information should be written next to each item in the list?
First at foremost, the list _itself_ has to be licensed as a free documentation. FWIW, most of ‘awesome lists’ are under CC0.
> * Do you think license information should be written next to each item in the list?
Anyway, imho, yes, it should. This is an information with the highest usefulness/length ratio. Perhaps, only maintained-or-abandoned bit could contend for it.
Actually, you might eventually find out useful to list something, because it has not a technical, but exactly a licensing advantage to another item.
For instance, the above-mentioned GNU G-Golf have a advantage over Guile GI as it does not follow a bad licensing practice of distributing a glue between a library under license A and a language under license B under terms of the third license C.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-07-14 9:00 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 21:19 Starting a GNU Guile awesome list Zelphir Kaltstahl
2020-07-13 21:56 ` Jack Hill
2020-07-13 22:56 ` Aleix Conchillo Flaqué
2020-07-14 23:26 ` Zelphir Kaltstahl
2020-07-14 9:00 ` Dmitry Alexandrov [this message]
2020-07-14 21:23 ` Zelphir Kaltstahl
2020-07-15 6:32 ` Dr. Arne Babenhauserheide
2020-07-16 8:47 ` Dmitry Alexandrov
2020-07-16 19:01 ` Dr. Arne Babenhauserheide
2020-10-10 12:31 ` Zelphir Kaltstahl
2020-10-10 13:14 ` Matt Wette
2020-10-11 0:57 ` Zelphir Kaltstahl
2020-10-11 19:51 ` Ricardo Wurmus
2020-10-11 23:39 ` Zelphir Kaltstahl
2020-10-12 10:33 ` Ricardo Wurmus
2020-11-08 17:09 ` Zelphir Kaltstahl
2020-11-08 18:55 ` Paul Smith
2020-12-05 18:15 ` Zelphir Kaltstahl
2020-07-15 6:36 ` Dr. Arne Babenhauserheide
2020-07-15 21:14 ` Zelphir Kaltstahl
2020-07-15 22:40 ` Dr. Arne Babenhauserheide
2020-07-16 9:18 ` A licence for an ‘awesome list’ (was: Starting a GNU Guile awesome list) Dmitry Alexandrov
2020-07-16 18:56 ` Dr. Arne Babenhauserheide
2020-07-16 18:58 ` Dr. Arne Babenhauserheide
2020-07-16 20:47 ` Zelphir Kaltstahl
2020-07-16 22:55 ` Vladimir Zhbanov
2020-07-16 23:05 ` Vladimir Zhbanov
2020-07-17 0:20 ` John Cowan
2020-07-17 6:43 ` Dr. Arne Babenhauserheide
2020-07-14 14:14 ` Starting a GNU Guile awesome list Dr. Arne Babenhauserheide
2020-07-15 21:24 ` Zelphir Kaltstahl
2020-07-15 22:29 ` Dr. Arne Babenhauserheide
2020-07-14 16:37 ` Taylan Kammer
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=imeqqxml.dag@gnui.org \
--to=dag@gnui.org \
--cc=guile-user@gnu.org \
--cc=zelphirkaltstahl@posteo.de \
/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).