Announcing the start of SMF 3.0 development
November 05, 2023, 07:55:26 PM Posted by Sesquipedalian on November 05, 2023, 07:55:26 PM in Announcing the start of SMF 3.0 development | 27 CommentsHello everyone,
We have a couple of important announcements to make regarding SMF development.
First, @shawnb61 has recently decided to step down as lead developer. We're sad to see him leave that role, but the good news is that he will still be around as a contributor. I will be taking over the role of lead developer in the interim until the next team elections in July 2024. Thanks, shawnb61, for all that you have done for us!
Second, the Dev Team also wants to let you know that we are making a significant change to the currently published roadmap for SMF. Specifically, we have decided not to create an SMF 2.2 branch. Instead, we are launching development of SMF 3.0.
The revised development roadmap is as follows:
The largest change in SMF 3.0 is a massive overhaul and modernization of under-the-hood code. Specifically, the code in SMF 3.0 Alpha 1 has been entirely rewritten to use modern, object oriented programming paradigms. This is a major update that helps ensure the continued longevity of SMF and, we hope, will also prove attractive to new generations of PHP coders who want to contribute.
Additionally, a great deal of effort has gone into maintaining backward compatibility with modifications and integrations that rely on integration hooks. Generally speaking, mods designed for SMF 2.1 and marked as "hooks only" in the SMF Customization database should be compatible out-of-the-box with SMF 3.0.
User facing improvements in SMF 3.0 will include a fresh, modern theme with better accessibility for users with various disabilities, improvements to the likes system, easy anonymization upon account deletion (important for GDPR), and more.
To help ensure a timely release, the development roadmap for 3.0 will remain tightly defined. As always, the timeline for the release is "when it's ready" (so don't bother asking
) but our intention is to stick closely to our roadmap and release once those goals are reached. We might add some more features and changes to the roadmap beyond those already listed, but a convincing case will need to be made for any such additions.
We have a couple of important announcements to make regarding SMF development.
First, @shawnb61 has recently decided to step down as lead developer. We're sad to see him leave that role, but the good news is that he will still be around as a contributor. I will be taking over the role of lead developer in the interim until the next team elections in July 2024. Thanks, shawnb61, for all that you have done for us!
Second, the Dev Team also wants to let you know that we are making a significant change to the currently published roadmap for SMF. Specifically, we have decided not to create an SMF 2.2 branch. Instead, we are launching development of SMF 3.0.
The revised development roadmap is as follows:
| Release | Functional Updates | Technical Updates | Maintenance Focus |
| 2.1.5 |
|
| |
| 2.1.6 |
|
|
|
| 3.0 |
|
|
|
The largest change in SMF 3.0 is a massive overhaul and modernization of under-the-hood code. Specifically, the code in SMF 3.0 Alpha 1 has been entirely rewritten to use modern, object oriented programming paradigms. This is a major update that helps ensure the continued longevity of SMF and, we hope, will also prove attractive to new generations of PHP coders who want to contribute.
Additionally, a great deal of effort has gone into maintaining backward compatibility with modifications and integrations that rely on integration hooks. Generally speaking, mods designed for SMF 2.1 and marked as "hooks only" in the SMF Customization database should be compatible out-of-the-box with SMF 3.0.
User facing improvements in SMF 3.0 will include a fresh, modern theme with better accessibility for users with various disabilities, improvements to the likes system, easy anonymization upon account deletion (important for GDPR), and more.
To help ensure a timely release, the development roadmap for 3.0 will remain tightly defined. As always, the timeline for the release is "when it's ready" (so don't bother asking
) but our intention is to stick closely to our roadmap and release once those goals are reached. We might add some more features and changes to the roadmap beyond those already listed, but a convincing case will need to be made for any such additions.Comments
Sounds useful. 
Awesome, awesome, awesome.
@Sesquipedalian great work man, great work.
[offtopic]
I must say I am confused by the min version for 3.0 being 8.0 if 2.1.6 is adding php 8.3 support... I guess my question is really why target a version that is about to drop security support?
[/offtopic]
Guess it's time to knock the dust off
@Sesquipedalian great work man, great work.
[offtopic]
I must say I am confused by the min version for 3.0 being 8.0 if 2.1.6 is adding php 8.3 support... I guess my question is really why target a version that is about to drop security support?
[/offtopic]
Guess it's time to knock the dust off
Quote from: Tyrsson on November 05, 2023, 10:08:56 PMI must say I am confused by the min version for 3.0 being 8.0 if 2.1.6 is adding php 8.3 support... I guess my question is really why target a version that is about to drop security support?
SMF 2.0's maximum supported PHP version is 8.0. Pegging SMF 3.0's minimum supported version to PHP 8.0 is intended to ease the upgrade path for forum admins that are still running SMF 2.0. We might decide later to raise the minimum PHP version requirement to something more recent, but for the time being that is where we have put it.
Quote from: Sesquipedalian on November 05, 2023, 10:46:06 PMMakes sense.Quote from: Tyrsson on November 05, 2023, 10:08:56 PMI must say I am confused by the min version for 3.0 being 8.0 if 2.1.6 is adding php 8.3 support... I guess my question is really why target a version that is about to drop security support?
SMF 2.0's maximum supported PHP version is 8.0. Pegging SMF 3.0's minimum supported version to PHP 8.0 is intended to ease the upgrade path for forum admins that are still running SMF 2.0. We might decide later to raise the minimum PHP version requirement to something more recent, but for the time being that is where we have put it.
Lovely!
Awesome news!
I'm excited for this! 
Great to see. I'm not all that familiar with OOP (at least not on the PHP side of things - I did some with Visual Basic / C# and ASP .NET years ago in college), but I'm always willing to learn new things. Looking forward to playing around with it more once the installer fixes get merged in.
Quote from: Oldiesmann on November 06, 2023, 09:37:41 PMGreat to see. I'm not all that familiar with OOP (at least not on the PHP side of things - I did some with Visual Basic / C# and ASP .NET years ago in college), but I'm always willing to learn new things. Looking forward to playing around with it more once the installer fixes get merged in.Install ran fine for me....
Quote from: Tyrsson on November 06, 2023, 10:26:21 PMQuote from: Oldiesmann on November 06, 2023, 09:37:41 PMGreat to see. I'm not all that familiar with OOP (at least not on the PHP side of things - I did some with Visual Basic / C# and ASP .NET years ago in college), but I'm always willing to learn new things. Looking forward to playing around with it more once the installer fixes get merged in.Install ran fine for me....
Not for me. See https://github.com/SimpleMachines/SMF/issues/7852
Quote from: Oldiesmann on November 06, 2023, 10:30:34 PMCheck my question on Discord. Might be relevant.Quote from: Tyrsson on November 06, 2023, 10:26:21 PMQuote from: Oldiesmann on November 06, 2023, 09:37:41 PMGreat to see. I'm not all that familiar with OOP (at least not on the PHP side of things - I did some with Visual Basic / C# and ASP .NET years ago in college), but I'm always willing to learn new things. Looking forward to playing around with it more once the installer fixes get merged in.Install ran fine for me....
Not for me. See https://github.com/SimpleMachines/SMF/issues/7852
I am looking forward to.
Hello, Great Announcement!!
Do you have any estimate on the possible dates of these implementations?
.. or when can there be a working version of SMF 3.0 for production?
aprox.
Do you have any estimate on the possible dates of these implementations?
.. or when can there be a working version of SMF 3.0 for production?
aprox.
And my day just got brighter! Great news.
Quote from: _sebas_ on November 10, 2023, 04:10:42 AMHello, Great Announcement!!
Do you have any estimate on the possible dates of these implementations?
.. or when can there be a working version of SMF 3.0 for production?
aprox.
You should know better than that.
The answer, as always is -- when it is ready.
Quote from: _sebas_ on November 10, 2023, 04:10:42 AMHello, Great Announcement!!It will definitely be done by Christmas.
Do you have any estimate on the possible dates of these implementations?
.. or when can there be a working version of SMF 3.0 for production?
aprox.
But not by Christmas this year.
Exciting news!
Is a Beta or so available?
No, not for a while yet. We're still working on Alpha 1.
You can download the code from GitHub (the "release-3.0" branch), but there aren't any frontend changes right now - it looks exactly the same as 2.1 (and features/functionality are the same as well - though not everything is working yet due to the code changes).
Great Job Guys, love that 3.0 includes recurring Calendar events!
Please don't forget to make it SEO Responsive with Indexing thanks 
"SEO responsive"? that's a stupid buzzword that means nothing.
SMF is already pretty SEO friendly (and uses canonical to assist with that) but **NO** forum is ever going to be SEO "great" because it's user written content - not curated content.
SMF 2.1.x (and even 2.0.x) already responsive design (as long as the custom theme or mods don't break it)
SMF is already pretty SEO friendly (and uses canonical to assist with that) but **NO** forum is ever going to be SEO "great" because it's user written content - not curated content.
SMF 2.1.x (and even 2.0.x) already responsive design (as long as the custom theme or mods don't break it)
This is encouraging news.
A big thank you to @shawnb61 for all your work to date and to @Sesquipedalian for stepping up.
Given the whole world is moving that way - though I'm NOT suggesting it be integrated as core functionality or anything - but the potential use of AI should be contemplated as a design consideration.
That is, making it so that AI tools can be integrated into SMF in future.
I know very little about it or protocols etc (is there a version of 'hooks' for AI? )but I think it's a potential opportunity which if missed may make SMF less attractive as an option,. if other forum software does take it into account.
Ok I've even lost myself now
Anyway keep up all the good work ladies, gentlemen and well, everyone.
A big thank you to @shawnb61 for all your work to date and to @Sesquipedalian for stepping up.
Given the whole world is moving that way - though I'm NOT suggesting it be integrated as core functionality or anything - but the potential use of AI should be contemplated as a design consideration.
That is, making it so that AI tools can be integrated into SMF in future.
I know very little about it or protocols etc (is there a version of 'hooks' for AI? )but I think it's a potential opportunity which if missed may make SMF less attractive as an option,. if other forum software does take it into account.
Ok I've even lost myself now
Anyway keep up all the good work ladies, gentlemen and well, everyone.
@Sesquipedalian What's your take on jQuery? Do you think 3.0 is a good opportunity to drop it in favor of vanilla JS? (I know we're heavily relying on it. caret/atwho/scrollbar/datepicker etc...)
Quote from: asmith on November 27, 2023, 03:02:53 AM@Sesquipedalian What's your take on jQuery? Do you think 3.0 is a good opportunity to drop it in favor of vanilla JS? (I know we're heavily relying on it. caret/atwho/scrollbar/datepicker etc...)
Personally, I'm indifferent. However, I'm pretty sure @live627 wants to remove it. If he (or anyone else) wants to make that happen by the time 3.0 is ready for beta testing, I won't object one bit.