Re: [hylafax-users] [hylafax-devel] Re: new community site

[Chris Parsons <chrisp@xxxxxxxxxxxxxx>]

>-----Original Message-----
>From: hylafax-devel-bounce@xxxxxxxxxxx
>[mailto:hylafax-devel-bounce@xxxxxxxxxxx]On Behalf Of Darren Nickerson
>Sent: Friday, 4 November 2005 3:39 AM
>To: Lee Howard
>Cc: hylafax-users@xxxxxxxxxxx; hylafax-devel@xxxxxxxxxxx
>Subject: [hylafax-devel] Re: [hylafax-users] new community site


>As a side point, I'm also concerned about 
>fragmentation/duplication/confusion in the bug tracking database. You'll be

>asking people to file bugs on Lee Howard releases on the Lee Howard bug 
>tracker?

This is what concerns me the most. And the mailing lists. Its hard enough
for noobs to find the information that they want about setting up hylafax
around their problems from ONE mailing list, let alone 2 seperate one. Lee,
what do you propose to do to solve the fragmented bug tracking and mailing
list dificulties?

I contribute to this community when my input is possibly helpful.. (Which
lately hasnt been often, people obviously use the archives!) However, since
Hylafax is the stable product that it is, I havent had to draw on the
knowledge of this community very often at all, since our hylafax
installation has been running quite happily for a few years now.
Considering this, I see no benefit for myself or other employees of InfoTec
Communications using the sourceforge site, because I see no benefit in it
for us. Plus I also believe the source forge tools to be inferior to what
hylafax already has set up.




Regards,



Chris Parsons
InfoTec Communications

____________________ HylaFAX(tm) Users Mailing List _______________________
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
 On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*