proposal to nuke PHP from aurora-webui master branch

proposal 2.md

1. The PHP will not be removed from frozen branch so will still be available to end-users
2. The master branch can be tagged something to the effect of "pre-nuke" for ease-of-use instead of reading through the log
3. The PHP is incredibly difficult to maintain
   • It requires a non-strict PHP configuration
   • It only supports MySQL and cannot be used with SQLite
   • It assumes all tables are in one database, making it unusable when operating Aurora in grid mode with decentralised services
   • The code that interacts with the WebUI module is not centralised, making it difficult to maintain.
   • Translation is handled in a non-standard format.

By removing the original PHP from the master branch whilst retaining it in the frozen branch, less burden is placed on developers to maintain the PHP when modifying the c# module, freeing up time to develop independent website implementations such as [https://github.com/skidzTweak/Aurora-Sim-Joomla](skidz' Joomla implementation) and [https://github.com/SignpostMarv/Aurora-WebUI-GPL](Marv's standalone PHP implementation).

The further proposal is that once the independent implementations are feature-complete compared to the original website they can be cloned to aurora-sim team repos, potentially encouraging third-party developers to write further independent implementations for other platforms (e.g. WordPress/BuddyPress) or other languages (perl/python, or even an additional separate c# module that runs on Aurora!)

again, use IRC.