COmanage Developers List

[Warren Anderson <>]

Hi Marie,

On Oct 13, 2011, at 13:12 , Marie Huynh wrote:

>> I think this is probably LIGO specific so can you put an issue
>> into bugs.ligo.org under 'MyLIGO'?
>> 
> 
> https://bugs.ligo.org/redmine/issues/194
> 
>>> He
>>> assumes nobody will try to join both CIT and Hanford, so we can sort
>>> people by such categories.
>> 
>> I bet he is proven wrong within the year.
> 
> We could still sort but have them show up in both lists, plus a note
> about being in both.  Shall I file that as a related issue or subtask?
> 
>>> 
>>> PI/Group managers should be able to manage council delegates but
>>> that's broken on the current system and I may be working on that.  I
>>> assume this is just another group managing a COU for us?
>>> 
>> 
>> No, I don't see council delegates as a COU. It is just a
>> group. So I think the scenario is using the COmanage UI to
>> push through to Grouper.
>> 
>> We do, however, want each COU to have some special knowledge
>> that there does exist a council delegates group.
>> 
> 
> Hmm... I'm still not sure how the council delegates fit into the
> picture. What is the purpose of this group and what sort of
> interaction is it going to have with other groups or COUs that makes
> this special knowledge necessary?

At the risk of muddying the waters into which I was not asked to wade 
in the first place:

"Council delegate" is a role that is assigned to members of some types 
of COUs in the LSC, much like the "graduate student" or "Group Manager"
roles. The set of all people from all COUs that have that role is 
authorized (or required) to do certain things (receive certain email 
lists, look at certain web areas, etc) based on their council delegate 
role. Since we are using groups for authorizations, rather than roles 
(at the moment), we want to have all council delegates in a "Council 
Delegates" group that can be used to create authorization ACLs.

One notable difference between the council delegate role and other roles
is that there are a precise number of people who should have that role at 
all times within each COU that has that role (based on a formula that 
involves the number of FTEs in the COU). Most other roles can have 
variable numbers (eg there should be >= 1 group manager per COU, there 
should be >= 0 graduate students per COU, etc). If there are an incorrect 
number of people with the council delegate role in a COU that has council 
delegates, that needs to be noted and brought to someone's attention. I 
believe the details of how and when it should be brought to someone's 
attention (and the exact list of people whose attention to which it should 
be brought) are not determined yet, but since the role is assigned from 
within the COU (like the group manager role, but perhaps unlike the 
graduate student role), certainly word has to get back to the COU somehow
if they have an incorrect number of delegates. But the bottom line is that 
the number of delegates a COU should have and the number they do have and 
the list of people within the COU to whom the role have been assigned are 
all things that should be prominently seen in an overview of any COU that
has council delegates.

Another difference between council delegate and other roles is that 
the delegate roles tend to get reassigned to different people in a COU more 
frequently than most other roles. It would not be unusual for a council 
delegate role to be reassigned 3 or 4 times per year. This also argues for 
making the list of who is currently assigned the council delegate role 
within a COU easily accessed and prominent.

Does that clarify anything?

Finally, I don't want to interfere in the work you all are doing - if this
seems like interference, let me know. I will not be offended and will 
gladly go back to lurking on this list.

Cheers,
Warren

> 
> Thanks,
> 
> Marie
> 
>> Cheers,
>> 
>> Scott
>> 


+================[ WARREN G. ANDERSON ]====================+
| PO Box 413, Dept. of Physics, Milwaukee, WI 53201, USA   |
|   CANADA: (403) 212 1426          USA: (414) 212 5446    |
+==========================================================+

Attachment: smime.p7s
Description: S/MIME cryptographic signature