Trusted Users
The Trusted Users serve the following purposes:
- Maintain the community repository as an intermediary between Arch Linux's official repositories and the unsupported package collection in the AUR.
- Maintain, manage, and watch over the operation of the AUR.
How do I become a TU?
The minimum requirements to becoming a TU are as follows:
- know basic shell scripting
- maintain a few packages in AUR with clean, high-quality PKGBUILDs
- basic community involvement (mailing list, forums, IRC)
- know Google-Fu
- a general idea of the kind of packages you want to maintain (basically, why do you want to become TU?)
Even though you could become a TU by merely fulfilling those minimum requirements, the people judging you during the standard voting procedure might expect more from you. Such as:
- involvement in the bug tracker (reporting, research, info)
- patches for Arch projects
- involvement in a few open-source projects (even if they are your own)
If you still feel up to becoming a TU after reading these lines, the first step is to find two TUs who agree to sponsor you. Once sponsored, you should write a witty application signed with your GPG key to the aur-general mailing list.
Note: Should a TU you contact decline to sponsor your application, you should make this fact known if you seek sponsorship from another TU.
For more information, see the Trusted User Bylaws, Trusted Users Bylaw Amendment and AUR Trusted User guidelines.
Active Trusted Users
Past Trusted Users
See https://archlinux.org/people/trusted-user-fellows/
gollark: I'll try and explain it better then- the quotas at random.org are *presumably* limiting your access to random bits based on your IP - that is, the IP it gets the requests from, not one you specify, that would be silly.- when using your proxy, the requests are coming from the proxy's IP- thus, you should get the quotas from the *same IP* you're contacting random.org from- in the case of your `curl` thing it works, as you're requesting the quota for the same IP you send requests from- this will not be the case if you attempt to fetch the quota for your computer's real IP when it's accessing random.org through the proxy
gollark: **gollark** is typing...
gollark: *But* that's *invalid* if you're going to use the proxy to contact random.org itself.
gollark: No, if he's sending the random.org request from `curl` and then using the IP of the device `curl`ing for the quota, it'll work.
gollark: You're entirely missing the point.
This article is issued from Archlinux. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.