From: Lance Albertson <ramereth@gentoo.org>
Cc: gentoo-trustees@lists.gentoo.org
Subject: Re: [gentoo-trustees] Transfer, continued
Date: Wed, 18 May 2005 14:42:54 -0500 [thread overview]
Message-ID: <428B9ABE.2040207@gentoo.org> (raw)
In-Reply-To: <20050518190044.GM8032@bmb24.uth.tmc.edu>
[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]
> ----- Forwarded message from seemant <seemant@gentoo.org> -----
> I'm personally fine with drobbins having the @gentoo email forward
> indefinitely. I know infra may have issues (corey, kurt, rame --
> comments?), but philosophically, I agree with Grant on the matter.
I don't have a problem of doing this unless something bad happens with his email
address (I can't even think of an example). We do at least owe him that. The
only thing I ask is that any forward he uses is fairly reliable. If its bouncing
a lot and making a huge queue, I may have to take his .forward out so things get
delivered locally at least.
> As for the rest, the only thing I'm unsure of is how we'd handle the
> developers' copyright assignments (specifically revoking the same).
I'm not sure as I need to read up on whats all going on!
--
Lance Albertson <ramereth@gentoo.org>
Gentoo Infrastructure | Operational Manager
---
Public GPG key: <http://www.ramereth.net/lance.asc>
Key fingerprint: 0423 92F3 544A 1282 5AB1 4D07 416F A15D 27F4 B742
ramereth/irc.freenode.net
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]
next prev parent reply other threads:[~2005-05-18 19:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 19:00 [seemant@gentoo.org: Re: [gentoo-trustees] Transfer, continued] Grant Goodyear
2005-05-18 19:42 ` Lance Albertson [this message]
2005-05-18 19:50 ` Corey Shields
-- strict thread matches above, loose matches on Subject: below --
2005-05-18 18:38 [gentoo-trustees] Transfer, continued Grant Goodyear
2005-05-18 19:19 ` Grant Goodyear
2005-05-18 21:06 ` Deedra Waters
2005-05-18 22:38 ` 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=428B9ABE.2040207@gentoo.org \
--to=ramereth@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