public inbox for gentoo-trustees@lists.gentoo.org
 help / color / mirror / Atom feed
From: Corey Shields <cshields@gentoo.org>
To: gentoo-trustees@lists.gentoo.org
Cc: drobbins@gentoo.org
Subject: [gentoo-trustees] Re: TODO list posted.
Date: Wed, 5 May 2004 21:43:57 -0500	[thread overview]
Message-ID: <200405052143.58314.cshields@gentoo.org> (raw)
In-Reply-To: <20040429015352.GU13780@mail.lieber.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


It has been a week now since this has been posted.  Can we get status reports 
from everyone so Kurt can update the list?

The IRS application I am working on will take some time.  Right now I am 
investigating and I want to take legal opinions from as many groups possible 
and then present those to the rest of you so we can get this done right.  
Bear with me on this but know that I am working on it.

How about the rest of the stuff?

I have no problem with the bank that Kurt had mentioned earlier.  Will we have 
a starting balance in order to open the account?  Do we have a federal tax ID 
yet  (should the Gentoo Technologies ID transfer without giving us problems 
when filing the 501?)

Cheers!

- -Corey

On Wednesday 28 April 2004 08:53 pm, you wrote:
> I have taken the transition plan I posted earlier and transformed it into a
> web page where we can keep track of things:
>
> http://dev.gentoo.org/~klieber/trustees/todo.php
>
> Tasks that Daniel needs to be involved in are grouped at the top.  The
> others are at the bottom.  Regarding the 501(c)(6) application, I talked to
> Corey who said that Indiana University (where he works) may be willing to
> help us process the necessary paperwork.  We have a good, established
> relationship with IU (they host a number of infra boxes for us) so if
> nobody else objects, I'd like to suggest we take advantage of their offer.
>
> For the Internal Board Structure, Sven had indicated he was interested in
> documenting this and nobody else spoke up, so I arbitrarily listed his name
> there.  I would expect that we'll all be involved in the actual formulation
> of the structure -- I just thought Sven would be the natural choice to
> write it all down. :)
>
> For the other tasks, you'll note there are click-through links to go to
> pages that contain additional information.  Please review as you have time
> and post any comments/questions/suggestions here.
>
> --kurt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAmaZtpq/4o6MEFFMRAq2kAJoD40UNvG/kYvujeDbLdDcFq99F5ACgkUl+
VarQ02mM3Oic7UVNkIBHqm4=
=kJr1
-----END PGP SIGNATURE-----

--
gentoo-trustees@gentoo.org mailing list


       reply	other threads:[~2004-05-06  2:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040429015352.GU13780@mail.lieber.org>
2004-05-06  2:43 ` Corey Shields [this message]
2004-05-06  7:02   ` [gentoo-trustees] Re: TODO list posted Sven Vermeulen
2004-05-08 14:35   ` Deedra Waters
2004-05-08 21:42     ` Seemant Kulleen
2004-05-08 21:58       ` Deedra Waters
     [not found] <20040506080449.2F79E283B3@meep.gentoo.org>
2004-05-06 20:51 ` Corey Shields
2004-05-06 21:11   ` Daniel Robbins

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=200405052143.58314.cshields@gentoo.org \
    --to=cshields@gentoo.org \
    --cc=drobbins@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