Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversations - community discussions on Collective pages #2223

Open
piamancini opened this issue Jul 9, 2019 · 14 comments
Open

Conversations - community discussions on Collective pages #2223

piamancini opened this issue Jul 9, 2019 · 14 comments

Comments

@piamancini
Copy link
Contributor

@piamancini piamancini commented Jul 9, 2019

User story

As contributor, I can open an issue on a collective's page so that I can start a conversation about a topic, make a proposal, get and provide feedback, provide or ask for community support, organize.

Best solution for this problem

Github Issues on the collective page.
Comments on expenses posted on the thread in the CP
Comments on transactions posted on the thread in the CP
Pinned issues/updates from core contributors
Link comments to transactions.

MVP

An MVP is a comment thread that lets anyone start or answer to a thread and lets core contributors post their updates as comments on the thread and pin them.

Metrics

Engagement on the CP measured by number of threads started and commented on.

Documentation

N/A

@piamancini piamancini changed the title #Feature: Conversations #Feature: Conversations Issue from Brussels Summer Team Retreat Jul 9, 2019
@Betree Betree added this to Backlog in New collective page via automation Jul 24, 2019
@xdamman

This comment has been minimized.

Copy link
Contributor

@xdamman xdamman commented Oct 14, 2019

I wonder if we could start with renaming the table Updates to Conversations and allow anyone to create one. And following the existing design pattern of filtering a list by tag, we could filter conversation from "Core Contributors" or "All conversations" (Updates are today effectively conversations started by the core contributors). Later we could introduce the concept of tags for conversations to let people define a "Updates" tag.

Another thought I had was about how we could include comments on expenses because they are also "conversations". Maybe a good way to fetch the list of latest "Conversations" would be to not only fetch the latest updates but also the latest comments.

E.g.

XR Belgium Conversations

  • Sunday: What about doing an action at the Atomium? by Tom
    (No comment yet)
  • Saturday: Expense: €300 for paint for the pink boat submitted by Majo
    Latest comment by Xavier
  • Friday: Good luck for the Royal Rebellion by Bernadette
  • Friday: Expense for posters submitted by Shadowfaxxx
    Latest comment by Misternature
@xdamman

This comment has been minimized.

Copy link
Contributor

@xdamman xdamman commented Oct 15, 2019

After talking to Ben and thinking more about it, I’d propose to have two separate sections on the collective page that can be each turned on/off for each collective (like the global goals, events sections): one section for updates and one section for conversations.
From Ben’s perspective it’s not that complicated to merge the two sections.
From my perspective I’d like to keep things separated so that the collective can turn each section on/off independently. Waiting for design feedback on that.

In the MVP we won’t implement the emoji reactions (though I think it’s a great great feature that would be very nice to have, so that’s a stretch goal, cherry on the cake) :-)

The form to create a conversation should be a minimal rich text editing that allows for image upload.

Everyone that participates in the conversation should automatically « follow » the conversation and can unfollow with one click by email.
Question: where can we show who follows the conversation?

Collective page

Conversation page

Mobile view

@piamancini

This comment has been minimized.

Copy link
Contributor Author

@piamancini piamancini commented Oct 15, 2019

Great progress!
What's the rationale for having two separate sections? it seems to me that updates is just a pinned conversation and only admins can pin/unpin it. Pretty much like a twitter pinned tweet. You can only have one item pinned at a time so it'd be the latest update. I think simplicity should be something we try to do more of.

@xdamman

This comment has been minimized.

Copy link
Contributor

@xdamman xdamman commented Oct 15, 2019

I think it’s confusing to mix the two.
Especially if at a later stage we gonna introduce the concept of pinned conversations.

I’d like to keep both separated like on a facebook page.
You can publish posts on your page and you can participate in conversations in the facebook group associated to your page. But there is a clear distinction.
Same on telegram where you have the concept of a broadcast channel to get updates from the community and then an associated “chat” where anyone can initiate a conversation. Here again, it’s very well separated. And here again you have the concept of “pinned message”.

It’s also two very different level of engagement. Only the people quite involved in the community will be interested in the conversations. People just supporting financially will only be interested in the “Official Updates”.

@Memo-Es

This comment has been minimized.

Copy link

@Memo-Es Memo-Es commented Oct 21, 2019

Here are the results after the first round of feedback on Friday, Oct 18th @Betree
👉 Prototype

Updates Conversations
@piamancini

This comment has been minimized.

Copy link
Contributor Author

@piamancini piamancini commented Oct 22, 2019

Looks great @Memo-Es - We need a view that includes the Create a new update for logged in admins.

@xdamman

This comment has been minimized.

Copy link
Contributor

@xdamman xdamman commented Oct 24, 2019

See my comments in the images below:

Let me know if you have any questions.

@Betree

This comment has been minimized.

Copy link
Member

@Betree Betree commented Oct 24, 2019

@Memo-Es Looks great! We need to have some pagination for these pages. That may not be implemented for MVP, but that's something we're 100% sure will be needed if Collectives start using the feature.

@xdamman

This comment has been minimized.

Copy link
Contributor

@xdamman xdamman commented Nov 4, 2019

Feedback on latest export from @raulgrafico @Memo-Es

I'd also put the Conversations section right below the Updates section.

Can you share the latest version of the the Conversation page?

@raulgrafico

This comment has been minimized.

Copy link

@raulgrafico raulgrafico commented Nov 4, 2019

@xdamman this is the latest version for the conversation page.

03 → Conversation Thread

@alanna alanna changed the title #Feature: Conversations Issue from Brussels Summer Team Retreat Conversations - community discussions on Collective pages Nov 12, 2019
@Betree

This comment has been minimized.

Copy link
Member

@Betree Betree commented Nov 12, 2019

Notes from today's meeting:

MVP

  • Use Notification + Member tables to manage subscriptions
  • Follow/unfollow button for conversations
  • Create/Delete
  • Rich text (bold, italic)

Important

  • Reactions
  • Hide
  • Edit
  • Reply

Backlog

  • Manually subscribe to updates #1445
  • Pin conversation
  • Mentions
  • Posting as (posting comments as a collective)
  • Private comments
  • Pagination

Won't do

  • Showing organization on avatar
@raulgrafico

This comment has been minimized.

Copy link

@raulgrafico raulgrafico commented Nov 13, 2019

Hi guys, this is the latest update for this. The overlay to view all the people on a reaction is still pending, and I want to confirm with @cuiki if there is a pattern for that.
@piamancini @Betree @xdamman

Collective page (Option 1) Collective page (Option 2) Collective conversations Conversation thread Create conversation Updates Create new update
01-Collective - COMPRESSED  - A  01-Collective - COMPRESSED  - B  03-Conversations - List  05 → Conversation Thread 02 → Create new conversation STEO 02 03-Updates - List 02 → Create new update

*Currently working on updates made in a call on Nov 13th

@Betree

This comment has been minimized.

Copy link
Member

@Betree Betree commented Nov 18, 2019

Looking great @raulgrafico!

The Create conversation CTA's position on the form still feels strange to me.

I'm ready to start implementing if @xdamman think we're ready.

@raulgrafico

This comment has been minimized.

Copy link

@raulgrafico raulgrafico commented Nov 25, 2019

Update

@xdamman @Betree

Collective desktop Conversation (Create new) Web Updates (Create new) Web Conversation (List) Web Updates (List) Web Conversation (Thread) Web Updates (Detail)
01-Collective - Desktop 02 1 → Create new conversation 02 2 → Create new update 03 1-Conversations - List 03 2-Updates - List 05 1 → Conversation thread 05 2 → Update detail
Conversation (Create new) Mobile Updates (Create new) Mobile Conversation (List) Mobile Updates (List) Mobile Conversation (Thread) Mobile Updates (Detail) Mobile
02 1 → Create new conversations - Mobile 02 1 → Create new update - Mobile 03 1-Conversations - List - Mobile 03 1-Updates - List - Mobile 05 1 → Conversation thread - Mobile 05 2 → Update - Mobile
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
5 participants
You can’t perform that action at this time.