Forgive me, if this is presumptuous, but if it were me, this is more or less what I would do.
- Work out a roadmap of the future of what you guys want it to be, and what you guys want it to become.
What do you use QB64 for? Do you want to modernize it? Do you want it stay the same? Do you want it to include more platforms. What is one small feature or bug fix that you want the most? Perhaps take specific polls on what people are happy with, and what they are not happy with.
- Work out who your core dev team is, and what their constraints are.
As far as I know, we are almost all hobbyist and working for free, because we enjoy it. Whomever takes the reigns of developer, will need to balance this project and life.
- Decide on a programming style.
Not everyone is at the same skill level, and we don't all have the programming style. Outline some best practice's in the Wiki.
- Prioritize bug fixes and refactoring
This is a no brainer. The current code base is not very approachable, and can be difficult to track down bugs.
- Trickle out small features somewhat regularly, and work on big features as time allows.
This shows the community that you are active and as you get better with the code base, new features will be quicker to add.
This is my 2 cents.
