unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Stefan Kangas <stefan@marxist.se>
Cc: Philip Kaludercic <philipk@posteo.net>,  emacs-devel@gnu.org
Subject: Re: [nongnu] main 74116339a8 2/3: * elpa-packages (anzu): New package
Date: Sun, 16 Jan 2022 18:47:34 -0500	[thread overview]
Message-ID: <jwva6fvp7vh.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CADwFkm=e5pVqLrp8VUfGPo2mo9tB+2r3XDRdKNHNS+mM15HV1g@mail.gmail.com> (Stefan Kangas's message of "Sun, 16 Jan 2022 14:32:47 -0800")

>>> I am not against any efforts in this direction, of course, and I would
>>> welcome any kind of initiative to do "community outreach" here.
>> What do you mean by this?
> I think it would be beneficial to think of ways to encourage people to
> consider sending patches to Emacs or packages instead of writing up yet
> another package.  This could be in the form of posts on Reddit, IRC,
> blogs, etc.

I think in many cases it's illusory to expect this because it's easier
for the users to write their own package custom-tailored to their
specific case (oftentimes without realizing to what extent it's custom
tailored) than to try and understand the generic code which has to take
into account many more cases that they've never even dreamed of.

But we should at least aim to make it so those users find it natural to
send us a bug report showing describing the problem they encountered and
the way they fixed it in their package.  And also make sure that we then
followup on it, to try and integrate a fix or the features, encouraging
him to take part in it, without necessarily forcing him to do the work.

> Personally, I would just do it.  The new defaults are arguably just
> better in those cases; no one will benefit from not having NonGNU ELPA
> or trying to connect to an almost dead IRC network.

Actually for `package-archives` I was thinking of doing it in
`gnu-elpa-keyring-update`.


        Stefan




  parent reply	other threads:[~2022-01-16 23:47 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <164145738158.2838.5769558384331859964@vcs2.savannah.gnu.org>
     [not found] ` <20220106082302.0A19CC0DA1E@vcs2.savannah.gnu.org>
2022-01-06 10:02   ` [nongnu] main 74116339a8 2/3: * elpa-packages (anzu): New package Philip Kaludercic
2022-01-06 12:00     ` Stefan Kangas
2022-01-06 13:35       ` Philip Kaludercic
2022-01-06 14:30         ` Packages quality (was: [nongnu] main 74116339a8 2/3: * elpa-packages (anzu): New package) Stefan Monnier
2022-01-06 15:03           ` Bozhidar Batsov
2022-01-06 17:07             ` Packages quality Stefan Monnier
2022-01-06 19:50               ` Tim Cross
2022-01-07  7:54               ` Stefan Kangas
2022-01-07 11:45                 ` John Yates
2022-01-07 12:16                   ` Stefan Kangas
2022-01-07 15:52                     ` John Yates
2022-01-07  7:55             ` Packages quality (was: [nongnu] main 74116339a8 2/3: * elpa-packages (anzu): New package) Stefan Kangas
2022-01-07 10:22               ` Bozhidar Batsov
2022-01-07 10:54                 ` Stefan Kangas
2022-01-06 17:28           ` Packages quality Philip Kaludercic
2022-01-06 19:55         ` [nongnu] main 74116339a8 2/3: * elpa-packages (anzu): New package Juri Linkov
2022-01-07  7:55         ` Stefan Kangas
2022-01-16 17:49           ` Philip Kaludercic
2022-01-16 22:19             ` Stefan Monnier
2022-01-19  8:57               ` Philip Kaludercic
2022-01-19 15:19                 ` Stefan Monnier
2022-01-16 22:32             ` Stefan Kangas
2022-01-16 23:16               ` Ergus
2022-01-19  9:05                 ` Philip Kaludercic
2022-01-16 23:47               ` Stefan Monnier [this message]
2022-01-19  9:03               ` Philip Kaludercic
2022-01-17  7:37             ` Jean Louis
2022-01-19  9:10               ` Philip Kaludercic
2022-01-07 10:02         ` Stefan Kangas
2022-01-10  1:18           ` Stefan Monnier
2022-01-07  9:38     ` Augusto Stoffel

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=jwva6fvp7vh.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.net \
    --cc=stefan@marxist.se \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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