Ok, so here are some info; The list of things to do before graduation, is things not yet done and you listed what has been achieved so far. This early in the incubation, I would put something like this "Weex community is really excited of getting going and we are in the process of getting organized" for this report. The follow, "We have so far managed..." and your list of things.
The format/template is not strict and people are happy to see more engaging language of what is going on. The "webpage" you refer to is called the "STATUS page". The webpage will eventually end up on https://weex.incubator.apache.org, which is a domain that has been created, but no content/site has been pushed there yet. The "questions" in the template should not be kept. If the release was done outside Apache (which it must have been), then it is not a release. You can mention that while getting organized in Apache, you still managed to crank out a release in the pre-Apache project. But I am overall not disappointed with the first report effort. And after a while it will be no issue. Cheers Niclas On Fri, Dec 30, 2016 at 4:04 PM, Bono Lv (Ali ZiKuan) < [email protected]> wrote: > Thanks Niclas. > > Following is our draft of first report. The template is from > https://wiki.apache.org/incubator/January2017 > > -------------------- > Weex is a framework for building Mobile cross- > platform high performance UI. > > Weex has been incubating since 2016-11-30. > > Three most important issues to address in the move towards graduation: > > 1. 7 members of Weex team have submitted ICLAs. > 2. SGA & CCLA have been signed and have been mailed to secretary > of ASF. > 3. Webpage have been created on the Apache incubator site: incubator. > apache.org/projects/weex.html > 4. Project maillist & JIRA have been activated & we > have volunteer JIRA administrator. > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/ > need to be aware of? > > * Code repository need to be set up. > > How has the community developed since the last report? > > * Weex Github star number was reached 10k on December 21. > > How has the project developed since the last report? > > * Several bugs have been fixed and some new features > have been added (detail information: https://github. > com/alibaba/weex/releases/tag/v0.9.4) > > Date of last release: > > 2016-12-22 > > When were the last committers or PPMC members elected? > > None > > Signed-off-by: > > [ ](weex) Luke Han > [ ](weex) Willem Jiang > [ ](weex) Stephan Ewen > [ ](weex) Niclas Hedhman > > Shepherd/Mentor notes: > > > ------------------------------------------------------------------ > From:Niclas Hedhman <[email protected]> > Time:2016 Dec 29 (Thu) 10:11 > To:dev <[email protected]> > Subject:Reporting duties > > Everyone, > > All projects in ASF has to report their activities to > the Board. Incubating > projects will report to the Incubator project, which in > turn reports to the > Board. This is to foster the reporting mentality in new projects, and also > give the Incubator PMC an idea if podlings are making progress. > > The first 3 months as a podling, as well as the first 3 months as a > top-level project, we report every month. After that, it is a quarterly > schedule, unless otherwise requested by Board/Incubator but that is quite > rare. > > Reports are important, but keep in mind that the world doesn't stop if it > doesn't happen or the report is not of the best quality. Everyone makes > mistakes, forgets and there is a general forgiving attitude. > > So, what does the report covers? > > * Community changes, such as new committers, PPMC members > * Progress, such as mailing list activity (up/down), JIRA issues solved > (up/down) > * Issues needing assistance, if we need help from someone else, such as > Legal, Infra and so on. > * Releases > > The report should not contain technical details that only users/developers > of the project would understand. It should not contain individual names, > unless extraordinary reasons for it. We operate as a unit, a single > community and we all own the responsibility of this project. > > Finally, Mentors are not expected to write the report, but we will assist > to fine tune it. Check https://lists.apache.org/list.html and search for > reports on dev@ lists (top level projects and/or > podlings) to get a general > idea. > > The report goes into this page; > https://wiki.apache.org/incubator/January2017 and it has a template for > Weex (and all the others) in it. I suggest that a Draft is written and > proposed on this list first. Any Volunteers? > > > Incubator has also released this timeline, in case you didn't noticed; > > Wed January 04 -- Podling reports due by end of day > Sun January 08 -- Shepherd reviews due by end of day > Sun January 08 -- Summary due by end of day > Tue January 10 -- Mentor signoff due by end of day > Wed January 11 -- Report submitted to Board > Wed January 18 -- Board meeting > > Hope this helps. > -- > Niclas Hedhman, Software Developer > http://zest.apache.org - New Energy for Java > > > -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java
