Bug 50979 - Request an fdo account
Summary: Request an fdo account
Status: RESOLVED FIXED
Alias: None
Product: freedesktop.org
Classification: Unclassified
Component: New Accounts (show other bugs)
Version: unspecified
Hardware: All other
: medium normal
Assignee: fd.o Admin Massive
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-11 12:06 UTC by Alexander von Gluck
Modified: 2012-06-13 11:36 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
kallisti5 public ssh key (403 bytes, application/octet-stream)
2012-06-11 12:07 UTC, Alexander von Gluck 		Details
kallisti5 public gpg key (3.06 KB, application/octet-stream)
2012-06-11 12:15 UTC, Alexander von Gluck 		Details
View All

Description Alexander von Gluck 2012-06-11 12:06:03 UTC 
Alexander von Gluck
kallisti5@unixzen.com

Reason for request:
 Upkeep of Haiku Mesa build target and other related tasks.

 My goal for Mesa is to keep stock Mesa (and Gallium3D) functioning on Haiku. So far the design policy has been to do minimal Haiku references in the Mesa codebase to ensure as little strain as possible occurs on the Mesa team. (not needing to rewrite large chunks of Haiku centric code for changes, etc)

 Stock Mesa on Haiku.. that's our goal.
Comment 1 Alexander von Gluck 2012-06-11 12:07:58 UTC 
Created attachment 62898 [details]
kallisti5 public ssh key
Comment 2 Alexander von Gluck 2012-06-11 12:15:04 UTC 
Created attachment 62900 [details]
kallisti5 public gpg key
Comment 3 Alexander von Gluck 2012-06-11 12:19:31 UTC 
Little additional information:

 * xorg foundation member since Jan 2012
 * frequent commiter to Haiku project (MIT licensed)
   http://cgit.haiku-os.org/haiku/log/?qt=author&q=kallisti5
 * wrote Haiku radeon_hd driver
 * got stock Mesa 8.0 swrast running under Haiku (moving away from Haiku's forked Mesa)
Comment 4 Brian Paul 2012-06-11 14:37:51 UTC 
Approved.
Comment 5 Tollef Fog Heen 2012-06-13 11:36:49 UTC 
Account created, welcome.

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.