If you built scopes would it require the incubator to bring it in?
If you built all the code from scratch couldn't you just import it
into the sandbox? Or would we want to bring it through the incubator
to ensure there are no IP issues?
The LGPL parts would probably need to be factored out.
I'm really not sure of the protocol here. If you have something
valuable to contribute and you're already a committer, it would be
nice if you didn't have to go through the Incubator. But maybe it's
better to do so just to avoid IP issues.
BTW, this is not an endorsement or otherwise of Scopes. I don't even
know what it is :-)
Greg
On Aug 30, 2006, at 3:45 AM, Antonio Petrelli wrote:
Michael Jouravlev ha scritto:
Hi Antonio,
I looked through your code, it is quite clear, so I started pulling
needed stuff from your library and sticking it into Struts. I also
want this scope to be available for ActionForms in action mapping
definition, and for errors/messages.
One of the reasons for which I built Scopes was the possible use in
every layer of the web application, even in the Model, e.g. imagine
the use of Conversation Scope with Spring scopes.
So for the moment you are doing the right thing pulling the code
directly, but now I am guessing if it is the case of incubating
Scopes, or probably putting it in the sandbox under the Struts
umbrella, if it raises attention by this community.
But I think that there are two possible barriers to incubation:
- Scopes has a lonely developer for the moment (me :-) )
- A (small but interesting) part of Scopes (the "window" scope) is
based on a LGPL library.
What do you think?
Ciao
Antonio
---------------------------------------------------------------------
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]
