Look, it’s absolutely fair to say MODX3 is late. I’m not denying that. We could talk forever about all the dramas from the past and mistakes in prioritisation and planning that have been made, pointing fingers in all directions, and not get a single thing done in the meantime.
I want to look and move forward.
The current situation is that we have a third alpha released after an amazing sprint and an increase in core contributors. MODX3 is here, and has actually been for a little while.
It’s not yet considered “done” or “stable”. Some say that the alpha doesn’t go far enough in replacing legacy code, some don’t like certain design changes, some are disappointed that features are missing from the alpha which were promised by people who vanished from core development after their funding ran out. It’s a compromise, and work is ongoing to continue making it better.
There is one thing I know for certain. Every single person involved with the core in one way or another, (past, future, and present) is aware this release is taking longer than anyone wants it to. It’s totally unnecessary to shame them and tell them to their face (or behind their back) that they’re not meeting expectations.
Saying things like “dead” or “limping along” actively chips away at the motivation of people putting in their best effort for the community’s benefit. I can’t stress that enough. By stating something like that, even if you perceive it to be true or a fair characterization, you’re actively making it harder for the people that care to continue to care about the work they’re doing. Prefacing a comment with “I have the utmost respect for…” doesn’t absolve that.
Basically… why should I bother donating my time and energy to make MODX better, or even just give the slightest damn about what goes on, for people pronouncing it dead? Might as well take up woodworking instead.
Now to avoid even more speculation… I’m not at that point (woodworking does sound fun), and am committed to MODX and getting MODX3 ready, but I am fed up with doomsayers actively making things worse, best intentions be damned, hence me pushing back so heavily against this type of discussion.
Bob, you’ve made a tremendous positive impact over the many years. I would not be a core developer without your help on the forums a decade ago, even though you yourself are not actively involved on a core code level. Everyone using MODX has at one point gotten help from you on the forum or found what they were looking for on your site. I hope you’ll join me in encouraging this amazing community to explore similar ways to have a positive and lasting impact on the project like you have.
MODX 3 is not going to be complete this month or next month, but there’s movement and active contributors doing what they can. The more contributors, testers, cheerleaders, documenters etc that we can get involved for this massive undertaking, the better.
Right, perhaps my cough communication cough wasn’t clear.
Hypothetically, if I have 2 hours available for MODX work, I can either spend 2 hours reviewing a few pull requests that actually improve MODX, or fix issues/implement a new feature. Or I can spend those 2 hours drafting an article that talks about about what other people did. I can’t do both with only 2 hours, so I need to prioritize.
Personally I consider my skills as a developer (and role as integrator) most valuable to the project, so I mostly focus on technical stuff.
Everyone involved with the project makes similar choices, based on their own skills. Currently that leans more towards development time for most because of the technical changes in MODX3 and wanting to get that finished, so more time for communication would either need to be “added to the pool” by someone new, or it would come at the cost of development time from existing contributors. It’s always a trade-off, but I wouldn’t put it to the extreme of “never get it finished”.
I’d personally love to see new people step up and take on the role of regularly communicating progress on GitHub to a wider audience (eg on MODX.today) on a regular basis (e.g. biweekly/monthly). Ideally someone that’s a naturally good writer so they can get it done in half the time it would cost me or another developer.