Re: [Contribution] wskdebug

2020-02-19 Thread Bertrand Delacretaz
Hi,

On Wed, Feb 19, 2020 at 1:35 AM Alexander Klimetschek
 wrote:
> ...Note that the granted source code zip [1] still has the Adobe copyright 
> headers.
> We would have to remove/replace them. Bertrand told me that I would have to 
> do this
> during the contribution process...

Yes, as per https://apache.org/legal/src-headers.html, it's best to
have those copyright headers removed and that must be done by "the
copyright owner (or owner's agent)", so those modifications should be
done by an Adobe employee.

OTOH I think it's fair for to add a mention of such contributions to
the CREDITS.txt file [1].

-Bertrand

[1] https://github.com/apache/openwhisk/blob/master/CREDITS.txt

-Bertrand


Re: [Contribution] wskdebug

2020-02-18 Thread Alexander Klimetschek
Hi David,

I just sent the signed grant to the secretary (cc'ed you).

Great to see that the dependencies are all ok wrt their licenses!

Note that the granted source code zip [1] still has the Adobe copyright 
headers. We would have to remove/replace them. Bertrand told me that I would 
have to do this during the contribution process, I assume when committing this 
(exact) source code to a new openwhisk repo.

Let me know what else I can do! Otherwise I assume I'll have to wait for the 
PMC's vote on the contribution.

[1] https://github.com/adobe/wskdebug/archive/v1.1.2.zip

Cheers,
Alex

From: David P Grove 
Sent: Tuesday, February 18, 2020 06:55
To: dev@openwhisk.apache.org 
Subject: RE: [Contribution] wskdebug


Hi Alex,

Thanks for pushing this forward!

Once the grant is submitted to the ASF secretary we can push ahead
with the formal process.  Thanks for filling in more of the wskdebug.xml; I
updated the version in the incubator svn repository to match.

For the license check, the critical list is the production
dependencies (what is required to run the released module).  Dev
dependencies are not blockers because end users do not need dev
dependencies to use the released software. From your attached list the
production dependency licenses are:

  - MIT: 99
  - ISC: 20
  - Apache-2.0: 8
  - BSD-3-Clause: 3
  - BSD-2-Clause: 3
  - MIT*: 2
  - Custom: http://github.com/substack/node-bufferlist: 1 (effectively MIT)
  - AFLv2.1,BSD: 1
  - Unlicense: 1

MIT, ISC, Apache-2.0, BSD-3-Clause, BSD-2-Clause, Unlicense, are all
"Category A" licenses [1].  All fine.

AFLv3.0 is a "Category A" license.  AFLv2.1 is not listed in any category
at [1]. However, the one package with that license [2] is dual-licensed as
either BSD-3-Clause or AFLv2.1. Since BSD-3 is Category A, we are fine.

So, I see no license issues.  Everything is Category-A.

--dave

[1] http://www.apache.org/legal/resolved.html
[2] https://github.com/kriszyp/json-schema/blob/master/LICENSE



RE: [Contribution] wskdebug

2020-02-18 Thread David P Grove

Hi Alex,

Thanks for pushing this forward!

Once the grant is submitted to the ASF secretary we can push ahead
with the formal process.  Thanks for filling in more of the wskdebug.xml; I
updated the version in the incubator svn repository to match.

For the license check, the critical list is the production
dependencies (what is required to run the released module).  Dev
dependencies are not blockers because end users do not need dev
dependencies to use the released software. From your attached list the
production dependency licenses are:

  - MIT: 99
  - ISC: 20
  - Apache-2.0: 8
  - BSD-3-Clause: 3
  - BSD-2-Clause: 3
  - MIT*: 2
  - Custom: http://github.com/substack/node-bufferlist: 1 (effectively MIT)
  - AFLv2.1,BSD: 1
  - Unlicense: 1

MIT, ISC, Apache-2.0, BSD-3-Clause, BSD-2-Clause, Unlicense, are all
"Category A" licenses [1].  All fine.

AFLv3.0 is a "Category A" license.  AFLv2.1 is not listed in any category
at [1]. However, the one package with that license [2] is dual-licensed as
either BSD-3-Clause or AFLv2.1. Since BSD-3 is Category A, we are fine.

So, I see no license issues.  Everything is Category-A.

--dave

[1] http://www.apache.org/legal/resolved.html
[2] https://github.com/kriszyp/json-schema/blob/master/LICENSE



Re: [Contribution] wskdebug

2019-08-19 Thread Alexander Klimetschek
FYI, a little status update: we are going through the internal legal process 
for a grant to ASF. Both contributors have signed the ICLA (check) but there 
might be a few more steps necessary that will take a few days. We will update 
the IP clearance document once we reach that.

Thanks,
Alex

From: David P Grove 
Sent: Tuesday, August 13, 2019 14:56
To: dev@openwhisk.apache.org 
Cc: Jesse MacFadyen ; Fil Maj ; Moritz Raho 
; Shazron Abdullah ; Simon Mac Donald 

Subject: RE: [Contribution] wskdebug




Alexander Klimetschek  wrote on 08/13/2019
05:06:54 PM:
>
> thanks. The IP clearance page says "The receiving PMC is responsible
> for doing the work." but I am happy to help if there is anything I can
do.
>

Hi. Sorry, I could have done a better job of telling you what I needed you
to do.  The quoted text really means "the Incubator PMC is _not_responsible
for doing any of the work."  We still need the people making the donation
to do some work as they are the ones who know the history of the code and
have the legal standing to donate it.

I created a draft IP clearance record at [1].  I can drive the mechanics of
the Apache process, but I need your help with (a) a brief description of
the code base (b) submitting the appropriate software grant (based on the
set of contributors to wskdebug) and (c) completing the sections of the
"Copyright" and "Verify distribution rights" of the IP clearance form.

--dave

[1]
https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/openwhisk-wskdebug.xml


RE: [Contribution] wskdebug

2019-08-13 Thread David P Grove



Alexander Klimetschek  wrote on 08/13/2019
05:06:54 PM:
>
> thanks. The IP clearance page says "The receiving PMC is responsible
> for doing the work." but I am happy to help if there is anything I can
do.
>

Hi. Sorry, I could have done a better job of telling you what I needed you
to do.  The quoted text really means "the Incubator PMC is _not_responsible
for doing any of the work."  We still need the people making the donation
to do some work as they are the ones who know the history of the code and
have the legal standing to donate it.

I created a draft IP clearance record at [1].  I can drive the mechanics of
the Apache process, but I need your help with (a) a brief description of
the code base (b) submitting the appropriate software grant (based on the
set of contributors to wskdebug) and (c) completing the sections of the
"Copyright" and "Verify distribution rights" of the IP clearance form.

--dave

[1]
https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/openwhisk-wskdebug.xml


Re: [Contribution] wskdebug

2019-08-13 Thread Matt Sicker
A software grant will be needed for the donation to be accepted, for one.

On Tue, 13 Aug 2019 at 16:07, Alexander Klimetschek
 wrote:
>
> Hi Dave,
>
> thanks. The IP clearance page says "The receiving PMC is responsible for 
> doing the work." but I am happy to help if there is anything I can do.
>
> The entire codebase is available and can be cloned from 
> https://github.com/adobe/wskdebug
>
> Cheers,
> Alex
>
> 
> From: David P Grove 
> Sent: Tuesday, August 13, 2019 13:40
> To: dev@openwhisk.apache.org 
> Cc: Jesse MacFadyen ; Fil Maj ; Moritz Raho 
> ; Shazron Abdullah ; Simon Mac Donald 
> 
> Subject: Re: [Contribution] wskdebug
>
>
>
> Alexander Klimetschek  wrote on 08/08/2019 12:27:57 AM:
> >
> > Hi OpenWhisk team,
> >
> > after presenting wskdebug in today's community call I would like
> > to formally start the contribution process. There was agreement in
> > the call to accept a contribution into Apache OpenWhisk.
>
> Great!
>
> The IP clearance process is described at [1].  The next steps would be get
> a snapshot of the code together and fill out the IP Clearance form
> describing it.
>
> --dave
>
> [1] http://incubator.apache.org/ip-clearance/



-- 
Matt Sicker 


Re: [Contribution] wskdebug

2019-08-13 Thread Alexander Klimetschek
Hi Dave,

thanks. The IP clearance page says "The receiving PMC is responsible for doing 
the work." but I am happy to help if there is anything I can do.

The entire codebase is available and can be cloned from 
https://github.com/adobe/wskdebug

Cheers,
Alex


From: David P Grove 
Sent: Tuesday, August 13, 2019 13:40
To: dev@openwhisk.apache.org 
Cc: Jesse MacFadyen ; Fil Maj ; Moritz Raho 
; Shazron Abdullah ; Simon Mac Donald 

Subject: Re: [Contribution] wskdebug



Alexander Klimetschek  wrote on 08/08/2019 12:27:57 AM:
>
> Hi OpenWhisk team,
>
> after presenting wskdebug in today's community call I would like
> to formally start the contribution process. There was agreement in
> the call to accept a contribution into Apache OpenWhisk.

Great!

The IP clearance process is described at [1].  The next steps would be get
a snapshot of the code together and fill out the IP Clearance form
describing it.

--dave

[1] http://incubator.apache.org/ip-clearance/


Re: [Contribution] wskdebug

2019-08-13 Thread David P Grove


Alexander Klimetschek  wrote on 08/08/2019 12:27:57 AM:
>
> Hi OpenWhisk team,
>
> after presenting wskdebug in today's community call I would like
> to formally start the contribution process. There was agreement in
> the call to accept a contribution into Apache OpenWhisk.

Great!

The IP clearance process is described at [1].  The next steps would be get
a snapshot of the code together and fill out the IP Clearance form
describing it.

--dave

[1] http://incubator.apache.org/ip-clearance/


[Contribution] wskdebug

2019-08-07 Thread Alexander Klimetschek
Hi OpenWhisk team,

after presenting wskdebug [1] in today's community call I would like to 
formally start the contribution process. There was agreement in the call to 
accept a contribution into Apache OpenWhisk.

If you couldn't join, I suggest to look at the recording from today: video [2], 
slides [3] and notes [4] (btw - awesome how organized you folks run this!).

Some relevant notes:

  *   The project has already been fully open sourced from Adobe's side on 
github [1].
  *   It is licensed under the Apache 2.0 license [5].
  *   We have 3 teams at Adobe using & supporting this tool and would have (at 
least) the following maintainers:
 *   Moritz Raho (signed Apache CLA, a few OW contributions)
 *   Jesse McFadyen (ASF committer)
 *   Shazron Abdullah (ASF committer)
 *   Alexander Klimetschek (ASF committer, a few OW contributions)
  *   I am tracking the contribution process in [6].
  *   Naming of the repository: openwhisk-wskdebug?

Let me know the next steps - looking forward to it!

[1] https://github.com/adobe/wskdebug
[2] https://youtu.be/Qtsi8VFm0uY (wskdebug presentation starts at 9:10)
[3] 
https://www.dropbox.com/s/p8swolzlrintged/wskdebug-openwhisk-presentation.pdf?dl=0
[4] 
https://cwiki.apache.org/confluence/display/OPENWHISK/2019-08-07+OW+Tech+Interchange+-+Meeting+Notes
[5] https://github.com/adobe/wskdebug/blob/master/LICENSE
[6] https://github.com/adobe/wskdebug/issues/2

Cheers,
Alex