Re: Question about the website of weex

I am totally aware of the situation, but what we met here is that someone published a VSCode extension named weex-plugin/tool/helper. I cannot contact all of the author of such extension to ask them rename their code or invite all of them into Weex repo under Apache. Either of these choices is

Re: New Committer: He Ling

Congratulations He Ling!! Greets, Myrle On Wed, Mar 6, 2019 at 11:46 AM Jan Piotrowski wrote: > Welcome He Ling! > > Am Mi., 6. März 2019 um 03:41 Uhr schrieb 申远 : > > > > The Podling Project Management Committee (PPMC) for Apache Weex has > invited > > He Ling to become a committer and we are

Re: Question about the website of weex

Apache Weex dev team: Using the Weex name to denote something that isn't weex is a problem. Calling a team a "weex team" if they aren't the Apache Weex committers and PMC is confusing to end users. Apache doesn't allow project brands to be diluted like this. Registering a website with the weex

Re: New Committer: He Ling

Welcome He Ling! Am Mi., 6. März 2019 um 03:41 Uhr schrieb 申远 : > > The Podling Project Management Committee (PPMC) for Apache Weex has invited > He Ling to become a committer and we are pleased to announce that he has > accepted. > > He Ling is a great iOS Developer and works with weex project

New Committer: He Ling

The Podling Project Management Committee (PPMC) for Apache Weex has invited He Ling to become a committer and we are pleased to announce that he has accepted. He Ling is a great iOS Developer and works with weex project for a while. He focuses on improving the stability, utility of Weex and the

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

Already done. https://github.com/apache/incubator-weex/projects/1?add_cards_query=is%3Aopen Best Regards, YorkShen 申远 Jan Piotrowski 于2019年3月5日周二 下午7:22写道： > Great that we are on the same page here. > > Could someone from the PMC please request a project board on Github > being created at

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

Great that we are on the same page here. Could someone from the PMC please request a project board on Github being created at https://github.com/apache/incubator-weex/projects so I can create a space to track all these TODO items regarding incubation, compliance etc? We don't want to miss

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

> Technically speaking, I or other Weex PPMC are not the owner of weex.io, I can not ask EMAS team uses another domain as weex.io is not under my or other PPMC's control. Yes, this domain name is currently managed in my hands. On the construction of this website, the EMAS team gave us a lot of

Re: Question about the website of weex

Of course there can still be a "VS Code extension" entry under (e.g.) "Third party tools". And the extension actually has a perfectly fine website, so no need to rehost the documentation and images etc: Both https://marketplace.visualstudio.com/items?itemName=weex.vscode-weex and

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

Technically speaking, I or other Weex PPMC are not the owner of weex.io, I can not ask EMAS team uses another domain as weex.io is not under my or other PPMC's control. Actually, I think Dan may have the admin privilege of weex.io. What do you think, Dan? Best Regards, YorkShen 申远 Jan

Re: Question about the website of weex

Agreed. We should set the boundary clearly about what is Apache Weex and what is not and mention that on the webpage. But given current situation, it is hard to move them to a seperate domain totally. For example, vscode extension are just

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

Actually, I think https://cn.aliyun.com/solution/emas?spm=a2c7j.-zh-community-biz-emas.0.0.5daac8eecHbyWI already is an external website for EMAS - so this can probably just be listed under "Tools using Apache Weex" on the new Apache Weex website. Am Fr., 1. März 2019 um 11:17 Uhr schrieb Jan

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

I understood that, and that is exactly why EMAS can not be under one of the official domains being used for Apache Weex. As weex.io is a plain redirect, it will be considered as "part of Apache Weex" by the users. If EMAS uses the same domain, users will make the same assumption here - which is

Re: Question about the website of weex

Ok, then it's pretty simple: Those tools should have their own website on another domain (one that does not redirect to the .apache.org site by default - maybe subdomains for weex-community.io or something if someone wants to sponsor that?) and the official weex page just links out to them,

Re: Question about the website of weex

> > Sorry, did I miss part of the thread here? What "development tools and > others" are you talking about? Under the right side of the page [1], there is a list for weex tool. Except for Playground App, others are developed by third party developers. As such tools are useful and we cannot move

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

Technically speaking, EMAS is an enterprise mobile develop solution based on weex, and I think the target users of EMAS are Chinese. Actually, there is an entry[1] for EMAS in Chinese document. Besides that, there is no difference between http://weex.apache.org and http://emas.weex.io/ . And Weex

Re: Question about the website of weex

> Such tools are useful and attractive for users of Weex, and we need a place to list such tools in Weex eco system, ... Sorry, did I miss part of the thread here? What "development tools and others" are you talking about? > As weex users are Android/iOS/JavaScript developers, they often choose

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

I don't understand. A "commercial eco system for weex" should not just mirror the complete site, even (and especially!) if they add their own things. Right now I have no idea what this really is when I go there, so this should definitely be cleaned up. -J Am Do., 28. Feb. 2019 um 04:24 Uhr

Re: Question about the website of weex

When you send the announcement of the code release, you need to list the released artifacts just like this[1]. Here is dubbo release guidelines that you can take a look. [1]http://servicecomb.apache.org/release/ [2] http://dubbo.apache.org/en-us/blog/prepare-an-apache-release.html Willem Jiang

Re: Question about the website of weex

> > But we can only host the downloads of the weex project, not the other > tools which are built on top it. Such tools are useful and attractive for users of Weex, and we need a place to list such tools in Weex eco system, which is important from our users' point. If there is a better place

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

EMAS is a commercial eco-system for weex, so this url[1] should not be redirected to https:/weex.apache.org I have talked to guys of EMAS, they are using the source code of incubator-weex-site [2] and some third-party content to build the website, while weex only use incubator-weex-site [2] [1]

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

Nice! Just found http://emas.weex.io/ which is not redirecting yet. J Am Mi., 27. Feb. 2019 um 07:00 Uhr schrieb 申远 : > > http://weex-project.io is also redirected to http://weex.apache.org > > Except for the following issue, I think we have done the relaunch procedure > of website: > > >-

[jira] [Created] (WEEX-678) createInstance failed using webpack UglifyJsPlugin after upgrade weex from 0.18.3 to the latest one

mjsornp created WEEX-678: Summary: createInstance failed using webpack UglifyJsPlugin after upgrade weex from 0.18.3 to the latest one Key: WEEX-678 URL: https://issues.apache.org/jira/browse/WEEX-678

Re: [DISCUSS] Can we improve the playground app project?

> > 1. Default to use the public version but no local compile package, like > `com.taobao.android:weex_sdk:0.20.3.0-beta`, that can be work on anywhere. As local compiling is a feature, not a bug, and updating the default version is painful as well. Maybe you should write version info in a

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

http://weex-project.io is also redirected to http://weex.apache.org Except for the following issue, I think we have done the relaunch procedure of website: - Google Search Console Account - Redirect http://weex.apache.org to https://weex.apache.org Best Regards, YorkShen 申远 Dan

Re: [DISCUSS] Can we improve the playground app project?

There are three necessary features that need to be adapted: 1. Default to use the public version but no local compile package, like `com.taobao.android:weex_sdk:0.20.3.0-beta`, that can be work on anywhere. 2. Adding XML parser to parse `app/src/main/res/xml/app_config.xml` which Weex Cli rely on

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

> The server should just be a Apache webserver (of course!) that can accept .htaccess files to redirect non-http requests. Super complicated example from Cordova: https://github.com/apache/cordova-docs/blob/3c41a7d14192eb26c883c65fc63be303f811474e/www/.htaccess#L118-L130 There should be much

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

The check has passed now. Best Regards, YorkShen 申远 Willem Jiang 于2019年2月22日周五 下午8:08写道： > FYI, there is a tool[1] to check if the website is following the Apache > rules. > Please take a look and fix them ASAP. The website issues need to be > addressed before graducation. > >

Re: [DISCUSS] Can we improve the playground app project?

I'd like to help you do the merge/rewrite of Android. Could you please list the feature you need? It seems like this two repos is different in many ways, maybe cherry-pick is a better idea. Best Regards, YorkShen 申远 Dan 于2019年2月26日周二 下午10:22写道： > Hi, all > > Recently I tried to upgrade the

[DISCUSS] Can we improve the playground app project?

Hi, all Recently I tried to upgrade the weexSDK version of android weex playground app that I rely on in the Weex Cli, user can use `weex platform add android` to add this project into the workspace. Here's the template project which the Weex Cli rely on: [0] [Android Template](

Re: Question about the website of weex

At present, I have added a file to redirect the old documents to the new documents. These are the links of the first 20 pages about weex that I have searched through Google search and Baidu search. If there are other pages that cannot find the corresponding content, we can redirect user access by

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

Thanks for fixing the 404s and making the homepage editable. > we can not control the Apache server to force redirect all non-https requests to the https version, so, now we can just replace manually, I will check it through automated means. The server should just be a Apache webserver (of

Re: Question about the website of weex

Hm, what kind of code is the user missing at that link? (Google Translate unfortunately didn't help) If there was something on the old site that can now not be par of it any more, it should at least be moved somewhere else (subdomain of weex.io for example?) and the old URL redirected. Being

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

> > I am fine with editing any .yml or .json files that include the > content, but the headline "Cross Platforms" has to come from somewhere > in this repo, right? > The homepage is generated by https://github.com/apache/incubator-weex-site/blob/draft/docs/.vuepress/data/lang-en.js on draft

Re: Question about the website of weex

1. https://weex.io has been redirected to https://weex.apache.org 2. All the commercial should also be removed now. If there is still something inappropriate, please let me know, thanks. Best Regards, YorkShen 申远 申远 于2019年2月26日周二 上午11:54写道： > I will redirect weex.io, weex-project.io and all

Re: [DISCUSS] Language used in Mail/Github/etc..

After considering the current situation and the international goal of Weex, I'd like to answer Chinese question both in English and Chinese with the following template. I will give responses with the following template for one month or more, after that maybe we will have a better idea of the

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

Hi, Jan > I am fine with editing any .yml or .json files that include the content, but the headline "Cross Platforms" has to come from somewhere in this repo, right? I have created a pull request to support edit homepage date, see [docs] support edit homepage data

Re: Question about the website of weex

I will redirect weex.io, weex-project.io and all other domain to weex.apache.org ASAP. Meanwhile, if there is any inappropriate content under apache domain[1], please let me know. So far, the following content is inappropriate: - https://weex.apache.org/zh/community/biz-emas.html [1]

Re: Question about the website of weex

sure, that will be remove soon, that’s my mistake, > 在 2019年2月26日，上午11:33，Willem Jiang 写道： > > It's not only about the domain name, but also about the content[1]. > That's the key issue, if we cannot drop clear line between the apache > project and commercial product, the user could be

Re: Question about the website of weex

It's not only about the domain name, but also about the content[1]. That's the key issue, if we cannot drop clear line between the apache project and commercial product, the user could be confused. [1]http://weex.apache.org/zh/community/biz-emas.html Willem Jiang Twitter: willemjiang Weibo:

Re: Question about the website of weex

The weex.io doesn't use to redirect the weex.apache.org now, we have discussed on the mail list about use weex.io as the short domain of weex apache website, if it's ok, I will redirect all the weex.io page to the weex.apache.org. Thanks, Dan Willem Jiang 于2019年2月26日周二 上午10:51写道： > There is

Question about the website of weex

There is angry user github issue[1] about he wants his use case code back. So I get a close look of the weex.io website, it looks there are some Alibaba's content[2] in the site. As weex is donated to ASF, and ASF in vendor neutral organization. We cannot mix the commercial content with Apache

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

I am fine with editing any .yml or .json files that include the content, but the headline "Cross Platforms" has to come from somewhere in this repo, right? One thing I would advise is that you make all non-https requests redirect to the https version as soon as possible. Old links that are

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

Hi, Jan We deployed an automated server build system for building the content of weex.apache.org, the homepage is not a pure HTML file that can be easily edited. If you have any advice about this page, please let me know, I will improve it later. Maybe some of the content can be built from a

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

Yeah, the homepage is unfortunately missing that button ;) As the content is still in the `draft` branch, I also can't just search for a sub string of the headlines to fine the page that represents the homepage - could you please point me to the correct file? -J Am Mo., 25. Feb. 2019 um 10:59

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

There are two options. 1. On the bottom of each page, there is a button called *Edit this page.* Just click it, then you will be navigated to the right branch and file on the github. 2. If you prefer do things manually, Go to draft branch of

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

Nice. Which is the repository and branch to send PRs with typo fixes etc to? Am Mo., 25. Feb. 2019 um 10:18 Uhr schrieb 申远 : > > Hi, there > > I had fix the 404 error and updated the website of weex.apache.org, which > content should be the same as weex.io now. I will configure a 302 >

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

Hi, there I had fix the 404 error and updated the website of weex.apache.org, which content should be the same as weex.io now. I will configure a 302 redirection later, which will make all the mirror site redirects to weex.apache.org. Best Regards, YorkShen 申远 申远 于2019年2月22日周五 下午8:46写道： >

Re: Update weex descriptions on Apache site

I got the updated site, too. It seems that we have to wait one days before it updates. Thanks Best Regards, YorkShen 申远 Willem Jiang 于2019年2月23日周六 上午9:36写道： > I got the updated site, @YorkShen maybe you need to refresh your browser > for it. > > Willem Jiang > > Twitter: willemjiang >

Re: Update weex descriptions on Apache site

I got the updated site, @YorkShen maybe you need to refresh your browser for it. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Feb 22, 2019 at 9:35 PM Jan Piotrowski wrote: > http://incubator.apache.org/projects/weex.html schows the correct mentors > now I think: > > [image:

Re: [DISCUSS] Language used in Mail/Github/etc..

After further thinking about it I think I agree with Myrle: If you can answer a Chinese issue in Chinese, just do so. If you want, you can translate both question and answer to English manually or automatically as well. I don't read any Chinese, so I would definitely have to translate to English

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

As there is a wired 404 problem under Apache domain, which works fine under weex.io domain, I have to revert all the changes on weex.apache.org . I will publish it again when I find out what is happening here. Meanwhile, one may take https://weex.io as the preview version of new weex website

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

FYI, there is a tool[1] to check if the website is following the Apache rules. Please take a look and fix them ASAP. The website issues need to be addressed before graducation. [1]https://whimsy.apache.org/pods.cgi/project/weex Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Feb

Re: [DISCUSS] Language used in Mail/Github/etc..

It may relate to audience which we are target. If the target audience doesn't speak English it could be challenge for him to get the answer in English. It's natural to fill strange if you just see a bunch of Chinese sitting together using their unfluent English talk to each other. But as you may

Re: [recycle-list] Raise two issues for recycle list

OK, I will report on GitHub Regards Fred > On Feb 22, 2019, at 4:20 PM, 申远 wrote: > > Could you please give us a Github issue? We will look into that. > > Normally, we prefer talk bugs in Github, which is a more suitable place for > sharing code detail. > > Thanks > > Best Regards, >

Re: [recycle-list] Raise two issues for recycle list

Could you please give us a Github issue? We will look into that. Normally, we prefer talk bugs in Github, which is a more suitable place for sharing code detail. Thanks Best Regards, YorkShen 申远 476443...@qq.com <476443...@qq.com> 于2019年2月22日周五 下午4:11写道： > I’d like to raise two issues about

Re: [FEATURE] Add a new component to support Html tags(can custom tag's implement)

Thanks, I will just paste the content description of the *Bruce too* here. I'd really appreciate if someone could give some option or do a review. It's the same as the original PR https://github.com/apache/incubator-weex/pull/2071 *Add a new component to support Html tags which named

[recycle-list] Raise two issues for recycle list

I’d like to raise two issues about recycle-list component, please double check, thanks. The first one is the behavior is not consistent on android and iOS platform. I have write a demo, following is the the main code, you can also check it at

Re: [DISCUSS] Language used in Mail/Github/etc..

> > I saw some people using Google Translate to translate the question, > then repost the question in English before answering. That makes it > clear(er), that English is the preferred language and also allows > people like me to participate. I used to paste the result of Google Translate from

Re: Update weex descriptions on Apache site

Sadly, the website [1] is still outdated. For example the mentors information in weex.xml[2] are up to date, which should only include Willem Jiang and Myrle Krantz, but the web site still lists the original mentors. BTW, is https://svn.apache.org/repos/asf/incubator/public/trunk/build.sh the

Re: Update weex descriptions on Apache site

Hi, I just checked the website, the changes are updated. I'm not sure if the build is triggered by hand. BTW, you can run the build.sh from the project to verify if the xml document changes are OK. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Feb 22, 2019 at 11:28 AM 申远 wrote:

Re: Update weex descriptions on Apache site

Wired things happened. The source file[1] is already updated, but the website[2] isn't. Do I need trigger a build for the website? BTW: How do we start vote for changes on SVN? There is no such thing called push or PR on SVN. After I had entered "svn commit", it just pushed to the server

Re: [DISCUSS] Language used in Mail/Github/etc..

This is just my personal opinion, but: I'd talk about development in English, but answer users in Chinese if they ask their question in Chinese. I know that makes for some awkward transitions since the shift between explaining something to a user, and recognizing an area where improvement is

Re: [FEATURE] Add a new component to support Html tags(can custom tag's implement)

There also seems to be a related documentation PR at https://github.com/apache/incubator-weex-site/pull/308 -J Am Do., 21. Feb. 2019 um 09:41 Uhr schrieb 申远 : > > It would be better if you could share your feature with more detail here, > like document so that everyone can understand what is

Re: Update weex descriptions on Apache site

Ha, good that you got some practice in then - you will probably also need SVN to publish the releases to be voted on ;) (Using TortoiseSVN for me was a really nostalgic moment. So many years working with that software - all forgotten now) -J Am Do., 21. Feb. 2019 um 07:31 Uhr schrieb 申远 : > I

Re: [DISCUSS] Language used in Mail/Github/etc..

Difficult situation. Apache projects definitely use English as the default language, but with an existing userbase that is used to create issue in Chinese, this would be negative to enforce. I saw some people using Google Translate to translate the question, then repost the question in English

Re: [FEATURE] Add a new component to support Html tags(can custom tag's implement)

It would be better if you could share your feature with more detail here, like document so that everyone can understand what is happening here. Thanks Best Regards, YorkShen 申远 Bruce too 于2019年2月21日周四 下午3:08写道： > We can check this PR >

[FEATURE] Add a new component to support Html tags(can custom tag's implement)

We can check this PR

Re: Update weex descriptions on Apache site

I have updated the website of http://incubator.apache.org/projects/weex.html according to monthly incubator PMC report from Jan, 2017 to now. It may take a while before the website updated. BTW: This is the first time I used svn after I had got graduated from college, which reminds me of school

[DISCUSS] Language used in Mail/Github/etc..

As we all know, there are many users of Weex are Chinese. As a result, there are many user expresses their opinion using Chinese in Github . What should we do under this situation? 1. Answering their question with English, which is wired as

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

Good question comment you posted on the INFRA post. I hope they will agree, that there is no problem at all as long as the official website is at weex.apache.org. -J Am Mi., 20. Feb. 2019 um 09:48 Uhr schrieb 申远 : > > > > > But until this happens I think an absolutely practical solution would >

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

> > But until this happens I think an absolutely practical solution would > be to use a second host in China with a separate domain that can > provide better speeds to Chinese users. It just has to show the exact > same content as the official site (and be hidden from search engines > via

Re: Weex, Apache and outside code

>From my perspective, I'd like the idea of *geting the weex-toolkit donated and making the contributors Weex committers.* 1. If the corresponding code is owned by Alibaba, and someone represented the company would sign the SGA, is there any necessary to have all the contributors signed the SGA

Re: Ios运行异常

As this is an English mailing list, I will just Google translate your mail: Title: Ios is running abnormally > Content: Assertion failed: ([scheme isEqualToString:@"ws"] || [scheme > isEqualToString:@"http"] || [scheme isEqualToString:@"wss"] || [scheme > isEqualToString:@"https"]) > Problem as

??????Ios????????

?? iPhone -- -- ??: : 2019??2??20?? 14:29 ??: dev : ??Ios Assertion failed: ([scheme isEqualToString:@"ws"] || [scheme isEqualToString:@"http"] || [scheme isEqualToString:@"wss"] ||

Ios运行异常

Assertion failed: ([scheme isEqualToString:@"ws"] || [scheme isEqualToString:@"http"] || [scheme isEqualToString:@"wss"] || [scheme isEqualToString:@"https”]) 问题如上 期待回复！

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

Uh, the _domain name_ is not actually at all related to the speed of the site - the _hosting_ is. My results for those two domains from Germany, Berlin for example: C:\Users\Jan>ping weex.io Pinging weex.io [47.75.160.176] with 32 bytes of data: Reply from 47.75.160.176: bytes=32 time=327ms

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

Sorry，I just came across this email. I found you already sent the mail to the general mailing, I will reply the mail there. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Feb 15, 2019 at 2:39 PM Dan wrote: > > Hi, Myrle/Willem, > > Currently, we have a domain name of weex.io and

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

I've created an INFRA ticket: https://issues.apache.org/jira/browse/INFRA-17872 I won't promise that INFRA can solve this, but hopefully they'll at least look at it. Feel free to add any details you have. Best Regards, Myrle On Tue, Feb 19, 2019 at 7:18 AM Dan wrote: > Thanks, Jan, I will

Re: Weex, Apache and outside code

More information, here are the steps that will have to be completed for the IP clearance: http://incubator.apache.org/ip-clearance/ip-clearance-template.html I think finding out who currently *owns* the code is a good first step. My suspicion is that most of it is work-for-hire performed for

Re: Weex, Apache and outside code

Hi YorkShen, You may not need to contact all of the contributors. Some of the contributions may not pass the threshold of originality which is commonly applied in copyright law. For example: https://github.com/weexteam/weex-toolkit/commits?author=RiverCheng0825 This contributor only provided

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

Thanks, Jan, I will take a look at this. Jan Piotrowski 于2019年2月18日周一 下午6:15写道： > Cordova uses the npm package `insight` for telemetry, you can see more > in these two files: > https://github.com/apache/cordova-cli/blob/master/src/telemetry.js >

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

Cordova uses the npm package `insight` for telemetry, you can see more in these two files: https://github.com/apache/cordova-cli/blob/master/src/telemetry.js https://github.com/apache/cordova-cli/blob/master/src/cli.js The data being tracked is very limited, and all done only after explicit opt-in

Re: Weex, Apache and outside code

It took me some time to read things about IP Clearance , and I think https://github.com/weexteam/weex-toolkit is the only repo we should move. The following problems may prevent us from moving weex-toolkit to apache 1. According to

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

Hi Jan, Thanks for getting back to me. Your opinion has helped us a lot. We will migrate the deployment of the document to weex.apache.org in these two days. BTW, do you know the detail about how to do the user-track bellow the apache way, I know the Cordova has telemetry.cordova.io to record

Re: [DISCUSS] Rules for Weex Community

It seems like there is no objection, I will just merge the PR about the community document. Best Regards, YorkShen 申远 申远 于2019年2月15日周五 上午1:26写道： > Hi, there > > I rewrite some documents about Weex community in the listed aspect: > >

Re: [DISCUSS] can we use weex.io as the short domain name for the apache project

Besides what the rules say (which I don't really know): An apache.org domain has an incredible effect on credibility and trust. Apache is a really strong brand with developers, and especially new projects like Weex can benefit from that. (The project will be called "Apache Weex" anyway) Apache

[DISCUSS] can we use weex.io as the short domain name for the apache project

Hi, Myrle/Willem, Currently, we have a domain name of weex.io and want to use it to replace the previous weex-project.io domain name for the following reasons: 1. The domain name is shorter and easier to remember. 2. Apache's website has slower access to the developer in China, so there is a

Re: Weex, Apache and outside code

> > 1. What repositories should be imported? (=> List of repositories) https://github.com/weexteam/weex-toolkit 2. Who contributed to theses repositories? Who are active and relevant > contributors? (Individuals and companies) (=> List of names) > 25 individuals, maybe two or three are active,

Re: Fwd: PMCs: share your Project's experience with The Apache Way

I am glad to write such blogs for weex project. As I am not an English native speakers, I am a little concerned of my English writing skills when facing writing such an article. Best Regards, YorkShen 申远 Sally Khudairi 于2019年2月14日周四 下午5:02写道： > Thank you, Myrle; hello Apache Weex podling! >

Re: Fwd: PMCs: share your Project's experience with The Apache Way

Thank you YorkShen. I'll be happy to help you with any editing that might be needed. Most importantly is sharing your perspective and your experience :-) Kind regards, Sally - - - Vice President Marketing & Publicity Vice President Sponsor Relations The Apache Software Foundation Tel +1 617 921

[DISCUSS] Rules for Weex Community

Hi, there I rewrite some documents about Weex community in the listed aspect: 1. Bug report 2. Join Weex Community 3. Contribute Code This change includes both Chinese and English version, one can review the detail on corresponding Github PR

Re: Weex, Apache and outside code

I read through the links you provided Willem, and extracted the following questions that have to be answered: 1. What repositories should be imported? (=> List of repositories) 2. Who contributed to theses repositories? Who are active and relevant contributors? (Individuals and companies) (=>

Re: Fwd: PMCs: share your Project's experience with The Apache Way

Thank you, Myrle; hello Apache Weex podling! Feel free to contact me directly with any questions. Warmest regards, Sally - - - Vice President Marketing & Publicity Vice President Sponsor Relations The Apache Software Foundation Tel +1 617 921 8656 | s...@apache.org On Thu, Feb 14, 2019, at

Fwd: PMCs: share your Project's experience with The Apache Way

Hi all, Hello Weex, This invitation is for the Weex PMC as well. Would anyone here like to write a blog? In addition to being good publicity for Apache, it's also good publicity for your project. Best Regards, Myrle - Original message - From: Sally Khudairi To: "ASF Marketing &

Re: Weex, Apache and outside code

We need to do the IP Clearance[1] first. To be honest, it's my first time to go through this process. We could take the others project path[2] as an example. [1]https://incubator.apache.org/guides/ip_clearance.html [2]http://incubator.apache.org/ip-clearance/ Willem Jiang Twitter: willemjiang

Re: Weex, Apache and outside code

Hi YorkShen, If you’re ready, I’ll file a Jira ticket with INFRA. Or would you like to do it? Best Regards, Myrle On Thu, Feb 14, 2019 at 3:48 AM 申远 wrote: > According to dependency in package.json > , I > don't think there is

Re: android 9 上 weex image组件图片显示不清晰问题

Weex community encourage using English when discussion to let developers around the world to know what is happening here. If you could use English next time, it would be great for the community The message above translated to English by Google and me together is shown below: Recently, all the

android 9 ?? weex image??????????????????????

??android 9??weex?? ??weex?? resize=cover, ??centerCrop

Re: Weex, Apache and outside code

According to dependency in package.json , I don't think there is a IP issue. Maybe Dan could do a double check. BTW, what's the standard procedure if we want to move a repo to Apache project ? Best Regards, YorkShen 申远 Willem

<    2   3   4   5   6   7   8   9   10   11   >