[Discuss] Graduate Apache OpenWhisk (incubating) as a TLP

[David P Grove]

Hi all,

In the two and a half years that Apache OpenWhisk (incubating) has
been a part of the Apache incubator, the community has grown, diversified,
and adapted to the Apache Way. We believe that the project is ready to
graduate to a TLP.

As a community, we have discussed [1] and voted [2] to graduate to a
TLP, we have worked through the maturity model [3], notified the IPMC that
we have the intention to graduate [4], discussed our resolution [5, 6] and
proposed PMC chair [7].

Please see the draft resolution appended below and provide any
comments or feedback you have on it.

We would like to continue the graduation process and hereby ask you
all for your opinion on this. The discussion is open for 72 hours, after
which we will start a [VOTE] on graduation here.

thanks,

--dave
on behalf of the Apache OpenWhisk PPMC

[1]
https://lists.apache.org/thread.html/8daa3a05148f54ca82458777e2b2b5e25ba99d39dcf8ce7dd85d0188@%3Cdev.openwhisk.apache.org%3E
[2]
https://lists.apache.org/thread.html/34e5740cdf1ce5f74c9468d9f9b222ba8994f0c63a82777b020cdf10@%3Cdev.openwhisk.apache.org%3E
[3] https://cwiki.apache.org/confluence/display/OPENWHISK/Project+Maturity
+Model
[4]
https://lists.apache.org/thread.html/02dd71dcc6b2f326015954388c61d06d12f982fd64f34ee40e076171@%3Cgeneral.incubator.apache.org%3E
[5]
https://lists.apache.org/thread.html/5b52f89c9af99fc79c7d466db83be1b299a441f258b8419285359ac5@%3Cdev.openwhisk.apache.org%3E
[6]
https://lists.apache.org/thread.html/5a44e377f3292a24de13c3a23f82735b82364c6419fab13e997bd91a@%3Cdev.openwhisk.apache.org%3E
[7]
https://lists.apache.org/thread.html/1c0366181b6812de7ae8f68cb546bb3a4512b53dc4e89edba7b27075@%3Cdev.openwhisk.apache.org%3E
[8]
https://lists.apache.org/thread.html/1c0366181b6812de7ae8f68cb546bb3a4512b53dc4e89edba7b27075@%3Cdev.openwhisk.apache.org%3E


Proposed Resolution for the Apache OpenWhisk project for the ASF Board:

X. Establish the Apache OpenWhisk Project

WHEREAS, the Board of Directors deems it to be in the best interests of the
Foundation and consistent with the
Foundation's purpose to establish a Project Management Committee charged
with the creation and maintenance of
open-source software, for distribution at no charge to the public, related
to a platform for building serverless applications with functions.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC),
to be known as the "Apache OpenWhisk Project",
be and hereby is established pursuant to Bylaws of the Foundation; and be
it further

RESOLVED, that the Apache OpenWhisk Project be and hereby is responsible
for the creation and maintenance of software
related to a platform for building serverless applications with functions;
and be it further

RESOLVED, that the office of "Vice President, Apache OpenWhisk" be and
hereby is created, the person holding such office to
serve at the direction of the Board of Directors as the chair of the Apache
OpenWhisk Project, and to have primary responsibility
for management of the projects within the scope of responsibility of the
Apache OpenWhisk Project; and be it further

RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the
Apache OpenWhisk Project:
Bertrand Delacretaz, bdelacre...@apache.org
Carlos Santana, csantan...@apache.org
Chetan Mehrotra, chet...@apache.org
Dave Grove, dgr...@apache.org
Dominic Kim, styl...@apache.org
Dragos Dascalita Haut, dra...@apache.org
James Dubee, du...@apache.org
James Thomas, jamestho...@apache.org
Jeremias Werner, jeremiaswer...@apache.org
Krzysztof Sobkowiak, ksobkow...@apache.org
Markus Thömmes, markusthoem...@apache.org
Matt Rutkowski, mrutkow...@apache.org
Matt Sicker, mattsic...@apache.org
Michele Sciabarra, msciaba...@apache.org
Olivier Tardieu, tard...@apache.org
Rob Allen, akra...@apache.org
Rodric Rabbah, rab...@apache.org
Sven Lange-Last, sla...@apache.org
Tyson Norris, tysonnor...@apache.org
Vincent Hou, houshen...@apache.org

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dave Grove be appointed to the
office of Vice President, Apache OpenWhisk,
to serve in accordance with and subject to the direction of the Board of
Directors and the Bylaws of the Foundation until death,
resignation, retirement, removal or disqualification, or until a successor
is appointed; and be it further

RESOLVED, that the Apache OpenWhisk Project be and hereby is tasked with
the migration and rationalization of the Apache
Incubator OpenWhisk podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache Incubator
OpenWhisk podling encumbered upon the Apache Incubator
Project are hereafter discharged.

[RESULT] was: [VOTE] Release Apache Flagon (Incubating) v2.0.0

[Joshua Poore]

Hi Everyone,

VOTING for Apache Flagon UserALE.js (Incubating) v2.0.0 has closed on both dev@ 
and general@.

This Major release includes a wealth of additional features beyond v1.0.0, 
notably:

1. Interval Logs
2. WebExtensionSupport for Chrome/Firefox
3. API support for filtering, mapping, and custom logs 
4. Overhauled Unit Tests

The VOTE's have been counted and RESULT's are as follows:

[ 7 ] +1, let's get it released!!!
Joshua Poore
Laura Mariano
Rob Foley
Michael Schreiber
Dave Meikle* (Flagon PMC)
Justin Mclean* (IPMC)
Paul King* (IPMC)

[ 0 ] +/-0, fine, but consider to fix few issues before…
[ 0 ] -1, nope, because... (and please explain why)

* Binding VOTE

The VOTE to release Apache Flagon UserALE.js (Incubating) v2.0.0 PASSES!

Thanks to all who VOTED!

The Flagon community will now progress with the remainder of the release 
procedures.


> On Jul 1, 2019, at 7:15 PM, Paul King  wrote:
> 
> Yes, when I say "probably worth correcting" I mean for future builds if
> possible. Good luck with the release.
> 
> Cheers, Paul.
> 
> 
> 
> Virus-free.
> www.avast.com
> 
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> 
> On Tue, Jul 2, 2019 at 2:05 AM Joshua Poore 
> wrote:
> 
>> Thanks, Paul.
>> 
>> Yes, some of our webextension files are build from a few other source
>> files. The best way we could manage to get headers in those these build
>> files resulted in some repetition of headers from various arc files. We’ll
>> see if we can’t find a better way, but at present we’re leaning on
>> compliance and functional soundness.
>> 
>> Joshua Poore
>> 
>> 
>>> On Jul 1, 2019, at 10:01 AM, Paul King  wrote:
>>> 
>>> +1 (binding)
>>> 
>>> Checked:
>>> * incubator in name
>>> * LICENSE/NOTICE files
>>> * checksums
>>> * ASF headers in files (though a few js files in UserAleWebExtension have
>>> the header repeated multiple times - not a big deal but probably worth
>>> correcting unless these files are generated that way)
>>> 
>>> Cheers, Paul.
>>> 
>>> 
>>> <
>> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
>>> 
>>> Virus-free.
>>> www.avast.com
>>> <
>> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
>>> 
>>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>> 
>>> On Mon, Jul 1, 2019 at 11:24 PM Joshua Poore 
>>> wrote:
>>> 
 Hi Folks,
 
 72 hours has passed on our VOTE on general@ to Release Apache Flagon
 v2.0.0.
 
 We are missing one binding VOTE from IPMC to release. Please review and
 VOTE.
 
 We presently have +4 community votes & +2  binding votes. No one has
>> voted
 +0 or -1.
 
 Thanks!
 
 Joshua Poore
 
 
> On Jun 29, 2019, at 8:06 PM, Justin Mclean 
 wrote:
> 
> Hi,
> 
> +1 (binding)
> 
> I checked:
> - incubating in name
> - signature and hashes fine
> - DISCLAIMER exists
> - LICENSE has minor issue (see below)
> - NOTICE is fine
> - all ASF files have correct headers
> 
> As noted above the LICENSE file has incorrect copyright line in the
 license appendix.
> 
> 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: [VOTE] Release Apache Flagon (Incubating) v2.0.0

[Paul King]

Yes, when I say "probably worth correcting" I mean for future builds if
possible. Good luck with the release.

Cheers, Paul.



Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Tue, Jul 2, 2019 at 2:05 AM Joshua Poore 
wrote:

> Thanks, Paul.
>
> Yes, some of our webextension files are build from a few other source
> files. The best way we could manage to get headers in those these build
> files resulted in some repetition of headers from various arc files. We’ll
> see if we can’t find a better way, but at present we’re leaning on
> compliance and functional soundness.
>
> Joshua Poore
>
>
> > On Jul 1, 2019, at 10:01 AM, Paul King  wrote:
> >
> > +1 (binding)
> >
> > Checked:
> > * incubator in name
> > * LICENSE/NOTICE files
> > * checksums
> > * ASF headers in files (though a few js files in UserAleWebExtension have
> > the header repeated multiple times - not a big deal but probably worth
> > correcting unless these files are generated that way)
> >
> > Cheers, Paul.
> >
> >
> > <
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> >
> > Virus-free.
> > www.avast.com
> > <
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> >
> > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >
> > On Mon, Jul 1, 2019 at 11:24 PM Joshua Poore 
> > wrote:
> >
> >> Hi Folks,
> >>
> >> 72 hours has passed on our VOTE on general@ to Release Apache Flagon
> >> v2.0.0.
> >>
> >> We are missing one binding VOTE from IPMC to release. Please review and
> >> VOTE.
> >>
> >> We presently have +4 community votes & +2  binding votes. No one has
> voted
> >> +0 or -1.
> >>
> >> Thanks!
> >>
> >> Joshua Poore
> >>
> >>
> >>> On Jun 29, 2019, at 8:06 PM, Justin Mclean 
> >> wrote:
> >>>
> >>> Hi,
> >>>
> >>> +1 (binding)
> >>>
> >>> I checked:
> >>> - incubating in name
> >>> - signature and hashes fine
> >>> - DISCLAIMER exists
> >>> - LICENSE has minor issue (see below)
> >>> - NOTICE is fine
> >>> - all ASF files have correct headers
> >>>
> >>> As noted above the LICENSE file has incorrect copyright line in the
> >> license appendix.
> >>>
> >>> 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
>
>

[ANNOUNCE] Apache Doris (incubating) 0.10.0 Release

[MingyuChen]

Hi All,

We are pleased to announce the release of Apache Doris 0.10.0-incubating.

Apache Doris (incubating) is an MPP-based interactive SQL data warehousing for 
reporting and analysis.
Thanks to everyone who has contributed to this release.
The release and its note can be found here:
https://github.com/apache/incubator-doris/releases/tag/0.10.0-rc04 



Best Regards,

On behalf of the Doris team,
ChenMingyu

Re: [VOTE] Release Apache Doris 0.10.0-incubating-rc04

[MingyuChen]

Hi ShaoFeng:
Thanks for your check!

> 在 2019年7月1日，上午11:21，ShaoFeng Shi  写道：
> 
> +1
> I have checked:
> 
> 1. Download links are all good.
> 2. Checksums and PGP signatures are OK.
> 3. LICENSE and NOTICE files are all corrected.
> 
> 
> Best regards,
> 
> Shaofeng Shi 史少锋
> Apache Kylin PMC
> Email: shaofeng...@apache.org
> 
> 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
> 
> 
> 
> 
> MingyuChen  于2019年6月30日周日 下午5:25写道：
> 
>> Hi Sheng Wu:
>> 
>> Thank you for your remind.
>> 
>> We just use MySQL client library in Doris so that Doris is able to visit
>> external MySQL table.
>> Without MySQL client library, Doris still works, fully functional.
>> So I think this dependency is OPTIONAL to Doris.
>> 
>> On the other hand, we are considering to replace the MySQL client library
>> with other alternative implements,
>> so that it will not be a problem anymore.
>> 
>> 
>>> 在 2019年6月30日，上午11:39，Sheng Wu  写道：
>>> 
 We will change the default building options of some libraries which
>>> License are not compatible with ASL, such as Mysql, to false
>>> on next release.
>>> 
>>> Just a reminder.
>>> For this kind of dependency, you also should make this library as
>> optional
>>> in your feature. Such as for MySQL, should have a default DB, which
>> license
>>> is compatible with Apache 2.0
>>> If MySQL is always required, and you just didn't include in binary, it is
>>> still the catalog X dependency.
>>> 
>>> Sheng Wu 吴晟
>>> 
>>> Apache SkyWalking, ShardingSphere, Zipkin
>>> Twitter, wusheng1108
>>> 
>>> 
>>> MingyuChen  于2019年6月30日周日 上午9:55写道：
>>> 
 Hi Willem:
 
 Thank you for your check.
 
 We will change the default building options of some libraries which
 License are not compatible with ASL, such as Mysql, to false
 on next release.
 
 
> 在 2019年6月29日，下午5:58，Willem Jiang  写道：
> 
> +1.
> 
> I checked
> The artifacts has incubating in the name.
> There is no binary in the release kit.
> signature and hash is OK
> DISCLAIMER file exists
> LICENSE and NOTICE looks good to me.
> 
> There is a license notice section in the README file need to be
> polished, I think by default build we should exclude the libraries
> which License is not compiled with ASL.
> End user could enable the feature by building the binary himself with
> some additional options.
> 
> Willem Jiang
> 
> Twitter: willemjiang
> Weibo: 姜宁willem
> 
> On Tue, Jun 25, 2019 at 9:15 AM 陈明雨  wrote:
>> 
>> Hi all,
>> 
>> 
>> Please review and vote on Apache Doris 0.10.0-incubating-rc04 release.
>> 
>> 
>> Apache Doris is an MPP-based interactive SQL data warehousing for
 reporting and analysis.
>> 
>> 
>> The Apache Doris community has voted on and approved this release:
>> 
 
>> https://lists.apache.org/thread.html/a4b5c1102168769e6802aa7fe4db0482f7288d76210b58125b074355@%3Cdev.doris.apache.org%3E
>> 
>> 
>> The vote result email is at end of this thread:
>> 
 
>> https://lists.apache.org/thread.html/a4b5c1102168769e6802aa7fe4db0482f7288d76210b58125b074355@%3Cdev.doris.apache.org%3E
>> 
>> 
>> The release candidate has been tagged in GitHub as 0.10.0-rc04,
 available here:
>> https://github.com/apache/incubator-doris/releases/tag/0.10.0-rc04
>> 
>> 
>> = CHANGE LOG 
>> 
>> 
>> New Features:
>> 
>> 
>> * Support Routine Load
>> Doris now support routine load job, which allow user to create a
>> routine
>> load job with simple instruction, and the data will be consumed and
 loaded
>> into Doris automatically. More information and guide can be found in
>> [Routine Load](
 
>> https://github.com/apache/incubator-doris/blob/master/docs/documentation/cn/administrator-guide/load-data/routine-load-manual.md
 ).
>> 
>> 
>> * Support Doris on ES
>> Doris now support querying Elasticsearch. User can create an extern
 table
>> with engine type `ES`, and query it as a normal table. Doris also
 support a
>> new built-in function `es_query()`, which allow user to write special
>> Elasticsearch query language in SQL. More information and guide can be
>> found in [Doris-On-ES](
 
>> https://github.com/apache/incubator-doris/blob/master/docs/documentation/cn/extending-doris/doris-on-es.md
 )
>> 
>> 
>> * Support UDF and UDAF
>> Now user can write UDF and UDAF in C++ language.
>> 
>> 
>> * New documentation framework
>> All documents of Doris will be moved to the directory
>> `docs/documentation/`. You can see [README](
>> https://github.com/apache/incubator-doris/blob/master/docs/readme.md)
 to
>> get more information, and help us 

[RESULT][VOTE] Release Apache Doris 0.10.0-incubating-rc04

[MingyuChen]

Hi,

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

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

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

The vote thread:
https://lists.apache.org/thread.html/49474e13d2580a344fc4a7edb6b727d2afb5ea95b610fe45a311e275@%3Cgeneral.incubator.apache.org%3E
 


Best Regards,
ChenMingyu

Re: Transition a recently minted Member from PMC to Mentor?

[Justin Mclean]

Hi,

> Where do we find mentor tutorials?

We don’t really have any tutorials or training for mentors. It’s basically 
assumed that you know what to do because you are an ASF member and/or gone 
through the incubating process yourself. (Learning theory might have something 
to say on that, but that’s a discussion for another thread,)

I would start with [1] (which is a little out of date) and more procedural, 
then take a look at some of the incubator talks given over the years.

A previous incubator talk I did (from 2017):
https://www.youtube.com/watch?v=I0-lp1t9ee0 


And here’s a talk I gave last year, and that has been donated to Apache 
Training. [2] I’ll see if I can find a link to the recording.

Try and find other incubator talks that offer different perspectives, each 
ApacheCon has a couple of them and they are usually recorded.

Here’s a short, useful, worked example on how to assemble LICENSE and NOTICE:
https://github.com/justinmclean/ApacheWombat 

https://vimeo.com/171210141 

(I’ve fleshed this out further into a workshop, and it on my todo list to 
donating it.)

Thanks,
Justin

1.https://incubator.apache.org/guides/mentor.html
2. 
https://github.com/apache/incubator-training/tree/master/content/ApacheWay/NavigatingASFIncubation
 

Re: Transition a recently minted Member from PMC to Mentor?

[Trevor Grant]

Where do we find mentor tutorials?

Thanks,

tg

On Mon, Jul 1, 2019 at 3:03 PM Ted Dunning  wrote:

> It is a great thing to consider.
>
> It might be a good thing for that new mentor to spend some time getting
> some intensive mentor tutorial.
>
>
>
> On Mon, Jul 1, 2019 at 12:53 PM Markus Weimer  wrote:
>
> > Hi,
> >
> > is there any reason not to consider a recently minted ASF member who is a
> > PMC member of a podling for becoming a Mentor on that podling?
> >
> > Thanks,
> >
> > Markus
> >
>

Re: Transition a recently minted Member from PMC to Mentor?

[Ted Dunning]

It is a great thing to consider.

It might be a good thing for that new mentor to spend some time getting
some intensive mentor tutorial.



On Mon, Jul 1, 2019 at 12:53 PM Markus Weimer  wrote:

> Hi,
>
> is there any reason not to consider a recently minted ASF member who is a
> PMC member of a podling for becoming a Mentor on that podling?
>
> Thanks,
>
> Markus
>

Transition a recently minted Member from PMC to Mentor?

[Markus Weimer]

Hi,

is there any reason not to consider a recently minted ASF member who is a
PMC member of a podling for becoming a Mentor on that podling?

Thanks,

Markus

Re: LGPL dependency

[Jim Jagielski]

Myrle, did you get all you needed? Enough votes and all to get the release 
unblocked?

> On Jun 28, 2019, at 11:24 AM, Myrle Krantz  wrote:
> 
> I've said it on dev@weex, and on private@incubator, but I wanted to make
> sure and say it here too.  Weex should cut the release.  We'll figure out
> the rest later.  The straw poll on private@incubator also confirms: you
> have my support and the support of many of the mentors in the incubator.  I
> apologize for us blocking you for so long.
> 
> Best Regards,
> Myrle Krantz
> PMC Member, Apache Incubator
> 
> On Thu, Jun 27, 2019 at 6:06 AM 申远  wrote:
> 
>> It looks like we have got result[1] from Legal VP, I will bring it here now
>> 
>>   1. It's fine if Weex only could include header files under 2-clause BSD
>>   license from Webkit at compiling time and has a dynamic link to
>> Webkit.so
>>   at runtime.
>>   2. It's recommended that excluding Webkit.so from Weex convenience
>>   library. Users would include the code snippet below to include both weex
>>   and webkit.
>> 
>> 
>> 
>>weex_sdk
>> 
>> 
>> 
>> 
>> 
>>webkit
>> 
>> 
>> 
>> 
>> The following is what I need to consult from Incubator:
>> 
>> Google will ban all apps without 64 bit published in Google Play from 1st,
>> August, 2019 [1]. Though it's a good idea of excluding Webkit.so from
>> convenience library of Weex, Weex community needs to publish next release
>> with 64-bit support ASAP to give users enough time to upgrade Weex. I'd
>> like to remain webkit.so in convenience library of Weex only for next
>> release.
>> 
>> [1] https://issues.apache.org/jira/browse/LEGAL-464
>> [2] https://developer.android.com/distribute/best-practices/develop/64-bit
>> 
>> Best Regards,
>> YorkShen
>> 
>> 申远
>> 
>> 
>> Roman Shaposhnik  于2019年6月24日周一 上午7:32写道：
>> 
>>> Lets continue this discussion on
>>> https://issues.apache.org/jira/browse/LEGAL-464 please
>>> 
>>> On Sat, Jun 22, 2019 at 2:18 PM Matt Sicker  wrote:
 
 WebKit dates back to KHTML, an LGPL web engine from KDE. It sounds like
 it’s some WebKit specific files that are BSD licensed. I haven’t
>>> inspected
 the individual files, but I suspect that the header files are BSD
>>> licensed
 to make linking less of a legal headache.
 
 On Sat, Jun 22, 2019 at 07:11, Craig Russell 
>>> wrote:
 
> The Webkit license page https://webkit.org/licensing-webkit/ says
> portions licensed under LGPL and BSD licenses.
> 
> Usually this means it's the user's choice which license to use.
> 
> We would choose the BSD License for the components that we use.
> 
> Can you find anywhere a statement that the Webkit.so is licensed only
> under LGPL?
> 
> Craig
> 
>> On Jun 14, 2019, at 1:40 AM, 申远  wrote:
>> 
>> As mentioned above, Webkit is under dual License(BSD and LPGL) and
>>> it's
>> almost impossible for us to figure out which function is a pure BSD
>> function. I don't know
>> Weex.apiA->Webkit.BSD.apiB->Webkit.BSD.apiC->Webkit.LGPL will
>> happen
>>> or
>> not. Perhaps pure BSD header file will lead to pure BSD
>>> implementation.
>> Perhaps?
>> 
>> As for alternative dependency, it's possible if we make some major
> changes
>> to Weex. But convenience binary of each Weex release includes
>>> Webkit.so,
>> how to solve that problem? Maybe publish two convenience binary,
>> one
> named
>> Weex_WebKit.aar and the other named Weex_BSDKit.aar ? Not sounds
>>> like a
>> good idea to me.
>> 
>> Best Regards,
>> YorkShen
>> 
>> 申远
>> 
>> 
>> Sheng Wu  于2019年6月14日周五 下午4:23写道：
>> 
>>> Hi York
>>> 
>>> I am not a C/C++ coder, so I could be wrong.
>>> 
>>> But from I saw, Catalog X dependency required is not right. Like
>> Hen
> said,
>>> alternative is an option.
>>> 
>>> Such as
>>> Today’s another incubating project, ShardingSphere.
>>> When user wants to MySQL sharing, then they needs to accept MySQL
>>> Driver
>>> license first(or already accepted).
>>> But user could use ShardingSphere with PostgreSQL JDBC Driver.
>>> 
>>> 
>>> Sheng Wu
>>> Apache Skywalking, ShardingSphere, Zipkin
>>> 
>>> 
>>> 
 在 2019年6月14日，下午4:15，Hen  写道：
 
 Assuming Weex requires Webkit and is unable to work with an
> alternative,
 the issue here is that users of Weex would seem to have to permit
> reverse
 engineering in their legal terms. Our position has been that that
>>> goes
 beyond the scope of the Apache 2.0 license and would be an
>>> unpleasant
 surprise for users.
 
 (seem to have to  =>  this is how we've discussed the license; an
> actual
 court may decide something completely different)
 
 Looking at Weex's website's description, it does not seem to be
>>> that a
>>> user
 of Weex will already have 

Re: [VOTE] Release Apache Flagon (Incubating) v2.0.0

[Joshua Poore]

Thanks, Paul.

Yes, some of our webextension files are build from a few other source files. 
The best way we could manage to get headers in those these build files resulted 
in some repetition of headers from various arc files. We’ll see if we can’t 
find a better way, but at present we’re leaning on compliance and functional 
soundness.

Joshua Poore


> On Jul 1, 2019, at 10:01 AM, Paul King  wrote:
> 
> +1 (binding)
> 
> Checked:
> * incubator in name
> * LICENSE/NOTICE files
> * checksums
> * ASF headers in files (though a few js files in UserAleWebExtension have
> the header repeated multiple times - not a big deal but probably worth
> correcting unless these files are generated that way)
> 
> Cheers, Paul.
> 
> 
> 
> Virus-free.
> www.avast.com
> 
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> 
> On Mon, Jul 1, 2019 at 11:24 PM Joshua Poore 
> wrote:
> 
>> Hi Folks,
>> 
>> 72 hours has passed on our VOTE on general@ to Release Apache Flagon
>> v2.0.0.
>> 
>> We are missing one binding VOTE from IPMC to release. Please review and
>> VOTE.
>> 
>> We presently have +4 community votes & +2  binding votes. No one has voted
>> +0 or -1.
>> 
>> Thanks!
>> 
>> Joshua Poore
>> 
>> 
>>> On Jun 29, 2019, at 8:06 PM, Justin Mclean 
>> wrote:
>>> 
>>> Hi,
>>> 
>>> +1 (binding)
>>> 
>>> I checked:
>>> - incubating in name
>>> - signature and hashes fine
>>> - DISCLAIMER exists
>>> - LICENSE has minor issue (see below)
>>> - NOTICE is fine
>>> - all ASF files have correct headers
>>> 
>>> As noted above the LICENSE file has incorrect copyright line in the
>> license appendix.
>>> 
>>> 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: [VOTE] Release Apache Flagon (Incubating) v2.0.0

[Paul King]

+1 (binding)

Checked:
* incubator in name
* LICENSE/NOTICE files
* checksums
* ASF headers in files (though a few js files in UserAleWebExtension have
the header repeated multiple times - not a big deal but probably worth
correcting unless these files are generated that way)

Cheers, Paul.



Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Mon, Jul 1, 2019 at 11:24 PM Joshua Poore 
wrote:

> Hi Folks,
>
> 72 hours has passed on our VOTE on general@ to Release Apache Flagon
> v2.0.0.
>
> We are missing one binding VOTE from IPMC to release. Please review and
> VOTE.
>
> We presently have +4 community votes & +2  binding votes. No one has voted
> +0 or -1.
>
> Thanks!
>
> Joshua Poore
>
>
> > On Jun 29, 2019, at 8:06 PM, Justin Mclean 
> wrote:
> >
> > Hi,
> >
> > +1 (binding)
> >
> > I checked:
> > - incubating in name
> > - signature and hashes fine
> > - DISCLAIMER exists
> > - LICENSE has minor issue (see below)
> > - NOTICE is fine
> > - all ASF files have correct headers
> >
> > As noted above the LICENSE file has incorrect copyright line in the
> license appendix.
> >
> > 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 Flagon (Incubating) v2.0.0

[Joshua Poore]

Hi Folks,

72 hours has passed on our VOTE on general@ to Release Apache Flagon v2.0.0.

We are missing one binding VOTE from IPMC to release. Please review and VOTE.

We presently have +4 community votes & +2  binding votes. No one has voted +0 
or -1.

Thanks!

Joshua Poore


> On Jun 29, 2019, at 8:06 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> +1 (binding)
> 
> I checked:
> - incubating in name
> - signature and hashes fine
> - DISCLAIMER exists
> - LICENSE has minor issue (see below)
> - NOTICE is fine
> - all ASF files have correct headers
> 
> As noted above the LICENSE file has incorrect copyright line in the license 
> appendix.
> 
> 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: Podlings, the Incubator, relationships and Apache

[Justin Mclean]

HI,

>   But it is up to any TLP.  

I wouldn't go that far for instance see [1] ("Projects MUST notify the Board…") 
and [2] ("Deviations from this policy may have an adverse effect …”) and [3] 
("Every ASF release MUST comply with ASF licensing policy.”) As someone said in 
another thread a disclaimer doesn’t void legal rights or compliance.

The words "authorized business decision” were chosen very carefully again see 
[2]

> Whether the incubator needs to have a secondary vote is not required by the 
> above.

Currently it requires that 3 IPMC members vote on it  [4], most podlings can’t 
get 3 +1 IPMC votes on their list. Current incubator policy goes a little 
further [5]

>  IPMC members could drop in on the podling vote thread.

IMO Currently the IPMC doesn’t  have the bandwidth to do that, release 
candidates sometime struggle to get votes, having to vote on 2-5x as many RC is 
 unlikely to be possible.

Thanks,
Justin

1. http://www.apache.org/legal/release-policy.html#administration
2. http://www.apache.org/legal/release-policy.html#why
3. http://www.apache.org/legal/release-policy.html#licensing
4. http://www.apache.org/legal/release-policy.html#release-approval
5. https://incubator.apache.org/policy/incubation.html#releases
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Podling expectations and some issues encountered in incubation

[Justin Mclean]

Hi,

> Ownership of the Projects.  Once a project enters the Incubator, ASF owns the 
> project.

Owns is probably too strong a word, but it expected they follow ASF policies 
(and what you listed)  by the time they are ready to graduate.

> All trademark/IP around the project belongs to ASF now.

The ASF/ALv2 only asks for a grant of copyright not IP ownership, the code 
actually still belong to it’s original owners (and that’s often noted in the 
NOTICE file), but both IP and trademarks  are taken very seriously.

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

Re: New disclaimer text

[Justin Mclean]

Hi,

>> Some of the project releases may not follow ASF policy or have
>> incomplete or unknown licensing conditions….

Yes just that line added, I put it own the wiki and highlighted any changes.

> It works for me but I'd say "incubating project" to be clearer.

Will change.

> I don't think that works as modifying the disclaimer to list issues
> will change the digests of the archive that's being voted on - and
> those shouldn't change IMO.

I think the intent was to only list known issues, so yes issues found in the 
current RC may not be listed and that may be an issue. I’m not against other 
ideas.

> As Paul suggests in a different thread I'd go for easy to find tickets
> to describe those changes. The disclaimer might point to
> http://incubator.apache.org/release-issues which in turn points to
> those tickets, keyed by release name and version number. Or something
> like that - a permalink that points to the details.

The problem wth that is that content at that URL would change, it hard to 
compare what has changed between releases, or without careful tagging anyway.

Thanks,
Justin



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

Re: New disclaimer text

[Bertrand Delacretaz]

Hi,

On Sun, Jun 30, 2019 at 1:39 AM Justin Mclean  wrote:
> ...I put up suggested text changes for an incubator disclaimer here [1]...

Basically just adding this, right?

> Some of the project releases may not follow ASF policy or have
> incomplete or unknown licensing conditions

It works for me but I'd say "incubating project" to be clearer.

> ...It also been suggested than any known issues be listed in the disclaimer...

I don't think that works as modifying the disclaimer to list issues
will change the digests of the archive that's being voted on - and
those shouldn't change IMO.

As Paul suggests in a different thread I'd go for easy to find tickets
to describe those changes. The disclaimer might point to
http://incubator.apache.org/release-issues which in turn points to
those tickets, keyed by release name and version number. Or something
like that - a permalink that points to the details.

-Bertrand

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

Re: Podling expectations and some issues encountered in incubation

[York Shen]

Agreed with that, from a poddling’s respective, I think it’s important that the 
community understand the following issues before it enters the incubator:
Governance Model. Projects in Incubator would adopt Meritocracy model, no 
exception.
Ownership of the Projects.  Once a project enters the Incubator, ASF owns the 
project. All trademark/IP around the project belongs to ASF now. Though if they 
choose retire from Incubator, the incubator would give it back.

Best Regards,
York Shen

申远

> 在 2019年7月1日，14:32，Geertjan Wielenga  写道：
> 
> Well, I think a lot of frustration with the Apache incubation process could
> be avoided simply by very explicitly asking this question to a community
> planning to start incubation: “Are you aware that until you complete
> incubation you will not be in full control of your project, for example,
> please scrap your release schedule until you complete incubation because
> your release dates will not be under your control?”

Re: Podling expectations and some issues encountered in incubation

[Geertjan Wielenga]

Well, I think a lot of frustration with the Apache incubation process could
be avoided simply by very explicitly asking this question to a community
planning to start incubation: “Are you aware that until you complete
incubation you will not be in full control of your project, for example,
please scrap your release schedule until you complete incubation because
your release dates will not be under your control?”

Gj

On Mon, 1 Jul 2019 at 00:46, Daniel Shahaf  wrote:

> Geertjan Wielenga wrote on Sun, Jun 30, 2019 at 18:14:52 +0200:
> > Any community joining Apache should be very clear in their own minds that
> > the Incubator is there for them to get used to the Apache Way. It is not
> > there for getting releases done in the same cadence as before the
> community
> > entered the Incubator, nor does it carry the responsibility for that.
> Until
> > leaving the Incubator, a project is not in the hands of its community but
> > in those of the Incubator. There should be no confusion about that very
> > simple principle.
>
> I don't understand what you mean by your penultimate sentence.  Might you
> explain it in different words?
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>