Discord Scheduling

Status
development in progress
Problem Statement
What's the need we're addressing?
Web3 community member is trying to schedule a meeting with another 1-4 people they regularly engage with via discord but finds it frustrating because they have to use another tool (e.g. lettucemeet) and chase people around so they give their availabilities
User Story
What's the solution going to be like?
Community members that have gained the permission (TBD how, see research questions) can find the next available slot for a meeting with another 1-4 members and directly get the invite in everyone's calendar for everyone to accept/refuse
Functional Requirements
key functionalities that the feature provides
  • gating system so only “approved” members can use the feature
  • ability to know which members have connected their calendars and hence are available
    • members can configure their “work hours” so that slots outside of these are not counted as available
  • ability to identify next available slot between the members
  • ability to create meeting invite in the calendar of both the inviter and invitees for the next available slot
  • if the meeting is refused in the calendar of any member (both invitees and inviters), next available slot is proposed
  • ability to definitely refuse the meeting (see research questions)
 
 
Non-functional Requirements
other requirements of the feature
  • after onboarding, lowest friction possible to schedule
  • customers don't feel their privacy is violated
     
    Acceptance Criteria
    what needs to happen/be true for this feature to be approved
    • At least some RnDAO members use this feature regularly
    • .
     
    Research Questions
    to be discovered through the design process
    • if meeting is refused by invitees, the next option could be automatically offered in their calendars. But how do they refuse the meeting definitively?

        Discord Scheduling

        Status
        development in progress
        Problem Statement
        What's the need we're addressing?
        Web3 community member is trying to schedule a meeting with another 1-4 people they regularly engage with via discord but finds it frustrating because they have to use another tool (e.g. lettucemeet) and chase people around so they give their availabilities
        User Story
        What's the solution going to be like?
        Community members that have gained the permission (TBD how, see research questions) can find the next available slot for a meeting with another 1-4 members and directly get the invite in everyone's calendar for everyone to accept/refuse
        Functional Requirements
        key functionalities that the feature provides
        • gating system so only “approved” members can use the feature
        • ability to know which members have connected their calendars and hence are available
          • members can configure their “work hours” so that slots outside of these are not counted as available
        • ability to identify next available slot between the members
        • ability to create meeting invite in the calendar of both the inviter and invitees for the next available slot
        • if the meeting is refused in the calendar of any member (both invitees and inviters), next available slot is proposed
        • ability to definitely refuse the meeting (see research questions)
         
         
        Non-functional Requirements
        other requirements of the feature
        • after onboarding, lowest friction possible to schedule
        • customers don't feel their privacy is violated
           
          Acceptance Criteria
          what needs to happen/be true for this feature to be approved
          • At least some RnDAO members use this feature regularly
          • .
           
          Research Questions
          to be discovered through the design process
          • if meeting is refused by invitees, the next option could be automatically offered in their calendars. But how do they refuse the meeting definitively?