From: "Canek Peláez Valdés" <caneko@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Removing pulseaudio
Date: Sun, 28 Apr 2013 12:56:23 -0500 [thread overview]
Message-ID: <CADPrc83mT79mPRdnPYFK9pix_mm9cg3YkKRTTnvpBqPvp57y4g@mail.gmail.com> (raw)
In-Reply-To: <517D5891.6070901@gmail.com>
On Sun, Apr 28, 2013 at 12:12 PM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> On 28/04/2013 18:11, Canek Peláez Valdés wrote:
>>> What we complain about here is basic low-level software changes that
>>> > affect much more than just their own little universe, and will do it ON
>>> > ALL LINUX MACHINES NOW AND IN THE FUTURE.
>> The source is out there NOW AND IN THE FUTURE. If there is enough
>> developers interested in maintaining something, it will be maintained;
>> but you cannot force no developer to maintain nothing.
>
> You keep saying this, over and over in many places for many reasons.
>
> But it just is not true.
>
> It's easy to get a dev to support something - you just ask them.
>
> Have you ever asked a dev to support something you needed?
Yes of course; you can ask a developer for anything: you can ask him,
for example, to throw himself over a cliff. Believe me: he will
probably not do it.
I said: you cannot *FORCE* a developer to maintain nothing. You want
to *FORCE* them to support PA-less systems (in the case of GNOME,
perhaps, in the future) and /usr-separated systems without initramfs
(in udev case), only because *you* think is the right thing to do, or
because it was previously "supported" (in the /usr-separated it was
actually a problem waiting to happen).
The developers in those projects made their choice: make yours. Stick
with those projects and accept that the developers word is law; or
contribute so that your word has weight; or fork the project; or
switch projects; or whatever. Complaining over choices already made by
the people in charge is not very productive.
Of course you can express your opinion. But without any code behind
it, the most probably outcome is that it will be ignored.
Even more in a place like this list: some Gentoo developers read
gentoo-user, and from those even less are upstream in certain
projects. But the majority of the people writing the code (the kernel,
systemd-udev, PulseAudio, GStreamer, GNOME,
whatever-application-you-use) most of the time don't read this list.
Complaining here about PulseAudio being a hard dependency on GNOME is
basically yelling into an echo chamber: you will most of the time get
only responses from people with the same opinion as yours, and they
all will get into a long rant about the evils of who-knows-what new
fangled project that goes against "old Unix principles" (whatever that
is). And. Nothing. Will. Change... because the people coding the code
are the ones making the decisions. And they do not read (in general)
this particular mailing list.
The developers in several projects are making their decisions;
sometimes they listen to users, sometimes they don't. If we don't step
in and contribute code to said projects, arguing here about what
constitutes a "good" or a "bad" developer is pretty pointless.
To finish (this mail and my participation in this thread), you know
what developer is famous for not listening to users? Linus Torvalds.
Google what has happened whenever someone has tried to set up a
petition campaign to get something into the kernel.
And he's certainly one of the best project leaders we have.
--
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México
next prev parent reply other threads:[~2013-04-28 17:56 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 19:32 [gentoo-user] Removing pulseaudio Alan Mackenzie
2013-04-18 19:48 ` Michael Mol
2013-04-18 20:02 ` Volker Armin Hemmann
2013-04-18 20:13 ` Michael Mol
2013-04-18 20:43 ` Volker Armin Hemmann
2013-04-18 21:10 ` Michael Mol
2013-04-18 21:46 ` Volker Armin Hemmann
2013-04-18 22:02 ` Michael Mol
2013-04-19 20:34 ` Volker Armin Hemmann
2013-04-18 22:57 ` [Bulk] " Kevin Chadwick
2013-04-18 21:26 ` [gentoo-user] " Hartmut Figge
2013-04-18 21:29 ` Michael Mol
2013-04-18 20:02 ` [gentoo-user] " Stroller
2013-04-18 20:31 ` Alan Mackenzie
2013-04-18 20:47 ` Volker Armin Hemmann
2013-04-18 21:28 ` [Bulk] " Kevin Chadwick
2013-04-18 21:14 ` Michael Mol
2013-04-21 19:46 ` [gentoo-user] Re: [Bulk] " Nuno J. Silva (aka njsg)
2013-04-21 21:20 ` Kevin Chadwick
2013-04-22 3:13 ` Nuno J. Silva (aka njsg)
2013-04-25 20:15 ` [Bulk] " Kevin Chadwick
2013-04-19 7:28 ` [gentoo-user] " Alan McKinnon
2013-04-19 8:49 ` Kevin Chadwick
2013-04-19 9:53 ` [gentoo-user] Re[2]: " the guard
2013-04-23 20:59 ` William Hubbs
2013-04-23 22:12 ` Michael Hampicke
2013-04-24 2:46 ` Walter Dnes
2013-04-24 10:21 ` Michael Hampicke
2013-04-24 20:55 ` William Hubbs
2013-05-13 13:32 ` Alex Schuster
2013-04-25 20:10 ` [Bulk] " Kevin Chadwick
2013-04-25 19:34 ` Michael Hampicke
2013-04-24 10:46 ` Alan Mackenzie
2013-04-24 21:19 ` Alecks Gates
2013-04-25 15:37 ` Mark David Dumlao
2013-04-20 9:34 ` Walter Dnes
2013-04-20 14:48 ` Michael Mol
2013-04-26 12:13 ` Mark David Dumlao
2013-04-20 15:41 ` Alan McKinnon
2013-04-20 19:34 ` Yuri K. Shatroff
2013-04-21 1:15 ` Canek Peláez Valdés
2013-04-21 10:28 ` Neil Bothwick
2013-04-21 11:52 ` Mick
2013-04-21 14:24 ` Dale
2013-04-21 16:00 ` Neil Bothwick
2013-04-21 18:40 ` Dale
2013-04-21 21:09 ` Alan Mackenzie
2013-04-22 0:36 ` [gentoo-user] " walt
2013-04-20 21:05 ` [gentoo-user] " Neil Bothwick
2013-04-25 15:48 ` Mark David Dumlao
2013-04-25 17:31 ` Yuri K. Shatroff
2013-04-25 20:26 ` [gentoo-user] " Steven J. Long
2013-04-26 3:10 ` [gentoo-user] " Mark David Dumlao
2013-04-25 19:17 ` Walter Dnes
2013-04-26 8:34 ` Mark David Dumlao
2013-04-26 12:05 ` Yuri K. Shatroff
2013-04-26 12:56 ` Yohan Pereira
2013-04-26 13:26 ` Yuri K. Shatroff
2013-04-26 15:41 ` Mark David Dumlao
2013-04-26 16:29 ` Alan Mackenzie
2013-04-26 17:02 ` Canek Peláez Valdés
2013-04-26 18:38 ` Alan Mackenzie
2013-04-26 19:09 ` Canek Peláez Valdés
2013-04-26 20:34 ` Alan Mackenzie
2013-04-26 22:14 ` Canek Peláez Valdés
2013-04-27 0:57 ` Mark David Dumlao
2013-04-26 20:21 ` Kevin Chadwick
2013-04-26 20:38 ` Kevin Chadwick
2013-04-26 22:28 ` Walter Dnes
2013-04-27 2:11 ` Canek Peláez Valdés
2013-04-27 6:37 ` Mark David Dumlao
2013-04-26 18:03 ` Yuri K. Shatroff
2013-04-26 18:25 ` Canek Peláez Valdés
2013-04-26 19:51 ` Yuri K. Shatroff
2013-04-27 1:10 ` Mark David Dumlao
2013-04-27 15:55 ` Randy Barlow
2013-04-27 20:13 ` Dale
2013-04-28 0:24 ` Randy Barlow
2013-04-28 9:59 ` Alan McKinnon
2013-04-28 16:02 ` Randy Barlow
2013-04-28 17:00 ` Alan McKinnon
2013-04-28 16:11 ` Canek Peláez Valdés
2013-04-28 17:12 ` Alan McKinnon
2013-04-28 17:33 ` Mick
2013-04-28 17:56 ` Canek Peláez Valdés [this message]
2013-04-26 21:54 ` Walter Dnes
2013-04-25 19:55 ` Alan McKinnon
2013-04-26 8:50 ` Mark David Dumlao
2013-04-26 13:59 ` Alan McKinnon
2013-04-26 21:37 ` [gentoo-user] " Steven J. Long
2013-04-26 22:37 ` [gentoo-user] " Walter Dnes
2013-04-19 13:43 ` Canek Peláez Valdés
2013-04-19 15:28 ` [gentoo-user] " James
2013-04-19 16:16 ` Karl Lindén
2013-04-19 16:20 ` Kevin Chadwick
2013-04-19 16:44 ` James
2013-04-19 16:55 ` Kevin Chadwick
2013-04-19 20:36 ` [gentoo-user] " Stefan G. Weichinger
2013-04-19 21:06 ` Mark David Dumlao
2013-04-19 21:19 ` Stefan G. Weichinger
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=CADPrc83mT79mPRdnPYFK9pix_mm9cg3YkKRTTnvpBqPvp57y4g@mail.gmail.com \
--to=caneko@gmail.com \
--cc=gentoo-user@lists.gentoo.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