On 26/02/13 22:12, Jonathan Steel wrote:
On Tue, Feb 26, 2013 at 03:37:48PM +0100, Jorge Barroso wrote:
El Lunes, 25 de febrero de 2013 20:46:46 Vitor Eiji Justus Sakaguti escribió:
On Feb 25, 2013 4:26 PM, "Connor Behan" <connor.behan@gmail.com> wrote:
On 25/02/13 08:09 AM, Rudy Matela wrote:
https://wiki.archlinux.org/index.php/Trusted_Users#How_to_become_TU.3F
On Mon, Feb 25, 2013 at 1:01 PM, Jorge Barroso
<jorge_barroso_11@hotmail.com> wrote:
Hi, I'm Jorge Barroso (jorge_barroso in the AUR), I've been an Arch
user for
some time and I've learned a lot of things since I do it. Now, I'd
like to
apply as a trusted user, so I'd like that anybody helped me telling me
what
should I do yet to became a Trusted User
Regards
And the one additional requirement for becoming a TU not mentioned there is no top posting! :-P
Also, you need a really good excuse to get away with using hotmail!
Jaja, sorry, I have recently started to use kmail as email desktop client, and I got two email accounts. The hotmail one it's because of I have some old accounts with my hotmail account registered, and it also helps me to avoid span on my gmail account, which is the official one which I registered here :P I've read the wiki page from Rudy Matela, and I think I have all the basic things I should have... Know basic shel scripting... 18 packages on the aur Basic community involvement I really know google-fu (if it is what I think it is...) and I got a general idea on the kind of packages I would like to mantain
If someone could tell me their opinion, it would be great, because I'd like to improve what I need to improve
Make sure you follow the packaging standards and read similar wiki pages (anything about packaging, standards, TU/developer pages). It would help to look at PKGBUILDs from the official repos to get an idea of the style that is used and standardise yours.
It would help to get involved upstream, improve the wiki, help on the forum etc. Get familiar with svn and use devtools to build your packages.
Fix bugs on the bugtracker, report bugs. You could for example join #archlinux-bugs.