I spoke to Dave today. I've known him for quite a while on IRC and have found him to be knowledgeable and helpful. Given how crazy my life has been lately, I'm more than willing to turn over some of my packages to him, and believe he will be a great asset to the team. If Ionut hadn't agreed to sponsor him, I would have been more than happy to do so. On Mon, Nov 29, 2010 at 7:01 PM, Dave Reisner wrote:

Greetings!

Please consider this my application to become a Trusted User. My name is Dave Reisner, and I'm 27 years old, currently residing in the New York City area. Ionut Biru has graciously offered to sponsor this application. I'm a self-taught programmer, computer enthusiast, an occasional IT consultant, and I enjoy brutal sarcasm & dry wit. During the daytime, I star as a QA website tester, writing automated test scripts with the Selenium framework. At night, I prefer Bash & C, but I also dabble in Go, Java, Ruby, and Python.

Although I've only been using Arch for a little over a year now, I've become very much appreciative and endeared to its simplistic style and offer of freedom in administration. I quickly settled into a CLI setup featuring DWM, mutt, ncmpcpp, tmux, etc and filled in any missing gaps with Bash and C programs of my own design. In particular, I wrote cower and burp, which interface with the AUR to do clean and fast downloading and uploading (respectively) from the AUR. Please feel free to visit my Github repositories [1].

I also consider myself to have been an active contributor to the Arch community. I advocate the testing repo (which I use on all the boxes I maintain), I diligently file and follow up with bug reports, providing patches or other solutions whenever possible, and I've made a few (though somewhat minor) code contributions to pacman.

Over the course of the past year, I've picked up a number of packages in the AUR [2]. While many of these aren't very popular, I would like to make an effort to bring Systemd into community to make it more accessible. I believe that while it does not necessarily fall directly in line with the "true spirit" of Arch, it's an excellent project and there are many people interested in its offerings within the Arch community. I've been following its development since a month after Lennart made his initial announcement, and I have been the major provider of Systemd packages on the AUR.

In addition, I've spoken with Daniel Griffiths and I offered to relieve him of some of his packaging duties (given his hectic schedule), and we agreed on: asciidoc, html2text, and rsnapshot. Eventually, as I become more comfortable with the role, I would like to take on more packages to help insure that our repos stay fresh and full of useful software. Since the recent cleanup.

I'm happy to answer any questions you may have. Thanks for taking the time to consider my application.

Dave.

[1] http://github.com/falconindy [2] http://aur.archlinux.org/packages.php?SeB=m&K=falconindy

On 30/11/10 11:01, Dave Reisner wrote:

Greetings!

Please consider this my application to become a Trusted User.

It is awesome to see you applying. I think you will be a great addition to the team. Allan

Greetings!

Please consider this my application to become a Trusted User. My name is Dave Reisner, and I'm 27 years old, currently residing in the New York City area. Ionut Biru has graciously offered to sponsor this application. I'm a self-taught programmer, computer enthusiast, an occasional IT consultant, and I enjoy brutal sarcasm & dry wit. During the daytime, I star as a QA website tester, writing automated test scripts with the Selenium framework. At night, I prefer Bash & C, but I also dabble in Go, Java, Ruby, and Python.

Although I've only been using Arch for a little over a year now, I've become very much appreciative and endeared to its simplistic style and offer of freedom in administration. I quickly settled into a CLI setup featuring DWM, mutt, ncmpcpp, tmux, etc and filled in any missing gaps with Bash and C programs of my own design. In particular, I wrote cower and burp, which interface with the AUR to do clean and fast downloading and uploading (respectively) from the AUR. Please feel free to visit my Github repositories [1].

I also consider myself to have been an active contributor to the Arch community. I advocate the testing repo (which I use on all the boxes I maintain), I diligently file and follow up with bug reports, providing patches or other solutions whenever possible, and I've made a few (though somewhat minor) code contributions to pacman.

Over the course of the past year, I've picked up a number of packages in the AUR [2]. While many of these aren't very popular, I would like to make an effort to bring Systemd into community to make it more accessible. I believe that while it does not necessarily fall directly in line with the "true spirit" of Arch, it's an excellent project and there are many people interested in its offerings within the Arch community. I've been following its development since a month after Lennart made his initial announcement, and I have been the major provider of Systemd packages on the AUR.

In addition, I've spoken with Daniel Griffiths and I offered to relieve him of some of his packaging duties (given his hectic schedule), and we agreed on: asciidoc, html2text, and rsnapshot. Eventually, as I become more comfortable with the role, I would like to take on more packages to help insure that our repos stay fresh and full of useful software. Since the recent cleanup.

I'm happy to answer any questions you may have. Thanks for taking the time to consider my application.

Dave.

[1] http://github.com/falconindy [2] http://aur.archlinux.org/packages.php?SeB=m&K=falconindy

Wow this is falconindy. I am a huge fan of burp and cower and your post on systemd was quite educational (or linked to another page that was quite educational; I don't remember which). I looked through your PKGBUILD's on AUR and they look like they are in quite nice shape. Good luck! I think you would make a great addition to the team. --Kaiting. -- Kiwis and Limes: http://kaitocracy.blogspot.com/

On 30 November 2010 09:32, Kaiting Chen wrote:

...

Greetings!

Please consider this my application to become a Trusted User. My name is Dave Reisner, and I'm 27 years old, currently residing in the New York City area. Ionut Biru has graciously offered to sponsor this application. I'm a self-taught programmer, computer enthusiast, an occasional IT consultant, and I enjoy brutal sarcasm & dry wit. During the daytime, I star as a QA website tester, writing automated test scripts with the Selenium framework. At night, I prefer Bash & C, but I also dabble in Go, Java, Ruby, and Python.

Although I've only been using Arch for a little over a year now, I've become very much appreciative and endeared to its simplistic style and offer of freedom in administration. I quickly settled into a CLI setup featuring DWM, mutt, ncmpcpp, tmux, etc and filled in any missing gaps with Bash and C programs of my own design. In particular, I wrote cower and burp, which interface with the AUR to do clean and fast downloading and uploading (respectively) from the AUR. Please feel free to visit my Github repositories [1].

I also consider myself to have been an active contributor to the Arch community. I advocate the testing repo (which I use on all the boxes I maintain), I diligently file and follow up with bug reports, providing patches or other solutions whenever possible, and I've made a few (though somewhat minor) code contributions to pacman.

Over the course of the past year, I've picked up a number of packages in the AUR [2]. While many of these aren't very popular, I would like to make an effort to bring Systemd into community to make it more accessible. I believe that while it does not necessarily fall directly in line with the "true spirit" of Arch, it's an excellent project and there are many people interested in its offerings within the Arch community. I've been following its development since a month after Lennart made his initial announcement, and I have been the major provider of Systemd packages on the AUR.

In addition, I've spoken with Daniel Griffiths and I offered to relieve him of some of his packaging duties (given his hectic schedule), and we agreed on: asciidoc, html2text, and rsnapshot.  Eventually, as I become more comfortable with the role, I would like to take on more packages to help insure that our repos stay fresh and full of useful software. Since the recent cleanup.

I'm happy to answer any questions you may have. Thanks for taking the time to consider my application.

Dave.

[1] http://github.com/falconindy [2] http://aur.archlinux.org/packages.php?SeB=m&K=falconindy

Wow this is falconindy. I am a huge fan of burp and cower and your post on systemd was quite educational (or linked to another page that was quite educational; I don't remember which). I looked through your PKGBUILD's on AUR and they look like they are in quite nice shape. Good luck! I think you would make a great addition to the team. --Kaiting.

I remember the nick from #archlinux and the Ubuntu forums. A very knowledgable character overall, PKGBUILDs are good, attitude is right, I have nothing bad to say.

On Mon, Nov 29, 2010 at 8:15 PM, Christopher Brannon wrote:

Dave Reisner writes:

...

Please consider this my application to become a Trusted User. My name is Dave Reisner, and I'm 27 years old,

As far as I can tell, you are strongly self-motivated.  I admire that quality.  You also have name-recognition in the community. You would make an excellent addition to the team. Good luck!

-- Chris

I also remember his nick from IRC, +1 from me. I do have a question out of curiosity though, do you have a specific path in my you would like to take? or nothing specific in mind? P.S. "keep doin' what you're doin'" Cheers!

On Mon, Nov 29, 2010 at 8:15 PM, Christopher Brannon wrote:

Dave Reisner writes:

...

Please consider this my application to become a Trusted User. My name is Dave Reisner, and I'm 27 years old,

As far as I can tell, you are strongly self-motivated.  I admire that quality.  You also have name-recognition in the community. You would make an excellent addition to the team. Good luck!

-- Chris

I concur! Having had observed Dave's work in the past, I am definitely impressed by his strong work ethic. Frankly, I'm surprised you [Dave] have waited such a long time to apply. +1 from me. Thanks, Brad

On Mon, 29 Nov 2010 20:01:04 -0500 Dave Reisner wrote:

Greetings!

Please consider this my application to become a Trusted User. My name is Dave Reisner, and I'm 27 years old, currently residing in the New York City area. Ionut Biru has graciously offered to sponsor this application. I'm a self-taught programmer, computer enthusiast, an occasional IT consultant, and I enjoy brutal sarcasm & dry wit. During the daytime, I star as a QA website tester, writing automated test scripts with the Selenium framework. At night, I prefer Bash & C, but I also dabble in Go, Java, Ruby, and Python.

<snip>

I'm happy to answer any questions you may have. Thanks for taking the time to consider my application.

Dave.

[1] http://github.com/falconindy [2] http://aur.archlinux.org/packages.php?SeB=m&K=falconindy

Given the fact that I remember your nick from the international comm- unity and I associate a good impression with it. Your character seems to be strong enough to bear with <s>our dragon</s> svenstaro, so there is not much to add, except that this is a great introduction. So +1 from me. Thorsten -- Jabber: atsutane@freethoughts.de Blog: http://atsutane.freethoughts.de/ Key: 295AFBF4 FP: 39F8 80E5 0E49 A4D1 1341 E8F9 39E4 F17F 295A FBF4

A little tangent but from this page it seems to me that a '-git' or '-svn' suffix should only be applied when there is a version of the package without that suffix in the name; this is to differentiate between the 'stable' and the 'development' version of the same package. https://wiki.archlinux.org/index.php/VCS_PKGBUILD_Guidelines In his AUR page there are some packages with '-svn' or '-git' suffixes that do not have non-suffixed counterparts. Is this correct? I would like to update that wiki page to explain the convention more clearly. --Kaiting. -- Kiwis and Limes: http://kaitocracy.blogspot.com/

On Thursday 02 December 2010 14:08:07 Allan McRae wrote:

On 03/12/10 00:01, Kaiting Chen wrote:

...

A little tangent but from this page it seems to me that a '-git' or '-svn' suffix should only be applied when there is a version of the package without that suffix in the name; this is to differentiate between the 'stable' and the 'development' version of the same package.

I think a -git suffix should be used always when the PKGBUILD is building from git sources.

+1 Also, remember that the version without the -git suffix is often in another repo, so doesn't show up on an AUR search. Pete.

On Fri, Dec 03, 2010 at 12:08:07AM +1000, Allan McRae wrote:

On 03/12/10 00:01, Kaiting Chen wrote:

...

A little tangent but from this page it seems to me that a '-git' or '-svn' suffix should only be applied when there is a version of the package without that suffix in the name; this is to differentiate between the 'stable' and the 'development' version of the same package.

I think a -git suffix should be used always when the PKGBUILD is building from git sources.

Allan

This is the interpretation I've always followed. I am however, guilty of one infraction of this by way of systemd-arch-units. I've meant to tag this and turn it into a straight download, but it hasn't happened yet. dave

On 2 December 2010 22:01, Kaiting Chen wrote:

A little tangent but from this page it seems to me that a '-git' or '-svn' suffix should only be applied when there is a version of the package without that suffix in the name; this is to differentiate between the 'stable' and the 'development' version of the same package.

https://wiki.archlinux.org/index.php/VCS_PKGBUILD_Guidelines

In his AUR page there are some packages with '-svn' or '-git' suffixes that do not have non-suffixed counterparts. Is this correct? I would like to update that wiki page to explain the convention more clearly. --Kaiting.

OK, let me get this right. You mean that when for eg. a software only has a development source tree and no tarball, it should just be 'package' and not 'package-vcs'? If so, I don't think that would be proper. If a PKGBUILD fetches development sources, it should have a development suffix. However, exceptions can be made sometimes. Personally, I know of at least one upstream that does not directly offer a tarball, but instead has (or rather had) an SVN tag that distributors could check out. This package would then be named without a vcs suffix.

On Thu, Dec 2, 2010 at 9:55 AM, Ray Rashif wrote:

...

A little tangent but from this page it seems to me that a '-git' or '-svn' suffix should only be applied when there is a version of the package without that suffix in the name; this is to differentiate between the 'stable' and the 'development' version of the same package.

https://wiki.archlinux.org/index.php/VCS_PKGBUILD_Guidelines

In his AUR page there are some packages with '-svn' or '-git' suffixes

On 2 December 2010 22:01, Kaiting Chen wrote: that

...

do not have non-suffixed counterparts. Is this correct? I would like to update that wiki page to explain the convention more clearly. --Kaiting.

OK, let me get this right. You mean that when for eg. a software only has a development source tree and no tarball, it should just be 'package' and not 'package-vcs'?

If so, I don't think that would be proper. If a PKGBUILD fetches development sources, it should have a development suffix. However, exceptions can be made sometimes.

Personally, I know of at least one upstream that does not directly offer a tarball, but instead has (or rather had) an SVN tag that distributors could check out. This package would then be named without a vcs suffix.

My original view had been that a package would be simply called 'package' regardless of whether or not a source tarball was offered. Then if someone makes a version that builds against upstream VCS, that package would be called package-vcs. In light of this new discussion however, I feel like the proper policy is to name a package without a suffix if there is a 'versioned release', no matter where this comes from (source tarball, vcs tag, etc.). Then the converse is that if a package has *no release* but just a rolling development trunk, then it is given a suffix. --Kaiting. -- Kiwis and Limes: http://kaitocracy.blogspot.com/

Kaiting Chen wrote:

In light of this new discussion however, I feel like the proper policy is to name a package without a suffix if there is a 'versioned release', no matter where this comes from (source tarball, vcs tag, etc.). Then the converse is that if a package has *no release* but just a rolling development trunk, then it is given a suffix. --Kaiting.

I agree with this. The "-vcs" suffix implies that you get the latest source version of the package at the time of building, i.e. the bleeding-edge developmental version (in the main branch at least). Packages that are built from vcs but which are based on some form of upstream "release" should not include the tag in the package name. I think the simplest rule of thumb would be that if the same PKGBUILD generates different binary packages depending on when makepkg was run, then it should include the suffix in the name. Regards, Xyne

On Thu, Dec 02, 2010 at 05:13:56PM +0100, Cédric Girard wrote:

On Thu, Dec 2, 2010 at 4:59 PM, Xyne wrote:

...

Packages that are built from vcs but which are based on some form of upstream "release" should not include the tag in the package name.

I think the simplest rule of thumb would be that if the same PKGBUILD generates different binary packages depending on when makepkg was run, then it should include the suffix in the name.

These two rules are not the same. For instance the package xbmc-svn [1] is based on fixed svn version that does not corresponds to any "release" upstream. It is just tested svn revisions (by the packager) as not every revisions are usable.

[1] http://aur.archlinux.org/packages.php?ID=20156

So doesn't that just mean that we have some packages currently in existance which break the guideline we're trying to establish? I propose that this particular package is named incorrectly, and would be better off as xbmc-devel. dave

On Thu, Dec 2, 2010 at 5:20 PM, Dave Reisner wrote:

On Thu, Dec 02, 2010 at 05:13:56PM +0100, Cédric Girard wrote:

...

On Thu, Dec 2, 2010 at 4:59 PM, Xyne wrote:

...

Packages that are built from vcs but which are based on some form of upstream "release" should not include the tag in the package name.

I think the simplest rule of thumb would be that if the same PKGBUILD generates different binary packages depending on when makepkg was run, then it

should

...

include the suffix in the name.

These two rules are not the same. For instance the package xbmc-svn [1] is based on fixed svn version that does not corresponds to any "release" upstream. It is just tested svn revisions (by the packager) as not every revisions are usable.

[1] http://aur.archlinux.org/packages.php?ID=20156

So doesn't that just mean that we have some packages currently in existance which break the guideline we're trying to establish? I propose that this particular package is named incorrectly, and would be better off as xbmc-devel.

dave

Yes you are right I misread Xyne message and understood the two rules quoted above as different. One is just broader than the other but there is no contradiction between them. -- Cédric Girard

Peter Lewis wrote:

On Thursday 02 December 2010 16:13:56 Cédric Girard wrote:

...

On Thu, Dec 2, 2010 at 4:59 PM, Xyne wrote:

...

Packages that are built from vcs but which are based on some form of upstream "release" should not include the tag in the package name.

I think the simplest rule of thumb would be that if the same PKGBUILD generates different binary packages depending on when makepkg was run, then it should include the suffix in the name.

These two rules are not the same. For instance the package xbmc-svn [1] is based on fixed svn version that does not corresponds to any "release" upstream. It is just tested svn revisions (by the packager) as not every revisions are usable.

My view would be that if a package builds a semi-stable but unreleased version (from wherever) which has been selected by the packager or upstream, then the package should be suffixed by -dev, -prerelease -unstable or something similar.

For the removal of confusion, -git -svn etc. should *track* the VCS in my view.

Pete.

For clarity, the only tag that I referred to in my previous post was the "vcs" tag. I agree with your comments regarding other suffixes. I think my proposed rule-of-thumb still works because the PKGBUILD for semi-stable releases still generates a fixed binary package. /Xyne

On Thu 02 Dec 2010 10:39 -0500, Kaiting Chen wrote:

On Thu, Dec 2, 2010 at 9:55 AM, Ray Rashif wrote:

My original view had been that a package would be simply called 'package' regardless of whether or not a source tarball was offered. Then if someone makes a version that builds against upstream VCS, that package would be called package-vcs.

In light of this new discussion however, I feel like the proper policy is to name a package without a suffix if there is a 'versioned release', no matter where this comes from (source tarball, vcs tag, etc.). Then the converse is that if a package has *no release* but just a rolling development trunk, then it is given a suffix.

I agree, but shouldn't this topic be in a separate thread?