From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: council@gentoo.org
Subject: Re: [gentoo-project] Council meeting 2019-12-08 19:00 UTC - Agenda topics?
Date: Mon, 02 Dec 2019 10:10:55 +0100 [thread overview]
Message-ID: <cea26bfbb39daf70a672078f6c25b71f5d1449bb.camel@gentoo.org> (raw)
In-Reply-To: <1804325.WCBl8XsjWq@pinacolada>
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
On Wed, 2019-11-27 at 00:26 +0100, Andreas K. Huettel wrote:
> The next council meeting will be on Sunday 2019-12-08, 19:00 UTC in the
> #gentoo-council channel on Freenode. Please reply to this mail with desired
> agenda topics.
>
I'd like to pass a big question™ towards the Council since there seems
to be some disagreement on the direction Gentoo should take:
===
Should Gentoo developers be expected to be able to find a way to work
together to build a somewhat consistent distribution, or should it be
allowed for individual developers to 'run their own shops' and ignore
everybody else?
===
To explain what I mean with an extreme example: in the past we had
a developer who blocked adding systemd units to his own packages because
of his own personal agenda against systemd. This was obviously harmful
to systemd users who couldn't install use those packages normally,
and was harmful to consistent user experience across Gentoo.
In my opinion, such behavior is unacceptable but given that similar
issues regularly emerge, maybe I'm wrong.
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2019-12-02 9:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 23:26 [gentoo-project] Council meeting 2019-12-08 19:00 UTC - Agenda topics? Andreas K. Huettel
2019-11-27 6:20 ` Ulrich Mueller
2019-12-02 9:10 ` Michał Górny [this message]
2019-12-02 9:44 ` Lars Wendler
2019-12-02 10:07 ` Michał Górny
2019-12-02 14:22 ` 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=cea26bfbb39daf70a672078f6c25b71f5d1449bb.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=council@gentoo.org \
--cc=gentoo-project@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