Re: Please provide a daily summary of commits, not one email per commit
| From: | Andrea Faulds | Date: | Thu, 31 Jul 2014 17:18:48 +0000 |
| Subject: | Re: Please provide a daily summary of commits, not one email per commit | ||
| References: | 1 2 | Groups: | php.standards |
| Request: | Send a blank email to standards-+get-199@lists.php.net to get a copy of this message | ||
On 31 Jul 2014, at 18:06, Sara Golemon <pollita@php.net> wrote:
> On Thu, Jul 31, 2014 at 8:36 AM, Andrea Faulds <ajf@ajf.me> wrote:
>> Please provide a daily summary of commits, not one email per commit.
>> My inbox is being stuffed with emails about commits for minor changes,
>> and because there are so many of them, I don’t read half of them.
>> A daily (half-daily? quarter-daily?) summary would be enough.
>>
> That's likely to be awkward given the way PHP's infrastructure was
> built. More likely we'd create another list (standards-vcs@) for
> commit emails.
>
> For my part, I just have a filter rule in place to auto-archive those.
> But it'd certainly make paging through history on
> news.php.net/php.standards easier to navigate. :)
I don’t really like the idea of just using a filter rule or a separate list. In the former case, I
bet I’d never check that folder (I know I didn’t when I started auto-filtering ReactOS bug
reports), and in the latter case I’d never subscribe.
But, here’s a crazy idea for you. Our mailing list infrastructure permits a daily digest. What if
we make standards subscribe to standards-vcs? Assuming we can somehow make it possible for list
recipients not to unsubscribe the list from the list.
--
Andrea Faulds
http://ajf.me/