Hi Andrew, On 25/04/18 02:38, Andrew Sullivan wrote: > Hi, > > No, a registration number will not be available under the plan, because > the prospective registrant won't actually be registered before payment. > Payment will be a necessary condition for registration. Without paying, > one won't be registered. > > I hope that's clearer. > That's clear. FWIW, I think that's another bit of a bad plan - I see no reason why the ability to buy a social ticket or not, or the ability to register a companion or not, would affect meeting income. So the above sounds to me like a plan that's going further than it needs to, and that may represent more change vs. current tooling and folks' processes than is needed. I'd ask that the IAOC re-consider those aspects. S. PS: I realise my workflow may be a bit of a corner-case, but I'm starting to regret that the IAOC didn't just bump the meeting fee and leave it at that - another US$100 or something on the fee could even work out cheaper for me compared to the time spent dealing more with my local bureaucrats... and for them having to deal more with me too of course;-) > Best regards, > > A > > -- > Please excuse my clumbsy thums > ---------- > On April 24, 2018 19:30:52 Brian E Carpenter > <brian.e.carpenter@xxxxxxxxx> wrote: > > On 25/04/2018 04:56, Andrew Sullivan wrote: > .... > There is one assumption in your question, however, that is worth > emphasising: you can't get a social ticket until you're registered, > and under our plan "registration" means "paid registration". This > also applies to companion registrations to the meeting, &c &c. There > will simply be no such status as "registered but not paid", even if > registration may take many weeks so that payment can be processed > separately from sign-up. > > Digging a bit deeper into that, there are other cases where you need > a registration number well before the meeting - registering for > certain types of side-meeting, for example. So will the registration > *number* be available while payment is pending? (An implementation > detail, I know, but probably better debugged in advance.) > > Brian > > > >
Attachment:
0x5AB2FAF17B172BEA.asc
Description: application/pgp-keys
Attachment:
signature.asc
Description: OpenPGP digital signature
