From: joakim@verona.se
To: Yoni Rabkin <yoni@rabkins.net>
Cc: emacs-devel@gnu.org
Subject: Re: anything.el inclusion
Date: Sun, 28 Mar 2010 19:39:06 +0200 [thread overview]
Message-ID: <m3zl1sz6px.fsf@verona.se> (raw)
In-Reply-To: <87ljdc7u95.fsf@rabkins.net> (Yoni Rabkin's message of "Sun, 28 Mar 2010 10:58:14 +0300")
Yoni Rabkin <yoni@rabkins.net> writes:
> Juri Linkov <juri@jurta.org> writes:
>
>>> What needs to happen for inclusion of anything.el by itself,
>>> in your opinion?
>>
>> What do you think about the following idea for package.el?
>>
>> To every package handled by package.el add a new parameter that tracks
>> the package's "popularity". This could mean either the number of
>> downloads from the server that hosts these packages, or to add UI
>> where users would be able to vote for a package.
>>
>> Then we could sort all available packages by popularity in package.el UI,
>> so the top packages are objective candidates for inclusion in Emacs.
>
> This is the exact kind of of thinking that makes me want to avoid any
> centralized system such as package.el. Centralized systems like these
> makes people start thinking of all kinds of "benefits" the centralized
> system can bestow on users without the users ever asking for them (or
> knowing they exist).
I havent seen any such tendency with the distribution specific
repositories I have used (Fedora, Debian, Suse)
--
Joakim Verona
next prev parent reply other threads:[~2010-03-28 17:39 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 6:18 kill-ring visualization joakim
2010-03-18 14:06 ` Stefan Monnier
2010-03-18 18:39 ` Leo
2010-03-18 19:37 ` joakim
2010-03-24 9:34 ` Juri Linkov
2010-03-24 13:54 ` Stefan Monnier
2010-03-25 7:04 ` Juri Linkov
2010-03-25 9:47 ` Thierry Volpiatto
2010-03-25 10:13 ` joakim
2010-03-25 10:20 ` Thierry Volpiatto
2010-03-25 13:56 ` anything.el inclusion (was: kill-ring visualization) Ted Zlatanov
2010-03-25 17:28 ` anything.el inclusion Juri Linkov
2010-03-26 6:37 ` Thierry Volpiatto
2010-03-26 7:01 ` Juri Linkov
2010-03-26 7:22 ` Thierry Volpiatto
2010-03-26 20:19 ` Stefan Monnier
2010-03-29 18:32 ` Ted Zlatanov
2010-03-29 19:34 ` Thierry Volpiatto
2010-04-03 5:44 ` Thierry Volpiatto
2010-04-03 13:53 ` Stefan Monnier
2010-04-03 14:17 ` Thierry Volpiatto
2010-04-03 19:08 ` Stefan Monnier
2010-03-26 17:09 ` Ted Zlatanov
2010-03-27 19:38 ` Juri Linkov
2010-03-27 21:35 ` Johan Busk Eriksson
2010-03-28 7:58 ` Yoni Rabkin
2010-03-28 17:39 ` joakim [this message]
2010-03-29 18:25 ` Ted Zlatanov
2010-03-26 2:00 ` regexp completion (was: kill-ring visualization) Stefan Monnier
2010-03-25 17:29 ` kill-ring visualization Juri Linkov
2010-03-26 2:53 ` Stefan Monnier
2010-03-26 7:09 ` Juri Linkov
2010-03-26 20:17 ` Stefan Monnier
2010-03-27 19:42 ` Juri Linkov
2010-03-27 20:37 ` Stefan Monnier
2010-03-30 16:07 ` Juri Linkov
2010-03-30 20:35 ` Stefan Monnier
2010-03-31 15:04 ` Juri Linkov
2010-03-25 16:49 ` Drew Adams
2010-03-18 15:16 ` Drew Adams
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=m3zl1sz6px.fsf@verona.se \
--to=joakim@verona.se \
--cc=emacs-devel@gnu.org \
--cc=yoni@rabkins.net \
/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.