Implement site selection token purchasing support for Nasfic and Worldcon

[offbyone]

This will involve merging the site-selection branch and ensuring that site selection token purchasing doesn't interfere with the operation of the cart

Requirements:

• Support 0..n site selection elections (generally 1 or 2)
• purchases should be allowed to be grouped, or done separately at different times.
• display the site selection token to the user
• prepare for integration with online voting systems (which may require us to pre-generate tokens for voting, and assign them at purchase time)

[offbyone]

One feature we may need is the ability to purchase a token that is a "non-voting token" that can be purchased and identified as a non-voting token so that it can be enforced to be a "no preference" vote.

These tokens need to be transferrable to a human member so that they can become a voting token.

[fnbauer]

This could only work if you already track non-human members in some fashion.There are likely only a few instances where this is needed, and those irganizations know to vote no preference anyway.-FredSent from my phone -------- Original message --------From: Chris Rose @.> Date: 4/9/22 12:36 PM (GMT-05:00) To: ChicagoWorldcon/wellington @.> Cc: Subscribed @.***> Subject: Re: [ChicagoWorldcon/wellington] Implement site selection token purchasing support for Nasfic and Worldcon (Issue #148) One feature we may need is the ability to purchase a token that is a "non-voting token" that can be purchased and identified as a non-voting token so that it can be enforced to be a "no preference" vote. These tokens need to be transferrable to a human member so that they can become a voting token.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

[wmbuff]

I think the idea is that some small number of orgs and people (like NESFA, WSFA, GRRM, and Kevin Standlee) have traditionally purchased some extra memberships in the winning convention through site selection for org members/friends/staff to be named later. So what we're looking for there is a way to allow the payment into the site selection system without generating a voting token for those kinds of things.

It's relevant in part because Glasgow seems to be working on a pre-support structure that encourages this to a degree.

But the thing I think runs a greater risk is making sure we have an ability to turn someone's ability to buy a voter token off, especially at-con. I see that posing some real potential problems with unidentifiable double votes. Pre-con, we can easily tell whose vote a mail-in ballot is, and prevent a double-vote by only counting the one we received electronically. But at-con, we're separating the vote portion from the voter info.

Maybe we could turn off token purchases online for attending memberships once the person picks up their badge? That would be a way to prevent double-votes, and then we could just hold the walk-in ballots from supporting/virtual members sent with a friend to separate after verifying at the close of voting that that member hasn't voted electronically as well.