Forums / Suggestions / Roadmap and priorities...

Roadmap and priorities...

Previous topic

Suggestions

Next topic

Author	Message
mikael lindqvist	Monday 01 September 2003 2:44:53 pm I just noticed the thread: http://ez.no/developer/ez_publish_3/forum/suggestions/ezno_forum_notification which partly answers my post below ------------------------------------------------------> This is probably an old question and I do not demand a detailed answer or justification on the pros and cons BUT hear me out, please :) As a beginner starting to learn the system it's crucial to keep a close contact with what's going on, both within the community and from the developers side. Communication and availability of quality information are the two keywords. Transparency is the oil that makes everything tick (I guess). FORUMS -------- Therefore I think it's VERY important that eZ give the community (and themselves) some addional functions accompanying the forums. 1. Subscribe to threads with email notification system This is time-saving and crucial if you gonna get some response on replies to new and particularly old threads. 2. Archive all posts per user (I would like to be able to list all posts made by a particular user). ROADMAP --------- Maybe I'm wrong but from my side I would very much appreciate to see what's going on behind the scene. I do not demand a complete day-to-day list with all the details of job-efforts but rather an easy overview of which projects are being worked on and planned completion date. Quite like the bug-report list. For example, is a more "flexible" messageboard being worked on and if so which features are planned and estimated release date? Pros with a roadmap is: 1. Quality of information is improved and benefits are quite a few. Cons with a roadmap is: 1. May put developers under too much pressure (particularly if they fail to deliver on time).
Paul Forsyth	Tuesday 02 September 2003 12:14:35 am At the conference a few weeks ago major community improvements were discussed and ez are in the process of working out how to implement these. Changes will be incremental. But, a good roadmap summarising what we spoke about and when changes will be implemented would be good to publish now. I do know that some of the ez community developers are on holiday at the moment. Ez, is it possible to announce your intentions about a roadmap and when changes will start to filter into the ez.no site? This will help address many peoples concerns. Paul
Paul Borgermans	Tuesday 02 September 2003 9:34:39 am I guess the right time will be after the beta2 release tomorrow which also means a feature freeze. A personal report from the meeting (features targeted for 3.3 or 3.4, the ez crew will decide so take it with a large grain of salt): - pdf/rtf export (the manuals will be out with 3.2 final) - speed enhancements - full featured import/export xml filter for data too - passing variables between templates (maybe sooner than 3.3) - standard features of 2.2.x series including polls, calendar etc as seperate packages - webdav interface to full class attributes (partly 3.2 I hope) - more groupware features (also better forums) - a spellchecker, server-side (not only Bård needs one :-) ) - more notification/collaboration handlers and types - probably permissions on attribute level - class inheritance of some sort - slick design of "standard" templates (Pia & co are great designers) - lots of little things I did not write down Furthermore, the community part on ez.no will be improved step by step, including: - periodical (weekly?) summaries of important posts - focus on new members: need fast answers to simple questions (we all have to help with this) Some more watermouthing from our side: - soon you will find a contribution that is a first step into more xml support: an xslt filter (operator to be used in templates on text fields). - later on we'll probably develop a new "general xml datatype" which will be able to hold things like OOo presentations (not documents yet, OOo is not yet pure xslt-able). Some code appeared in the php developer magazine for a kick start on this. Smile, tomorrow its beta2 day -paul eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans

Author

Message

mikael lindqvist

Monday 01 September 2003 2:44:53 pm

I just noticed the thread:

http://ez.no/developer/ez_publish_3/forum/suggestions/ezno_forum_notification

which partly answers my post below

------------------------------------------------------>

This is probably an old question and I do not demand a detailed answer or justification on the pros and cons BUT hear me out, please :)

As a beginner starting to learn the system it's crucial to keep a close contact with what's going on, both within the community and from the developers side. Communication and availability of quality information are the two keywords. Transparency is the oil that makes everything tick (I guess).

FORUMS
--------
Therefore I think it's VERY important that eZ give the community (and themselves) some addional functions accompanying the forums.

1. Subscribe to threads with email notification system

This is time-saving and crucial if you gonna get some response on replies to new and particularly old threads.

2. Archive all posts per user (I would like to be able to list all posts made by a particular user).

ROADMAP
---------
Maybe I'm wrong but from my side I would very much appreciate to see what's going on behind the scene. I do not demand a complete day-to-day list with all the details of job-efforts but rather an easy overview of which projects are being worked on and planned completion date. Quite like the bug-report list.

For example, is a more "flexible" messageboard being worked on and if so which features are planned and estimated release date?

Pros with a roadmap is:
1. Quality of information is improved and benefits are quite a few.

Cons with a roadmap is:
1. May put developers under too much pressure (particularly if they fail to deliver on time).

Paul Forsyth

Tuesday 02 September 2003 12:14:35 am

At the conference a few weeks ago major community improvements were discussed and ez are in the process of working out how to implement these. Changes will be incremental.

But, a good roadmap summarising what we spoke about and when changes will be implemented would be good to publish now.

I do know that some of the ez community developers are on holiday at the moment.

Ez, is it possible to announce your intentions about a roadmap and when changes will start to filter into the ez.no site? This will help address many peoples concerns.

Paul

Paul Borgermans

Tuesday 02 September 2003 9:34:39 am

I guess the right time will be after the beta2 release tomorrow which also means a feature freeze.

A personal report from the meeting (features targeted for 3.3 or 3.4, the ez crew will decide so take it with a large grain of salt):

- pdf/rtf export (the manuals will be out with 3.2 final)
- speed enhancements
- full featured import/export xml filter for data too
- passing variables between templates (maybe sooner than 3.3)
- standard features of 2.2.x series including polls, calendar etc as seperate packages
- webdav interface to full class attributes (partly 3.2 I hope)
- more groupware features (also better forums)
- a spellchecker, server-side (not only Bård needs one :-) )
- more notification/collaboration handlers and types
- probably permissions on attribute level
- class inheritance of some sort
- slick design of "standard" templates (Pia & co are great designers)
- lots of little things I did not write down

Furthermore, the community part on ez.no will be improved step by step, including:
- periodical (weekly?) summaries of important posts
- focus on new members: need fast answers to simple questions (we all have to help with this)

Some more watermouthing from our side:
- soon you will find a contribution that is a first step into more xml support: an xslt filter (operator to be used in templates on text fields).
- later on we'll probably develop a new "general xml datatype" which will be able to hold things like OOo presentations (not documents yet, OOo is not yet pure xslt-able). Some code appeared in the php developer magazine for a kick start on this.

Smile, tomorrow its beta2 day

-paul

eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans