Alan Burlison wrote: > 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.
Why do we need employee numbers? It seems like we just need a SCA number field and a Commit role field in addition to whatever other roles that person has. And, an entry and exit process, so as people change companies we always have the right number. We already have multiple people that work for companies using the same SCA number and we don't track their employee numbers. Sun shouldn't be any different. Sun just needs it's own SCA number. The employee number granularity shouldn't be needed. User roles should define what an OpenSolaris user can and can not do. (And, if you get the user names to match inside and outside Sun like you want then you can cross check that person via LDAP if for some reason you need to do that.) Jim
