[Proftpd-devel] Re: ProFTPD modules and core code... (looking forward to 1.3)

[Jesse S S. <js...@in...>]

On Tue, Feb 27, 2001 at 11:35:09AM -0500, Charles Seeger wrote:
> Policy question: should a question like this be on the core list
> or the proftpd-devel list?

I am cc:'ing this to -devel.

I'm not going to get into what seems to essentially be a private conversation
between you and TJ, let me just state that I feel it is important to avoid
making assumptions about where final code should go or will lie, when a
"roadmap" for 1.3 has not really been established at all (although with
pre-1.3 cvs, I have started that task).  Basically, what I am saying is "let's
not get the cart before the horse."

One of the first things I would like to see is some casual documentation
w.r.t. the API, the distribution layout (filesystem-wise) and some
pseudo-code.  I'm currently working on this sort of thing, and you'll see my
work show up in pre-1.3.

I would like to invite *everyone* to look at the pre-1.3 cvs, specifically at
libpr, which is a general-purpose library that I intend to use in 1.3.  I
would welcome any comments and/or tweaks (the core team should all have
commit to this repository, if you don't please let me know).  The library is
essentially complete, with the notable exception of logging channels, which I
intend to add very soon.

Anonymous CVS information:

export CVSROOT=:pserver:ano...@cv...:/var/cvs/proftpd
cvs login
p: proftpd
cvs checkout pre-1.3

-- 
"In the event of a failure, the system can be configured to automatically
restart itself.  This feature of Windows NT Server provides maximum system
up-time."  -- Reliability and Fault Tolerance in Windows NT Server, MSC