public inbox for gentoo-trustees@lists.gentoo.org
 help / color / mirror / Atom feed
From: Deedra Waters <dmwaters@gentoo.org>
To: gentoo-trustees@lists.gentoo.org
Subject: RE: [gentoo-trustees] Legal advice
Date: Thu, 15 Jul 2004 12:14:16 -0500 (CDT)	[thread overview]
Message-ID: <Pine.LNX.4.56L0.0407151211080.22515@toucan.gentoo.org> (raw)
In-Reply-To: <20040715165002.83ABD5DF6B@meep.gentoo.org>

I still think that we should stay with c6 status. c3 may or may not give us more benifits, but  1, we don't know that it will for sure, and 2, as I've said before there's  a lot more potential to end up with problems if we're not careful. I would rather stay with what the origional agreement was, and that's c6.

I'm not oposed to a second opinion either, but this is just what I think.


On Thu, 15 Jul 2004, Daniel Robbins wrote:

> Date: Thu, 15 Jul 2004 10:40:22 -0600
> From: Daniel Robbins <drobbins@gentoo.org>
> Reply-To: gentoo-trustees@lists.gentoo.org
> To: gentoo-trustees@lists.gentoo.org
> Subject: RE: [gentoo-trustees] Legal advice
> 
> Hi,
> 
> Since our agreement was for the NFP to apply for federal trade association
> (not charity) status, exploring the possibility of c3 status constitutes a
> significant change of our agreed-upon plan.
> 
> If you choose to apply for c3 status instead, I reserve the right to make
> some reasonable adjustments on my side as well. So while I'm skeptical of
> the legitimacy of applying for c3 status, I'm also open to you getting
> additional legal advice and even applying for c3 status if lawyers agree
> that it's perfectly legitimate. 
> 
> But it's important for all trustees to understand that this would constitute
> a material change to our agreed-upon plan. If you make changes, I reserve
> the right to make some changes too. 
> 
> Hopefully, we can stay on the same page, and if any adjustments need to be
> made, we'll try to make sure that they're reasonable to everyone. Just
> please understand that if you tweak the plan, you should be willing to allow
> me to make tweaks as well. If you're not willing to allow me to make tweaks,
> then you shouldn't be willing to make tweaks to the plan either. Just trying
> to be egalitarian here.
> 
> Regards,
> 
> Daniel
> 
> 
> 
> --
> gentoo-trustees@gentoo.org mailing list
> 
> 

-- 
Deedra Waters - Gentoo developer relations, accessibility and infrastructure -
dmwaters@gentoo.org
Gentoo linux: http://www.gentoo.org


--
gentoo-trustees@gentoo.org mailing list


  parent reply	other threads:[~2004-07-15 17:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-14 21:11 [gentoo-trustees] Legal advice John Davis
2004-07-14 21:14 ` Deedra Waters
2004-07-14 21:31   ` Seemant Kulleen
2004-07-14 21:37 ` Grant Goodyear
2004-07-15  0:26   ` Nicholas Jones
2004-07-15 12:22     ` Kurt Lieber
2004-07-15 16:40       ` Daniel Robbins
2004-07-15 16:52         ` Kurt Lieber
2004-07-15 17:38           ` Daniel Robbins
2004-07-15 17:41             ` Deedra Waters
2004-07-15 17:14         ` Deedra Waters [this message]
2004-07-15 17:22         ` Corey Shields
2004-07-15 17:45           ` Daniel Robbins
2004-07-16  5:43             ` Paul de Vrieze
2004-07-15 16:49       ` Aron Griffis

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=Pine.LNX.4.56L0.0407151211080.22515@toucan.gentoo.org \
    --to=dmwaters@gentoo.org \
    --cc=gentoo-trustees@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