So sign me up for the community edition. I would really like to put some time and effort in this project! And let’s get a move on! Because we can we complain but that’s not going to change anything. Let’s create a vision where the community version should go, setup a roadmap and get people involved…

All the best for your new life.

As Tony said, you will be missed, both as an eZ Systems employee, and as an hyperactive community member. I second you on the fact that the community aspects of eZ’s underlying model were not dealt with diligently enough in the past months. I suspect this is due to the fact that eZ Systems, as a company, must be healthy. This in order to keep innovating, creating valuable software, and backing up its products with professional services. This makes the eZ ecosystem way more solid and sustainable, including the community, than it was in the past, and we will all benefit from this, from the eZ-beginner hacking its first extension, to the long-run senior architects, basing their business on eZ products. eZ products can *not* be without the community, eZ is aware of this, more than ever. The focus is slowly but surely coming back 100% to the product, meaning that the community shall be back in the limelight and involved in a deeper fashion…it has always been the case in eZ’s heart…but not systematically put in practice lately.

Keep all up your excellent work !

What you experienced a few month ago is something I feel familiar, albeit experienced before you.

As an open source tool, I find frustrating the speed of evolutions, and yes, ez is becoming a bloatware, and less and less agile.

Might be also a lack of resources as put from ez.

Anyway, that’s been a pleasure to meet you and your work has been greatly appreciated. Keep in touch.

X+

I wish you luck and enjoyment in whatever you choose to do next.

Have fun

Tony

I also think a fork is not necessary, because a lot of corporate client need a opensource product with a strong company behind.

There are very experience partners that could handle improvement in ez publish core.

I like the way typo3 seems to work together with developers. Perhaps ez system should move to a similar concept…

Sad to hear that you are leaving.. First they sold Odessa office, now you are leaving.. Hope eZ can handle it.

Good luck in your future work!

The solution could be in deriving a procedure for partners to submit code to the main product, all within commercial, technical or whatever goals of eZ Systems … Bertrand?

“The eZ philosophy of openness and information sharing is still the basics guideline for the company, employees and Ecosystem” is a quote from the ez.no/company page. It is concerning to see the number of communication issues highlighted in the comments here and the lack of eZ Systems to recognise they no longer meet their own vision “Help Businesses Manage, Publish and Share information”.

With a hazy roadmap, very little public disclosure or community input being valued, a broken release cycle (especially evident in 2008) and an ever shrinking development team we have to wonder as partners, community members and clients of eZ Systems what their intent really is at this point in time. For a company who I expect to produce software it is disheartening to see development teams shrinking and the focus continually being shifted to other projects (ez flow, ez find, ez now, ez components).

I agree with Piotrek in hoping that eZ Systems recognise and deal with the underlying issues in eZ Publish before we are all forced to move on to other options that better meet the increasing needs of our clients.