From: Deedra Waters <dmwaters@gentoo.org>
To: gentoo-trustees@lists.gentoo.org
Subject: RE: [gentoo-trustees] TODO list, revisited
Date: Sat, 17 Jul 2004 11:32:49 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.56L0.0407171130260.13087@toucan.gentoo.org> (raw)
In-Reply-To: <200407171613.i6HGDfAM025423@mail-relay.iu.edu>
In all honesty, I think a phone conference would be a bit better then an irc meeting, though I'm not sure how many would go for this...
As for september, August or very early september might be better, I'll be moving in september, and will probably be out of touch from about the 10th till the 17th unless I can steal internet access from polvi or while I'm at work.
On Sat, 17 Jul 2004, Corey Shields wrote:
> Date: Sat, 17 Jul 2004 11:13:51 -0500
> From: Corey Shields <cshields@gentoo.org>
> Reply-To: gentoo-trustees@lists.gentoo.org
> To: gentoo-trustees@lists.gentoo.org
> Subject: RE: [gentoo-trustees] TODO list, revisited
>
>
> Yes, I think a meeting would be good. September might be too far off..
>
> As for the IRS 1024 application, we will need 3 things:
>
> - An Employee ID number (I'm already working on that)
> - Our list of bylaws, we all need to jump on this
> - $500. (not $5,000, it just costs $500)
>
> Bylaws, anyone?? :)
>
> Cheers!
>
> -----Original Message-----
> From: Grant Goodyear [mailto:g2boojum@gentoo.org]
> Sent: Saturday, July 17, 2004 11:05 AM
> To: gentoo-trustees@lists.gentoo.org
> Subject: [gentoo-trustees] TODO list, revisited
>
> Dear all,
> Once upon a time Kurt posted a todo list at
> http://dev.gentoo.org/~klieber/trustees/todo.php. I think it's time we take
> another look at this list, see where we stand, and divide up tasks and set
> new target deadlines so that we can get things moving as though we actually
> have a plan. (I assume we can get this list moved onto the new groupware
> server once it goes live, so that we can all make changes as appropriate?)
> Also, I think we should schedule a Trustees meeting on IRC for sometime in
> September.
>
> Revisions to the todo list:
>
> Transfer IRC channels -- I assume this is done Complete NFP paperwork --
> done Hard copies of copyright forms -- pointless, since I'm pretty sure
> we're going to need new ones anyway.
> Transition dev machines to OSU -- done, I believe Obtain legal counsel --
> zhen has taken point here
>
> Best,
> g2boojum
>
> PS. Because it's one that I'm familiar with, I'm using the Python Software
> Foundation (http://www.python.org/psf/) as an example for what we might want
> to do. Do people have additional examples that might be useful to examine?
>
--
Deedra Waters - Gentoo developer relations, accessibility and infrastructure -
dmwaters@gentoo.org
Gentoo linux: http://www.gentoo.org
--
gentoo-trustees@gentoo.org mailing list
next prev parent reply other threads:[~2004-07-17 16:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-17 16:04 [gentoo-trustees] TODO list, revisited Grant Goodyear
2004-07-17 16:13 ` Corey Shields
2004-07-17 16:32 ` Deedra Waters [this message]
2004-07-19 16:34 ` Daniel Robbins
2004-07-19 16:55 ` Corey Shields
2004-07-19 19:54 ` Daniel Robbins
2004-07-17 16:28 ` Deedra Waters
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.0407171130260.13087@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