[aur-general] I'm wonder is there any tool to list TU's workload?
I guest the TU's workload may be calculated by a. How many packages which he owns. b. How many commits during a past year c. How many bugs required to solved? To print out by graph maybe interesting. These may be calculated by some SQL if owned the access permission of database. For person without permission may pull the packages and bugs listing and git log to get that picture
[aur-general] [tu-bylaws][PATCH] extend tu addition discussion period to 14 days
I quite definitively should not send patches when being incredibly tired, of cause the subject should be "14 days" matching what the body actually describes and changes. I'm sorry >.> Levente signature.asc Description: OpenPGP digital signature
[aur-general] [tu-bylaws][PATCH] extend tu addition discussion period to 7 days
Just adding this signed mail to authenticate i indeed proposed this change :) cheers, Levente signature.asc Description: OpenPGP digital signature
[aur-general] [tu-bylaws][PATCH] extend tu addition discussion period to 7 days
From: anthraxx Signed-off-by: Levente Polyak --- The discussion period for the addition of a new TU is too short. After having some chats on this topic with multiple TUs it seemed like a general consensus to extended the dicussion period to 14 days, hence this proposal. 5 days are rarely enough to discuss all details with the applicant taking into account that f.e. lots of packages need to be reviewed. Once feedback was given to the applicant there shall be enough time to work through it, potentially research, apply and/or discuss things out of the feedback. Given the fact that many people, including the applicant, may be in the middle of a work week (or otherwise busy), having only 5 days to do one or multiple feedback loops is unrealistic and too much pressure. Considering the fact that it is an essential part for a TU to be able to decide on the vote as well as for the applicant to have enough time and the possibility to respond properly to the input an adjusted discussion period of 14 days shall be appropriate. --- tu-bylaws.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tu-bylaws.txt b/tu-bylaws.txt index 27e4804..d32e06c 100644 --- a/tu-bylaws.txt +++ b/tu-bylaws.txt @@ -104,10 +104,10 @@ In order to become a TU, one must first find a sponsoring TU, and arrange privately with them to announce their candidacy on the https://mailman.archlinux.org/mailman/listinfo/aur-general[aur-general] mailing list. Following the announcement, standard voting procedure commences with a -discussion period of 5 days, a quorum of 66%, and a voting period of 7 days. +discussion period of 14 days, a quorum of 66%, and a voting period of 7 days. -SVP( addition_of_TU, 5, 0.66, 7 ); +SVP( addition_of_TU, 14, 0.66, 7 ); If a candidate is rejected by SVP, they may not reapply to become a Trusted -- 2.18.0
Re: [aur-general] TU application - Daniel YC Lin
Finally, I've re-setup my Enigmail and opengpg with correct e-mail. Now this e-mail is signed with the same email address which I use for register aur-genearl maillist. On 8/17/18 11:06 AM, Daniel YC Lin wrote: > Hello, > > My name is Daniel YC Lin, I'm 48 years old and I'm programmer in Taipei, > Taiwan. On the forums and irc you can find me as dlintw. > > As you can see with some of my packages > [https://aur.archlinux.org/packages/?O=0=m=dlin;] > > I'm interested in packaging for arch related zh-tw locale packages. > > I've nearly 30 years shell scripts experiences. I've build Archlinux on > sh4 CPU about 4-5 years ago. During that experience I've learned from > uboot to linux kerenl and all 'base' packages build from scratch. > There are no special packages which I wish to put in my repository. > I wish to share the loading of Felix Yan for example (gcin) > My sponsor is Felix Yan. > > Best Regards, > Daniel Lin > > > signature.asc Description: OpenPGP digital signature
