[aur-general] Package orphaning policy improvement - RFC
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 overhead when it's obvious a package is no longer maintained. For example, those marked out-of-date for more than 3 months, or those that have numbers of comments requesting update with no single response from the maintainer. It includes a situation when a maintainer is otherwise active on AUR, e.g. they update their other packages. The fact is they don't upgrade the very one package that people are interested in - otherwise a package wouldn't have been marked out-of-date in the first place. 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. -- Kind regards, Damian Nowak StratusHost www.AtlasHost.eu
On Sun, 25 May 2014 17:06:21 +0200 Nowaker <enwukaer@gmail.com> 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 updates, responds to the comments, etc.
However, this is an overhead when it's obvious a package is no longer maintained. For example, those marked out-of-date for more than 3 months, or those that have numbers of comments requesting update with no single response from the maintainer.
It includes a situation when a maintainer is otherwise active on AUR, e.g. they update their other packages. The fact is they don't upgrade the very one package that people are interested in - otherwise a package wouldn't have been marked out-of-date in the first place.
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.
Hello, I totally agree with you. I have been, and still are, busy updating older Brother print/scan packages. It would save a lot of time and effort if this would be implemented. Besides if the maintainer of such packages is really serious he should enable notifications. Regards, libernux
+1 — Jeremy "Ichimonji10" Audet
On Sun, 25 May 2014 17:06:21 +0200 Nowaker <enwukaer@gmail.com> 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, say, one week before the auto-orphaning.
+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 < thiagoperrotta95@gmail.com> wrote:
On Sun, 25 May 2014 17:06:21 +0200 Nowaker <enwukaer@gmail.com> 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, say, one week before the auto-orphaning.
On Sun, 2014-05-25 at 18:11 -0300, Thiago Barroso Perrotta wrote:
On Sun, 25 May 2014 17:06:21 +0200 Nowaker <enwukaer@gmail.com> 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, say, one week before the auto-orphaning.
And to auto-mail to the list, perhaps somebody is willing to maintain a package.
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 Actions". Only interested people + the maintainer would get the notifications. -- Kind regards, Damian Nowak StratusHost www.AtlasHost.eu
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 ?
On Mon, May 26, 2014 at 4:58 AM, Nowaker <enwukaer@gmail.com> 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. Would be beter to have "Notify of orpaning" link in "Package Actions". Only interested people + the maintainer would get the notifications.
How about a daily digest email of orphaned packages, similar to the repository reports sent out for testing and community-testing? Regards, ~Celti
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.
participants (9)
-
Berno Strik
-
Ernie Brodeur
-
Jeremy Audet
-
Nowaker
-
Patrick Burroughs (Celti)
-
Ralf Mardorf
-
Thiago Barroso Perrotta
-
Yamakaky
-
Zack Buhman