Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-trustees
Navigation:
Lists: gentoo-trustees: < Prev By Thread Next > < Prev By Date Next >
Headers:
From: Lance Albertson <ramereth@g.o>
Subject: Re: Transfer, continued
Date: Wed, 18 May 2005 14:42:54 -0500
> ----- Forwarded message from seemant <seemant@g.o> -----

> 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@g.o>
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:
signature.asc (OpenPGP digital signature)
References:
[seemant@g.o: Re: Transfer, continued]
-- Grant Goodyear
Navigation:
Lists: gentoo-trustees: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
[seemant@g.o: Re: Transfer, continued]
Next by thread:
Re: [seemant@g.o: Re: Transfer, continued]
Previous by date:
Re: Transfer, continued
Next by date:
Re: [seemant@g.o: Re: Transfer, continued]


Updated Jun 17, 2009

Summary: Archive of the gentoo-trustees mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.