This site has been archived. To learn more about our current products Ibexa Content, Ibexa Experience, Ibexa Commerce head over to the Ibexa Developer Portal

eZ Community » Forums » Discussions » Developers, developers, developers!*
expandshrink

Tuesday 30 November 2010 2:50:43 pm - 14 replies

» Read full blog post

Introduction

Software big guns like Microsoft, Google, Apple, etc. wouldn’t be so spread across the globe if they did not think about the developers who work on their platform, so eZ Systems should do the same thing - take special care about eZ platform developing potential.

* Paraphrasing Ballmer’s energy in http://www.youtube.com/watch?v=KMU0tzLwhbE

Tuesday 30 November 2010 3:12:54 pm

Hi Ivo and thanks for this very motivational speech,

Our daily synchronisation gets me to promptly understand your post as a strong call to the whole eZ Community : let us move together towards a killer eZ Publish, Content Management Platform.

I, and presumably the share.ez.no team, will join your call by bringing additional information on most of the points you are raising. Both eZ, and the teams of volunteers helping our community have great ideas in the pipeline.

So stay tuned for an additional information delivery, following-up on this post !

Cheers, and yes : Let's go eZ Community !

Tuesday 30 November 2010 3:32:15 pm

Thanks for this motivational post, full of ideas !

I particularly like your idea to include community extensions in the community edition, as most of time developers tend to develop their own ones covering features that are well-known. Besides, this is the idea of the eZ France project.

I also like your "guru master class" idea, so as the way to identify these guys on the community portal (a special badge on the forum posts ? blunk.gif Emoticon)

Tuesday 30 November 2010 3:57:48 pm

I particularly like your idea to include community extensions in the community edition, as most of time developers tend to develop their own ones covering features that are well-known. Besides, this is the idea of the eZ France project.

Hi Jerome,

Can you tell me more about the eZ France project?

Tuesday 30 November 2010 4:29:32 pm

This is actually a ready-to-use distribution of eZ Publish. It means that everything is pre-installed and pre-configured, for french speaking developers.

It comes with the last translation file, a flat MySQL dump (eZ Publish installed with eZWebin), a virtual host example and several useful extensions :

  • NovenINIUpdate
  • eZClassLists
  • eZObjectRelationBrowse
  • RedirectOperators

It would be nice to have such a distribution with the community edition, with common extensions that are really useful (Swark, GGSysInfo, GGWebservices, JVMonitoring - for simple HTTP monitoring, SQLIImport...). This would avoid developers to always reinvent the wheel for each project (no offense happy.gif Emoticon)

Tuesday 30 November 2010 4:33:27 pm

It would be nice to have such a distribution with the community edition, with common extensions that are really useful (Swark, GGSysInfo, GGWebservices, JVMonitoring - for simple HTTP monitoring, SQLIImport...). This would avoid developers to always reinvent the wheel for each project (no offense happy.gif Emoticon)

This is exactly what I want to see with the community edition happy.gif Emoticon Of course we can all have some local versions, etc. but the community version should be "ready to use" as much as possible.

Tuesday 30 November 2010 6:19:24 pm

Well, we could start out with a poll / forum dedicated to the extensions that could be bundled. For some functionality there might be more than one candidate.

Otoh, we could instead focus on a coding sprint where we improve the way to install extensions from a source repo - just like it is possible using pear or apt-get

- create an extension that turns an ezp install into a pear server

- create an extension that builds in the pear client and shows available extensions from the chosen servers

Prerequisite is of course a better release-management/versioning-and-requirements infrastructure on projects.ez.no (and possibly within the eZP packaging system itself)

Besides bundling, there is also some advantage in unbundling. Things I think we should remove from the kernel in the community version: webshop, rss feeds

Tuesday 30 November 2010 11:14:23 pm

I second the idea about bundling quality community extensions into community edition of eZP.

We at Netgen were discussing such an idea for a long time, at least for our own installations (as Jerome said, not to reinvent the wheel each time we start another eZ Publish project).

This could also be a well deserved recognition for developers of those extensions (to have your own extension included into community version), and could give additional push for developers to improve and maintain those extensions.

Friday 03 December 2010 6:13:18 pm

I think we can first read the report posted by Nicolas: http://www.waterandstone.com/downloads/2009OSCMSMarketShare.zip

This file has some numbers about the CMS market share, I think we could try to research them to discover what eZ is missing, mainly Joomla, WordPress and Drupal, and answear question about their strong and weak points. We know a member that knows Joomla very well, Robin, I think he could talk about something why Joomla is so pop and eZ not. I am finishing my graduation now but I will help here as soon as possible.

Modified on Friday 03 December 2010 7:34:45 pm by Thiago Campos Viana

Friday 03 December 2010 8:33:00 pm

I think we can first read the report posted by Nicolas: http://www.waterandstone.com/downloads/2009OSCMSMarketShare.zip

This file has some numbers about the CMS market share, I think we could try to research them to discover what eZ is missing, mainly Joomla, WordPress and Drupal, and answear question about their strong and weak points. We know a member that knows Joomla very well, Robin, I think he could talk about something why Joomla is so pop and eZ not. I am finishing my graduation now but I will help here as soon as possible.

We should research competitors, that is for sure, but I think Joomla and WordPress are not in that group. IMO Drupal is.

Saturday 04 December 2010 5:30:48 pm

I am not sure that the community should engage in is comparative analysis of competitors as starting point for "going forward". There is a company, with paid employees, for that blunk.gif Emoticon

The community should instead focus on

1. defining the itches than can / have to be scratched, based on their current, actual needs (I am sure we're in no lack of those)

2. scratch them

Looking at other cms to see how they solve problems is more part of step 2 than 1...

...but of course any community activity is welcome in end!

Saturday 04 December 2010 8:14:21 pm

I like the simplicity of itch->scratch.

There are few kernel hacks that we routinely do - I'm sure everyone has these - off the top of my head, we almost always add a receiver attribute check to kernel/content/collectinformation.php, i.e.

$dataMap = $object->attribute( 'data_map' );
$receiver = $dataMap['collection_email']->content();

So that you can define a receiver per form.

We also add subtree to kernel/classes/eznodeviewfunctions.php so we have that as a template override option.

What I think is that maybe there should be a forum where people can propose changes like this and people can maybe vote the idea up or down or say why the code is/isn't a good idea, make code change proposals etc. Sort of a community code review/wishlist.

After a certain time period then maybe it could be encorporated...

Of course, this would only really work if the code changes were included with the request for inclusion otherwise it'll become an endless "fix my problemz for free pleaze."

Of course, I could just open an issue and try and affect change that way... but I'm thinking an up/down vote would show the relative interest in the change too.

Monday 06 December 2010 9:59:44 am

I am not sure that the community should engage in is comparative analysis of competitors as starting point for "going forward". There is a company, with paid employees, for that blunk.gif Emoticon

I agree, I was just emphasizing that if we (community, ez systems, partner company,... ) comparing features of eZ with some other CMS we should compare it rather with Drupal, not with Joomla or Wordpress

Monday 06 December 2010 10:02:38 am

I like the simplicity of itch->scratch.

There are few kernel hacks that we routinely do - I'm sure everyone has these - off the top of my head, we almost always add a receiver attribute check to kernel/content/collectinformation.php, i.e.

$dataMap = $object->attribute( 'data_map' );
$receiver = $dataMap['collection_email']->content();

So that you can define a receiver per form.

We also add subtree to kernel/classes/eznodeviewfunctions.php so we have that as a template override option.

What I think is that maybe there should be a forum where people can propose changes like this and people can maybe vote the idea up or down or say why the code is/isn't a good idea, make code change proposals etc. Sort of a community code review/wishlist.

The whole point of community version is to make it easier for you, me or some other community member to make this sort of changes in the eZ code happy.gif Emoticon That is "boosting invention"...

Monday 06 December 2010 5:03:41 pm

The whole point of community version is to make it easier for you, me or some other community member to make this sort of changes in the eZ code happy.gif Emoticon That is "boosting invention"...

Yeah, I guess that's the point, what we really need is some sort of (easy) process to make this happen.

expandshrink

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from