jdarcy@pinocchio.encore.com (Jeff d'Arcy) (11/19/89)
Many people in this newsgroup have expressed the feeling that Encore is not being responsive to their concerns, and some have suggested that this group could serve as a vehicle for greater communication between Encore and Encore's users. I think everyone agrees that this would be a Good Thing (tm), but there has been little discussion about the specifics of how to get from here to there. Since nobody else seems foolhardy enough, I guess I'll try to get this ball rolling. I'm trying to light a fire in one of Encore's internal newsgroups in the hopes that some action will be taken before I'm strung up for being a loudmouthed pain is the <bleep>, but the really important input has to come from outside. What can Encore do to make more effective use of this medium? Would you like to see: (1) product/standards/business announcements? (2) announcements about major enhancements/fixes to existing products? (3) discussions of issues involving products under development? It is often possible to make predictions about upcoming products without making commitments. Would people like to see this sort of thing, *knowing* that the predictions are uncertain and do not represent any commitment? Or would people rather see "just the facts"? Will management go for it? Will I ever shut up? Again, I'd like to point out that I'm a developer (I don't do product support or sales for obvious reasons) using some of my own time to address an issue that I take rather personally. I do *NOT* speak for Encore or for any other Encore employee. Jeff d'Arcy OS/Network Software Engineer jdarcy@encore.com Encore has provided the medium, but the message remains my own
rcowh@dropbear.co.rmit.oz (Warwick Heath) (11/20/89)
From article <10404@encore.Encore.COM>, by jdarcy@pinocchio.encore.com (Jeff d'Arcy): > What can Encore do to make more effective use of this medium? Would you like > to see: > (1) product/standards/business announcements? > (2) announcements about major enhancements/fixes to existing products? > (3) discussions of issues involving products under development? > Jeff d'Arcy OS/Network Software Engineer jdarcy@encore.com > Encore has provided the medium, but the message remains my own All of the above sound like good ideas. It would also be nice if there was made available a list of known major problems (Encore SPR's) so that we know which bugs are being worked on, and which are ones that have never before seen the light of day. Good to see someone at Encore taking an interest, thanks, warwick heath. ACSnet: rcowh@dropbear.co.rmit.oz CSNET: rcowh@dropbear.co.rmit.oz.au ARPA: rcowh%dropbear.co.rmit.oz.au@uunet.uu.net BITNET: rcowh%dropbear.co.rmit.oz.au@CSNET-RELAY UUCP: ...!uunet!munnari!dropbear.co.rmit.oz.au!rcowh Royal Melbourne Institute of Technology, P.O. Box 2476V, Latrobe St, Melbourne, 3000, Australia
rxxgap@minyos.xx.rmit.oz (Greg Price) (11/20/89)
> .......... in the hopes that some action will be taken before I'm strung up > for being a loudmouthed pain is the <bleep>, but the really important input > has to come from outside. > The problem is we don't get information, etc. Your management needs to understand this. > > What can Encore do to make more effective use of this medium? Would you like > to see: > > (1) product/standards/business announcements? > (2) announcements about major enhancements/fixes to existing products? > (3) discussions of issues involving products under development? > > that the predictions are uncertain and do not represent any commitment? > yes, yes, yes, fine! It appears our problems are the same, even overseas, we don't get any info from our local supplier. Control Data have a system called solver. This system contains release material for the past, present and future as well as bug reports from customers and replies from the company. Control Data sites have logon id's for the system. When you get a problem you search the database for anything matching on keywords topics etc., if you cant find anything then you report it, they either supply a work around, patch, defer it to the next release and so on. The system allows you to make suggestions for changes, improvements, and new features in another section. It works very well! Even internal staff in different sections report problems with it. This system saves the same bug being tracked down and reported multiple times, even avoiding possible problems. Enough said, I think everyone should understands. Comments anyone? More ideas? I trust things will get better as it is almost intolerable presently! ---------------------------------------------------------------------------- Greg Price, Computer Centre, Systems Programmer. Royal Melbourne Institute of Technology, P.O. Box 2476V, Melbourne. 3001. ACSnet: rxxgap@minyos.xx.rmit.oz (124 Latrobe St., Melbourne.) CSNET: rxxgap@minyos.xx.rmit.oz.au Australia. ARPA: rxxgap@minyos.xx.rmit.oz.au@uunet.uu.net BITNET: rxxgap@minyos.xx.rmit.oz.au@CSNET-RELAY PHONE +61 3 660 2934 UUCP: ...!uunet!munnari!minyos.xx.rmit.oz.au!rxxgap FAX +61 3 663 5652 ----------------------------------------------------------------------------