Opt-ou/in email notification

Whenever the user receive a notification, Hubl sends an email.

• Add a checkbox/switch on "Edit my profile" page which allows the user to opt-in/out for all email related to notifications.

---

Original mesage/user story:

Apparently when someone @mentions you in a chat room, you get the message as an email.

WHOAH, please tell me that is optional, and where to administrate that.

As for this ticket: I would expect such administration to be intuitive to locate, and enabled only after an explicit consent!

mentioned in issue #670 (moved)

@jonas Indeed, we get this feedback more and more. Thanks for bringing this up.

@rachel That might be a duplicate of #255 (moved). I let you pick the one that makes sense to keep alive.

ESS France is willing to finance this feature : to have a simple checkbox in my profile page to opt-out of all email notifications (except new password request ?). Could someone evaluate its cost ?

Can't they just place us in SPAM?

OK I stop...

@jbpasquier is your man

Let say that we run for a checkbox on the user profile which opt-out of all email notifications (Things which come on the notification component)

Involve work on: djangoldp-profile, djangoldp-notifications, solid-directory

May conflict with #281 (closed) & #255 (moved)

Added an estimation to this issue

@jbpasquier I see an estimated time of 4h. Can you clarify how many tokens it would require?

Depending on who take it, from 35 to 45 tokens, possibly in the middle.

Let say 45.

changed time estimate to 4h

@sylvain @louis.csn Cf. #669 (comment 39334), but I'm not sure how product ownership comes into play here. It feels to me that if we let clients decide what the interface should do, as is happening here, we'll endup having Gimp instead of Photoshop.

Agree, or Odoo where there is no consistency between modules.

I guess we need to have a constant UX work to adapt all components.

@sylvain so it would be the project manager who needs to have a UX reviewing all feature requests?

That suppose there is a UX designer (or more) that know about what is happening in the ecosystem?

I guess

ESS France can put 20 token to finance that. I guess it's not enough, can we find someone else to co-finance it ?

changed title from no administration of email notifications to Opt-ou/in email notification

changed the description

changed the description

Any news about that ? I see it is funded. Are the 20 tokens from ESS France engaged in this funding and how much more tokens are engaged ? From where ?

Hey @fabien4vo , Yes indeed, it's on his rails, how long yet ? I Ask @jbpasquier to tell us, but it's like very soon.

@fabien4vo Yes, the tokens from ESS France are engaged on this feature. I realize we didn't let you know.

@rachel @louis.csn @jbpasquier Worth noting here that @fabien4vo had said ESS France was ready to invest 20 tokens on this one. @jbpasquier then convinced @Cyrilthiriet to invest the rest to develop the feature, but we didn't think of letting @fabien4vo and ESS France know that their 20 tokens were chipped in on this feature. If @fabien4vo had spent them elsewhere, that could have been a problem, especially with bigger amounts. We need to ensure this doesn't happen.

Thanks @alexbourlier . I would also be interested to know how much token is "the rest" to inform ESS France.

@Cyrilthiriet was supposed to tell you that FNK is adding the missing 25 tokens here. :-)

OK, thanks !

@alexbourlier thanks for pointing this out. I think the communication has been pretty fluid in that case: the client was informed that its 20 tokens would be coinvested on that feature. But indeed, ideally a confirmation should have been sent to @fabien4vo before starting the work, to check if the client hadn't changed its mind in the meantime. Probably the risk relies on the dev team here, who engaged work without awaiting for a formal green light from the client :)

Exactly

mentioned in issue #853 (moved)

Server side is working and deployed, front-end struggle due to the un-ability to change this check from the user's profile edition page.

Related issue djangoldp-packages/djangoldp#307 (closed)

Fixed on djangoldp side, published on solid-directory, will come on the next release of Hubl.

closed