Bringing Evo back to life again

307 Posts

virtualbear Reply #461, 14 years, 3 months ago

hi,

@Stefanie, yep, i have nearly the same thing in mind, what i understand reading this post is clearly that evo has no future (at least, as i said, under modx trademark)

@microcipcip, you're right, i've read that too, but according to what we've seen so far, i.e, post from the team, probably sincere, saying things like "we're looking forwards to the next evo..." and what really happened i would put my money on no or an irrealistic upragde path from evo
furthermore, i would add that even if there is an upgrade path, revo being part of cloud core (yes, i've read "the best from evo and revo" too

), i'm not that sure i'll want to upgrade

i'm not saying that cloud will not be a great tool (after all, they made evo once!) and i sincerely wish the best to the team and modx future.
i'm just saying we now all know the team's project for it, no real... evolution because they have other things in mind, it's their absolute right of course as it's ours to keep it alive, whatever reincarnation this may imply, after all, that's what great in the open source world and thanks to the team for having choosen this way for modx.

good luck to modx cloud, long life to evo's future

have swing

réfléchir avant d'agir

898 Posts

chucktrukk Reply #462, 14 years, 3 months ago

I hope they give us their blessing to continue with Evo under MODx trademark. Then work with us to provide an upgrade path to MODx 3.

Chuck the Trukk
ProWebscape.com :: Nashville-WebDesign.com
- - - - - - - -
What are TV's? Here's some info below.
http://modxcms.com/forums/index.php/topic,21081.msg159009.html#msg1590091
http://modxcms.com/forums/index.php/topic,14957.msg97008.html#msg97008

MODX Staff
10,725 Posts

opengeek Reply #463, 14 years, 3 months ago

We would love to give this group our blessing. And we've been making every possible effort to help get this effort reintegrated to the official Evo project, but the current state of Stefanie's 1.1.dev branch is not promising. There are a number of FATAL errors and breaking changes immediately visible, the sample site is completely broken, and I'm not going to continue reviewing this branch until it is stable and some clarity/documentation is provided on ALL of the changes that are being included in it.

Unless someone wants to start taking important pieces and submitting sane pull requests to have them included in a more practical and manageable manner? Please?!

FWIW, the LGPL license discussion in the wiki should be closed. You cannot relicense the Evolution code base without rewriting ALL of the code from scratch, nor is MODX interested in having the GPL license changed on the MODX branded product.

Jason Coward
Chief Architect @ MODX
http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek

☆ A M B ☆
1,231 Posts

yama Reply #464, 14 years, 3 months ago

OK, I make modifications as far as I can do it.
However, I will not actively demand in future because I read new declaration of Ryan at the blog.
I look forward to MODX 3.

172 Posts

TimGS Reply #465, 14 years, 3 months ago

Quote from: opengeek at May 30, 2012, 05:21 PM

We would love to give this group our blessing. And we've been making every possible effort to help get this effort reintegrated to the official Evo project, but the current state of Stefanie's 1.1.dev branch is not promising. There are a number of FATAL errors and breaking changes immediately visible, the sample site is completely broken, and I'm not going to continue reviewing this branch until it is stable and some clarity/documentation is provided on ALL of the changes that are being included in it.

You've never had a site pass through intermediate 'broken' stages during development?

Quote from: opengeek at May 30, 2012, 05:21 PM

FWIW, the LGPL license discussion in the wiki should be closed. You cannot relicense the Evolution code base without rewriting ALL of the code from scratch, nor is MODX interested in having the GPL license changed on the MODX branded product.

I personally agree with you (regarding GPL) and have said so on that discussion. However no one has any business saying the discussion should be closed.

-- Tim.

172 Posts

TimGS Reply #466, 14 years, 3 months ago

Quote from: microcipcip at May 30, 2012, 11:03 AM

Quote from: Ryan
There will also be well defined migration paths for both Evo and Revo to MODX 3.0.

This leaves developers sadly in a bit of a quandry, as we've heard that before with the Evo->Revo upgrade facility that never happened.

If we tell clients that Evo/Revo have a future in MODX 3, and the upgrade facility doesn't happen, we have a problem.

-- Tim.

4,149 Posts

splittingred Reply #467, 14 years, 3 months ago

You've never had a site pass through intermediate 'broken' stages during development?

The policy at MODX has always been that Pull Requests for MODX products that cause breakage will not be integrated until they fix or resolve the issues.

shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com

☆ A M B ☆
1,231 Posts

yama Reply #468, 14 years, 3 months ago

Hello, Shaun.
I want to say a word.

https://github.com/modxcms/evolution/pulls
There is not the clear answer for these. I waited for the answer from you for two years.
I learned how to use GitHub so that you said.
Nevertheless there is not an answer all the time.
I think that you are the people who do not keep a promise.
If you keep a promise, I send as many pull requests.
I asked you many times.

However, I still have the will to cooperate. This is because MODX is necessary.

☆ A M B ☆
1,231 Posts

yama Reply #469, 14 years, 3 months ago

https://github.com/sjstoelting/evolution/downloads
I want you to try this if interested.
This is shabbier than Revo, but is more useful than present Evo.
But I think that this does not need to adopt it.
I am glad if useful for new MODX3.

☆ A M B ☆
1,231 Posts

yama Reply #470, 14 years, 3 months ago

I bring up one wife and two daughters in MODX.
My family is happy. I thank you.