Re: [ANNOUNCE] Welcome new committer Douma Fang

[方曦(千之)]

Hey, developers in Weex community,

I am Douma Fang. Thanks a lot for the trust you showed me during my work for 
Incubator Weex project. I think this project is very promising and is very 
worth invseting energy.

And it was also nice of Adam to send me an invitation to become Incubator Weex 
committer.

I come from China and focus on developing components and modules of WeexSDK, 
now I am working for Alibaba,Inc. Also I will continue contributing code to 
Incubator Weex project. I sincerely wish we can have a great cooperation 
relationship in Weex community.

Very sincerely yours,

Douma Fang.

> 在 2018年12月12日，12:43，Adam Feng  写道：
> 
> Hi, Community,
> 
> I am pleased to announce that Douma Fang, whose Apache JIRA user name is @qz 
> and Github user name is @doumafang, has been voted in as a new Incubator Weex 
> committer.
> 
> He has did and is doing a great job on Weex,  especially in iOS part,  and I 
> just want to say thanks and congratulations. Please join me to say 
> congratulations to Douma Fang!
> 
> Douma, would you please briefly introduce yourself to the community?
> 
> Thanks.
> Adam Feng

Re: New committer : Wang Qianyuan

[方曦(千之)]

Congratulations!

> 在 2018年12月10日，15:35，Adam Feng  写道：
> 
> Congratulations!

Re: [VOTE]- Release Apache Weex (Incubating) 0.19.0 [RC4]

[方曦(千之)]

+1

I checked:
- LICENSE file looks good
- NOTICE is ok
- Can build from source by using `scripts/build_from_source.sh`
- Git tag and hash are correct

> 在 2018年9月16日，23:51，Willem Jiang  写道：
> 
> We need more vote for it.
> PPMC Please take some time to verify the kit.
> 
> Willem Jiang
> 
> Twitter: willemjiang
> Weibo: 姜宁willem
> 
> On Mon, Sep 10, 2018 at 5:21 PM 申远  wrote:
>> 
>> +1
>> 
>> I checked the following issue:
>> * LICENSE is good.
>> * No binary file found in the source.
>> * I can build the binary from the source code
>> 
>>> 在 2018年9月10日，12:04，Hanks Zhang  写道：
>>> 
>>> Hi Weex Community,
>>> 
>>> I'm calling this vote to release Apache Weex (Incubating) version 0.19.0.
>>> 
>>> The tag to be voted upon:
>>> 
>>> https://github.com/apache/incubator-weex/commits/0.19.0-rc4
>>> (88caa7fb95a4f8bae6bf3fa53fbd07aa9f496e80)
>>> 
>>> The source code artifacts can be found at:
>>> 
>>> https://dist.apache.org/repos/dist/dev/incubator/weex/0.19.0/RC4/apache-weex-incubating-0.19.0-RC4-src.tar.gz
>>> 
>>> The SHA-512 checksum for apache-weex-incubating-0.19.0-RC4-src.tar.gz:
>>> 
>>> E41BB93D 26BCAB55 F39BF11B 91649221 92A56671 9D076C1A 60182569 E3F29D05
>>> 026F73CC
>>> D09B4F31 2E3012AD A3B00599 B647CD36 E7E0DD8A 19A9D0B3 362C9FFD
>>> 
>>> The artifacts have been signed with Key: 4FD8BC09C7E9DB81, which can be
>>> found in the keys file:
>>> 
>>> https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS
>>> 
>>> Release note about this version:
>>> 
>>> https://issues.apache.org/jira/projects/WEEX/issues/WEEX-464
>>> 
>>> This vote will remain open for at least 72 hours.
>>> 
>>> Please vote on releasing this RC.
>>> 
>>> [ ] +1 approve
>>> 
>>> [ ] +0 no opinion
>>> 
>>> [ ] -1 disapprove (and the reason why)

Re: [VOTE] Move Incubator-weex-site Repo to Gitbox

[方曦(千之)]

+ 1

> 在 2018年8月6日，11:27，Adam Feng  写道：
> 
> +1
> 
> 
> 
> Thanks.
> Adam Feng
> 在 2018年8月2日 +0800 AM11:30，Hanks Zhang ，写道：
>> +1
>> 
>> Totally agree, it can simplify the workflow of updating documents. Really
>> looking forward to this.

Re: [VOTE]: Release Apache Weex (Incubating) 0.19.0 [RC2]

[方曦(千之)]

+1.
Thank you for the release work.

发自我的 iPhone

> 在 2018年6月26日，21:32，申远  写道：
> 
> +1
> Thank you for the release

Re: [DISCUSS] The first conference/meetup of Apache Weex, Hangzhou 2018

[方曦(千之)]

I'm very happy to hear from WeexConf again.

At the same time I am also very eager to hear the voice from the industry team, 
Will WeexConf have invited some non-Alibaba team to do the sharing plan?

As a personal developer, I also very much hope to come to feel the atmosphere 
of communication.

Wish all the best.


> 在 2017年12月11日，22:16，Adam Feng > 
> 写道：
> 
> Hi, all:
> We are going to organise the third Weex Conf (first of Apache Weex) in 
> Hangzhou in mid-January, 2018.
> Potential Content:
> 
> • 1 day conference
> • 7-9 x 40 minute presentations
> • Talks on: Apache way, contributions, performance, applications, best 
> practices, roadmap, etc.
> 
> Please share your ideas on anything…schedules, venues, speakers, attendees, 
> topics, or any talks you would like to give. We want to hear what kind of 
> conference contributors want. This conference should be one that does its 
> best to gather developers who are specifically interested in Weex and cater 
> to the wants and needs of the attendees.
> 
> 
> Thanks.
> Adam Feng

Re: Moving Playground & Examples out of Weex repo

[方曦(千之)]

Also very agree with Hanks.
+1

> 在 2017年12月6日，10:31，Jonathan Dong  写道：
> 
> I love the idea about the online playground demos, things are kept online 
> should be easy to publish, modify and revoke. And for the demo application 
> itself, should be kept as simple as it can be, with minimum features like 
> navigation, debug, QR scan, and maybe a easy access point to the online 
> playground demo.
> 
> I think I can follow this implementation on app side.
> 
>> On 6 Dec 2017, at 10:21 AM, 谷宝剑(剑白)  wrote:
>> 
>> 
>>   have an online playground demo like hao123 website, collect as many 
>> example as possible. so that developer can get lastest feature and example
>> 
>> --From:Hanks 
>> Zhang Time:2017 Dec 5 (Tue) 21:41To:dev 
>> Subject:Re: Moving Playground & Examples out 
>> of Weex repo
>> Moreover, I think our playground app should be redesigned.
>> 
>> Most examples are based on the ".we" framework, which will be removed soon.
>> Even those examples written in Vue are not the best practice and have no
>> reference value. The UI of it is also rough and has not been updated for a
>> long time. We should provide more practical examples and make it easy to
>> use.
>> 
>> Besides the examples, I think this app is also a link between Weex team and
>> developers. It can be used to expose information and thoughts to
>> developers, and can also be used to collect the feedback. We should make
>> good use of it.
>> 
>> Best Regards, Hanks
>> 
>> 
>> 2017-10-31 17:49 GMT+08:00 Adam Feng :
>> 
>>> +1
>>> 
>>> The playground in Weex repo should be a simple “Weex browser”,  a Weex
>>> examples viewer that lets you navigate to Weex experiences just like
>>> websites.
>>> 
>>> Thanks.
>>> Adam Feng
>>> 
>>> On 30 Oct 2017, 10:13 PM +0800, xing zhang ,
>>> wrote:
 We should update the Playground App in App Store both on Android and iOS
 frequently, so the developers can use it to preview their page using the
 new feature, and we can fix the emergency bug at the same time.
 
 2017-10-30 21:59 GMT+08:00 Jonathan Dong  Hi Weex folks,
> 
> I’m thinking of moving Playground and Examples out of Weex repo to
> simplify our code base, I hope we can fully discuss if it is necessary
>>> to
> make this move.
> 
> Playground is a good entry to fiddle with the features of basic
>>> components
> and debug your pages, but it is kind of heavy if we take it as a demo
>>> in
> the Weex repo. As many of the Weex developers tend to create their own
> applications based on the Playground project, I suppose it is
>>> necessary to
> create a simpler one, say AppShell, which only contains QR Scan and
>>> page
> load functions, it would be sufficient for users to test their Weex
>>> pages,
> and much easier for them to take it as an application template to
>>> create
> their own project. Playground should be maintained in a separate repo
>>> in
> WeexTeam, which can be maintained and distributed separately.
> 
> Same things should also happens to examples directory, I suppose what
>>> we
> really need is one or few simplified example to demonstrate the usage
>>> of
> the main components and the way of implementing app using Weex in the
> simplest way, not to keep those detailed example for each components in
> Weex repo. Instead I think it is a good practice to move them into
>>> WeexTeam
> and maintains as a separate repo, and replace the .we implementation
>>> with
> .vue as well.
> 
> Any thought? I hope we can fully discuss it and bring out a proposal to
> make it happen asap.
> 
> Cheers,
> Jonathan Dong
> 
> 
>>> 
>> 
> 

Re: customize request when download bundle js in weex

[方曦(千之)]

Yeath，I am very agree with this case.
And in some scenarios, this feature is very much needed.

+1.

> 在 2017年11月30日，17:16，xing zhang  写道：
> 
> Hi all,
> 
> According to my observation,  you can specify a URL or js content to
> render a page, for URL , then WeexSDK build a request for download the
> resource and pour into the engine to
> 
> render. But in most case, we need customize a request for downloading a
> resource, and we can setup our request userAgent and headers, our server
> can receive these header to
> 
> customize response for a request from a device.
> 
> As for this  we can expose a `renderWithRequest` interface for
> WXSDKInstance, is this way convenient ?
> 
> comments? please