First allow me to apologize for breaking the thread(s). As a brand
new list member, I wasn''t able to easily retrieve from the archives.
I believe initiative is a great attribute for every team member, but as
Alex points out, I too believe there must be a "buck stops here"
authority
to ensure that everyone''s initiative is at least heading in the
generally accepted
correct direction.
I have seen several popular open-source projects fragment/fork/fall apart
due lack of cohesive leadership. Having a development background, I can
assure you that while a larger team membership does provide more man hours
that can be applied to the project, the effort required to coordinate
those resources
increases proportionally.
I therefore propose or recommend that a project leader or champion be
selected.
In my note of thanks to Tom this morning I foolishly volunteered. I am not
going to rescind my offer, but I must point out that one of the reasons
I have
been such a silent shorewall user, is that the internals of iptables and
netfiltering
doesn''t interest me greatly. As a user I wanted and used a tool like
shorewall that was relatively easy to configure, flexible and stable. To
keep it moving forward while maintaining those properties will take
as much or more project management as development.
Jim Richardson
====================Tom Eastep wrote:
> Going forward, I think that the future of Shorewall depends on what
> people do on their own initiative and not on what I tell them to do.
Alex Martin wrote:
> Last, someone needs to take an authoritative position and dictate what
> is going to happen, maybe let the devel list moderate, then execute a
> plan, because I can see that a lot of offers and ideas bouncing back and
> forth on the email are nice, but not necessarily problem solving.
