Skip to content

Bug: Newcomers should be protected from being selected as single #3

@LBC970

Description

@LBC970

Description

When there's an odd number of participants, someone must be "single" (unpaired) that week. The current logic selects whoever "has been single least recently or never."

The problem: Newcomers by definition have never been single, making them prime candidates to be picked. This contradicts the veteran-newcomer pairing preference which exists to help newcomers integrate.

Real Example

Geraldine Powderly participated twice but was selected as single on her second participation — not a great experience for a newcomer.

Proposed Fix

When selecting who goes single:

  1. Filter to participants with 3+ participations first
  2. Apply the "least recently single" logic to that filtered list
  3. Only fall back to newcomers if everyone remaining is a newcomer (edge case)

Location

src/lambda_function.py - get_last_single_date() usage in generate_pairings() around lines 263-268

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions