unofficial mirror of emacs-tangents@gnu.org
 help / color / mirror / Atom feed
From: Sacha Chua <sacha@sachachua.com>
To: Jean Louis <bugs@gnu.support>
Cc: Tom Davey <tom@tomdavey.com>, Emanuel Berg <incal@dataswamp.org>,
	emacs-tangents@gnu.org
Subject: Re: 2022-06-06 Emacs news
Date: Tue, 7 Jun 2022 23:37:09 -0400	[thread overview]
Message-ID: <CAJGZZeL2PYCLfwsjf80W2dKArCc8Su=WVnJjFXdWp_qQ2gSHeQ@mail.gmail.com> (raw)
In-Reply-To: <Yp+1+lZswtmQR2Em@protected.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1873 bytes --]

Hello, all!

On Tue., Jun. 7, 2022, 17:28 Jean Louis, <bugs@gnu.support> wrote:

My suggestion is that you setup a database with title, description and
> URL, and then let people add to it on a website, as the database will
> make sure that links are unique. Then you will know what is new and
> what not.
>

Reddit and Lemmy are essentially those, with the benefits of also
supporting discussion, voting, and moderation.

One of the things on my "when I have more focused time someday" list (or,
realistically, see if anyone else wants to pick it up) is to organize
selected links into something more like maps and trails. It makes sense to
keep those on a wiki so people can update it. It's not just about recency
or popularity, or even the rough categorization I do in Emacs News. It's
more like saying, okay, this week there have been a couple of interesting
links about Emacs Lisp testing. They could be added to something that can
point people to those, Cask, ERT, Buttercup, etc. in a way that makes it
easier for people to figure out how things relate to each other or what to
try when.

Searching through the index.org in Emacs News just lets you work with
categories, URLs, and titles. I think there's an opportunity to make more
sense of things, but I don't think I'll have focus time for at least
another year. :) No worries if it sounds too vague - someone (maybe me)
will probably get to it someday!

Also, there's some space between the weekly Emacs News and the yearly Emacs
News Highlights I put together for EmacsConf. If someone wants to do a
monthly highlights thing (kind of like how This Month in Org is awesome!),
that might be neat too.

There's always helping out by writing up something you've learned or
experimented with recently. All skill levels welcome!

All sorts of non-code ways to help the community get even more connected! :)

Sacha

>

[-- Attachment #2: Type: text/html, Size: 2722 bytes --]

  parent reply	other threads:[~2022-06-08  3:37 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07  4:49 2022-06-06 Emacs news Sacha Chua
2022-06-07  4:55 ` Emanuel Berg
2022-06-07 11:13   ` Jean Louis
2022-06-07 13:20     ` Emanuel Berg
2022-06-07 13:47       ` How to send links for Emacs News " Sacha Chua
2022-06-07 14:58         ` Emanuel Berg
2022-06-07 15:29       ` Jean Louis
2022-06-07 15:48         ` Tom Davey
2022-06-07 16:04           ` Sunil Patel
2022-06-07 16:21           ` Emanuel Berg
2022-06-07 16:25           ` Sacha Chua
2022-06-07 16:36             ` Emanuel Berg
2022-06-07 20:32             ` Jean Louis
2022-06-07 23:55               ` Emanuel Berg
2022-06-08  4:40                 ` Jean Louis
2022-06-08  5:30                   ` Emanuel Berg
2022-06-08  3:37               ` Sacha Chua [this message]
2022-06-08  4:00                 ` Emanuel Berg
2022-06-08 16:03           ` Marcin Borkowski
2022-06-08 19:19             ` Jean Louis
2022-06-09  0:57               ` Emanuel Berg
2022-06-09  5:06               ` Marcin Borkowski
2022-06-09  5:22                 ` Emanuel Berg
2022-06-09  7:21                 ` Jean Louis
2022-06-09  8:01                   ` Emanuel Berg
2022-06-09  0:55             ` Emanuel Berg
2022-06-07 16:44         ` 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='CAJGZZeL2PYCLfwsjf80W2dKArCc8Su=WVnJjFXdWp_qQ2gSHeQ@mail.gmail.com' \
    --to=sacha@sachachua.com \
    --cc=bugs@gnu.support \
    --cc=emacs-tangents@gnu.org \
    --cc=incal@dataswamp.org \
    --cc=tom@tomdavey.com \
    /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).