Re: [aur-general] TU Application: Daniel M. Capella

[Daniel Capella via aur-general]

> - The following can be used for GitHub releases (where $url is eg.
>>   ):
>>
>>   - Before:
>> `source=("$pkgname-$pkgver.tar.gz::$url/archive/v$pkgver.tar.gz")`
>>   - After: `source=("$url/archive/v$pkgver/$pkgname-v$pkgver.tar.gz")`
>
>
> Correction: $pkgname in the after line is only correct if it matches the
> project name, tense included -- assuming you like it to match the name of
> the downloaded tarball. Same goes for the version (eg. the "v" some
> projects use). For ease of use, perhaps best to keep this out of the
> guidelines.
>

Further correction: With the after line, the "v" is always stripped with
the downloaded tarball. That would make this example:
`source=("$url/archive/v$pkgver/$pkgname-$pkgver.tar.gz")`

-- 
Best,
polyzen

Re: [aur-general] TU Application: Daniel M. Capella

[Daniel Capella via aur-general]

>
> - The following can be used for GitHub releases (where $url is eg.
>   ):
>
>   - Before:
> `source=("$pkgname-$pkgver.tar.gz::$url/archive/v$pkgver.tar.gz")`
>   - After: `source=("$url/archive/v$pkgver/$pkgname-v$pkgver.tar.gz")`


Correction: $pkgname in the after line is only correct if it matches the
project name, tense included -- assuming you like it to match the name of
the downloaded tarball. Same goes for the version (eg. the "v" some
projects use). For ease of use, perhaps best to keep this out of the
guidelines.

-- 
Best,
polyzen

Re: [aur-general] TU Application: Daniel M. Capella

[Ivy Foster via aur-general]

I confirm my sponsorship; let the games (or discussion, I guess)
begin!

iff ("escondida")


signature.asc
Description: PGP signature

[aur-general] TU Application: Daniel M. Capella

[Daniel M. Capella via aur-general]

Hello,

My name is Daniel M. Capella (aka polyzen), and I am applying to be a Trusted
User with Ivy Foster's sponsorship.

My current main interest lies in Rustlang-based blockchain/distributed
app/cryptocurrency implementations; half for the tech, half so I can escape the
world of indentured slavery, fearlessly. My dream for the future is to write
software that will help increase the pace it takes science to build the world
of tomorrow -- whatever that means. I watch too much sci fi.

I hope you like lists as much as I apparently do.



Stats:

- Arch vanilla user since 2013. ALARM user for my home servers since perhaps a
  year or two before then. For completion's sake, even before that I had used
  Ubuntu and Archbang. This year I will be getting the LPIC-2[1] certificate
  (may or may not be related to my LPIC-1 expiring this year ^^).

- Held a workshop called "Git for Gits"[2] with meskarune under the Arch Linux
  Classroom. The class is (very) slowly being revamped for further sessions.

- Coordinated AUR Cleanup Day 2017[3]. The original plan was for this to occur
  every other year, but the previous one was in 2010. I hope to continue the
  tradition of this occurring biennially.

- Co-maintainer of pacman-contrib. Funny story: when I requested Git access,
  Florian gave it to me thinking I was Kyrias. ^^ I had a habit of nick (IRC)
  hopping back then.

- Arch Linux Tester when I remember that's a thing I signed up for.

- Relatively active with IRC and bug tracker support.

- Very active with upstreams WRT packaging and then some.



Here follows the packages I'd like to move to and/or co-maintain in Community:

- Packages I already maintain:

  - Automatic exception:

- espeak-ng (accessibility)

  See also .

  - Popular:

- firefox-ublock-origin
- firefox-umatrix

- pulseaudio-dlna

- python-black 

  Maxim already plans to add this to the repos, but I would like to
  (co-)maintain this, being the original submitter (before it was merged
  into python-black due to the naming convention).

- razercfg/razerd

  - 1% usage on pkgstats:

- firefox-bookmarkdupes
- firefox-multiple-tab-handler
- firefox-referer-control
- firefox-stylus
- firefox-tab-flip-for-tree-style-tab
- Firefox-tree-style-tab

- termdown

- tty-solitaire

  See .

  - There was consensus from a few TU's in #archlinux-aur on considering the
popularity of release variants:

- Popular:

  - shaderc (-git)

See also .

- 1% usage on pkgstats:

  - gmailieer (-git)

  - termtosvg (-git)

- Other users' AUR packages:

  - Popular:

- alot

- hsetroot

- python-proselint

- ttf-symbola

- yamllint

  - 1% usage on pkgstats:

- python-vint

- skim

- Repo packages:

  - Orphans in Extra that I have installed:

- ttf-indic-otf

- vulkan-icd-loader

  - Packages I submitted to the AUR that were adopted or were added to the repos
without checking the AUR first :p:

- asp

- fd

- newsboat



Notes from Ivy that may come up in reviews:

- “These Node.js and mkchromecast packages give me nightmares.”:
  
  ..Okay, actually that was my response when he brought them up.

  mkchromecast has a setup.py for its next release. npm packages have no hope.
  I've had to change chown invocations far too many times. Please don't hate me.

- “This isn't a technical critique; more of an aesthetic one that you probably
  shouldn't listen to. It would be slightly amusing to add firefox as an
  optdepends to firefox-* (-:”:

  firefox was removed as a dep for these to make it easier for people to use
  them with Palemoon and such.

- Go package LDFLAGS:

  Will take care of this.

- “hangups: "sed -i 's/==/>=/g' setup.py" -- why? Also, has that change been
  submitted upstream? It's minor, but if it fixes something it's probably
  worthwhile”:

  Has to be done for pinned outdated dependencies.

- “razercfg: have you submitted that tmpfile.conf upstream? Also, re: the
  install file, I'm pretty sure that ldconfig happens automagically, and
  systemd-udev-reload.hook should handle reloading udev rules”:

  Will take care of this.

- “shaderc: there were a lot of patches in prepare(), which I can say from
  experience probably won't go over super well. I'm guessing these probably are
  waiting on acceptance or something?”:

  See 
  and .

- “no need for install -m755; -m755 is the default”:

  Taking care of this.



Some notes of my own that could be added to the guidelines:

- My Rust packages use published crates if available, eg.: 
  

Re: [aur-general] On TU application, TU participation and community/ package quality

[Jakob Gruber via aur-general]

On Sun, Nov 11, 2018 at 11:10 PM Sébastien Luttringer via aur-general <
aur-general@archlinux.org> wrote:

> On Sun, 2018-11-11 at 13:29 -0500, Santiago Torres-Arias via aur-general
> wrote:
> > ## Issues
> > * Existing Trusted Users are not followed closely in their actions, and
> the
> > quality of some packages for instance is more than questionable.
> Do you have several example to show?
> > * New applications are not carefully reviewed, and a several TUs seem
> > to  just vote “Yes” by default.
> From which facts are this assumption is built from?
> > * There is a general feeling of decreasing/not high enough quality in
> the
> > packages provided in the community/ repository.
> Idem. What elements do you have to support this feeling ?
> > * The implication of some TUs in the distribution is very limited
> outside of
> > packaging.
> What's wrong with that?


+1 to all of this. Some contribute more, others less, and in different
ways. My impression has always been that this is totally fine as long as
quality doesn't suffer. Not all TUs need to have hundreds of packages and
IRC / forum presence.

Found a bad or outdated package? Prepare a new PKGBUILD and send a quick
mail to the owner.

Think someone shouldn't be a TU? There are processes in place for that.

Votes have an 'abstain' option. That should be the logical vote if one does
not have a strong opinion / enough information.

IMHO there's really no need for governance structures.

Re: [aur-general] TU application: Maxim Baz

[Morten Linderud via aur-general]

Yo!

The discussion period is over and the voting has begun!

Great review session everyone, and I hope we can see more things like that in
the future :)

https://aur.archlinux.org/tu/?id=113

-- 
Morten Linderud
PGP: 9C02FF419FECBE16


signature.asc
Description: PGP signature