Re: [aur-general] Package orphaning policy improvement - RFC

2014-05-26 Thread Zack Buhman
On Mon, May 26, 2014 at 06:08:55AM -0700, Patrick Burroughs (Celti) wrote: > How about a daily digest email of orphaned packages, similar to the > repository reports sent out for testing and community-testing? And out-of-date (>x days?) summarization. pgp5RTG8xMlh2.pgp Description: PGP signature

Re: [aur-general] Package orphaning policy improvement - RFC

2014-05-26 Thread Patrick Burroughs (Celti)
On Mon, May 26, 2014 at 4:58 AM, Nowaker wrote: >>> Of course, it would be nice to also auto-mail the maintainer, say, one >>> week before the auto-orphaning. >> >> And to auto-mail to the list, perhaps somebody is willing to maintain a >> package. > > I'm afraid there will be tons of such e-mails

Re: [aur-general] Package orphaning policy improvement - RFC

2014-05-26 Thread Yamakaky
Would be beter to have "Notify of orpaning" link in "Package Actions". Only interested people + the maintainer would get the notifications. Yes, and why not a RSS feed/mail subscription to follow the comments ?

Re: [aur-general] Package orphaning policy improvement - RFC

2014-05-26 Thread Nowaker
Of course, it would be nice to also auto-mail the maintainer, say, one week before the auto-orphaning. And to auto-mail to the list, perhaps somebody is willing to maintain a package. I'm afraid there will be tons of such e-mails. Would be beter to have "Notify of orpaning" link in "Package

Re: [aur-general] Package orphaning policy improvement - RFC

2014-05-25 Thread Ralf Mardorf
On Sun, 2014-05-25 at 18:11 -0300, Thiago Barroso Perrotta wrote: > On Sun, 25 May 2014 17:06:21 +0200 > Nowaker wrote: > > > What do you think about auto-orhpaning packages that stay marked > > out-of-date for more than, say, 3 months? Done automatically by AUR, > > with no request on ML. > >

Re: [aur-general] Package orphaning policy improvement - RFC

2014-05-25 Thread Ernie Brodeur
+1 to auto-mail + auto-orphan, I bet more packages will get picked up instead of sitting in limbo until somebody wants to deal with the process of getting a package orphaned. On Sun, May 25, 2014 at 2:11 PM, Thiago Barroso Perrotta < thiagoperrott...@gmail.com> wrote: > On Sun, 25 May 2014 17:

Re: [aur-general] Package orphaning policy improvement - RFC

2014-05-25 Thread Thiago Barroso Perrotta
On Sun, 25 May 2014 17:06:21 +0200 Nowaker wrote: > What do you think about auto-orhpaning packages that stay marked > out-of-date for more than, say, 3 months? Done automatically by AUR, > with no request on ML. > +1 for that. Of course, it would be nice to also auto-mail the maintainer, sa

Re: [aur-general] Package orphaning policy improvement - RFC

2014-05-25 Thread Jeremy Audet
+1 — Jeremy "Ichimonji10" Audet

Re: [aur-general] Package orphaning policy improvement - RFC

2014-05-25 Thread Berno Strik
On Sun, 25 May 2014 17:06:21 +0200 Nowaker wrote: > Hey, > > Currently one has to contact the maintainer and wait 2 weeks before > reaching a TU on the ML to take over the package. I think this is > totally OK when the maintainer really maintains the package, e.g. has > generally frequent upd

Re: [aur-general] Package orphaning policy improvement - RFC

2014-05-25 Thread Yamakaky
Also, how about if orphaned for more than 3 months, then delete? I think auto-orphan is ok, but auto-delete is a bit wrong. There is a lot of really outdated packages, but maybe some ones are using them. And it can be used as a template for an updated version.

Re: [aur-general] Package orphaning policy improvement - RFC

2014-05-25 Thread Steven Honeyman
As a newcomer to packaging for the AUR, that was one of the things I thought "I wonder why they don't do that already" I'd read about some September cleanups (2011/2012 only?). Also, how about if orphaned for more than 3 months, then delete? There are some really outdated packages on there! On

[aur-general] Package orphaning policy improvement - RFC

2014-05-25 Thread Nowaker
Hey, Currently one has to contact the maintainer and wait 2 weeks before reaching a TU on the ML to take over the package. I think this is totally OK when the maintainer really maintains the package, e.g. has generally frequent updates, responds to the comments, etc. However, this is an over