www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-8400) Bug in LDAP schema?
Date Tue, 30 Sep 2014 12:18:33 GMT

    [ https://issues.apache.org/jira/browse/INFRA-8400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14153112#comment-14153112
] 

Gavin commented on INFRA-8400:
------------------------------

It is to reflect what is stated in the (current) ICLA.
If a committer is in need of changing that field to a new email address, they use the current
procedure which is:-

1. email new ICLA to secretary with updated email address. (And proof they own the current
account)
2. root@ change the LDAP record.


> Bug in LDAP schema?
> -------------------
>
>                 Key: INFRA-8400
>                 URL: https://issues.apache.org/jira/browse/INFRA-8400
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: LDAP
>            Reporter: Sebb
>            Assignee: Gavin
>
> The LDAP shema [1] includes the following description:
> 	NAME 'asf-icla-email' 
> 	DESC 'This is the email from which the ICLA was received, and the official contact email
address.' 
> This implies that the official contact email address cannot be changed without sending
a replacement ICLA. This does not seem right.
> [1] https://svn.apache.org/repos/infra/infrastructure/trunk/ldap/schema/asf-custom.schema



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message