Re: [hylafax-users] new community site

[Bill Binko <bill-sender-4b2fd6@xxxxxxxxx>]

Gentlemen,

I really considered not posting on this topic.  My thought was that this 
would just blow over like the rest of the disputes between you two, and 
that we'd get back to business as usual.  However, at this point, I'm 
going to go ahead and speak up.

First, the reasons Lee states for why he created the new site are very 
valid, and he's not the only one bothered by them.  For example:

1) Commercial content on the hylafax.org site

While the "hardware" box on the main page is marginally OK, the
information on the "Support" page is clearly inappropriate for a ".org"
site.  It speaks in the first person ("we can help you there too!") as if
ifax.com IS the hylafax community and that there are no other choices for
support.

Looking at other community sites (apache.org, python.org, zope.org, 
postfix.org, php.net) shows nothing similar to this type of text.  Of 
particular note is php.net.  Zend.com is very much THE vendor for PHP.  
However, even they only have a single link under "Related Sites".

The current text makes it look like iFax.com _benefits_ from the 
open-source version of Hylafax being difficult to use and support.  Now, 
I've worked with Darren in the past, and found him to be very helpful 
solving open-source Hylafax problems, and in setting up the wiki, etc.  
However, that doesn't change the _appearance_ created by the support page.

2) Slow releases

My client has unforunately abandoned the HylaFAX releases, and we now
build RPMs from CVS HEAD whenever there's an update we need.  This has
even required emails to the list and directly to Lee asking, "Is CVS HEAD
currently stable enough to deploy?"  It's simply not reasonable to have 8+
months between releases and consider this an active project.

3) Stale content on the hylafax.org site

The FAQ was updated in 2003, the latest press release is 2002, 18 dead 
links on the Links page, Troubleshooting last updated in 2002.  This 
complaint, I believe, is not disputable.

4) Limitations of iFax.com's community support

Let's face it: Sourceforge raised the bar for open-source community sites 
and tools.  It is completely possible for an open-source project to get 
better hosting, bug tracking, releases, testing environments, etc. at 
sf.net than can be built and supported by your average "commercial 
sponsor."  Moving to sf.net is an excellent idea that should be discussed.


However, with all of that being said, I can't stand the solution Lee 
chose.  It DOES confuse newcomers to the community.  Many will come to the 
sf.net site through Freshmeat which will certainly list it first (since 
OSDN owns them both).  There is no link back to the original hylafax.org 
site, and no clarity that this is not THE official Hylafax site.

It also reeks of plagiarism, copyright infringement, hijacking, and a
general lack of class (I mean, you even stole their frog!).

Lee, if your point was to get those of us who agreed with you to speak up, 
congratulations, but Please don't continue on this path.  I know that our 
turn-around time on Fax issues would triple without your rapid responses, 
and I don't want to lose that.  However, this solution is just plain bad.


Darren, if you're redoing the website anyway, please take into account the
fact that your current commercial content is deemed (at least to some of
us) inappropriate, and my be counter-productive.  Also, please realize
that maintaining the wiki, the lists, the cvs server, etc., while a great
deal of work, might not provide the same benefit it used to in a world
with sf.net in place.  This may be a good time to reconsider how iFax.com
can best contribute to the community, and get back those hours for 
development.

Also (to everyone), I think we should consider an odd/even approach to 
releases similar to Linux and many other open-source projects.  Let Lee 
manage the experimental releases and iFax.com manage the stable releases.  
That would make 8-month intervals much more managable for those of us in 
the field.

Bill


____________________ 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*