Stephen Lau wrote: > There's the case of Sun employees who have since left.... > If they've filed an individual SCA, then the SCA field is filled out - > but if they haven't, then there isn't any way to differentiate them from > current Sun employees.
Correct. That is why the new database schema distinguishes between different classes of SCA - if we know a particular person is covered by a Sun SCA, we also know that their 'reference' will be a Sun employee ID, and that could be checked against the corporate LDAP database. The bigger problem is that we need to bootstrap this by deciding who in the current database *is* a Sun employee. At present we have no guaranteed way of telling. My suggestion that we insist that OS userid + email match the SWAN userid + email was an attempt to help alleviate this problem, as well as to try to make it possible for humans to match up a commit message (say) with a Sun person. This would however require that anyone with a borg-id had their SWAN username changed, unless we are going to leak employee ids, and that change aslo has its own set of problems. -- Alan Burlison --
