Bug 22662 - Account Request
Summary: Account Request
Status: RESOLVED FIXED
Alias: None
Product: freedesktop.org
Classification: Unclassified
Component: New Accounts (show other bugs)
Version: unspecified
Hardware: All All
: medium normal
Assignee: fd.o Admin Massive
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-07 11:56 UTC by Gaetan Nadon
Modified: 2009-11-05 16:09 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
SSH RSA Public Key (394 bytes, text/plain)
2009-07-07 11:56 UTC, Gaetan Nadon
Details
GPG Public key (2.80 KB, text/plain)
2009-07-07 11:58 UTC, Gaetan Nadon
Details

Description Gaetan Nadon 2009-07-07 11:56:07 UTC
Created attachment 27474 [details]
SSH RSA Public Key

Real name: Gaetan Nadon
e-mail: memsize@videotron.ca
Preferred account name: memsize

I have attached the SSH and GPG public keys. For now I have a couple of bugs to fix 22611 and 22616 with Alan's help.
Comment 1 Gaetan Nadon 2009-07-07 11:58:07 UTC
Created attachment 27475 [details]
GPG Public key
Comment 2 Gaetan Nadon 2009-07-08 15:33:29 UTC
Apologies, I just read the RepoPolicy. This is what I had been looking for in the last few days. Makes sense now, it's very similar to eclipse.org. I came across the Account Request page first. 

It would be premature to have commit privilege right now. I'd be happy to use one of the alternatives. I have no fixed plan, I was following the "janitor" suggestion and see where it leads.
Comment 3 Gaetan Nadon 2009-07-18 07:32:08 UTC
Will request later. Closing for now.
Thanks
Comment 4 Gaetan Nadon 2009-09-27 17:35:35 UTC
Reopening.

Preferred account name: gnadon

Thanks Peter
Comment 5 Peter Hutterer 2009-09-27 17:54:02 UTC
ACK
Comment 6 Alan Coopersmith 2009-09-27 21:44:43 UTC
Ack from me too, reassigning to fdo admin queue for processing.
Comment 7 Benjamin Close 2009-11-05 16:09:32 UTC
Account Created - Please run initial patches past Peter before committing.
Welcome aboard!


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.