From: Alec Warner <antarus@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Subject: Re: [gentoo-project] Formally have Council oversee the Foundation 2.0
Date: Mon, 16 Jan 2017 10:02:52 -0800 [thread overview]
Message-ID: <CAAr7Pr-1WB52+o14Ks8yjp8xJ6+tN0QkNvwzY1OgxR68R=537w@mail.gmail.com> (raw)
In-Reply-To: <CAGfcS_n+sKjoMEqckXv5jAv1dnwAR_KJChUoLqyQ7dsUuPCAQA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 946 bytes --]
On Mon, Jan 16, 2017 at 10:01 AM, Rich Freeman <rich0@gentoo.org> wrote:
> On Mon, Jan 16, 2017 at 12:50 PM, Alec Warner <antarus@gentoo.org> wrote:
> >
> > I agree with William here.
> >
> > The SPI does not indemnify its associated projects or members.
>
> Well, on that I agree with William as well. I never claimed otherwise.
>
> >
> > Its not clear to me how trademark enforcement works, for example. Its
> > something I am following up on as part of my SPI review (and FAQ) for the
> > Gentoo Board (and its members, all the stuff will be public.)
> >
>
> Are you doing an SPI review? Based on the fact that none of the
> Trustees seemed interested in doing one I was actually going to reach
> out to them myself, but I'd certainly prefer that it come from the
> Trustees.
I also wanted a unified front (a bunch of people have been talking about
it.) I'll follow up on -nfp regarding who is doing what for SPI.
-A
>
> --
> Rich
>
>
[-- Attachment #2: Type: text/html, Size: 1657 bytes --]
next prev parent reply other threads:[~2017-01-16 18:02 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-14 21:43 [gentoo-project] Formally have Council oversee the Foundation 2.0 Andreas K. Huettel
2017-01-14 23:03 ` Matthew Thode
2017-01-14 23:08 ` Kristian Fiskerstrand
2017-01-14 23:19 ` Matthew Thode
2017-01-14 23:22 ` Kristian Fiskerstrand
2017-01-14 23:25 ` Matthew Thode
2017-01-15 20:26 ` William L. Thomson Jr.
2017-01-15 1:16 ` Rich Freeman
2017-01-15 20:28 ` William L. Thomson Jr.
2017-01-15 21:00 ` Rich Freeman
2017-01-15 22:23 ` Raymond Jennings
2017-01-16 1:01 ` Rich Freeman
2017-01-16 14:56 ` William L. Thomson Jr.
2017-01-15 20:31 ` William L. Thomson Jr.
2017-01-15 20:59 ` Rich Freeman
2017-01-16 14:52 ` William L. Thomson Jr.
2017-01-16 15:06 ` Rich Freeman
2017-01-16 16:31 ` William L. Thomson Jr.
2017-01-16 16:56 ` Rich Freeman
2017-01-16 17:35 ` William L. Thomson Jr.
2017-01-16 17:59 ` Rich Freeman
2017-01-16 18:08 ` William L. Thomson Jr.
2017-01-16 18:23 ` Rich Freeman
2017-01-16 19:10 ` William L. Thomson Jr.
2017-01-16 18:13 ` Dale
2017-01-16 18:19 ` Rich Freeman
2017-01-16 18:25 ` Alec Warner
2017-01-16 18:46 ` Dale
2017-01-16 18:58 ` Rich Freeman
2017-01-16 19:13 ` Dale
2017-01-16 18:46 ` Rich Freeman
2017-01-16 18:52 ` Alec Warner
2017-01-16 19:08 ` Rich Freeman
2017-01-16 19:20 ` Dale
2017-01-16 19:34 ` William L. Thomson Jr.
2017-01-16 19:54 ` Dale
2017-01-16 20:11 ` Rich Freeman
2017-01-16 20:31 ` Dale
2017-01-16 20:40 ` Rich Freeman
2017-01-16 20:47 ` William L. Thomson Jr.
2017-01-16 20:57 ` Dale
2017-01-16 20:27 ` William L. Thomson Jr.
2017-01-16 20:38 ` Dale
2017-01-16 20:51 ` William L. Thomson Jr.
2017-01-16 21:09 ` Roy Bamford
2017-01-16 19:31 ` William L. Thomson Jr.
2017-01-16 19:20 ` Dale
2017-01-16 18:43 ` Dale
2017-01-16 18:52 ` Rich Freeman
2017-01-16 19:21 ` William L. Thomson Jr.
2017-01-16 19:19 ` William L. Thomson Jr.
2017-01-16 17:50 ` Alec Warner
2017-01-16 18:01 ` Rich Freeman
2017-01-16 18:02 ` Alec Warner [this message]
2017-01-16 18:10 ` William L. Thomson Jr.
2017-01-16 20:16 ` Andreas K. Huettel
2017-01-16 20:23 ` M. J. Everitt
2017-01-16 20:27 ` Ciaran McCreesh
2017-01-16 20:42 ` Dale
2017-01-16 21:41 ` William L. Thomson Jr.
2017-01-16 21:37 ` William L. Thomson Jr.
2017-01-16 18:40 ` Matthew Thode
2017-01-16 18:49 ` Dale
2017-01-15 15:00 ` Roy Bamford
2017-01-15 15:30 ` 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='CAAr7Pr-1WB52+o14Ks8yjp8xJ6+tN0QkNvwzY1OgxR68R=537w@mail.gmail.com' \
--to=antarus@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