thunderbird / thunderbird/appointment
Investigate merging Slots and Appointments
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 552
- Forks
- 29
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 23
Description
This is not saying we should get rid of the concept of multiple people on an appointment via slots, but maybe we should merge things like booking_status (and every other field) on the appointment model, and have attendees directly tie into the appointment model instead of slots.
We should also flip the relationship of attendees, and make it so attendees have an appointment_id, instead of slots having a attendee_id. That will help us moving forward with multi-person appointments.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the appointment, slot, and attendee model definitions and mapping their current fields and relationships. Done means the shared appointment fields and attendee relationship consistently support multi-person appointments without losing the slot concept.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, database
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100