Tuesday 23 September 2003 9:32:13 am

I think it would be helpful for all if the plans and timeline for upgrades are made more transparent. Before the summer conference we were promised many times that notifications would be made ready but this didn't happen and now seems forgotten.

Personally i would like to see the notes made at the saturday morning session of the summer conference as a document here for the community to discuss. Along side that can be a timeline of what will be implemented and when, given priorities etc.

Is this possible? Any other comments from others at the conference?

paul

Tuesday 23 September 2003 10:15:05 am

There are always too many 1-minute jobs getting in the away :)

We do need transparency. Those of who were at the conference know that there was great discussion on saturday morning about the community at ez.no. We came away with the impression that lots will be fixed and improved.

Unfortunately those who were not there do not know this and are likely confused at missing promised features. When questions are asked those present at the conference are confused about how to answer because ez are silent.

If we can't see what will be fixed tomorrow and what will be fixed in three months time then support account are affected. Questions regarding accelerating the development of some feature will be far more useful with the knowledge that it will be some time before that feature starts to work... Hope you see what i mean here. As support questions are costly we want to ensure our money is spent asking the right questions.

Paul

Thursday 25 September 2003 2:40:51 am

Paul, we're sorry for little feedback. We've been very busy with the 3.2 release so we haven't had time to work on ez.no before this week.

We will later today publish an article about the 3.3 release which was dicsussed on the summer conference.

We should do the same with ez.no community upgrades.

--bård

Documentation: http://ez.no/doc

Thursday 25 September 2003 3:39:15 am

When you say that the bug reports are worse now, do you mean the bug lists or the bug view?

For the list we could cut the version column since it's not that important, maybe also integrate type, status and resolution into the bug text.

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq

Thursday 25 September 2003 4:20:59 am

We cut down on the displayed characters for the list to make sure it doesn't break or fill up the entire screen. Now too much space is used for the other attributes, I think the list needs a bit more tweaking.
Also this should encourage people to write shorter summaries, we have the description for more details.

As for the edit field bug, it should be fixed (at least my edit box is OK :)
http://ez.no/developer/ez_publish_3/bug_reports/edit_fields_sometimes_ends_up_in_half_size

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq

Thursday 25 September 2003 6:25:38 am

Shifting attention back to the original message:

I agree with Paul that we really really really need to know what to expect in the way of changes to these forums, and ez.no as a whole. As one of those people who was not able to make the conference I have little idea what was discussed. While I post quite a few suggestions, and at times receive positive feedback from the eZ crew or other community members, it is rare to see the feedback incorporated into actual changes.

I know you all are extremely busy, and obviously need to focus on for-profit work to ensure eZ publish continues to exist, but I worry that you are falling into the same pit that so many open source projects have fallen prey to before: lack of communication with the community supporting you.

It really doesn't take much time to list all of the suggested feedback, assign a priority and a date to each item and post a running list. In fact, I bet there are several of us who would volunteer to compile the list for you! As has been mentioned before, major changes could be made in short order on your part; these changes would have a massive impact on the community, and ultimately the success of eZ publish.

We are a community that wants to support you, but without information we don't know what to expect. Without some simple additions/upgrades, we aren't as effective as we could be.

Please help us help each other and you,

Alex

Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]

<i>When in doubt, clear the cache.</i>