Downloading Revolution via SVN#

Hi,

I'd like to download Revolution in its current state to start playing with and investigating the new admin area. However, the SVN trunk appears to be 0.9.6 rather than Revolution and when exploring the branches it asks for a username and password, which I don't have. Is it possible for someone who's not a member of the coding team to check out Revolution?

There will be a public preview very very soon ... working on a few more issues on the installer (packaging/transport mechanisms).

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?

Quote from: pbowyer at Jun 17, 2007, 10:12 AM

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.

It's a chicken and egg situation - I think I want to contribute to development, but until I see the code, structuring, the direction it's taking etc I can't say "I do". But unless I say "I do" I cannot see the code...

Considering the successful projects of the last 5-10 years there is a tradition of having the source code open for review, whether development branches or currently released code. If this hasn't been the case, I've missed any signs of it In the world of open source something that has recurred over a few years can (I argue) be called a tradition, as the time period for defining a behaviour as a tradition must be affected by the speed of change within the situation in which it's located.

Anyhow it's an unnecessary disagreement, all we're disputing is what is normal/traditional in open source.

Slightly off topic but will modx 0.9.7 final come with a brand new website ?
Btw. Maybe after releasing for exemple 0.9.6 final the trac could be opened for bugfixes only and people could submit patches that can be reviewed by the core maintainers and maybe a code guidline needs to be published
Just my 2 cents

You should indeed see a new support site. We want to make things more consistent and easier to use.
We also want a more transparent development workflow, too, and that should become more apparent in the very near future. And we definitely want code input and suggestions from lots of sources, too!

Quote from: CoolGoose at Jun 19, 2007, 01:22 AM

Btw. Maybe after releasing for exemple 0.9.6 final the trac could be opened for bugfixes only and people could submit patches that can be reviewed by the core maintainers and maybe a code guidline needs to be published

Trac will likely not be used moving forward; our bug tracker is fine for our current purposes of reporting bugs, requesting features, and submitting patches. Official code guidelines and best practices will be made available with 0.9.7.

Any updates ?

Bump