My take would be that if we see that the Bayesian code becomes too big within the host project (Server) we could still factor it into its own subproject. From recent subprojects (mimej, jSPF, Postage) we see that they have a tendency to be only maintained by very few committers and thus lack community and oversight. If only one person or two persons work together, public communication tends to converge against zero.
Bernd On 12/2/07, Norman Maurer <[EMAIL PROTECTED]> wrote:
Hi Guys, maybe some of you had noticed in JIRA that i opened a task about move BayesianFilter stuff to an extra subproject some time ago. Even if i not thing i will have time to work in it before completing the handlerapi-experiment i want to collect some other opions about that. Anyone against this ? Do i need a real vote for this ? I think it whould be cool to isolate it to a subproject to provide some lightwight filter framework. bye Norman --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
