[ 
https://issues.apache.org/jira/browse/SINGA-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16929778#comment-16929778
 ] 

Moaz Reyad commented on SINGA-486:
----------------------------------

It was [requested in the mail 
list|https://lists.apache.org/thread.html/6509d10c02817d662ebe04c0f7415ee38a2033861a6e23653a5a8a97@%3Cdev.singa.apache.org%3E]
 that the reports should have more details. I propose that we open the ticket 
for the report as early as possible, so we have more time to fill it with 
useful information. 

For example, if next report is in December (assuming reporting cycle does not 
change after graduation), we can open a ticket for December report from now. 
The ticket can be updated with every news or update that happens in the project 
from now to December. So when it is time for submitting the report, it will be 
ready and complete. 

Also this issue and SINGA-461 can be closed now.

> September report
> ----------------
>
>                 Key: SINGA-486
>                 URL: https://issues.apache.org/jira/browse/SINGA-486
>             Project: Singa
>          Issue Type: Task
>            Reporter: wangwei
>            Priority: Major
>
> Here is a draft for the report, which is also available at 
> https://wiki.apache.org/confluence/display/INCUBATOR/September2019
>  
> ----------
> h2. 
> [SINGA|https://wiki.apache.org/confluence/display/INCUBATOR/September2019#singa]
> SINGA is a distributed deep learning platform.
> SINGA has been incubating since 2015-03-17.
> h3. [Three most important unfinished issues to address before 
> graduating:|https://wiki.apache.org/confluence/display/INCUBATOR/September2019#three-most-important-unfinished-issues-to-address-before-graduating-15]
>  # Fix the code grant issue being discussed in the general@ list.
>  # Update the documentation and packages (e.g., docker images and conda 
> pacakges)
>  # 
> h3. [Are there any issues that the IPMC or ASF Board need to be aware 
> of?|https://wiki.apache.org/confluence/display/INCUBATOR/September2019#are-there-any-issues-that-the-ipmc-or-asf-board-need-to-be-aware-of-15]
> N.A
> h3. [How has the community developed since the last 
> report?|https://wiki.apache.org/confluence/display/INCUBATOR/September2019#how-has-the-community-developed-since-the-last-report-15]
>  * The community has been discussing about the graduation
>  * Currently, we have 45 contributors, 1803 stars and 479 forks on github.
> h3. [How has the project developed since the last 
> report?|https://wiki.apache.org/confluence/display/INCUBATOR/September2019#how-has-the-project-developed-since-the-last-report-15]
>  * Since the last report, we have been focusing on enhancing the ONNX feature 
> and distributed training. More than 20 ONNX operators are added. Distributed 
> training using NCCL and MPI has been tested.
>  * 180 new commits are merged since last report.
>  * There are 57, 142 and 472 emails on dev@ list for June, July and August 
> respectively.
> h3. [How would you assess the podling's 
> maturity?|https://wiki.apache.org/confluence/display/INCUBATOR/September2019#how-would-you-assess-the-podlings-maturity-15]
> Please feel free to add your own commentary.
>  *  Initial setup
>  *  Working towards first release
>  *  Community building
>  *  Nearing graduation
>  *  Other:
> h3. [Date of last 
> release:|https://wiki.apache.org/confluence/display/INCUBATOR/September2019#date-of-last-release-15]
> 2019-04-20
> h3. [When were the last committers or PPMC members 
> elected?|https://wiki.apache.org/confluence/display/INCUBATOR/September2019#when-were-the-last-committers-or-ppmc-members-elected-15]
> 2018-12-21
> h3. [Have your mentors been helpful and 
> responsive?|https://wiki.apache.org/confluence/display/INCUBATOR/September2019#have-your-mentors-been-helpful-and-responsive-15]
> Are things falling through the cracks? If so, please list any open issues 
> that need to be addressed.
> Yes. The mentors raised very important issues like the code grant in the 
> graduation discussion.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to