PfSense moves to Apache License





  • I have this bad feeling that this is the end of pfSense as we know it. And the beginning of purely commercially oriented/driven pfSense. BTW, sad to see you go Chris.



  • @azzido:

    I have this bad feeling that this is the end of pfSense as we know it. And the beginning of purely commercially oriented/driven pfSense. BTW, sad to see you go Chris.

    Thanks. Don't worry about it being the end, or that anything will even change. My departure has nothing to do with anything going on or planned here.



  • @kpa:

    Also you're apparently not even aware that Chris has been the first and foremost defender of this policy what you call "purely commercial oriented/driven pfSense", think about that.

    What "policy" would that be, exactly? There have been "commercially driven" accusations made for 9 years now, ever since we first started offering commercial support. I've been calling those out as bullshit for 9 years because they are. One would think eventually people would stop with the claims, but I guess 9 years isn't long enough.

    What has the community lost in 9 years through these repeated accusations of being "commercially driven" and the end of times is near? Not one single thing. In fact, it's gained significantly through having more developers employed to work on the project.

    While there are a number of much-appreciated community contributors, the vast majority of the work around here comes from those we employ. Yes, I've always been supportive of what allows us to make a living. That's also what allows this project to exist as it does, so those same things are in the best interests of the community as well. The only reason we've survived and thrived for 12 years is because we've been able to build a business around the project and employ people to work on it. It would have long ago died off like IPCop, m0n0wall, and a number of others if that weren't the case.