Tom Eastep wrote: > It is with regret that I announce that Shorewall development and support is > officially ended. > > Sean's post has finally driven it home to me that in the long term, trying > to support a project like Shorewall is impossible for a person of my > personality and age. > ... > Unlike the originators of other successful open source projects, I have not > been able to attract a core of people who believe in Shorewall and who are > willing to make sacrifices to ensure it's success. That is my weakness and I > accept it. But is means that I have been left with trying to develop, > document, and support Shorewall almost single-handedly. I cannot do it any > more. > ... > I will leave the Shorewall website and server in place until July 4 in case > there is any community interest in picking up the pieces. Please email me > privately if you are interested in carrying on; I'll do what I can to help. > > Tonight I am deleting myself from all of the Shorewall and Leaf mailing lists. > > I will clean up what I have for a 2.3 release and place it on the server as > the last Shorewall release -- Shorewall 2.4.0.
Tom has finally admitted what some of us have thought all along. The day had to come. If you get to the point where you're not happy with your life, something has to give. And since none of us owe you anything, i think you've made the right choice, Tom. Best of luck and God bless. Righto, lads! Now what are we going to do about this? I for one am reluctant to lose shorewall, as it is the only firewall i trust. As for the mechanics of shorewall.net going away: we have a functional sourceforge.net project page and web site for shorewall. If Tom is willing, perhaps he could add some of us on the devel list as project admins on his sf.net page, and we could make sure all of the right information is copied over from his site. Am i right in remembering that lists.shorewall.net is hosted elsewhere, Tom? On the more long-term side, we probably need to have a discussion about the direction of shorewall. I have a some of suggestions to start with, which we probably should start a new thread before talking about: - A slightly slower, more conservative release strategy. Tom has been compulsively adding features for the last several years as soon as he gets one request for something that sounds interesting. - We need to look at the big issues and make sure we've got a good handle on them. For me, these include (in rough order of priority from my perspective): * Multiple ISPs & load balancing * Features to enable building a personal firewall with shorewall * IPv6 -- Paul <http://paulgear.webhop.net> -- Did you know? Microsoft Internet Explorer and Outlook have a poor track record for security <http://www.kb.cert.org/vuls/id/713878>. Why not try one of the more secure alternatives from <http://mozilla.org>?
signature.asc
Description: OpenPGP digital signature
