#7043 RFE: discussion.fp.o use your fp.o alias
Closed: Upstream 5 years ago Opened 5 years ago by langdon.

  • Describe what you need us to do:

I would prefer when I create an account on discussion.fedoraproject.org that it create it with my fas alias rather than the email the fas alias maps to. For example, when I get prompted to setup an account after fas login, use langdon@fp.o not langdon@rht.c


So, the issue is that Discourse likely send notification to that email, and may use that email for incoming discussion by email.

I am rather confident that we do not have yet the reply by email feature activated (since there is no MX or anything set for that domain), but maybe I am wrong. But email notification is likely working.

And if we use the @fp.o email, that work for cla+1, that mean someone at cla+0 will use a non working email. And that's likely bad and gonna break something (what, i do not know).

Metadata Update from @kevin:
- Issue priority set to: Next Meeting (was: Needs Review)

5 years ago

Couldn't you offer the user the option? Or even, have them type the preferred email address? You don't need to take the one that the oauth gives you, do you?

We discussed this in our last weekly meeting. Sorry for not updating it sooner.

Basically, we cannot do this now.

However, we can try and add something for this to CAIAPI (which is going to partly replace FAS) and it's web ui (which will replace FAS'es web ui). That would allow users that do have the alias to say 'use my alias instead of my base email'.

We agreed to keep this ticket open here for now to track this, and close it once we have CAIAPI tracking up and running.

Metadata Update from @kevin:
- Issue assigned to puiterwijk
- Issue priority set to: Waiting on Assignee (was: Next Meeting)

5 years ago

The caiapi tracker is live and the project is being worked on.

I've filed https://pagure.io/CAIAPI/issue/6 over there. Please feel free to add anything to that ticket that I missed here.

Thanks for your patience on this and hopefully we will get there soon.

Metadata Update from @kevin:
- Issue close_status updated to: Upstream
- Issue status updated to: Closed (was: Open)

5 years ago

Login to comment on this ticket.

Metadata