Wednesday 08 September 2010 10:11:18 am

Don't get me wrong, I love eZ publish, but I just think it will not work. I think the license of eZ publish doesn't motivates community contribution to the point that a fork of eZ publish code could be done by the community. This is GPL code, and it's infect all the projects that a bigger code contributor could do with eZ, and we need to remember that all the work we do in the code will be eZ systems code. Only eZ systems can license private code.

A MIT license would be great, at least for extension development, because the question is, why developers would contribute to kernel if they can't publish some private extension that would help them buy food and beer to keep them alive to contribute to kernel code without having to pay for eZ systems a huge amount of money to a project ( eZ publish community edition ) made in part by them, because all the code contributed will be of eZ systems.

Maybe I'm wrong, this is just an opinion to start the discussion.

The actual model works just because eZ systems actually developes all, or at least almost all, the code, so it's right eZ systems keep all the rights to create a dual license system, including the extension license, but if community will develop some expressive part of the kernel, extension development should be MIT.

Just some thoughts, I can change my mind if I am missing some points.

eZ Publish Certified Developer: http://auth.ez.no/certification/verify/376924

Twitter: http://twitter.com/tcv_br

Wednesday 08 September 2010 11:08:57 am

I approve too and sounds great :)

But i think i ll not have enough time to do all i would like to do ..

Certified Developer (4.1): http://auth.ez.no/certification/verify/272607
Certified Developer (4.4): http://auth.ez.no/certification/verify/377321

G+ : http://plus.tl/dspe
Twitter : http://twitter.com/dspe

Wednesday 08 September 2010 10:51:20 pm

Hello all,

Since I missed last summer conference, I'm not quite up to date with the Enterprise vs. Community concept, and perhaps some other people out there aren't either. What would be the best source of information on that subject (except for this thread and latest ez.no news)?

I am especially interested in how (if at all) will both be synchronized with each other and whether Community edition will ever benefit from the Enterprise, or is it only vice-versa?

I'd be grateful for any links, articles, slides etc.

Big thanks,
Piotrek

--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu

Thursday 09 September 2010 12:46:56 am

I agree with Greg's additional criteria and the comment regarding the various regions of the world. It would be a shame to have a Europe "heavy" community board.

Andrew Duck, Executive Director, Quiqcorp Limited
eZ Certified Developer and Trainer.
Member of the Community Project Board
http://quiqcorp.com | http://twitter.com/andrewduck

Thursday 09 September 2010 2:39:35 am

I'll second Robin's comment, as familiarity with other eZ developers in generally should be positive as well. Not all eZ developers are active in the community, many more just work on the eZ platform all day employ by one of the eZ partners.

There should be a mix basically, to represent all users.

eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom

Thursday 09 September 2010 8:38:52 am

@Piotrek: I think the current information about that is quite incomplete now (at least to ppl who were not at the conf, such as myself), but that part of the job of the board will be setting up the missing procedures: not only there is commit rights on the code to be taken into account, but also management of documentation and translations, bug tracking and roadmap planning.

I see that the press release mentions "SCRUM (3 week sprints)", but I am sure that will be discussed a lot.

@Thiago: nothing prohibits any developer or partner to keep developing his code in (gpl'ed) extensions, if they fear that eZ Systems will piggyback their your work. But keep in mind that eZ is still producing gpl code for everybody in the community, and will continue to do so, even with the "Enterprise version" brand.

I think that right now the community is more hampered by the "though" participation processes (cannot commit, cannot manage bugs, cannot write docs) than by the licensing, and that we will be see a community participation increase. But of course everybody has his own opinions on licenses...

Principal Consultant International Business
Member of the Community Project Board

Monday 13 September 2010 4:16:34 am

The community edition will have its own board, so the roadmap will be one of the issues they deal with. Having a proper one could be hard; developers in open source projects often develop to scratch their own itch - thus the growth is often organic rather than planned. eZ Systems will have our own roadmap, but this is not (directly, at least) influenced by the community edition road map - although the sheer amount of it will probably have a large influence on the community edition too.

As for viability, I hope it will be a vibrant community and a great place to learn, test new ideas and technologies, gain skills, prototype web technlogies and for setting up personal and other minor sites. And, of course, when the time comes for larger projects, and you need something proven, tested, supported and stable the enterprise edition is the obvious choice. Like Fedora and Red Hat Enterprise Linux.

Trond Eivind Glomsrød
VP Engineering
eZ Systems

Monday 13 September 2010 5:58:46 am

Hi Tony,

Before updating the community with a synthetic reply, including all the feedback received, here is a short reply to you regarding potential divergences between the Community Project and the Enterprise Edition.

This is something the Board will try to reduce as much as possible, serving everyone's interests. All details on this question and a few other very practical and pretty interesting points there : http://share.ez.no/forums/discussions/feedback-regarding-the-ez-community-entreprise-announcement

Per the Community Project's direction in terms of "Product Management", see points 2 & 3 in the "Responsibilities" paragraph in the Governance draft. The Community Project Board will wisely control the direction of the Community Project, one of its most important of not the main responsibility.

Cheers !

--
Nicolas Pastorino
Director Community - eZ
Member of the Community Project Board

eZ Publish Community on twitter: http://twitter.com/ezcommunity

t : http://twitter.com/jeanvoye
G+ : http://plus.tl/jeanvoye

Monday 13 September 2010 6:38:56 am

One is being draft by yours truly, and i will soon publish this open to get everyone's feedback. I am really keen on hearing yours, and potentially adding of your ready-made charter into it. Stay tuned Tony !

--
Nicolas Pastorino
Director Community - eZ
Member of the Community Project Board

eZ Publish Community on twitter: http://twitter.com/ezcommunity

t : http://twitter.com/jeanvoye
G+ : http://plus.tl/jeanvoye

Wednesday 15 September 2010 6:15:04 am

This is a great initiative !

I have two comments to add :

1 - According to what I just read, there will be 6 members in the board. This is definitely a bad decision. You need 5 or 7 members so that when it comes to a difficult vote, you'll always have a majority.
No decision is a bad decision, nothing should stop the process.

2 - There should be one seat at the board for a non technical user. Somebody whose primary objective should be usability, ease of use.

My two cents !

;-)