![]() |
I think an item that prevents Hylafax from being actively maintained and improved is that fact that so much of it is written in c++. I may be way off base here, but I know that's what prevents me from mucking around with the code. There just aren't as many c++ hackers as there c hackers, and the few that are out there are probably working for Microsoft :-) Again, I may be way off base, but my personal recommendation for the future of Hylafax would be to migrate away from c++, if such a thing is even possible. Then again, perhaps there are plenty of c++ gurus out there willing to pitch in and maintain Hylafax. Maybe this is just "sour grapes" from an old procedural hacker who just can't seem to make the jump to object-oriented. -----Original Message----- From: owner-flexfax@celestial.com [mailto:owner-flexfax@celestial.com] On Behalf Of Ken Berland Sent: Friday, March 19, 1999 12:24 PM To: Mike Porter Cc: Phil Watkinson; HylaFAX List; Damian A Ivereigh Subject: Re: flexfax: Whose looking after Hylafax? yessss... On Fri, 19 Mar 1999, Mike Porter wrote: > > This would a first step in changing the culture of hylafax development > > - to move to a modern, opensource 'bazaar' type of team working - but > > with all social changes, it will require patience and effort from all > > of us. > > > > Regards, > > Phil. > > /// > > Would it be possible to host an anonymous CVS site on the machine > that supports www.hylafax.org? Seems to work well for projects > like gimp... > > Mike >