Re: [tei-council] SVN Users

No, they only have closed ones. Oh well. If they don't have a GitHub account the issues will get assigned to sf_user_THEIR-SF-USER On Thu, Aug 20, 2015 at 12:40 PM, Hugh Cayless wrote:

A quick search doesn’t turn up anything…they may well just not have GitHub accounts. Do they have active tickets assigned to them?

...

On Aug 20, 2015, at 12:30 , Raffaele Viglianti < raffaeleviglianti@gmail.com> wrote:

Hello,

could you guys help me figure out some of the GitHub user names from the spreadsheet that Hugh put together?

...

I can't really get usernames if the user hid their email... Or maybe they are just not on GH?

I'm looking for: brettbarney dpod epierazzo rwelzenb

On Thu, Aug 20, 2015 at 8:53 AM, James Cummings < James.Cummings@it.ox.ac.uk> wrote:

...

It is true that it will increase traffic on the list (though continual prods to be looking at github might be a good thing...) I count about 8 notifications I've received this month (slow month though...). Obvious

if

...

we were using github fulltime for both Stylesheets (etc.), and Guidelines then traffic would be that much higher.

I'm not sure the archives are currently reader-friendly, but I take your point that it 'pollutes' them with process-related information.

To get the ball rolling I've set up a user TEITechnicalCouncil but not yet subscribed it to repositories or added it to the TEIC organisation. (I'm waiting to hear back from Kevin about whether the right email addresses can be added to the mailing list first.) When I change its email to be the mailing list (tomorrow if no complaints) then I'll probably have a verification email sent through.

If we decide it is too much notification then we can reduce those using github's own controls. If we decide it is just not working we can always delete the github account. ;-)

-James

On 20/08/15 13:34, Martin Holmes wrote:

...

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

...

...

...

cause us all to pay less attention to the list in general. It'll make

...

...

...

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

...

...

...

...

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,

...

...

...

...

...

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

https://docs.google.com/spreadsheets/d/1N8hIBphezGsNB0SvEx7wSamyshNrszeNrlm6... that the the like 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 > >

-- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived