> -----Original Message----- > From: Ted Husted [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 26, 2004 10:21 PM > To: Struts Developers List > Subject: Re: Adding new Struts features/sub-projects (was [Bug 28609] - > Scriptable Actions Support) > > > 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.
Interesting comment. I'm not really interested in getting into a discussion of the social aspects of open source development right now (mostly because I just don't have the time), but I couldn't help noticing the juxtaposition of "obligation to the community" and the open source mantra of "stratch your own itch". > 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 honestly don't mean to throw jacks in the road, but I think we need to sort ourselves out a bit before we start bringing things in from outside. For example, we need to get our web site under struts.apache.org, and we need to create the new CVS repo structure we discussed a while ago. Once our own new house is in order, we can have a housewarming party and invite some interested guests to come talk to us. ;-) > 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. Not the incubator, no. However, I do think a software grant might be appropriate, since we're moving a project from SourceForge. That's just a piece of paper that makes a legal statement to the effect that everybody is happy. It's really very lightweight to deal with, but I think would be a good thing to put in place. If nothing else, it would demonstrate to the board that we are properly overseeing the project that we have so recently been granted custody over. > 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. I'd be astonished if this happened. Really. We've just recently ditched a dependency on Commons Collections, which I personally think was a big mistake. If people object to depending on a Commons component that was actually created from Struts code in the first place, I simply can't imagine adding a dependency on something like BSF to the core. -- Martin Cooper > > -Ted. > > > > --------------------------------------------------------------------- > 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]
