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

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

"Lee Howard" <faxguy@xxxxxxxxxxxxxxxx> wrote:

> You've thrown up the "fork! fork!" flares and overreacted.

I don't think so. I'm happy for there to be another website dedicated to 
HylaFAX, I simply object (as have others) to it looking so similar to the 
hylafax.org one, and most of all I object to you singlehandedly doing 
releases and announcements as "The HylaFAX Development Team" without any of 
the regular democratic release process that has been our tradition. If you 
want to be a part of the development community, you have an obligation to 
work within that community. If you want to go outside that community and 
arbitrarily decide to do releases when it suits you, then I think you should 
make it clear that this is your initiative, not that of the hylafax 
developer community.

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? Clearly they'll also be relevant to the current CVS HEAD version of 
HylaFAX. Once your team has reached their concensus (or more likely you have 
decided for them) will you then re-post the bugs to bugs.hylafax.org? Or 
will you be asking the hylafax-devel mailing list to consider bug reports on 
your bug tracker, and referring to your bugs when you commit changes to the 
hylafax.org CVS?

I would appreciate clarification on this matter. I do not favor two bug 
trackers, of course, but if there is to be two of them, we'll need to know 
how you expect "The HylaFAX Development Team" to interact with it.

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