You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Todd Volkert <tv...@gmail.com> on 2009/09/03 14:42:29 UTC
[VOTE] Release Pivot 1.3 RC2
All:
The Pivot community voted on and has approved a proposal to release Apache
Pivot 1.3 Release Candidate 2. We would now like to request the permission
of the Incubator PMC to publish the artifacts on the Pivot download page.
The artifacts, RAT reports, KEYS file, and release notes can be found at
http://people.apache.org/~tvolkert/dist/pivot/v1.3-rc2/. The tag from which
the release artifacts were generated can be found at
http://svn.apache.org/repos/asf/incubator/pivot/tags/v1.3-rc2/. The podling
vote summary can be found at
http://mail-archives.apache.org/mod_mbox/incubator-pivot-dev/200909.mbox/%3C168ef9ac0909030453p43dec2een337e3abc4ebf683d@mail.gmail.com%3E
Please vote to publish this release by Wednesday, Sep 9 12:00 GMT (adding
extra time since the vote spans a weekend and a US holiday).
[ ] +1 Publish
[ ] +0
[ ] -0
[ ] -1 Don't publish, because...
Much appreciated,
-T
Re: [VOTE] Release Pivot 1.3 RC2
Posted by sebb <se...@gmail.com>.
On 04/09/2009, Todd Volkert <tv...@gmail.com> wrote:
> > > > The LICENSE file does not contain the full CCA LICENSE for the Silk
> > > > icons; see http://creativecommons.org/licenses/by/2.5/legalcode for
> > > > the full text.
> > >
> > > Good to know - I'll update it on the trunk. Given that we got it from
> > > http://creativecommons.org/licenses/by/2.5/, which is the license
> > linked to
> > > off the silk icon home page, should this block a release?
> >
> > Yes, because it's not actually the license.
> >
>
>
> I'm adding the full license to the trunk now, but with all due respect, I'm
> gonna wait for an IPMC opinion on this one, since we've already gone out
> with the 1.1 and 1.2 releases with the existing license (and since this is
> an incubating release). Don't get me wrong: I'm not against re-tagging if
> it's required; but no sense in calling off the vote prematurely.
>
>
> > > For 3rd party libraries which use the AL 2.0 license (e.g. Smack &
> > > > Groovy) for completeness this should be noted in the LICENSE file.
> > >
> > > the NOTICE file says which items are Apache 2.0 licensed, and the LICENSE
> > > file contains the Apache 2.0 license text. Is this not sufficient?
> >
> > It would make life a lot easier for users (and reviewers) if the
> > LICENSE file had the complete list.
> >
>
>
> Just to be clear what you're saying, you want something like the following
> at the very top of the LICENSE file:
>
> "For Apache Tomcat's Servlet 2.5 implementation, the Smack Jabber API, and
> the Groovy scripting engine:"
>
> Saying that they're Apache 2.0 licensed in the NOTICE file would seem to be
> sufficient, given that users and reviewers will see the Apache license at
> the top of the LICENSE file. The other licenses are shown to what they
> pertain because otherwise it'd be hard to search for them in the LICENSE
> file.
>
> If we add the afformentioned line at the top, should we also add "and for
> Apache Pivot"? Unless I'm misunderstanding what you're suggesting, it seems
> like we're catering to the lowest common denominator here.
Have a look at how Photark have done it:
http://svn.apache.org/repos/asf/incubator/photark/tags/M1-incubating-RC4/distribution/src/main/release/bin/LICENSE
>
> > > The NOTICE file mentions VMWare, but fails to mention any associated
> > > > license.
> > >
> > > That's because VMware maintains a copyright ownership over the code
> > > contributed to the ASF, as described in the "Overview" and "Source File
> > > Headers for Code Developed at the ASF" sections of the ASF Source Header
> > and
> > > Copyright Notice Policy (http://www.apache.org/legal/src-headers.html).
> > > This copyright notice is pursuant to ASF copyright notice policy.
> >
> > That's why there is a mention in the NOTICE file, but surely there
> > must be some license associated with the VMWare code? What is it, and
> > where is it?
> >
>
>
> Actually, IANAL, but I think you're wrong. VMware hasn't licensed the file
> to the ASF - they've donated it to the ASF -- but are still covered by
> copyright protection.
>
IANAL either, but in that case, presumably the code is now under AL 2.0.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release Pivot 1.3 RC2
Posted by Todd Volkert <tv...@gmail.com>.
Makes sense. I'll call off the vote and re-tag. I'll send another heads up
when the podling voting starts on the RC3 candidate.
Thanks everyone, especially Sebb, for your attention,
-T
Re: [VOTE] Release Pivot 1.3 RC2
Posted by ant elder <an...@gmail.com>.
On Fri, Sep 4, 2009 at 10:36 AM, Leo Simons<ma...@leosimons.com> wrote:
> On Fri, Sep 4, 2009 at 3:05 AM, Todd Volkert<tv...@gmail.com> wrote:
>>> > > The LICENSE file does not contain the full CCA LICENSE for the Silk
>>> > > icons; see http://creativecommons.org/licenses/by/2.5/legalcode for
>>> > > the full text.
>>> >
>>> > Good to know - I'll update it on the trunk. Given that we got it from
>>> > http://creativecommons.org/licenses/by/2.5/, which is the license
>>> linked to
>>> > off the silk icon home page, should this block a release?
>>>
>>> Yes, because it's not actually the license.
>>
>> I'm adding the full license to the trunk now, but with all due respect, I'm
>> gonna wait for an IPMC opinion on this one, since we've already gone out
>> with the 1.1 and 1.2 releases with the existing license (and since this is
>> an incubating release). Don't get me wrong: I'm not against re-tagging if
>> it's required; but no sense in calling off the vote prematurely.
>
> IMHO all valid objections to releases that are made for legal reasons
> should always be addressed, and they should block a release until they
> are addressed. IMHO, making a mistake once before is no excuse for
> making the same mistake again.
>
> The discussion is difficult because we're not lawyers, and so "valid
> objection" is a difficult judgment call for us to make. The IPMC errs
> on the side of caution, probably a bit more so than most other PMCs,
> probably because we're setting an example as much as anything else.
>
> Rather than force the IPMC to make these judgment calls, please also
> err on the side of caution and fix things.
>
> (These discussions can also be difficult because there can be a
> dispute about what actually should be in a file or what license
> applies or whatever. Different advice would apply then...but the most
> appropriate action seems rather obvious here.)
>
> cheers,
>
> - Leo
>
The ASF policy is clear on how release votes work - there are no vetos
on releases all that is needed are three +1s. This works ok because if
a _valid_ issue is raised PMC members wont vote +1 or will retract
their vote. One of the reasons poddlings are at the Incubator is to
learn, if we're inconsistent and unduly pedantic about release reviews
people give up trying and learn less, so err'ing on the side of any
objection blocking a release is not appropriate IMHO.
In this case a missing license is clearly a problem that needs to be
fixed, so -1 from me on this RC.
...ant
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release Pivot 1.3 RC2
Posted by Leo Simons <ma...@leosimons.com>.
On Fri, Sep 4, 2009 at 3:05 AM, Todd Volkert<tv...@gmail.com> wrote:
>> > > The LICENSE file does not contain the full CCA LICENSE for the Silk
>> > > icons; see http://creativecommons.org/licenses/by/2.5/legalcode for
>> > > the full text.
>> >
>> > Good to know - I'll update it on the trunk. Given that we got it from
>> > http://creativecommons.org/licenses/by/2.5/, which is the license
>> linked to
>> > off the silk icon home page, should this block a release?
>>
>> Yes, because it's not actually the license.
>
> I'm adding the full license to the trunk now, but with all due respect, I'm
> gonna wait for an IPMC opinion on this one, since we've already gone out
> with the 1.1 and 1.2 releases with the existing license (and since this is
> an incubating release). Don't get me wrong: I'm not against re-tagging if
> it's required; but no sense in calling off the vote prematurely.
IMHO all valid objections to releases that are made for legal reasons
should always be addressed, and they should block a release until they
are addressed. IMHO, making a mistake once before is no excuse for
making the same mistake again.
The discussion is difficult because we're not lawyers, and so "valid
objection" is a difficult judgment call for us to make. The IPMC errs
on the side of caution, probably a bit more so than most other PMCs,
probably because we're setting an example as much as anything else.
Rather than force the IPMC to make these judgment calls, please also
err on the side of caution and fix things.
(These discussions can also be difficult because there can be a
dispute about what actually should be in a file or what license
applies or whatever. Different advice would apply then...but the most
appropriate action seems rather obvious here.)
cheers,
- Leo
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release Pivot 1.3 RC2
Posted by Todd Volkert <tv...@gmail.com>.
> > > The LICENSE file does not contain the full CCA LICENSE for the Silk
> > > icons; see http://creativecommons.org/licenses/by/2.5/legalcode for
> > > the full text.
> >
> > Good to know - I'll update it on the trunk. Given that we got it from
> > http://creativecommons.org/licenses/by/2.5/, which is the license
> linked to
> > off the silk icon home page, should this block a release?
>
> Yes, because it's not actually the license.
>
I'm adding the full license to the trunk now, but with all due respect, I'm
gonna wait for an IPMC opinion on this one, since we've already gone out
with the 1.1 and 1.2 releases with the existing license (and since this is
an incubating release). Don't get me wrong: I'm not against re-tagging if
it's required; but no sense in calling off the vote prematurely.
> > For 3rd party libraries which use the AL 2.0 license (e.g. Smack &
> > > Groovy) for completeness this should be noted in the LICENSE file.
> >
> > the NOTICE file says which items are Apache 2.0 licensed, and the LICENSE
> > file contains the Apache 2.0 license text. Is this not sufficient?
>
> It would make life a lot easier for users (and reviewers) if the
> LICENSE file had the complete list.
>
Just to be clear what you're saying, you want something like the following
at the very top of the LICENSE file:
"For Apache Tomcat's Servlet 2.5 implementation, the Smack Jabber API, and
the Groovy scripting engine:"
Saying that they're Apache 2.0 licensed in the NOTICE file would seem to be
sufficient, given that users and reviewers will see the Apache license at
the top of the LICENSE file. The other licenses are shown to what they
pertain because otherwise it'd be hard to search for them in the LICENSE
file.
If we add the afformentioned line at the top, should we also add "and for
Apache Pivot"? Unless I'm misunderstanding what you're suggesting, it seems
like we're catering to the lowest common denominator here.
> > The NOTICE file mentions VMWare, but fails to mention any associated
> > > license.
> >
> > That's because VMware maintains a copyright ownership over the code
> > contributed to the ASF, as described in the "Overview" and "Source File
> > Headers for Code Developed at the ASF" sections of the ASF Source Header
> and
> > Copyright Notice Policy (http://www.apache.org/legal/src-headers.html).
> > This copyright notice is pursuant to ASF copyright notice policy.
>
> That's why there is a mention in the NOTICE file, but surely there
> must be some license associated with the VMWare code? What is it, and
> where is it?
>
Actually, IANAL, but I think you're wrong. VMware hasn't licensed the file
to the ASF - they've donated it to the ASF -- but are still covered by
copyright protection.
Re: [VOTE] Release Pivot 1.3 RC2
Posted by sebb <se...@gmail.com>.
On 04/09/2009, Todd Volkert <tv...@gmail.com> wrote:
> > The NOTICE file contains items which should not be there, i.e. Tomcat.
> >
>
>
> The servlet implementation could come from a number of places. We
> originally didn't mention it in the NOTICE file, but it got caught as
> something that needed to be there in our 1.1 release to remove any ambiguity
> as to which implementation we're using and whether we're legally allowed to
> do so. So it must stay. Are there any other items that you think should
> not be there?
>
>
>
> > Also - a minor point - the ========= dividers are unnecessary (the
> > NOTICE file should be as short as possible).
> >
>
>
> That's a stylistic choice -- we did it to increase readability. It
> certainly should have no bearing on a release vote.
>
>
>
> > The LICENSE file does not contain the full CCA LICENSE for the Silk
> > icons; see http://creativecommons.org/licenses/by/2.5/legalcode for
> > the full text.
> >
>
>
> Good to know - I'll update it on the trunk. Given that we got it from
> http://creativecommons.org/licenses/by/2.5/, which is the license linked to
> off the silk icon home page, should this block a release?
Yes, because it's not actually the license.
>
> For 3rd party libraries which use the AL 2.0 license (e.g. Smack &
> > Groovy) for completeness this should be noted in the LICENSE file.
> >
>
>
> the NOTICE file says which items are Apache 2.0 licensed, and the LICENSE
> file contains the Apache 2.0 license text. Is this not sufficient?
It would make life a lot easier for users (and reviewers) if the
LICENSE file had the complete list.
>
>
> > The LICENSE file should note the name of the license, as well as
> > including the text.
> > The URL would be helpful.
> >
>
>
> Not a bad idea, but certainly not a requirement. For quick reference, I
> looked at httpd's LICENSE file, and they don't do this (
> http://svn.apache.org/repos/asf/httpd/httpd/trunk/LICENSE).
>
>
> The NOTICE file mentions VMWare, but fails to mention any associated
> > license.
> >
>
>
> That's because VMware maintains a copyright ownership over the code
> contributed to the ASF, as described in the "Overview" and "Source File
> Headers for Code Developed at the ASF" sections of the ASF Source Header and
> Copyright Notice Policy (http://www.apache.org/legal/src-headers.html).
> This copyright notice is pursuant to ASF copyright notice policy.
That's why there is a mention in the NOTICE file, but surely there
must be some license associated with the VMWare code? What is it, and
where is it?
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release Pivot 1.3 RC2
Posted by Todd Volkert <tv...@gmail.com>.
> The NOTICE file contains items which should not be there, i.e. Tomcat.
>
The servlet implementation could come from a number of places. We
originally didn't mention it in the NOTICE file, but it got caught as
something that needed to be there in our 1.1 release to remove any ambiguity
as to which implementation we're using and whether we're legally allowed to
do so. So it must stay. Are there any other items that you think should
not be there?
> Also - a minor point - the ========= dividers are unnecessary (the
> NOTICE file should be as short as possible).
>
That's a stylistic choice -- we did it to increase readability. It
certainly should have no bearing on a release vote.
> The LICENSE file does not contain the full CCA LICENSE for the Silk
> icons; see http://creativecommons.org/licenses/by/2.5/legalcode for
> the full text.
>
Good to know - I'll update it on the trunk. Given that we got it from
http://creativecommons.org/licenses/by/2.5/, which is the license linked to
off the silk icon home page, should this block a release?
For 3rd party libraries which use the AL 2.0 license (e.g. Smack &
> Groovy) for completeness this should be noted in the LICENSE file.
>
the NOTICE file says which items are Apache 2.0 licensed, and the LICENSE
file contains the Apache 2.0 license text. Is this not sufficient?
> The LICENSE file should note the name of the license, as well as
> including the text.
> The URL would be helpful.
>
Not a bad idea, but certainly not a requirement. For quick reference, I
looked at httpd's LICENSE file, and they don't do this (
http://svn.apache.org/repos/asf/httpd/httpd/trunk/LICENSE).
The NOTICE file mentions VMWare, but fails to mention any associated
> license.
>
That's because VMware maintains a copyright ownership over the code
contributed to the ASF, as described in the "Overview" and "Source File
Headers for Code Developed at the ASF" sections of the ASF Source Header and
Copyright Notice Policy (http://www.apache.org/legal/src-headers.html).
This copyright notice is pursuant to ASF copyright notice policy.
Re: [VOTE] Release Pivot 1.3 RC2
Posted by sebb <se...@gmail.com>.
On 03/09/2009, Todd Volkert <tv...@gmail.com> wrote:
> All:
>
> The Pivot community voted on and has approved a proposal to release Apache
> Pivot 1.3 Release Candidate 2. We would now like to request the permission
> of the Incubator PMC to publish the artifacts on the Pivot download page.
>
> The artifacts, RAT reports, KEYS file, and release notes can be found at
> http://people.apache.org/~tvolkert/dist/pivot/v1.3-rc2/. The tag from which
> the release artifacts were generated can be found at
> http://svn.apache.org/repos/asf/incubator/pivot/tags/v1.3-rc2/. The podling
> vote summary can be found at
> http://mail-archives.apache.org/mod_mbox/incubator-pivot-dev/200909.mbox/%3C168ef9ac0909030453p43dec2een337e3abc4ebf683d@mail.gmail.com%3E
>
> Please vote to publish this release by Wednesday, Sep 9 12:00 GMT (adding
> extra time since the vote spans a weekend and a US holiday).
>
> [ ] +1 Publish
> [ ] +0
> [ ] -0
> [X] -1 Don't publish, because...
The NOTICE file contains items which should not be there, i.e. Tomcat.
Also - a minor point - the ========= dividers are unnecessary (the
NOTICE file should be as short as possible).
The LICENSE file does not contain the full CCA LICENSE for the Silk
icons; see http://creativecommons.org/licenses/by/2.5/legalcode for
the full text.
For 3rd party libraries which use the AL 2.0 license (e.g. Smack &
Groovy) for completeness this should be noted in the LICENSE file.
The LICENSE file should note the name of the license, as well as
including the text.
The URL would be helpful.
The NOTICE file mentions VMWare, but fails to mention any associated license.
> Much appreciated,
>
> -T
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org