From: Ben de Groot <yngwin@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Cc: Tim Harder <radhermit@gentoo.org>, gentoo-dev-announce@lists.gentoo.org
Subject: Re: [gentoo-project] Council meeting 2015-04-14: call for agenda items
Date: Sat, 11 Apr 2015 15:13:50 +0800 [thread overview]
Message-ID: <CAB9SyzRn+cSSJxO8O+UMPgaHQ5BCqgLVduNFZfOpK2aY4Ev6Rw@mail.gmail.com> (raw)
In-Reply-To: <20150406112805.32b1eefb@pomiot.lan>
On 6 April 2015 at 17:28, Michał Górny <mgorny@gentoo.org> wrote:
> Dnia 2015-04-02, o godz. 10:14:28
> Tim Harder <radhermit@gentoo.org> napisał(a):
>
>> The next council meeting will be on April 14th, 19:00 UTC in
>> #gentoo-council on Freenode.
>>
>> Please respond to this message on the gentoo-project list with any
>> agenda items you want to propose or discuss.
>
> I would like to ask the Council to confirm or reject the switch of
> libav/ffmpeg default to ffmpeg. I don't want to take a stand there but
> I'm concerned that our users will end up suffering a ping-pong of
> developers fighting and changing the defaults from time to time.
>
> [1]:https://archives.gentoo.org/gentoo-dev/message/50c181372e098719b2573e7b16c74482
My reasons for the switch are summarized here:
https://archives.gentoo.org/gentoo-dev/message/215e894205c6ca4a6e4e76291872ce95
If anything more is wanted, please let me know, and I'd be happy to expand.
--
Cheers,
Ben | yngwin
Gentoo developer
next prev parent reply other threads:[~2015-04-11 7:13 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 14:14 [gentoo-project] Council meeting 2015-04-14: call for agenda items Tim Harder
2015-04-02 16:45 ` Ulrich Mueller
2015-04-03 19:33 ` [gentoo-project] " Michael Palimaka
2015-04-03 20:01 ` Rich Freeman
2015-04-03 20:13 ` Andreas K. Huettel
2015-04-04 14:31 ` Michael Palimaka
2015-04-04 15:13 ` Rich Freeman
2015-04-04 15:44 ` Michał Górny
2015-04-04 15:48 ` Michał Górny
2015-04-04 22:02 ` William Hubbs
2015-04-05 12:32 ` Pacho Ramos
2015-04-05 12:44 ` Ben de Groot
2015-04-05 19:50 ` William Hubbs
2015-04-05 20:20 ` James Le Cuirot
2015-04-05 21:27 ` Andrew Savchenko
2015-04-05 22:54 ` Rich Freeman
2015-04-05 23:05 ` Patrick Lauer
2015-04-06 0:47 ` Rich Freeman
2015-04-06 7:55 ` Michał Górny
2015-04-06 20:52 ` Pacho Ramos
2015-04-06 22:22 ` Matt Turner
2015-04-07 15:38 ` Michael Palimaka
2015-04-07 23:25 ` Anthony G. Basile
2015-04-07 23:29 ` Rich Freeman
2015-04-07 23:50 ` Anthony G. Basile
2015-04-08 11:51 ` William Hubbs
2015-04-08 13:33 ` Rich Freeman
2015-04-08 17:39 ` William Hubbs
2015-04-08 18:15 ` Rich Freeman
2015-04-08 22:41 ` William Hubbs
2015-04-09 0:01 ` Rich Freeman
2015-04-08 11:58 ` Michael Palimaka
2015-04-07 23:38 ` Rich Freeman
2015-04-07 23:42 ` Francesco Riosa
2015-04-08 0:01 ` Matt Turner
2015-04-08 0:35 ` Rich Freeman
2015-04-05 23:38 ` Andrew Savchenko
2015-04-06 7:59 ` Michał Górny
2015-04-06 10:29 ` Rich Freeman
2015-04-06 11:09 ` Michał Górny
2015-04-06 21:37 ` Andrew Savchenko
2015-04-06 22:05 ` Michał Górny
2015-04-06 22:25 ` Andrew Savchenko
2015-04-06 22:28 ` William Hubbs
2015-04-07 0:02 ` Rich Freeman
2015-04-06 9:28 ` [gentoo-project] " Michał Górny
2015-04-11 7:13 ` Ben de Groot [this message]
2015-04-11 9:04 ` Ulrich Mueller
2015-04-11 11:58 ` Rich Freeman
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=CAB9SyzRn+cSSJxO8O+UMPgaHQ5BCqgLVduNFZfOpK2aY4Ev6Rw@mail.gmail.com \
--to=yngwin@gentoo.org \
--cc=gentoo-dev-announce@lists.gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
--cc=radhermit@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