Due to the recent unavailability of the main Java-GNOME developer commit access for cairo-java needs to be assigned to at least one other person. After discussion with the active community several people have been nominated to take on the role at the moment. -Ismael Juma, currently has a freedesktop account, needs to get it enabled for cairo-java. -Andrew Cowie (andrew@operationaldynamics.com), currently has no freedesktop account, needs to have one created and enabled for cairo-java (ssh key attached). -Igor Foox (ifoox@redhat.com), currently has no freedesktop account, needs to have one created and enabled for cairo-java(ssh key attached) -Sami Wagiaalla (swagiaal@redhat.com), currently has no freedesktop account, needs to have one created and enabled for cairo-java(ssh key attached) -Adam Jocksch (ajocksch@redhat.com), currently has no freedesktop account, needs to have one created and enabled for cairo-java(ssh key attached).
Created attachment 3191 [details] SSH key for Andrew Cowie
Created attachment 3192 [details] SSH key for Adam Jocksch
Created attachment 3193 [details] SSH key for Igor Foox
Created attachment 3194 [details] SSH key for Sami Wagiaalla
BTW Ismael's freedesktop account name is 'ijuma'.
Desired account name for Andrew Cowie is 'afcowie', for the others it is the same as the first portion of the email (i.e. ifoox, ajocksch, swagiaal). Thanks :) Igor
I've added cairo-java committ access to the ijuma account. Since all the other requests require new account creation as well, I'll need GPG keys before I can do that.
Created attachment 3207 [details] GPG Key for Igor Foox Added GPG key
Created attachment 3208 [details] GPG Key for Sami Wagiaalla Added GPG key
Created attachment 3209 [details] GPG Key for Adam Jocksch Added GPG key
Created attachment 3210 [details] GPG Key for Andrew Cowie
Thanks for the extra information. All of these accounts have now been created and given commit access to the cairo-java CVs module. Happy hacking!
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.