From: Scott K. <sc...@ki...> - 2003-07-06 02:18:28
|
On Sat, 2003-07-05 at 18:22, TiMax wrote: > On 05 Jul 2003 12:40:20 -0500, Scott Kindley wrote: > > > > How about having each support site volunteer one member to join and keep > > active on this email list. Then perhaps prior to public releases support > > sites can have all the information needed about upcmoing releases prior > > to it hitting the street. > > > > In other words our support sites should be activly involoved in Envo > > development instead of sitting back and waiting for things to be spoon > > fed to them. > > > > Just as Envo as a whole activly engages our end user community so too > > should we as developers engage each other! But not after there is a > > problem.....instead before a problem exists. > > > > Just my two cents worth! > > > > Zoom > > You are right Scott, but ... when one member ask you .... i have a problem and you answer ..... what is your problem > .... and this member insteand to tell you what is his problem go in his site and start stupid flames ...... > > ...... sorry, but i think this member is a problem ... > > > TiMax > You can't please everyone all the time. But we can communicate better! That is one of the reasons we have this development email list. All developers should use it to keep up on information and share information. It's silly to think that developers are going to be up to date on progress if they choose not to utilize the resources at their disposal. That is all I was suggesting. But we can't create rules or structure REQUIREING developers to use it such as what Denver eluded to in his previous post. That just pushes people away. So...who is this person your referring to Max. I can talk to him/her and explain this to them. This issue is really getting blown out of proportion. It's nothing more than simple mis-communication. So instead fo everyone trying to figure out who to blame...why don't we instead decide to bridge the mis-communication by inviting this person into the development list? Zoom |