Yes, we will have a vote for new members and a few BUIPs before the end of this year (late Nov or early Dec).
Regarding the hard forks. I am aware of two:
We have already had a BUIP about SegWit2x, and that was rejected, which means our options are limited there apart from continuing to offer a non-segwit client which is 2MB compatible.
With the Bitcoin Cash HF there is no real argument against improving the difficulty adjustment algorithm. So the solution which is used in ABC is basically essential maintenance and therefore BU development have the right to adopt the same change. A BUIP could be raised by a member to reject the HF change, but I can't see a majority of BU members wanting to fork away from the Cash chain.
Do you have anything else in mind?
No nothing else in mind. Just wanted to set my reminder on my phone to check this BU forum sometime around the voting period, so I don't miss a vote. I wonder if we should have some kind of alert system for members (maybe email?) when a new vote is planned we can email members when an election is coming up or in progress.
Another solution would be to define multiple voting dates well in advance.
It would make the system a bit slower to react but if we have predefined voting dates every 3 months than it should only be an issue for emergency decisions.
I would even propose a scheme that will be valid every year. e.g. the first Sunday of February, May, August, November with a maximum duration of 5 days for each voting date.
@solex what do you think of this solution?
[doublepost=1508846912][/doublepost]On second though August could be problematic for some because of holidays and thus pushing it to September might be better.