Re: Fyi: Weekly Digest are now monthly

I don't assiduously follow the spec-prod list, and in some ways that 
makes my comment appear less relevant, but in other ways it makes it 
more so, because digests have more value.

Spec-prod emails bypass my inbox into a folder that i look into from 
time to time. It's extremely useful to be able to see in a compact list 
form what discussions & PRs have been taking place over the past week, 
and then quickly link to the discussions i've missed that are of 
interest.  Given the size of the weekly digests, a monthly digest will 
probably be too long to be effective. But perhaps more important, it is 
not timely enough to intersect with discussions in a timely way – it 
will probably be very late to join many discussions.  The point of a 
digest is not to simply have a list of what happened, but it's to draw 
your attention so that you can join a discussion that's of interest 
while it is happening.

I receive many daily and weekly digests they are clearly labelled in the 
subject line, so i find it hard to think that, if you don't want to read 
it,  it's a significant chore to hit the delete button once a week.

ri




Philippe Le Hégaret wrote on 26/04/2023 16:26:
> Fyi, we switched to monthly notifications to limit the noise:
>  https://github.com/w3c/github-notify-ml-config/pull/257
>
> kuddos to @dontcallmedom and @marcoscaceres.
>
> Next digest will be this Monday.
>
> Feel free to follow up here if you'd prefer something else.
>
> Philippe
>
> On 12/12/2022 3:19 PM, fantasai wrote:
>> Hi!
>> I am wondering if anyone finds these automated “weekly digest” emails 
>> useful; and even if they are useful, can we push them to a different 
>> mailing list for people who *want* such automatic notifications?
>>
>> I think it would be a lot better for spec-prod if we can have less 
>> noise, and encourage more spec editors to join for whatever few 
>> relevant, but high-quality, human-initiated conversations we happen 
>> to have.
>>
>> I am sure the Bikeshed and Respec editors can make an effort to 
>> manually push to spec-prod any critical notifications that need the 
>> full attention of W3C spec editors.
>>
>> Thanks~
>> ~fantasai
>>
>