[hylafax-devel] Re: Pep talk

[Joe Phillips <jaiger@acm.org>]

On Mon, Jul 31, 2000 at 01:10:26AM -0400, Darren Nickerson wrote:
> 
> Okay folks,

<stuff snipped to save bandwidth>

> Any and all suggestions welcome.

Here's my general take on things.  I'll note that currently I am not a
HylaFAX user but I have configured/used the server and have implemented
the network protocol in Java.  I have followed the HylaFAX mail lists
for a few years now.

As someone else mentioned, the website is stale.  There are many old and
out-dated "news" items and I don't get the impression that it is very
actively maintained.  I say this particularly because I have offered
news items in the past that still have not made it to the site.  I
announced my Java package that implements the HylaFAX network protocol
to the mail lists and the webmaster.  I've seen no indication that the
message was received.  No post on the mail list and nothing on the website
indicating my class library as client code.

To me, this is annoying.  To outsiders and newcomers this makes the mail
list and website "quiet" possibly indicating a dead project.  They may 
think there aren't any new developments going on.  Nobody's going to
get into a dead project.

Now, as for the HylaFAX package itself.  To move forward with bug fixing,
we need to take inventory of all bugs/problems/etc, prioritize them and
set to fixing them one by one.  I volunteer to host a bugzilla database
for HylaFAX if the group is ok with using that product for bug tracking.

I suggest that we then make a "beta" release of the current CVS with the
README pointing users to http://bugs.hylafax.org/ for problems.  Once
bugs have been logged and categorized we can move forward and solve the
problems.

What does the group think?

-joe


____________________ HylaFAX(tm) Developers Mailing List ____________________
 To unsub: mail -s unsubscribe hylafax-devel-request@hylafax.org < /dev/null