You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Brian K. Wallace" <br...@transmorphix.com> on 2006/05/16 16:36:08 UTC
NPL javascript
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
As noted on the user list, PracticalBrowserSniffer.js is licensed under
the Netscape Public License v. 1.1. According to threads on
legal-discuss as well as documented here
http://people.apache.org/~cliffs/3party.html, the NPL is not allowed in
Apache projects (yes, that's the extremely short version, but it gets
the point across).
This is only used in the 4.x thread in contrib:Palette.
I'm going to be opening an issue as a blocker to get this issue resolved
so we're in compliance with ASF legal guidelines.
Brian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
iD8DBQFEaeNYaCoPKRow/gARAgxBAJ9vHXQXGOB89B40baefpYs16nQMiQCcCzv/
thptibLsRaNizqSR/drW7lc=
=NdJM
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: NPL javascript
Posted by Jesse Kuhnert <jk...@gmail.com>.
Ah nevermind...Heres the legalese:
General Rule
All prohibited works<http://people.apache.org/%7Ecliffs/3party.html#define-prohibitedwork>that
are currently included in builds or releases must be removed from
future versions by the earlier of:
- one year from the effective
date<http://people.apache.org/%7Ecliffs/3party.html#effectivedate>of
this policy, or
- the second major release of any ASF product.
In addition, as of the effective
date<http://people.apache.org/%7Ecliffs/3party.html#effectivedate>of
this policy,
*new* prohibited
works<http://people.apache.org/%7Ecliffs/3party.html#define-prohibitedwork>must
not be added to any project build or distribution.
So, we must not have it in all future releases, but don't need to freak out
and start removing old published releases and such.
On 5/16/06, Jesse Kuhnert <jk...@gmail.com> wrote:
>
> I'm fairly confident I can create a similar functioning script to plop in
> its place in pretty short order, but what are the ramifications for the
> previous releases? Do we have to go into the apache server and either remove
> or update all jars/releases now? Sounds like it. If we do, do we make them
> the same version and just have it updated, or do we have to release a brand
> new 4.x / 3.x and completely remove the old ones?
>
>
> On 5/16/06, Brian K. Wallace <br...@transmorphix.com> wrote:
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > As noted on the user list, PracticalBrowserSniffer.js is licensed under
> > the Netscape Public License v. 1.1. According to threads on
> > legal-discuss as well as documented here
> > http://people.apache.org/~cliffs/3party.html
> > <http://people.apache.org/%7Ecliffs/3party.html>, the NPL is not allowed
> > in
> > Apache projects (yes, that's the extremely short version, but it gets
> > the point across).
> >
> > This is only used in the 4.x thread in contrib:Palette.
> >
> > I'm going to be opening an issue as a blocker to get this issue resolved
> >
> > so we're in compliance with ASF legal guidelines.
> >
> > Brian
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.2.5 (MingW32)
> >
> > iD8DBQFEaeNYaCoPKRow/gARAgxBAJ9vHXQXGOB89B40baefpYs16nQMiQCcCzv/
> > thptibLsRaNizqSR/drW7lc=
> > =NdJM
> > -----END PGP SIGNATURE-----
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@tapestry.apache.org
> >
> >
>
>
> --
> Jesse Kuhnert
> Tacos/Tapestry, team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind.
>
--
Jesse Kuhnert
Tacos/Tapestry, team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind.
Re: NPL javascript
Posted by "Brian K. Wallace" <br...@transmorphix.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I am only going by what's been posted (aka: IANAL, etc...), but
according to http://people.apache.org/~cliffs/3party.html#transition,
this part specifically:
General Rule
All prohibited works that are currently included in builds or releases
must be removed from future versions by the earlier of:
* one year from the effective date of this policy, or
* the second major release of any ASF product.
In addition, as of the effective date of this policy, new prohibited
works must not be added to any project build or distribution.
it appears as though what's out there now is alright (frowned upon, but
alright since it's already released), but putting out a 3.0.5/4.0.3|4.1
as soon as possible without the offending file might be a darned good
idea. (my opinion as it states "the second major release of any ASF
product").
Again, IANAL - but this would seem the prudent course.
Brian
Jesse Kuhnert wrote:
> I'm fairly confident I can create a similar functioning script to plop in
> its place in pretty short order, but what are the ramifications for the
> previous releases? Do we have to go into the apache server and either
> remove
> or update all jars/releases now? Sounds like it. If we do, do we make them
> the same version and just have it updated, or do we have to release a brand
> new 4.x / 3.x and completely remove the old ones?
>
> On 5/16/06, Brian K. Wallace <br...@transmorphix.com> wrote:
>>
> As noted on the user list, PracticalBrowserSniffer.js is licensed under
> the Netscape Public License v. 1.1. According to threads on
> legal-discuss as well as documented here
> http://people.apache.org/~cliffs/3party.html, the NPL is not allowed in
> Apache projects (yes, that's the extremely short version, but it gets
> the point across).
>
> This is only used in the 4.x thread in contrib:Palette.
>
> I'm going to be opening an issue as a blocker to get this issue resolved
> so we're in compliance with ASF legal guidelines.
>
> Brian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
iD8DBQFEaekBaCoPKRow/gARAml8AKC+ChEjeNWhpqGq+XWduupJo04WLQCg9rhh
g4yr3nSN5xq6YJAWlz5NlzE=
=Gbjr
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: NPL javascript
Posted by Jesse Kuhnert <jk...@gmail.com>.
I'm fairly confident I can create a similar functioning script to plop in
its place in pretty short order, but what are the ramifications for the
previous releases? Do we have to go into the apache server and either remove
or update all jars/releases now? Sounds like it. If we do, do we make them
the same version and just have it updated, or do we have to release a brand
new 4.x / 3.x and completely remove the old ones?
On 5/16/06, Brian K. Wallace <br...@transmorphix.com> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> As noted on the user list, PracticalBrowserSniffer.js is licensed under
> the Netscape Public License v. 1.1. According to threads on
> legal-discuss as well as documented here
> http://people.apache.org/~cliffs/3party.html, the NPL is not allowed in
> Apache projects (yes, that's the extremely short version, but it gets
> the point across).
>
> This is only used in the 4.x thread in contrib:Palette.
>
> I'm going to be opening an issue as a blocker to get this issue resolved
> so we're in compliance with ASF legal guidelines.
>
> Brian
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (MingW32)
>
> iD8DBQFEaeNYaCoPKRow/gARAgxBAJ9vHXQXGOB89B40baefpYs16nQMiQCcCzv/
> thptibLsRaNizqSR/drW7lc=
> =NdJM
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tacos/Tapestry, team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind.