More specifically, the so-called "lock" on 1.3 for the past few years is where I see the biggest problem.KaylaKaze wrote:Actually, I was constantly hearing "It's coming in 1.4" since I first started using MT 7 years ago. Frankly, it's a massive problem. Either start posting some code for 1.4 or just call it dead so some of us who still care about enhancing MT can fork from the existing 1.3 codebase without having to worry about our work becoming obsolete by a new version.
It has deterred a good number of people from contributing, all in the name of not doing anything more with a 1.3 that "should be done with 1.4" (or 2.0 as that is now generally understood to be the next "real" version of MT coming from the fingertips of core developers we hear very little from these days).
That entire "1.3 lock" concept needs to be set aside yesterday.
People should continue to be encouraged to submit patches and mods for implementation in 1.3 until such a time as there is an actual 2.0 in the wild for users and volunteer developers to actually focus on.
Further, I feel that Az should explicitly relinquish his duties with 1.3 and *actively* seek out someone who is willing to carry the torch. His participation in the community and project over the last year very much mirrors the disintegrating focus Trevor once had... where much time was also lost waiting for a transition to present itself.
As for forks... I know there are at least 3 forks already out there:
Lee's unreleased fork.
The b90 beta that has been promoted very often by core community users for default use.
Lord Ashe's Plugin fork.
That is not a positive sign.