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

Moaz Reyad commented on SINGA-405:
----------------------------------

SINGA entered the incubator in March 2015. Currently the project is near 
graduation according to the [Incubator PMC report for September 
2018|https://wiki.apache.org/incubator/September2018].

For successful graduation, we need to
 # Check project maturity according to [Apache maturity 
model|http://community.apache.org/apache-way/apache-project-maturity-model.html]
 # Perform [graduation preparation steps 
|https://incubator.apache.org/guides/graduation.html]

To start with the first step, the incubator projects usually publish their ASF 
Maturity Evaluation in the [Apache Confluence Wiki|https://cwiki.apache.org/]. 
See for example, the evaluation of 
[HAWQ|https://cwiki.apache.org/confluence/display/HAWQ/ASF+Maturity+Evaluation] 
and 
[SkyWalking|https://cwiki.apache.org/confluence/display/SKYWALKING/Apache+Maturity+Model+Assessment+for+SkyWalking]
 projects.

There is no _Space_ for SINGA on the [Apache Confluence 
Wiki|https://cwiki.apache.org/]. Maybe we need first to create a Space for 
SINGA there. Then create ASF Maturity Evaluation page in that space. However, I 
don't have permissions to create a space or page on confluence. Can any one 
help with this?

> Graduate Apache SINGA (incubating) as a TLP
> -------------------------------------------
>
>                 Key: SINGA-405
>                 URL: https://issues.apache.org/jira/browse/SINGA-405
>             Project: Singa
>          Issue Type: Improvement
>            Reporter: Moaz Reyad
>            Priority: Major
>
> This issue is open for preparing the graduation of SINGA as Top Level Project 
> (TLP). 
> It is required to complete the Graduation Check List from the [graduation 
> guidelines|https://incubator.apache.org/guides/graduation.html]. We will 
> discuss the check list items in this issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to