Zeta is currently at risk / in the process of being removed from Incubator stage because of lack of activity (no release).

The plan was originally to do a small release with full bc from eZ Components, and what is holding that back right now is that several unit tests are broken because of a phpunit upgrade and no one being active moving the project forward. So someone/several needs to get the release process going, and on that part I have no overview on what needs to be done.

We had some talks about this with James Pic and Tobias Schlitt in Lisbon for the eZ Winter conference this year. And the outcome was that there is a clear need for stakeholders to step up and take ownership (maintainer ownership, not forking the code) over the Components they depend on.eZ is willing to do this as well, but we don't have much capacity at the moment, so that would be strictly restricted to the components we use ourself in eZ Publish and ezp-next.

Those Components that do not have an owner when the focus (if ever) turns to Zeta 2.0 will not be part of 2.0.Changes for 2.0 that seemed reasonable when it was discussed was:

Change to namespaces and PSR-0 autoloading

Use a light dependency injection container instead of singeltons

Optional: improve api & performance (some API breaks could be allowed as long as a clear upgrade path is provided)

Would you, or do you know anyone in the eZ community that would be willing to contribute?

Update: Looks like Zeta can be moved to Github and use the infrastructure there.

But might be a need to set up a light organization around Zeta that can take ownership of github account, do release management of releases, setup webpage (github pages?) and CI infrastructure (travis CI ?).

But do you propose that a Russian-speaking / writing community should take this ownership, sounds like that move would exclude a lot of potential contributors?