Re: List structure

Mark Smith wrote:

> I'm going to take a moment to bring back something I mentioned some time
> ago - multiple mailing lists.
> 
> I strongly recommend we split the list to keep the user requests away from
> development or design.  We seem to have need for a development and design
> discussion, which I want to keep off the main user list.  The existing list
> could then be used for assistance and announcements, which should hopefully
> keep the bandwidth down a little.  The new list could then take all the
> traffic we've been seeing with regards everyone's desire to help, to discuss
> even if individuals do not possess technical knowledge.
> 
> I know I'm no crypto expert, but I am a programmer and I'd like to think
> I've got a little bit of common sense, I've already been taking a look at
> the potential for messing with packets, so as a result I believe I have
> something I may be able to contribute into a discussion about the matter.
> I've seen many others with similar desires and differing abilities.
> 
> We have two user bases - end users and contributors.  Let's make use of this
> while we can.
> 

I'd vote for two lists also......

Fil


--
Message sent by the [email protected] mailing list.
Unsubscribe: mail [email protected], "unsubscribe cipe-l" in body
Other commands available with "help" in body to the same address.
CIPE info and list archive: <URL:http://sites.inka.de/~bigred/devel/cipe.html>