The meeting points for this meeting:
listen to that one, there are some additional questions by 
It's far too early to commit to any date, but we are hoping to ship it by january/february
It's mostly a dev issue I face when working, I wasn't sure if others were seeing it too, so I figured I'd ask. We'll sync on it via a gitlab issue.
@arcangeThere is no penalty for removing a vote. But you don't get voting power back.
validation check is "hours * recurrence < 730 days"
when hours = 24 (1 day) => max recurrence = 730 (i.e. 2 years)
when hours = 720 (30 days) => max recurrence = 24 (i.e. 2 year)
Why has the limit been set in days and not in total number of occurrence?
I got a bit confused by the question, but basically this limitation is in place to prevent someone from creating a recurrent transfer and letting it exist forever on the chain (as this induces costs for witnesses and api node operators) (it's for the same reason that a proposal fee increase was introduced past a few months).
We want a recurrent transfer to only exist for a maximum of 2 years so that's why this limit was put in place, As rc costs get better defined, we may increase that value if there is a need for it.
Some back and forth there, it's good to listen to the debate but tl;dr: we don't think it's worth the time investment and risk.
Meetings have shifted quite a bit in the past few iterations due to vacations etc. We will now keep a very stable schedule of every two weeks and if we have nothing to say for one iteration, we'll just skip that one.
This should give the meetings more predictability, so the next one will be dec 6 at 5pm UTC :)