Give organizers the option to automatically accept registrations up to the competitor limit

[jfly]

Oliver just asked for this, and we spec-ed out a rough idea of how to do this. Some thoughts here:

• New registrations now start out "unprocessed". "Processed" registrations get moved to the waiting list, which means "this registration looks legit, and I'd like for this person to compete at my competition if there is space for them"
• Registrations on the waiting list are automatically marked as "accepted" if there's room for them in the registration list. This includes handling the case where an accepted registration is deleted, thereby freeing up space in the registration list.
  • NOTE: Do we want to allow changing a registration from processed to not processed? I believe we should allow changing a registration to not processed, IFF that registration is not accepted.
    • NOTE: I'm undecided if this should be implemented with 2 booleans: processed? and accepted?, or if it should be a single enum with 3 states: unprocessed, processed AKA pending AKA on-waiting-list. I am kind of leaning towards the enum...
  • NOTE: What about moving a registant from the accepted list to the pending list? Do we want to support something like that? It's weird, because if you try to un-accept someone, space frees up in the registration list, and then you have to pick someone from the waiting list to accept, which will be the person in the waiting list who registered earliest, which is probably the very person you just tried to move off the registration list...
  • Notify people when their registration is automatically moved from the waiting (aka: processed) list to the accepted registration list.
    • Also notify everyone still on the waiting list that they've moved 1 spot closer to competing?
      • NOTE: This seems potentially spammy, especially if the organizer is deleting a couple of people from the registration list, as each deletion will cause a slew of emails. FURTHER NOTE: We're already hitting our Mandril email limits pretty quickly, we'd have to decide just how much money we want to spend on emailing. See this screenshot from February 9th (9 days into the month, and we're already at 8.1/12k free emails):

[jfly]

After some discussion on the delegates@ mailing list, it turns out the registrants are confused by the fact that they end up on a waiting list when there's clearly space for them in the competition. We should be more explicit about why someone's registration is not accepted yet. Here's my proposal:

Everything shows up as "pending review" at first. This would show up to the user as "Your registration is pending review by the organizers". As an organizer, it would be your job to move the registrant from the pending review category to either the waiting list (because registration is full), accept the registration, contact the registrant to fix their information, or just reject (aka: delete, see #386) the registration if it's spam. That would give us enough information to give the registrant a more useful error message.

In case the it wasn't clear from the previous 2 paragraphs, the autogenerated email we send a user when they first register should make it clear what it means for your registration to be unprocessed/pending review (Your registration will be approved, if all of the requirements are met (such as: WCA ID assigned, pre-payment issued if necessary.)... Or something similar, to let them know that it is not automatic. )

[viroulep]

I like the idea of a list of registrations pending reviews, with the organizer having to move the registration to the appropriate list.

I'd like to point out that if we go with some automatic system, the organizers should always be able to move themselves in the accepted registrations list, regardless of when they registered.
(I'm thinking about a corner case scenario where the registrations are full while the organizer didn't manage to be available when they opened)

[cubewhiz]

From Philippe Virouleau in an email to announcements in September (regarding Stripe's fees)

• Refunds: We will no longer return Stripe fees when refunding a customer. We currently return all of the Stripe fees from the original charge when a business refunds a customer. Unfortunately, we still incur costs from the various payment partners we work with when a charge is refunded. Until now, we've absorbed these fees; moving forward, we’ve decided to adjust how refund fees are handled.

And the second point affects specifically US and Canadian users:

• International transactions: For US users, all non-US card transactions will now be charged an additional 1% fee. At the same time, we’re lowering our fee for currency conversion in the US from 2% to 1%. This fee applies only if the charge currency differs from the payout currency. For Canadian users, the currency conversion fee will remain unchanged but all non-Canadian card transactions will now be charged an additional 0.6% fee. Other countries are not affected.

---

Related, but separately, is it possible for registrations to be accepted up until the competitor limit is reached? Is that discussed here or elsewhere?

[dunkOnIT]

#10416 is the basic implementation of auto accept