Details

      Description

      At present, committers and members have several places where e-mail addresses need to be maintained.
      - Selfserve - email forwarding
      - MailAlias.txt - e-mail aliases
      - members.txt - e-mail aliases

      It is tedious keeping these in step, and can be hard for mail moderators to access the aliases (see separate Jira for moderation enhancement)

      The suggestion is:
      - add field for e-mail alias to LDAP. The source for this is MailAlias.txt, which is committer-private. LDAP could be read-only for all but the owner. Perhaps allow updates by PMC chairs?
      - might as well add the home URL from urls.txt. This is public, as it is published on people.apache.org


      LATER
      - add missing entries from members.txt if/when that is converted to LDAP

        Issue Links

          Activity

          Sebb created issue -
          Sebb made changes -
          Field Original Value New Value
          Link This issue relates to INFRA-3868 [ INFRA-3868 ]
          Hide
          #asfinfra Bot added a comment -
          <danielsh> How about: add altEmail attribute to LDAP, then cron generate MailAlias.txt from LDAP, while adding a member={yes,no} column to it ?
          Show
          #asfinfra Bot added a comment - <danielsh> How about: add altEmail attribute to LDAP, then cron generate MailAlias.txt from LDAP, while adding a member={yes,no} column to it ?
          Hide
          #asfinfra Bot added a comment -
          <danielsh> see r796798
          Show
          #asfinfra Bot added a comment - <danielsh> see r796798
          Gavin made changes -
          Component/s LDAP [ 12313430 ]
          Hide
          #asfinfra Bot added a comment -
          <danielsh> design question, does anyone care to have alternate email addresses shared that are shared only to members but not to committers? (like today addresses in members.txt but not in MailAlias.txt+LDAP)
          Show
          #asfinfra Bot added a comment - <danielsh> design question, does anyone care to have alternate email addresses shared that are shared only to members but not to committers? (like today addresses in members.txt but not in MailAlias.txt+LDAP)
          Hide
          Sebb added a comment -
          Perhaps that question should be asked on members@
          Show
          Sebb added a comment - Perhaps that question should be asked on members@
          Hide
          #asfinfra Bot added a comment -
          <danielsh> personally I'm tempted to answer "yes", and it shouldn't complicate things too much.
          Show
          #asfinfra Bot added a comment - <danielsh> personally I'm tempted to answer "yes", and it shouldn't complicate things too much.
          #asfinfra Bot made changes -
          Assignee Daniel Shahaf (äñ§€¥£¢) [ danielsh ]
          Hide
          #asfinfra Bot added a comment -
          <danielsh> created an LDAP attribute, populated it from MailAlias.txt
          Show
          #asfinfra Bot added a comment - <danielsh> created an LDAP attribute, populated it from MailAlias.txt
          Hide
          #asfinfra Bot added a comment -
          <danielsh> What are all the places (not including whimsy, and not including documentation for new committers) that refer to MailAlias.txt? Particularly scripts, etc, that read it.
          Show
          #asfinfra Bot added a comment - <danielsh> What are all the places (not including whimsy, and not including documentation for new committers) that refer to MailAlias.txt? Particularly scripts, etc, that read it.
          Hide
          Sebb added a comment -
          Looks like it was originally set up for Agora, but I think that is now defunct.

          I've used it in some of the validation utilities, but they don't read it directly, they just read a local copy, so easy enough to fix that by exporting from LDAP or whatever.
          Also, the validation utilities have been largely superseded by whimsy.

          Some of the scripts in https://svn.apache.org/repos/infra/infrastructure/trunk/tools use the file:
          apache-alias.rb
          committer.rb
          guess_pmc_list.pl

          Not yet checked to see if these are still relevant.
          Show
          Sebb added a comment - Looks like it was originally set up for Agora, but I think that is now defunct. I've used it in some of the validation utilities, but they don't read it directly, they just read a local copy, so easy enough to fix that by exporting from LDAP or whatever. Also, the validation utilities have been largely superseded by whimsy. Some of the scripts in https://svn.apache.org/repos/infra/infrastructure/trunk/tools use the file: apache-alias.rb committer.rb guess_pmc_list.pl Not yet checked to see if these are still relevant.
          Hide
          #asfinfra Bot added a comment -
          <danielsh> the first two are used by whimsy
          Show
          #asfinfra Bot added a comment - <danielsh> the first two are used by whimsy
          Hide
          #asfinfra Bot added a comment -
          <rubys> apache-alias.rb has been fixed
          Show
          #asfinfra Bot added a comment - <rubys> apache-alias.rb has been fixed
          Hide
          #asfinfra Bot added a comment -
          <rubys> committer.rb has been removed
          Show
          #asfinfra Bot added a comment - <rubys> committer.rb has been removed
          #asfinfra Bot made changes -
          Status Open [ 1 ] Closed [ 6 ]
          Resolution Fixed [ 1 ]
          Hide
          Sebb added a comment -
          What about the e-mail addresses in members.txt?

          Does it make sense for members.txt to have another set of e-mail aliases?

          Are any e-mail aliases in members.txt not intended for publication to non-members, i.e. should not appear in the exported MailAlias.txt?

          As it stands now, moderators still need to check both MailAlias.txt and members.txt.

          Aliases that are in members.txt and are already in LDAP could presumably be removed from members.txt, as that is just duplication.

          But what to do about aliases which are only in members.txt?
          I think this question may need to be asked on members@
          Show
          Sebb added a comment - What about the e-mail addresses in members.txt? Does it make sense for members.txt to have another set of e-mail aliases? Are any e-mail aliases in members.txt not intended for publication to non-members, i.e. should not appear in the exported MailAlias.txt? As it stands now, moderators still need to check both MailAlias.txt and members.txt. Aliases that are in members.txt and are already in LDAP could presumably be removed from members.txt, as that is just duplication. But what to do about aliases which are only in members.txt? I think this question may need to be asked on members@
          Sebb made changes -
          Resolution Fixed [ 1 ]
          Status Closed [ 6 ] Reopened [ 4 ]
          Hide
          Sebb added a comment -
          Also, the original JIRA mentioned urls.txt
          Show
          Sebb added a comment - Also, the original JIRA mentioned urls.txt
          Hide
          #asfinfra Bot added a comment -
          <danielsh> then ask it on members@
          Show
          #asfinfra Bot added a comment - <danielsh> then ask it on members@
          #asfinfra Bot made changes -
          Status Reopened [ 4 ] Closed [ 6 ]
          Resolution Fixed [ 1 ]
          Tony Stevenson made changes -
          Workflow jira [ 12627821 ] INFRA Workflow [ 12711565 ]
          Gavin made changes -
          Fix Version/s Initial Clearing [ 12325964 ]
          Transition Time In Source Status Execution Times Last Executer Last Execution Date
          Open Open Closed Closed
          142d 16h 25m 1 #asfinfra Bot 11/Jan/12 04:25
          Closed Closed Reopened Reopened
          9h 46m 1 Sebb 11/Jan/12 14:11
          Reopened Reopened Closed Closed
          1h 41m 1 #asfinfra Bot 11/Jan/12 15:52

            People

            • Assignee:
              Daniel Shahaf (äñ§€¥£¢)
              Reporter:
              Sebb
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development