Let's do this on a trial basis. I worry about increasing the automated traffic to the Council list; it might generate a lot of notifications that cause us all to pay less attention to the list in general. It'll make the archives a bit less reader-friendly too. Cheers, Martin On 15-08-20 04:27 AM, James Cummings wrote:
Ok, since at least one other person thinks it is a good idea, using our voting-by-apathy rules, I'll go ahead and do it if no one shouts in the next day. ;-)
-James
On 20/08/15 12:22, Hugh Cayless wrote:
I think this is probably a good idea. It also means GitHub traffic, like Stuart's recent pull request, will be archived and is that much less likely to be ignored. The only downside I see is that (as you note) we'll probably all want to go turn our own notifications off.
I vote yes.
On Thu, Aug 20, 2015 at 6:07 AM, James Cummings
wrote: On 17/08/15 16:38, Hugh Cayless wrote:
I think we should just call the user "root" "TEI Council", and use the Council email address.
Following up on this, it seems a sensible idea to me that we should add a TEI Council user to github and use tei-council@lists.tei-c.org as its email address.
Does anyone have any objections before I just go an add that user? Before doing so we would need Kevin to add notifications@github.com (and if possible to whitelist domains, *@noreply.github.com) to the approved senders for the tei-council mailing list. Council list would then get any notifications to repositories we subscribed that user to. This seems like a useful thing, given we can always mute repositories in our personal accounts.
What are the problems I'm overlooking?
-James
-- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford