Tuesday 07 November 2006 11:06:39 am
Hi Xavier Thanks for your input.
What about bugs ?
When the bugs where managed into ez publish, they created a contrib category. Unfortunately, the bugs reported them never found their way to the real devs of the contribs.
Can you clarify this? I'm not sure I understood you correctly.
Don't know about the new bug system, but it'd be great if it'd be used for the projects as well.
We should ask the opinion of eZ systems about this. I haven't seen anything in wIT that can't be done with eZ publish and some additional PHP libraries. In any case, a project bug system (or more general: a tracking system) will not be included in the first release due to time constraints.
Moreover, as the number of contrib grows, it's really difficult for a new commer to know what extensions are really used or just there as exemples or to solve a very specific point.
It'd be nice to be able to qualify them better. Some extensions are so usefull they should be "core" flaged. Don't know if this is some kind of tag system that users can update, or if we need a few moderators/editors on this section or a mix of that.
I agree there need to be better ways to qualify the projects. Maybe we can make a hierarchical categorization of extensions, the project owner can choose more than one category his extension belongs too. For example you will have categories for the intended end users: * portal user (...) * administrator (ezjaxx, Search form in admin content/browse.tpl, http://ez.no/community/contribs/hacks/update_class_from_command_line, ...) * template writer ( http://ez.no/community/contribs/hacks/dynamic_debug, http://ez.no/community/contribs/hacks/attribute_show_identing_and_colors ) * extension developer (http://ez.no/community/contribs/applications/extension_manager) You could also have categories with different eZ publish plugable types, this would be great to search for example code:
* workflow event type
* datatype
* module
* view
* operation
* fetch function
* module policies
* search plugin
* file upload handler
* extended attribute filter
* notification event type
* notification event handler
* content action handler
* content edit handler
* template operator * template function I can go on summing up categories for a while :-)
Another thing that'd be great is to ease the update/installation process.
It would be brilliant if I could automatically see the list of contribs and download a contrib into my extension area from my back-office.
Moreover, it'd great to see if there has been an update on the extensions I have installed.
I completely agree, installing and updating extensions should be more Mozilla-like. But this requires some serious improvements to the package manager. I don't know (yet) if eZ has any plans for this.
independent eZ Publish developer and service provider | http://blog.coomanskristof.be | http://ezpedia.org
|