I'm disowning sage-mathematics, sage-mathematics-spkgs(optdepends for
sage-mathematics), fityk, and xylib(dependency for fityk).
I will move them to the aur in a week if no TU adopts them in community.
If you plan on adopting sage-mathematics, you should know that it is
currently unbuildable on archlinux, and some other newer distros due
to how it is built.
It is currently out of date, and you wont be able to update it without
http://trac.sagemath.org/sage_trac/ticket/10572 (13 month old bug
without recent comments)
http://trac.sagemath.org/sage_trac/ticket/11391 (9 month old bug I
filed without a sign of activity)
If you plan on adopting fityk, note that it needs a development
version of wxwidgets which I statically build in the same PKGBUILD.
I was looking for a sponsor in August 2012 , and thank Jonathan
Steel for contacting me right after he became a new TU. He helps me a
lot and I'm keeping clean up and improve my PKGBUILDs in AUR with his
suggestions. I think I can do more than as a user, so I am now
applying to become a Trusted User, after some knowledge & skills
preparing in the last few weeks. Bartłomiej Piotrowski has kindly
sponsored me (just today :P and thanks a lot).
I love Arch mainly because of the PKGBUILD. Never could I find another
great and simple-enough to write description file of an easy-to-use
package manager. I never created a successful package in .deb although
I was a Ubuntu and PPA user for more than two years(Hmm, my lack of
knowledge in bash & English should also be a problem at that time).
When I began to use Arch, I was impressed deeply by pacman(A lot of
points are in "ILoveCandy", although :P) and that's why I switched all
my workspaces to Arch.
I have been an Archer only for one year and a half but 4 for the Linux
world. I submitted my first package by the end of last year, and
maintain more and more during the last a few months (61 for now ,
with a total of 460 votes). I am eager to maintain packages that loved
and needed by Chinese users as I am one too, such as input
methods(fcitx-*, ibus-*, sunpinyin, libpinyin, rime, etc), internet
supplicant in Chinese universities(mentohust/ruijieclient), chat tools
qq related(linuxqq, webqq, libqq*, etc) and popular proxy tools
(sshuttle, goagent, etc). As I am a python programmer and maintaining
more than 20 python libraries I use for now, I'm also ready for some
popular python libraries. I'll take those orphans in [community] (or
possibly [extra] if approved and moved) in these cases, too.
I am also a good user in keeping active in reporting and following
issues upstream, such as pidgin-lwqq .
As I looked after more and more packages on AUR I found many users not
so convenient to install so many packages in AUR, so I joined
archlinuxcn's community repository project  to provide popular
packages in binary. But this is not good for user to involve in (such
as flag out-of-date, report bugs, etc). It could be a lot better if I
could move the most popular ones into [community] so users does not
need to manually add a (not fully-trusted) third-party community
I am also an IT manager in work, and maintaining several Arch servers.
I only use x86_64 architecture but keep an eye on i686 as some of the
old hardwares are not ready for 64-bit. I have several popular WM/DEs
installed but using XFCE mostly.
I am a wine user and keep an eye on its fresh news. Although I am not
using any wine programs too much, I sometimes play osu! or TESV:
Skyrim under wine.
Some more info about me: 21, male, Wuhan in China, working in a
startup, not very good at C and English, but trying to keep them in a
package-ready level :P A classical music lover, and also accept some
of the NewAge.
Thank you for your time in reading my application.
 https://github.com/xiehuc/pidgin-lwqq/issues?page=1&state=closed (Chinese)
I converted our TU bylaws to AsciiDoc and imported he converted document
into a Git repository that I temporarily hosted on . Maybe we can
eventually move that to one of the Arch Linux servers.
Benefits of the new version:
* Much less noise in bylaw patches (HTML patches were unreadable).
* History of bylaw amendments.
* AsciiDoc style that we use in a couple of other places already.
Kyle and me will probably also send one or two patches to the content,
so if there's anything else that you would like to add/amend, now would
be a good time to do that.
I also temporarily hosted a preview of the new HTML document on .
Opinions? Any objections to the AsciiDoc conversion?