From: Richard Yao <ryao@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Thank you
Date: Sun, 09 Feb 2014 13:23:10 -0500 [thread overview]
Message-ID: <52F7C78E.3080903@gentoo.org> (raw)
In-Reply-To: <CADPrc83g_24F=Ww2D+upCTQsQb87mjnbK93D1usdyKnQ9eChYg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2430 bytes --]
Gentoo is very open to providing users with the option of using
new/different as long as they don't break existing things. I cannot say
that many of us like design decisions being taken in GNOME/systemd, but
as the long as the few interested in it do not interfere with existing
things, they are free to package it as they see fit.
On 02/06/2014 01:30 AM, Canek Peláez Valdés wrote:
> Hi. TL;DR, this is basically just a THANK YOU to the Gentoo devs, so
> you can go on your daily business if you don't want to read the rest
> of it. No biggie.
>
> I just want to say THANK YOU to all of our Gentoo developers. I've
> been using Gentoo since ca. 2002 (damn, that's more than a decade),
> and I've seen a lot of flamewars and bikeshedding on the -dev mailing
> list.
>
> However, you guys get the job done, and although there are some things
> that I would like to have sooner (or would have liked to have
> earlier), in the end the people working keep pushing the necessary
> changes so the distribution keeps going, and (if so desired) using new
> and interesting technologies.
>
> More importantly, the developers and the bureaucratic structures they
> have created don't get (too much) in the way of individual or small
> groups of developers pushing for progress. In general at least; there
> will be always someone resisting change, but in general Gentoo keeps
> advancing, and the council and the other bureaucratic structures don't
> punish people for just wanting to have more new and cool features in
> the distribution.
>
> I've never said Thank You to all our developers in all these years
> using Gentoo, but after seeing the discussion the Debian CTTE is
> having related to the default init they should use[1][2][3] (including
> bureaucratic maneuvers, dilatory tactics, legalese interpretation of
> their rulings, etc.), I think the time is long overdue for me to do
> it.
>
> Thank you for all the work you guys do and have done.
> Thank you for not penalize progress.
> Thank you for not being so rigid.
> Thank you for keeping the distribution moving and evolving.
> And finally, just thank you.
>
> From a proud Gentoo+systemd+GNOME 3 user, thank you.
>
> Regards.
>
> [1] https://lists.debian.org/debian-ctte/2014/01/threads.html
> [2] https://lists.debian.org/debian-ctte/2014/02/threads.html
> [3] http://lwn.net/Articles/584227/#Comments
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2014-02-09 18:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 6:30 [gentoo-dev] Thank you Canek Peláez Valdés
2014-02-06 7:22 ` Tom Wijsman
2014-02-07 23:00 ` Denis Dupeyron
2014-02-09 18:08 ` Rick "Zero_Chaos" Farina
2014-02-09 18:23 ` Richard Yao [this message]
2014-02-09 18:46 ` Rich Freeman
2014-02-10 8:32 ` Ultrabug
2014-02-14 7:43 ` Sergey Popov
2014-02-19 23:43 ` [gentoo-dev] " Duncan
-- strict thread matches above, loose matches on Subject: below --
2002-04-10 8:10 [gentoo-dev] " Darrell Wright
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=52F7C78E.3080903@gentoo.org \
--to=ryao@gentoo.org \
--cc=gentoo-dev@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