gell-schedule

scheduled sessions using the gell framework

• see gell-session/domain/CONFERENCE.md for overlap with gell-session conference abstraction

Concepts

• event
  • future session that can be scheduled
  • could also be called template "instance"
• resource
  • person or thing that can participate in an event
• invitation
  • used to associate resources to an event
• plan
  • session capturing activity related to planning one or more events
• template
  • captures common event attributes for a series of events
  • provides basis for recurring events
  • cannot be scheduled
• schedule
  • defines time-related attributes used to generate repeating events
• calendar
  • time range bounded by a start and end time
  • can be named i.e. "March 2023"
• timeline
  • collection of related events
• trigger
  • see trigger.md for more

Events

• schedule
• cancel

Working with Time Zones

Scheduling

• time zone should be associated with resource

Brainstorm

• a scheduled event is really just a logical representation of some Session that will happen in the future
  • usually part of a larger Session
  • for example, a "meeting" may be scheduled for an hour at 1p tomorrow
    • associated activity before the meeting takes place
    • associated activity after the meeting takes place
    • could be part of a series of associated meetings
• "templates" will play a large role in implementations
  • not sure if these are declarative or code based
  • perhaps the library assists in building code based templates
  • might be sequences (generators)
  • persistent ones might be stored in the directory table
  • a group of templates can be organized in to a "catalog"
• where does workflow abstraction fit in?

Meeting Use Case

1. someone or something needs to schedule when it is going to happen
   • based on a template?
   • ...
2. people must be invited
3. resources can be associated
   • voice call
   • video conference
   • etc
4. people/resources can acknowledge the invitations in some way
   • optional step
5. people/resources can be sent notifications or reminders
6. the "meeting place" is started
   • video conference, etc
   • NOTE: as this point, a Session is in progress
7. people/resources join the meeting place
8. people/resources leave the meeting place
9. people/resource contribute follow on activities

On Demand Notes

• in effect, on demand use cases are a type of scheduling
• this may split the domain between on demand and traditional "meeting" type scenarios

Testing

• part of this effort should be a better approach to testing and simulation

Use Cases

or are these REALMs?

• video conference
• game
• task list
• reservation
• itinerary planning