incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jinjiang Zhao <>
Subject Re: Seek one Champion for incubating Weex project
Date Fri, 04 Nov 2016 02:59:27 GMT
Great! It will be our pleasure to have you as a champion. Maybe we can keep
in touch and we are glad to show you more details about Weex :-)



On Nov 04, 2016, at 05:35 AM, "Edward J. Yoon" <> wrote:

Weex team,

I'm recently developing a cross-platform runtime javascript framework and
its backend service [1], so I'm very interested in learning this project. If
you think we can make some synergy, feel free to add me as a mentor, or
champion. I can help.


Best Regards, Edward J. Yoon

-----Original Message-----
From: Benjamin Young []
Sent: Thursday, November 03, 2016 11:13 PM
Cc: weex-apache; Stephan Ewen;;; willem.; Longda Feng
Subject: Re: Seek one Champion for incubating Weex project

Hi Jinjiang and Longda,

Were you all able to find a Champion for the Incubator? I'd hate to see this
great project miss out on benefiting from the Apache Way.

Please let us know if you're still in need of help finding a Champion or




From: 略쏩쉭 <>
Sent: Tuesday, October 11, 2016 5:18:03 PM
Cc: weex-apache; Stephan Ewen;;; willem.; Longda Feng
Subject: Re: Seek one Champion for incubating Weex project

Hi I'am Jinjiang Zhao from Weex team.

Weex hope to help more people build their mobile apps with high perf easier
and faster. Just write once run any platforms. Also it uses HTML, CSS,
JavaScript syntax and is more friendly for frontend developers.
Very glad to know every guys.



瞳 2016쾨10墩11휑,09:54,Longda Feng <> 畇돛:


The Weex team are looking forward to one champion for Weex project

Any help is appreciated.

Weex is a framework for building Mobile cross-platform UI. Weex allows
developers to build iOS, Android and Web user interface with a single

The project is pretty hot in github ,
there are more than 7000 stars on it, there are more than 200 members
in the Weex forum. We want to donate this project to the ASF and
incubate this project in ASF. At the same time, due to there is few
project in the UI field, If the project can incubate in the ASF, I
think more wonderful projects in these field will join ASF in the

Right now, there are 4 mentors in our project, but we are seeking one
champion for our project. If you are interested in this project or
want to help us, please feel free to contact us.



The following is the Weex proposal

Weex Proposal


## Abstract

Weex is a framework for building Mobile cross-platform UI.

## Proposal

Weex allows developers to build iOS,Android and Web user interface
with a single codebase. Compared with WebView based UI framework which
performance and features are limited, Weex preserves its lightweight
development pattern and improve the user experience by high-quality
native view and native features at the same time..

Weex provide a tag based language which maintained a consistent style
with Web standards. Developers write in this language just like
writting in HTML. After transforming to JSBundle by Weex build-in
tools, these tag will be render to higher-level platform-specific
components using Weex SDK.

Because Weex use JavaScript as UI operation and data processing
language which don't need compile before execute in user's Mobile
phone. Interface implemented by Weex is "Dynamic". At the time of this
writing , another famed dynamic Native UI framework is React Native
which developed by Facebook Inc .

Weex and React Native share some common features but have different
language syntax. React Native use specific JSX , whereas Weex use
vanilla Javascript .React Native set target that to replace whole
Mobile App development process, whereas Weex allow developer choose
which page in Mobile App should be implemented by Weex freely. At
principle level React Native adopt "Learn Once, Write Anywhere",
whereas Weex keep "Write Once, Run Everywhere" on different platform
development environment.

We think Weex is an effective supplement to Apache Cordova. Both
Apache Cordova and Weex help developer for leveraging Web development
technique in Mobile age. Boot developer the ability of delivering
consistent content to different platform. With our sincere heart and
determination to open source , we will always keep an open mind for
Apache Cordova community.

## Background

Prior to Weex, in order to develop high performance mobile application
we need write at least three different codebase(iOS,Android,Mobile
Web) or adopt WebView based UI technique(Apache Cordova for example)
which can't satisfy the demand for neat user experience on critical
Interactive scenes.

A special task force at Alibaba Inc try to provide a solution for this
problem have been setup since 2013. At first the team release an
cross-platform rendering engine which render a special format JSON to
native components on different platform. To output this JSON file the
team had build a website which other developer can use to simply
design final interface.

This solution had worked for a while. We found it not able to meet our
requirement , the website be use to design interface have too many
limitations , the JSON file be use to render final interface lacks
enough dynamics. The following discussion inspire we start to develop

Now days, Mobile Taobao App which developed by Alibaba Inc , the
largest user volume eCommerce App in China have adapted Weex in a lot
of UI. We have measured Weex page and prior Mobile Web page which have
same interface design and content with Weex page by A/B testing in one
of Mobile Taobao shopping guide product. The result show the Bounce
Rate drop from 5.5%(Mobile Web page) to 1.7%(Weex page).

## Current Status

Weex have become a open source project since June 2016. It have been
use at a lot of Alibaba producted mobile softwares which running on
the mobile phone of millions of users.

Weex code repository located at GitHub . All development activities
have already happened on GitHub as open source manner.

## Community

The community surrounding Weex is a variety of developer which have
different technique background. iOS,Android,Web developer must
collaborate closely to implement most Weex feature.

Currently total 43 contributors involved in the GitHub development
process. Weex repository have received 517 pull requests until Aug

Beyond committer from Alibaba Inc,Weex community welcome anybody join
us.Now days Evan You from Vue Technology LLC, Wang Run Xiang from
Aipai Inc and lots of GitHub users have contributed source code or
document to Weex.

At the time of this writing ( Aug 2016) Weex GitHub star number is
4935 , watch number is 1829 , fork number is 500.

Weex use GitHub issue for problem tracking and technical discussion.
Currently 437 issues have been submited , 362 of them have been

## Known Risks

"Write Once Run Everywhere" is one of original goal of Weex. But as
Weex provides more feature ,we have received more suggestions for
implement single platform exclusive feature.

## Source Code

* Main repository:

* Weex transformer:

* Weex toolkit:

* Weex loader:

* Gulp Weex:

## Documentation

* English Document:

* Chinese Document(English first , currently only partially been
translate to Chinese):櫓匡匡도

## External Dependencies

* semver( developed by Tom Preston-Werner ,
licensed under the Creative Commons - CC BY 3.0 License.

* core-js( developed by Denis
Pushkarev , licensed under the MIT License.

* vuejs( developed by Yuxi Evan You ,
licensed under the MIT License.

* scroll-to ( developed by
TooTallNate , licensed under the MIT License.

* Chrome V8( developed by Google Inc
& V8 project authors, licensed under BSD License.

* css-layout( developed by
Facebook Inc., licensed under the BSD License.

## Next Goals

* License all Weex source code and documentation to the Apache
Software Foundation. ( We already using Apache license for our main
code repository)

* Setup and standardize the open governance of the Weex Project.

* Move Weex development activity to Apache infrastructure ( Git
repository , Mail list )

To unsubscribe, e-mail:
For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
    • Unnamed multipart/related (inline, None, 0 bytes)
View raw message