On Mon, 2005-10-31 at 16:36 -0600, Bill Marquette wrote: > > I do find that offensive, we "obviously" could have done alot, the > first of which is not release fixes quickly. Certainly if we made > money off this product I wouldn't release an update until it had been > fully tested. pfSense isn't commercial, so the cost of doing business > is that YOU get to test it. My favorite saying goes like this: "With > open source, the vendor is you", I take it to heart every time I > choose an open source product. I decide how much time _I'm_ willing > to spend supporting it, if I'm not, then I'd rather just pay for a > commercial product so I don't have to deal with the heartache.
If I offended you, sorry. I understand pretty well what OpenSource nature of the project is. I understand right now you're not having business with this project, I however do not know your further intentions. Many OpenSource projects actually end up making money out of the product - SourceFire and snort could be best example in firewall area. Sometimes it is product packaged is sold sometimes it is support or services. I chose not to pay for commercial product, furthermore I choose to spend a time with "bleeding edge" product rather than going with m0n0wall smothwall or setting up firewall on OpenBSD. > > > I have limited time to spend on pfSense - I need to make it up and > > running. I've already found workarounds for most of my problems. > > I could just keep my findings for myself or I could have them reported > > with some fix ideas suggested. > > We have limited time also. I'm in the middle of a move and am the > primary developer for the shaper. I know it sucks, I know it has > bugs, I also know that pfSense is an alpha product. I expect bugs, > I'm not surprised when I find them. I understand. I really appreciate your prompt replies and fixes. The question I ask myself here is - what is the best help I can offer to this product having my limitations ? I can do some intensive testing and report problems and provide other feedback and suggestions. This is exactly what I'm doing. For problems which I discover I share the fix idea, if I have one. If I can't share the code I think this is best I can do. Once again do not be offended with it :) It is just attempt to find a better solution - if you do not like my idea drop it :) > Your attitude obviously comes from having to deploy a product that's > not ready to be deployed in a production environment in the manner > which you are attempting to deploy it. While pfSense is deployed in > prod environments and there are a couple very stable configurations, > it is alpha, we aren't marking it beta yet for reasons outside the OS. > When someone can go through the interface and find 6 bugs in 5 > minutes, it's not ready for beta. Well... I'd say I just live being early adopter. This is perhaps the best way to learn the product - Few years from now with tens of thousands of users I would unlikely be so easily speaking to core developers :) I have few other serious pieces in my system which are rather new and I've been previously doing it as well. The fact it is not production ready as you put it makes me cautious - this is why I go in bridging mode as this way I can bypass firewall physically by switching couple of cables which staff at remote facility can do for me. But it is not entirely what is moving me. I actually found workarounds for most of my problems long ago. I could simply avoid writing about the bugs. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
