RE: mailing list division?



2 different ideas

first ideas would be to have it stay the same.
it is good for end users to talk to developers. end users are often good
testers. The more the testers the more bugs can be fixed.
An install document that is kept up to date would be important. That way a
user can use the document to install it and if it fails he/she can talk to
developers telling them:
a. there is something wrong with the code/tarball.
b. the document needs to be changed.


second idea would split it into 3 groups.
1 for install
1 for developers
1 for general

> -----Original Message-----
> From:	Sam Vilain [SMTP:sam@hydro.gen.nz]
> Sent:	Friday, February 05, 1999 3:57 PM
> To:	Fox, Kevin M
> Subject:	Re: mailing list division?
> 
> "Fox, Kevin M" <KMFox@mail.bhi-erc.com> writes:
> 
> > <thought my="$0.02"> 
> > The nice thing about having everything together is that, new users can
> talk
> > to developers directly with there install problems. The developers can
> see
> > what problems a user is having and fix up the code. Also having the
> users
> > see the developer discussions on things like usability allows the user
> to
> > give feedback on how a usability idea might work. The user is the one
> who is
> > going to use a feature, so it only stands to reason that he/she should
> give
> > some feedback on a feature..
> > </thought>
> 
> Out of interest, did you see my posting on this issue?  If so, what
> did you think of the idea I suggested?
> -- 
> Sam Vilain, sam@whoever.com         work: sam.vilain@unisys.com
> http://www.hydro.gen.nz                home: sam@hydro.gen.nz



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]