From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Foundation meeting agenda for April 2018
Date: Mon, 09 Apr 2018 10:23:53 +0200 [thread overview]
Message-ID: <5476501.U949GqNMEO@porto> (raw)
In-Reply-To: <20180409001118.GA29309@clocktown>
Am Montag, 9. April 2018, 02:11:19 CEST schrieb zlg:
> > We request that the Gentoo Council and the Board of Trustees of the
> > Gentoo
> > Foundation affirm Gentoo's metastructure GLEP 39 as the governing
> > principle
> > of the Gentoo Linux developer community. In particular, both acknowledge
> > the split between
> >
> > - the Gentoo Council, which is responsible for the Gentoo Linux
> > developer
> >
> > community, its user base and all technical decisions,
> >
> > - and the Gentoo Foundation, whose role is to hold Gentoo's assets
> >
> > (such as trademarks and server infrastructure) and support the
> > developer
> > and user community.
[snip]
> To the Council:
>
> What makes you accountable to this community? Why should we trust or
> respect you when you have nothing on the line except a title? What
> happens next if these affirmations are made? What's your angle, your
> real motivation?
This proposal describes precisely
* how I was taught "Gentoo works" for my quizzes sometime around 2010
* how the cooperation and separation of responsibilities between council and
foundation worked for the years since then
* and what was the basis of understanding for council and trustees elections
Thus, we are asking for an affirmation of the status quo, nothing else.
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, perl, libreoffice, comrel)
next prev parent reply other threads:[~2018-04-09 8:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-08 20:27 [gentoo-project] Foundation meeting agenda for April 2018 Matthew Thode
2018-04-08 20:43 ` Matthias Maier
2018-04-08 20:48 ` Andreas K. Huettel
2018-04-09 0:11 ` zlg
2018-04-09 0:14 ` Rich Freeman
2018-04-09 1:06 ` Matthias Maier
2018-04-09 1:38 ` Alec Warner
2018-04-09 4:10 ` William Hubbs
2018-04-09 11:11 ` Luca Barbato
2018-04-09 3:29 ` zlg
2018-04-09 3:42 ` Virgil Dupras
2018-04-09 4:39 ` zlg
2018-04-09 5:47 ` Michał Górny
2018-04-09 6:28 ` Paweł Hajdan, Jr.
2018-04-09 14:12 ` William Hubbs
2018-04-09 7:17 ` Matthias Maier
2018-04-09 7:50 ` zlg
2018-04-09 12:38 ` Rich Freeman
2018-04-09 8:23 ` Andreas K. Huettel [this message]
2018-04-09 9:56 ` Matthew Thode
2018-04-09 11:36 ` Luca Barbato
2018-04-09 15:44 ` Matthew Thode
2018-04-09 12:01 ` Alexis Ballier
2018-04-09 6:12 ` Michał Górny
2018-04-09 4:25 ` Alec Warner
2018-04-09 15:53 ` Matthias Maier
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=5476501.U949GqNMEO@porto \
--to=dilfridge@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