Convo v2

angela

What is this topic

Creating this topic for us to have a place to discuss a wishlist (feature requests) for Convo.

Relevant Links

Taiga Board: For things being currently worked on [need to update]
repository: https://github.com/angelagilhotra/convo-app
prod: https://convo-app-gray.vercel.app/
staging: (via every PR on the repository)

What can be expected in this thread

I’ll be posting a weekly “Current State of Things” with subheadings “Changelog” and “Current Focus”
Changelog would include all the changes since last week that can be seen in the app
and Current Focus would include what I’m currently working on
This would be a fairly technical update

I’ll be converting discussions from here into tasks and put them on the Taiga board - that is the place to look into if you want to see all that’s currently work in progress. [need to update]

angela

Current state of things

We currently have two versions of Convo: v1 and v2.

The reasoning behind upgrading it this way was because we wanted a bunch of new features that required changing quite a lot of backend and the database schema. Because Convo was being heavily used when I started (the block was still running) it didn’t make sense to upgrade the sort of stable app.

Current Focus

Upgrade to v2: move convo subdomain to point to the v2 version of the app
For this to be possible, I still need to work on some features:
- Confirmation state (after submitting the form and after RSVP)
- Access controlled events (adding an option to token gate a particular event - the idea is to eventually add simpler gating as well, eg., slack auth)
- filter button on home (/) and upcoming (/all) page to filter for the events that have been allowed for the tokens in the user’s wallet - if signed in. If not signed in, will just see public events
- either upgrade via Vercel or our server if we get to fix the hosting issue before then (and turn off Digital Ocean server)

Changelog

What changes in v2?

sign in with wallet: required to propose an event and RSVP
RSVP flow: click on RSVP -> a modal that asks for email and/or a display name
- we do not force the requirement of the email, but if we don’t have it the user loses on:
  - notification before start of the event
  - any changes that were made to the event
  - viewing other people who are attending the event
view token gated events in / and /all

cryptowanderer

@angela said in Convo v2:

sign in with wallet: required to propose an event and RSVP

This should not be required when RSVP’ing to public events, right?

Also, any chance we could port this thread over the forum.kernel.community. We can mark it’s visibility only to staff so that just we can see it for now if that makes you happier?

angela

@cryptowanderer moved to https://forum.kernel.community/t/convo-v2-updates-and-progress/41/2