On Fri, Apr 13, 2012 at 3:43 AM, Kaiting Chen <kaitocracy@gmail.com> wrote:

Agreed; it's nice to have a single centralized document that delineates the procedure. I don't think that we should remove the eleventh point of

https://wiki.archlinux.org/index.php/New_AUR_TU_guidelines#TODO_list_for_new...

however as it is perfectly conceivable for a TU to use a different key for their package signing. --Kaiting.

On Fri, Apr 13, 2012 at 3:38 AM, Ike Devolder <ike.devolder@gmail.com>wrote:

...

Hi,

after my own application and seeing it again i would like to propose an update to the TU Bylaws giving more information that the application should be gpg signed with the addidional publication of the public key.

This would also imply we can remove the eleventh point of:

https://wiki.archlinux.org/index.php/New_AUR_TU_guidelines#TODO_list_for_new...

attached the patch for https://aur.archlinux.org/trusted-user/TUbylaws.html

--Ike

-- Kiwis and Limes: http://kaitocracy.blogspot.com/

Ahh sorry about the top post guys. A little inebriated after a long day of work and I forgot about the standard here. --Kaiting. -- Kiwis and Limes: http://kaitocracy.blogspot.com/

Op vrijdag 13 april 2012 13:30:23 schreef Florian Pritz:

On 13.04.2012 09:38, Ike Devolder wrote:

...

This would also imply we can remove the eleventh point of: https://wiki.archlinux.org/index.php/New_AUR_TU_guidelines#TODO_list_for_n ew_Trusted_Users Don't remove it, but replace it with something like "Get your/a GPG key signed by the master keys".

...

attached the patch for https://aur.archlinux.org/trusted-user/TUbylaws.html

Looks like mailman removed it.

yeah great

-- Florian Pritz

http://www.herecura.be/files/tu-bylaws-gpg-update.diff --Ike