Team's contact e-mail address options should be more obvious
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Low
|
Ian Booth | ||
Bug Description
Currently <https:/
The confirmation process seems unnecessary. I don't need to use e-mail to finish the registration of a product or a project, so why do I need to for a team? It has also caused confusion about whether this address is for team administration, or team-wide notifications.
The confirmation process should be removed, and this part of the form should be rendered like this:
Messages for the team should be sent to:
(*) Each member individually
( ) A mailing list address: [______]
The same applies to the page for changing the address after the fact (+editemail).
Related branches
- Curtis Hovey (community): Approve (code)
-
Diff: 308 lines (+28/-117)9 files modifiedlib/lp/app/stories/form/xx-form-layout.txt (+2/-2)
lib/lp/registry/browser/team.py (+3/-18)
lib/lp/registry/browser/tests/test_person.py (+0/-27)
lib/lp/registry/interfaces/person.py (+0/-20)
lib/lp/registry/stories/team/xx-team-contactemail.txt (+8/-0)
lib/lp/registry/stories/team/xx-team-home.txt (+1/-1)
lib/lp/registry/stories/teammembership/xx-teammembership.txt (+0/-46)
lib/lp/registry/templates/person-macros.pt (+2/-2)
lib/lp/registry/templates/team-contactaddress.pt (+12/-1)
| description: | updated |
| Changed in launchpad: | |
| status: | Unconfirmed → Confirmed |
| Barry Warsaw (barry) wrote | #1 |
| Curtis Hovey (sinzui) wrote | #2 |
| Changed in launchpad-registry: | |
| importance: | Medium → Low |
| status: | Confirmed → Triaged |
| tags: | added: teams |
| tags: | added: email |
| Changed in launchpad: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Ian Booth (wallyworld) |
| Ian Booth (wallyworld) wrote | #3 |
| Launchpad QA Bot (lpqabot) wrote | #4 |
| tags: | added: qa-needstesting |
| Changed in launchpad: | |
| status: | In Progress → Fix Committed |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
The other problem with this work flow is that a confirmation message really should not be sent to a mailing list's posting address. It's highly likely that such a confirmation message would get held for approval if the mailing list limits non-member posts. That would accidentally be okay because it's probable that the list owner is creating that connection between the team and the external mailing list, and they'll be able to see the held message and complete the confirmation process.
It's even worse though if the message gets posted to the list, because then any list member would be able to complete the confirmation.
There should be a way for a list owner to complete the confirmation (or avoid it) for setting a team's contact address to an external mailing list.