Re: [hylafax-users] New Community site

["Darren Nickerson" <darren.nickerson@xxxxxxxx>]

> Consider, if you will, the case of a competitor to iFAX.  How frequently 
> do you think that an iFAX competitor will invest time and money in 
> developing fixes and features for HylaFAX, or other kinds of 
> contributions, and then return them to the community?

They will do so for the same reasons that we do:

1. It's the right thing to do
2. It's very difficult to maintain your own private version of HylaFAX - 
much more efficient to mainline all the changes you can
3. The 'many eyes makes all bugs small' is a much better way to do 
development
4. The BSD license works
5. See 1.

> Consider a vendor or a manufacturer that does not want to attract 
> attention to its underlying technology.  It shouldn't be all that 
> surprising, either.  iFAX knows of this situation well:
>
>  http://www.ifax.com/content/view/26/66/

Thanks for pointing out HylaCAP. We're proud of that - we're committed to 
helping companies get their code into the open source version of HylaFAX!

It's true, there are companies (we work with several) who don't want anyone 
to know they have HylaFAX embedded in their product. I don't see how the 
existence of iFAX Solutions, or Howard Silvan and Associates, or any of the 
other consulting companies out there have any impact on this whatsoever.

> Please understand that the following were the issues that I was trying to 
> address by doing what I did:
>
> 1) I feel like the on-line information and documentation at hylafax.org 
> has become outdated and stale, and recently contributing to it as I have 
> done in the past has been impeded by the hylafax.org registrar, 
> necessitating a move away from hylafax.org

You and I are in agreement that the content was too stale. Whose 
responsiblity was it to keep it fresh? Volunteers have come and gone but 
recently there have been very few updates to the site. We attribute this to 
how hard it is to add content, and recognizing that it wasn't going to get 
redone all by itself, we recently announced iFAX's commitment (as a public 
service) to completely redo the site and make it easier for people to 
contribute. As for anyone impeding your contributions to the website, well 
I'm confused. You have full commit privileges to the CVS repository for the 
website, and you have been steadily updating the how-to and we have been 
steadily pushing out those changes for you.

> 2) some kind of code release needs to happen much, much more frequently 
> for code exposure and in order to assist the user community in getting 
> fixes and features easily in a more timely manner, this kind of release 
> probably would need to not undergo the same "release process" in order for 
> the frequency to be as needed

The 4.2.2 release came out on 26 September. On 26 October the release cycle 
for 4.2.3 was started. If you want a quick release cycle now that it's 
underway, please just advocate for it on hylafax-devel. If nobody disagees, 
it will happen. It's unfair to say all release cycles have been painfully 
slow. Some have been very slow, but they haven't all been bad!

-Darren


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