[VOTE] Release Apache Training - Navigating the ASF Incubator Process 1.0 (incubating)

[Justin Mclean]

Hi,

This is a call for a releasing Apache Training Navigating the ASF Incubator 
Process 1.0 (incubating)

This is the first release for the Apache Training product. The vote result can 
be found here:
https://lists.apache.org/thread.html/350acb02776cbcdf164cc46d1bf250568a3a10182cd03ff522f578d1@%3Cdev.training.apache.org%3E

We have 2 IPMC votes, and only require one more +1 IPMC vote. So I ebncourage 
any IPMC member to that a look and provide feedback / vote on it.

The source artefact, including signatures and hashes can be found at:
https://dist.apache.org/repos/dist/dev/incubator/training/ApacheWay/NavigatingASFIncubation/1.0_rc2/
 


The tag to be voted upon is NavigatingASFIncubation1.0_rc2:
https://github.com/apache/incubator-training/tree/NavigatingASFIncubation1.0_rc2
 

The release hash is b719c7d5cb96aee0e213b68a5e758809fc02e619

The KEYS file is available at:
https://dist.apache.org/repos/dist/dev/incubator/training/KEYS/ 


There’s a release checklist here [1], that might be helpful in checking the 
release.

The vote will be open for a minimum of 72 hours or until we have a result.

[ ] +1 release this package
[ ] +0 no opinion
[ ] -1 do not release this package because…

Thanks,
Justin

1. 
https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
 

[DISCUSS] Release of Apache Training - Navigating the ASF Incubator Process 1.0 (incubating)

[Justin Mclean]

Hi,

Please keep the discussion here and not in the vote thread,

Even if not voting, mentors and IPMC members may want to talk a look at the 
material as it is based on several years of talks at ApacheCon and elsewhere. 
The idea here is that any IPMC person should be able to take this material and 
use it to give an incubating talk at a conference or inside your company. 
Feedback, pull requests etc etc also welcome.

For those who make their own slides you might also want to take a look as it 
uses maven to compile asciidoctor (improved markdown) to a reveal.js slide show 
(with timer and speaker notes and other features) this also means that your 
slides content can be put under version control and it easier to work 
collaborative on it. It also possible to covert the output to pdf or power 
point. They look quite nice as well.

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] check LICENSE and NOTICE for Apache Tuweni

[Antoine Toulme]

Is there anything else I need to get looked at?

> On Jun 6, 2019, at 8:45 AM, Antoine Toulme  wrote:
> 
> Thanks Justin.
> 
>> On Jun 3, 2019, at 14:30, Justin Mclean  wrote:
>> 
>> Hi,
>> 
>>> If that’s no trouble, I’d rather have the text inlined and in the LICENSE 
>>> file. Please let me know if that’s a problem.
>> 
>> No issue it can be done either way. I won’t be able to do a full check until 
>> later this week, so hopefully someone else can review it.
>> 
>> Thanks,
>> Justin
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [IMPORTANT] Board proposal on podling releases

[Justin Mclean]

Hi,

> I think it would be a mistake to include the word serious in the
> proposal that you are asking for board approval.  That likely will
> result in a 'no' response.  As would any request that that board
> approve anything that is illegal, like distributing code without
> complying with the terms under which that code is licensed.

Thanks for that feedback, I see if I can reword it in that way.

> There may be some wiggle room in getting the board to approve letting
> the incubator produce releases that are legal but may not comply with
> ASF policy.

The issue here is that is actually stricter that what we currently do. We allow 
podlings to make releases that are not legal reasonably often.

Thanks,
Justin

Re: [IMPORTANT] Board proposal on podling releases

[Sam Ruby]

On Fri, Jun 7, 2019 at 8:57 PM Justin Mclean  wrote:
>
> Hi,
>
> > 1) Is it legal to include GPL licensed software in releases?  The
> > answer is yes... as long as we comply with the terms of that license.
> > In the case of strong copyleft licenses, that could mean that the
> > podling release itself may need also be GPL licensed.
>
> And in cases where this has happened, it’s been ALv2 licensed, so I guess 
> that wouldn’t be legal. But we also allow minor stuff like this a lot of the 
> time e.g forgetting to add  MIT license text to LICENSE.
>
> > 2) Is it legal to include compiled code in releases?  Yes.
>
> But certainly against ASF policy and one of it core values.
>
> > 3) Is it legal to include copyright violations in releases?  No.
>
> In most cases, where this has occurred this has been minor, like including a 
> cat photo, and can be easily sorted by removing or asking for permission. If 
> someone did come along as say you don’t have permission to do that, we’d say 
> we were very sorry and fix it.
>
> Perhaps rewording the proposal to say "serious issue typically found in 
> podling releases” would help? Podlings generally make some effort to try and 
> get things right.

I think it would be a mistake to include the word serious in the
proposal that you are asking for board approval.  That likely will
result in a 'no' response.  As would any request that that board
approve anything that is illegal, like distributing code without
complying with the terms under which that code is licensed.

There may be some wiggle room in getting the board to approve letting
the incubator produce releases that are legal but may not comply with
ASF policy in one or more ways, given that those deviations are
documented, there exists a plan to fix those deviations, and that
podling graduation is gated on the fixing of those deficiencies.

> Thanks,
> Justin

- Sam Ruby

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [IMPORTANT] Board proposal on podling releases

[Davor Bonaci]

I think my position is well-known, but I'll restate it for completeness:

(1) Podling releases are foundation releases; no exceptions. They are
distributed in the same way, adopted by a foundation PMC in the same
manner, and they being with word "Apache". We are responsible for them.
(2) IPMC desires to foster learning and iterative improvement. We want to
be lenient with releases, and waive various *ASF policies* as deemed in the
best interest of the podling and the foundation.
(3) IPMC does not have authority to waive any legal requirements (like
someone's license) or policies of others (like someone's trademark policy).
If such an issue in a release *against a third party* is discovered, even
if minor, the IPMC should block such a release unconditionally. Note that
accidental and unintentional omission is fine, but known and willful is not.
(4) Given the above, it would be beneficial for the IPMC if the Board would
explicitly confirm IPMC's discretionary authority in waiving ASF release
and distribution policy.

I feel less strongly about:
(5) IPMC doesn't need to specify what is "may", "should", or "must" too
precisely. The precision above is good enough. In fact, "best interests"
doesn't mean "equality". Even if two releases suffer from the same issue,
it may be fine for a podling in early stages, but be blocked for a podling
where they have a regression compared to a previous release. "Committee
discretion" is much better than "rules". No new rules please.

On Sat, Jun 8, 2019 at 9:31 AM Julian Hyde  wrote:

> We’re trying to nail down the definition of “serious”.  May I suggest that
> we divide the guidelines into MAY, SHOULD and MUST. Anything with MUST is
> mandatory for all podling releases.
>
> The list may or may not be the same as for TLP releases.
>
> Julian
>
>
>
> Sent from my iPad
> > On Jun 7, 2019, at 5:56 PM, Justin Mclean 
> wrote:
> >
> > Hi,
> >
> >> 1) Is it legal to include GPL licensed software in releases?  The
> >> answer is yes... as long as we comply with the terms of that license.
> >> In the case of strong copyleft licenses, that could mean that the
> >> podling release itself may need also be GPL licensed.
> >
> > And in cases where this has happened, it’s been ALv2 licensed, so I
> guess that wouldn’t be legal. But we also allow minor stuff like this a lot
> of the time e.g forgetting to add  MIT license text to LICENSE.
> >
> >> 2) Is it legal to include compiled code in releases?  Yes.
> >
> > But certainly against ASF policy and one of it core values.
> >
> >> 3) Is it legal to include copyright violations in releases?  No.
> >
> > In most cases, where this has occurred this has been minor, like
> including a cat photo, and can be easily sorted by removing or asking for
> permission. If someone did come along as say you don’t have permission to
> do that, we’d say we were very sorry and fix it.
> >
> > Perhaps rewording the proposal to say "serious issue typically found in
> podling releases” would help? Podlings generally make some effort to try
> and get things right.
> >
> > Thanks,
> > Justin
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [IMPORTANT] Board proposal on podling releases

[Julian Hyde]

We’re trying to nail down the definition of “serious”.  May I suggest that we 
divide the guidelines into MAY, SHOULD and MUST. Anything with MUST is 
mandatory for all podling releases. 

The list may or may not be the same as for TLP releases. 

Julian



Sent from my iPad
> On Jun 7, 2019, at 5:56 PM, Justin Mclean  wrote:
> 
> Hi,
> 
>> 1) Is it legal to include GPL licensed software in releases?  The
>> answer is yes... as long as we comply with the terms of that license.
>> In the case of strong copyleft licenses, that could mean that the
>> podling release itself may need also be GPL licensed.
> 
> And in cases where this has happened, it’s been ALv2 licensed, so I guess 
> that wouldn’t be legal. But we also allow minor stuff like this a lot of the 
> time e.g forgetting to add  MIT license text to LICENSE. 
> 
>> 2) Is it legal to include compiled code in releases?  Yes.
> 
> But certainly against ASF policy and one of it core values.
> 
>> 3) Is it legal to include copyright violations in releases?  No.
> 
> In most cases, where this has occurred this has been minor, like including a 
> cat photo, and can be easily sorted by removing or asking for permission. If 
> someone did come along as say you don’t have permission to do that, we’d say 
> we were very sorry and fix it. 
> 
> Perhaps rewording the proposal to say "serious issue typically found in 
> podling releases” would help? Podlings generally make some effort to try and 
> get things right.
> 
> Thanks,
> Justin

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE]: Release Apache OpenWhisk Runtime Node.js v1.14.0 (incubating)

[Sobkowiak Krzysztof]

+1

Best regards

Krzysztof

On 06.06.2019 10:49, James Thomas wrote:

Dear IPMC members,

This is a call for vote to release Apache OpenWhisk Runtime Node.js
v1.14.0 (incubating)

The Apache OpenWhisk community has voted on and approved a proposal to
release Apache OpenWhisk Runtime Node.js v1.14.0 (incubating). We now
ask Incubator PMC members to review and vote on this incubator
release.

Vote Thread: 
https://mail-archives.apache.org/mod_mbox/openwhisk-dev/201905.mbox/%3CCAH3ObvociVHFCW%2BKE2OVpGQhVvM0qbYqQg4t1d7YWHR64tf%2BrQ%40mail.gmail.com%3E

Result Thread: 
https://mail-archives.apache.org/mod_mbox/openwhisk-dev/201906.mbox/%3CCAH3Obvr2-qAnjMTY_uaN%2BX%2BBZoQ0oXyhAjztHLuSSWs3Fh09kw%40mail.gmail.com%3E

This release comprises of source code distribution only. There is only
one module within this release number 1.14. The artifact were built
from the following Git commit IDs:

Apache OpenWhisk Runtime Node.js: 14d2af8

https://github.com/apache/incubator-openwhisk-runtime-nodejs/commits/14d2af8

The source code artifact of can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.14.0-incubating-rc2/openwhisk-runtime-nodejs-1.14.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact is:

openwhisk-runtime-nodejs-1.14.0-incubating-sources.tar.gz: EA61BE97
5E7CCA26 E18D95B5 24B5414A 1C3998C7 C00B5C8A 39F8E3F0 04F4A20B
7045173D 0F588F43 CA911AE1 EEE0B31F 9C297417 4370BF67 3A95B83F
31335048

which can can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.14.0-incubating-rc2/openwhisk-runtime-nodejs-1.14.0-incubating-sources.tar.gz.sha512

The signature of the artifact of openwhisk client js can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.14.0-incubating-rc2/openwhisk-runtime-nodejs-1.14.0-incubating-sources.tar.gz.asc

KEYS file is available here:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS

You can use this UNIX script to download the release and verify the
checklist below:

https://gitbox.apache.org/repos/asf?p=incubator-openwhisk-release.git;a=blob_plain;f=tools/rcverify.sh;hb=HEAD

Usage:

curl -s 
"https://gitbox.apache.org/repos/asf?p=incubator-openwhisk-release.git;a=blob_plain;f=tools/rcverify.sh;hb=HEAD";
-o rcverify.sh

chmod +x rcverify.sh

./rcverify.sh openwhisk-runtime-nodejs 'OpenWhisk Runtime Node.js'
1.14.0-incubating rc2

The vote will be open for at least 72 hours or until necessary number
of votes are reached.

Please vote accordingly: [ ] +1 approve [ ] +0 no opinion [ ] -1
disapprove with the reason


--
Krzysztof Sobkowiak

JEE & OSS Architect, Integration Architect
Apache Software Foundation Member (http://apache.org/)
Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/)
Apache Incubator PMC Member (https://incubator.apache.org/)
Senior Solution Architect @ Capgemini SSC 
(http://www.capgeminisoftware.pl/)