NOM-009 may not be met

[ietf-svn-bot]

owner:ejimenez@yaco.es resolution_fixed type_defect | by rjsparks@nostrum.com

---

From RFC6730:

NOM-009: The tool MUST allow a communication email address for a
nominee to be set to one different than the email address with
which they were nominated.

How is this satisfied?

Other than sending reminder email to accept a nomination, how is the chair able to use that address? Is the intent to expose the address as a link and let the chair's email client handle the rest? If so, the address to use for communication with this nominee needs to be prominently placed.

---

Issue migrated from trac:1013 at 2022-03-04 02:47:56 +0000

[ietf-svn-bot]

@ejimenez@yaco.es commented

---

We need to meet this requirement, we think the best choice is:

• Add links to edit email nominee (only visible by chair) to the nominees table in the feedback view
• The chair could change the email nominee if the email introduced does not exist yet. If the new email does not exists, it will be created and the person object will be associated to this email.

If you aggree with the abobe points, we will develop rapidly.

[ietf-svn-bot]

@rjsparks@nostrum.com commented

---

I assume you would display this "designated email address" as a new column in the
table at nomcom/2013/private/view-feedback/ and make it viewable by members
and editable by the chair?

I'm not sure this is an address that we want to associate with the Person (unless we're
putting them in a Nominee Role or something like that). If we did that, it would show up
as an address they would have to manage themselves later. (See https://datatracker.ietf.org/accounts/profile/
when you are logged into the tracker).

We have that address in the Nominee object. Making that visible and allowing the chair to edit that should be enough, wouldn't it?

[ietf-svn-bot]

@ejimenez@yaco.es commented

---

Right now, when nomination is done, if the candidate name does not exists, a new mail and person are created, and them are associated, and nominee object has a foreignkey to this email. Then in all templates the nominee is showed as "[ nominee ]" and the unicode function of nominee model is:

def __unicode__(self):
  return u'%s' % self.email.formatted_email()

And formatted_email (function of Email model) uses object person as follows:

    def formatted_email(self):
        if self.person and self.person.name:
            return u'"%s" <%s>' % (self.person.plain_name(), self.address)
        else:
            return self.address

It is necessary to show nominee as: "Name of nominee" nominee@test.com in all templates, if we don't associate the new mail with the previous person, only email will be showed in templates like list of nominees.

I think there are two alternatives.

The first one:

• Change field address of Email object associated to Nominee object
• Change field address of person object associated to previous Email object

The second on:

• Create a new object Email to associate to the Nominee object.
• Change field address of person object associated to the new Email object created

As I said before, if we don't associate the email to a person object, we may not show the name of nominee in templates, because the email object only has address info.

[ietf-svn-bot]

@rjsparks@nostrum.com commented

---

Ok - after thinking more and talking with Henrik, I'm less concerned about creating a Person in the cases you describe. Your proposal in comment 1 seems good (but consider displaying it as I describe in comment 2).

[ietf-svn-bot]

@ejimenez@yaco.es commented

---

From f998e0d:

Add form to change email of nominees.
Refactor merge form to avoid merge old duplicate nominees.
See #1013

[ietf-svn-bot]

@ejimenez@yaco.es changed status from new to closed

[ietf-svn-bot]

@ejimenez@yaco.es changed resolution from `` to fixed