Just want to clarify. SMF2.1 IS compatible with PHP7, the one that needs compatibility is SMF2.0.x.
And for the record, I'm not opposite to people asking questions, its the forms and the severe misinformation that has been spreading around.
However, what I am frustrated with the most is with people more than capable of helping out who instead prefer to just sit on their high thrones and start demanding things to get done the way they want it, when they want it. It also completely baffles me the way former contributors just automagically forget how slow and complicated things are around and inside the organization and how once they are out, suddenly SMF and everyone on it are a bunch of lazy bastards who are always completely wrong. Completely forgetting or perhaps conveniently ignoring, that they were once a part of SMF and their efforts (or lack thereof), for better or for worst, had contributed to the state SMF is today.
I know I am giving my best, while others preferred the easy way and quit, I decided to stay and keep the torch lit. That alone will keep me away from ******ing and whining to future SMF team members because I will know I did the best I could and I will be in peace with myself and what I accomplished.
But anyway, theres currently 3 major "milestones":
- SMF 2.1 Beta3
- SMF 2.0 PHP 7 compatibility.
- SMF 2.0 maintenance.
SMF 2.1 Beta 3 is ready, it was postponed to take care of the recent issues with 2.0.12 patch. But thanks to our awesome contributors it is still been developed quite nicely, I will never get tired of expressing my gratitude to them.
SMF 2.0.x compatibility with PHP 7 is been worked on, a preliminary patch has been tested and worked on. The real work is getting the full install to be compatible. It is semi-postponed until the issues with the .12 patch gets fixed. We've been also thinking whats the best course of action to take regarding PHP 7.1/7.2 too. Yes, theres not only the issue with been compatible with PHP 7, we need to also think about 7.1/7.2 and the deprecation of create_function().
SMF 2.0.13 has been created to fix the issues on .12 as well as other issues reported since then, its currently been tested on.
Can we be more open? yes of course we can, thats not the issue. The issue is, and always has been, lack of manpower. Heres a recent example and I can now telling this because it is no longer feasible to fulfill it.
Our inner roadmap, decided back in June, included releasing .12 that month, followed by Beta 3 two months later and PHP 7 compatibility at the end of the year. Starting 2017 with 2.1 RC1/Beta 4. As you can see, none of that was fulfilled on time. Several factors influenced it but the bigger ones was lack of time and lack of manpower.
We simply can't shout out our plans because it doesn't depend on us to fulfill them. Also, theres a bad or bad situation here:
Bad if you aren't open.
Bad if you are and cannot fulfill the expectations.
We just chose the "Lesser of two evils" option, it will be utterly demoralizing to publish your agenda and then failing to fulfill it, (it already is pretty demoralizing failing to fulfill an inner agenda) not to mention the pressure from the community will increase.
TL;DR: we aren't open to preserve our sanity.