The foundation doesn't require CCLAs (they're a good CYA for the employees
though) but we do require ICLAs.
On Sunday, February 8, 2015, John D. Ament wrote:
> All,
>
> Just wanted to confirm with others. If a company is donating a new project
> to the ASF, a CCLA (or multiple ICLAs) are requir
On Sun, Feb 8, 2015 at 6:09 PM, John D. Ament wrote:
> And specifically, is there ever a case where a CCLA can cover for a SGA?
I would seriously doubt it.
Thanks,
Roman.
-
To unsubscribe, e-mail: general-unsubscr...@incubator.
On Sun, Feb 8, 2015 at 6:06 PM, John D. Ament wrote:
> On Sun Feb 08 2015 at 8:59:21 PM Roman Shaposhnik
> wrote:
>
>> On Sun, Feb 8, 2015 at 5:16 PM, John D. Ament
>> wrote:
>> > Hope I didn't throw you off, just wanted to make sure I was doing some
>> > basic shepherding work (since I pulled t
On Sun Feb 08 2015 at 9:04:43 PM John D. Ament
wrote:
> All,
>
> Just wanted to confirm with others. If a company is donating a new
> project to the ASF, a CCLA (or multiple ICLAs) are required to allow
> contributors from that project to continue on in Apache, as well as an SGA
> to allow the c
On Sun Feb 08 2015 at 8:59:21 PM Roman Shaposhnik
wrote:
> On Sun, Feb 8, 2015 at 5:16 PM, John D. Ament
> wrote:
> > Hope I didn't throw you off, just wanted to make sure I was doing some
> > basic shepherding work (since I pulled the NPanday card this month :-)
>
> Nah, its cool. I've initiate
All,
Just wanted to confirm with others. If a company is donating a new project
to the ASF, a CCLA (or multiple ICLAs) are required to allow contributors
from that project to continue on in Apache, as well as an SGA to allow the
company to transfer the existing software to the ASF.
Basically, th
On Sun, Feb 8, 2015 at 5:16 PM, John D. Ament wrote:
> Hope I didn't throw you off, just wanted to make sure I was doing some
> basic shepherding work (since I pulled the NPanday card this month :-)
Nah, its cool. I've initiated all the required steps and updated the website.
At this point, we're
+1 binding. Contents look good.
Ideally you should point to a git commit id for the release though. Not a
big deal, more procedural (rather than a branch you're on, since the branch
may have additional commits on it over the final hash).
John
On Thu Feb 05 2015 at 12:50:21 PM Maxim Khutornenko
Hope I didn't throw you off, just wanted to make sure I was doing some
basic shepherding work (since I pulled the NPanday card this month :-)
John
On Sun Feb 08 2015 at 8:06:51 PM Roman Shaposhnik
wrote:
> FWIW: Cos and I were planning to finalize the retirement steps today.
>
> Thanks,
> Roman
FWIW: Cos and I were planning to finalize the retirement steps today.
Thanks,
Roman.
On Sun, Feb 8, 2015 at 5:01 AM, John D. Ament wrote:
> On Sun Feb 08 2015 at 7:57:28 AM Dave Fisher wrote:
>
>> We need to report that NPanday is being retired.
>>
>>
> Yep, added a retired section.
>
> John
>
Thanks Justin, we will check it out for the additional LICENSE issue.
- Henry
On Sat, Feb 7, 2015 at 6:35 PM, Justin Mclean wrote:
> Hi,
>
> +1 (binding)
>
> - signatures and hashes correct
> - LICENSE and NOTICE correct but may have minor issue (see below)
> - DISCLAIMER exits
> - incubating i
Regarding the number of users using this project -- at this moment, the
community is not big. A few local start-ups have been trying to use it
(mainly due to announcement in our seminar list), eg. one is using it for
image recognition (given a phone snapped by a user, it wants to be return
the sa
Hi,
+1 (binding)
- signatures and hashes correct
- LICENSE and NOTICE correct but may have minor issue (see below)
- DISCLAIMER exits
- incubating in source package
- all source files have headers
- no unexpected binaries in release
- can compile source
Minor LICENSE issue, looks like angular-s
Hi,
Sorry but it's -1 binding from me. Willing to change my vote if other
incubator members think these issues are OK for this release and/or corrective
action is taken for the next release.
All source files have headers and there no unexpected binaries but looks to be
be a few license and no
On Sun Feb 08 2015 at 7:57:28 AM Dave Fisher wrote:
> We need to report that NPanday is being retired.
>
>
Yep, added a retired section.
John
> On Feb 8, 2015, at 4:50 AM, John D. Ament wrote:
>
> > On Sun Feb 08 2015 at 7:48:11 AM John D. Ament
> > wrote:
> >
> >> So, at this point, is this
We need to report that NPanday is being retired.
On Feb 8, 2015, at 4:50 AM, John D. Ament wrote:
> On Sun Feb 08 2015 at 7:48:11 AM John D. Ament
> wrote:
>
>> So, at this point, is this resolved? I may have missed the final
>> resolution summary.
>>
>>
> Nevermind, got thrown off in my sea
On Sun Feb 08 2015 at 7:48:11 AM John D. Ament
wrote:
> So, at this point, is this resolved? I may have missed the final
> resolution summary.
>
>
Nevermind, got thrown off in my search by a late vote. I just retired them
from podlings.xml and will remove them from the board report shortly,
unl
So, at this point, is this resolved? I may have missed the final
resolution summary.
John
On Wed Jan 21 2015 at 5:15:33 PM Roman Shaposhnik wrote:
> This is a vote on recommending a retirement option
> for the NPanday poddling.
>
> It comes on the hills of the general consensus of
> the NPanda
Hi,
+1 binding
- hashes and signature correct
- LICENCE and NOTICE correct (except notice year is wrong)
- DISCLAIMER exists
- incubating in source package name
- all source file have Apache header
- no unexpected binary files in release
- can compile from source
Minor issues:
- you may want to
Sorry to be MIA on this vote. Glad to see it go out.
On Sat, Feb 7, 2015 at 12:16 PM, Julian Hyde wrote:
> This vote passes with 3 +1s and no 0 or -1 votes:
> +1 Brock Noland
> +1 Alan Gates (mentor)
> +1 Ashutosh Chauhan (champion)
>
> Thanks everyone. We’ll now roll the release out to the m
20 matches
Mail list logo
