Skip to content

How to have different Hugo voting properties for the same membership type #64

@arkoebel

Description

@arkoebel

The constitution says that members are only able to nominate if they joined the convention before the end of the previous year (or they were members of the previous year's convention). There is no distinction for voting (you only need to be a member), but there is one for nominating.

I understand that with the previous versions of Kansa, this could be dealt with by updating the hugo nomination indicator in the people table. However, since the people table doesn't have this indicator anymore, I can't see an easy way to deal with this issue.

What we've done so far:

  • Members of the previous WC were loaded under the type HugoNominator. If they choose to upgrade (we shouldn't call that "Upgrade", but that's what's written on that button), they retain their right to nominate.
  • Members who joined before Dec 31st have the voting rights associated with their membership type
  • Members who join after Dec 31st are each switched by the registration team to an equivalent category without nomination rights (so Adult becomes AdultNV). However, this is burdensome for the registration team and there is always the possibility that someone manages to nominate before we catch them.

How would you go about this?

There is always the possibility to modify the client to assign a NV type for new members, but how to deal with upgrades (If I was a supporter before Dec 31st and I upgrade to Adult, I should stay Adult, whereas if I joined after, I should upgrade to AdultNV)?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions