Looking forward to when it's available. I'm wondering though, why has this model been adopted rather than the traditional open source practice of code being visible at all stages during development?
First, using traditional to describe anything open source does not make sense to me. How is anything related to open source old enough to be considered traditional? The free software business is just beginning to define itself IMHO. We live in a time when things are changing at an ever increasing rate, and open source is still a relatively young concept that is both gaining acceptance in and making enemies amongst traditional organizations and businesses. But this too will change as time goes on, along with the transparency of MODx development as the foundation and community grow.
Second, I've personally written this entire new code base from scratch, going through great lengths and personal sacrifice to architect a vision of how to evolve MODx and maintain a sane level of compatibility and familiarity. And until I feel enough of that vision is in place, I do not want it in the average users' (or competitors') hands; simple as that. I feel if I expose too much of the work in progress too soon, not enough of the future vision will be revealed or meet expectations based on current MODx experience, forming a chasm between MODx pre- and post-0.9.7 that could be hard to cross.
If you want to contribute to development, documentation, or otherwise before it's made available publicly, feel free to contact me via PM to request a place on the team. As with most "successful" (forget "traditional") open-source projects, our community is open to the public and free to join, but commit privileges and core team membership are based on a meritocracy.
Topic: Downloading Revolution via SVN (Read 51727 times)
