You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Jesse Kuhnert <jk...@gmail.com> on 2005/12/28 14:37:10 UTC

Third party licensing

Just to get some resolution on this, are there any definitive yes/no
thoughts on whether or not tapestry should include any form of dojo? I've
received confirmation that the license is compatible with apache's, so it
should be ok in that respect.

If any was included I'd think it would be very very minimal in footprint as
I'm sure the majority of it won't be used directly, at least not initially.
I would however like to eventually re-factor some of the javascript (ok,
maybe more or less all) in tapestry to work off of more of the dojo ant
build scripts so that we can start adding js unit tests and build packaging
to provide an easier to navigate source structure/overall stability.

I'm sure the ajax stuff could probably be left open for debate, but I'm
still leaning initially towards being able to provide very direct
support/implementation for it within tapestry, leaving tacos to focus on
writing really cool components. (Not that tapestrys components won't be
re-worked, we'll have to define which tacos components get included and
which don't I guess )

The recent asset changes sort of make the inclusions possible now, but I
think the Shell component/global asset inclusion logic needs to be completed
before anything like this can begin.

Thoughts?

jesse

Re: Third party licensing

Posted by Martin Cooper <ma...@apache.org>.
Howard Lewis Ship wrote:
> My concern is the bundling of Dojo with Tapestry, as Dojo is not an
> Apache project; I believe that may be a problem to be resolved with
> the Jakarta PMC.

That would not be a problem. Dojo is dual-licensed under AFL 2.1 and 
Modified BSD. The latter has been confirmed, by the ASF legal team, as 
compatible with the Apache License.

Go for it, Jesse! :-)

--
Martin Cooper


> On 12/28/05, Jesse Kuhnert <jk...@gmail.com> wrote:
> 
>>Just to get some resolution on this, are there any definitive yes/no
>>thoughts on whether or not tapestry should include any form of dojo? I've
>>received confirmation that the license is compatible with apache's, so it
>>should be ok in that respect.
>>
>>If any was included I'd think it would be very very minimal in footprint as
>>I'm sure the majority of it won't be used directly, at least not initially.
>>I would however like to eventually re-factor some of the javascript (ok,
>>maybe more or less all) in tapestry to work off of more of the dojo ant
>>build scripts so that we can start adding js unit tests and build packaging
>>to provide an easier to navigate source structure/overall stability.
>>
>>I'm sure the ajax stuff could probably be left open for debate, but I'm
>>still leaning initially towards being able to provide very direct
>>support/implementation for it within tapestry, leaving tacos to focus on
>>writing really cool components. (Not that tapestrys components won't be
>>re-worked, we'll have to define which tacos components get included and
>>which don't I guess )
>>
>>The recent asset changes sort of make the inclusions possible now, but I
>>think the Shell component/global asset inclusion logic needs to be completed
>>before anything like this can begin.
>>
>>Thoughts?
>>
>>jesse
>>
>>
> 
> 
> 
> --
> Howard M. Lewis Ship
> Independent J2EE / Open-Source Java Consultant
> Creator, Jakarta Tapestry
> Creator, Jakarta HiveMind
> 
> Professional Tapestry training, mentoring, support
> and project work.  http://howardlewisship.com


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


Re: Third party licensing

Posted by Howard Lewis Ship <hl...@gmail.com>.
My concern is the bundling of Dojo with Tapestry, as Dojo is not an
Apache project; I believe that may be a problem to be resolved with
the Jakarta PMC.

On 12/28/05, Jesse Kuhnert <jk...@gmail.com> wrote:
> Just to get some resolution on this, are there any definitive yes/no
> thoughts on whether or not tapestry should include any form of dojo? I've
> received confirmation that the license is compatible with apache's, so it
> should be ok in that respect.
>
> If any was included I'd think it would be very very minimal in footprint as
> I'm sure the majority of it won't be used directly, at least not initially.
> I would however like to eventually re-factor some of the javascript (ok,
> maybe more or less all) in tapestry to work off of more of the dojo ant
> build scripts so that we can start adding js unit tests and build packaging
> to provide an easier to navigate source structure/overall stability.
>
> I'm sure the ajax stuff could probably be left open for debate, but I'm
> still leaning initially towards being able to provide very direct
> support/implementation for it within tapestry, leaving tacos to focus on
> writing really cool components. (Not that tapestrys components won't be
> re-worked, we'll have to define which tacos components get included and
> which don't I guess )
>
> The recent asset changes sort of make the inclusions possible now, but I
> think the Shell component/global asset inclusion logic needs to be completed
> before anything like this can begin.
>
> Thoughts?
>
> jesse
>
>


--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind

Professional Tapestry training, mentoring, support
and project work.  http://howardlewisship.com

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


Re: Third party licensing

Posted by Leonardo Quijano Vincenzi <le...@dtqsoftware.com>.
Jesse Kuhnert wrote:
> Just to get some resolution on this, are there any definitive yes/no
> thoughts on whether or not tapestry should include any form of dojo? I've
> received confirmation that the license is compatible with apache's, so it
> should be ok in that respect.
>
> If any was included I'd think it would be very very minimal in footprint as
> I'm sure the majority of it won't be used directly, at least not initially.
> I would however like to eventually re-factor some of the javascript (ok,
> maybe more or less all) in tapestry to work off of more of the dojo ant
> build scripts so that we can start adding js unit tests and build packaging
> to provide an easier to navigate source structure/overall stability.
>
> I'm sure the ajax stuff could probably be left open for debate, but I'm
> still leaning initially towards being able to provide very direct
> support/implementation for it within tapestry, leaving tacos to focus on
> writing really cool components. (Not that tapestrys components won't be
> re-worked, we'll have to define which tacos components get included and
> which don't I guess )
>
> The recent asset changes sort of make the inclusions possible now, but I
> think the Shell component/global asset inclusion logic needs to be completed
> before anything like this can begin.
>
> Thoughts?
>
> jesse
>
>   
I think it would be great if Tapestry moved all core components to a 
separate Tapestry-Components (including the current contrib and the core 
components) in a way that could be handled like a mini-project. Optional 
Ajax stuff could go in that project, or in Tacos as a separate 
"contribution" to the core components (a Tapestry-Ajax mini-project, hehe).

Other common non-Ajax Javascript stuff would be useful to use as 
components too, though I don't really know Dojo's scope.

-- 
Ing. Leonardo Quijano Vincenzi
DTQ Software



---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org