suggestions for future QB64

[Fortran66]

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.

Your 2-cents is pretty much the way things have worked since 2007. The creator and first developer, Rob (Galleon) was a loan gun. He did an astonishing amount of coding on the project. For for whatever reason he was overly fond of using GOTO statements. That was a double edged sword. It helped him develop faster, because he had a good memory of the code, but after he left the project, well, I can imagine some of the shocked faces of folks who looked at the coding style. Luckily, Fell and luke jumped in, and handled it extremely well with the existing construct. That was probably around 2012 or 2013, I think. Anyway, Fell sure seemed to be tired of all the work involved, quit the project, is not coming back, and my guess is we will need to find someone like him if the project is to continue forward. As for fixing a few bug issues, that will probably get taken care of by those familiar with the project within this community. As for new platforms like mobile devices, I think that would require a re-write in JAVA. That's a tall task. Personally, I'd love to see a  version of QB64 to write mobile apps.

Pete

Pete,

If Fillippe is permanently out of the QB64 project, then who will maintain the Inform RAD?

John