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 service endpoint to do the same redirect. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Sat, Dec 21, 2019 at 11:54 PM 任 跃兵 wrote: > > 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: [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 use > > editor.weex.apache.org in our document, discussion and any other secnario > > we coud have. > > > > With approach above, the existing Weex user could still use editor.weex.io > > without interruption. And for ASF's concern, only one DNS change records is > > needed. > > > > If this is not enough for protecting ASF's trademark, maybe we could > > convince our committer to donate the domain name to ASF and let ASF paid > > for it. But that's another story, and I'd like to implement the approach I > > mentioned above first if there is no objection. > > > > [1] "Disclaimer | 免责声明Apache Weex, Weex and Apache are either registered > > trademarks or trademarks of the Apache Software Foundation in the United > > States and/or other countries, and are used with permission as of 2014. The > > Apache Software Foundation has no affiliation with and does not endorse or > > review the materials provided at this website, which is managed by Alibaba." > > > > I am forwarding the conclusion we have in private mailing list to this > mailing list for your information. > > Best Regards, > YorkShen > > 申远 > > > 申远 于2019年12月5日周四 下午5:24写道： > > > 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 by HTTP 301. > > > > Best Regards, > > YorkShen > > > > 申远 > > > > > > Jan Piotrowski 于2019年12月5日周四 上午2:54写道： > > > >> 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 07:55 Uhr schrieb 申远 : > >> > >> > 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 name also violate the legal right of ASF.* > >> > > >> > Best Regards, > >> > YorkShen > >> > > >> > 申远 > >> > > >> > > >> > Jan Piotrowski 于2019年12月4日周三 上午4:29写道： > >> > > >> > > 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 > >> > > external subdomain. > >> > > > >> > > I am happy to sponsor the cost for weex.io for the first year to > >> whoever > >> > > takes over the domain: https://www.domcomp.com/tld/io > >> > >
Re: [ANNOUNCEMENT] Weex.io will be offliine in the end of this month
It's better to redirect to apache website instead of shutdown the weex.io. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Nov 5, 2019 at 10:08 PM 申远 wrote: > > Thanks > > According to the message from incubator [1], weex.io could still exists if > they meet some requirements. > > We could convince the owner of weex.io to do some change, or we could > rewrite links on our website. What do you think? > > [1] > https://mail-archives.apache.org/mod_mbox/incubator-general/201911.mbox/%3cCAEWfVJ=jns8oq6_ftg33eqzobqhf5mhjsuadbseee94uzop...@mail.gmail.com%3e > > Best Regards, > YorkShen > > 申远 > > > 任 跃兵 于2019年11月5日周二 下午8:03写道： > > > The links in page [1] will be unable to open. > > Please pay attention to these demos and links to this domain in the > > website [2]. > > > > [1] https://weex.apache.org/community/code-demos.html > > [2] https://weex.apache.org< > > https://weex.apache.org/community/code-demos.html> > > > > > > 发件人: 申远 > > 发送时间: 2019年11月5日 10:55 > > 收件人: dev > > 主题: [ANNOUNCEMENT] Weex.io will be offliine in the end of this month > > > > Hi, communtiy > > > > The website of weex used to host on a thirt party domain [1], and we > > configured a 302 redirect to our official website [2] years ago. > > > > We will not pay for the old domain server [1] in this month, which means > > you will not be able to visit the old domain [1]. Please always visit Weex > > through the new domain [2]. > > > > [1] https://weex.io > > [2] https://weex.apache.org > > > > Best Regards, > > YorkShen > > > > 申远 > >
Re: [DISCUSS] Delete unused repo of Weex
You may consider to put the repo into read only mode for a while instead of delete it. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Mon, Oct 28, 2019 at 11:26 AM 申远 wrote: > > 72 hours passed and no -1, I will take this as a lazy consensus and create > a JIRA issue [1] to INFRA. > > [1] https://jira.apache.org/jira/browse/INFRA-19346 > > Best Regards, > YorkShen > > 申远 > > > 申远 于2019年10月25日周五 下午3:14写道： > > > Hi, community > > > > There is an unused repo [1] of Apache Weex. I once created it for > > backwards-compability purpose as we're switching package name from > > `com.taobao.weex` to `org.apache.weex`, but now we have a better solution, > > there is no need to remain it. > > > > I will create a JIRA issue to INFRA to delete it if there is no objections. > > > > [1] https://github.com/apache/incubator-weex-android-compatible > > [2] https://weex.apache.org/download/major_change.html#package-name > > > > Best Regards, > > YorkShen > > > > 申远 > >
Re: Apache project meetup in ShangHai Sep 21st
The time is around 1:30 PM to 4:00 PM, now it's about 20 people will join us. We are just trying to find some place to hold this event. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Sep 17, 2019 at 6:14 AM Liu Ted wrote: > > Hi Willem, What's the current status if the captioned meeting in Shanghai on > Seot. 21st? Has the venue and time been decided yet? > > Best regards, > > Ted Liu, > ASF Member, Sponsor Ambassador, Incubator PMC Member > > > 2019 年 8 月 21 日周三 10:55，Willem Jiang 写道： Hi, > > We would like to hold a meetup in ShangHai Sep 21st by inviting some > Apache members ( Craig Russell, Justin Mclean, Willem Jiang）and some > apache projects committers in China like we did last year. > > We hold this meetup can help Apache projects to know each other in > China. As there are lot of Apache project committers are based in east > China, we can leverage this opportunity to let Apache know better > about the committers in China and give us some advice to build up > health community. > > The discussion topic of meetup could be: > How to be the TLP of ASF? > How can we help ASF know better about China? > How can we help more Chinese know better about ASF? > > If you are interested about this meetup, please drop an email to > ningjiang AT apache.org with the information of your name, phone > number and the project name before Sep 18th 12 PM. We will send you > detail information of the meetup later. > > Please forward the mail to your friend who may be interested about this event. > > Willem > > - > To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org > For additional commands, e-mail: dev-h...@echarts.apache.org >
Apache project meetup in ShangHai Sep 21st
Hi, We would like to hold a meetup in ShangHai Sep 21st by inviting some Apache members ( Craig Russell, Justin Mclean, Willem Jiang）and some apache projects committers in China like we did last year. We hold this meetup can help Apache projects to know each other in China. As there are lot of Apache project committers are based in east China, we can leverage this opportunity to let Apache know better about the committers in China and give us some advice to build up health community. The discussion topic of meetup could be: How to be the TLP of ASF? How can we help ASF know better about China? How can we help more Chinese know better about ASF? If you are interested about this meetup, please drop an email to ningjiang AT apache.org with the information of your name, phone number and the project name before Sep 18th 12 PM. We will send you detail information of the meetup later. Please forward the mail to your friend who may be interested about this event. Willem
Re: Weex Trademark(CopyRight) issue
>From my understanding, if the work is done during the work time, the IP is belonged to the company. If the developer is listed in the CLA, it should be fine. If not, you may still need to get a SGA from the company. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Sat, Jun 8, 2019 at 9:32 AM York Shen wrote: > > I agreed with that. Users should and could create a Weex App only using tools > under Apache Weex. If this is not possible, we should consider donating > corresponding tools to ASF. > > While, one of the reason that stops us from donating tools to ASF is the IP > of the tools is unclear. At least I know some of the tools are developed at > work time with company’s laptop. Under this case, I am not sure the IP > belongs to individual or company. > > > 在 2019年6月6日，22:05，Jan Piotrowski 写道： > > > > That sounds like a good plan YorkShen. > > > > For me, with a user hat on, > > https://weex.apache.org/guide/develop/create-a-new-app.html is > > definitely the first place I will go to test Weex. So I will be told > > to use `weex-toolkit`. The preview rendered by `npm start` will tell > > me to use https://weex.apache.org/tools/playground.html. > > > > So for the toolkit we definitely need a solution, as this will > > effectively be understood as "being" Weex by users (When people talk > > about Apache Cordova, they often actually mean the CLI `cordova` - for > > `weex` this comes from the toolkit). > > The playground app needs to come from Apache Weex as well, and be > > released as a normal Apache Weex project - but we already talked about > > that elsewhere and this is in progress if I understood correctly. (It > > then of course should also not be listed under "Third Party Tools" on > > the website any more). > > > > A bit confusing might be https://weex.apache.org/tools/dotwe.html > > which is linked as "Online Playground", which indicates to belong to > > the Playground app, but is actually a third party thing hosted on > > editor.weex.io (which of course it not ok as domain). What you get > > clicking the link also actually looks different than the preview > > screenshot, which looks a lot more like http://dotwe.org/vue/ - which > > itself is not linked at all in "Third Party Tools". > > > > If I as a user can follow the "Create a new app" instructions without > > needing to use third party tools or encountering confusing links and > > discrepancies, a good part of the problems might be solved already. > > > > -J > > > > PS: Small bug report: https://weex.apache.org/tools/ide.html shows > > Chinese disclaimer. > > > > Am Do., 6. Juni 2019 um 12:08 Uhr schrieb 申远 : > >> > >> Hi, community > >> > >> I spent some time this week to figure out what are essential parts to run > >> Apache Weex and what are not. Those essential part should go into Apahce > >> Weex's umbrella, while others could change their name to avoid violation of > >> ASF's trademark and copyright. What's more, the document itself should be > >> clear enough about what exactly users download or install when they use > >> Weex and where it come from. Here are progresses and issues still need > >> solved. > >> > >> Documentation > >> The following issues are solved, all of the are marked as Un-Apache or > >> deleted: > >> > >> - https://weex.apache.org/tools/ide.html > >> - https://weex.apache.org/tools/extension.html > >> - https://weex.apache.org/tools/toolkit.html > >> - https://weex.apache.org/404.html > >> - https://github.com/weex-plugins > >> - https://github.com/weexteam/ (Some of the repos may still have > >> problems, see later discussion about Github Repo) > >> > >> BTW: After some negotiation, I am a administor of the last two Github team. > >> And I will guide those repos to make sure all of them are not violation of > >> ASF's policies. > >> > >> The following issues doesn't need solved, as they are clear about whether > >> they are part of Apache or not. > >> > >> - https://weex.apache.org/tools/playground.html > >> - https://github.com/weexext > >> - https://github.com/weex-cli > >> > >> Currently, there are two essential tools listed in the documents and none > >> of them are under ASF: > >> > >> - weex-toolkit [1] > >> - vue-loader [2] > >> > >> Weex-toolkit is a collection of useful tools, maybe we cou
Re: [DISCUSS] Do we need to list all third part files and their license one by one?
If there is no other Licensed code there, it makes sense we just specify the directory for the License disclaimation. Now I just have a quick question for the WebKit, can we just use compiled binary file if we don't change change the code of WebKit? Regards, Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Jun 4, 2019 at 4:27 PM 申远 wrote: > > Hi, community. > > Recently, I am checking third party files in Weex and adding their license > to our LICENSE file. What happens here is that Weex copied around 1500 > header files(.h file) from Webkit [1] and it is obviously that some of > these Webkit files are missed in our LICENSE[2] file. > > >- I can add all these files and there license to Weex LICENSE file, but >a Weex LICENSE file listed over 1500 third-party files may be too long to >read for our developers. Is it OK if I just list the directories containing >the third-part file, not the files itself? >- License for those third-part files are similar to each other, with >little difference. For example, the following two files are different only >in year. Should I take these two license as the same and only list one in >Weex LICENSE file? Otherwise, there would be tens or hundreds of third >party license header in Weex LICENSE file, which will make it hard to read >for our developers. > - /* >* Copyright (C) 2006 Apple Inc. All rights reserved. >* >* Redistribution and use in source and binary forms, with or without >* modification, are permitted provided that the following conditions >* are met: >* 1. Redistributions of source code must retain the above copyright >*notice, this list of conditions and the following disclaimer. >* 2. Redistributions in binary form must reproduce the above > copyright >*notice, this list of conditions and the following disclaimer in > the >*documentation and/or other materials provided with the > distribution. > - /* >* Copyright (C) 2013, 2016 Apple Inc. All rights reserved. >* >* Redistribution and use in source and binary forms, with or without >* modification, are permitted provided that the following conditions >* are met: >* 1. Redistributions of source code must retain the above copyright >*notice, this list of conditions and the following disclaimer. >* 2. Redistributions in binary form must reproduce the above > copyright >*notice, this list of conditions and the following disclaimer in > the >*documentation and/or other materials provided with the > distribution. > > > > > [1] > https://svn.webkit.org/repository/webkit/releases/WebKitGTK/webkit-2.17.4/ > [2] https://github.com/apache/incubator-weex > > Best Regards, > YorkShen > > 申远
Re: [ANNOUNCEMENT] Weex 0.24.0 Released
On Mon, May 27, 2019 at 8:04 PM 申远 wrote: > > I agree with that. > > Moving playground to another separate repository(also under ASF?) may take > couple of days, I don't think there will be big technical issue. > > But this doesn't solve the issue that Weex Playground is under Apple > Developer Enterprise Program Account of Taobao (China) Software. And there > is a similar situation for Weex Android Playground. > So, it looks like Taobao publish the binary release of Weex Playground. I'm not sure if it is OK for Apache. Maybe we should find a way to let the PMC member to provide the convenience binary. > I could and would mark thing "Stuff that some third party provides for > Apache Weex", but for "Stuff for Weex the Apache Weex team also provides", > this is really confusing concept. > > Best Regards, > YorkShen > > 申远 > > > Jan Piotrowski 于2019年5月27日周一 下午4:32写道： > > > Thanks for the clarification. I understand why the Playground app is > > valuable and awesome for developers. > > > > Would it be an option to move the playground and connected code (e.g. > > for http://dotwe.org/vue) to a separate repository? Or does the > > `playground` code benefit so much from being in the same repository? > > > > For me right now this is one of these cases, where it is totally > > unclear what actually is part of "Apache Weex" (vs. "Stuff for Weex > > the Apache Weex team also provides" vs. "Stuff that some third party > > provides for Apache Weex"). > > > > -J > > > > > > Am Mo., 27. Mai 2019 um 09:01 Uhr schrieb 申远 : > > > > > > Let me rephrase myself. > > > > > >- The code of Android or iOS playground app is never part of Apache > > >Release. The release scripts always delete code of the Playground App > > >before publishing release candidate. > > >- The code of playground and weex_sdk is loosely coupled and the > > >playground is mainly for demo purpose, like Google Sample [1]. It > > should > > >*never* go into real product environment. > > >- But the playground does provide developers the convenience of > > >verifying the API or feature of Weex. They just need write code > > snippet > > >online [2], and scan the QR code, then they get what they write. > > > > > > [1] https://github.com/googlesamples > > > [2] http://dotwe.org/vue > > > > > > Best Regards, > > > YorkShen > > > > > > 申远 > > > > > > > > > Jan Piotrowski 于2019年5月24日周五 下午8:14写道： > > > > > > > A compiled Android or iOS native app is actually an interesting case. > > > > Is this actually part of the release, or is just the source code of > > > > the app? > > > > > > > > How tightly coupled are weex and the playground app anyway? Right now > > > > the playground app seems to live in a `playground` subfolder of `ios` > > > > and `android`. Would it maybe make sense to split that off in its own > > > > repo and have its own releases? I don't expect actual users of weex to > > > > really need the `playground` code, or do they? > > > > > > > > But yes, it would definitely be better to have this app not be > > > > published via a different commercial entity - no matter if you define > > > > the binary app to be part of the release or not. If Apache itself has > > > > a App Store Connect account I don't know though - best start by asking > > > > INFRA via a ticket. (Maybe it could also be published via one of the > > > > committers personal account as a fallback) > > > > > > > > -J > > > > > > > > > > > > -J > > > > > > > > Am Fr., 24. Mai 2019 um 12:20 Uhr schrieb 申远 : > > > > > > > > > > Dear Community > > > > > > > > > > Weex 0.24.0 is released now, one can download source or convenience > > > > binary > > > > > through the link in our website [1]. > > > > > > > > > > And there is a remaining issue for the release. One may notice that > > there > > > > > exists a showcase app called Weex Playground[2], which is compiled > > > > > from incubator-weex, but it is not a part os Apache Release as the > > > > release > > > > > script deleted the files of Playground when publishing release > > candidate. > > > > > As one need a enterprise certificates to publish an iOS App, we used > > to > > > > > borrow the certificates from Taobao(China), LTD. > > > > > > > > > > Based on the fact above, I have following concerns: > > > > > > > > > >1. I'd like to know whether it is ok to exclude some file during > > > > apache > > > > >release, like the code for Weex playground > > > > >2. I am not sure whether it is suitable that I continue borrow the > > > > >enterprise certificates from Taobao(China), LTD and publish the > > iOS > > > > App. If > > > > >it is not acceptable, is there any iOS enterprise certificates > > under > > > > ASF? > > > > > > > > > > [1] https://weex.apache.org/download/download.html#latest-release > > > > > [2] https://itunes.apple.com/cn/app/weex-playground/id1130862662 > > > > > > > > > > Best Regards, > > > > > YorkShen > > > > > > > > > > 申远 > > > > > >
Fwd: [incubator-weex] annotated tag 0.9.1.7 deleted (was 7e9a946)
Can I know why do we remove these tags? It's very danger to change the tags without any notification. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem -- Forwarded message - From: Date: Fri, May 24, 2019 at 5:38 PM Subject: [incubator-weex] annotated tag 0.9.1.7 deleted (was 7e9a946) To: comm...@weex.apache.org This is an automated email from the ASF dual-hosted git repository. kyork pushed a change to annotated tag 0.9.1.7 in repository https://gitbox.apache.org/repos/asf/incubator-weex.git. *** WARNING: tag 0.9.1.7 was deleted! *** tag was 7e9a946 The revisions that were on this annotated tag are still contained in other references; therefore, this change does not discard any commits from the repository.
Re: [DISCUSS] Weex Trademark issue
Hi York， Please take a look at the wiki page of the Apache-Dubbo-external-ecosystem-status, most of the repos were moved into Apache Dubbo umberaller. As Jan has said, we cannot see any improvements on Weex side yet. I think we should work together to try our best address this important issue in few month. BTW, I just have a quick look at the projects in the weex-plugin and weexteam. Lots of projects in weex-plugin have no update since 2017. I think we need to put more efforts to work with weexteam to make sure the projects are handled properly. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Mon, May 13, 2019 at 3:39 PM 申远 wrote: > > Hi, community > > I know this discussion happened before, but I'd like to mention it again. > > After review the discussion of trademark issue in Apache dubbo[1], I think > Weex should pay more attention trademark, too. As both Weex and Dubbo have > external ecosystem, which means there are repos[2] on github related to > Weex but not under ASF. > > Owners of this repo can choose donate this repo to Weex, renaming repos to > xxx-for-apache-weex or deleting such repos. Apache Dubbo really shows us a > good example. > > [1] > https://lists.apache.org/thread.html/dd36fa6c4ae4c1962be6c6a1235507eaa8c5c3ae009281e7cfdb2522@%3Cgeneral.incubator.apache.org%3E > [2] https://github.com/weex-plugins > [3] https://github.com/weexteam > [4] > https://github.com/apache/incubator-dubbo/wiki/Apache-Dubbo-external-ecosystem-status > > Best Regards, > YorkShen > > 申远
Re: [VOTE] Release Apache Weex (Incubating) 0.24.0-RC1
There is a big holiday in China, I guess lot lof PPMC member may out of town. @York Shen I think you need to ping around PPMC once you send out the release mail next time. Now we have to wait for the feedback from PPMC. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Thu, May 2, 2019 at 2:26 PM Myrle Krantz wrote: > > Hey Weex PMC, > > I'm concerned by the lack of voting here. Creating a release candidate as > YorkShen has done here requires a fair bit of effort. > > Please check the release and vote on it. > > YorkShen, you don't have to close the vote after 72 hours. 72 is a > minimum, not a maximum. You can wait until people have voted. Perhaps > there is a holiday there that prevented people from getting to this in the > 72 hours? > > Best, > Myrle > Mentor, Apache Weex (Incubating) > > On Mon, Apr 29, 2019 at 10:43 AM 申远 wrote: > > > Hi, community. > > > > I am going to call a vote for release Apache Weex (Incubating) 0.24.0 as > > mentioned before. > > > > > >- Git tag for this Release: > >https://github.com/apache/incubator-weex/releases/tag/0.24.0-RC1 > >- The source tarball could be found at : > > > > https://dist.apache.org/repos/dist/dev/incubator/weex/0.24.0/RC1/apache-weex-incubating-0.24.0-RC1-src.tar.gz > >- The signature of the source tarball could be found at : > > > > https://dist.apache.org/repos/dist/dev/incubator/weex/0.24.0/RC1/apache-weex-incubating-0.24.0-RC1-src.tar.gz.asc > >- The SHA-512 checksum of the source tarball could be found at : > > > > https://dist.apache.org/repos/dist/dev/incubator/weex/0.24.0/RC1/apache-weex-incubating-0.24.0-RC1-src.tar.gz.sha512 > >- The source tarball is signed with Key: EC0B28566883F364, which could > >be found in the key file: > >https://dist.apache.org/repos/dist/release/incubator/weex/KEYS > > > > One can build the binary from source according to > > https://github.com/apache/incubator-weex/blob/0.24.0-RC1/HOW-TO-BUILD.md > > with > > corresponding compiling tools. > > > > Note:* As the compiling tools relies on XCode/NDK 13/NDK 16, it would not > > be a surprise if your build fails on a non-Mac environment or without > > corresponding NDK tools.* > > > > This vote will remain open for at least 72 hours. Please vote on releasing > > this RC. > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove (and reason why) > > > > Best Regards, > > YorkShen > > > > 申远 > >
Re: New Committer: Peihan Chen
Welcome aboard! Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Apr 9, 2019 at 10:33 AM 申远 wrote: > > The Podling Project Management Committee (PPMC) for Apache Weex has invited > Peihan Chen to become a committer and we are pleased to announce that he > has accepted. > > Peihan Chen is a great Android Developer and give weex project many useful > PRs. He focuses on improving the stability, utility of Weex and the > following is part of his commit: > >- https://github.com/apache/incubator-weex/pull/1425, task may be null, >should be check, not try/catch >- https://github.com/apache/incubator-weex/pull/1835, edit interaction >logic && edit exception report logic #1835 >- https://github.com/apache/incubator-weex/pull/2029, fix multithread >task crash after instance crash && rm unnecessary exception > > Being a committer enables easier contribution to the project since there is > no need to go via the Github Pull Request process. This should enable > better productivity. Being a PMC member enables assistance with the > management and to guide the direction of the project. > > Best Regards, > YorkShen > > 申远
Re: Podling Report Reminder - April 2019
Hi， There are some issues on the weex apache website which need to be resolved ASAP. 1. We don't have the download link for the weex project. 2. There are lots download links tools[1] in the weex website, which source code are not part of apache weex project. [1]https://weex.apache.org/tools/ Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Mar 26, 2019 at 11:31 AM York Shen wrote: > > Hi, there > > As we need to prepare the Weex Podling Reports before 3rd, April, and we have > a national holiday in 5th, April in China, we’d better finish the report a > little earlier. > > The content of the report draft is below: > > 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. Third party plugins like weex-toolkit is not part of Apache Weex, and > they may violate the trademark / copyright of ASF > 2. The release procedure for Weex is not documented clearly. > 3. More active committers and PPMC members should be invited into the > community. > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > aware of? > No > > > How has the community developed since the last report? > 1. There are two new committers for Weex, e.g. He Ling and Darin726. > 2. We have a new mentor : Jan Piotrowski > 3. The mailing list for weex community is getting better, as we have 28 > mailing threads in d...@weex.apache.org <mailto:d...@weex.apache.org> > > > How has the project developed since the last report? > 1. We launched new website for Weex. > 2. We merged and closed 144 Github PRs > 3. We had 212 Github issues created and 145 of them are solved. > > > How would you assess the podling's maturity? > Please feel free to add your own commentary. > [ ] Initial setup > [ ] Working towards first release > [X] Community building > [ ] Nearing graduation > [ ] Other: > > Date of last release: > 2018-12-10 (v0.20.0) > > When were the last committers or PPMC members elected? > 2019-03-06 > > Have your mentors been helpful and responsive or are things falling > through the cracks? In the latter case, please list any open issues > that need to be addressed. > Yes, I think we have achieved lots of progress with their help in these month. > > > Best Regards, > York Shen > > 申远 > > > 在 2019年3月26日，10:45，York Shen 写道： > > > > As the deadline for Weex podling reports is 03, April, I am volunteer to > > write the draft and will send it to the mailing list to see if there is > > something need fixed. > > > > Best Regards, > > York Shen > > > > 申远 > > > >> 在 2019年3月24日，09:23，jmcl...@apache.org <mailto:jmcl...@apache.org> 写道： > >> > >> 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, 17 April 2019, 10:30 am PDT. > >> The report for your podling will form a part of the Incubator PMC > >> report. The Incubator PMC requires your report to be submitted 2 weeks > >> before the board meeting, to allow sufficient time for review and > >> submission (Wed, April 03). > >> > >> Please submit your report with sufficient time to allow the Incubator > >> PMC, and subsequently board members to review and digest. Again, the > >> very latest you should submit your report is 2 weeks prior to the board > >> meeting. > >> > >> Candidate names should not be made public before people are actually > >> elected, so please do not include the names of potential committers or > >> PPMC members in your report. > >> > >> Thanks, > >> > >> The Apache Incubator PMC > >> > >> Submitting your Report > >> > >> -- > >> > >> Your report should contain the following: > >> > >> * Your project name > >> * A brief description of your project, which assumes no knowledge of > >>the project or necessarily of its field > >> * A list of the three most important issues to address in the move > >>towards graduation. > >> * Any issues that the Incubator PMC or ASF Board might wish/need to be > >>aware of > >> * How has the community developed since the last report > >> * How has the project developed since the l
Re: New Committer: He Ling
Welcome He Ling！ I hope you already subscribe the dev mailing list. YorkShen, could you help us confirm that? Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Wed, Mar 6, 2019 at 10:41 AM 申远 wrote: > > 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 following is > part of his commit: > >- https://github.com/apache/incubator-weex/pull/1938, Fix >backgroundColor issues >- https://github.com/apache/incubator-weex/pull/2124, Fix text color >issues >- https://github.com/apache/incubator-weex/pull/2024, Fix crash > > Being a committer enables easier contribution to the project since there is > no need to go via the Github Pull Request process. This should enable > better productivity. Being a PMC member enables assistance with the > management and to guide the direction of the project. > > Best Regards, > YorkShen > > 申远
Re: [DISCUSS] Apache Project Maturity Model
It's getting better. For the release part, I just found we need to list all the artifacts which were released in the download page of our website. It's important that we need to go through the annou...@apache.org[1], and all the releases must be archived[2]. Please go through these two pages for more information about release. [1]http://www.apache.org/legal/release-policy.html#release-announcements [2]http://www.apache.org/dev/release-distribution.html#archival Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Thu, Mar 7, 2019 at 11:54 AM 申远 wrote: > > Hi, there > > It took me a few hours to evaluate the maturity for Weex according to The > Apache Project Maturity Model ( > http://community.apache.org/apache-way/apache-project-maturity-model.html), > it seems like there is still a big improvement space for Weex. The detail > is listed below: > Document issueReleaseRE50 > > The release process is documented and repeatable to the extent that someone > new to the project is able to independently generate the complete set of > artifacts required for a release. > > We should list the Apache Release procedure clearly in the document. > QualityQU30 > > The project provides a well-documented, secure and private channel to > report security issues, along with a documented way of responding to them. > > Again, we should list the report channel clearly in the document. > CommunityCO50 > > The way in which contributors can be granted more rights such as commit > access or decision power is clearly documented and is the same for all > contributors. > > Still, we need to list some basic requirement to be a committers. > Consensus BuildingCS10 > > The project maintains a public list of its contributors who have decision > power -- the project's PMC (Project Management Committee) consists of those > contributors. > > The PPMC & Committer is listed in in the weex status page > <http://incubator.apache.org/projects/weex.html>, I think adding a link to > weex status page in our document is enough. > CS20 > > Decisions are made by consensus among PMC members and are documented on the > project's main communications channel. Community opinions are taken into > account but the PMC has the final word if needed. > > Though we follow the normal Apache consensus building and voting procedure, > but we should make it clear in our document. > Long time issueCommunity > > The community is meritocratic and over time aims to give more rights and > responsibilities to contributors who add value to the project. > > The active committer of Weex is not enough, we need get more people > involved, and find more contributors and committers from weex users. > Consensus building > > All "important" discussions happen asynchronously in written form on the > project's main communications channel. Offline, face-to-face or private > discussions that affect the project are also documented on that channel. > > We are getting better at this part, but not enough. > Release > > We may need more release. > > Guys, what do you think of ? > > Best Regards, > YorkShen > > 申远
Re: Question about the website of weex
This kind of issue is exit for a while, for the health of the community, we need to get touch with these developers and help them to donate the code into Apache. I think most of them will be happy to be a part of the big family. If the code has some kind of License issue (has the hard dependency of GPL or LGPL), which we cannot host it in Apache. We could find another solution for it by naming it differently, just like camel-extra[1] with the Apache Camel[2]. But we cannot use the Apache Camel in the extra project. [1]https://github.com/camel-extra [2]https://github.com/apache/camel Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Thu, Mar 7, 2019 at 1:00 AM York Shen wrote: > > I understand the brand issues and the general topics. But let me explain my > concerns first: > > There are definitely some third party extensions violating the trademark of > Apache Weex. But in my opinion, I think weex’s( difficult to pronounce 路♀️) > priority is getting more developers into the community (mailing list instead > of github) and encourage them from users to contributor or committers. > Trademark issue is time consuming and may be not that urgent to Weex > community at this point (just personal opinion). > I’d like to treat thirty-party extensions as good sign because the Weex is > useful so that someone would develop tools for Weex. I want to show the kind > and friendly part of the Weex community, not threaten developers with law. > Maybe the boundary between kindness and weakness is not so clear, such > kindness may be treated as weakness. But I really don’t appreciate the idea > of threatening enthusiastic developers with law. > > Though, I understand that from ASF’s point, such violation may be > unacceptable and need corrected. So, I am really in a dilemma. > > > 在 2019年3月6日，23:11，Jan Piotrowski 写道： > > > > I assume Myrle's response was not focused on this one extension, but > > on the general topic we discussed over multiple emails. > > > > As soon as I have the necessary rights I will start to collect all the > > "problematic" things I can find in the GitHub project board and we can > > then start to discuss possible solutions or workarounds for those. > > > > The website is now fully on Git, so we should be able to iterate here > > quickly and efficiently. And I am sure we will find great solutions > > with all third parties as well. > > > > -J > > > > Am Mi., 6. März 2019 um 16:03 Uhr schrieb 申远 : > >> > >> 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 impractical. > >> > >> But these tools are useful, I can't pretend that I don't know there is a > >> such tool and ignore all the things that happened in the world beyond > >> apache community. > >> > >> What I can think of is that listing the useful tools in weex website and > >> make it clear it is not part of apache weex. > >> > >> Best Regards, > >> YorkShen > >> > >> 申远 > >> > >> > >> Myrle Krantz 于2019年3月6日周三 下午7:44写道： > >> > >>> 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 name which offers code that isn't from > >>> the weex project is a problem. If these tools are important to the > >>> project > >>> to the point that it is important that they share the weex brand, then > >>> they > >>> *do* belong on the Apache weex website. They also need to be licensed > >>> under ALv2, and released by the Weex PMC, and the source needs to be > >>> hosted > >>> on the apache github account. > >>> > >>> The Weex PMC needs to have control of all the weex code or else you won't > >>> be able to graduate. And generating more code in these off-list projects > >>> pushes your project *away* from graduation, not towards it. > >>> > >>> Best Regards, > >>> Myrle > >>> > >>> On Mon, Mar 4, 2019 at 1:51 PM Jan Piotrowski &
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 Twitter: willemjiang Weibo: 姜宁willem On Thu, Feb 28, 2019 at 11:46 AM 申远 wrote: > > > > > 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 than https://weex.apache.org/ for such > tools, I can move them. > > I cannot find the download the weex artifacts but only the weex IDE > > and playground. > > > As weex users are Android/iOS/JavaScript developers, they often choose > Gradle/Cocoapods/NPM to install the artifacts instead of source. But I > could list the artifacts and Gradle/Cocoapods/NPM link together in a > webpage later. > > BTW, once we vote the release, we need to distributed those release > > kit to Apache mirrors for the downloads of user. > > I don't think we did this step of work after the vote of weex 0.22.0 > > > I will move it later. I think I would propose the next release of weex, > which will give me a better understanding of the whole Apache release > procedure. > > Best Regards, > YorkShen > > 申远 > > > Willem Jiang 于2019年2月28日周四 上午10:35写道： > > > Hi York, > > > > I know weex team put lot of effort to build the whole eco system, from > > the runtime to development tools and others. > > But we can only host the downloads of the weex project, not the other > > tools which are built on top it. > > I cannot find the download the weex artifacts but only the weex IDE > > and playground. > > > > Could you explain it? > > > > BTW, once we vote the release, we need to distributed those release > > kit to Apache mirrors for the downloads of user. > > I don't think we did this step of work after the vote of weex 0.22.0[1] > > > > [1] > > https://lists.apache.org/thread.html/76f90754258431e48a6d86afedd3862b642320a43e3c96de4326a9cd@%3Cgeneral.incubator.apache.org%3E > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Tue, Feb 26, 2019 at 11:54 AM 申远 wrote: > > > > > > 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] https://weex.apache.org/ > > > > > > Best Regards, > > > YorkShen > > > > > > 申远 > > > > > > > > > Dan 于2019年2月26日周二 上午11:35写道： > > > > > > > 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 confused. > > > > > > > > > > [1]http://weex.apache.org/zh/community/biz-emas.html > > > > > > > > > > Willem Jiang > > > > > > > > > > Twitter: willemjiang > > > > > Weibo: 姜宁willem > > > > > > > > > > On Tue, Feb 26, 2019 at 10:57 AM Dan wrote: > > > > >> > > > > >> 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 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 project in the same site. > > > > >>> > > > > >>> I'm not sure if the PPMC member are knowing about this things, can > > you > > > > >>> explain it and let work on an solution together. > > > > >>> > > > > >>> [1]https://github.com/apache/incubator-weex-site/issues/325 > > > > >>> [2]http://emas.weex.io/zh/community/biz-emas.html > > > > >>> > > > > >>> Willem Jiang > > > > >>> > > > > >>> Twitter: willemjiang > > > > >>> Weibo: 姜宁willem > > > > >>> > > > > > > > > > >
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: 姜宁willem On Tue, Feb 26, 2019 at 10:57 AM Dan wrote: > > 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 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 project in the same site. > > > > I'm not sure if the PPMC member are knowing about this things, can you > > explain it and let work on an solution together. > > > > [1]https://github.com/apache/incubator-weex-site/issues/325 > > [2]http://emas.weex.io/zh/community/biz-emas.html > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > >
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 project in the same site. I'm not sure if the PPMC member are knowing about this things, can you explain it and let work on an solution together. [1]https://github.com/apache/incubator-weex-site/issues/325 [2]http://emas.weex.io/zh/community/biz-emas.html Willem Jiang Twitter: willemjiang Weibo: 姜宁willem
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: image.png] > > -J > > Am Fr., 22. Feb. 2019 um 08:43 Uhr schrieb 申远 : > >> 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 file you mentioned above? If so, I can't checkout that, as the >> directory of trunk took me 10GB hard disk space, and was still growing. I >> have just checkout >> https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects >> , >> which is a much smaller directory. >> >> [1]. http://incubator.apache.org/projects/weex.html >> [2]. >> >> https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/weex.xml >> [3] >> >> >> Best Regards, >> YorkShen >> >> 申远 >> >> >> Willem Jiang 于2019年2月22日周五 下午2:26写道： >> >> > 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: >> > >> > > 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 automatically, which give me a big surprise. >> > > >> > > [1]. >> > > >> > > >> > >> https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/weex.xml >> > > [2]. http://incubator.apache.org/projects/weex.html >> > > >> > > >> > > Best Regards, >> > > YorkShen >> > > >> > > 申远 >> > > >> > > >> > > Jan Piotrowski 于2019年2月21日周四 下午8:48写道： >> > > >> > > > 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 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 time. >> > > > > >> > > > > Best Regards, >> > > > > YorkShen >> > > > > >> > > > > 申远 >> > > > > >> > > > > >> > > > > Willem Jiang 于2019年2月13日周三 下午12:38写道： >> > > > > >> > > > > > You can send me the diff file if you don't have the right to >> > change. >> > > > > > >> > > > > > Willem Jiang >> > > > > > >> > > > > > Twitter: willemjiang >> > > > > > Weibo: 姜宁willem >> > > > > > >> > > > > > >> > > > > > On Wed, Feb 13, 2019 at 11:41 AM 申远 >> wrote: >> > > > > > >> > > >
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 22, 2019 at 7:58 PM 申远 wrote: > > It seems like INFRA is not ok the mirror site in China. > > Anyway, I have updated the content of https://weex.apache.org/, which is > the same as https://weex.io now. *As there is a > privilege issue, https://weex-project.io/ <https://weex-project.io/> is not > updated yet.* > > Later, I will redirect https://weex.io and https://weex-project.io/ to > https://weex.apache.org/ using 302 redirection and configure robots. > > Feedback of the new design for https://weex.apache.org/ is welcomed. > > Thanks > > Best Regards, > YorkShen > > 申远 > > > Jan Piotrowski 于2019年2月20日周三 下午8:02写道： > > > 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 > > > > 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 robots.txt to not confuse them). INFRA should have no real problem > > > > with that (as it is a appropriate workaround for their slow response > > > > times in China - and no branding stuff is ignored). > > > > > > > > > 1. Deploying the same content to two different host and domains is what > > we > > > are planning to do until we understand it may still break one domain > > rule. > > > > > > 2. According to https://issues.apache.org/jira/browse/INFRA-17872 , I > > think > > > INFRA have different point of view on separate domain with same content. > > > > > > 3. Personally speaking, I understand a world wide CDN is not practical > > now > > > and sometimes one may give up a better engineer solution due to law > > issue. > > > From user points, we need to give a brief explanation of the latency > > > problem. > > > > > > Best Regards, > > > YorkShen > > > > > > 申远 > > > > > > > > > Jan Piotrowski 于2019年2月20日周三 上午2:24写道： > > > > > > > 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 TTL=46 > > > > Reply from 47.75.160.176: bytes=32 time=327ms TTL=46 > > > > Reply from 47.75.160.176: bytes=32 time=327ms TTL=46 > > > > Reply from 47.75.160.176: bytes=32 time=335ms TTL=46 > > > > > > > > Ping statistics for 47.75.160.176: > > > > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > > > > Approximate round trip times in milli-seconds: > > > > Minimum = 327ms, Maximum = 335ms, Average = 329ms > > > > > > > > C:\Users\Jan>ping weex.apache.org > > > > > > > > Pinging weex.apache.org [2a01:4f9:2a:185f::2] with 32 bytes of data: > > > > Reply from 2a01:4f9:2a:185f::2: time=46ms > > > > Reply from 2a01:4f9:2a:185f::2: time=46ms > > > > Reply from 2a01:4f9:2a:185f::2: time=49ms > > > > Reply from 2a01:4f9:2a:185f::2: time=46ms > > > > > > > > Ping statistics for 2a01:4f9:2a:185f::2: > > > > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > > > > Approximate round trip times in milli-seconds: > > > > Minimum = 46ms, Maximum = 49ms, Average = 46ms > > > > > > > > So you should be aware that the actual problem (Apache server is slow > > > > from China) is a different one that is now discussed with INFRA (Can > > > > project use a different domain). > > > > > > > > The only real solution is for INFRA to use a world wide CDN that is > > &g
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 not know there could be other people who try to find information in the mailing list by using the search engine. As an apache project, there are lots of potential users who speak English, using English to answer the question could help them to understand the who pictures more easily. Most of Chinese developer can read and write English document, as we spend more than 6 years to study English. I don't think it could be a blocker for us to build the community by answering the question in English. But we need to keep in mind that the discussion we have is not just for us, it's could for the community to catch up later. FYI, there are some discussions[1] years ago about using IM (such as QQ and WeChat) and Chinese, you may take a look at them. [1]https://www.mail-archive.com/general@incubator.apache.org/msg57192.html Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Feb 22, 2019 at 4:05 PM 申远 wrote: > > > > > 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 Chinese question to > English, then answer it in English, until I realized that the users who > post the question may not understand my answer in English, which doesn't > fulfill the goal of helping user at all. Besides, from our users' point, > choosing a language the original user may not understand by deliberately > may be a arrogant behavior. > > Maybe I should answer Chinese Question with English and then Google > translate back to English, which is still a little wired and complicated > though. > > Best Regards, > YorkShen > > 申远 > > > Willem Jiang 于2019年2月22日周五 上午10:48写道： > > > I think using the English to discuss is consider for more audiences > > across the world, with the help of translator service it's not big > > challenge for the average chinese developer to get involved. > > We could set up a rule in the mailing list or gitter to discuss the > > question in English. From my experience it's a big first step to build > > the internationalized community. > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Thu, Feb 21, 2019 at 12:21 PM 申远 wrote: > > > > > > 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 <https://github.com/apache/incubator-weex/issues>. What should > > we do > > > under this situation? > > > > > > 1. Answering their question with English, which is wired as original post > > > is Chinese. Moreover, it may be a little arrogant as answering Chinese > > > question with English shows the person written the answer understand > > > Chinese but somehow choose a language(English) deliberately the original > > > poster may not understand. > > > > > > 2. Answering questions with Chinese, which is a easy work for me and > > other > > > Chinese users. But other users that who doesn't speak Chinese will have a > > > difficult time to understand what is happening here. > > > > > > Best Regards, > > > YorkShen > > > > > > 申远 > >
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: > 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 automatically, which give me a big surprise. > > [1]. > > https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/weex.xml > [2]. http://incubator.apache.org/projects/weex.html > > > Best Regards, > YorkShen > > 申远 > > > Jan Piotrowski 于2019年2月21日周四 下午8:48写道： > > > 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 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 time. > > > > > > Best Regards, > > > YorkShen > > > > > > 申远 > > > > > > > > > Willem Jiang 于2019年2月13日周三 下午12:38写道： > > > > > > > You can send me the diff file if you don't have the right to change. > > > > > > > > Willem Jiang > > > > > > > > Twitter: willemjiang > > > > Weibo: 姜宁willem > > > > > > > > > > > > On Wed, Feb 13, 2019 at 11:41 AM 申远 wrote: > > > > > > > > > It seems like that XML file hosted on SVN, which is a quite classic > > > way. > > > > > > > > > > > > > > I will try later after I get my SVN environment installed. > > > > > > > > > > Best Regards, > > > > > YorkShen > > > > > > > > > > 申远 > > > > > > > > > > > > > > > Willem Jiang 于2019年2月2日周六 上午11:49写道： > > > > > > > > > > > Yes, the website is generated from the XML file. Can you try to > > > update > > > > > > the file yourself? > > > > > > The Apache Member has the right to change it but I'm such if the > > PPMC > > > > > > has the same right to updated the file. > > > > > > > > > > > > > > > > > > Willem Jiang > > > > > > > > > > > > Twitter: willemjiang > > > > > > Weibo: 姜宁willem > > > > > > > > > > > > On Thu, Jan 31, 2019 at 11:10 AM York Shen > > > > > wrote: > > > > > > > > > > > > > > I found the content of the weex website ( > > > > > > http://incubator.apache.org/projects/weex.html < > > > > > > http://incubator.apache.org/projects/weex.html>) is written by > XML > > > > > > > > > > > > > > > > > > > > > https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/weex.xml > > > > > > < > > > > > > > > > > > > > > > > > > > > > https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/weex.xml > > > > > > > > > > > > . > > > > > > > > > > > > > > Do I need to change the XML file directly or is the XML file > > > > generated > > > > > > by another file like xxx.html and I should change xxx.html? > > > > > > > > > > > > > > Best Regards, > > > > > > > York Shen > > > > > > > > > > > > > > 申远 > > > > > > > > > > > > > > > 在 2019年1月29日，09:00，Willem Jiang 写道： > > > > > > > > > > > > > > > > The website is generated from the here[1]. You may need to > > Apache > > > > > > > > member right to edit it. > > > > > > > > If you cannot change it, please let me know the change, I'd > > happy > > > > to > > > > > > > > update it for you. > > > > > > > > > > > > > > > > [1]https://svn.apache.org/repos/asf/incubator/public/trunk > > > > > > > > [2] > > > > > > > > > > > > > > > > > > > > > https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/weex.xml > > > > > > > > > > > > > > > > Willem Jiang > > > > > > > > > > > > > > > > Twitter: willemjiang > > > > > > > > Weibo: 姜宁willem > > > > > > > > > > > > > > > > On Wed, Jan 16, 2019 at 8:49 PM 申远 > > wrote: > > > > > > > >> > > > > > > > >> Hi, there > > > > > > > >> > > > > > > > >> I’d like to update the page of weex > > > > > > http://incubator.apache.org/projects/weex.html < > > > > > > http://incubator.apache.org/projects/weex.html> , it seems like > > > > > outdated. > > > > > > I didn’t find any editing button on the page, it would be great > if > > > some > > > > > > could tell me how to edit that page. > > > > > > > >> > > > > > > > >> Thanks > > > > > > > > > > > > > > > > > > > > > > > > > > > >
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 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 mirror website weex-project.io for Chinese developer. > 3. We expect to support https on this website and support some of our own > server functions, such as Q robots, article blog posts, etc. > > I would like to ask if apache has any restrictions on this third-party > domain name, and look forward to hearing from you. > > Thanks, > Dan
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 Weibo: 姜宁willem On Thu, Feb 14, 2019 at 10:48 AM 申远 wrote: > > According to dependency in package.json > <https://github.com/weexteam/weex-toolkit/blob/master/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 Jiang 于2019年2月13日周三 下午2:35写道： > > > If we want to move the repo, we need to address the SGA problem first. > > It has nothing to do with the committer right yet, we just need to > > make sure the IP issue is resolved before moving forward. > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Wed, Feb 13, 2019 at 11:41 AM Dan wrote: > > > > > > Hi Jan, > > > > > > > Definitely include INFRA in the move of the repositories, they can > > > probably > > > make it a normal move/transfer of a GitHub repository between two orgs, > > so > > > not only the stars, but also issues, PRs etc are moved and the old URLs > > are > > > automatically forwarded. The only thing one has to do manually, is to > > > update the user/repository name if you use it in the code somewhere - but > > > probably also not _right now_, but whenever you have the time to do so - > > as > > > all the links, repository clones etc. should be forwarded. > > > > > > Did you mean to transfer the `weexteam/weex-toolkit` project to the link > > > like `apache/incubator-weex-tools`? This seems to be a relatively > > low-cost > > > method at present. I only need someone to help me check the > > specifications > > > of the project. > > > > > > By the way, after that, there will be three git repo on the > > > `apache/weex` team, like `apache/incubator-weex`, `apache/incubator- > > > weex-site` and `apache/incubator-weex-tools`, I don't know that's ok or > > > not, just tell the situation. > > > > > > I am not a committer for the apache/weex now, also I am not very familiar > > > with the apache process. > > > > > > Maybe someone can list what we need to do next? > > > > > > Thanks, > > > Dan > > > > > > Jan Piotrowski 于2019年2月12日周二 下午9:20写道： > > > > > > > If I may give some input here as well: > > > > Definitely include INFRA in the move of the repositories, they can > > probably > > > > make it a normal move/transfer of a GitHub repository between two > > orgs, so > > > > not only the stars, but also issues, PRs etc are moved and the old > > URLs are > > > > automatically forwarded. The only thing one has to do manually, is to > > > > update the user/repository name if you use it in the code somewhere - > > but > > > > probably also not _right now_, but whenever you have the time to do so > > - as > > > > all the links, repository clones etc. should be forwarded. > > > > > > > > -J > > > > > > > > Am Di., 12. Feb. 2019 um 13:43 Uhr schrieb Willem Jiang < > > > > willem.ji...@gmail.com>: > > > > > > > > > I don't aware the git repository transfer issue, if it related to the > > > > > snapshot release, I think we can work out a solution for it. > > > > > If it relates to SGA things, I think we need to dig more detail about > > > > that. > > > > > Anyway, I'd happy to help you to do the code transfer work. > > > > > > > > > > Willem Jiang > > > > > > > > > > Twitter: willemjiang > > > > > Weibo: 姜宁willem > > > > > > > > > > On Tue, Feb 12, 2019 at 5:33 PM Myrle Krantz > > wrote: > > > > > > > > > > > > Hey Dan, > > > > > > > > > > > > On Tue, Feb 12, 2019 at 4:46 AM Dan wrote: > > > > > > > > > > > > > Hi, Myrle > > > > > > > > > > > > > > Sorry for the delay getting back to you. > > > > > > > > > > > > > > > > > > > No problem. I hope you
Re: Weex, Apache and outside code
If we want to move the repo, we need to address the SGA problem first. It has nothing to do with the committer right yet, we just need to make sure the IP issue is resolved before moving forward. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Wed, Feb 13, 2019 at 11:41 AM Dan wrote: > > Hi Jan, > > > Definitely include INFRA in the move of the repositories, they can > probably > make it a normal move/transfer of a GitHub repository between two orgs, so > not only the stars, but also issues, PRs etc are moved and the old URLs are > automatically forwarded. The only thing one has to do manually, is to > update the user/repository name if you use it in the code somewhere - but > probably also not _right now_, but whenever you have the time to do so - as > all the links, repository clones etc. should be forwarded. > > Did you mean to transfer the `weexteam/weex-toolkit` project to the link > like `apache/incubator-weex-tools`? This seems to be a relatively low-cost > method at present. I only need someone to help me check the specifications > of the project. > > By the way, after that, there will be three git repo on the > `apache/weex` team, like `apache/incubator-weex`, `apache/incubator- > weex-site` and `apache/incubator-weex-tools`, I don't know that's ok or > not, just tell the situation. > > I am not a committer for the apache/weex now, also I am not very familiar > with the apache process. > > Maybe someone can list what we need to do next? > > Thanks, > Dan > > Jan Piotrowski 于2019年2月12日周二 下午9:20写道： > > > If I may give some input here as well: > > Definitely include INFRA in the move of the repositories, they can probably > > make it a normal move/transfer of a GitHub repository between two orgs, so > > not only the stars, but also issues, PRs etc are moved and the old URLs are > > automatically forwarded. The only thing one has to do manually, is to > > update the user/repository name if you use it in the code somewhere - but > > probably also not _right now_, but whenever you have the time to do so - as > > all the links, repository clones etc. should be forwarded. > > > > -J > > > > Am Di., 12. Feb. 2019 um 13:43 Uhr schrieb Willem Jiang < > > willem.ji...@gmail.com>: > > > > > I don't aware the git repository transfer issue, if it related to the > > > snapshot release, I think we can work out a solution for it. > > > If it relates to SGA things, I think we need to dig more detail about > > that. > > > Anyway, I'd happy to help you to do the code transfer work. > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > > On Tue, Feb 12, 2019 at 5:33 PM Myrle Krantz wrote: > > > > > > > > Hey Dan, > > > > > > > > On Tue, Feb 12, 2019 at 4:46 AM Dan wrote: > > > > > > > > > Hi, Myrle > > > > > > > > > > Sorry for the delay getting back to you. > > > > > > > > > > > > > No problem. I hope you enjoyed Chinese New Year! > > > > > > > > > Normally repo history can also be imported to an Apache repository. > > Is > > > > > that what you mean by warehouse? > > > > > > > > > > The `warehouse` is caused by incorrect translation, it should means > > git > > > > > repo, don't mind. I know there has a way to import history into > > Apache > > > > > repo, but based on the experience of the last weex repo migration, > > some > > > > > developers will be very uncomfortable with this change, and may even > > > feel > > > > > that this is an unstable performance. At the same time, some > > developers > > > > > will still feedback new project issues in the old project. We need to > > > > > conduct reasonable and effective guidance, I think this is not a > > matter > > > > > that can be decided immediately, I will initiate a vote on this > > matter. > > > > > > > > > > > > > I'm sorry to hear that things didn't go smoothly in the first transfer. > > > I > > > > don't know the details, since I wasn't mentoring then. > > > > > > > > As I understand it, Infra can also do a repository move, which would > > > bring > > > > over all the stars, etc. Would you like me to ask? > > > > > > > > Best Regards, > > > > Myrle > > > > >
Re: Update weex descriptions on Apache site
You can send me the diff file if you don't have the right to change. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Wed, Feb 13, 2019 at 11:41 AM 申远 wrote: > It seems like that XML file hosted on SVN, which is a quite classic way. > > I will try later after I get my SVN environment installed. > > Best Regards, > YorkShen > > 申远 > > > Willem Jiang 于2019年2月2日周六 上午11:49写道： > > > Yes, the website is generated from the XML file. Can you try to update > > the file yourself? > > The Apache Member has the right to change it but I'm such if the PPMC > > has the same right to updated the file. > > > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Thu, Jan 31, 2019 at 11:10 AM York Shen wrote: > > > > > > I found the content of the weex website ( > > http://incubator.apache.org/projects/weex.html < > > http://incubator.apache.org/projects/weex.html>) is written by XML > > > https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/weex.xml > > < > > > https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/weex.xml > > > > . > > > > > > Do I need to change the XML file directly or is the XML file generated > > by another file like xxx.html and I should change xxx.html? > > > > > > Best Regards, > > > York Shen > > > > > > 申远 > > > > > > > 在 2019年1月29日，09:00，Willem Jiang 写道： > > > > > > > > The website is generated from the here[1]. You may need to Apache > > > > member right to edit it. > > > > If you cannot change it, please let me know the change, I'd happy to > > > > update it for you. > > > > > > > > [1]https://svn.apache.org/repos/asf/incubator/public/trunk > > > > [2] > > > https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/weex.xml > > > > > > > > Willem Jiang > > > > > > > > Twitter: willemjiang > > > > Weibo: 姜宁willem > > > > > > > > On Wed, Jan 16, 2019 at 8:49 PM 申远 wrote: > > > >> > > > >> Hi, there > > > >> > > > >> I’d like to update the page of weex > > http://incubator.apache.org/projects/weex.html < > > http://incubator.apache.org/projects/weex.html> , it seems like > outdated. > > I didn’t find any editing button on the page, it would be great if some > > could tell me how to edit that page. > > > >> > > > >> Thanks > > > > > >
Re: Weex, Apache and outside code
I don't aware the git repository transfer issue, if it related to the snapshot release, I think we can work out a solution for it. If it relates to SGA things, I think we need to dig more detail about that. Anyway, I'd happy to help you to do the code transfer work. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Feb 12, 2019 at 5:33 PM Myrle Krantz wrote: > > Hey Dan, > > On Tue, Feb 12, 2019 at 4:46 AM Dan wrote: > > > Hi, Myrle > > > > Sorry for the delay getting back to you. > > > > No problem. I hope you enjoyed Chinese New Year! > > > Normally repo history can also be imported to an Apache repository. Is > > that what you mean by warehouse? > > > > The `warehouse` is caused by incorrect translation, it should means git > > repo, don't mind. I know there has a way to import history into Apache > > repo, but based on the experience of the last weex repo migration, some > > developers will be very uncomfortable with this change, and may even feel > > that this is an unstable performance. At the same time, some developers > > will still feedback new project issues in the old project. We need to > > conduct reasonable and effective guidance, I think this is not a matter > > that can be decided immediately, I will initiate a vote on this matter. > > > > I'm sorry to hear that things didn't go smoothly in the first transfer. I > don't know the details, since I wasn't mentoring then. > > As I understand it, Infra can also do a repository move, which would bring > over all the stars, etc. Would you like me to ask? > > Best Regards, > Myrle
Re: Update weex descriptions on Apache site
Yes, the website is generated from the XML file. Can you try to update the file yourself? The Apache Member has the right to change it but I'm such if the PPMC has the same right to updated the file. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Thu, Jan 31, 2019 at 11:10 AM York Shen wrote: > > I found the content of the weex website > (http://incubator.apache.org/projects/weex.html > <http://incubator.apache.org/projects/weex.html>) is written by XML > https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/weex.xml > > <https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/weex.xml> > . > > Do I need to change the XML file directly or is the XML file generated by > another file like xxx.html and I should change xxx.html? > > Best Regards, > York Shen > > 申远 > > > 在 2019年1月29日，09:00，Willem Jiang 写道： > > > > The website is generated from the here[1]. You may need to Apache > > member right to edit it. > > If you cannot change it, please let me know the change, I'd happy to > > update it for you. > > > > [1]https://svn.apache.org/repos/asf/incubator/public/trunk > > [2]https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/weex.xml > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Wed, Jan 16, 2019 at 8:49 PM 申远 wrote: > >> > >> Hi, there > >> > >> I’d like to update the page of weex > >> http://incubator.apache.org/projects/weex.html > >> <http://incubator.apache.org/projects/weex.html> , it seems like outdated. > >> I didn’t find any editing button on the page, it would be great if some > >> could tell me how to edit that page. > >> > >> Thanks >
Re: Weex, Apache and outside code
Here is instruction of distribution unrelease materials[1], as the SNAPSHOT means it's not official release, we just use it for the feedback the development. [1]https://www.apache.org/dev/release-distribution#unreleased Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Feb 1, 2019 at 4:44 PM York Shen wrote: > > According to my understanding and what Justin Mclean wrote > https://lists.apache.org/thread.html/5c5a75f00d78211f75e10d17bfeb05bc7b0b4f9e8416fa602b0ebb54@%3Cgeneral.incubator.apache.org%3E > > <https://lists.apache.org/thread.html/5c5a75f00d78211f75e10d17bfeb05bc7b0b4f9e8416fa602b0ebb54@%3Cgeneral.incubator.apache.org%3E> > , any format of unofficial release is forbidden, all release must be voted > before we publish it. > > Correct me if I am wrong. > > > Best Regards, > York Shen > > 申远 > > > 在 2019年2月1日，16:27，Willem Jiang 写道： > > > > A lot of Apache project has the SNAPSHOT release to get quick feedback > > from the community. > > It's OK if we don't announce the SNAPSHOT release as an office Apache > > release. > > > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Fri, Feb 1, 2019 at 3:07 PM Dan wrote: > >> > >> Hey > >> > >> I'm the author of the weex-toolkit, also the main developer of the tools > >> around weex, I need to explain the questions you mentioned above. > >> > >>> Is this redirection and inclusion of outside code intentional? Is this > >> temporary or meant to be permanent? > >> Early in the development and maintenance of this project, the project was > >> designed to support package integration of multiple command line tools, and > >> to manage mappings between them through xtoolkit module, the idea is good, > >> but too many projects are scattered into the various git repo, such as > >> weex-debugger, weex-pack and so on. > >> > >> On the weex-toolkit@2.0, I'm split each function module into separate > >> parts, and manage multiple separate releases in the repository via Lerna, > >> after that you can find all the module you want in the weex-toolkit repo > >> (currently in the alpha process), you can enjoy it follow the document > >> here: https://weex.io/tools/toolkit.html, it also supports the thrid-part > >> extensions, the document will be further supplemented > >> > >>> About move weex-toolkit project into the Apache repo. > >> > >> For now, this is a little difficult and also inconvenient thing cause the > >> current 2.0 tools are in a state of rapid iteration, and I also hope to get > >> the user's usage from the tool, this may not be allowed by apache, I prefer > >> to develop these tools as a third-party developer, it should be ok to > >> remind users in the documentation that it's not part of Apache Weex. > >> > >>> why the module called toolkit but not cli? > >> > >> This is the name defined by the previous module creator. I personally think > >> it might be better to call it weex-cli. Maybe I will consider renaming the > >> module soon. > >> > >> Thanks > >> Dan > >> > >> Jan Piotrowski 于2019年2月1日周五 上午3:13写道： > >> > >>> (Answering from my Apache address as my Gmail didn't receive your > >>> responses - I can only see them in the list archive. Strange.) > >>> > >>> Thanks York Shen and Willem Jiang for your answers. > >>> > >>>> As there are many Weex users coming from China and the GFW is a huge > >>> problem for them, so we create several website for users from China to > >>> have > >>> the right access. You can choose whatever you want, as the three websites > >>> are all the same. > >>> > >>> Thanks for that explanation. > >>> > >>> In my opinion (and maybe Apache guidelines?) there should only be _one_ > >>> domain per Apache project, so you know you can trust the content of that > >>> domain. You (the team) should probably decide which one of the two > >>> apache.org domains you should use (and can use per incubation rules!), > >>> and redirect the other one. Otherwise both Google and users can be > >>> confused. > >>> For the non-Apache mirrors for Chinese users you could maybe add a banner > >>> that this is a mirror of *.apache.org for Chinese users and link to it > >>> from somewhere _on_ the site so it is discoverable? Addition
Re: Weex, Apache and outside code
A lot of Apache project has the SNAPSHOT release to get quick feedback from the community. It's OK if we don't announce the SNAPSHOT release as an office Apache release. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Feb 1, 2019 at 3:07 PM Dan wrote: > > Hey > > I'm the author of the weex-toolkit, also the main developer of the tools > around weex, I need to explain the questions you mentioned above. > > > Is this redirection and inclusion of outside code intentional? Is this > temporary or meant to be permanent? > Early in the development and maintenance of this project, the project was > designed to support package integration of multiple command line tools, and > to manage mappings between them through xtoolkit module, the idea is good, > but too many projects are scattered into the various git repo, such as > weex-debugger, weex-pack and so on. > > On the weex-toolkit@2.0, I'm split each function module into separate > parts, and manage multiple separate releases in the repository via Lerna, > after that you can find all the module you want in the weex-toolkit repo > (currently in the alpha process), you can enjoy it follow the document > here: https://weex.io/tools/toolkit.html, it also supports the thrid-part > extensions, the document will be further supplemented > > > About move weex-toolkit project into the Apache repo. > > For now, this is a little difficult and also inconvenient thing cause the > current 2.0 tools are in a state of rapid iteration, and I also hope to get > the user's usage from the tool, this may not be allowed by apache, I prefer > to develop these tools as a third-party developer, it should be ok to > remind users in the documentation that it's not part of Apache Weex. > > > why the module called toolkit but not cli? > > This is the name defined by the previous module creator. I personally think > it might be better to call it weex-cli. Maybe I will consider renaming the > module soon. > > Thanks > Dan > > Jan Piotrowski 于2019年2月1日周五 上午3:13写道： > > > (Answering from my Apache address as my Gmail didn't receive your > > responses - I can only see them in the list archive. Strange.) > > > > Thanks York Shen and Willem Jiang for your answers. > > > > > As there are many Weex users coming from China and the GFW is a huge > > problem for them, so we create several website for users from China to have > > the right access. You can choose whatever you want, as the three websites > > are all the same. > > > > Thanks for that explanation. > > > > In my opinion (and maybe Apache guidelines?) there should only be _one_ > > domain per Apache project, so you know you can trust the content of that > > domain. You (the team) should probably decide which one of the two > > apache.org domains you should use (and can use per incubation rules!), > > and redirect the other one. Otherwise both Google and users can be > > confused. > > For the non-Apache mirrors for Chinese users you could maybe add a banner > > that this is a mirror of *.apache.org for Chinese users and link to it > > from somewhere _on_ the site so it is discoverable? Additionally maybe > > no-index the domain, so Google doesn't list them? Then it is all > > transparent and there is no confusion. > > > > > The repo for weex is https://github.com/apache/incubator-weex, from > > where weex community generates apache release. > > > All the other repos is not officially belong to weex, though some of are > > useful tools for debug, development purpose. They are just useful tools, > > one can using weex framework without these tools with no problem. I will > > consider these tools as useful plugins, and there are perhaps tens of such > > plugins, so they are not under Apache repositories. > > > I will ask the authors of https://github.com/weexteam/xtoolkit and > > https://github.com/weexteam/weex-pack, not sure whether there is a > > license issue or they are happy to move into Apache Weex umbrella > > officially. > > > > The documentation and guides made them sound very much a part of Weex - so > > if in any way possible you should move _all_ the tools, plugins, > > playground, and other pieces that are used in the documentation and > > examples to Apache repositories (PMC members and committers can create > > additional repositories at https://gitbox.apache.org/setup/newrepo.html). > > > > If you can't transfer any of the code for licence reasons, it should be > > clearly documented in the documentation when you advise users to use it > > that this is not part of Apache Weex, but a user space plugin or proj
Re: Weex, Apache and outside code
Apache is encourage to unify the community and current infrastructure supports one project has multiple repositories. If there is no license issue, we need to consider to move these repositories into the umbrella of Apache Weex. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Thu, Jan 31, 2019 at 8:59 PM York Shen wrote: > > 1. Repos Problem > https://github.com/apache/incubator-weex-site > <https://github.com/apache/incubator-weex-site> is the repos for weex’s > website as you mentioned. > The repo for weex is https://github.com/apache/incubator-weex > <https://github.com/apache/incubator-weex>, from where weex community > generates apache release. > All the other repos is not officially belong to weex, though some of are > useful tools for debug, development purpose. They are just useful tools, one > can using weex framework without these tools with no problem. I will consider > these tools as useful plugins, and there are perhaps tens of such plugins, so > they are not under Apache repositories. > > > 2. All website you listed is coming > https://github.com/apache/incubator-weex-site > <https://github.com/apache/incubator-weex-site> . As there are many Weex > users coming from China and the GFW is a huge problem for them, so we create > several website for users from China to have the right access. You can choose > whatever you want, as the three websites are all the same. > > 3. Feel free to ask anything about weex, I am glad to answer these questions. > > Best Regards, > York Shen > > 申远 > > > 在 2019年1月31日，20:31，Jan Piotrowski 写道： > > > > Hey, > > > > I recently spent some time looking into Weex (I am a PMC member of > > committer to Apache Cordova and was interested how you do things). But I > > quickly noticed, that although Weex being an Apache Incubator project, most > > of the code of Weex seems to come from an outside Github organization. This > > left me a bit confused what is going on, and where what code is coming from > > and what it is used for. > > > > There are only 2 Apache (Incubator) repositories for Weex: > > https://github.com/apache/incubator-weex > > https://github.com/apache/incubator-weex-site > > > > The main repository https://github.com/apache/incubator-weex quickly links > > me to https://github.com/weexteam/weex-toolkit which seems to be a CLI > > (toolkit = CLI?) to create and build Weex based apps. Its npm dependencies > > are pretty light, but it seems to download many more code via > > https://github.com/weexteam/xtoolkit anyway and cache it with some custom > > mechanism, like e.g. https://github.com/weexteam/weex-pack that seems to > > contain the code to create, run, build native apps. > > > > Is this redirection and inclusion of outside code intentional? > > Is this temporary or meant to be permanent? > > > > There are also many more repositories at https://github.com/weexteam that I > > have no idea what they are used for. > > > > (That being said, the guide at http://weex.apache.org/guide/ is really good > > and gives a very clear picture what steps need to be taken to developer a > > Weex app - it just all breaks down if you look behind the curtain and try > > to understand where all the code comes from and what is going on a level > > deeper.) > > > > The website also seems to be available under several domains: > > http://weex.incubator.apache.org > > https://weex.apache.org > > https://weex-project.io > > Do these all host the same content from > > https://github.com/apache/incubator-weex-site? Or are those different > > things? > > > > Best, > > Jan >
Re: Update weex descriptions on Apache site
The website is generated from the here[1]. You may need to Apache member right to edit it. If you cannot change it, please let me know the change, I'd happy to update it for you. [1]https://svn.apache.org/repos/asf/incubator/public/trunk [2]https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/weex.xml Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Wed, Jan 16, 2019 at 8:49 PM 申远 wrote: > > Hi, there > > I’d like to update the page of weex > http://incubator.apache.org/projects/weex.html > <http://incubator.apache.org/projects/weex.html> , it seems like outdated. I > didn’t find any editing button on the page, it would be great if some could > tell me how to edit that page. > > Thanks
Re: [DISCUSS] Local Language mailing list?
There was a hot discussion[1] about the mailing list language when RocketMQ join the Apache. We still need to encourage people to use the mailing list with English for the audience around the world. In the meantime, we could lower the bar by let more people involved by avoiding the internal discussion first and starting the discussion in the public mailing list. [1]https://www.mail-archive.com/general@incubator.apache.org/msg57218.html Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Jan 25, 2019 at 2:57 PM 申远 wrote: > > Hi, guys > > As Weex is created by a group of Chinese developers, and there are plenty of > Chinese users / contributors for weex project and most Github issues of weex > https://github.com/apache/incubator-weex/issues > <https://github.com/apache/incubator-weex/issues> are Chinese too. It’s > difficult to get our users in China involved in the community, as written > English in this mailing list is a challenge for many Chinese-speaking users. > > Is it necessary to create a Chinese mailing list to get more people speaking > Chinese involved? > What’s common rule for official language used in Apache project’s community, > English only? Or bilingual community is also fine.
Re: prerender discuss
Do you know this guy ? https://cwiki.apache.org/confluence/display/~jinjiang Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Jan 25, 2019 at 12:13 PM 申远 wrote: > > It seems like a great tool, how do apply for admin right? > > > 在 2019年1月25日，08:05，Willem Jiang 写道： > > > > +1 to use the Confluence for the design proposal discussion. > > FYI, we just open a whitelist to the user to have the write access > > right to avoid the spam. > > You can add the user here with below link[1], if you have the admin right. > > > > [1]https://cwiki.apache.org/confluence/spaces/spacepermissions.action?key=WEEX > > > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Thu, Jan 24, 2019 at 6:53 PM Myrle Krantz wrote: > >> > >> On Thu, Jan 24, 2019 at 4:09 AM 申远 wrote: > >> > >>> Thanks. > >>> > >>> There are two types of document for weex now > >>> API/FAQ documents, which we hosted it in another git repos. > >>> https://github.com/apache/incubator-weex-site/ < > >>> https://github.com/apache/incubator-weex-site/> > >>> System design documents, which is the case happening here. > >>> > >>> There is no suitable place to write system design documents now. Is there > >>> any advice or where will other Apache project host their system design > >>> documents. > >>> > >> > >> Everyone makes their own decisions, but many projects use Confluence for > >> this purpose. There are draw.io and Gliffy integrations which can both be > >> used to collaboratively edit design proposals. > >> > >> For example: https://cwiki.apache.org/confluence/display/FINERACT > >> > >> You already have: https://cwiki.apache.org/confluence/display/WEEX but the > >> permissions are very restrictive. > >> > >> Would this be useful to you? Should we look into making the WEEX > >> confluence space a bit more open? > >> > >> Best Regards, > >> Myrle >
Re: prerender discuss
+1 to use the Confluence for the design proposal discussion. FYI, we just open a whitelist to the user to have the write access right to avoid the spam. You can add the user here with below link[1], if you have the admin right. [1]https://cwiki.apache.org/confluence/spaces/spacepermissions.action?key=WEEX Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Thu, Jan 24, 2019 at 6:53 PM Myrle Krantz wrote: > > On Thu, Jan 24, 2019 at 4:09 AM 申远 wrote: > > > Thanks. > > > > There are two types of document for weex now > > API/FAQ documents, which we hosted it in another git repos. > > https://github.com/apache/incubator-weex-site/ < > > https://github.com/apache/incubator-weex-site/> > > System design documents, which is the case happening here. > > > > There is no suitable place to write system design documents now. Is there > > any advice or where will other Apache project host their system design > > documents. > > > > Everyone makes their own decisions, but many projects use Confluence for > this purpose. There are draw.io and Gliffy integrations which can both be > used to collaboratively edit design proposals. > > For example: https://cwiki.apache.org/confluence/display/FINERACT > > You already have: https://cwiki.apache.org/confluence/display/WEEX but the > permissions are very restrictive. > > Would this be useful to you? Should we look into making the WEEX > confluence space a bit more open? > > Best Regards, > Myrle
Fwd: Official releases vs unreleased code
Hi Team， I'm not sure if you are aware the official release and unreleased code in Apache Incubator. Please take some time read through the code and let me know what you think. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem -- Forwarded message - From: Justin Mclean Date: Sun, Jan 6, 2019 at 7:21 AM Subject: Official releases vs unreleased code To: Hi, Over the last few months I’ve run into 1/2 dozen podlings who are making and promoting releases to the wider community that contain unreleased code, and I’m a little surprised that they were unaware that this is not allowed. This also has come up in feedback received from the exit questionnaire. In the release policy [3] it clearly states: "Projects MUST direct outsiders towards official releases rather than raw source repositories, nightly builds, snapshots, release candidates, or any other similar packages.” This has been discussed many times but these two legal JIRAs [1][2] spell it out quite clearly. And while these tickets refer to docker the same applies to any distribution mechanism. In short “It is appropriate to distribute official releases through downstream channels, but inappropriate to distribute unreleased materials through them.” So if your projects is using docker, PiPY, GitHub releases, npm or any other ways of distribution please make sure that the wider community is only pointed at official release and the best way to do this is not to publish unreleased code on those platforms. Ask yourself is someone outside of the project likely to use this and if the answer is yes then reconsider how you are using that distribution channel and make sure it only contains official releases. Thanks, Justin 1. https://issues.apache.org/jira/browse/LEGAL-270 2. https://issues.apache.org/jira/browse/LEGAL-427 3. http://www.apache.org/legal/release-policy.html#publication - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Weekly beta release of 20181217
As we don't vote this release, it should be a snapshot deployment, not a release. For the Apache release, we need to go through the PPMC vote and IPMC vote. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Mon, Dec 17, 2018 at 3:50 PM 申远 wrote: > > Hi, all > > As discussed early, weex will publish a weekly beta release every Thursday > or Friday. Well, the first weekly beta release is build on 17th, Dec with > the following content. > > The weekly beta release version for this week is *0.20.3.0-beta*, one can > checkout this version from JCenter(Android), CocoaPods(iOS) or Github if > you prefer source code. > > ChangeLog > Android Feature > >- Support direction:rtl > - For international useage, support direction:rtl > <https://developer.mozilla.org/en-US/docs/Web/CSS/direction> > - Pull Request: https://github.com/apache/incubator-weex/pull/1664 >- Support richtext component > - Support richtext component richtext > <http://weex-project.io/cn/references/components/richtext.html> > - Pull Request: https://github.com/apache/incubator-weex/pull/1796 >- Performance optimization(init) > - rm useless log && reduce reflection > - Pull Request:https://github.com/apache/incubator-weex/pull/1844 >- rm useless code of WXInstanceExceptionRecord > - Pull Request：https://github.com/apache/incubator-weex/pull/1606 > > Bugfix > >- Emoji not show on Android 9.0(init) > - Emoji not show on Android 9.0(init) > - Pull Request: > https://github.com/apache/incubator-weex/pull/1804/files >- Support ontouch event on scroller component > - Pull Request: https://github.com/apache/incubator-weex/pull/1896 >- Fix NPE && No such Element Exception > - Pull Request: https://github.com/apache/incubator-weex/pull/1896 >- ignore fixed element for interactionTime > - Pull Request：https://github.com/apache/incubator-weex/pull/1900 > > iOSBugfix > >- Forbid adjustment of safeArea by system for cycle slider component. > - https://github.com/apache/incubator-weex/pull/1780 >- Fix dead-lock if subclass of WXListComponent is registered to WeexSDK. > - https://github.com/apache/incubator-weex/pull/1790 >- Podspec use libc++ by default. >- Release jscontext in bridge thread to avoid main thread deadlock. > - https://github.com/apache/incubator-weex/pull/1822 >- Fix multicontext recreate. > - https://github.com/apache/incubator-weex/pull/1818 >- Fix image load > - https://github.com/apache/incubator-weex/pull/1795 >- Fix crash when multithread accessing setCustomEnvironment and >customEnvironment of WXSDKEngine. > - https://github.com/apache/incubator-weex/pull/1875 >- Fix remove active pseudo class doesn't work. > - https://github.com/apache/incubator-weex/pull/1854 >- Fix css style width & height set to 0, but doesn't relayout. > - https://github.com/apache/incubator-weex/pull/1848 >- When navigation ishidden, the weexinstance will relayout, it should >modify WXRootView's frame, in same case it does't not work because of the >execute sequence. > - Pull Reuqest:https://github.com/apache/incubator-weex/pull/1901 > > Features > >- Support RTL layout direction. > - Pull Request: https://github.com/apache/incubator-weex/pull/1664 >- Add completion callback for registerService. > - Pull Request: https://github.com/apache/incubator-weex/pull/1776 >- Support richtext component > - Support richtext component. > - Pull Request: https://github.com/apache/incubator-weex/pull/1799 >- Add a feature to control the offset of list attach to bottom. > - Pull Request：https://github.com/apache/incubator-weex/pull/1813 >- supprot devtool show the new performance info > - Pull Request : https://github.com/apache/incubator-weex/pull/1751 >- Add script section in opcode file > - Pull Request：https://github.com/apache/incubator-weex/pull/1827 >- Animation of slider on iOS can be forbidden > - Pull Request: https://github.com/apache/incubator-weex/pull/1849 >- Add upriseOffset attribute for edit component to control uprise offset >triggered by keyboard. > - Pull Request: https://github.com/apache/incubator-weex/pull/1893 > > > -- > > > Best regards, > > York Shen
Re: New committer : Wang Qianyuan
Welcome aboard Qianyuan！ Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Mon, Dec 10, 2018 at 12:10 PM shihan zheng wrote: > > The Project Management Committee (PMC) for Apache Weex > has invited Wang Qianyuan to become a committer and we are pleased > to announce that he has accepted. > > We look forward to Wang Qianyuan classmates making greater contributions to > the Weex community. > > Being a committer enables easier contribution to the > project since there is no need to go via the patch > submission process. This should enable better productivity. > Being a PMC member enables assistance with the management > and to guide the direction of the project. > -- > > Best Regards! > - > Shihan Zheng (Weex project team member )
The decision making process of Apache
Hi Team， We started some vote for the new committer recently. But I think we need to know the common process of building the consensus[1] in Apache. Normally if we have some proposal, we can discuss it first to build the consensus first, then we start the vote[2]. Building the consensus is a key milestone for the community maturity model[3]. So please take some time to go through this document[4]. [1]https://community.apache.org/committers/consensusBuilding.html [2]https://community.apache.org/committers/voting.html [3]https://community.apache.org/apache-way/apache-project-maturity-model.html [4]https://blogs.apache.org/comdev/entry/how_apache_projects_use_consensus Willem Jiang Twitter: willemjiang Weibo: 姜宁willem
Re: Thank you all for welcoming me as your mentor
I highly recommend PPMC go through the document and do the evaluation yourself. It could help you find the gap. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Wed, Nov 28, 2018 at 7:24 PM Myrle Krantz wrote: > > I was wondering. Are you familiar with the maturity model? > > https://community.apache.org/apache-way/apache-project-maturity-model.html > > This is not required for graduation. But it can help you determine your > level of readiness. It can also help you find what your project might want > to improve before (or after) graduation. > > Best Regards, > Myrle > Weex Mentor
Re: [DISCUSS] Weex Project Roadmap
Normally, we need to let more audiences to know better about the roadmap. We could update the roadmap on the website and discuss about through the mailing list. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Nov 20, 2018 at 10:55 AM Dan wrote: > > I think the roadmap needs to be synchronized on the official website or > GitHub Wiki page as soon as possible. > > It’s hard to let more people know what‘s weex team doing right now in the > mailing list. > > Thanks. > Dan > > Willem Jiang 于2018年11月6日周二 下午8:35写道： > > > Do we have a wiki page for the roadmap? We could put this roadmap into > > the wiki page. > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Tue, Nov 6, 2018 at 7:36 PM Adam Feng wrote: > > > > > > Good start for roadmap discussion， are there any issues related to the > > roadmap? Everyone can join the discussion and decide how Weex will > > develop in the next versions. > > > > > > Thanks. > > > Adam Feng > > > 在 2018年11月6日 +0800 PM3:08，shihan zheng ，写道： > > > > Weex Project Roadmap > > > > > > > > This document outlines work that is currently being worked on and > > things we > > > > plan to work on next. And we hope to obtain valuable feedback from the > > > > community to help us better understand user needs and adjust our > > roadmaps. > > > > > > > > <https://yuque.antfin-inc.com/weexcore/weexcore/girgde#weexcore > > >WeexCore > > > > <https://yuque.antfin-inc.com/weexcore/weexcore/girgde#js-binding>JS > > binding > > > > <https://yuque.antfin-inc.com/weexcore/weexcore/girgde#v020>v0.20 > > > > > > > > - Will be supporting C++ timer that more efficient than platform timer > > > > module; > > > > - Feature of MessageLoop for thread interactions; > > > > > > > > <https://yuque.antfin-inc.com/weexcore/weexcore/girgde#v021>v0.21 > > > > > > > > - Using javaScriptCore standard API instead of source code > > > > - Support dom Binding for better portability and performance. > > > > > > > > <https://yuque.antfin-inc.com/weexcore/weexcore/girgde#layout>Layout > > > > <https://yuque.antfin-inc.com/weexcore/weexcore/girgde#v020-1>v0.20 > > > > > > > > - Add test infrastructure for layout engine. > > > > - Support direction:RTL and minor bugfix. > > > > > > > > <https://yuque.antfin-inc.com/weexcore/weexcore/girgde#v021-1>v0.21 > > > > > > > > - Add enough test cases to cover layout engine. > > > > > > > > <https://yuque.antfin-inc.com/weexcore/weexcore/girgde#render>Render > > > > <https://yuque.antfin-inc.com/weexcore/weexcore/girgde#v020-2>v0.20 > > > > > > > > - Support renderPage life cycle management and resource management. > > > > - Support render task schedule. > > > > > > > > <https://yuque.antfin-inc.com/weexcore/weexcore/girgde#tools>tools > > > > > > > > This year, the weex-toolkit will release version 2.0.0, it mainly > > provides > > > > the following new features: > > > > > > > > - Flawless installation and upgrade experience. > > > > - Better unit & functional testing support. > > > > - Visual Studio Code extensions with support for build/run/debug. > > > > - Split into multiple packages that can be reused on the Node-side > > > > program. > > > > > > > > Also, there will be some features and optimization for the submodules, > > such > > > > as weex-debugger, weex-pack and so on. > > > > > > > > All the schedules can be viewed on the milestones > > > > <https://github.com/weexteam/weex-toolkit/milestones>. > > > > > > > > -- > > > > > > > > Best Regards! > > > > - > > > > Shihan Zheng (Weex project team member ) > >
Re: [NEW MENTOR REQUIRED] Apache Weex (incubating)
There could be some new IPMC member onboard recently. It could be good opportunity for Weex to look for new mentor. I appreciate any help you can provide. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Mon, Nov 19, 2018 at 7:54 PM Adam Feng wrote: > > +1 > > We would be grateful to anyone who can volunteer time to help. A few of us > are still > new to the ASF processes and need guidance. > > > Thanks. > Adam Feng > 在 2018年11月14日 +0800 AM11:03，Hanks Zhang ，写道： > > +1. > > > > I also think Weex needs more guidance from more mentors, they can give > > advice from different perspectives. On the other hand, most PPMC and > > committers of Weex are Chinese, we wish Weex can absorb ideas form > > more world-wide developers from different cultures. Looking forward to your > > opinions. > > > > Best Regards, > > Hanks Zhang > > > > Jonathan Dong 于2018年11月12日周一 下午7:32写道： > > > > > Hi Folks, > > > > > > I’m writing to seek for new motivated mentors for the Apache Weex > > > (incubating) project, to drive and mentor the community and project to > > > graduate. > > > > > > Weex is a project aims to build high-performance mobile applications by > > > leveraging mobile web development experience. It was accepted into the > > > Apache Incubator since Nov. 30, 2016, there are 2 Apache releases during > > > the incubation period, and 11 PPMC and 3 committers by now. We have been > > > struggling with the active mentorship which could lead us through the > > > podling process and push the project to the graduation, for now we only > > > have one active mentor Willem Jiang (who helps a lot to grow the community > > > as well as the processes, thanks), and we believe it’s the right time to > > > invite one more mentor or two to offload some mentoring duty from Willem > > > and push us through the graduation. > > > > > > If you are interested, please let use know at > > > dev@weex.incubator.apache.org. Looking forward to your guidance. > > > > > > Cheers, > > > > > > Jonathan Dong > > >
Re: [ANOUNCE] New PPMC member: Jonathan Dong
Hi Jonathan, Congratulation! FYI, I just added the Jonathan Dong into PPMC[1] [1]https://whimsy.apache.org/roster/ppmc/weex Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Nov 9, 2018 at 3:12 PM Adam Feng wrote: > > Hi, all, > > I am pleased to announce that Jonathan Dong has been voted as a new Weex > PPMC member. > > He has done a great job with Weex community in the past days , please join > me to say congratulations to Jonathan! > > > Thanks. > Adam Feng
Re: [DISCUSS] Weex Project Roadmap
Do we have a wiki page for the roadmap? We could put this roadmap into the wiki page. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Nov 6, 2018 at 7:36 PM Adam Feng wrote: > > Good start for roadmap discussion， are there any issues related to the > roadmap? Everyone can join the discussion and decide how Weex will develop > in the next versions. > > Thanks. > Adam Feng > 在 2018年11月6日 +0800 PM3:08，shihan zheng ，写道： > > Weex Project Roadmap > > > > This document outlines work that is currently being worked on and things we > > plan to work on next. And we hope to obtain valuable feedback from the > > community to help us better understand user needs and adjust our roadmaps. > > > > <https://yuque.antfin-inc.com/weexcore/weexcore/girgde#weexcore>WeexCore > > <https://yuque.antfin-inc.com/weexcore/weexcore/girgde#js-binding>JS binding > > <https://yuque.antfin-inc.com/weexcore/weexcore/girgde#v020>v0.20 > > > > - Will be supporting C++ timer that more efficient than platform timer > > module; > > - Feature of MessageLoop for thread interactions; > > > > <https://yuque.antfin-inc.com/weexcore/weexcore/girgde#v021>v0.21 > > > > - Using javaScriptCore standard API instead of source code > > - Support dom Binding for better portability and performance. > > > > <https://yuque.antfin-inc.com/weexcore/weexcore/girgde#layout>Layout > > <https://yuque.antfin-inc.com/weexcore/weexcore/girgde#v020-1>v0.20 > > > > - Add test infrastructure for layout engine. > > - Support direction:RTL and minor bugfix. > > > > <https://yuque.antfin-inc.com/weexcore/weexcore/girgde#v021-1>v0.21 > > > > - Add enough test cases to cover layout engine. > > > > <https://yuque.antfin-inc.com/weexcore/weexcore/girgde#render>Render > > <https://yuque.antfin-inc.com/weexcore/weexcore/girgde#v020-2>v0.20 > > > > - Support renderPage life cycle management and resource management. > > - Support render task schedule. > > > > <https://yuque.antfin-inc.com/weexcore/weexcore/girgde#tools>tools > > > > This year, the weex-toolkit will release version 2.0.0, it mainly provides > > the following new features: > > > > - Flawless installation and upgrade experience. > > - Better unit & functional testing support. > > - Visual Studio Code extensions with support for build/run/debug. > > - Split into multiple packages that can be reused on the Node-side > > program. > > > > Also, there will be some features and optimization for the submodules, such > > as weex-debugger, weex-pack and so on. > > > > All the schedules can be viewed on the milestones > > <https://github.com/weexteam/weex-toolkit/milestones>. > > > > -- > > > > Best Regards! > > - > > Shihan Zheng (Weex project team member )
Re: [DISCUSS] The Content of Weex Podling Report
Hi Hanks, Could you update the report on this page[1]? We need to finish the podling report this Wednesday. [1]https://wiki.apache.org/incubator/November2018 Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Oct 30, 2018 at 7:25 PM Hanks Zhang wrote: > > Here is the draft of the podling report, please share your opinions if you > found something improper. > > > Weex > > Weex is a framework for building high-performance mobile apps with modern > web development experience. > > Weex has been incubating since 2016-11-30. > > Three most important issues to address in the move towards graduation: > > 1. Propose more open discussions in the mailing list, improve the > activity. > 2. Establish a regular release schedule and a clear roadmap. > 3. Develop more committers and PPMCs, stay focused on the community. > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware > of? > > Apologize for missing the last podling report. > > The main reason for it is the PPMC and committers does not pay enough > attention in the mailing list. We have realized this mistake and decide to > take more efforts on building the community. > > Here are some actions: > 1. Hold meetings regularly among core contributors of Weex and publish > the summary to the mailing list. > 2. Take turns on duty for each release and podling reports. > > How has the community developed since the last report? > > * Released a new version (v0.19.0) of Weex. > https://lists.apache.org/thread.html/3e7bfe9e3f79a8d4b46dbe668bfb559e4e539bd7c5f4143107e6af00@%3Cgeneral.incubator.apache.org%3E > * Hold a meetup in Shanghai at 2018-09-15, discussed technologies about > the new render pipeline and interactive experience of Weex. > * Migrate the source code from (git-wip-us.apache.org) to ( > gitbox.apache.org) and enabled the issue panel on the GitHub. > > How has the project developed since the last report? > > * In average, more than 10 PRs or commits were merged to the main branch > each week. The Github repository now has 162 contributors (8 new since the > last > report) and 1451 forks (130 new). > * Weex has developed a new render pipeline and used it in production, but > it still needs more improvement. > * A more CSS-friendly Weex Renderer is under discussing, it can fix many > cross-platform inconsistency problems. > > How would you assess the podling's maturity? Please feel free to add your > own commentary. > > [ ] Initial setup > [ ] Working towards the first release > [x] Community building > [x] Nearing graduation > [ ] Other: > > Date of the last release: > > 2018-10-08 (v0.19.0) > > When were the last committers or PPMC members elected? > > New PPMC member: jondong (Jonathan Dong) > > Signed-off-by: > > IPMC/Shepherd notes: > > -- > > By the way, I am not the PPMC member yet and not authorized to edit this > page: https://wiki.apache.org/incubator/September2018 > I wish someone could help me to update this content to the report page. > > Best Regards, > Hanks Zhang
Re: [DISCUSS] The Content of Weex Podling Report
"It's not happened if it is not on the mailing list. " We leverage the mail to talk to the developer and community. And we make the consensus decision through the mail. I think we need stay a bit longer in the incubator to let all the committer and PPMC member knows about it. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Oct 30, 2018 at 7:25 PM Hanks Zhang wrote: > > Here is the draft of the podling report, please share your opinions if you > found something improper. > > > Weex > > Weex is a framework for building high-performance mobile apps with modern > web development experience. > > Weex has been incubating since 2016-11-30. > > Three most important issues to address in the move towards graduation: > > 1. Propose more open discussions in the mailing list, improve the > activity. > 2. Establish a regular release schedule and a clear roadmap. > 3. Develop more committers and PPMCs, stay focused on the community. > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware > of? > > Apologize for missing the last podling report. > > The main reason for it is the PPMC and committers does not pay enough > attention in the mailing list. We have realized this mistake and decide to > take more efforts on building the community. > > Here are some actions: > 1. Hold meetings regularly among core contributors of Weex and publish > the summary to the mailing list. > 2. Take turns on duty for each release and podling reports. > > How has the community developed since the last report? > > * Released a new version (v0.19.0) of Weex. > https://lists.apache.org/thread.html/3e7bfe9e3f79a8d4b46dbe668bfb559e4e539bd7c5f4143107e6af00@%3Cgeneral.incubator.apache.org%3E > * Hold a meetup in Shanghai at 2018-09-15, discussed technologies about > the new render pipeline and interactive experience of Weex. > * Migrate the source code from (git-wip-us.apache.org) to ( > gitbox.apache.org) and enabled the issue panel on the GitHub. > > How has the project developed since the last report? > > * In average, more than 10 PRs or commits were merged to the main branch > each week. The Github repository now has 162 contributors (8 new since the > last > report) and 1451 forks (130 new). > * Weex has developed a new render pipeline and used it in production, but > it still needs more improvement. > * A more CSS-friendly Weex Renderer is under discussing, it can fix many > cross-platform inconsistency problems. > > How would you assess the podling's maturity? Please feel free to add your > own commentary. > > [ ] Initial setup > [ ] Working towards the first release > [x] Community building > [x] Nearing graduation > [ ] Other: > > Date of the last release: > > 2018-10-08 (v0.19.0) > > When were the last committers or PPMC members elected? > > New PPMC member: jondong (Jonathan Dong) > > Signed-off-by: > > IPMC/Shepherd notes: > > -- > > By the way, I am not the PPMC member yet and not authorized to edit this > page: https://wiki.apache.org/incubator/September2018 > I wish someone could help me to update this content to the report page. > > Best Regards, > Hanks Zhang
Re: [DISCUSS] The Content of Weex Podling Report
We need to make sure all the PPMC monitors the dev mailing list. The Report request mail were send the mailing list serval time. It's hard to miss it if we keep an eye on the mailing list. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Oct 30, 2018 at 4:31 PM Adam Feng wrote: > > As we failed to report last month, we were asked to answer these questions > for the board: > - Why this report was missed > - Why requests for the report to the dev and private mailing lists were > ignored > - What you are going to do to educate your committers about why the report is > important (see the reply on dev list) > - What will be done to improve this and make sure it doesn't happen again. > > > Here is my proposal to avoid missing podling report again: > 1. Add more PPMCs as there’re not enough members in PPMC who are taking > notice of the private@ and dev@ mailing list. > 2. Make a reporting schedule for next year, try to involve main committers to > participate in the reporting rather than same PPMC every time. For example, > this quarter is Hanks and next quarter is Jonathan, thus tell all the > committers what a podling report is and why it is important to our community. > > > Thanks. > Adam Feng > 在 2018年10月30日 +0800 AM11:23，Hanks Zhang ，写道： > > Hi, Weex Community > > > > The board meeting of Apache is near, we should finish the IPMC report this > > week. > > > > Here is the report outline, there are many questions we should answer. I > > will prepare the most of them, please feel free to add your comments. > > > > > > > > Weex > > > > Weex is a framework for building high-performance mobile apps with modern > > web development experience. > > > > Weex has been incubating since 2016-11-30. > > > > Three most important issues to address in the move towards graduation: > > > > 1. > > 2. > > 3. > > > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware > > of? > > > > How has the community developed since the last report? > > > > How has the project developed since the last report? > > > > How would you assess the podling's maturity? Please feel free to add your > > own commentary. > > > > [ ] Initial setup > > [ ] Working towards the first release > > [x] Community building > > [ ] Nearing graduation > > [ ] Other: > > > > Date of the last release: > > > > 2018-10-08 (v0.19.0) > > > > When were the last committers or PPMC members elected? > > > > Have your mentors been helpful and responsive or are things falling > > through the cracks? In the latter case, please list any open issues > > that need to be addressed. > > > > Signed-off-by: > > > > IPMC/Shepherd notes: > > > > - > > > > Best Regards, > > Hanks
Re: Podling Report Reminder - November 2018
As we missed the last month IPMC report. Please prepare your IPMC report this week. We can start the discussion on the mailing list first. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Thu, Oct 25, 2018 at 5:34 AM wrote: > > 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, 21 November 2018, 10:30 am PDT. > The report for your podling will form a part of the Incubator PMC > report. The Incubator PMC requires your report to be submitted 2 weeks > before the board meeting, to allow sufficient time for review and > submission (Wed, November 07). > > Please submit your report with sufficient time to allow the Incubator > PMC, and subsequently board members to review and digest. Again, the > very latest you should submit your report is 2 weeks prior to the board > meeting. > > Candidate names should not be made public before people are actually > elected, so please do not include the names of potential committers or > PPMC members in your report. > > Thanks, > > The Apache Incubator PMC > > Submitting your Report > > -- > > Your report should contain the following: > > * Your project name > * A brief description of your project, which assumes no knowledge of > the project or necessarily of its field > * A list of the three most important issues to address in the move > towards graduation. > * Any issues that the Incubator PMC or ASF Board might wish/need to be > aware of > * How has the community developed since the last report > * How has the project developed since the last report. > * How does the podling rate their own maturity. > > This should be appended to the Incubator Wiki page at: > > https://wiki.apache.org/incubator/November2018 > > Note: This is manually populated. You may need to wait a little before > this page is created from a template. > > Mentors > --- > > Mentors should review reports for their project(s) and sign them off on > the Incubator wiki page. Signing off reports shows that you are > following the project - projects that are not signed may raise alarms > for the Incubator PMC. > > Incubator PMC
Re: Moving the github related notification mail to other mailing list
FYI, you can fill a JIRA[1] to send the github mails to the notification mailing list. [1]https://issues.apache.org/jira/projects/INFRA/issues Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Mon, Oct 8, 2018 at 11:04 AM Hanks Zhang wrote: > > Agree. > > Actually, I already create a custom filter to separate GitHub notifications > from normal discussions in my own inbox. > > Regards, > Hanks > > Jonathan Dong 于2018年10月7日周日 上午11:22写道： > > > Agree, commits channel should be a better place for GitHub auto generated > > mails. > > > > Cheers, > > Jonathan Dong > > > > From: Adam Feng > > Sent: Sunday, October 7, 2018 11:08:29 AM > > To: dev; dev@weex.incubator.apache.org > > Subject: Re: Moving the github related notification mail to other mailing > > list > > > > Agree, I suggest move all the Github notifications to > > comm...@weex.apache.org > > > > The email volume from GitHub might lead to dev@ list being ignored. > > > > Thanks. > > Adam Feng > > 在 2018年10月7日 +0800 AM9:42，Willem Jiang ，写道： > > > Hi， > > > > > > As there are lot of traffic from the github in the dev, it's hard for > > > us to checkout the other mail in the dev@weex. > > > Can we move the git related notification to another mailing list? > > > > > > Any thoughts? > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > >
Moving the github related notification mail to other mailing list
Hi， As there are lot of traffic from the github in the dev, it's hard for us to checkout the other mail in the dev@weex. Can we move the git related notification to another mailing list? Any thoughts? Willem Jiang Twitter: willemjiang Weibo: 姜宁willem
Apache project meetup in ShangHai Oct 13th
Hi Apache ServiceComb will hold a meetup in ShangHai Oct 13th, 1 PM to 4 PM, by inviting three Apache members (Roman Shaposhik，Justin Mclean， Craig Russell, Willem Jiang) and the apache projects committer in China. We hold this meetup can help Apache projects to know each other in China. As there are lot of Apache project committers live around east China, we can leverage this opportunity to let Apache know better about the committers in China and give us some advice to build up health community. The discussion topic of meetup could be: How to be the TLP of ASF? How can we help ASF know better about China? How can we help more Chinese know better about ASF? If you are interested about this meetup, please drop an email to ningjiang AT apache.org with the information of your name, phone number and the project name before Oct 8th 12 PM. We will send you detail information of the meetup later. Please forward the mail to your friend who may interest about this event. Regards, Willem Jiang Twitter: willemjiang Weibo: 姜宁willem
Re: Participate in the community
Any contribution are welcome in Apache. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Thu, Sep 13, 2018 at 10:42 AM Paul Adams wrote: > > Hi, due to work obligations, I have been finding it hard to contribute. > Hopefully I will have time in the near future to resume work on the English > docs. > > On Wed, Sep 12, 2018, 9:16 PM Rex <623243...@qq.com> wrote: > > > Participate in the community
Re: [VOTE]- Release Apache Weex (Incubating) 0.19.0 [RC4]
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]: Release Apache Weex (Incubating) 0.19.0 [RC2]
Much better now. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Jul 13, 2018 at 1:44 PM, 莫绪旻 wrote: > Hi, Willem > > The version code of chromium is v66.0.3344.2 , I have updated the LICENSE > file and this is the address of Pull Request : https://github.com/apache/ > incubator-weex/pull/1325/files > > > Miomin Mo > > > -- 原始邮件 -- > *发件人:* "willem.jiang"; > *发送时间:* 2018年7月12日(星期四) 晚上10:44 > *收件人:* "dev"; > *主题:* Re: [VOTE]: Release Apache Weex (Incubating) 0.19.0 [RC2] > > For the LICENSE file, we need to specify the version of chromium, the > License information could be different with different version. > > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Thu, Jul 12, 2018 at 9:26 PM, Adam Feng wrote: > > > Hi, Willem > > > > Thanks for your kind advices. > > > > We have updated the LICENSE file [1] according to [2]，I have checked > every > > file and directory( android/sdk/ directory will be updated to > android_sdk/ > > when released) to make sure it is updated correctly and NO ASF License on > > the top of third party code. > > Please have a check again, If everything is OK，I’ll call another VOTE and > > every PPMC member SHOULD specify what they checked and what to resolve. > > > > [1] https://github.com/apache/incubator-weex/blob/release/LICENSE > > [2] http://apache.org/dev/licensing-howto.html#permissive-deps > > > > Thanks. > > Adam Feng > > 在 2018年6月30日 +0800 PM5:30，Willem Jiang ，写道： > > > Please don't just add +1 on the vote. > > > As the PPMC voting we need to specify what we checked and what kind of > > > issue we still need to resolve. > > > > > > I just checked License file, it looks like there are some file > directory > > is > > > changed and we need to updated. > > > And we are not supposed just copy the License Header to the License > file, > > > please check this section[1] for more information. > > > Most of time you are not supposed to add the ASF License on the top of > > > third party code.[2] > > > > > > [1]http://apache.org/dev/licensing-howto.html#permissive-deps > > > [2]https://www.apache.org/legal/src-headers.html#3party > > > > > > > > > > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > > On Thu, Jun 28, 2018 at 6:11 PM, 宁栗 wrote: > > > > > > > +1 > > > > Thank you for the release. > > > > > > > > 2018-06-27 11:13 GMT+08:00 Jason Xu : > > > > > > > > > +1 > > > > > Thank you for the release. > > > > > > > > > > 2018-06-27 8:02 GMT+08:00 方曦(千之) : > > > > > > > > > > > +1. > > > > > > Thank you for the release work. > > > > > > > > > > > > 发自我的 iPhone > > > > > > > > > > > > > 在 2018年6月26日，21:32，申远 写道： > > > > > > > > > > > > > > +1 > > > > > > > Thank you for the release > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Thanks. > > > > > Jason Xu > > > > > > > > > > > > >
Re: [VOTE]: Release Apache Weex (Incubating) 0.19.0 [RC2]
For the LICENSE file, we need to specify the version of chromium, the License information could be different with different version. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Thu, Jul 12, 2018 at 9:26 PM, Adam Feng wrote: > Hi, Willem > > Thanks for your kind advices. > > We have updated the LICENSE file [1] according to [2]，I have checked every > file and directory( android/sdk/ directory will be updated to android_sdk/ > when released) to make sure it is updated correctly and NO ASF License on > the top of third party code. > Please have a check again, If everything is OK，I’ll call another VOTE and > every PPMC member SHOULD specify what they checked and what to resolve. > > [1] https://github.com/apache/incubator-weex/blob/release/LICENSE > [2] http://apache.org/dev/licensing-howto.html#permissive-deps > > Thanks. > Adam Feng > 在 2018年6月30日 +0800 PM5:30，Willem Jiang ，写道： > > Please don't just add +1 on the vote. > > As the PPMC voting we need to specify what we checked and what kind of > > issue we still need to resolve. > > > > I just checked License file, it looks like there are some file directory > is > > changed and we need to updated. > > And we are not supposed just copy the License Header to the License file, > > please check this section[1] for more information. > > Most of time you are not supposed to add the ASF License on the top of > > third party code.[2] > > > > [1]http://apache.org/dev/licensing-howto.html#permissive-deps > > [2]https://www.apache.org/legal/src-headers.html#3party > > > > > > > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Thu, Jun 28, 2018 at 6:11 PM, 宁栗 wrote: > > > > > +1 > > > Thank you for the release. > > > > > > 2018-06-27 11:13 GMT+08:00 Jason Xu : > > > > > > > +1 > > > > Thank you for the release. > > > > > > > > 2018-06-27 8:02 GMT+08:00 方曦(千之) : > > > > > > > > > +1. > > > > > Thank you for the release work. > > > > > > > > > > 发自我的 iPhone > > > > > > > > > > > 在 2018年6月26日，21:32，申远 写道： > > > > > > > > > > > > +1 > > > > > > Thank you for the release > > > > > > > > > > > > > > > > > > > > > -- > > > > Thanks. > > > > Jason Xu > > > > > > > >
Re: Podling Report Reminder - July 2018
Hi, The Podling report is due by end of today. Please send your report ASAP. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Thu, Jun 28, 2018 at 5:41 AM, wrote: > 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, 18 July 2018, 10:30 am PDT. > The report for your podling will form a part of the Incubator PMC > report. The Incubator PMC requires your report to be submitted 2 weeks > before the board meeting, to allow sufficient time for review and > submission (Wed, July 04). > > Please submit your report with sufficient time to allow the Incubator > PMC, and subsequently board members to review and digest. Again, the > very latest you should submit your report is 2 weeks prior to the board > meeting. > > Candidate names should not be made public before people are actually > elected, so please do not include the names of potential committers or > PPMC members in your report. > > Thanks, > > The Apache Incubator PMC > > Submitting your Report > > -- > > Your report should contain the following: > > * Your project name > * A brief description of your project, which assumes no knowledge of > the project or necessarily of its field > * A list of the three most important issues to address in the move > towards graduation. > * Any issues that the Incubator PMC or ASF Board might wish/need to be > aware of > * How has the community developed since the last report > * How has the project developed since the last report. > * How does the podling rate their own maturity. > > This should be appended to the Incubator Wiki page at: > > https://wiki.apache.org/incubator/July2018 > > Note: This is manually populated. You may need to wait a little before > this page is created from a template. > > Mentors > --- > > Mentors should review reports for their project(s) and sign them off on > the Incubator wiki page. Signing off reports shows that you are > following the project - projects that are not signed may raise alarms > for the Incubator PMC. > > Incubator PMC >
Re: Suggestion on moving Weex Code Repo to Gitbox
+1 to use the Gitbox. With Gitbox, we can just work as we do in Github directly. BTW, this mail thread is just for discussion[1]. we need to start a vote for it[2]. [1]https://community.apache.org/committers/decisionMaking.html [2]https://community.apache.org/committers/voting.html Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Thu, Jun 28, 2018 at 6:13 PM, 申远 wrote: > Hi, Folks > > Apache Infa now provided us read/write access directly to weex repos on > Github through a utility called Gitbox( https://gitbox.apache.org/). PMCs > have the option to embrace the Gitbox and using Github UI to review code, > merge PRs. > > For now, there are plenty of Apache projects hosted by GItbox( > https://gitbox.apache.org/repos/asf). Personally, I am fascinated by the > idea of directly access to Github, which will make committers life far more > easy. > > I'd like to suggest that we host Apache Weex ( > https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git) on Gitbox to > enable read/write access of Repos on Github. > -- > > > Best regards, > > York Shen >
Re: [VOTE]: Release Apache Weex (Incubating) 0.19.0 [RC2]
Please don't just add +1 on the vote. As the PPMC voting we need to specify what we checked and what kind of issue we still need to resolve. I just checked License file, it looks like there are some file directory is changed and we need to updated. And we are not supposed just copy the License Header to the License file, please check this section[1] for more information. Most of time you are not supposed to add the ASF License on the top of third party code.[2] [1]http://apache.org/dev/licensing-howto.html#permissive-deps [2]https://www.apache.org/legal/src-headers.html#3party Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Thu, Jun 28, 2018 at 6:11 PM, 宁栗 wrote: > +1 > Thank you for the release. > > 2018-06-27 11:13 GMT+08:00 Jason Xu : > > > +1 > > Thank you for the release. > > > > 2018-06-27 8:02 GMT+08:00 方曦(千之) : > > > > > +1. > > > Thank you for the release work. > > > > > > 发自我的 iPhone > > > > > > > 在 2018年6月26日，21:32，申远 写道： > > > > > > > > +1 > > > > Thank you for the release > > > > > > > > > > > -- > > Thanks. > > Jason Xu > > >
Re: [DISCUSS] Forward to our second Apache release (0.19)
Current some incubator podling projects just do the source release. I guess we can do it step by step, to address the source license issue first. Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Wed, May 23, 2018 at 10:56 AM, Adam Feng <cxfe...@gmail.com> wrote: > Thanks, It looks much clearer to me. > > So can I ask if it is OK to only provide the source release in Apache？ > > Weex, by its nature, has a complicated codebase, it includes > iOS/Android/Web/JS code, and the environment required to build Weex > includes NodeJS/JDK/Android SDK/Gradle/Xcode, it is far from a java project > with a jar output. I suppose it’s difficult for us to release Weex in a > single binary. > > If it is OK, can we provide the source release using the current version > of POSSIBLE-NOTICES-FOR-BIN-DIST? > > In any case, I will go through the POSSIBLE-NOTICES-FOR-BIN-DIST later > and check every dependency to see if some additional notice is really > required. > > Thanks. > Adam Feng > > On 23 May 2018, 9:29 AM +0800, Willem Jiang <willem.ji...@gmail.com>, > wrote: > > Hi, > > > > For the source release, the NOTICE file looks good. > > I just checked the release you did last year, it looks like you only > > provide the source release, so it's OK. > > But for the POSSIBLE-NOTICES-FOR-BIN-DIST, it looks you put the all the > > third party License information into the NOTICE file. > > It's a common mistake. NOTICE is not supposed to hold the LICENSE > > information, if you are planing to do the binary release, you need to > > provide another version of License to hold the third party license > > information there. > > > > > > > > > > Willem Jiang > > > > Blog: http://willemjiang.blogspot.com (English) > > http://jnn.iteye.com (Chinese) > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Tue, May 22, 2018 at 11:06 PM, Adam Feng <cxfe...@gmail.com> wrote: > > > > > Thanks for the document, Willem. I have just read through it and have > > > some confusions here： > > > > > > > NOTICE is reserved for a certain subset of legally required > > > notifications which are not satisfied by either the text of LICENSE or > the > > > presence of licensing information embedded within the bundled > dependency. > > > Aside from Apache-licensed dependencies which supply NOTICE files of > their > > > own, it is uncommon for a dependency to require additions to NOTICE. > > > > Copyright notifications which have been relocated from source files > > > (rather than removed) must be preserved in NOTICE. However, elements > such > > > as the copyright notifications embedded within BSD and MIT licenses > need > > > not be duplicated in NOTICE -- it suffices to leave those notices in > their > > > original locations. > > > > It is important to keep NOTICE as brief and simple as possible, as > each > > > addition places a burden on downstream consumers. > > > > Do not add anything to NOTICE which is not legally required. > > > 1. I can’t figure out any special cases that we need modify NOTICE for > src > > > release, so if the LICENSE file[1] is good for the src release， will a > > > clean NOTICE[2] be OK for src release ? > > > 2. I see why the POSSIBLE-NOTICES-FOR-BIN-DIST[3] file come in the > > > mailing thread[4], it is supposed to be used in binary release, should > we > > > create another POSSIBLE-LICENSE-FOR-BIN-DIST file? For most of what's > being > > > called out in NOTICE should actually be in LICENSE, but the last Weex > > > Release[5] which had passed voting was not including such file. > > > > > > Please give your comment, thanks! > > > > > > > > > [1] https://git-wip-us.apache.org/repos/asf?p=incubator- > > > weex.git;a=blob_plain;f=LICENSE;hb=f44a8fd5d6e0d9fb2292f921ebbef8 > > > 424563f93d > > > [2] https://git-wip-us.apache.org/repos/asf?p=incubator- > > > weex.git;a=blob_plain;f=NOTICE;hb=f44a8fd5d6e0d9fb2292f921eb > bef8424563f93d > > > [3] https://git-wip-us.apache.org/repos/asf?p=incubator- > > > weex.git;a=blob_plain;f=POSSIBLE-NOTICES-FOR-BIN-DIST;hb= > > > f44a8fd5d6e0d9fb2292f921ebbef8424563f93d > > > [4] https://lists.apache.org/thread.html/636530863af603203bb3320 > a93b3f2 > > > 4e38bbeaf8a2cacb420f6f6734@%3Cgeneral.incubator.apache.org%3E > > > [5] http://apache.org/dist/incubator/weex/0.12.0-incubating/ >
Re: [DISCUSS] Forward to our second Apache release (0.19)
Hi, For the source release, the NOTICE file looks good. I just checked the release you did last year, it looks like you only provide the source release, so it's OK. But for the POSSIBLE-NOTICES-FOR-BIN-DIST, it looks you put the all the third party License information into the NOTICE file. It's a common mistake. NOTICE is not supposed to hold the LICENSE information, if you are planing to do the binary release, you need to provide another version of License to hold the third party license information there. Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Tue, May 22, 2018 at 11:06 PM, Adam Feng <cxfe...@gmail.com> wrote: > Thanks for the document, Willem. I have just read through it and have > some confusions here： > > > NOTICE is reserved for a certain subset of legally required > notifications which are not satisfied by either the text of LICENSE or the > presence of licensing information embedded within the bundled dependency. > Aside from Apache-licensed dependencies which supply NOTICE files of their > own, it is uncommon for a dependency to require additions to NOTICE. > > Copyright notifications which have been relocated from source files > (rather than removed) must be preserved in NOTICE. However, elements such > as the copyright notifications embedded within BSD and MIT licenses need > not be duplicated in NOTICE -- it suffices to leave those notices in their > original locations. > > It is important to keep NOTICE as brief and simple as possible, as each > addition places a burden on downstream consumers. > > Do not add anything to NOTICE which is not legally required. > 1. I can’t figure out any special cases that we need modify NOTICE for src > release, so if the LICENSE file[1] is good for the src release， will a > clean NOTICE[2] be OK for src release ? > 2. I see why the POSSIBLE-NOTICES-FOR-BIN-DIST[3] file come in the > mailing thread[4], it is supposed to be used in binary release, should we > create another POSSIBLE-LICENSE-FOR-BIN-DIST file? For most of what's being > called out in NOTICE should actually be in LICENSE, but the last Weex > Release[5] which had passed voting was not including such file. > > Please give your comment, thanks! > > > [1] https://git-wip-us.apache.org/repos/asf?p=incubator- > weex.git;a=blob_plain;f=LICENSE;hb=f44a8fd5d6e0d9fb2292f921ebbef8 > 424563f93d > [2] https://git-wip-us.apache.org/repos/asf?p=incubator- > weex.git;a=blob_plain;f=NOTICE;hb=f44a8fd5d6e0d9fb2292f921ebbef8424563f93d > [3] https://git-wip-us.apache.org/repos/asf?p=incubator- > weex.git;a=blob_plain;f=POSSIBLE-NOTICES-FOR-BIN-DIST;hb= > f44a8fd5d6e0d9fb2292f921ebbef8424563f93d > [4] https://lists.apache.org/thread.html/636530863af603203bb3320a93b3f2 > 4e38bbeaf8a2cacb420f6f6734@%3Cgeneral.incubator.apache.org%3E > [5] http://apache.org/dist/incubator/weex/0.12.0-incubating/ > > > > Thanks. > Adam Feng > > On 22 May 2018, 7:48 PM +0800, Willem Jiang <willem.ji...@gmail.com>, > wrote: > > The LICENSE file looks good for the src release, but for the NOTICE is > not > > right. > > For the binary release, you need to provide another LICENSE file. Please > go > > through the document here[1]. > > > > [1]http://www.apache.org/dev/licensing-howto.html > > > > > > Willem Jiang > > > > Blog: http://willemjiang.blogspot.com (English) > > http://jnn.iteye.com (Chinese) > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Tue, May 22, 2018 at 5:08 PM, Adam Feng <cxfe...@gmail.com> wrote: > > > > > Hi, Willem > > > > > > Thanks for reminding. > > > > > > I’ve found the License[1] and Notice[2] files in Weex, and I’ll make > > > sure that all the dependencies are declared in these files. > > > > > > Is there anything we should notice about these two files? We’d like to > > > hear your advice about release sincerely before calling a VOTE on dev@ > . > > > > > > [1] https://github.com/apache/incubator-weex/blob/master/LICENSE > > > [2] https://github.com/apache/incubator-weex/blob/master/ > > > POSSIBLE-NOTICES-FOR-BIN-DIST > > > > > > Thanks. > > > Adam Feng > > > > > > On 22 May 2018, 4:31 PM +0800, Willem Jiang <willem.ji...@gmail.com>, > > > wrote: > > > > As we need to specify the license of the bundled third party jars. > > > > Please make sure we provides two License and Notice files for source > > > > release and binary release. > > > > > > > > > > > > > > >
Re: [DISCUSS] Forward to our second Apache release (0.19)
The LICENSE file looks good for the src release, but for the NOTICE is not right. For the binary release, you need to provide another LICENSE file. Please go through the document here[1]. [1]http://www.apache.org/dev/licensing-howto.html Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Tue, May 22, 2018 at 5:08 PM, Adam Feng <cxfe...@gmail.com> wrote: > Hi, Willem > > Thanks for reminding. > > I’ve found the License[1] and Notice[2] files in Weex, and I’ll make > sure that all the dependencies are declared in these files. > > Is there anything we should notice about these two files? We’d like to > hear your advice about release sincerely before calling a VOTE on dev@. > > [1] https://github.com/apache/incubator-weex/blob/master/LICENSE > [2] https://github.com/apache/incubator-weex/blob/master/ > POSSIBLE-NOTICES-FOR-BIN-DIST > > Thanks. > Adam Feng > > On 22 May 2018, 4:31 PM +0800, Willem Jiang <willem.ji...@gmail.com>, > wrote: > > As we need to specify the license of the bundled third party jars. > > Please make sure we provides two License and Notice files for source > > release and binary release. > > > > > > > > Willem Jiang > > > > Blog: http://willemjiang.blogspot.com (English) > > http://jnn.iteye.com (Chinese) > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Tue, May 22, 2018 at 10:57 AM, Adam Feng <cxfe...@gmail.com> wrote: > > > > > Hi all, > > > > > > Since the work of replacing Facebook’s Yoga has beed done, Let's plan > our > > > second Apache release. > > > > > > I volunteer to take 'release manager' for this version (0.19), and I'll > > > figure out how to release in Apache way. > > > > > > As we haven’t released for nearly 1 year, some work needs to be > confirmed > > > before releasing： > > > > > > > > > 1. Make sure all the Yoga code have been deleted in master branch. > > > 2. Make sure no Category X[1] dependencies or Category B[1] source > code is > > > distributed. > > > 3. Make sure that NOTICE and LICENSE files are correct. > > > > > > I will start a [VOTE] about the release later this week. > > > > > > [1] https://www.apache.org/legal/resolved.html > > > > > > > > > Thanks. > > > Adam Feng > > > >
Re: [DISCUSS] Forward to our second Apache release (0.19)
As we need to specify the license of the bundled third party jars. Please make sure we provides two License and Notice files for source release and binary release. Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Tue, May 22, 2018 at 10:57 AM, Adam Feng <cxfe...@gmail.com> wrote: > Hi all, > > Since the work of replacing Facebook’s Yoga has beed done, Let's plan our > second Apache release. > > I volunteer to take 'release manager' for this version (0.19), and I'll > figure out how to release in Apache way. > > As we haven’t released for nearly 1 year, some work needs to be confirmed > before releasing： > > > 1. Make sure all the Yoga code have been deleted in master branch. > 2. Make sure no Category X[1] dependencies or Category B[1] source code is > distributed. > 3. Make sure that NOTICE and LICENSE files are correct. > > I will start a [VOTE] about the release later this week. > > [1] https://www.apache.org/legal/resolved.html > > > Thanks. > Adam Feng >
Re: Weex Incubation Guidance
It's quite an important incubating work to the release. The most hardest part is resolving the license issue. We barely do the Apache release for more than 10 month due to the Facebook license issue. It's time for us to find a way to resolve the issue. Do you have any plan to do the Apache release recently? Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Tue, May 1, 2018 at 11:48 PM, Jonathan Dong < jondong.commun...@outlook.com> wrote: > Hi Luke, Niclas, Willem, Stephan and Raphael, > > I’m Jonathan from Weex community, I’m just writing to enquire if we still > have the privilege to be guided by you to proceed the incubation journey. > > From late last year, we see some progress has been made within the > community, but definitely that is not enough. We held the 3rd WeexConf as > well as the meetup in Shenzhen during this year, which is widely > acknowledged by the Weex community and developers mainly from China; The > activities in the mail list has increased, but still varies time to time; > and we have new contributors from PayTM, Tencent and other companies, but > still need more contribution to be a committer; and the community release > has been blocked by the Yoga replacement, the work has been done recently > and we are preparing for a new release in the near future. > > From my perspective, this is still a young community and need to be > cultivated with your help. I’ve talked with the committers and main > contributors of this project, from them I see the enthusiasm and belief in > the open source and community, even they don’t quite know how exactly to > make things right under the Apache way, especially under such a pressure of > their job work. So I hope we can still receive your guidance as a mentor > and continue to help this project to graduate, if you still have time and > passion to follow up. > > The next big thing is the community release, we hope to make it done asap, > but none of the active committer is familiar with the procedure. So if > anyone of you can help to follow the release guidance that would be > appreciated, and we hope we can finish the incubating journey as soon as > possible with your continuous help, thanks. > > Cheers, > Jonathan Dong
Re: [RESULT] [VOTE] New committer: toretto
FYI, You can find out the contribution of toretto here[1], his github id yuhun-alibaba. [1]https://github.com/apache/incubator-weex/commits?author=yuhun-alibaba Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Sun, Jan 7, 2018 at 11:28 AM, Willem Jiang <willem.ji...@gmail.com> wrote: > Just found the voting mail thread. > The Binding +1 were Adam Feng, He Sai, Shihan Zheng, Yuan Shen. > > > Willem Jiang > > Blog: http://willemjiang.blogspot.com (English) > http://jnn.iteye.com (Chinese) > Twitter: willemjiang > Weibo: 姜宁willem > > On Sun, Jan 7, 2018 at 10:38 AM, Willem Jiang <willem.ji...@gmail.com> > wrote: > >> Hi, >> >> I don't find the voting mail for toretto instead of this result mail. I >> don't know who vote +1 for it. >> @以马内利 Could you provide the voting thread here？ >> >> >> Willem Jiang >> >> Blog: http://willemjiang.blogspot.com (English) >> http://jnn.iteye.com (Chinese) >> Twitter: willemjiang >> Weibo: 姜宁willem >> >> On Wed, Oct 18, 2017 at 6:00 PM, 以马内利 <279483...@qq.com> wrote: >> >>> The vote has now closed. The results are: >>> >>> Binding Votes: >>> >>> +1 [TOTAL BINDING +4 VOTES] >>> 0 [TOTAL BINDING +0 VOTES] >>> -1 [TOTAL BINDING +0 VOTES] >>> >>> The vote is ***successful*** >>> >> >> >
Re: [RESULT] [VOTE] New committer: toretto
Just found the voting mail thread. The Binding +1 were Adam Feng, He Sai, Shihan Zheng, Yuan Shen. Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Sun, Jan 7, 2018 at 10:38 AM, Willem Jiang <willem.ji...@gmail.com> wrote: > Hi, > > I don't find the voting mail for toretto instead of this result mail. I > don't know who vote +1 for it. > @以马内利 Could you provide the voting thread here？ > > > Willem Jiang > > Blog: http://willemjiang.blogspot.com (English) > http://jnn.iteye.com (Chinese) > Twitter: willemjiang > Weibo: 姜宁willem > > On Wed, Oct 18, 2017 at 6:00 PM, 以马内利 <279483...@qq.com> wrote: > >> The vote has now closed. The results are: >> >> Binding Votes: >> >> +1 [TOTAL BINDING +4 VOTES] >> 0 [TOTAL BINDING +0 VOTES] >> -1 [TOTAL BINDING +0 VOTES] >> >> The vote is ***successful*** >> > >
Re: [RESULT] [VOTE] New committer: toretto
Hi, I don't find the voting mail for toretto instead of this result mail. I don't know who vote +1 for it. @以马内利 Could you provide the voting thread here？ Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Wed, Oct 18, 2017 at 6:00 PM, 以马内利 <279483...@qq.com> wrote: > The vote has now closed. The results are: > > Binding Votes: > > +1 [TOTAL BINDING +4 VOTES] > 0 [TOTAL BINDING +0 VOTES] > -1 [TOTAL BINDING +0 VOTES] > > The vote is ***successful*** >
Re: Hi my name is ...
Hi, My name is Willem. My Apache journey started from Apache CXF in 2006, and I also worked on Apache ActiveMQ, Apache Camel and Apache ServiceMix. It's my pleasure to join the Weex project as a mentor. My interesting is reactive programing and the backend service stacks. BTW, I'm living in Beijing :) Regards, Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Wed, Jan 4, 2017 at 2:30 PM, 大诗胸 <sospar...@gmail.com> wrote: > wow~~ '200 meters', means you two are available to yell to each > other literally. > > On Wed, Jan 4, 2017 at 1:49 PM, Niclas Hedhman <nic...@hedhman.org> wrote: > > > Hi, > > My name is Niclas and I have been involved in Apache software since ~1997 > > (JServ), and I am here to help you guys to understand what is > #TheApacheWay > > and how to navigate the various resources available to projects. So, I am > > one of 4 Mentors, and our role has nothing to do with the codebase, only > > the community. > > > > It may also help that I have lived in Malaysia more or less since 1986, > > except 5 years in Shanghai from 2010 to November last year. > Coincidentally, > > 200 meters from Luke Han, also a Mentor on the project. > > > > Cheers > > > > On Wed, Jan 4, 2017 at 9:24 AM, Edward J. Yoon <edward.y...@samsung.com> > > wrote: > > > > > Hi weex devs, Happy new year! > > > > > > My name is Edward J. Yoon and I'm on the Apache Hama, Bigtop, Incubator > > > PMC. > > > Recently my interests moves from batch based data-driven backend > systems > > to > > > real-time event-driven and serverless architecture, and edge computing > + > > > multi-devices applications' frontend. :) > > > > > > If you wish to introduced yourself we can use this same thread. > > > > > > -- > > > Best Regards, Edward J. Yoon > > > > > > > > > > > > > > > > > > > > > -- > > Niclas Hedhman, Software Developer > > http://polygene.apache.org <http://zest.apache.org> - New Energy for > Java > > > > > > -- > sospartan > Phone:13588488290 > HangZhou >
