Projects organisation

Next topic

Author	Message
paul bolger	Monday 29 November 2010 10:12:43 pm I'm finding the projects section a bit unwieldy: There seem to be lots of projects which haven't been updated to work with 4.xx, and a lot more which have not got past the naming stage. Would it be possible to change the project area browsing so that one could only look at projects which actually have content, and which work with current versions of Ez? It'd also be nice to have a voting system to gauge interest in older projects which need updating. Paul Bolger
Nicolas Pastorino	Monday 29 November 2010 11:48:12 pm Hi Paul, Very good remarks. The lack of usability, and relative relevancy/uptodate-ness of many a project makes it hard to find the very relevant ones at a certain point in time. This was spotted by the share.ez.no team and added to the todo (see point 4/ here) already. Where it reads "Cleaning-up projects.ez.no", "making it a killer forge" is meant :) So your points would be (please correct/amend) : Better search/findability Better metadata : compatibility, Reputation : rating, reviews (extending/enhancing the currently existing one) Let us make this a question to all, the daily users like you always have good ideas. Thanks for triggering this, -- 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
paul bolger	Tuesday 30 November 2010 3:11:24 am Thanks Nicolas I think that casual users should only be able to see projects which work with 4.xx, and that it should be harder to see older ones. I also think projects which are still in the planning stage (no files available) should be in a special 'waiting for flight clearance' area. Sorry, had a much longer and more considered reply but hit "Add reply" (bottom button's off the screen), lost the lot, and can't be bothered spending another ten minutes re-typing. I've done that twice now. It'd be good if "Add reply" could check if there is already text in the editor and prompt the user if there is. Paul Bolger

Author

Message

Monday 29 November 2010 10:12:43 pm

I'm finding the projects section a bit unwieldy: There seem to be lots of projects which haven't been updated to work with 4.xx, and a lot more which have not got past the naming stage.

Would it be possible to change the project area browsing so that one could only look at projects which actually have content, and which work with current versions of Ez? It'd also be nice to have a voting system to gauge interest in older projects which need updating.

Paul Bolger

Nicolas Pastorino

Monday 29 November 2010 11:48:12 pm

Hi Paul,

Very good remarks. The lack of usability, and relative relevancy/uptodate-ness of many a project makes it hard to find the very relevant ones at a certain point in time. This was spotted by the share.ez.no team and added to the todo (see point 4/ here) already. Where it reads "Cleaning-up projects.ez.no", "making it a killer forge" is meant :)

So your points would be (please correct/amend) :

Better search/findability
Better metadata : compatibility,
Reputation : rating, reviews (extending/enhancing the currently existing one)

Let us make this a question to all, the daily users like you always have good ideas.

Thanks for triggering this,

--
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

paul bolger

Tuesday 30 November 2010 3:11:24 am

Thanks Nicolas

I think that casual users should only be able to see projects which work with 4.xx, and that it should be harder to see older ones.

I also think projects which are still in the planning stage (no files available) should be in a special 'waiting for flight clearance' area.

Sorry, had a much longer and more considered reply but hit "Add reply" (bottom button's off the screen), lost the lot, and can't be bothered spending another ten minutes re-typing. I've done that twice now. It'd be good if "Add reply" could check if there is already text in the editor and prompt the user if there is.

Paul Bolger

eZ debug

Timing:	Jan 18 2025 02:56:48
Script start
Timing:	Jan 18 2025 02:56:48
Module start 'layout'
Timing:	Jan 18 2025 02:56:48
Module start 'content'
Timing:	Jan 18 2025 02:56:49
Module end 'content'
Timing:	Jan 18 2025 02:56:49
Script end

Main resources:

Total runtime	0.4126 sec
Peak memory usage	4,096.0000 KB
Database Queries	58

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0066	588.0469	152.6406
Module start 'layout'	0.0066	0.0030	740.6875	39.4844
Module start 'content'	0.0095	0.4016	780.1719	548.4297
Module end 'content'	0.4111	0.0014	1,328.6016	12.1563
Script end	0.4125		1,340.7578

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0030	0.7233	16	0.0002
Check MTime	0.0012	0.2907	16	0.0001
Mysql Total
Database connection	0.0013	0.3037	1	0.0013
Mysqli_queries	0.3571	86.5602	58	0.0062
Looping result	0.0004	0.1067	56	0.0000
Template Total	0.3830	92.8	2	0.1915
Template load	0.0026	0.6276	2	0.0013
Template processing	0.3804	92.1972	2	0.1902
Template load and register function	0.0001	0.0289	1	0.0001
states
state_id_array	0.0009	0.2216	1	0.0009
state_identifier_array	0.0007	0.1783	2	0.0004
Override
Cache load	0.0021	0.5107	24	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0006	0.1469	2	0.0003
Fetch class attribute name	0.0008	0.2060	5	0.0002
XML
Image XML parsing	0.0011	0.2560	2	0.0005
class_abstraction
Instantiating content class attribute	0.0000	0.0027	6	0.0000
General
dbfile	0.0009	0.2223	22	0.0000
String conversion	0.0000	0.0017	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
3	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
5	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezxmltags/link.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/link.tpl
1	content/datatype/view/ezxmltags/li.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/li.tpl
1	content/datatype/view/ezxmltags/ul.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/ul.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 16 Number of unique templates used: 8

Time used to render debug report: 0.0002 secs