public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-project@lists.gentoo.org,zlg <zlg@gentoo.org>
Subject: Re: [gentoo-project] Foundation meeting agenda for April 2018
Date: Mon, 09 Apr 2018 07:47:17 +0200	[thread overview]
Message-ID: <176F090A-8C4B-4DAB-BF80-3E18287D34DE@gentoo.org> (raw)
In-Reply-To: <20180409043922.GC29309@clocktown>

Dnia 9 kwietnia 2018 06:39:22 CEST, zlg <zlg@gentoo.org> napisał(a):
>On Sun, Apr 08, 2018 at 11:42:01PM -0400, Virgil Dupras wrote:
>> On Sun, 8 Apr 2018 20:29:27 -0700
>> zlg <zlg@gentoo.org> wrote:
>> 
>> > Why should a group -- who holds no legal, social, or practical
>> > responsibility -- be trusted to lead the efforts of an
>organization?
>> 
>> Since Gentoo's CoC is strongly based on Debian, maybe we could look
>at Debian's constitution for clues on this and ask ourselves why it
>says in section 9 [1]:
>> 
>> > An organisation holding assets for Debian has no authority
>regarding
>> > Debian's technical or nontechnical decisions, except that no
>decision
>> > by Debian with respect to any property held by the organisation
>shall
>> > require it to act outside its legal authority.
>> 
>> Maybe that this type of separation of concerns worked well for them?
>Maybe it can work well for Gentoo?
>> 
>> Regards,
>> Virgil Dupras
>> 
>> [1] https://www.debian.org/devel/constitution#item-9
>> 
>
>Separating concerns may work, but not without a real, legally binding
>contract that both parties consent to and abide by. Otherwise, the
>Foundation takes on all the legal and financial risk and gets nothing
>for it.

And that is what it's called not-for-profit. They volunteer to help others and want nothing in return.

>
>An affirmation from the two parties is not a binding contract. I would
>support one if it was equitable and enforceable, i.e. not GLEP 39. If
>the relationship is reduced to business, then the Council should offer
>something in return.


-- 
Best regards,
Michał Górny (by phone)


  reply	other threads:[~2018-04-09  5:47 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 [this message]
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
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=176F090A-8C4B-4DAB-BF80-3E18287D34DE@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    --cc=zlg@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