The sad truth is that many teams that do use Struts cannot also use whatever other goody they find on SourceForge or on some other open source host.
Many do have permission to use Struts, but getting permission to use another product is a difficult task. I believe we have an obligation to the community to solicit the best and brightest extensions and invite them to join the Struts project. Obviously, we are not going to accept all of the extensions now available for Struts, and all of the extensions would not want to donate their code to Apache anyway. But when there is an extension what some or all of us want to support, or has developers we might want to nominate as committers, then we should bring them on. What criteria do we apply? The same as always. Is it something that fits within our charter, that benefits our community, and that we can support over the longterm. I think the scriptable actions meet the usual criteria, and would make for a good starter subproject. It's useful and small and easy to do. I think a lot of us would be willing to support the code once it is here. I know I would. I would also agree with Don in that this product does not seem like something that needs to go through the Incubator, since it was developed solely by Apache committers. But, it was created and released outside an Apache CVS, and we could offer to sponsor it through the incubator. I'd help with that too. Another way to go might be to just add it to the core. It would creates a runtime dependency on the bsf.jar, but I could live with that. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
