[
https://issues.apache.org/jira/browse/WHIMSY-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16577208#comment-16577208
]
Chris Thistlethwaite commented on WHIMSY-200:
---------------------------------------------
Yes, the script does need to take into account single names. However, the issue
isn't with publication but with LDAP needing first name and last name, which I
thought was for legal reasons. My point being, if John Smith puts in a ICLA
with public name Jimmy Shoe, then LDAP/etc would be created using that has his
legal name instead of the more appropriate Full Name. I haven't combed through
LDAP and ICLAs to find out if someone has a different Full Name than Public
Name but both are First/Last names, so I have no clue if this particular case
exists.
> Public name from ICLA prioritized over Full Name
> ------------------------------------------------
>
> Key: WHIMSY-200
> URL: https://issues.apache.org/jira/browse/WHIMSY-200
> Project: Whimsy
> Issue Type: Improvement
> Components: General
> Reporter: Chris Thistlethwaite
> Priority: Minor
>
> Recently there have been a few new accounts that made their way into
> new-account-reqs.txt that only have a single name in the full name field.
> While there are instances where single names are appropriate, it seems that
> if someone fills out "public name" and "full name", then "public name" gets
> submitted as their full name. Single names cause the make-accounts.sh script
> to fail (as LDAP is looking for first and last name).
> The work around is someone from Infra (me) has to look up their ICLA and find
> their actual full name, edit new-account-reqs.txt, then re-run the account
> creation script.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
