-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Hi Everyone,
My name is Dustin Falgout (aka lots0logs) and this is my application to join the Arch Linux project as a Trusted User.
About Me:
I'm 29 years old. I live on the Gulf Coast (USA). I work for a leading WordPress Theme Company where I do a little bit of everything: from sales, to development, to quality assurance, to tech support (you name it...). My first experience with linux was with Ubuntu in 2003. It wasn't until around 2008 that I began using linux exclusively on my desktops. Wanting more control than comes easily with Ubuntu, I first turned to openSUSE and was content for a while. In early 2013, I performed my first Arch linux installation and have been using it ever since.
- From the start I loved almost everything about Arch. The one thing I didn't love was the attitudes towards new users that was so common in the forum. I certainly understand all sides of what is a complex issue and I'm not trying to open that can of worms here. I'm only mentioning it because when I first became an Arch user I found the overall tone of the forum to be extremely off-putting, so much so that I can pinpoint it as the sole reason I shied away from trying to become an active contributor back then. Also, it will help everyone to know where my head was at when I tell you the rest of my story.
I stumbled upon Antergos in May 2013 and I immediately knew that I had found my home. The project's goals and the views of its developers aligned perfectly with my own. For me, Antergos was (and still is) the perfect solution as it has allowed me to contribute (albeit indirectly) to the advancement of what I truly believe to be the best linux distribution available. I know that's a rather broad statement, but I'm trying to keep this short and to the point. If anyone would like me to elaborate on something more specifically, I'd be happy to do so.
I currently maintain six or seven PKGBUILDS in the AUR, of which three are notable: pycharm-eap[1], lightdm-webkit2-greeter[2], and lightdm-webkit-theme-antergos[3]. I've indirectly contributed to other packages in the AUR through comments by offering advice to users, notifying maintainers of new releases as well as any problems with PKGBUILDS (always including a proposed solution), and directing bug reports away from AUR comments and to their proper channel. I always take the time to properly request deletion of PKGBUILDS that shouldnt be in the AUR (for whatever reason) whenever I come across one. I've also reported (and still do report) bugs on http://bugs.archlinux.org when it was/is appropriate. On one or two occasions I've gone as far as reaching out directly to maintainers of official packages to provide them with important information.
Its's also worth mentioning that I currently maintain many packages[4] for Antergos and I'm open to moving any (that are appropriate) to community.
So you might be wondering: "Why become a TU now?". Well, the reason is pretty simple. I was asked to consider applying by Alex Filgueira, the TU who currently maintains the Cinnamon packages and a person with whom I've had the pleasure of collaborating with on Antergos for the past three years. Sadly, his schedule has become far too busy to continue to maintain the Cinnamon packages. Another TU, György Balló, has been picking up the slack for the past few months but, having more than a few packages of his own to maintain, he told Alex that it would be nice to have some help with Cinnamon. Considering that Cinnamon is my own personal desktop of choice, Alex thought I would want to consider joining forces with György to maintain Cinnamon. Obviously, Alex was correct and so here we are. That's my story :)
I know that every minute of your free time is priceless, so thank you all in advance for taking the time review and consider my application. I look forward to (hopefully) "making things official" between myself and Arch Linux.
[1] https://aur.archlinux.org/packages/pycharm-eap/ [2] https://aur.archlinux.org/packages/lightdm-webkit2-greeter/ [3] https://aur.archlinux.org/packages/lightdm-webkit-theme-antergos/ [4] http://build.antergos.com/browse/main
Best Regards,
Dustin Falgout Web Developer
E-mail: dustin@falgout.us Google/Skype: dustinfalgout Freenode IRC: #antergos
On 2016-02-28 22:02, Dustin Falgout wrote:
Hi Everyone,
My name is Dustin Falgout (aka lots0logs) and this is my application to join the Arch Linux project as a Trusted User.
About Me:
I'm 29 years old. I live on the Gulf Coast (USA). I work for a leading WordPress Theme Company where I do a little bit of everything: from sales, to development, to quality assurance, to tech support (you name it...). My first experience with linux was with Ubuntu in 2003. It wasn't until around 2008 that I began using linux exclusively on my desktops. Wanting more control than comes easily with Ubuntu, I first turned to openSUSE and was content for a while. In early 2013, I performed my first Arch linux installation and have been using it ever since.
- From the start I loved almost everything about Arch. The one thing I didn't love was the attitudes towards new users that was so common in the forum. I certainly understand all sides of what is a complex issue and I'm not trying to open that can of worms here. I'm only mentioning it because when I first became an Arch user I found the overall tone of the forum to be extremely off-putting, so much so that I can pinpoint it as the sole reason I shied away from trying to become an active contributor back then. Also, it will help everyone to know where my head was at when I tell you the rest of my story.
I stumbled upon Antergos in May 2013 and I immediately knew that I had found my home. The project's goals and the views of its developers aligned perfectly with my own. For me, Antergos was (and still is) the perfect solution as it has allowed me to contribute (albeit indirectly) to the advancement of what I truly believe to be the best linux distribution available. I know that's a rather broad statement, but I'm trying to keep this short and to the point. If anyone would like me to elaborate on something more specifically, I'd be happy to do so.
I currently maintain six or seven PKGBUILDS in the AUR, of which three are notable: pycharm-eap[1], lightdm-webkit2-greeter[2], and lightdm-webkit-theme-antergos[3]. I've indirectly contributed to other packages in the AUR through comments by offering advice to users, notifying maintainers of new releases as well as any problems with PKGBUILDS (always including a proposed solution), and directing bug reports away from AUR comments and to their proper channel. I always take the time to properly request deletion of PKGBUILDS that shouldnt be in the AUR (for whatever reason) whenever I come across one. I've also reported (and still do report) bugs on http://bugs.archlinux.org when it was/is appropriate. On one or two occasions I've gone as far as reaching out directly to maintainers of official packages to provide them with important information.
Its's also worth mentioning that I currently maintain many packages[4] for Antergos and I'm open to moving any (that are appropriate) to community.
So you might be wondering: "Why become a TU now?". Well, the reason is pretty simple. I was asked to consider applying by Alex Filgueira, the TU who currently maintains the Cinnamon packages and a person with whom I've had the pleasure of collaborating with on Antergos for the past three years. Sadly, his schedule has become far too busy to continue to maintain the Cinnamon packages. Another TU, György Balló, has been picking up the slack for the past few months but, having more than a few packages of his own to maintain, he told Alex that it would be nice to have some help with Cinnamon. Considering that Cinnamon is my own personal desktop of choice, Alex thought I would want to consider joining forces with György to maintain Cinnamon. Obviously, Alex was correct and so here we are. That's my story :)
I know that every minute of your free time is priceless, so thank you all in advance for taking the time review and consider my application. I look forward to (hopefully) "making things official" between myself and Arch Linux.
[1] https://aur.archlinux.org/packages/pycharm-eap/ [2] https://aur.archlinux.org/packages/lightdm-webkit2-greeter/ [3] https://aur.archlinux.org/packages/lightdm-webkit-theme-antergos/ [4] http://build.antergos.com/browse/main
Best Regards,
Dustin Falgout Web Developer
E-mail: dustin@falgout.us Google/Skype: dustinfalgout Freenode IRC: #antergos
Hi Dustin,
To begin with, could Alex reply to your application to confirm it?
How exactly are you going to contribute to Arch, except maintaining Cinnamon? Packages from AUR you mentioned aren't really notable (and in fact, one just repackages proprietary tarball) and these in Antergos repositories also seem rather unpopular. Looks like some of them can't be even distributed at all unless JetBrains license allows that; as far as I know, distribution of ZFS binaries is a GPL violation.
Cheers, Bartłomiej
On Tue, Mar 1, 2016 at 2:33 PM, Bartłomiej Piotrowski bpiotrowski@archlinux.org wrote:
How exactly are you going to contribute to Arch, except maintaining Cinnamon? Packages from AUR you mentioned aren't really notable (and in fact, one just repackages proprietary tarball) and these in Antergos repositories also seem rather unpopular. Looks like some of them can't be even distributed at all unless JetBrains license allows that; as far as I know, distribution of ZFS binaries is a GPL violation.
FWIW, the zfs package in Antergos is a source distribution using DKMS to build. Also, (antergos-)gnome-defaults-list, assuming it's solid, is something the Arch GNOME distribution is in need of. Would be interesting to get in contact with whoever made that.
More on topic, if Cinnamon desperately needs maintainers, I'd welcome Dustin.
To: aur-general@archlinux.org> From: bpiotrowski@archlinux.org Date: Tue, 1 Mar 2016 14:33:18 +0100 Subject: Re: [aur-general] TU Application - Dustin Falgout
On 2016-02-28 22:02, Dustin Falgout wrote:
Hi Everyone,
My name is Dustin Falgout (aka lots0logs) and this is my application to join the Arch Linux project as a Trusted User.
About Me:
I'm 29 years old. I live on the Gulf Coast (USA). I work for a leading WordPress Theme Company where I do a little bit of everything: from sales, to development, to quality assurance, to tech support (you name it...). My first experience with linux was with Ubuntu in 2003. It wasn't until around 2008 that I began using linux exclusively on my desktops. Wanting more control than comes easily with Ubuntu, I first turned to openSUSE and was content for a while. In early 2013, I performed my first Arch linux installation and have been using it ever since.
- From the start I loved almost everything about Arch. The one thing I didn't love was the attitudes towards new users that was so common in the forum. I certainly understand all sides of what is a complex issue and I'm not trying to open that can of worms here. I'm only mentioning it because when I first became an Arch user I found the overall tone of the forum to be extremely off-putting, so much so that I can pinpoint it as the sole reason I shied away from trying to become an active contributor back then. Also, it will help everyone to know where my head was at when I tell you the rest of my story.
I stumbled upon Antergos in May 2013 and I immediately knew that I had found my home. The project's goals and the views of its developers aligned perfectly with my own. For me, Antergos was (and still is) the perfect solution as it has allowed me to contribute (albeit indirectly) to the advancement of what I truly believe to be the best linux distribution available. I know that's a rather broad statement, but I'm trying to keep this short and to the point. If anyone would like me to elaborate on something more specifically, I'd be happy to do so.
I currently maintain six or seven PKGBUILDS in the AUR, of which three are notable: pycharm-eap[1], lightdm-webkit2-greeter[2], and lightdm-webkit-theme-antergos[3]. I've indirectly contributed to other packages in the AUR through comments by offering advice to users, notifying maintainers of new releases as well as any problems with PKGBUILDS (always including a proposed solution), and directing bug reports away from AUR comments and to their proper channel. I always take the time to properly request deletion of PKGBUILDS that shouldnt be in the AUR (for whatever reason) whenever I come across one. I've also reported (and still do report) bugs on http://bugs.archlinux.org when it was/is appropriate. On one or two occasions I've gone as far as reaching out directly to maintainers of official packages to provide them with important information.
Its's also worth mentioning that I currently maintain many packages[4] for Antergos and I'm open to moving any (that are appropriate) to community.
So you might be wondering: "Why become a TU now?". Well, the reason is pretty simple. I was asked to consider applying by Alex Filgueira, the TU who currently maintains the Cinnamon packages and a person with whom I've had the pleasure of collaborating with on Antergos for the past three years. Sadly, his schedule has become far too busy to continue to maintain the Cinnamon packages. Another TU, György Balló, has been picking up the slack for the past few months but, having more than a few packages of his own to maintain, he told Alex that it would be nice to have some help with Cinnamon. Considering that Cinnamon is my own personal desktop of choice, Alex thought I would want to consider joining forces with György to maintain Cinnamon. Obviously, Alex was correct and so here we are. That's my story :)
I know that every minute of your free time is priceless, so thank you all in advance for taking the time review and consider my application. I look forward to (hopefully) "making things official" between myself and Arch Linux.
[1] https://aur.archlinux.org/packages/pycharm-eap/ [2] https://aur.archlinux.org/packages/lightdm-webkit2-greeter/ [3] https://aur.archlinux.org/packages/lightdm-webkit-theme-antergos/ [4] http://build.antergos.com/browse/main
Best Regards,
Dustin Falgout Web Developer
E-mail: dustin@falgout.us Google/Skype: dustinfalgout Freenode IRC: #antergos
Hi Dustin,
To begin with, could Alex reply to your application to confirm it?
How exactly are you going to contribute to Arch, except maintaining Cinnamon? Packages from AUR you mentioned aren't really notable (and in fact, one just repackages proprietary tarball) and these in Antergos repositories also seem rather unpopular. Looks like some of them can't be even distributed at all unless JetBrains license allows that; as far as I know, distribution of ZFS binaries is a GPL violation.
Cheers, Bartłomiej
Hi Bartłomiej, TBH, I'm not able to commit to much more than Cinnamon right now. You are right about my AUR packages, but IMO, its best to maintain packages that you actually use regularly. Everything I use for my workflow is available either in the official repos or in the AUR. Of course that's subject to change as time goes on and my workflow evolves. If the opportunity to maintain a more notable package presents itself, of course I'd be glad to do it. Also, its worth mentioning that I'll be continuing my work on Antergos as I firmly believe that it is beneficial to Arch. Best Regards,-- Dustin FalgoutWeb Developer E-mail: dustin@falgout.us
2016-02-28 16:02 GMT-05:00 Dustin Falgout dustin@falgout.us:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Hi Everyone,
My name is Dustin Falgout (aka lots0logs) and this is my application to join the Arch Linux project as a Trusted User.
About Me:
I'm 29 years old. I live on the Gulf Coast (USA). I work for a leading WordPress Theme Company where I do a little bit of everything: from sales, to development, to quality assurance, to tech support (you name it...). My first experience with linux was with Ubuntu in 2003. It wasn't until around 2008 that I began using linux exclusively on my desktops. Wanting more control than comes easily with Ubuntu, I first turned to openSUSE and was content for a while. In early 2013, I performed my first Arch linux installation and have been using it ever since.
- From the start I loved almost everything about Arch. The one thing I
didn't love was the attitudes towards new users that was so common in the forum. I certainly understand all sides of what is a complex issue and I'm not trying to open that can of worms here. I'm only mentioning it because when I first became an Arch user I found the overall tone of the forum to be extremely off-putting, so much so that I can pinpoint it as the sole reason I shied away from trying to become an active contributor back then. Also, it will help everyone to know where my head was at when I tell you the rest of my story.
I stumbled upon Antergos in May 2013 and I immediately knew that I had found my home. The project's goals and the views of its developers aligned perfectly with my own. For me, Antergos was (and still is) the perfect solution as it has allowed me to contribute (albeit indirectly) to the advancement of what I truly believe to be the best linux distribution available. I know that's a rather broad statement, but I'm trying to keep this short and to the point. If anyone would like me to elaborate on something more specifically, I'd be happy to do so.
I currently maintain six or seven PKGBUILDS in the AUR, of which three are notable: pycharm-eap[1], lightdm-webkit2-greeter[2], and lightdm-webkit-theme-antergos[3]. I've indirectly contributed to other packages in the AUR through comments by offering advice to users, notifying maintainers of new releases as well as any problems with PKGBUILDS (always including a proposed solution), and directing bug reports away from AUR comments and to their proper channel. I always take the time to properly request deletion of PKGBUILDS that shouldnt be in the AUR (for whatever reason) whenever I come across one. I've also reported (and still do report) bugs on http://bugs.archlinux.org when it was/is appropriate. On one or two occasions I've gone as far as reaching out directly to maintainers of official packages to provide them with important information.
Its's also worth mentioning that I currently maintain many packages[4] for Antergos and I'm open to moving any (that are appropriate) to community.
So you might be wondering: "Why become a TU now?". Well, the reason is pretty simple. I was asked to consider applying by Alex Filgueira, the TU who currently maintains the Cinnamon packages and a person with whom I've had the pleasure of collaborating with on Antergos for the past three years. Sadly, his schedule has become far too busy to continue to maintain the Cinnamon packages. Another TU, György Balló, has been picking up the slack for the past few months but, having more than a few packages of his own to maintain, he told Alex that it would be nice to have some help with Cinnamon. Considering that Cinnamon is my own personal desktop of choice, Alex thought I would want to consider joining forces with György to maintain Cinnamon. Obviously, Alex was correct and so here we are. That's my story :)
I know that every minute of your free time is priceless, so thank you all in advance for taking the time review and consider my application. I look forward to (hopefully) "making things official" between myself and Arch Linux.
[1] https://aur.archlinux.org/packages/pycharm-eap/ [2] https://aur.archlinux.org/packages/lightdm-webkit2-greeter/ [3] https://aur.archlinux.org/packages/lightdm-webkit-theme-antergos/ [4] http://build.antergos.com/browse/main
Best Regards,
Dustin Falgout Web Developer
E-mail: dustin@falgout.us Google/Skype: dustinfalgout Freenode IRC: #antergos -----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQEcBAEBCAAGBQJW02A1AAoJEK6lKb8SKQLlb6EH/2bE+uzlWsuU3kIouB8sEGwr qzGmBT3JntkZsOrsy1fYl7kNz2GAlc2/+8MCJ9LUinkv46Egiw93lW8C58G8eudQ LOJ1GTz7hh5suO+xOagXdmTJwJMK04VPtHksTeNg3mVONmJPNxSlDdRk77sTHZMd 95aAnvnPBkk1U6Zn4hr6pPUG6HvPGmMseDdmBLr62Fh5CgupsEli4Q2vmgTlZwr6 CoJo9LEaS20djXihDgXYY/6TDEeKeyzj7I9M33IP6eppoACEzsueXxInD5aBPyvD HgcqvC7UNnpha8k2LBbL5xyTOUiDyhwwpf8umLHWPLCA6OmK9se3aYiY2FaUd8A= =8/xf -----END PGP SIGNATURE-----
Hi
I confirm the sponsorship of Dustin Falgout.
So, now the 5 day discussion period begins.
Cheers
On 02/28/2016 10:02 PM, Dustin Falgout wrote:
I currently maintain six or seven PKGBUILDS in the AUR, of which three are notable: pycharm-eap[1], lightdm-webkit2-greeter[2], and lightdm-webkit-theme-antergos[3]. I've indirectly contributed to other packages in the AUR through comments by offering advice to users, notifying maintainers of new releases as well as any problems with PKGBUILDS (always including a proposed solution), and directing bug reports away from AUR comments and to their proper channel. I always take the time to properly request deletion of PKGBUILDS that shouldnt be in the AUR (for whatever reason) whenever I come across one. I've also reported (and still do report) bugs on http://bugs.archlinux.org when it was/is appropriate. On one or two occasions I've gone as far as reaching out directly to maintainers of official packages to provide them with important information.
Hi Dustin
I went through your packages and had a rough look at the PKGBUILDS... don't be scared but i wanted to dump my feedback and some personal opinions about those:
lightdm-webkit-theme-antergos: - just my 2 cents but post_install() should not sed around in your lightdm.conf as you can also install multiple theme packages
lightdm-webkit-theme-userdock: - just my 2 cents but post_install() should not be used for explaining documentation/setup
lightdm-webkit2-greeter: - you can use #tag=2.0.0 instead of doing a checkout in build() - reference to $pkgdir should always be quoted (make call) - should not sed the lightdm.conf in post_install() as you can possibly install multiple greeters
obs-service-recompress: - this package actually pulls the git HEAD and should either be renamed to obs-service-recompress-git or pull the 0.3.1 tarball and have the pkgver() removed. - reference to $pkgdir should always be quoted (make call)
obs-service-set_version: - same as obs-service-recompress, pulls git HEAD with pkgver() function instead of 0.5.3 tarball - reference to $pkgdir should always be quoted (make call)
obs-service-tar_scm: - same as obs-service-recompress, pulls git HEAD with pkgver() function instead of 0.5.3 tarball - reference to $pkgdir should always be quoted (make call)
pycharm-eap: - not sure what the _eap="True" variable and the if does there as its the -eap package, guess it can just be dropped (including the else) - just my 2 cents but using groups with "development" "IDE" "editor" and "jetbrains" feels a bit too much, groups should logically group together similarities like "vim-plugins" and not used like generic keywords
cheers, Levente
PS: instead of inline PGP you may want to have a look at PGP/MIME... besides weird text in clients that don't support PGP it can also result in breakage in various scenarios where the text gets altered by MTA/MUA
On 01/03, Levente Polyak wrote:
pycharm-eap:
...
- just my 2 cents but using groups with "development" "IDE" "editor"
and "jetbrains" feels a bit too much, groups should logically group together similarities like "vim-plugins" and not used like generic keywords
Not just similarities, things that you might want to actually install the whole group of, like base and base-devel & co. Not to mention the fact that groups are pretty useless in the AUR either way.
On 01/03/16 21:23, Johannes Löthberg wrote:
(...snip...) Not to mention the fact that groups are pretty useless in the AUR either way.
Well, they can be useful if you maintain a binary repo as well. I don't argue however with the other point that was made (and not quoted here).
Cheers, Luchesar
On 03/01/2016 02:23 PM, Johannes Löthberg wrote:
Not just similarities, things that you might want to actually install the whole group of, like base and base-devel & co. Not to mention the fact that groups are pretty useless in the AUR either way.
Groups aren't entirely useless in the AUR. Once they are installed, you can remove the whole group at once too.
Or make a custom repository out of them.
To: aur-general@archlinux.org> From: anthraxx@archlinux.org Date: Tue, 1 Mar 2016 17:12:04 +0100 Subject: Re: [aur-general] TU Application - Dustin Falgout
On 02/28/2016 10:02 PM, Dustin Falgout wrote:
I currently maintain six or seven PKGBUILDS in the AUR, of which three are notable: pycharm-eap[1], lightdm-webkit2-greeter[2], and lightdm-webkit-theme-antergos[3]. I've indirectly contributed to other packages in the AUR through comments by offering advice to users, notifying maintainers of new releases as well as any problems with PKGBUILDS (always including a proposed solution), and directing bug reports away from AUR comments and to their proper channel. I always take the time to properly request deletion of PKGBUILDS that shouldnt be in the AUR (for whatever reason) whenever I come across one. I've also reported (and still do report) bugs on http://bugs.archlinux.org when it was/is appropriate. On one or two occasions I've gone as far as reaching out directly to maintainers of official packages to provide them with important information.
Hi Dustin
I went through your packages and had a rough look at the PKGBUILDS... don't be scared but i wanted to dump my feedback and some personal opinions about those:
lightdm-webkit-theme-antergos:
- just my 2 cents but post_install() should not sed around in your lightdm.conf as you can also install multiple theme packages
lightdm-webkit-theme-userdock:
- just my 2 cents but post_install() should not be used for explaining documentation/setup
lightdm-webkit2-greeter:
- you can use #tag=2.0.0 instead of doing a checkout in build()
- reference to $pkgdir should always be quoted (make call)
- should not sed the lightdm.conf in post_install() as you can possibly install multiple greeters
obs-service-recompress:
- this package actually pulls the git HEAD and should either be renamed to obs-service-recompress-git or pull the 0.3.1 tarball and have the pkgver() removed.
- reference to $pkgdir should always be quoted (make call)
obs-service-set_version:
- same as obs-service-recompress, pulls git HEAD with pkgver() function instead of 0.5.3 tarball
- reference to $pkgdir should always be quoted (make call)
obs-service-tar_scm:
- same as obs-service-recompress, pulls git HEAD with pkgver() function instead of 0.5.3 tarball
- reference to $pkgdir should always be quoted (make call)
pycharm-eap:
- not sure what the _eap="True" variable and the if does there as its the -eap package, guess it can just be dropped (including the else)
- just my 2 cents but using groups with "development" "IDE" "editor" and "jetbrains" feels a bit too much, groups should logically group together similarities like "vim-plugins" and not used like generic keywords
cheers, Levente
PS: instead of inline PGP you may want to have a look at PGP/MIME... besides weird text in clients that don't support PGP it can also result in breakage in various scenarios where the text gets altered by MTA/MUA
Hi Levente, I've implemented your feedback where it was appropriate. Thanks :) I'm not familiar with PGP/MIME. I've heard of it, but I have no clue how to go about using it. I'll definitely look into it so thanks for the tip! Best Regards,Dustin
On 03/02/2016 04:16 AM, Dustin Falgout wrote:
To: aur-general@archlinux.org> From: anthraxx@archlinux.org Date: Tue, 1 Mar 2016 17:12:04 +0100 Subject: Re: [aur-general] TU Application - Dustin Falgout
On 02/28/2016 10:02 PM, Dustin Falgout wrote:
I currently maintain six or seven PKGBUILDS in the AUR, of which three are notable: pycharm-eap[1], lightdm-webkit2-greeter[2], and lightdm-webkit-theme-antergos[3]. I've indirectly contributed to other packages in the AUR through comments by offering advice to users, notifying maintainers of new releases as well as any problems with PKGBUILDS (always including a proposed solution), and directing bug reports away from AUR comments and to their proper channel. I always take the time to properly request deletion of PKGBUILDS that shouldnt be in the AUR (for whatever reason) whenever I come across one. I've also reported (and still do report) bugs on http://bugs.archlinux.org when it was/is appropriate. On one or two occasions I've gone as far as reaching out directly to maintainers of official packages to provide them with important information.
Hi Dustin
I went through your packages and had a rough look at the PKGBUILDS... don't be scared but i wanted to dump my feedback and some personal opinions about those:
lightdm-webkit-theme-antergos:
- just my 2 cents but post_install() should not sed around in your lightdm.conf as you can also install multiple theme packages
lightdm-webkit-theme-userdock:
- just my 2 cents but post_install() should not be used for explaining documentation/setup
lightdm-webkit2-greeter:
- you can use #tag=2.0.0 instead of doing a checkout in build()
- reference to $pkgdir should always be quoted (make call)
- should not sed the lightdm.conf in post_install() as you can possibly install multiple greeters
obs-service-recompress:
- this package actually pulls the git HEAD and should either be renamed to obs-service-recompress-git or pull the 0.3.1 tarball and have the pkgver() removed.
- reference to $pkgdir should always be quoted (make call)
obs-service-set_version:
- same as obs-service-recompress, pulls git HEAD with pkgver() function instead of 0.5.3 tarball
- reference to $pkgdir should always be quoted (make call)
obs-service-tar_scm:
- same as obs-service-recompress, pulls git HEAD with pkgver() function instead of 0.5.3 tarball
- reference to $pkgdir should always be quoted (make call)
pycharm-eap:
- not sure what the _eap="True" variable and the if does there as its the -eap package, guess it can just be dropped (including the else)
- just my 2 cents but using groups with "development" "IDE" "editor" and "jetbrains" feels a bit too much, groups should logically group together similarities like "vim-plugins" and not used like generic keywords
cheers, Levente
PS: instead of inline PGP you may want to have a look at PGP/MIME... besides weird text in clients that don't support PGP it can also result in breakage in various scenarios where the text gets altered by MTA/MUA
Hi Levente, I've implemented your feedback where it was appropriate. Thanks :) I'm not familiar with PGP/MIME. I've heard of it, but I have no clue how to go about using it. I'll definitely look into it so thanks for the tip! Best Regards,Dustin
Hey Dustin,
That was fast, but I think you accidentally forgot to implement the most important part of my feedback: It is not allowed to have no pkgname VCS postfix (like -git) but pull from a git HEAD. You either have to rename those packages or pull a static source like github or upstream tarballs. In case of github tarballs remember to use the source filename prefix to make them unique (like lightdm-webkit-theme-userdock).
cheers, Levente
On Wed, Mar 2, 2016 at 11:40 AM, Levente Polyak anthraxx@archlinux.org wrote:
That was fast, but I think you accidentally forgot to implement the most important part of my feedback: It is not allowed to have no pkgname VCS postfix (like -git) but pull from a git HEAD. You either have to rename those packages or pull a static source like github or upstream tarballs. In case of github tarballs remember to use the source filename prefix to make them unique (like lightdm-webkit-theme-userdock).
The simplest way to make these "static" if you want to import them into [community] is to pin the git source using #commit=1234567.
On 03/02/2016 11:56 AM, Jan Alexander Steffens wrote:
On Wed, Mar 2, 2016 at 11:40 AM, Levente Polyak anthraxx@archlinux.org wrote:
That was fast, but I think you accidentally forgot to implement the most important part of my feedback: It is not allowed to have no pkgname VCS postfix (like -git) but pull from a git HEAD. You either have to rename those packages or pull a static source like github or upstream tarballs. In case of github tarballs remember to use the source filename prefix to make them unique (like lightdm-webkit-theme-userdock).
The simplest way to make these "static" if you want to import them into [community] is to pin the git source using #commit=1234567.
Also in that case, only if you have a sane reason to not stick to the upstream released versions. If there is no real reason one should follow the upstream released version so the commit hash should not be arbitrary but the one of the release. In general we want to follow upstream releases.
cheers, Levente
To: aur-general@archlinux.org> From: anthraxx@archlinux.org Date: Wed, 2 Mar 2016 12:28:58 +0100 Subject: Re: [aur-general] TU Application - Dustin Falgout
On 03/02/2016 11:56 AM, Jan Alexander Steffens wrote:
On Wed, Mar 2, 2016 at 11:40 AM, Levente Polyak anthraxx@archlinux.org wrote:
That was fast, but I think you accidentally forgot to implement the most important part of my feedback: It is not allowed to have no pkgname VCS postfix (like -git) but pull from a git HEAD. You either have to rename those packages or pull a static source like github or upstream tarballs. In case of github tarballs remember to use the source filename prefix to make them unique (like lightdm-webkit-theme-userdock).
The simplest way to make these "static" if you want to import them into [community] is to pin the git source using #commit=1234567.
Also in that case, only if you have a sane reason to not stick to the upstream released versions. If there is no real reason one should follow the upstream released version so the commit hash should not be arbitrary but the one of the release. In general we want to follow upstream releases.
cheers, Levente
Hi Levente, I do have a sane reason indeed. Upstream is not following their github releases. If you look in openSUSE's package repo you will see that they are packaging the latest master as the most recently released version. Looking at the history of those packages it seems that whoever is maintaining the packages over at openSUSE does not use github releases in their release process on a regular basis. Considering that, it doesnt make sense to tag the end of the pkgname with "-git". If you are wondering why I didn't use the short version of the commit hash at the end of the pkgver, well that's simply a personal preference of mine (to use revision numbers instead). I hope that helps clear up any confusion as to why I chose to do it the way that I did. Cheers!Dustin
2016-03-02 20:21 GMT+01:00 Dustin Falgout dustin@falgout.us:
If you are wondering why I didn't use the short version of the commit hash at the end of the pkgver, well that's simply a personal preference of mine (to use revision numbers instead). I hope that helps clear up any confusion as to why I chose to do it the way that I did.
If you don't specify tag or commit hash at the end of the git source, then you should use the -git suffix. Users expect if the package has no -git suffix, then it's a working static version tested by the maintainer, and not some experimental code from git HEAD.
BTW, it would be nice if you could adopt some more orphan packages in the community repository.
-- György Balló Trusted User
On 03/02/2016 09:19 PM, Balló György wrote:
If you don't specify tag or commit hash at the end of the git source, then you should use the -git suffix. Users expect if the package has no -git suffix, then it's a working static version tested by the maintainer, and not some experimental code from git HEAD.
Its not just a should but a guideline rule [0] that must be followed upon. For official repositories it is mandatory and will also be enforced because of multiple reasons: the most obvious ones are rebuilds on sobumps and reproducible packages (not yet there but a topic that is being worked on). The only difference is that (besides that the AUR is unsupported) on the AUR people may not notice it or care enough to enforce that. However, in my personal opinion, a trusted user should do things above the general average, that's IMHO why someone should be _trusted_.
On 03/02/2016 08:21 PM, Dustin Falgout wrote:
I do have a sane reason indeed. Upstream is not following their github releases. If you look in openSUSE's package repo you will see >
that they are packaging the latest master as the most recently
released version. Looking at the history of those packages it seems that whoever is maintaining the packages over at openSUSE does not use github releases in their release process on a regular basis.
It applies for just one out of 3 packages, you should fully check your claim before using it as an argument. Also 2/3 of those packages are not something that could be considered "not released on regular basis"
obs-service-set_version: - last release: Sep 3, 2015 - patch commits since release: 4 - openSUSE version [1]: 0.5.3 release
obs-service-tar_scm: - last release: Jun 1, 2015 - patch commits since release: 9 - openSUSE version [2]: 0.5.3 0b4ce51 (2 patch commits since release)
obs-service-recompress: - last release: Nov 5, 2013 - patch commits since release: 7 - openSUSE version [3]: 7897d3f (7 patch commits since release)
Actually, as mentioned above, its just the recompress packages that really falls out of scope. The tar_scm is just a debian control file fix and a missing extension parameter to service file. I don't see any point why the release is not sufficient for those. Also did you try to contact upstream about a recompress release?
On 03/02/2016 08:21 PM, Dustin Falgout wrote:
Considering that, it doesnt make sense to tag the end of the pkgname >
with "-git"
As mentioned in my very first section, this part is not something that can be argued upon [0], there are just two sane possibilities: 1) use a static version and have the pure package name 2) use non-static VCS (like git HEAD) and add such postfix to pkgname
cheers, Levente
[0] https://wiki.archlinux.org/index.php/VCS_package_guidelines#Guidelines [1] https://build.opensuse.org/package/show/openSUSE:Tools/obs-service-set_versi... [2] https://build.opensuse.org/package/show/openSUSE:Tools/obs-service-tar_scm [3] https://build.opensuse.org/package/show/openSUSE:Tools/obs-service-recompres...
To: aur-general@archlinux.org> From: anthraxx@archlinux.org Date: Wed, 2 Mar 2016 22:48:27 +0100 Subject: Re: [aur-general] TU Application - Dustin Falgout
On 03/02/2016 09:19 PM, Balló György wrote:
If you don't specify tag or commit hash at the end of the git source, then you should use the -git suffix. Users expect if the package has no -git suffix, then it's a working static version tested by the maintainer, and not some experimental code from git HEAD.
Its not just a should but a guideline rule [0] that must be followed upon. For official repositories it is mandatory and will also be enforced because of multiple reasons: the most obvious ones are rebuilds on sobumps and reproducible packages (not yet there but a topic that is being worked on). The only difference is that (besides that the AUR is unsupported) on the AUR people may not notice it or care enough to enforce that. However, in my personal opinion, a trusted user should do things above the general average, that's IMHO why someone should be _trusted_.
On 03/02/2016 08:21 PM, Dustin Falgout wrote:
I do have a sane reason indeed. Upstream is not following their github releases. If you look in openSUSE's package repo you will see >
that they are packaging the latest master as the most recently
released version. Looking at the history of those packages it seems that whoever is maintaining the packages over at openSUSE does not use github releases in their release process on a regular basis.
It applies for just one out of 3 packages, you should fully check your claim before using it as an argument. Also 2/3 of those packages are not something that could be considered "not released on regular basis"
obs-service-set_version:
- last release: Sep 3, 2015
- patch commits since release: 4
- openSUSE version [1]: 0.5.3 release
obs-service-tar_scm:
- last release: Jun 1, 2015
- patch commits since release: 9
- openSUSE version [2]: 0.5.3 0b4ce51 (2 patch commits since release)
obs-service-recompress:
- last release: Nov 5, 2013
- patch commits since release: 7
- openSUSE version [3]: 7897d3f (7 patch commits since release)
Actually, as mentioned above, its just the recompress packages that really falls out of scope. The tar_scm is just a debian control file fix and a missing extension parameter to service file. I don't see any point why the release is not sufficient for those. Also did you try to contact upstream about a recompress release?
On 03/02/2016 08:21 PM, Dustin Falgout wrote:
Considering that, it doesnt make sense to tag the end of the pkgname >
with "-git"
As mentioned in my very first section, this part is not something that can be argued upon [0], there are just two sane possibilities:
- use a static version and have the pure package name
- use non-static VCS (like git HEAD) and add such postfix to pkgname
cheers, Levente
[0] https://wiki.archlinux.org/index.php/VCS_package_guidelines#Guidelines [1] https://build.opensuse.org/package/show/openSUSE:Tools/obs-service-set_versi... [2] https://build.opensuse.org/package/show/openSUSE:Tools/obs-service-tar_scm [3] https://build.opensuse.org/package/show/openSUSE:Tools/obs-service-recompres...
It applies for just one out of 3 packages, you should fully check your claim before using it as an argument
I'm sorry, I did not realize we were having an argument. You asked me why I did it the way that I did and I explained. If I was planning to move those packages into community or if I thought there was even the remote possibility of my doing so, I would certainly make sure the packages were inline with the repo guidelines. However, that is not the case here. Those three packages are no longer of much use to me at this point. I didn't want to just orphan them considering they weren't requiring much from me in terms of maintenance so I kept them. In any case, I understand what you are saying. I am not now, nor was I ever, saying you are wrong. I should have made been more clear about that, my apologies.
Best Regards,Dustin
On 03/02/2016 11:58 PM, Dustin Falgout wrote:
To: aur-general@archlinux.org> From: anthraxx@archlinux.org Date: Wed, 2 Mar 2016 22:48:27 +0100 Subject: Re: [aur-general] TU Application - Dustin Falgout
On 03/02/2016 09:19 PM, Balló György wrote:
If you don't specify tag or commit hash at the end of the git source, then you should use the -git suffix. Users expect if the package has no -git suffix, then it's a working static version tested by the maintainer, and not some experimental code from git HEAD.
Its not just a should but a guideline rule [0] that must be followed upon. For official repositories it is mandatory and will also be enforced because of multiple reasons: the most obvious ones are rebuilds on sobumps and reproducible packages (not yet there but a topic that is being worked on). The only difference is that (besides that the AUR is unsupported) on the AUR people may not notice it or care enough to enforce that. However, in my personal opinion, a trusted user should do things above the general average, that's IMHO why someone should be _trusted_.
On 03/02/2016 08:21 PM, Dustin Falgout wrote:
I do have a sane reason indeed. Upstream is not following their github releases. If you look in openSUSE's package repo you will see >
that they are packaging the latest master as the most recently
released version. Looking at the history of those packages it seems that whoever is maintaining the packages over at openSUSE does not use github releases in their release process on a regular basis.
It applies for just one out of 3 packages, you should fully check your claim before using it as an argument. Also 2/3 of those packages are not something that could be considered "not released on regular basis"
obs-service-set_version:
- last release: Sep 3, 2015
- patch commits since release: 4
- openSUSE version [1]: 0.5.3 release
obs-service-tar_scm:
- last release: Jun 1, 2015
- patch commits since release: 9
- openSUSE version [2]: 0.5.3 0b4ce51 (2 patch commits since release)
obs-service-recompress:
- last release: Nov 5, 2013
- patch commits since release: 7
- openSUSE version [3]: 7897d3f (7 patch commits since release)
Actually, as mentioned above, its just the recompress packages that really falls out of scope. The tar_scm is just a debian control file fix and a missing extension parameter to service file. I don't see any point why the release is not sufficient for those. Also did you try to contact upstream about a recompress release?
On 03/02/2016 08:21 PM, Dustin Falgout wrote:
Considering that, it doesnt make sense to tag the end of the pkgname >
with "-git"
As mentioned in my very first section, this part is not something that can be argued upon [0], there are just two sane possibilities:
- use a static version and have the pure package name
- use non-static VCS (like git HEAD) and add such postfix to pkgname
cheers, Levente
[0] https://wiki.archlinux.org/index.php/VCS_package_guidelines#Guidelines [1] https://build.opensuse.org/package/show/openSUSE:Tools/obs-service-set_versi... [2] https://build.opensuse.org/package/show/openSUSE:Tools/obs-service-tar_scm [3] https://build.opensuse.org/package/show/openSUSE:Tools/obs-service-recompres...
It applies for just one out of 3 packages, you should fully check your claim before using it as an argument
I'm sorry, I did not realize we were having an argument. You asked me why I did it the way that I did and I explained. If I was planning to move those packages into community or if I thought there was even the remote possibility of my doing so, I would certainly make sure the packages were inline with the repo guidelines. However, that is not the case here. Those three packages are no longer of much use to me at this point. I didn't want to just orphan them considering they weren't requiring much from me in terms of maintenance so I kept them. In any case, I understand what you are saying. I am not now, nor was I ever, saying you are wrong. I should have made been more clear about that, my apologies.
Best Regards,Dustin
Excuse me being a bit late, I was planning to respond before the end of the discussion but was held up from real life things.
I did not intended it just as a question to get an explanation, it was more a dialogue of improving your packages and making you aware of some problems. To be honest I'm still a bit confused and wondering as you implemented the quotes around the $pkgdir to those "abandoned" packages but they still pull the git HEAD and that part was fully ignored (besides acknowledging here that you don't think I'm wrong).
Being inline with general guidelines and having quality in PKGBUILDs shouldn't be something exclusive to the binary repositories but a general belief and ambition. Especially as a TU, quality and ambition to do the best and follow the general belief of the guidelines is something that is desired to be followed everywhere, no difference if AUR, binary repository or other parts of the ecosystem.
Sincerely, Levente
Date: Wed, 2 Mar 2016 21:19:08 +0100> From: ballogyor@gmail.com To: aur-general@archlinux.org Subject: Re: [aur-general] TU Application - Dustin Falgout
2016-03-02 20:21 GMT+01:00 Dustin Falgout dustin@falgout.us:
If you are wondering why I didn't use the short version of the commit hash at the end of the pkgver, well that's simply a personal preference of mine (to use revision numbers instead). I hope that helps clear up any confusion as to why I chose to do it the way that I did.
If you don't specify tag or commit hash at the end of the git source, then you should use the -git suffix. Users expect if the package has no -git suffix, then it's a working static version tested by the maintainer, and not some experimental code from git HEAD.
BTW, it would be nice if you could adopt some more orphan packages in the community repository.
-- György Balló Trusted User
Sure, I could do that. Do you have any particular packages in mind that I should consider first? Best Regards,Dustin
2016-03-02 23:44 GMT+01:00 Dustin Falgout dustin@falgout.us:
Date: Wed, 2 Mar 2016 21:19:08 +0100> From: ballogyor@gmail.com BTW, it would be nice if you could adopt some more orphan packages in the community repository.
Sure, I could do that. Do you have any particular packages in mind that I should consider first? Best Regards,Dustin
We have a lot of orphans, you can choose any of them: https://www.archlinux.org/packages/?repo=Community&maintainer=orphan
-- György Balló Trusted User
2016-02-28 16:02 GMT-05:00 Dustin Falgout dustin@falgout.us:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Hi Everyone,
My name is Dustin Falgout (aka lots0logs) and this is my application to join the Arch Linux project as a Trusted User.
About Me:
I'm 29 years old. I live on the Gulf Coast (USA). I work for a leading WordPress Theme Company where I do a little bit of everything: from sales, to development, to quality assurance, to tech support (you name it...). My first experience with linux was with Ubuntu in 2003. It wasn't until around 2008 that I began using linux exclusively on my desktops. Wanting more control than comes easily with Ubuntu, I first turned to openSUSE and was content for a while. In early 2013, I performed my first Arch linux installation and have been using it ever since.
- From the start I loved almost everything about Arch. The one thing I
didn't love was the attitudes towards new users that was so common in the forum. I certainly understand all sides of what is a complex issue and I'm not trying to open that can of worms here. I'm only mentioning it because when I first became an Arch user I found the overall tone of the forum to be extremely off-putting, so much so that I can pinpoint it as the sole reason I shied away from trying to become an active contributor back then. Also, it will help everyone to know where my head was at when I tell you the rest of my story.
I stumbled upon Antergos in May 2013 and I immediately knew that I had found my home. The project's goals and the views of its developers aligned perfectly with my own. For me, Antergos was (and still is) the perfect solution as it has allowed me to contribute (albeit indirectly) to the advancement of what I truly believe to be the best linux distribution available. I know that's a rather broad statement, but I'm trying to keep this short and to the point. If anyone would like me to elaborate on something more specifically, I'd be happy to do so.
I currently maintain six or seven PKGBUILDS in the AUR, of which three are notable: pycharm-eap[1], lightdm-webkit2-greeter[2], and lightdm-webkit-theme-antergos[3]. I've indirectly contributed to other packages in the AUR through comments by offering advice to users, notifying maintainers of new releases as well as any problems with PKGBUILDS (always including a proposed solution), and directing bug reports away from AUR comments and to their proper channel. I always take the time to properly request deletion of PKGBUILDS that shouldnt be in the AUR (for whatever reason) whenever I come across one. I've also reported (and still do report) bugs on http://bugs.archlinux.org when it was/is appropriate. On one or two occasions I've gone as far as reaching out directly to maintainers of official packages to provide them with important information.
Its's also worth mentioning that I currently maintain many packages[4] for Antergos and I'm open to moving any (that are appropriate) to community.
So you might be wondering: "Why become a TU now?". Well, the reason is pretty simple. I was asked to consider applying by Alex Filgueira, the TU who currently maintains the Cinnamon packages and a person with whom I've had the pleasure of collaborating with on Antergos for the past three years. Sadly, his schedule has become far too busy to continue to maintain the Cinnamon packages. Another TU, György Balló, has been picking up the slack for the past few months but, having more than a few packages of his own to maintain, he told Alex that it would be nice to have some help with Cinnamon. Considering that Cinnamon is my own personal desktop of choice, Alex thought I would want to consider joining forces with György to maintain Cinnamon. Obviously, Alex was correct and so here we are. That's my story :)
I know that every minute of your free time is priceless, so thank you all in advance for taking the time review and consider my application. I look forward to (hopefully) "making things official" between myself and Arch Linux.
[1] https://aur.archlinux.org/packages/pycharm-eap/ [2] https://aur.archlinux.org/packages/lightdm-webkit2-greeter/ [3] https://aur.archlinux.org/packages/lightdm-webkit-theme-antergos/ [4] http://build.antergos.com/browse/main
Best Regards,
Dustin Falgout Web Developer
E-mail: dustin@falgout.us Google/Skype: dustinfalgout Freenode IRC: #antergos -----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQEcBAEBCAAGBQJW02A1AAoJEK6lKb8SKQLlb6EH/2bE+uzlWsuU3kIouB8sEGwr qzGmBT3JntkZsOrsy1fYl7kNz2GAlc2/+8MCJ9LUinkv46Egiw93lW8C58G8eudQ LOJ1GTz7hh5suO+xOagXdmTJwJMK04VPtHksTeNg3mVONmJPNxSlDdRk77sTHZMd 95aAnvnPBkk1U6Zn4hr6pPUG6HvPGmMseDdmBLr62Fh5CgupsEli4Q2vmgTlZwr6 CoJo9LEaS20djXihDgXYY/6TDEeKeyzj7I9M33IP6eppoACEzsueXxInD5aBPyvD HgcqvC7UNnpha8k2LBbL5xyTOUiDyhwwpf8umLHWPLCA6OmK9se3aYiY2FaUd8A= =8/xf -----END PGP SIGNATURE-----
Well, the 5 day period has ended to interview the applicant, so now the 7 day period to vote is opened.
Good luck!
Cheers
Well, the 5 day period has ended to interview the applicant, so now the 7 day period to vote is opened.
Good luck!
Cheers
out of curiosity: is the voting over yet?
On mer., 2016-03-23 at 22:59 +0100, G. Schlisio wrote:
Well, the 5 day period has ended to interview the applicant, so now the 7 day period to vote is opened.
Good luck!
Cheers
out of curiosity: is the voting over yet?
Yes and the motion was denied.
Cheers,
On Wed, Mar 23, 2016 at 5:27 PM, Sébastien Luttringer seblu@seblu.net wrote:
On mer., 2016-03-23 at 22:59 +0100, G. Schlisio wrote:
Well, the 5 day period has ended to interview the applicant, so now the 7 day period to vote is opened.
Good luck!
Cheers
out of curiosity: is the voting over yet?
Yes and the motion was denied.
Cheers,
-- Sébastien "Seblu" Luttringer https://seblu.net | Twitter: @seblu42 GPG: 0x2072D77A
What was the vote count? Why the denial?
Am 23.03.2016 um 23:27 schrieb Sébastien Luttringer:
On mer., 2016-03-23 at 22:59 +0100, G. Schlisio wrote:
Well, the 5 day period has ended to interview the applicant, so now the 7 day period to vote is opened.
Good luck!
Cheers
out of curiosity: is the voting over yet?
Yes and the motion was denied.
Cheers,
Is there a change in policy? Until now, results always have been announced here, as far as i remember. Maybe i remember wrong though… thanks anyway!
On 2016-03-23 22:59, G. Schlisio wrote:
Well, the 5 day period has ended to interview the applicant, so now the 7 day period to vote is opened.
Good luck!
Cheers
out of curiosity: is the voting over yet?
Apparently Alexandre forgot to post the results here… To expand lakonic Sebastien's answer:
Yes: 7 No: 16 Abstain: 8
The quorum is met as participation is 72.09%.
Dustin, according to our bylaws, you can re-apply after 3 months. I hope you won't give up after this vote and we will see you again in that time.
Bartłomiej
aur-general@lists.archlinux.org