Skip to content

Separate table for membership requests #148

@maxnoe

Description

@maxnoe

Currently, membership requests are stored in the person table.

To disentangle this, we should make this a separate table. Separation of concerns.

class MembershipRequest:
    id = ...
    person_id = ...
    status = ...

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions