【Alibaba Summer of Code】Introduction And Some Questions

[WM]

Dear Mentors:

My name is Renmin Wang, a second-year postgraduate student of national 
university of defense technology. I am interested about participating in Weex 
Project of Alibaba Summer of Code Project.

After reading  High availability and continuous integration [#2421]( 
https://github.com/apache/incubator-weex/issues/2421 
), I have the following 
questions, which I sincerely hope you can discuss with me:


1. Help to build a user-friendly and high availability continuous 
integration(CI) environment and trigger the CI build each time a GitHub PR is 
created or updated.

I found that Travis CI has been integrated into the project which has met the 
issue's requirements.  After my investigation, I believe Travis CI is the best 
choice for our project, which is an open source project that might need a free 
MAC image. So, does the CI referred in the issue specially means Travis CI?


2. Help to build a mobile test infrastructure which provides the ability of 
Android and iOS UI/interface test upon the CI environment.

Does this specifically mean writing UITest for UI components, such as  
and  etc.


3. Help to build a static code lint system

I found out that Weex will choose ESLint as the default Code Lint tool when 
installing, and both the Vue and Rax can use ESLint for static code analysis. 
So does "help to build the static Code Lint system" refer to incubator-weex 
Project itself?


Finally, is there any specific content requirements and templates that I have 
to follow in my proposal? For example, the Proposal of GSOC includes Project 
Description, Project Outline, and Timeline, etc. Or is there any suggestions?

I am trying my best on writing the proposal. At your convince, would you please 
give me some feedback? Due to the limited time for the proposal, a prompt reply 
is greatly appreciated.


Best wishes,

Renmin Wang
王仁敏

Re: [ANNOUNCEMENT] The minute of Weex Meetup - June 10th, 2019

[申远]

Thanks, I will bring this to general@incubator.a.o later.

Best Regards,
YorkShen

申远


Jan Piotrowski  于2019年6月12日周三 上午1:54写道：

> > Cordova does too, so Jan may be able to answer.
>
> Apache Cordova fortunately only _uses_ it via APIs that are offered by the
> OS, and does not _include_ it (or any of its code) - so this problem never
> came up.
>
> -J
>
> Am Di., 11. Juni 2019 um 18:32 Uhr schrieb Myrle Krantz  >:
>
> > On Tue, Jun 11, 2019 at 2:20 PM 申远  wrote:
> >
> > > >
> > > > But you say "a mixture of LGPL and BSD license at runtime".  What do
> > you
> > > > mean by that?  Is there a way to reduce that to just BSD?  Or are you
> > > using
> > > > WebCore or JavaScriptCore?
> > >
> > >
> > > According to the document, "WebKit is open source software with
> portions
> > > licensed under the LGPL and BSD licenses available here." [1] and Weex
> > just
> > > has a dynamic link to the shared library of WebKit. IMO, the license of
> > > Webkit is really a mess, I really don't know whether Weex will invoke
> > LGPL
> > > part of Webkit at runtime, or there is a call chain will will lead to
> > LGPL
> > > code eventually, like Weex.apiA-> Webkit.BSD.apiA -> Webkit.BSD.apiB ->
> > > Webkit.LGPL.apiC
> > >
> >
> > I suggest asking on the gene...@incubator.apache.org list.  With luck,
> > you'll find someone there who's looked at this more deeply.   (Actually
> > Flex seems to use some part from webkit, so Justin may be able to answer
> > this question.  Cordova does too, so Jan may be able to answer.)  And if
> > not, they may send you on to the le...@apache.org list.  My guess is
> that,
> > if you're only using the parts that you can access using the BSD-licensed
> > headers, that you can consider it to be licensed under BSD.  I hope this
> is
> > true.  But I don't actually know.
> >
> > But what I do know is that all of the header files of a certain directory
> > > [2] in Webkit are under BSD License. And after some major change, Weex
> > > could just import the header file I mentioned at compiling stage,
> though
> > at
> > > runtime Weex has to dynamic link to the shared library of Webkit as
> > before.
> > > As for glibc(sorry for my misspelling, it's not glic, it's glibc),
> which
> > is
> > > also under LGPL license, any serious program could invoke the glibc by
> > > simply a *malloc* function in a *.c file. I don't see any difference
> > there
> > > between Weex using Webkit and any other C program using glibc.
> > >
> >
> > The point is that, if there are alternatives (which there are for the c
> > runtime), then the dependency is optional for your user.  Optional
> > dependencies are treated differently than required dependencies for ASF
> > release policy.  But again, I suggest asking on general@incubator.a.o.
> >
> > Best Regards,
> > Myrle
> >
>