Allow subscribing to convo without voting on all comments

[patcon]

Re-ticketed from https://github.com/pol-is/polis-issues/issues/116#issuecomment-624723827

@crkrenn: I would like the option of having a "quit"/"quit for now" button next to agree/disagree/pass that would jump straight to the email signup card.

@colinmegill in https://github.com/pol-is/polis-issues/issues/116#issuecomment-624783488

• [...] We really should only trigger an email to return if our confidence in our understanding of how they fit into the topology changes, not just because there are more comments or votes.
• [...]
• We should break out the issue of 'come back and vote later', pausing the UI, etc. This is a larger conversation, but a good one. How users relate to the conversation over time depends a lot on the context in which the conversation is embedded.

Does this title capture the general idea well enough, or should we tweak it?

[crkrenn]

I agree that it is good to separate these two issues.

I think it is a good strategy to not ask for email until the user is engaged.

For my current deployment plans, I've decided that a quit button is the best near-term choice.

Longer term, we might consider click rate. When that slows, we can offer the option of coming back later.

I also like devising a metric that won't contact users unless there are significant changes to conclusions or topics. Essentially the appearance of a new cluster.

[crkrenn]

And, I'm not arguing that this is the default or even in the user config. Only that it be available as a build time option.

[colinmegill]

@crkrenn Let's start with when we contact users. This is an important one because it also changes the messaging — "Someone else commented" (well, that was expected) to "We no longer have confidence about where you are" (I am personally needed).

The Jupyter notebooks ~5-10x the number of clusters. We'll need to find a better metric than just how many. This issue is probably dependent, @patcon @metasoaurous, on the integration of the new algorithms into the math module.

On Thu, May 7, 2020 at 9:35 PM crkrenn [email protected] wrote:

And, I'm not arguing that this is the default or even in the user config. Only that it be available as a build time option.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pol-is/polis-issues/issues/148#issuecomment-625580701, or unsubscribe https://github.com/notifications/unsubscribe-auth/AANQGGLIYRFPCTZNCGG7N53RQNOUZANCNFSM4M26D5BA .

[patcon]

cc @metasoarous

[crkrenn]

@metasoarous & @patcon,

I'm glad that this issue made it onto the Polis Development Priority list!

FYI, I've asked @tamas-soos-toptal to look into adding a "quit for now" button as a globally configurable option for deployment. We plan to open a pull request if progress is good. Depending on what you and others think, we could also add this as a conversation specific option.

[patcon]

Cool! I know that in the past @colinmegill has advocated collaborating on mockups (ie. sharing them in issue queue) before any visual work was attempted, to make sure the interaction was aligned. I know that simple interaction is really important to the team, so I'd recommend starting there before building too much. Just sketches on paper would be a great way to communicate, nothing fancy :)

Also, email notifications are currently disabled because they were not tuned enough. So might be worth contributing effort there first. See: https://github.com/compdemocracy/polis/issues/763

And oops, i think this is a dup of https://github.com/compdemocracy/polis/issues/766 :/ Maybe we could transfer details from one and close the other. I wasn't sure the team's stance on the "flexible hint card" idea, but I'm down to consider that out-of-scope if they think it would slow down this work

[crkrenn]

This is definitely related to https://github.com/compdemocracy/polis/issues/766, but we are proposing a more focused solution.

Below are mockups for the voting cards for web and mobile.

Our current idea is to put a "quit for now" "button" next to, but separated from, the "agree/disagree/pass" buttons. On the web, this could be on the same line. On mobile, it probably needs to be on a second line.

A second option would be to put the "quit for now" button above or below the "X remaining" text. I have a slight preference for our current mockup, but both sound good to me.

[crkrenn]

FYI, I've started working on this issue again... I'll share a minimum viable version when available.