> Lets leave everything as it is - i mean tags and branches. Right.
> Apache2 module is still unusable - when we'll be able to finish it is > unclear. Because as far as i see, we have to agree with set of > features and design of rivet first. That's easy: Apache 2 should do what Apache 1 does in terms of handling .rvt and .tcl files. After that, then other things can be added. Well, realistically, since "he who does the work decides", if you really want to add something that everyone agrees is cool, then that's what you get to do. But if you need a plan, the plan is to make Rivet work with Apache 2. Part of that unfortunately means taking a good look at the code already there, because I don't think it correctly uses the Apache API's. > Once this is done, we'll have to concentrate on development... > Looks like long way to go for me. > My proposal is: > 1.Leave 1_0 branch as it is, and do all development in the trunk. > 2. Discuss the layout of rivet and our aims, get the plan of tasks > that needs to be done, preferably with precise description of what and > how needs to be done. This will allow to new people to jump in > and start doing somethingl immediately, also this will allow us to > work on those tasks separately, still having understanding of who and > what trying to achieve. As far as I can tell, it's just you and Massimo, so I don't think too much planning is necessary - just a bit of coordination so that you're not working on the same file at the same time. -- David N. Welton http://www.welton.it/davidw/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
