* Bennett <[EMAIL PROTECTED]> [2005-11-27 01:58:17 -0600]:

> However, this fork of m0n0wall is a bit unnerving.  Yes, I know you have
> "radically different goals," but you also have similar goals and will
> face similar issues.  This fork detracts from BOTH projects because
> you've effectively cut the manpower for each project roughly in half
> (since everyone could be working on one project instead of two) while
> doubling the work (since each project will be duplicating work).  And
> let's not forget the user base is split, too, so each project has half
> the support and testers.

pfSense and m0n0wall are in a few respects very similar projects, but there are 
also several important differences that would make merging back into m0n0wall's 
codebase very difficult and quite probably harmful. m0n0wall has always 
targeted embedded systems where resources are at a premium, which is why Manuel 
is generally more conservative when it comes to adding or changing major pieces 
of code.

In contrast, pfSense targets machines that are not quite as minimal. Making 
this assumption about the machines that pfSense will be installed on allows us 
to implement amenities such as the package system, wizards, SSH, and so on. 
These are all things that would be very difficult to squeeze into m0n0wall's 
base without compromising one of that project's main goals.

> Even if you're sharing some code so you're not both reinventing the
> wheel, you still have to merge disjoint code as m0n0wall tries to add
> pfSense enhancements into their code and vice versa.  As a programmer, I
> know what all this patching is going to do to the code.  As you exchange
> code back and forth, m0n0wall is going to have some pfSense-specific
> code that they'll patch to retrofit into m0n0wall and then give it back
> to pfSense who will add some patches to the m0n0wall
> patches...Eventually, this bloated mess of patches is so convoluted that
> no one knows how it works and you're on your way to security holes and
> compromised networks.

Though we occasionally merge bugfixes and features from m0n0wall, to the best 
of my knowledge this has mostly been a 'one-way street'. At this point much of 
our base code has diverged significantly from the original m0n0wall codebase, 
and many of the features we have worked on since the fork will likely not make 
it back into m0n0 for the reasons described above.

> Thus, either you've doubled the work with half the developers/testers or
> you've doomed the code to buggy patches on top of patches.  This makes
> me question the founders of pfSense...Did they not foresee this when
> they decided to fork?  And these short-sighted individuals are who I am
> counting on to protect my valuable network?  Or is this some sort of ego
> thing?  Did the other m0n0wall programmers hurt their feelings so they
> ran off and made their own little project?  Or maybe the m0n0wall
> developers are unreasonable jerks and so pfSense politely forked rather
> than bash heads.  But those unreasonable developers are the ones who
> wrote the original m0n0wall code that you're using...

As I've already stated, there's really no reason to fear that pfSense is going 
to collapse under the weight of the patches we're forced to juggle, because 
there aren't many to begin with.

Also, it is my understanding that Scott and Chris originally forked because of 
Manuel's (obvious) resistance to taking his project in an entirely new 
direction. Few if any bridges were burned. It most certainly was not an 'ego 
thing'.

Skipping past the troll at the end,
Colin

Attachment: pgp3MFmHTBd4f.pgp
Description: PGP signature

Reply via email to