Re: FD.io TAC Proxy Policy


George Zhao
 

+1, same here, TAC can pick a proxy among FD.io TSCs

 

 

From: tsc@... [mailto:tsc@...] On Behalf Of Dave Barach
Sent: Tuesday, March 13, 2018 1:36 PM
To: tsc@...
Subject: Re: [tsc] FD.io TAC Proxy Policy

 

+1. Let’s try the simplest scheme [option 1] and see how it goes.  

 

From: tsc@... <tsc@...> On Behalf Of Joel Halpern
Sent: Tuesday, March 13, 2018 2:23 PM
To: tsc@...
Subject: Re: [tsc] FD.io TAC Proxy Policy

 

I am inclined to allow the rep to pick a proxy from the other TSC members.

If the TSC observes a pattern it has a problem with, then we can change the rules (and we probably have a bigger problem.)

 

Yours,

Joel

 

From: tsc@... [mailto:tsc@...] On Behalf Of Edward Warnicke
Sent: Tuesday, March 13, 2018 2:03 PM
To: tsc@...
Subject: [tsc] FD.io TAC Proxy Policy

 

The LFN TAC has decided that the individual projects should set their policy on how proxies to the TAC are determined if their TAC representative is unable to attend.

 

As I see it, there are minimally a couple of options:

 

1)  The FD.io representative to the TAC may pick a proxy themselves from the other FD.io TSC members (what was done two weeks ago for the TAC meeting)

2)  The FD.io TSC votes on a proxy for the FD.io TAC rep in the event they notify the FD.io TSC they need one for a meeting on a case by case basis.

 

There may be other good ideas on how to handle it.  Do folks have opinions?

 

Ed

Join tsc@lists.fd.io to automatically receive all group messages.