The code changes can all be developed and tested offline on the test/model website .... it can be done using a snapshot of the current database.

I'm unsure at the moment how long the MVP changes will take, but it's feasible that I may be able to get it done before 6 months. Depends if I run into any significant compatibility issues, which I don't really expect. Testing chews up a fair bit of time, because any logic changes in the phpBB3 viewing and posting code need to be reflected in the MVP code, I'm not sure yest if there are any significant program flow changes in the new phpBB3.3.11 . If the MVP changes are not correct, database consistency errors can occur.

The MVP code is mainly contained in 4 php files and a handful of display template files. I tried to keep it as separate as possible, while still maintaining the ability to set up the MVP forum and topics using the same logic flow used in the main forum software.

The trickiest bit is working out whether the dBase upgrade will work correctly with the MVP topics pointing to a set of new polll tables which do not exist in the standard phpBB3 database. Depends whether the Base update routines do any consistency checking.

Camel forgot to feed the hamster.

If it's a space thing, there are probably 8 or 9, maybe up to a dozen, of my posts that are pretty ordinary and could be deleted

but that coincides with the app having more and more intrusive ads