Re: [hylafax-users] new community site

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

"Darrick Hartman" <dhartman@xxxxxxxxxxxxxxxx> wrote:

> There are some reasons why I might want to code forked (as was brought up 
> on this list last week, the mysql logging).  But as I mentioned, I was 
> able to rework a few of the scripts with perl and get everything working 
> for my client's purposes.

Darrick,

I don't follow you here. If someone hung a patch on the hylafax.org bugzilla 
tomorrow that was deemed to be commit-worthy by a majority of developers 
(through public, open discussion) then it would absolutely be committed to 
the current code base. A variety of people might commit it, including but by 
no means limited to Lee. A fork isn't needed for that ...

HylaFAX development on hylafax.org is open, democratic and by concensus. It 
always has been since the site was founded. You wouldn't need a fork to get 
any feature added, you'd just need someone to do the work, and you'd need to 
have the patience to guide the patch through 'the process', accepting 
comments/review/feedback from the community etc.

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