Re: [VOTE] Release Apache Dubbo OPS (Incubating) 0.1 [RC3]

[Huxing Zhang]

Hi,

On Fri, Feb 15, 2019 at 2:00 PM Gosling Von  wrote:
>
> Hi,
>
> +1 binding(only on source)
>
> I checked:
> - incubating in name
> - DISCLAIMER exits
> - LICENSE and NOTICE are fine. I notice you have listed some css dependencies 
> as APL 2.0 license. But some other dependency such as vue.js is also the same 
> case. If we could hope for list all dependencies for completeness, more 
> details see here[1].

The css files are from third party project so they should be included
in LICENSE. The vue.js files are either generated by vue CLI[1] or
written manually so I think they should not be included in LICENSE.

[1] https://cli.vuejs.org/

> - Al source file have ASF headers
> - No unexpected binary files
> - Can compile from source
>
> P.S. Console is distributed as the binary according to common sense. I also 
> noticed we are discussing the binary distribution problem in anther thread. 
> As a transitional stage. I vote for release source code. Hopefully this 
> clarifies the discussion that follows.
>
>
> [1] http://www.apache.org/dev/licensing-howto.html#bundle-asf-product
>
>
> Best Regards,
> Von Gosling
>
> > 在 2019年2月12日，下午7:06，Minxuan Zhuang  写道：
> >
> > Hi community,
> >
> > Dubbo OPS 0.1 RC3 is still waiting for 3 binding votes to get it passed.
> > Would you please help to review and vote for the candidate?
> >
> >
> > On Thu, Feb 7, 2019 at 11:01 PM Minxuan Zhuang  wrote:
> >
> >> Hello Incubator Community,
> >>
> >> The Apache Dubbo community has voted on and approved a proposal to release
> >> Apache Dubbo OPS (Incubating) version 0.1.
> >>
> >> We now kindly request the Incubator PMC members review and vote on this
> >> incubator release.
> >>
> >> Apache Dubbo™ (incubating) is a high-performance, java based, open source
> >> RPC framework. Dubbo offers three key functionalities, which include
> >> interface based remote call, fault tolerance & load balancing, and
> >> automatic service registration & discovery.
> >>
> >> Dubbo community vote and result thread:
> >>
> >> https://lists.apache.org/thread.html/61b7e43b5813c794ef45e7d95dff9c0744ac2d70556ae7ff195405ee@%3Cdev.dubbo.apache.org%3E
> >>
> >> The release candidates (RC3):
> >> https://dist.apache.org/repos/dist/dev/incubator/dubbo/dubbo-ops/0.1/
> >>
> >>
> >> Git tag for the release (RC3):
> >> https://github.com/apache/incubator-dubbo-ops/releases/tag/0.1
> >>
> >> Hash for the release tag:
> >> 7e7b2c4421f54f86980dd2128fa58007f118a8d4
> >>
> >> Release Notes:
> >> *https://github.com/apache/incubator-dubbo-ops/releases/tag/0.1
> >> *
> >>
> >>
> >> The artifacts have been signed with Key :
> >> DA2108479B0C1E71, which can be
> >> found in the keys file:
> >> *https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS
> >> *
> >>
> >> 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
> >>
> >> Thanks,
> >> The Apache Dubbo (Incubating) Team
> >>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>


-- 
Best Regards！
Huxing

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

Re: [VOTE] Release Apache Dubbo OPS (Incubating) 0.1 [RC3]

[Gosling Von]

Hi,

+1 binding(only on source)

I checked:
- incubating in name
- DISCLAIMER exits
- LICENSE and NOTICE are fine. I notice you have listed some css dependencies 
as APL 2.0 license. But some other dependency such as vue.js is also the same 
case. If we could hope for list all dependencies for completeness, more details 
see here[1].
- Al source file have ASF headers
- No unexpected binary files
- Can compile from source

P.S. Console is distributed as the binary according to common sense. I also 
noticed we are discussing the binary distribution problem in anther thread. As 
a transitional stage. I vote for release source code. Hopefully this clarifies 
the discussion that follows. 


[1] http://www.apache.org/dev/licensing-howto.html#bundle-asf-product


Best Regards,
Von Gosling

> 在 2019年2月12日，下午7:06，Minxuan Zhuang  写道：
> 
> Hi community,
> 
> Dubbo OPS 0.1 RC3 is still waiting for 3 binding votes to get it passed.
> Would you please help to review and vote for the candidate?
> 
> 
> On Thu, Feb 7, 2019 at 11:01 PM Minxuan Zhuang  wrote:
> 
>> Hello Incubator Community,
>> 
>> The Apache Dubbo community has voted on and approved a proposal to release
>> Apache Dubbo OPS (Incubating) version 0.1.
>> 
>> We now kindly request the Incubator PMC members review and vote on this
>> incubator release.
>> 
>> Apache Dubbo™ (incubating) is a high-performance, java based, open source
>> RPC framework. Dubbo offers three key functionalities, which include
>> interface based remote call, fault tolerance & load balancing, and
>> automatic service registration & discovery.
>> 
>> Dubbo community vote and result thread:
>> 
>> https://lists.apache.org/thread.html/61b7e43b5813c794ef45e7d95dff9c0744ac2d70556ae7ff195405ee@%3Cdev.dubbo.apache.org%3E
>> 
>> The release candidates (RC3):
>> https://dist.apache.org/repos/dist/dev/incubator/dubbo/dubbo-ops/0.1/
>> 
>> 
>> Git tag for the release (RC3):
>> https://github.com/apache/incubator-dubbo-ops/releases/tag/0.1
>> 
>> Hash for the release tag:
>> 7e7b2c4421f54f86980dd2128fa58007f118a8d4
>> 
>> Release Notes:
>> *https://github.com/apache/incubator-dubbo-ops/releases/tag/0.1
>> *
>> 
>> 
>> The artifacts have been signed with Key :
>> DA2108479B0C1E71, which can be
>> found in the keys file:
>> *https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS
>> *
>> 
>> 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
>> 
>> Thanks,
>> The Apache Dubbo (Incubating) Team
>> 


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

[RESULT][VOTE] Release Apache Doris 0.9.0-incubating-rc02

[德 李]

Hi,

Thanks to everyone, and the vote for releasing Apache Doris
0.9.0-incubating-rc02 is now closed.

It has passed with 4 +1 (binding) votes and no 0 or -1 votes.

Binding:
+1 Willem Jiang
+1 Justin Mclean
+1 ShaoFeng Shi
+1 Makoto Yui

The vote thread:
https://lists.apache.org/thread.html/da05fdd8d84e35de527f27200b5690d7811a1e9
7d419d1ea66562130@%3Cgeneral.incubator.apache.org%3E

Best Regards,
Reed

Re: [VOTE] Release Apache Doris 0.9.0-incubating-rc02

[Makoto Yui]

Hi,

+1 (binding)

I checked
- incubator in name
- LICENSE and NOTICE are fine
- DISCLAIMER file
- sha512 and asc signature are good
- rat check passed
   The following showed some files not including ASF license headers
but they were borrowed codes
$ java -jar apache-rat-0.12/apache-rat-0.12.jar -a -d
apache-doris-0.9.0.rc02-incubating-src -e *.md *.MD .gitignore
.gitmodules .travis.yml manifest **vendor** **licenses** | grep File:
| grep -v "test_data" | grep -v "gutil" | grep -v "json" | grep -v
"patch" | grep -v "xml" | grep -v "conf" | grep -v "svg" | cut -f 3 -d
" " | xargs head -100
- can build from source within the docker image

Makoto

2019年2月15日(金) 11:46 ShaoFeng Shi :
>
> +1 binding,
>
> Checked the license file, the notice, the signature, the sha512 hash, all
> looks good; (I didn't run build as my docker is broken)
>
> Best regards,
>
> Shaofeng Shi 史少锋
> Apache Kylin PMC
> Work email: shaofeng@kyligence.io
> Kyligence Inc: https://kyligence.io/
>
> Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html
> Join Kylin user mail group: user-subscr...@kylin.apache.org
> Join Kylin dev mail group: dev-subscr...@kylin.apache.org
>
>
>
>
> Li,De(BDG)  于2019年2月14日周四 下午5:26写道：
>
> > Thank you, Justin, we will fix the license issue in next release.
> >
> > On 2019/2/14 上午10:39， "Justin Mclean"  wrote:
> >
> > >Hi,
> > >
> > >+1 binding but LICENSE is missing a couple of licenses please fix in next
> > >release.
> > >
> > >Checked:
> > >- incubating in name
> > >- hashes and signatures good
> > >- LICENSE is missing some licenses (se below)
> > >- NOTICE is fine
> > >- No unexpected binaries in file
> > >- All ASF source files have ASF headers
> > >- On OSX so didn’t build
> > >
> > >LICENSE is missing MIT licensed Sizzle.js [1] included in jQuery and MIT
> > >licensed normalize.css included in bootstrap.css.
> > >
> > >Thanks.
> > >Justin
> > >
> > >1. ./webroot/static/jquery.js
> > >2. ./webroot/static/bootstrap.css
> > >
> > >
> > >-
> > >To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > >For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> >

-- 
Makoto YUI 
Principal Engineer, Arm Treasure Data.
http://myui.github.io/

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

Re: [VOTE] Accept Training into the Apache Incubator

[Brahma Reddy Battula]

+1 (non-Binding).

Gone through discussion thread, it will greatly help in knowing the
ecosystem.
May we can extend to certification also..?

On Fri, Feb 15, 2019 at 1:08 AM Kenneth Knowles  wrote:

> +1 (binding)
>
> Looking forward to this.
>
> On Thu, Feb 14, 2019 at 11:11 AM Woonsan Ko  wrote:
>
> > +1 (binding)
> >
> > Cool!
> >
> > Woonsan
> >
> > On Wed, Feb 13, 2019 at 2:58 AM Lars Francke 
> > wrote:
> > >
> > > Hi everyone,
> > >
> > > we've discussed the proposal for the Training project in [1] and [2].
> The
> > > proposal itself can be found on the wiki[3].
> > >
> > > According to the Incubator rules[4] I'd like to call a vote to accept
> the
> > > new "Training" project as a podling in the Apache Incubator.
> > >
> > > A vote for accepting a new Apache Incubator podling is a majority vote.
> > > Everyone is welcome to vote, only Incubator PMC member votes are
> binding.
> > > It would be helpful (but not required) if you could add a comment
> stating
> > > whether your vote is binding or non-binding.
> > >
> > > This vote will run for at least 72 hours (but I expect to keep it open
> > for
> > > longer). Please VOTE as follows:
> > >
> > > [ ] +1 Accept Training into the Apache Incubator
> > > [ ] +0 Abstain
> > > [ ] -1 Do not accept Training into the Apache Incubator because ...
> > >
> > > Thank you for everyone who decided to join in in the past discussions!
> > > Lars
> > >
> > > [1] <
> > >
> >
> https://lists.apache.org/thread.html/5c00016b769135cc302bb2ce4e5f6bbfeeda933a07e9c38b5017d651@%3Cgeneral.incubator.apache.org%3E
> > > >
> > >
> > > [2] <
> > >
> >
> https://lists.apache.org/thread.html/9cb4d7eef73e0d526e0124944c3d37325aa892675351a1eed0a25de3@%3Cgeneral.incubator.apache.org%3E
> > > >
> > >
> > > [3] 
> > >
> > > [4] <
> > >
> >
> https://incubator.apache.org/policy/incubation.html#approval_of_proposal_by_sponsor
> > > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>


-- 
--Brahma Reddy Battula

Re: [VOTE] Release Apache Dubbo OPS (Incubating) 0.1 [RC3]

[Justin Mclean]

Hi,

> In this case, if we want to let source release pass, do we need 3 +1
> binding vote or 4 +1 binding vote?

I say only 3+1, but double check with Mark if his +1 still applies in this case.

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 Dubbo OPS (Incubating) 0.1 [RC3]

[Huxing Zhang]

Hi Justin,

In this case, if we want to let source release pass, do we need 3 +1
binding vote or 4 +1 binding vote?

On Fri, Feb 15, 2019 at 10:37 AM Justin Mclean  wrote:
>
> Hi,
>
> > One of our mentor, Mark, has voted +1 on the dev@ list [1]
> >
> > Can we count it as binding on the general@ vote?
>
> He's an IPMC member so yes that counts.
>
> Thanks.
> Justin
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>


-- 
Best Regards！
Huxing

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

Re: [VOTE] Release Apache Doris 0.9.0-incubating-rc02

[ShaoFeng Shi]

+1 binding,

Checked the license file, the notice, the signature, the sha512 hash, all
looks good; (I didn't run build as my docker is broken)

Best regards,

Shaofeng Shi 史少锋
Apache Kylin PMC
Work email: shaofeng@kyligence.io
Kyligence Inc: https://kyligence.io/

Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html
Join Kylin user mail group: user-subscr...@kylin.apache.org
Join Kylin dev mail group: dev-subscr...@kylin.apache.org




Li,De(BDG)  于2019年2月14日周四 下午5:26写道：

> Thank you, Justin, we will fix the license issue in next release.
>
> On 2019/2/14 上午10:39， "Justin Mclean"  wrote:
>
> >Hi,
> >
> >+1 binding but LICENSE is missing a couple of licenses please fix in next
> >release.
> >
> >Checked:
> >- incubating in name
> >- hashes and signatures good
> >- LICENSE is missing some licenses (se below)
> >- NOTICE is fine
> >- No unexpected binaries in file
> >- All ASF source files have ASF headers
> >- On OSX so didn’t build
> >
> >LICENSE is missing MIT licensed Sizzle.js [1] included in jQuery and MIT
> >licensed normalize.css included in bootstrap.css.
> >
> >Thanks.
> >Justin
> >
> >1. ./webroot/static/jquery.js
> >2. ./webroot/static/bootstrap.css
> >
> >
> >-
> >To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>

Re: [VOTE] Release Apache Dubbo OPS (Incubating) 0.1 [RC3]

[Justin Mclean]

Hi,

> One of our mentor, Mark, has voted +1 on the dev@ list [1]
> 
> Can we count it as binding on the general@ vote?

He's an IPMC member so yes that counts.

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 Dubbo OPS (Incubating) 0.1 [RC3]

[Huxing Zhang]

Hi,

One of our mentor, Mark, has voted +1 on the dev@ list [1]

Can we count it as binding on the general@ vote?

[1] 
https://lists.apache.org/thread.html/61b7e43b5813c794ef45e7d95dff9c0744ac2d70556ae7ff195405ee@%3Cdev.dubbo.apache.org%3E

On Thu, Feb 7, 2019 at 11:00 PM Minxuan Zhuang  wrote:
>
> Hello Incubator Community,
>
> The Apache Dubbo community has voted on and approved a proposal to release
> Apache Dubbo OPS (Incubating) version 0.1.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Apache Dubbo™ (incubating) is a high-performance, java based, open source
> RPC framework. Dubbo offers three key functionalities, which include
> interface based remote call, fault tolerance & load balancing, and
> automatic service registration & discovery.
>
> Dubbo community vote and result thread:
> https://lists.apache.org/thread.html/61b7e43b5813c794ef45e7d95dff9c0744ac2d70556ae7ff195405ee@%3Cdev.dubbo.apache.org%3E
>
> The release candidates (RC3):
> https://dist.apache.org/repos/dist/dev/incubator/dubbo/dubbo-ops/0.1/
>
>
> Git tag for the release (RC3):
>  https://github.com/apache/incubator-dubbo-ops/releases/tag/0.1
>
> Hash for the release tag:
> 7e7b2c4421f54f86980dd2128fa58007f118a8d4
>
> Release Notes:
> *https://github.com/apache/incubator-dubbo-ops/releases/tag/0.1
> *
>
>
> The artifacts have been signed with Key :
> DA2108479B0C1E71, which can be
> found in the keys file:
> *https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS
> *
>
> 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
>
> Thanks,
> The Apache Dubbo (Incubating) Team



-- 
Best Regards！
Huxing

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

Re: [VOTE] Release Apache Zipkin Brave Karaf (Incubating) version 0.1.2

[Adrian Cole]

Perfectly fine naming suggestion. thanks, Dave.

"Apache Zipkin Brave (incubating) for Apache Karaf"

I will put that into a pull request and suspect no-one will contest it.

-A

On Fri, Feb 15, 2019, 7:43 AM Dave Fisher  Hi Adrian,
>
> (NOTE - cross posted to private lists. Take care with replies.)
>
> Thanks for your patience regarding the branding issue I mentioned.
>
> > On Feb 14, 2019, at 4:29 AM, Adrian Cole 
> wrote:
>
> 
>
> > Finally, there was an unresolved question about branding of the repo. I
> > dont think we should attempt another release if there is something else
> > lurking.
>
> The name Apache Zipkin Brave Karaf (incubating) represents a confusion of
> two Apache Brands - Zipkin an incubating podling and Apache Karaf.
>
> See http://www.apache.org/foundation/marks/pmcs#other
>
> This suggests that the proper name respecting Karaf’s brand would be
> "Apache Zipkin Brave (incubating) for Apache Karaf"
>
> Regards,
> Dave
>
> >
> > Thanks for the help folks.
> >
> > -Adrian
> >
> >
> > On Thu, Feb 14, 2019, 7:40 PM John D. Ament  wrote:
> >
> >> On Thu, Feb 14, 2019 at 6:35 AM Justin Mclean 
> wrote:
> >>
> >>> Hi,
> >>>
>  I can follow up with the developer to fix their headers via a github
> >>> issue (if no one else gets to it before me).
> >>>
> >>> I already have raise it as an issue :-)  Add to it it if you want. [1]
> >>>
>  Including prior statements about NOTICE is completely optional, but in
> >>> the
>  case of no SGA would be ideal.  I don't think that's a blocker for
> >>> release …
> >>>
> >>> No neither do I think it is a blocker, but having a jar in a source
> >>> release is.
> >>>
> >>>
> >> And I can see in the repo that's already been resolved.  So I think
> >> Adrian's all set to re-roll the release and put it up for a vote.
> >>
> >>
> >>> Thanks,
> >>> Justin
> >>>
> >>> 1. https://github.com/takari/maven-wrapper/issues/104
> >>> -
> >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >>> For additional commands, e-mail: general-h...@incubator.apache.org
> >>>
> >>>
> >>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@zipkin.apache.org
> For additional commands, e-mail: dev-h...@zipkin.apache.org
>
>

Re: [VOTE] Release Apache Zipkin Brave Karaf (Incubating) version 0.1.2

[Dave Fisher]

Hi Adrian,

(NOTE - cross posted to private lists. Take care with replies.)

Thanks for your patience regarding the branding issue I mentioned.

> On Feb 14, 2019, at 4:29 AM, Adrian Cole  wrote:



> Finally, there was an unresolved question about branding of the repo. I
> dont think we should attempt another release if there is something else
> lurking.

The name Apache Zipkin Brave Karaf (incubating) represents a confusion of two 
Apache Brands - Zipkin an incubating podling and Apache Karaf.

See http://www.apache.org/foundation/marks/pmcs#other

This suggests that the proper name respecting Karaf’s brand would be "Apache 
Zipkin Brave (incubating) for Apache Karaf"

Regards,
Dave

> 
> Thanks for the help folks.
> 
> -Adrian
> 
> 
> On Thu, Feb 14, 2019, 7:40 PM John D. Ament  
>> On Thu, Feb 14, 2019 at 6:35 AM Justin Mclean  wrote:
>> 
>>> Hi,
>>> 
 I can follow up with the developer to fix their headers via a github
>>> issue (if no one else gets to it before me).
>>> 
>>> I already have raise it as an issue :-)  Add to it it if you want. [1]
>>> 
 Including prior statements about NOTICE is completely optional, but in
>>> the
 case of no SGA would be ideal.  I don't think that's a blocker for
>>> release …
>>> 
>>> No neither do I think it is a blocker, but having a jar in a source
>>> release is.
>>> 
>>> 
>> And I can see in the repo that's already been resolved.  So I think
>> Adrian's all set to re-roll the release and put it up for a vote.
>> 
>> 
>>> Thanks,
>>> Justin
>>> 
>>> 1. https://github.com/takari/maven-wrapper/issues/104
>>> -
>>> 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: [VOTE] Release Apache NetBeans parent pom 1

[Justin Mclean]

Hi,

Changing my vote to +1 binding.

> On the copyright dates in NOTICE

It not actually required just helpful and best if you mention the year of 
publication, most projects seem to including the starting year.

> Copyright 2014 and onwards The Apache Software Foundation.

Please don’t do this, copyright has an expiry date and while it’s unlikely any 
of us will live to see that date it does exist.

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

Re: [VOTE] Accept Training into the Apache Incubator

[Kenneth Knowles]

+1 (binding)

Looking forward to this.

On Thu, Feb 14, 2019 at 11:11 AM Woonsan Ko  wrote:

> +1 (binding)
>
> Cool!
>
> Woonsan
>
> On Wed, Feb 13, 2019 at 2:58 AM Lars Francke 
> wrote:
> >
> > Hi everyone,
> >
> > we've discussed the proposal for the Training project in [1] and [2]. The
> > proposal itself can be found on the wiki[3].
> >
> > According to the Incubator rules[4] I'd like to call a vote to accept the
> > new "Training" project as a podling in the Apache Incubator.
> >
> > A vote for accepting a new Apache Incubator podling is a majority vote.
> > Everyone is welcome to vote, only Incubator PMC member votes are binding.
> > It would be helpful (but not required) if you could add a comment stating
> > whether your vote is binding or non-binding.
> >
> > This vote will run for at least 72 hours (but I expect to keep it open
> for
> > longer). Please VOTE as follows:
> >
> > [ ] +1 Accept Training into the Apache Incubator
> > [ ] +0 Abstain
> > [ ] -1 Do not accept Training into the Apache Incubator because ...
> >
> > Thank you for everyone who decided to join in in the past discussions!
> > Lars
> >
> > [1] <
> >
> https://lists.apache.org/thread.html/5c00016b769135cc302bb2ce4e5f6bbfeeda933a07e9c38b5017d651@%3Cgeneral.incubator.apache.org%3E
> > >
> >
> > [2] <
> >
> https://lists.apache.org/thread.html/9cb4d7eef73e0d526e0124944c3d37325aa892675351a1eed0a25de3@%3Cgeneral.incubator.apache.org%3E
> > >
> >
> > [3] 
> >
> > [4] <
> >
> https://incubator.apache.org/policy/incubation.html#approval_of_proposal_by_sponsor
> > >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept Training into the Apache Incubator

[Woonsan Ko]

+1 (binding)

Cool!

Woonsan

On Wed, Feb 13, 2019 at 2:58 AM Lars Francke  wrote:
>
> Hi everyone,
>
> we've discussed the proposal for the Training project in [1] and [2]. The
> proposal itself can be found on the wiki[3].
>
> According to the Incubator rules[4] I'd like to call a vote to accept the
> new "Training" project as a podling in the Apache Incubator.
>
> A vote for accepting a new Apache Incubator podling is a majority vote.
> Everyone is welcome to vote, only Incubator PMC member votes are binding.
> It would be helpful (but not required) if you could add a comment stating
> whether your vote is binding or non-binding.
>
> This vote will run for at least 72 hours (but I expect to keep it open for
> longer). Please VOTE as follows:
>
> [ ] +1 Accept Training into the Apache Incubator
> [ ] +0 Abstain
> [ ] -1 Do not accept Training into the Apache Incubator because ...
>
> Thank you for everyone who decided to join in in the past discussions!
> Lars
>
> [1] <
> https://lists.apache.org/thread.html/5c00016b769135cc302bb2ce4e5f6bbfeeda933a07e9c38b5017d651@%3Cgeneral.incubator.apache.org%3E
> >
>
> [2] <
> https://lists.apache.org/thread.html/9cb4d7eef73e0d526e0124944c3d37325aa892675351a1eed0a25de3@%3Cgeneral.incubator.apache.org%3E
> >
>
> [3] 
>
> [4] <
> https://incubator.apache.org/policy/incubation.html#approval_of_proposal_by_sponsor
> >

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

Re: [VOTE] Accept Training into the Apache Incubator

[Matt Sicker]

On Wed, 13 Feb 2019 at 14:38, Lars Francke  wrote:
> I'm not sure if I understand the question. Could you rephrase?
> Do you mean training on "The Apache Way"?

Essentially, yes.

-- 
Matt Sicker 

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

RE: [VOTE] Release Apache NetBeans parent pom 1

[Eric Barboni]

Hi,

I prepared the dist/dev [1]. I hope this is enough to restart vote. If yes, I 
will reply to this thread with [RESTARTING] . 
Mavenized artefacts [3] not changed.

On the copyright dates in NOTICE, 
it's seems that on the sample given [2] it's a range between 2 years, it 
appears that other Apache project have different scheme
-- Extracts
Copyright 2016 The Apache Software Foundation.
Copyright 2014 and onwards The Apache Software Foundation.

Who wins :p ? 

Thank for your advise
Best Regards
Eric

[1] 
https://dist.apache.org/repos/dist/dev/incubator/netbeans/incubating-netbeans-mavenutils/netbeans-parent/
[2] http://www.apache.org/dev/licensing-howto.html#notice
[3] 
https://repository.apache.org/content/repositories/orgapachenetbeans-1007/org/netbeans/maven/netbeans-parent/1/


-Message d'origine-
De : Justin Mclean  
Envoyé : jeudi 14 février 2019 12:26
À : general@incubator.apache.org
Objet : Re: [VOTE] Release Apache NetBeans parent pom 1

Hi,

> Would a rename of the artefacts (zip,asc,sha512)in the 
> https://dist.apache.org/repos/dist/dev/incubator to be enough ?

That would work for me as long as the released artefacts also have that name. 
No need for a revote on the PPMC.

> If possible I would like to keep the NOTICE file in 2017-2018 for this first 
> incubating release.

Yep that’s just  a minor issue and can be fixed next release.

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

Re: [VOTE] Release Apache Zipkin Brave Karaf (Incubating) version 0.1.2

[Adrian Cole]

We would really prefer us to not have to add a non standard and explicit
line in the NOTICE file about "The OpenZipkin Authors" as it doesnt exist
as a legal entity and even if it did, it didn't sign an SGA.

We would like that to not only be a non-blocker for this release, but also
subsequent ones in different repos which are yet to move. In other words,
we would like a clean file and if there is confusion on this topic it be
fully resolved prior to any more work on incubation.

In other words agree that this "The OpenZipkin Authors" addendum to the
NOTICE is neither required nor will be resurrected as a blocker to a future
release or graduation? If this is a disagreement, we would prefer to have
multiple IPMC members say so and why before asking us to escalate to legal.

Finally, there was an unresolved question about branding of the repo. I
dont think we should attempt another release if there is something else
lurking.

Thanks for the help folks.

-Adrian


On Thu, Feb 14, 2019, 7:40 PM John D. Ament  On Thu, Feb 14, 2019 at 6:35 AM Justin Mclean  wrote:
>
> > Hi,
> >
> > > I can follow up with the developer to fix their headers via a github
> > issue (if no one else gets to it before me).
> >
> > I already have raise it as an issue :-)  Add to it it if you want. [1]
> >
> > > Including prior statements about NOTICE is completely optional, but in
> > the
> > > case of no SGA would be ideal.  I don't think that's a blocker for
> > release …
> >
> > No neither do I think it is a blocker, but having a jar in a source
> > release is.
> >
> >
> And I can see in the repo that's already been resolved.  So I think
> Adrian's all set to re-roll the release and put it up for a vote.
>
>
> > Thanks,
> > Justin
> >
> > 1. https://github.com/takari/maven-wrapper/issues/104
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Release Apache Zipkin Brave Karaf (Incubating) version 0.1.2

[John D. Ament]

On Thu, Feb 14, 2019 at 6:35 AM Justin Mclean  wrote:

> Hi,
>
> > I can follow up with the developer to fix their headers via a github
> issue (if no one else gets to it before me).
>
> I already have raise it as an issue :-)  Add to it it if you want. [1]
>
> > Including prior statements about NOTICE is completely optional, but in
> the
> > case of no SGA would be ideal.  I don't think that's a blocker for
> release …
>
> No neither do I think it is a blocker, but having a jar in a source
> release is.
>
>
And I can see in the repo that's already been resolved.  So I think
Adrian's all set to re-roll the release and put it up for a vote.


> Thanks,
> Justin
>
> 1. https://github.com/takari/maven-wrapper/issues/104
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: the case of the maven wrapper

[John D. Ament]

On Thu, Feb 14, 2019 at 3:22 AM Ignasi Barrera  wrote:

> On Thu, 14 Feb 2019 at 09:15, Ignasi Barrera  wrote:
>
> > In the particular case of the "MavenWrapperDownloader.java" file, I would
> > say it is OK not to mention it in the LICENSE/NOTICE files, as per the
> > existing policy [1]. The project does not contain a NOTICE file, so there
> > is nothing to propagate there, and policy says that if the bundled
> > dependency is already ASLv2, there is no need to modify the LICENSE file.
> >
> > IMO, it is fine that the Incubator makes the podlings aware of the "for
> > completeness it is useful to list the products and their versions" part,
> > but just a matter of convenience. The policy is clear, though: it should
> > not be a requirement, and thus the Incubator should enforce that as such
> > (I'm not pretending to say it's doing ti now; just dumping my views).
> >
>
> typo :) s/the Incubator should enforce/the Incubator should *not* enforce/
>

Agreed, +1, there is nothing for us to enforce here.  While it would be
nice to include a mention, the author does not include any NOTICE so there
is nothing for us to propagate to users for a notice that is mandated by
ASF policy nor Apache License.


>
>
> >
> > We can enter the debate about fairness, ethics, etc, and mentioning
> > provenance in the license (but hey, if an ASLv2 licensed project wants to
> > enforce it, it can provide its own NOTICE file). In the end, what is not
> > mandatory in policy should not be a requirement to be implemented by
> > podlings, but a choice of every single community.
> >
> >
> > My $0.02
> >
> > I.
> >
> > [1] http://www.apache.org/dev/licensing-howto.html#alv2-dep
> >
> > On Thu, 14 Feb 2019 at 08:29, Justin Mclean 
> > wrote:
> >
> >> Hi,
> >>
> >> > If we all say fine.. let's just throw more paperwork at it, I would
> ask
> >> you
> >> > to help draft a line for the NOTICE of what we would do. suppose we
> >> would
> >> > also have to do this for gradle etc.
> >>
> >> You would need to do this for any 3rd party file bundled with a release
> >> and yes sometimes this is complex and takes time. See for example Apache
> >> Newt. [1]
> >>
> >> > So basically if we accept that the new norm is this level of detail on
> >> > incidental files,
> >>
> >> It’s a 3rd party file not an incidental file and the ASF has policy
> >> around what to do when including 3rd party files which a (P)PMC and
> >> releases need to comply with. [2][3]
> >>
> >> To comply however is a simple change that needs to be made once to
> >> clearly inculcate the IP province and license of that file to users of
> the
> >> projects.
> >>
> >> > would it be "this includes source generated by the takari maven
> plugin"?
> >> > and of course if we say this, the next cruft is explaining gradle etc.
> >>
> >> If you don’t know what to do ask you mentors or the IPMC for help. If
> you
> >> disagree with advice given then clarify on legal-discuss.
> >>
> >> Thanks,
> >> Justin
> >>
> >> 1. https://github.com/apache/mynewt-newt/blob/master/LICENSE
> >> 2. http://www.apache.org/dev/release-publishing.html#goal
> >> 3. http://www.apache.org/dev/release-publishing.html#valid
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
>

Re: [VOTE] Release Apache Zipkin Brave Karaf (Incubating) version 0.1.2

[Justin Mclean]

Hi,

> I can follow up with the developer to fix their headers via a github issue 
> (if no one else gets to it before me).

I already have raise it as an issue :-)  Add to it it if you want. [1]

> Including prior statements about NOTICE is completely optional, but in the
> case of no SGA would be ideal.  I don't think that's a blocker for release …

No neither do I think it is a blocker, but having a jar in a source release is.

Thanks,
Justin

1. https://github.com/takari/maven-wrapper/issues/104
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Zipkin Brave Karaf (Incubating) version 0.1.2

[John D. Ament]

Hi all,

I just want to point out that the issue is that MavenWrapperDownloader has
incorrect license headers in its source repository, see [1].  We should not
fault Apache projects for leveraging this, since the upstream is not
properly setup.  I can follow up with the developer to fix their headers
via a github issue (if no one else gets to it before me).  Likewise, we
should leave the source in as that is the ideal way to bootstrap the
plugin.  The developer even added it since many Apache projects were
struggling to create releases when his toolkit was in use.  Likewise, since
this project includes no NOTICE file there's nothing to add to a project's
notice file, per the Apache License.

Including prior statements about NOTICE is completely optional, but in the
case of no SGA would be ideal.  I don't think that's a blocker for release
since we have ICLAs on file for the main contributors [2] to this
codebase.  I see Adrian has already corrected this in the repo, so I would
be +1 to releasing with that modification.

John

[1]:
https://github.com/takari/maven-wrapper/blob/master/.mvn/wrapper/MavenWrapperDownloader.java
[2]:
https://github.com/apache/incubator-zipkin-brave-karaf/graphs/contributors



On Thu, Feb 14, 2019 at 1:02 AM Dave Fisher  wrote:

> Hi Adrian/Justin,
>
> We are discussing the wrong points. The clear question is what is
> MavenWrapperDownloader.java and why does it need to be in source release?
> It doesn’t.
>
> The Zipkin build instruction should include the installation instructions
> for MavenWrapper. [3]
>
> Adrian will that work for Zipkin?
>
> Regards,
> Dave
>
> [3] https://www.baeldung.com/maven-wrapper
>
> Sent from my iPhone
>
> > On Feb 13, 2019, at 6:07 PM, Justin Mclean 
> wrote:
> >
> > Hi,
> >
> > Sorry but it’s -1 (binding) as it contains compiled code (a .jar) [1],
> an ASF release must consist of source code only. The other issue are minor
> IMO and can be fixed in a future release.
> >
> > I checked:
> > - incubating in name
> > - signature and hashed correct
> > - LICENSE is fine
> > - NOTICE has some minor issue (see below)
> > - All source files have have headers
> > - An unexpected binary file in source release [1]
> > - Can compile from source
> >
> > Re NOTICE did you project come to the ASF in 2016? Who did it come from,
> and if the headers were changed to ASF ones then they should be mentioned
> in NOTICE.
> >
> > Should this file have an ASF header? [2] Where did it originally come
> from? Answer to this question may mean that some changes to LICENSE and
> HEADER are required.
> >
> > Re the maven wrapper jar several project have run into this issue and
> have managed to resolve it without including the jar. You should be able to
> find them with a search of this list. BTW A warning that rat didn’t pick
> this up and it seem it doesn’t follow directories with a dot in front of
> them.
> >
> > While i can compile it looks like the build assumes the code is checked
> out of GitHub and you’re not compiling the source release as I get a lot of
> these:
> > failure occured while calling class
> com.mycila.maven.plugin.license.git.CopyrightRangeProvider
> > java.lang.RuntimeException: Could not compute the year of the last git
> commit for file x
> >
> > Thanks,
> > Justin
> >
> > 1. ./.mvn/wrapper/maven-wrapper.jar
> > 2. .mvn/wrapper/MavenWrapperDownloader.java
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>

Re: [VOTE] Release Apache NetBeans parent pom 1

[Justin Mclean]

Hi,

> Would a rename of the artefacts (zip,asc,sha512)in the 
> https://dist.apache.org/repos/dist/dev/incubator to be enough ?

That would work for me as long as the released artefacts also have that name. 
No need for a revote on the PPMC.

> If possible I would like to keep the NOTICE file in 2017-2018 for this first 
> incubating release.

Yep that’s just  a minor issue and can be fixed next release.

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 NetBeans parent pom 1

[Eric Barboni]

Hi Justin,

 Thanks for the answer. 
 Would a rename of the artefacts (zip,asc,sha512)in the 
https://dist.apache.org/repos/dist/dev/incubator to be enough ? Should I cancel 
and restart a vote PPMC + IPMC ?

 If possible I would like to keep the NOTICE file in 2017-2018 for this first 
incubating release. As Apache Maven convenience binaries will depend on this 
particular artefact for Apache NetBeans (incubating) 9.0 and (incubating) 9 10 
that will have notice copyright  dated 2017-2018.

Best Regards
Eric 
 
-Message d'origine-
De : Justin Mclean  
Envoyé : jeudi 14 février 2019 04:02
À : general@incubator.apache.org
Objet : Re: [VOTE] Release Apache NetBeans parent pom 1

Hi,

Sorry but it’s -1 binding as the artefacts do not have incubating in their 
name. [1]

I checking
- no incubating in name [1] It might also be a good idea to add apache in there 
as well.
- signatures and hashed good
- DISCLAIMER exits
- LICENSE is OK
- NOTICE has wrong year
- No source code and no binaries
- Can compile from source

Thanks,
Justin

1. https://incubator.apache.org/policy/incubation.html#releases


1. 
https://dist.apache.org/repos/dist/dev/incubator/netbeans/incubator-netbeans-mavenutils/netbeans-parent/
-
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: [VOTE] Release Apache Doris 0.9.0-incubating-rc02

[Li,De(BDG)]

Thank you, Justin, we will fix the license issue in next release.

On 2019/2/14 上午10:39， "Justin Mclean"  wrote:

>Hi,
>
>+1 binding but LICENSE is missing a couple of licenses please fix in next
>release.
>
>Checked:
>- incubating in name
>- hashes and signatures good
>- LICENSE is missing some licenses (se below)
>- NOTICE is fine
>- No unexpected binaries in file
>- All ASF source files have ASF headers
>- On OSX so didn’t build
>
>LICENSE is missing MIT licensed Sizzle.js [1] included in jQuery and MIT
>licensed normalize.css included in bootstrap.css.
>
>Thanks.
>Justin
>
>1. ./webroot/static/jquery.js
>2. ./webroot/static/bootstrap.css
>
>
>-
>To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>For additional commands, e-mail: general-h...@incubator.apache.org
>

Re: the case of the maven wrapper

[Ignasi Barrera]

On Thu, 14 Feb 2019 at 09:15, Ignasi Barrera  wrote:

> In the particular case of the "MavenWrapperDownloader.java" file, I would
> say it is OK not to mention it in the LICENSE/NOTICE files, as per the
> existing policy [1]. The project does not contain a NOTICE file, so there
> is nothing to propagate there, and policy says that if the bundled
> dependency is already ASLv2, there is no need to modify the LICENSE file.
>
> IMO, it is fine that the Incubator makes the podlings aware of the "for
> completeness it is useful to list the products and their versions" part,
> but just a matter of convenience. The policy is clear, though: it should
> not be a requirement, and thus the Incubator should enforce that as such
> (I'm not pretending to say it's doing ti now; just dumping my views).
>

typo :) s/the Incubator should enforce/the Incubator should *not* enforce/


>
> We can enter the debate about fairness, ethics, etc, and mentioning
> provenance in the license (but hey, if an ASLv2 licensed project wants to
> enforce it, it can provide its own NOTICE file). In the end, what is not
> mandatory in policy should not be a requirement to be implemented by
> podlings, but a choice of every single community.
>
>
> My $0.02
>
> I.
>
> [1] http://www.apache.org/dev/licensing-howto.html#alv2-dep
>
> On Thu, 14 Feb 2019 at 08:29, Justin Mclean 
> wrote:
>
>> Hi,
>>
>> > If we all say fine.. let's just throw more paperwork at it, I would ask
>> you
>> > to help draft a line for the NOTICE of what we would do. suppose we
>> would
>> > also have to do this for gradle etc.
>>
>> You would need to do this for any 3rd party file bundled with a release
>> and yes sometimes this is complex and takes time. See for example Apache
>> Newt. [1]
>>
>> > So basically if we accept that the new norm is this level of detail on
>> > incidental files,
>>
>> It’s a 3rd party file not an incidental file and the ASF has policy
>> around what to do when including 3rd party files which a (P)PMC and
>> releases need to comply with. [2][3]
>>
>> To comply however is a simple change that needs to be made once to
>> clearly inculcate the IP province and license of that file to users of the
>> projects.
>>
>> > would it be "this includes source generated by the takari maven plugin"?
>> > and of course if we say this, the next cruft is explaining gradle etc.
>>
>> If you don’t know what to do ask you mentors or the IPMC for help. If you
>> disagree with advice given then clarify on legal-discuss.
>>
>> Thanks,
>> Justin
>>
>> 1. https://github.com/apache/mynewt-newt/blob/master/LICENSE
>> 2. http://www.apache.org/dev/release-publishing.html#goal
>> 3. http://www.apache.org/dev/release-publishing.html#valid
>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

Re: the case of the maven wrapper

[Adrian Cole]

FYI I've asked takari to donate the wrapper to the ASF. It is
important but tiny
https://github.com/takari/takari-maven-plugin/issues/18

Meanwhile, we will remove the wrapper from the source distribution as
putting it in the NOTICE file is something off-putting to a few of our
contributors. We can build without the wrapper and it isn't worth
making a commitment to the NOTICE file for what seems not thought
through.

If the enforcement rules loosen back to where we don't need to do
this, or the plugin or a copy of it is donated to the ASF, we'll
likely put it back into the source distribution.

On Thu, Feb 14, 2019 at 3:29 PM Justin Mclean  wrote:
>
> Hi,
>
> > If we all say fine.. let's just throw more paperwork at it, I would ask you
> > to help draft a line for the NOTICE of what we would do. suppose we would
> > also have to do this for gradle etc.
>
> You would need to do this for any 3rd party file bundled with a release and 
> yes sometimes this is complex and takes time. See for example Apache Newt. [1]
>
> > So basically if we accept that the new norm is this level of detail on
> > incidental files,
>
> It’s a 3rd party file not an incidental file and the ASF has policy around 
> what to do when including 3rd party files which a (P)PMC and releases need to 
> comply with. [2][3]
>
> To comply however is a simple change that needs to be made once to clearly 
> inculcate the IP province and license of that file to users of the projects.
>
> > would it be "this includes source generated by the takari maven plugin"?
> > and of course if we say this, the next cruft is explaining gradle etc.
>
> If you don’t know what to do ask you mentors or the IPMC for help. If you 
> disagree with advice given then clarify on legal-discuss.
>
> Thanks,
> Justin
>
> 1. https://github.com/apache/mynewt-newt/blob/master/LICENSE
> 2. http://www.apache.org/dev/release-publishing.html#goal
> 3. http://www.apache.org/dev/release-publishing.html#valid
>
>
> -
> 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: the case of the maven wrapper

[Ignasi Barrera]

In the particular case of the "MavenWrapperDownloader.java" file, I would
say it is OK not to mention it in the LICENSE/NOTICE files, as per the
existing policy [1]. The project does not contain a NOTICE file, so there
is nothing to propagate there, and policy says that if the bundled
dependency is already ASLv2, there is no need to modify the LICENSE file.

IMO, it is fine that the Incubator makes the podlings aware of the "for
completeness it is useful to list the products and their versions" part,
but just a matter of convenience. The policy is clear, though: it should
not be a requirement, and thus the Incubator should enforce that as such
(I'm not pretending to say it's doing ti now; just dumping my views).

We can enter the debate about fairness, ethics, etc, and mentioning
provenance in the license (but hey, if an ASLv2 licensed project wants to
enforce it, it can provide its own NOTICE file). In the end, what is not
mandatory in policy should not be a requirement to be implemented by
podlings, but a choice of every single community.


My $0.02

I.

[1] http://www.apache.org/dev/licensing-howto.html#alv2-dep

On Thu, 14 Feb 2019 at 08:29, Justin Mclean 
wrote:

> Hi,
>
> > If we all say fine.. let's just throw more paperwork at it, I would ask
> you
> > to help draft a line for the NOTICE of what we would do. suppose we would
> > also have to do this for gradle etc.
>
> You would need to do this for any 3rd party file bundled with a release
> and yes sometimes this is complex and takes time. See for example Apache
> Newt. [1]
>
> > So basically if we accept that the new norm is this level of detail on
> > incidental files,
>
> It’s a 3rd party file not an incidental file and the ASF has policy around
> what to do when including 3rd party files which a (P)PMC and releases need
> to comply with. [2][3]
>
> To comply however is a simple change that needs to be made once to clearly
> inculcate the IP province and license of that file to users of the projects.
>
> > would it be "this includes source generated by the takari maven plugin"?
> > and of course if we say this, the next cruft is explaining gradle etc.
>
> If you don’t know what to do ask you mentors or the IPMC for help. If you
> disagree with advice given then clarify on legal-discuss.
>
> Thanks,
> Justin
>
> 1. https://github.com/apache/mynewt-newt/blob/master/LICENSE
> 2. http://www.apache.org/dev/release-publishing.html#goal
> 3. http://www.apache.org/dev/release-publishing.html#valid
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>