Podling Weex Report Reminder - August 2020

Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 19 August 2020. The report for your podling will form a part of the

ApacheCon @Home 2020 call for papers closes in 2 days!

Hi, Only a couple of days to go before to call for papers closes for ApacheCon @Home 2020 on Monday. The Incubator will be running a track at this online conference, so if you're thinking of submitting something, please don't delay. We'll accept talks on the Apache incubator itself, and

Podling Weex Report Reminder - July 2020

Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 15 July 2020. The report for your podling will form a part of the

Podling Weex Report Reminder - April 2020

Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 15 April 2020, 10:30 am PDT. The report for your podling will form

Re: Podling Weex Report Reminder - April 2020

April, 2020 Weex Weex is a framework for building Mobile cross-platform high performance UI. Weex has been incubating since 2016-11-30. Three most important unfinished issues to address before graduating: 1. Branding issues

Study on annotation of design and implementation choices, and of technical debt

Dear all, As software engineering research teams at the University of Sannio (Italy) and Eindhoven University of Technology (The Netherlands) we are interested in investigating the protocol used by developers while they have to annotate implementation and design choices during their normal

Podling Weex Report Reminder - April 2020

Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 15 April 2020, 10:30 am PDT. The report for your podling will form

[DISCUSS] Next Step

Hi, all After absence from the Apache Weex community for month, I think I am good to be back. And I'd like to share you the next step I'd like to do in the following month. For tech parts, as I am a newbie to iOS, I will just share my opinion on Android*.* 1. Support AndroidX and X86-64. I

Re: Is there a global Object in SandBox mode?

1. If the global variables were allowed, then attackers could even replace the default implementation of string/array or anything eles you can image, then inject it to the global environment, you would be attacked by simply using array in your js bundle. Encoding/Decoding JS is not helpful here.

Re: Is there a global Object in SandBox mode?

Yeah，i get your mean(For security, i encode js bundle with XXTEA in OSS, and download/decode js bundle before SDKManager.render() )。 And in fact，broadcastChannel is content with the need of business. But it not *the best/most easy way to deal with neighbour pages*，especially the second page will

Re: Is there a global Object in SandBox mode?

Well, It seems like you could use broadcastChannel [1] to send message (not callback) among pages. If this is not enough, you have to use low level C++ api to implement it by yourself, which is hard to write and not encouraged. A message among pages is not enough in your case? I'd like to here

Re: Is there a global Object in SandBox mode?

OK, i get it. Thanks! But it is a shame. Both ways are not enough for me. (first is not suitable，second can not save JS callbacks in Native) I want a global object in JS, none of Native business. I use a way like Eventbus for communication between neighbour pages instead. Before Sandbox，I realize

Re: Is there a global Object in SandBox mode?

The answer is no, and you should never consider using Weex without sandbox. You could however, 1. use boradcastChannel [1] for communication between pages 2. or use JS service [2] for vendor.js, which is very similar to global object. [1]

Is there a global Object in SandBox mode?

Dear devs： I'm sorry to disturb you about a question about SandBox in both aos/ios. In some case, developer need a global Object to save/share something for different pages with JS callback，which can not save to Native SharedPreference. *1.In sandBox mode, is there a global Object

Re: A question about Js console log

Oh Yeah! It really works. Because of the old version log is printed in App process. So some people think the log of new version is same as the old. Thanks.I can answer the question in github about android log. 申远 于2020年2月21日周五 下午8:17写道： > Give it a try, and please let me know whether it works.

Two weeks off from Apache Weex community

Hi, there Due to some personal issues, I will have a two-weeks off from Apache Weex community. I probably not would response to mailing list/Github/etc. before 9th, March. Please send me emails (and cc d...@weex.apache.org) directly if there is something *emergency* and *need my help* during

Re: A question about Js console log

Give it a try, and please let me know whether it works. A the JS log is printed from a seperated process, please disable the process filter(or any other log filter you have) in Android Studio. Best Regards, YorkShen 申远 黄天宁 于2020年2月20日周四 上午11:39写道： > Dear devs： >I'm sorry to disturb you

A question about Js console log

Dear devs： I'm sorry to disturb you about the question about Js console log。After checking all issues about it in github, some people have the same question in 0.28。I tried it in a click event： *var logModule = weex.requireModule('sdk-console-log');logModule.switchLogLevel("debug");*

Re: Please give me some advice about my operation of merge request if you have time

Merged *FYI: You can assign me a Github PR next time if you want me to review it.* Best Regards, YorkShen 申远 黄天宁 于2020年1月16日周四 上午10:24写道： > Thanks a lot. > After re-build，All checks have passed > > 申远 于2020年1月15日周三 下午9:58写道： > >> The task of TravisCI failed, and you aren't not allowed to

Re: Please give me some advice about my operation of merge request if you have time

Thanks a lot. After re-build，All checks have passed 申远 于2020年1月15日周三 下午9:58写道： > The task of TravisCI failed, and you aren't not allowed to merge a PR > before it sucesss. > > There are many reasons of the TravisCI failure, you can click the detail > [1] link to see the stacktrace. As for your

Re: Please give me some advice about my operation of merge request if you have time

The task of TravisCI failed, and you aren't not allowed to merge a PR before it sucesss. There are many reasons of the TravisCI failure, you can click the detail [1] link to see the stacktrace. As for your case, I think it caused by network problem between TravisCI server and JCenter mirror on

Re: dev list

Please send an email to dev-subscr...@weex.incubator.apache.org Best Regards, YorkShen 申远 不看盛景、不叙深情 于2020年1月10日周五 下午7:51写道： >

Re: [DISCUSS] Features of Weex 0.30

Just updated the roadmap of Weex in 2020 [1]. Added some feature/infrastructure change we shall do in this year. [1] https://cwiki.apache.org/confluence/display/WEEX/Weex+2020 Best Regards, YorkShen 申远 申远 于2020年1月7日周二 下午10:23写道： > I totally agree with your idea about moving small and

Re: [DISCUSS] Features of Weex 0.30

I totally agree with your idea about moving small and moving fast. But considering the fact that it normally takes a week to go through an Apache Release procedure, I think we can put x86_64 and AndroidX support in version 0.30 , and Kotlin playground in version 0.31. As my job has nothing to do

Re: [DISCUSS] Features of Weex 0.30

I think it would be better to release a smaller version. For example, version 0.30 only support AndroidX, version 0.31 only support x86_x64, and version 0.32 change Java to Kotlin. Faster release, maybe our community can be more active. 在 2020/1/3 下午9:04，“申远” 写入: Dear community,

[ANNOUNCEMENT] New Apache Weex PPMC member: cnryb

Dear community: The Podling Project Management Committee (PPMC) of Apache Weex has invited cnryb as a PPMC member of Apache Weex and I'm glad to announce that he accepted the invitation. >From what we saw, he participated in mailing list discussion very often, through which he shows us that he

回复: [DISCUSS] Now how do you debug the weex program on the app?

@申远 Now andorid devtool support weex sdk 0.28.0. Please review it, thanks. https://github.com/weexteam/android-devtools-for-Apache-Weex/pull/75 发件人: 申远 发送时间: 2019年12月19日 23:04 收件人: dev 主题: Re:

[DISCUSS] Features of Weex 0.30

Dear community, I'd like to add the following features for next verion of Apache Weex - Support x86_64 - Support AndroidX [1] with jetifier [2]. And following features for Weex Playground: - Migrate Weex Playground Android from Java to Kotlin. As Weex Playground is mainly for demo

Re: [ANNOUNCEMENT] New committer: teining(zsmjhtn)

+1 welcome ！ 申远 于2019年12月30日周一 下午2:48写道： > Dear community: > > The Podling Project Management Committee (PPMC) of Apache Weex has invited > teining(zsmjhtn) as a committer of Apache Weex and I'm glad to announce > that he's a committer of Apache Weex now. > > From what we saw, teining(zsmjhtn)

[ANNOUNCEMENT] New committer: teining(zsmjhtn)

Dear community: The Podling Project Management Committee (PPMC) of Apache Weex has invited teining(zsmjhtn) as a committer of Apache Weex and I'm glad to announce that he's a committer of Apache Weex now. >From what we saw, teining(zsmjhtn) showed enough contribution [1] on Github solving over

Podling Weex Report Reminder - January 2020

Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 15 January 2020, 10:30 am PDT. The report for your podling will

Re: Podling Weex Report Reminder - January 2020

The podding report is submitted [1] officially. Thanks again for the help of cnryb. [1] https://cwiki.apache.org/confluence/display/INCUBATOR/January2020 Best Regards, YorkShen 申远 申远 于2019年12月23日周一 下午4:49写道： > Just have a look and edited a few things below: > >1. There is a trademark

Re: [DISCUSS] What should we handle editor.weex.io ?

The JIRA issue is here[1], according to which we need to configure the new domain name in our server, i.g. 47.56.99.112 @Dan @Hanks Zhang Could you have a look? I remembered the nginx server is in some of your hands. [1] https://issues.apache.org/jira/browse/INFRA-19577 Best Regards, YorkShen

Re: Podling Weex Report Reminder - January 2020

Just have a look and edited a few things below: 1. There is a trademark section in the new template report [1] from Incubator. I replied the question according the situation of Apache Weex. 2. We should start a Poddling Name Search [2], through which we will know whether we can

Re: [DISCUSS] What should we handle editor.weex.io ?

Hi I just found editor.weex.apache.org and editor.weex.io are point to the same machine 47.56.99.112. But there is no service for the editor. We may need to setup the nginx to send the redirect URI of editor.weex.apache.org for the request of editor.weex.io. We also need to setup the https

回复: [DISCUSS] What should we handle editor.weex.io ?

The url [1] now shows 'Welcome to nginx!' The url [2] is not found. Looks like some configuration needs to be done on the server 47.56.99.112 [1]http://editor.weex.apache.org/ [2]https://editor.weex.apache.org/ 发件人: 申远 发送时间: 2019年12月16日 16:14 收件人: dev 主题: Re:

Re: Podling Weex Report Reminder - January 2020

@申远 Please review the draft of Podding report[2]. Three most important unfinished issues and How has the community developed since, I'm not sure. I just wrote down the information I was sure. The pull request, issue in github and mailing list are calculated from

Re: [DISCUSS] Now how do you debug the weex program on the app?

I stopped convince the owner to donate it to ASF for the following reasons: - The ability of Debugging JS code of Weex is important, but not necessary. I think compiling tool is necessary, so I make some effort to have weex-loader and weex-cli donated to ASF. - The current owners of

Re: [DISCUSS] Now how do you debug the weex program on the app?

So, please convince the maintainers of devtools-for-Apache-Weex to donate it to ASF. Can also solve our Branding issues[5]. Not only *android-devtools-for-Apache-Weex * but also * devtool-iOS-for-Apache-Weex *. Or bring analyzer ? [5]

Re: [DISCUSS] Now how do you debug the weex program on the app?

[4] https://github.com/weexteam/android-devtools-for-Apache-Weex/blob/develop/LICENSE If you coud get *android-devtools-for-Apache-**Weex *worked, I will persuade the current owner donating it to ASF, so that you(or some other developers) can continue work for *android-devtools-for-Apache-**Weex

Re: [DISCUSS] Now how do you debug the weex program on the app?

These years, I works for Weex community on very low level (C++ code, Javascript interpreter, etc.) and very high level (trademark / license issue / inviting new committer, etc.). I have little exepriece in the middle level things, like a debugger tool developer by a third party developer. I don't

Re: Podling Weex Report Reminder - January 2020

Ok, I will try to write 发件人: 申远 日期: 2019年12月19日 星期四 下午4:53 收件人: dev , 任 跃兵 主题: Re: Podling Weex Report Reminder - January 2020 @cnryb Best Regards, YorkShen 申远 申远 mailto:shenyua...@gmail.com>> 于2019年12月19日周四 下午4:51写道： @cnryb Could you please do the honour for Weex wrting the draft of

Re: [DISCUSS] Now how do you debug the weex program on the app?

I want the weex code to be debugger in the app, which will make everyone work faster and better. Until I find no better way to debug weex code, I think I try my best to maintain devtools-for-Apache-Weex. If I can't do it alone, I will ask the community for help, or ask a friend or colleague

Re: Podling Weex Report Reminder - January 2020

@cnryb Best Regards, YorkShen 申远 申远 于2019年12月19日周四 下午4:51写道： > @cnryb > > Could you please do the honour for Weex wrting the draft of Podding report? > > You can take our previous report [1] as an example, thanks. > > [1] https://cwiki.apache.org/confluence/display/WEEX/Poddling+report > >

Re: Podling Weex Report Reminder - January 2020

@cnryb Could you please do the honour for Weex wrting the draft of Podding report? You can take our previous report [1] as an example, thanks. [1] https://cwiki.apache.org/confluence/display/WEEX/Poddling+report Best Regards, YorkShen 申远 于2019年12月19日周四 下午1:15写道： > Dear podling, > > This

Re: [DISCUSS] Now how do you debug the weex program on the app?

> > In the latest weex SDK version, it seems that the debugging tools are no > longer available. We have updated to the latest weex SDK. > android-devtools-for-Apache-Weex has not been updated for a long time, and > cannot be compiled [1]. Just found the Jcenter repo [3], maybe you could give it

Podling Weex Report Reminder - January 2020

Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 15 January 2020, 10:30 am PDT. The report for your podling will

Re: [DISCUSS] Now how do you debug the weex program on the app?

Sorry [1]https://github.com/weexteam/android-devtools-for-Apache-Weex/issues/72 [2]https://cwiki.apache.org/confluence/display/WEEX/Branding+issues 在 2019/12/19 上午11:04，“任 跃兵” 写入: In the latest weex SDK version, it seems that the debugging tools are no longer available. We have updated to

Re: [DISCUSS] Now how do you debug the weex program on the app?

In the latest weex SDK version, it seems that the debugging tools are no longer available. We have updated to the latest weex SDK. android-devtools-for-Apache-Weex has not been updated for a long time, and cannot be compiled [1]. devtools-for-Apache-Weex [2] seems to be part of the weex

Re: [DISCUSS] Now how do you debug the weex program on the app?

According to my knowledge, the ability of JS debugging is provided by Weex-CLI [1], which may only support the legacy package name(e.g. com.taobao.weex) [1] https://weex.apache.org/guide/develop/weex_cli.html Best Regards, YorkShen 申远 任 跃兵 于2019年12月18日周三 下午8:39写道： > Hi, all > > I compiled

[DISCUSS] Now how do you debug the weex program on the app?

Hi, all I compiled the android playground app using the source code. Execute weex debug to connect and debug. However, the most important js debugging is not available, network review is not available, and occasionally crash. Can you talk about how to debug the weex code on the app in daily

[jira] [Created] (WEEX-680) I Have No right to visit this website

Yayun Dong created WEEX-680: --- Summary: I Have No right to visit this website Key: WEEX-680 URL: https://issues.apache.org/jira/browse/WEEX-680 Project: Weex Issue Type: Bug Components:

Re: [DISCUSS] What should we handle editor.weex.io ?

Hi, all. 1. The server of Weex Editor will be host on the IP address of 47.56.99.112 > (Alibaba Cloud Server) > 2. Establish the following DNS record. > 47.56.99.112 A editor.weex.io > editor.weex.apache.org CNAME editor.weex.io > 3. Keep the disclaimer [1] as it is(Maybe reword it later), and

Re: [ANNOUNCEMENT] New committer: cnryb

You're welcomed. Diversiy of the Weex community is a good sign. FYI: Though many of Weex committers/PPMCs are full-time employees and use Weex in their daily work, it should be remembered that committers make decisions as an individual contributor for helping Apache Weex community, not for

Re: [ANNOUNCEMENT] New committer: cnryb

Thanks PPMC for your recognition and YorkShen for helping me. I'm Ren Yuebing. I live in Beijing and work for Zhilian. Hope weex will be useful to more people. My name on GitHub is cnryb. 在 2019/12/10 上午11:23，“申远” 写入: Dear community. The Podling Project Management Committee (PPMC) of

[ANNOUNCEMENT] New committer: cnryb

Dear community. The Podling Project Management Committee (PPMC) of Apache Weex has invited cnryb as a committer of Apache Weex and I'm glad to announce that he's a committer of Apache Weex now. >From what we saw, cnryb is focusing on solving documation issue [1][2] for Apache Weex, and he gave

Re: [DISCUSS] What should we handle editor.weex.io ?

Technically speaking, DNS CNAME doesn't equal to HTTP redirect. No matter whether there is a CNAME for editor.weex.io, the browser always shows editor.weex.io in its URL bar if you type in editor.weex.io. But yes, we could solve the problem by redirecting editor.weex.io to editor.weex.apache.org

Re: [DISCUSS] What should we handle editor.weex.io ?

The domain is not used to host any content, it just redirects to other URLs that host the actual content: ASF servers for Apache Weex things, random other server for random other content. But do what you think best, I will disengage from this topic after this message. J Am Mi., 4. Dez. 2019 um

Re: [DISCUSS] What should we handle editor.weex.io ?

Based on the conservation with ASF, Brand Management, I don't think it will satiffy ASF's requirement if we keep it in our hands. From my understanding, we either take it down or give it to ASF. *As said by several people several times, Weex is a trademark of ASF and using weex in domain domain

Re: I want to upgrade the iOS Weex Playground

Don't hurry and take your time. FYI: You can take the release procedure [1] of Weex SDK as an example. [1] https://cwiki.apache.org/confluence/display/WEEX/Release+Procedure Best Regards, YorkShen 申远 yaochenfeng <282696...@qq.com> 于2019年12月4日周三 上午11:55写道： > @YorkShen Yes, you can delete

Re: I want to upgrade the iOS Weex Playground

@YorkShen Yes, you can delete existing ones. I'm still learning how to Apache Source Code release for Weex Playground Best Regards, Kyle > 在 2019年12月2日，下午5:14，申远 写道： > > After negotiation with ASF and current owner of Weex Playground, I think > it's better if we could delete existing one as

Re: [DISCUSS] What should we handle editor.weex.io ?

I already sent somthing similar in the other thread, so repeating: If the editor code is not part of Apache Weex, it should live on its own domain. Keep the weex.io domain around so old links continue to work, but redirect the main domain to the Apache Weex site and the editor subdomain to the new

[DISCUSS] What should we handle editor.weex.io ?

Hi, community I am going to move discussion [1] of using editor.weex.io to here, which will make our discussion more clear. Background: http://editor.weex.io is a useful tool for Weex developers, however Weex is a trademark of ASF, and using weex in domain name without approval of ASF is an

Re: I want to upgrade the iOS Weex Playground

After negotiation with ASF and current owner of Weex Playground, I think it's better if we could delete existing one as this will solve the trademark issue. @yaochenfeng <282696...@qq.com> You could start Apache Source Code release for Weex Playground any time, as what I'm going to do(delete an

[GitHub] [incubator-weex-cli] YorkShen commented on issue #603: iOS pod update fails because repo url is not well defined

YorkShen commented on issue #603: iOS pod update fails because repo url is not well defined URL: https://github.com/apache/incubator-weex-cli/issues/603#issuecomment-560260521 It seems like you already find the solution for the problem, could you please help us solving the problem by

[GitHub] [incubator-weex-cli] YorkShen commented on issue #604: weex打包andriod包失败

YorkShen commented on issue #604: weex打包andriod包失败 URL: https://github.com/apache/incubator-weex-cli/issues/604#issuecomment-560258214 The issues is closed due to the repoerter didn't follow the issue template and there is nothing I can do with such litte information.

[GitHub] [incubator-weex-cli] YorkShen closed issue #604: weex打包andriod包失败

YorkShen closed issue #604: weex打包andriod包失败 URL: https://github.com/apache/incubator-weex-cli/issues/604 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use

[GitHub] [incubator-weex-cli] YorkShen commented on issue #605: mac无论创建新项目还是weex run ios 都报错--Error: Cannot find module 'download-git-repo'

YorkShen commented on issue #605: mac无论创建新项目还是weex run ios 都报错--Error: Cannot find module 'download-git-repo' URL: https://github.com/apache/incubator-weex-cli/issues/605#issuecomment-560257470 @erha19 Have a look? This is

Move Github Email notification of weex-cli,weex-loader to comm...@weex.apache.org

Hi, community As this mailing is getting noisy due to the Github Notification, I am going to move those notification to comm...@weex.apache.org A corresponding JIRA issue [1] is created. [1] https://issues.apache.org/jira/browse/INFRA-19509 Best Regards, YorkShen 申远

[GitHub] [incubator-weex-cli] TomWeJack edited a comment on issue #605: mac无论创建新项目还是weex run ios 都报错--Error: Cannot find module 'download-git-repo'

TomWeJack edited a comment on issue #605: mac无论创建新项目还是weex run ios 都报错--Error: Cannot find module 'download-git-repo' URL: https://github.com/apache/incubator-weex-cli/issues/605#issuecomment-559975145 有人遇到过这个问题吗，weex生态比较差，在Q群还有钉钉问了都没人回答，百度也没有相关问题，Does anyone have this trouble

[GitHub] [incubator-weex-cli] TomWeJack commented on issue #605: mac无论创建新项目还是weex run ios 都报错--Error: Cannot find module 'download-git-repo'

TomWeJack commented on issue #605: mac无论创建新项目还是weex run ios 都报错--Error: Cannot find module 'download-git-repo' URL: https://github.com/apache/incubator-weex-cli/issues/605#issuecomment-559975145 有人遇到过这个问题吗，weex生态比较差，在Q群还有钉钉问了都没人回答，百度也没有相关问题

[GitHub] [incubator-weex-cli] TomWeJack opened a new issue #605: mac无论创建新项目还是weex run ios 都报错--Error: Cannot find module 'download-git-repo'

TomWeJack opened a new issue #605: mac无论创建新项目还是weex run ios 都报错--Error: Cannot find module 'download-git-repo' URL: https://github.com/apache/incubator-weex-cli/issues/605 Error: Cannot find module 'download-git-repo' Require stack: -

[GitHub] [incubator-weex-cli] 18300618319 opened a new issue #604: weex打包andriod包失败

18300618319 opened a new issue #604: weex打包andriod包失败 URL: https://github.com/apache/incubator-weex-cli/issues/604 Makes sure these boxes are checked befor submitting your issue - thank you! - [] If you encounter any problems using the tool, please check if there has a new version

[GitHub] [incubator-weex-cli] hgc2002 opened a new issue #603: iOS pod update fails because repo url is not well defined

hgc2002 opened a new issue #603: iOS pod update fails because repo url is not well defined URL: https://github.com/apache/incubator-weex-cli/issues/603 "npm run ios" fails when cloning the pod repo because the repo url is not well defined. this make it to download the repo every time,

[DISCUSS] Transfer an iOS App to ASF's Apple account ?

Hi, community There is an iOS App called Weex Playground[1] built from the source code of incubator-weex-playground [2]. According to my knowledge, the App was uploaded before Weex donated to ASF under the bundle ID of `com.taobao.weexplayground`. Currently we are trying to solve the problems,

[GitHub] [incubator-weex-cli] YorkShen closed issue #602: Error: Command failed: call gradlew.bat clean assembleDebug

YorkShen closed issue #602: Error: Command failed: call gradlew.bat clean assembleDebug URL: https://github.com/apache/incubator-weex-cli/issues/602 This is an automated message from the Apache Git Service. To respond to

[GitHub] [incubator-weex-cli] YorkShen commented on issue #602: Error: Command failed: call gradlew.bat clean assembleDebug

YorkShen commented on issue #602: Error: Command failed: call gradlew.bat clean assembleDebug URL: https://github.com/apache/incubator-weex-cli/issues/602#issuecomment-559486875 Windows is never supported officially, use it at your own risk. The document is pretty clear.

Re: OSS-Bot Pilot group note

A notification for anyone who concerns about The discussion about OSS-Bot(e.g. WeChat Bot) will be hold at *8:30pm-9:00pm, today *(28th, Nov, 2019, UTC+8). Best Regards, YorkShen 申远 申远 于2019年11月26日周二 上午10:22写道： > According to the information I have, they are going to develop the >

Re: [ANNOUNCEMENT] Weex.io will be offliine in the end of this month

Based on the discussion I had with trademark management, ASF, I don't think the approach you suggested would be accepted by them. But we could use HTTP 301 or DNS CNAME to redirect editor.weex.io to new addres. @Hanks Zhang and I will try not to affect Weex users and satisfy the requirement of

回复: [ANNOUNCEMENT] Weex.io will be offliine in the end of this month

It is recommended that the http://editor.weex.io URL display a notice of abandonment of the address, be discarded after the specified date, and add a link to the new address. 发件人: 申远 发送时间: 2019年11月26日 11:54 收件人: dev ; Dan ; Hanks Zhang 主题: Re: [ANNOUNCEMENT]

[GitHub] [incubator-weex-cli] shylon0719 opened a new issue #602: Error: Command failed: call gradlew.bat clean assembleDebug

shylon0719 opened a new issue #602: Error: Command failed: call gradlew.bat clean assembleDebug URL: https://github.com/apache/incubator-weex-cli/issues/602 系统：win7 win10 在android studio里能跑，用weex run android 报下面错误： $ weex run android * daemon not running; starting now at tcp:5037

Re: [ANNOUNCEMENT] Weex.io will be offliine in the end of this month

Then it seems like we have a solution satisfy the need of ASF Brand Managemet, Weex Users and the maintainer of editor.weex.io @Hanks Zhang . I think this is the best we could do considering the situaion. Best Regards, YorkShen 申远 Hanks Zhang 于2019年11月27日周三 下午3:10写道： > I support using

Re: [ANNOUNCEMENT] Weex.io will be offliine in the end of this month

I support using xxx.dotwe.org instead of editor.weex.io if it really has the branding issue. The candidate domain name could be editor.dotwe.org or v2.dotwe.org. Technological speaking, redirect editor.weex.io to the new domain in DNS is feasible. However, the dotwe.org is not under my control,

Re: [ANNOUNCEMENT] Weex.io will be offliine in the end of this month

>From the information I have, the server of editor.weex.io will be offline by the end of Dec, 2019 if we don't migrate to the new data center. While the domain name could be alive until Nov, 2020 if we don't pay for it. I will not judge the domain name decsion made by ASF brand management, but I

Re: [ANNOUNCEMENT] Weex.io will be offliine in the end of this month

I think the concerns from ASF is mainly on domain part, as the domain weex.io does lead some confusion. Is domain of http://dotwe.org/vue on under your control? Could we create redirect editor.weex.io to .dotwe.org through http 301 redirect or DNS CNAME ? IMNAL, but I think backend-server is

Re: [ANNOUNCEMENT] Weex.io will be offliine in the end of this month

In my opinion, both close weex.io or migrate the server to ASF's VM is not a good idea, the cost is too expensive. For the branding issue of the domain, I think we can register a new domain name to replace the editor.weex.io, and redirect the legacy domain to the new one. Currently, the weex.io

Re: [ANNOUNCEMENT] Weex.io will be offliine in the end of this month

Well, it seems like the brand management,VP doesn't like the idea [1] that we hold the domain name of http://editor.weex.io/, we have to take down the domain name for better or worse. As some of you may not see discussion in private mailing list, I will move it back to this mailing list. Here is

Re: Move Github notification of Weex-UI to comm...@weex.apache.org

A JIRA issue [1] is just created for this purpose. [1] https://issues.apache.org/jira/browse/INFRA-19483 Best Regards, YorkShen 申远 申远 于2019年11月26日周二 上午11:05写道： > Hi, community. > > The emails of Github notification was always sent to > comm...@weex.apache.org. Recently, Weex-UI [1] joined

Move Github notification of Weex-UI to comm...@weex.apache.org

Hi, community. The emails of Github notification was always sent to comm...@weex.apache.org. Recently, Weex-UI [1] joined Apache Weex community and it seems like there is something wrong in the email configuration so that we received lots of Github notification in this current mailing

Re: OSS-Bot Pilot group note

According to the information I have, they are going to develop the OSS-Bot[1] based on WeChaty [2]. So It's an idea implemented partically. From the aspect of Apache Weex, it's not harm to participate it. [1] https://github.com/kaiyuanshe/OSS-Bot [2] https://github.com/wechaty/wechaty Best

[GitHub] [incubator-weex-cli] cnryb commented on issue #600: in @weex/plugins/debug-server run npm i got error

cnryb commented on issue #600: in @weex/plugins/debug-server run npm i got error URL: https://github.com/apache/incubator-weex-cli/issues/600#issuecomment-558424453 I want to understand how weex debugging works. But the corresponding documentation is missing. So, I try to run the

Re: OSS-Bot Pilot group note

The GitHub repo https://github.com/kaiyuanshe/OSS-Bot still has no code. Is this just an unrealized idea? 在 2019/11/25 下午3:57，“申远” 写入: Hi, community. I am forwarding the message to this mailing list as a couple of guys are going to make some change to help Apache Project

[GitHub] [incubator-weex-cli] erha19 commented on issue #600: in @weex/plugins/debug-server run npm i got error

erha19 commented on issue #600: in @weex/plugins/debug-server run npm i got error URL: https://github.com/apache/incubator-weex-cli/issues/600#issuecomment-558421490 @cnryb why are you use this package? it's only use for some case of backend-only like node side.

[GitHub] [incubator-weex-ui] tw93 opened a new pull request #481: moving to apache

tw93 opened a new pull request #481: moving to apache URL: https://github.com/apache/incubator-weex-ui/pull/481 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and

[GitHub] [incubator-weex-ui] tw93 merged pull request #481: moving to apache

tw93 merged pull request #481: moving to apache URL: https://github.com/apache/incubator-weex-ui/pull/481 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use

[GitHub] [incubator-weex-ui] tw93 closed pull request #480: Dev

tw93 closed pull request #480: Dev URL: https://github.com/apache/incubator-weex-ui/pull/480 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above

[GitHub] [incubator-weex-ui] tw93 opened a new pull request #480: Dev

tw93 opened a new pull request #480: Dev URL: https://github.com/apache/incubator-weex-ui/pull/480 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL

Fwd: OSS-Bot Pilot group note

Hi, community. I am forwarding the message to this mailing list as a couple of guys are going to make some change to help Apache Project originating in China by providing features like auto English-Chinese translation, Github message notification to WeChat, etc.. Their proposal is very

Re: [DISCUSS] Apply for outstanding open source project to COSCL, China

Just submitted it before the deadline. Best Regards, YorkShen 申远 任 跃兵 于2019年11月22日周五 下午4:54写道： > Hurry up. > Just worry that you will miss > > 在 2019/11/22 下午3:45，“申远” 写入: > > Hi, all > > COSCL(China Open Source Cloud League) [1] is an organization founded by > Ministry of

Re: [DISCUSS] Apply for outstanding open source project to COSCL, China

Hurry up. Just worry that you will miss 在 2019/11/22 下午3:45，“申远” 写入: Hi, all COSCL(China Open Source Cloud League) [1] is an organization founded by Ministry of Industry and Information Technology, China. Currently, COSCL is calling for outstanding open source project [2].

  1   2   3   4   5   6   7   8   9   10   >