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

[Tom Rymes <trymes@xxxxxxxxxxxxxxxx>]

On Nov 3, 2005, at 2:34 PM, Lee Howard wrote:


> Hello Tom,
>
> I understand that some people may be unhappy with there being  
> HylaFAX mailing lists on Sourceforge because they feel like they're  
> going to "miss out" on something useful that goes on there but yet  
> they refuse to register.  I think that every person in that  
> situation needs to evaluate whether or not they're really  
> interested in what is discussed on those lists.  If they are, then  
> register.  If they're not, then don't.  It's not like the traffic  
> in your in-box will double.  It's not like the topic is any  
> different.  It's merely a different list.

Well, that's true for everyone who knows about both lists, but it's a  
pain in the ass to keep track of where a given topic was discussed,  
and I don't see any advantage to a second list, given that there is  
no moderation on the existing list. I do understand what you are  
saying regarding the web site. This is not to mention stupid things  
like searching via google, etc is a pain in the ass, too b/c you have  
to specify site:hylafax.org and site:/hylafax.sourceforge.net or  
whatever. I just think that for the mailing list it splinters the  
discussion for no actual gain other than the piece of paper stating  
who owns the domain. If iFax starts monkeying around with lots of  
ads, asinine spam, and/or moderating, then by all means, start a  
second mailing list. Until then I fail to see the benefit.

> HylaFAX discussions and conversations happen all of the time on  
> other mailing lists.  You've seen some of them on asterisk-users,  
> for example.  Well, those kinds of discussions happen in many other  
> places, too, and really it's not a big deal.  I'm keen to support  
> HylaFAX whether it be on hylafax.org or on Sourceforge or on  
> asterisk-users or wherever it may be.  As I see it, the more  
> opportunities to have those discussions the better it is.

Sure, but tracking one list is certainly better than tracking two.


> Same goes for the bug trackers.  More opportunity is better.  And  
> in this case there is an assurance that developments on Sourceforge  
> will immediately be channeled towards the CVS repository (which is  
> on hylafax.org).

I'm not a developer, so I can't say, but given one source tree, I see  
no need for two bug trackers. Just keeping them in sync will be a  
major pain in the ass, and developers will have to update both  
trackers every time they fix something. If you actually fork the code  
and develop a separate  source tree, then I think it makes perfect  
sense.

> Again, I realize that some people are not going to agree with me on  
> these points.  And that's okay.  I don't need everyone to agree  
> with me.  I just need a place where I can do my thing and not feel  
> like I'm behind a fascade.  If you don't like the solution that I  
> needed, then that's okay.

That's cool, I just think that the mailing list and bug tracker  
aren't solving much of anything, unless the purpose is to wrest  
control from iFax. If that's the case, there are better ways IMHO.  
The web site is good, though because the hylafax.org one is too out  
of date. However, in an ideal world, I think that hylafax.org would  
be updated, not a new site created.

I guess in the end, it's a free country, but unless you decide to  
fork the project, a lot of this seems to be unnecessary duplication  
of resources.

I hope this works out well and ends up being constructive.

Tom


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