Thanks for your message. 1. We don't have the download link for the weex project.
I will handle this issue ASAP 2. There are lots download links tools[1] in the weex website, which source > code are not part of apache weex project. As it is not clear that we should invite them as Apache weex, or mark them Un-Apache Weex and notify them to rename their names, I think we need some time to handle this problem. Best Regards, YorkShen 申远 Willem Jiang <[email protected]> 于2019年4月1日周一 上午11:13写道： > 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 <[email protected]> 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 [email protected] <mailto:[email protected]> > > > > > > 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 <[email protected]> 写道： > > > > > > 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，[email protected] <mailto:[email protected]> 写道： > > >> > > >> 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 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/April2019 < > https://wiki.apache.org/incubator/April2019> > > >> > > >> 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 > > > > > >
