* [Qemu-devel] Bouncing maintainers @ 2015-03-25 14:48 Markus Armbruster 2015-03-25 15:45 ` John Snow 0 siblings, 1 reply; 7+ messages in thread From: Markus Armbruster @ 2015-03-25 14:48 UTC (permalink / raw) To: qemu-devel I just had another cc: to an address gotten from MAINTAINERS bounce with "user unknown". How do we weed out dead MAINTAINERS entries? ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Qemu-devel] Bouncing maintainers 2015-03-25 14:48 [Qemu-devel] Bouncing maintainers Markus Armbruster @ 2015-03-25 15:45 ` John Snow 2015-03-26 13:19 ` Kevin Wolf 0 siblings, 1 reply; 7+ messages in thread From: John Snow @ 2015-03-25 15:45 UTC (permalink / raw) To: Markus Armbruster, qemu-devel On 03/25/2015 10:48 AM, Markus Armbruster wrote: > I just had another cc: to an address gotten from MAINTAINERS bounce with > "user unknown". > > How do we weed out dead MAINTAINERS entries? > Automated spambot that runs once a release cycle and reports back to the list which entries were dead? --js ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Qemu-devel] Bouncing maintainers 2015-03-25 15:45 ` John Snow @ 2015-03-26 13:19 ` Kevin Wolf 2015-03-26 21:35 ` John Snow 0 siblings, 1 reply; 7+ messages in thread From: Kevin Wolf @ 2015-03-26 13:19 UTC (permalink / raw) To: John Snow; +Cc: Markus Armbruster, qemu-devel Am 25.03.2015 um 16:45 hat John Snow geschrieben: > > > On 03/25/2015 10:48 AM, Markus Armbruster wrote: > >I just had another cc: to an address gotten from MAINTAINERS bounce with > >"user unknown". > > > >How do we weed out dead MAINTAINERS entries? > > > > Automated spambot that runs once a release cycle and reports back to > the list which entries were dead? I don't need more email. Why can't we just send a patch to MAINTAINERS dropping the line the first time someone actually notices it? Kevin ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Qemu-devel] Bouncing maintainers 2015-03-26 13:19 ` Kevin Wolf @ 2015-03-26 21:35 ` John Snow 2015-03-31 10:01 ` Markus Armbruster 0 siblings, 1 reply; 7+ messages in thread From: John Snow @ 2015-03-26 21:35 UTC (permalink / raw) To: Kevin Wolf; +Cc: Markus Armbruster, qemu-devel On 03/26/2015 09:19 AM, Kevin Wolf wrote: > Am 25.03.2015 um 16:45 hat John Snow geschrieben: >> >> >> On 03/25/2015 10:48 AM, Markus Armbruster wrote: >>> I just had another cc: to an address gotten from MAINTAINERS bounce with >>> "user unknown". >>> >>> How do we weed out dead MAINTAINERS entries? >>> >> >> Automated spambot that runs once a release cycle and reports back to >> the list which entries were dead? > > I don't need more email. Why can't we just send a patch to MAINTAINERS > dropping the line the first time someone actually notices it? > > Kevin > Could make a bot that just watches from: addresses on the list. If it sees a mail from you within the last release cycle, it assumes you are still alive. If it doesn't hear from you for an entire release cycle, it sends out a small ping and looks for bounces. Only once a release would be not more than four times a year, and most active maintainers would never see a single email. Or, yes, manually when it happens... ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Qemu-devel] Bouncing maintainers 2015-03-26 21:35 ` John Snow @ 2015-03-31 10:01 ` Markus Armbruster 2015-03-31 17:03 ` John Snow 2015-04-01 1:42 ` Fam Zheng 0 siblings, 2 replies; 7+ messages in thread From: Markus Armbruster @ 2015-03-31 10:01 UTC (permalink / raw) To: John Snow; +Cc: Kevin Wolf, Fam Zheng, qemu-devel John Snow <jsnow@redhat.com> writes: > On 03/26/2015 09:19 AM, Kevin Wolf wrote: >> Am 25.03.2015 um 16:45 hat John Snow geschrieben: >>> >>> >>> On 03/25/2015 10:48 AM, Markus Armbruster wrote: >>>> I just had another cc: to an address gotten from MAINTAINERS bounce with >>>> "user unknown". >>>> >>>> How do we weed out dead MAINTAINERS entries? >>>> >>> >>> Automated spambot that runs once a release cycle and reports back to >>> the list which entries were dead? >> >> I don't need more email. Why can't we just send a patch to MAINTAINERS >> dropping the line the first time someone actually notices it? >> >> Kevin >> > > Could make a bot that just watches from: addresses on the list. If it > sees a mail from you within the last release cycle, it assumes you are > still alive. Is this something patchew could do for us? It already watches list traffic. > If it doesn't hear from you for an entire release cycle, it sends out > a small ping and looks for bounces. I'm not sure I'd bother with the ping. Post the list of absentee maintainers, and let humans take it from there. > Only once a release would be not more than four times a year, and most > active maintainers would never see a single email. > > Or, yes, manually when it happens... ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Qemu-devel] Bouncing maintainers 2015-03-31 10:01 ` Markus Armbruster @ 2015-03-31 17:03 ` John Snow 2015-04-01 1:42 ` Fam Zheng 1 sibling, 0 replies; 7+ messages in thread From: John Snow @ 2015-03-31 17:03 UTC (permalink / raw) To: Markus Armbruster; +Cc: Kevin Wolf, Fam Zheng, qemu-devel On 03/31/2015 06:01 AM, Markus Armbruster wrote: > John Snow <jsnow@redhat.com> writes: > >> On 03/26/2015 09:19 AM, Kevin Wolf wrote: >>> Am 25.03.2015 um 16:45 hat John Snow geschrieben: >>>> >>>> >>>> On 03/25/2015 10:48 AM, Markus Armbruster wrote: >>>>> I just had another cc: to an address gotten from MAINTAINERS bounce with >>>>> "user unknown". >>>>> >>>>> How do we weed out dead MAINTAINERS entries? >>>>> >>>> >>>> Automated spambot that runs once a release cycle and reports back to >>>> the list which entries were dead? >>> >>> I don't need more email. Why can't we just send a patch to MAINTAINERS >>> dropping the line the first time someone actually notices it? >>> >>> Kevin >>> >> >> Could make a bot that just watches from: addresses on the list. If it >> sees a mail from you within the last release cycle, it assumes you are >> still alive. > > Is this something patchew could do for us? It already watches list > traffic. > Good idea. We can add a Maintainers status page that shows how long it's been since it's heard from each maintainer, and sort them in order, and we can check the page here and again. (Or, when patchew is made to be more stable, incorporated into a quarterly status report that it sends out to the list) >> If it doesn't hear from you for an entire release cycle, it sends out >> a small ping and looks for bounces. > > I'm not sure I'd bother with the ping. Post the list of absentee > maintainers, and let humans take it from there. > >> Only once a release would be not more than four times a year, and most >> active maintainers would never see a single email. >> >> Or, yes, manually when it happens... ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Qemu-devel] Bouncing maintainers 2015-03-31 10:01 ` Markus Armbruster 2015-03-31 17:03 ` John Snow @ 2015-04-01 1:42 ` Fam Zheng 1 sibling, 0 replies; 7+ messages in thread From: Fam Zheng @ 2015-04-01 1:42 UTC (permalink / raw) To: Markus Armbruster; +Cc: Kevin Wolf, John Snow, qemu-devel On Tue, 03/31 12:01, Markus Armbruster wrote: > John Snow <jsnow@redhat.com> writes: > > > On 03/26/2015 09:19 AM, Kevin Wolf wrote: > >> Am 25.03.2015 um 16:45 hat John Snow geschrieben: > >>> > >>> > >>> On 03/25/2015 10:48 AM, Markus Armbruster wrote: > >>>> I just had another cc: to an address gotten from MAINTAINERS bounce with > >>>> "user unknown". > >>>> > >>>> How do we weed out dead MAINTAINERS entries? > >>>> > >>> > >>> Automated spambot that runs once a release cycle and reports back to > >>> the list which entries were dead? > >> > >> I don't need more email. Why can't we just send a patch to MAINTAINERS > >> dropping the line the first time someone actually notices it? > >> > >> Kevin > >> > > > > Could make a bot that just watches from: addresses on the list. If it > > sees a mail from you within the last release cycle, it assumes you are > > still alive. > > Is this something patchew could do for us? It already watches list > traffic. Yes. Patchew can be added a page to list active addresses by release cycles. By comparing against MAINTAINERS file we know who are inactive. Fam > > > If it doesn't hear from you for an entire release cycle, it sends out > > a small ping and looks for bounces. > > I'm not sure I'd bother with the ping. Post the list of absentee > maintainers, and let humans take it from there. > > > Only once a release would be not more than four times a year, and most > > active maintainers would never see a single email. > > > > Or, yes, manually when it happens... ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2015-04-01 1:51 UTC | newest] Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2015-03-25 14:48 [Qemu-devel] Bouncing maintainers Markus Armbruster 2015-03-25 15:45 ` John Snow 2015-03-26 13:19 ` Kevin Wolf 2015-03-26 21:35 ` John Snow 2015-03-31 10:01 ` Markus Armbruster 2015-03-31 17:03 ` John Snow 2015-04-01 1:42 ` Fam Zheng
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.