Stephen Hahn <sch at sun.com> writes: > * Alan Burlison <Alan.Burlison at sun.com> [2007-12-01 11:30]: >> The problem we have is that we have no reliable way of identifying Sun >> employees in the current OSO database. There is a employee_id column, >> but there's nothing to check it is filled in correctly, or even at all. >> Email addresses are no use either. And if we don't mandate that SWAN >> and OSO usernames are the same, the problem gets even harder still. > > I'm not sure what the problem is: ON (and other consolidations) > should not be granting commit rights to a user without either a > contributor agreement or a membership in an organization with a > contributor agreement. Has a consolidation done so? > > (I am assuming that the employee_id is only editable by site > administrators, and is presumed valid.) >
Contributor agreements are ephemeral. Sun employees are under a blanket SCA (in effect), a person leaving Sun should not lose their access, but it *would* require they then sign an SCA. (the same is true for companies signing agreements) Possession of an agreement when added isn't enough, they aren't pertpetually valid. -- Rich
