On Sat, Aug 01, 2009 at 02:41:45PM +0100, Stephen Gran wrote:
Encrypting this information to the various persons implies that the
project itself can lose access to this information if those people all
become unavailable in the future. Is the information also stored somewhere
that DSA (the
On Fri, Jul 31, 2009 at 04:03:14PM +0200, Joerg Jaspert wrote:
Currently we think a good way to do this is to have the applicant be
known to multiple Debian Developers who speak up for them to the DAM.
The applicant, who should be a long-term contributor already, also needs
to be willing to
This one time, at band camp, Steve Langasek said:
On Fri, Jul 31, 2009 at 04:03:14PM +0200, Joerg Jaspert wrote:
Currently we think a good way to do this is to have the applicant be
known to multiple Debian Developers who speak up for them to the DAM.
The applicant, who should be a
Hi,
while this was raised for a specific applicant, lets make this a general
statement.
In general we do require every applicant to join the project using their
legal name, not any given synonym they might use. This is one reason why
we require multiple signatures on every key added to the
1. Identification Account Data
First name: Vagrant
Last name: Cascadian
Key fingerprint: 4096R/E3BF6C78 093E 70A1 D8CF 9802 59EB E043 0304 2BF0
E3BF 6C78
Account: vagrant
Forward email: vagr...@freegeek.org
ID check
5 matches
Mail list logo
