[RESULT][VOTE] Recommend 'Apache SINGA graduation to Top Level Project' resolution to the board

[Moaz Reyad]

The vote to recommend Apache SINGA graduation to Top Level Project
resolution
to the board has passed with:

4 +1 votes:

Furkan Kamaci
Kevin Ratnasekera
Justin Mclean
Alan Gates

No 0 or -1 votes.

The voting thread:

https://lists.apache.org/thread.html/73948f8a21884e360fdb47bafe35ef873c9258d890ec79afb718ef20@%3Cgeneral.incubator.apache.org%3E

Thank you all for your participation in the vote. We'll submit the
resolution to the board.

Thank you,
Moaz, on behalf of Apache SINGA (incubating) community

Re: [DISCUSS] Improve code quality

[Moaz Reyad]

Thank you all for participating in the discussion. It is nice that everyone
agrees that code quality is important.

Here are some comments:

1. It seems that everyone agrees on cpplint and pylint, but no one
discussed lgtm. Do you agree on using also the lgtm tool which is proposed
in [1] ? or do you think it is not needed and the cpplint and pylint is
enough? Note that there are lgtm badges that can be added to SINGA readme
on Github and acts as a certificate of the code quality that is visible to
everyone. While cpplint and pylint are not as visible as lgtm. Also lgtm
seems to report other problems that cpplint and pylint do not recognize.
Please share your ideas about the lgtm tool and SINGA-484 [1] issue.

2. We need to separate the discussion of the problem of future code quality
and the problem of current code quality. Enforcing code quality in future
is great, but in my opinion the team must take some actions also for the
current code. There are hundreds of issues reported by the three tools as
mentioned in my previous email. Not all of them are important of course,
but some percentage of them need to be fixed.

3. For future code quality, it is a good idea to use continuous integration
to run static code checking (cpplint, pylint and also RAT). I can open a
ticket in jira for this and anyone is welcome to implement it (after
finishing the more urgent issues with Travis CI). But cpplint and pylint
test will show too many errors already on the current code in the master
branch. This is why I think we need to solve the problem of current code
quality before enforcing future code quality.

4. The official site of SINGA is [2]. When the user navigates to "How to
Contribute Code" link, he will go to [3]. The link that was mention in [4]
is not accessible from [2]. The English site was moved to the root as the
default language [5], so no need to use "/en" folder in the path. If you
use the latest site build script [6], it will not create "/en" folder. This
means the link [4] was not generated by the latest site build script [6].

5. The code style instructions in [4] can be useful only for code style
issues, but all other code problems (such as those hundreds of issues
reported by the three tools) are not only about code style. Check the LGTM
alerts for SINGA [7] for example, they are not code style or readability
issues. (e.g unused variables, unreachable code, ..)

best regards,
Moaz

[1] https://issues.apache.org/jira/projects/SINGA/issues/SINGA-484
[2] http://singa.apache.org
[3] http://singa.apache.org/develop/contribute-code.html
[4] http://singa.apache.org/en/develop/contribute-code.html
[5] https://issues.apache.org/jira/projects/SINGA/issues/SINGA-436
[6] https://github.com/apache/incubator-singa/blob/master/doc/build.sh
[7] https://lgtm.com/projects/g/apache/incubator-singa/alerts/?mode=list

On Sun, Sep 15, 2019 at 5:02 PM Yeung Sai Ho  wrote:

> P.S. Therefore, tools like cpplint and pylint are useful and can be
> integrated into CI process that can check code automatically.
>
> 從我的 iPhone 傳送
>
> Yeung Sai Ho mailto:dcs...@nus.edu.sg>> 於 2019年9月15日
> 下午10:18 寫道：
>
>
> Dear Prof. Moaz Reyad,
>
>
>
> Nice to discuss with you, I am currently with NUS as a research fellow,
> and working with my peer co-workers (e.g. shicong/dcslin, joddly, shicheng,
> wanqi, pinpom, etc.) on SINGA leaded by our boss. I am Chris Yeung and this
> is my first time to join the discussion here.
>
>
>
> I agree with you. As a researcher and developer, I totally feel the same
> since code quality is very important. The code analysis tool could save our
> time and improve coding quality.
>
>
>
> In this email, please let me share my own personal view, concerning some
> recent daily practice in our local team which is currently using to enhance
> code quality:
>
>
>
> We are currently using the tools like cpplint and pylint to check and
> reformat the code so that we make sure our code is in compliance with the
> google style.
>
>
>
> Concerning our SINGA website, the new developers are suggested to read the
> following SINGA doc web page before they join developing the SINGA, which
> gives a complete and useful guide for their development:
>
> https://singa.apache.org/en/develop/contribute-code.html
>
>
>
> The above website recommends a very simple approach to enforce the Google
> coding styles: We can use the VS Code editor (
> https://code.visualstudio.com) and set the linting and formating tools.
> First, we need to install the C/C++ extension and python extension. Then,
> we can edit the seetings.json as:
>
> "editor.formatOnSave": true,
>
> "python.formatting.provider": "yapf",
>
> "python.formatting.yapfArgs": [
>
> "--style",
>
> "

[DISCUSS] Improve code quality

[Moaz Reyad]

Dear team,

Since SINGA is going to graduate soon from the incubator, I propose to use
some tools to ensure high code quality. These tools check for known
problems in the code and provide a detailed report for fixing them. May be
some code came from scientific experimental projects. We need to improve
this code according to industry standards, so it can be used with more real
life projects.

1. I propose to add the code quality tools (cpplint[1], pylint[2] and
lgtm[3]) to SINGA contribution guideline[4], so that each developer is
encouraged to install and run code quality checks in his local repo and fix
any problems before creating a pull request.

1.A CPP Lint: running cpplint in the src directory shows 822 errors, while
running in the include directory shows 708 errors. The guidelines [4] has
an outdated information that instructs developers to use an old
non-existing file tool/cpplint.py.

1.B Python Lint: running pylint in python/singa shows 5.00/10 rating, while
running in python/rafiki shows 0.00/10 rating.

1.C LGTM :There is a Jira ticket for adding LGTM badges to the README[5],
so the quality of the code becomes more clear to everyone. LGTM pull
request automation can't be enabled in Apache repo due to infra
restrictions[6], but it works on personal forks of the project. Currently
LGTM rates both C++ and Python code in SINGA as grade D.

2. I propose also to give the code quality higher priority in the next
release since it is probably going to be the first release after
graduation. The team is invited to fix as much as possible from the current
code issues and to use tools that check their new code before pushing it to
SINGA. Let's try to make the lgtm grade and lint rating as high as possible.

Improving code quality is required to attract new users and developers.
Users will trust more the project with better code and developers will be
happy to contribute to it. It will also make the code review process easier
and more productive instead of wasting time in finding and fixing known
code problems.

New developers (or old developers who did not contribute for a while and
would like to warm up) can start working on fixing lgtm and lint issues,
since they are usually easy and there is a clear explanation of the problem
and how to solve it.

What do you think?

p.s. This discussion is the first topic in a series of proposals to improve
SINGA as it will be an Apache top level project soon. The next proposal
will discuss improving the build and test pipeline in a separate thread to
avoid discussing too many things in one thread.

best regards,
Moaz

[1] https://pypi.org/project/cpplint/
[2] https://www.pylint.org/
[3] https://lgtm.com/
[4] http://singa.apache.org/develop/contribute-code.html
[5] https://issues.apache.org/jira/projects/SINGA/issues/SINGA-484
[6] https://issues.apache.org/jira/browse/INFRA-17954

[jira] [Commented] (SINGA-486) September report

[Moaz Reyad (Jira)]

[ 
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)

[VOTE] Recommend 'Apache SINGA graduation to Top Level Project' resolution to the board

[Moaz Reyad]

In the four and a half years that Apache SINGA (incubating) has been
a part of the Apache incubator, the community has grown, diversified,
and adapted to the Apache Way. We believe that the project is ready
to graduate to a TLP.

As a community, we have discussed [1] and voted [2] to graduate to a
TLP, we have worked through the maturity model [3], notified the IPMC
that we have the intention to graduate [4] and proposed PMC chair [5].
We filed a software grant [6] and discussed the graduation here [7].

Please take a minute to vote on whether or not the IPMC should recommend
the resolution below to the Board by responding with one of the following:

[ ] +1 Apache SINGA should graduate
[ ]  0 No opinion
[ ] -1 Apache SINGA should not graduate because...

The VOTE is open for a minimum of 72 hours.

Thank you,
Moaz, on behalf of Apache SINGA (incubating) community

[1]
https://lists.apache.org/thread.html/fd2fe639f3314ff22d2e47d39bd6d4126d61d10e8628fa26f71ef01d@%3Cdev.singa.apache.org%3E
[2]
https://lists.apache.org/thread.html/cb40b73b3fd685b44a129601abd5967e4150db245b3fc6552f106faf@%3Cdev.singa.apache.org%3E
[3]
https://cwiki.apache.org/confluence/display/SINGA/Maturity+model+assessment
[4]
https://lists.apache.org/thread.html/5b5ebefe705084e0a9d67cfaf56f17ff27518273366f8088be19273e@%3Cgeneral.incubator.apache.org%3E
[5]
https://lists.apache.org/thread.html/2903ea94da1b862acf8d706dd4f7cd9ecbc434166d4381d170be731f@%3Cprivate.singa.apache.org%3E
[6]
https://lists.apache.org/thread.html/0ae459aa462ab1aac6771f6ce7ff2a8a14ac286103bee5e1a42426b2@%3Cprivate.singa.apache.org%3E
[7]
https://lists.apache.org/thread.html/8f4bbc5f2945ffcda848fcf5cf2f6ff676069e0807cef3221f401728@%3Cgeneral.incubator.apache.org%3E

--

Proposed Resolution for the Apache SINGA project for the ASF Board:

Establish the Apache SINGA Project

WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software, for distribution at no charge to
the public, related to a distributed deep learning platform.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache SINGA Project",
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further

RESOLVED, that the Apache SINGA Project be and hereby is
responsible for the creation and maintenance of software
related to a distributed deep learning platform;
and be it further

RESOLVED, that the office of "Vice President, Apache SINGA" be
and hereby is created, the person holding such office to
serve at the direction of the Board of Directors as the chair
of the Apache SINGA Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache SINGA Project; and be it further

RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache SINGA Project:

* Thejas Nair ( the...@apache.org )
* Alan Gates ( ga...@apache.org )
* Ted Dunning ( tdunn...@apache.org )
* Beng Chin Ooi ( oo...@apache.org )
* Wang Wei ( wang...@apache.org )
* Anh Dinh ( dinh...@apache.org )
* Chen Gang( c...@apache.org )
* Jinyang Gao ( jiny...@apache.org )
* Kian-Lee Tan ( tankian...@apache.org )
* Luo Zhaojing ( zhaoj...@apache.org )
* Xie Zhongle ( zhon...@apache.org )
* Zheng Kaiping ( kaip...@apache.org )
* Moaz Reyad ( m...@apache.org )

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Wang Wei
be appointed to the office of Vice President, Apache SINGA, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification,
or until a successor is appointed; and be it further

RESOLVED, that the initial Apache SINGA PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache SINGA Project; and be it further

RESOLVED, that the Apache SINGA Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator SINGA podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache
Incubator SINGA podling encumbered upon the Apache Incubator
Project are hereafter discharged.

[jira] [Comment Edited] (SINGA-485) Code Coverage Analysis

[Moaz Reyad (Jira)]

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

Moaz Reyad edited comment on SINGA-485 at 9/9/19 9:47 AM:
--

??In fact, the current travis configuration will run the unit tests for python 
via conda test??

Yes, the current Travis configuration runs Python unit tests (instead of C++ 
unit tests) in the C++ CI tasks. So there are two problems:
 # It does not run the C++ unit tests, which is supposed to happen because only 
[C++ 
language|https://github.com/apache/incubator-singa/blob/master/.travis.yml#L19] 
is given in the [build matrix|https://docs.travis-ci.com/user/build-matrix/].
 # It runs Python unit tests on the C++ build machines that are not prepared to 
support Python. It installs Python on the C++ build machines instead of using 
Python CI build by adding language:python to the build matrix. It also seems to 
test both [Python 
3.6|https://github.com/apache/incubator-singa/blob/master/tool/conda/singa/conda_build_config.yaml#L33]
 and [Python 
3.7|https://github.com/apache/incubator-singa/blob/master/tool/conda/singa/conda_build_config.yaml#L34]
 in the same item.

Some refactoring is required here in my opinion.

??Does the code coverage analysis give us a report on how to improve the code??

It will give a report on which parts of the code is not executed by the test. 
Here are some examples from Apache project that use 
[codecov|https://codecov.io/gh/apache?page=1] and 
[coverall|https://coveralls.io/github/apache?page=1].


was (Author: moazreyad):
??In fact, the current travis configuration will run the unit tests for python 
via conda test??

Yes, the current Travis configuration runs Python unit tests (instead of C++ 
unit tests) in the C++ CI tasks. So there are two problems:
 # It does not run the C++ unit tests, which is supposed to happen because only 
[C++ 
language|https://github.com/apache/incubator-singa/blob/master/.travis.yml#L19] 
is given in the [build matrix|https://docs.travis-ci.com/user/build-matrix/].
 # It runs Python unit tests on the C++ build machines that are not prepared to 
support Python. It installs Python on the C++ build machines instead of using 
Python CI build by adding language:python to the build matrix. It also seems to 
test both Python 2 and Python 3 in the same item.

Some refactoring is required here in my opinion.

??Does the code coverage analysis give us a report on how to improve the code??

It will give a report on which parts of the code is not executed by the test. 
Here are some examples from Apache project that use 
[codecov|https://codecov.io/gh/apache?page=1] and 
[coverall|https://coveralls.io/github/apache?page=1].

> Code Coverage Analysis
> --
>
> Key: SINGA-485
> URL: https://issues.apache.org/jira/browse/SINGA-485
> Project: Singa
>  Issue Type: Improvement
>Reporter: Moaz Reyad
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> SINGA development and testing can be improved by using a [code 
> coverage|https://en.wikipedia.org/wiki/Code_coverage] tool.
> Some Apache projects use [codecov|https://codecov.io/gh/apache?page=1], while 
> others use [coverall|https://coveralls.io/github/apache?page=1].
> This issue is open to choose a code coverage tool and add it to SINGA build 
> and test pipeline.
>  



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

[jira] [Commented] (SINGA-488) Travis CI always build from Apache master branch

[Moaz Reyad (Jira)]

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

Moaz Reyad commented on SINGA-488:
--

I found the reason of this problem. The _git_url_ is defined 
[here|https://github.com/apache/incubator-singa/blob/master/tool/conda/singa/meta.yaml#L31]
 as:

{code:bash}
git_url: https://github.com/apache/incubator-singa.git
{code}

This will force the conda build command to always use the Apache master branch, 
even if the command is used from Travis CI to test a pull request on the Apache 
repository or on another forked repository. 

I think we should not use conda in the C++ continuous integration tasks. The 
C++ CI should be done with _cmake_ and _make test_. Conda can be used in 
another CI tasks for Python, but with the _source_ defined to build the current 
checked out code instead of always using the fixed URL of Apache master branch.

> Travis CI always build from Apache master branch
> 
>
> Key: SINGA-488
> URL: https://issues.apache.org/jira/browse/SINGA-488
> Project: Singa
>  Issue Type: Bug
>Reporter: Moaz Reyad
>Priority: Blocker
>
> It seems that the Travis build always use the master branch from 
> github.com/apache/incubator-singa.git instead of building the pull request.
> When checking the job log of Travis, I found it reads from github two times:
> 1. In the first time, it reads the correct pull request: (for example Pull 
> Request 532)
> {code:bash}
> git clone --depth=50 https://github.com/apache/incubator-singa.git 
> apache/incubator-singa
> ...
> git fetch origin +refs/pull/532/merge:
> git checkout -qf FETCH_HEAD
> {code}
> 2. Then it ignores this correctly fetched code, and does another git clone 
> from the conda build script:
> {code:bash}
> Cloning into bare repository 
> '/home/travis/conda-bld-1594.2/git_cache/github.com/apache/incubator-singa.git'...
> ...
> Your branch is up to date with 'origin/master'.
> {code}
> This means that it always builds the master branch instead of building the 
> pull request. So it has two problems:
>  # Missed alarms: if the master branch builds successfully, this will be 
> shown as if the pull request is fine and can be merged. While the pull 
> request code was actually never built.
>  # False alarms: if the master branch does not build successfully, this will 
> be shown as if the pull request has a problem, even if the problem is 
> actually in the master branch not in the pull request.
> If this issue is correct, then this is a blocker issue and I suggest to 
> resolve it before creating or merging any pull request. Because the 
> continuous integration tools that is supposed to test the pull requests is 
> not working correctly.



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

[jira] [Created] (SINGA-488) Travis CI always build from Apache master branch

[Moaz Reyad (Jira)]

Moaz Reyad created SINGA-488:


 Summary: Travis CI always build from Apache master branch
 Key: SINGA-488
 URL: https://issues.apache.org/jira/browse/SINGA-488
 Project: Singa
  Issue Type: Bug
Reporter: Moaz Reyad


It seems that the Travis build always use the master branch from 
github.com/apache/incubator-singa.git instead of building the pull request.

When checking the job log of Travis, I found it reads from github two times:

1. In the first time, it reads the correct pull request: (for example Pull 
Request 532)
{code:bash}
git clone --depth=50 https://github.com/apache/incubator-singa.git 
apache/incubator-singa
...
git fetch origin +refs/pull/532/merge:
git checkout -qf FETCH_HEAD
{code}
2. Then it ignores this correctly fetched code, and does another git clone from 
the conda build script:
{code:bash}
Cloning into bare repository 
'/home/travis/conda-bld-1594.2/git_cache/github.com/apache/incubator-singa.git'...
...
Your branch is up to date with 'origin/master'.
{code}
This means that it always builds the master branch instead of building the pull 
request. So it has two problems:
 # Missed alarms: if the master branch builds successfully, this will be shown 
as if the pull request is fine and can be merged. While the pull request code 
was actually never built.
 # False alarms: if the master branch does not build successfully, this will be 
shown as if the pull request has a problem, even if the problem is actually in 
the master branch not in the pull request.

If this issue is correct, then this is a blocker issue and I suggest to resolve 
it before creating or merging any pull request. Because the continuous 
integration tools that is supposed to test the pull requests is not working 
correctly.



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

[jira] [Commented] (SINGA-485) Code Coverage Analysis

[Moaz Reyad (Jira)]

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

Moaz Reyad commented on SINGA-485:
--

??In fact, the current travis configuration will run the unit tests for python 
via conda test??

Yes, the current Travis configuration runs Python unit tests (instead of C++ 
unit tests) in the C++ CI tasks. So there are two problems:
 # It does not run the C++ unit tests, which is supposed to happen because only 
[C++ 
language|https://github.com/apache/incubator-singa/blob/master/.travis.yml#L19] 
is given in the [build matrix|https://docs.travis-ci.com/user/build-matrix/].
 # It runs Python unit tests on the C++ build machines that are not prepared to 
support Python. It installs Python on the C++ build machines instead of using 
Python CI build by adding language:python to the build matrix. It also seems to 
test both Python 2 and Python 3 in the same item.

Some refactoring is required here in my opinion.

??Does the code coverage analysis give us a report on how to improve the code??

It will give a report on which parts of the code is not executed by the test. 
Here are some examples from Apache project that use 
[codecov|https://codecov.io/gh/apache?page=1] and 
[coverall|https://coveralls.io/github/apache?page=1].

> Code Coverage Analysis
> --
>
> Key: SINGA-485
> URL: https://issues.apache.org/jira/browse/SINGA-485
> Project: Singa
>  Issue Type: Improvement
>Reporter: Moaz Reyad
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> SINGA development and testing can be improved by using a [code 
> coverage|https://en.wikipedia.org/wiki/Code_coverage] tool.
> Some Apache projects use [codecov|https://codecov.io/gh/apache?page=1], while 
> others use [coverall|https://coveralls.io/github/apache?page=1].
> This issue is open to choose a code coverage tool and add it to SINGA build 
> and test pipeline.
>  



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

[jira] [Resolved] (SINGA-449) Preparing Podling TLP resolution

[Moaz Reyad (Jira)]

 [ 
https://issues.apache.org/jira/browse/SINGA-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Moaz Reyad resolved SINGA-449.
--
Resolution: Fixed

> Preparing Podling TLP resolution
> 
>
> Key: SINGA-449
> URL: https://issues.apache.org/jira/browse/SINGA-449
> Project: Singa
>  Issue Type: Task
>    Reporter: Moaz Reyad
>Priority: Major
>
> This issue is for preparing the graduation resolution for SINGA given the 
> [template|https://svn.apache.org/repos/private/committers/board/templates/podling-tlp-resolution.txt].
> The resolution draft for SINGA is 
> [here|https://cwiki.apache.org/confluence/display/SINGA/Graduation+Resolution].
> Please check it and give your feedback.
> SINGA PPMC need to discuss and choose the project Chair (see private mail 
> list).
> We also need to specify initial project members. We can copy all the current 
> members without asking their permission (assuming everyone agrees) or we may 
> ask every member to explicitly agree to be added to the initial project 
> members.



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

[jira] [Commented] (SINGA-485) Code Coverage Analysis

[Moaz Reyad (Jira)]

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

Moaz Reyad commented on SINGA-485:
--

Currently the Travis CI configuration performs only the build but no test is 
enabled. It does not compile with {code:bash} ENABLE_TEST {code} option enabled.

To perform code coverage analysis, we need to:
* Enable the build of unit tests using -DENABLE_TEST=ON
* Run the unit tests

Note that the current configuration is for C++ only since it has the line 
{code:bash} language: cpp {code}
It builds python and conda packages, but this does not help in the unit test of 
C++ code. Later we need to add language:python to the travis build matrix and 
move the python build/test under that item.

Any comments or discussion is welcome.

> Code Coverage Analysis
> --
>
> Key: SINGA-485
> URL: https://issues.apache.org/jira/browse/SINGA-485
> Project: Singa
>  Issue Type: Improvement
>Reporter: Moaz Reyad
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> SINGA development and testing can be improved by using a [code 
> coverage|https://en.wikipedia.org/wiki/Code_coverage] tool.
> Some Apache projects use [codecov|https://codecov.io/gh/apache?page=1], while 
> others use [coverall|https://coveralls.io/github/apache?page=1].
> This issue is open to choose a code coverage tool and add it to SINGA build 
> and test pipeline.
>  



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

Re: [Discuss] Graduate Apache SINGA (incubating) as a TLP

[Moaz Reyad]

The PPMC reached a conclusion on the discussion [1] that there is no need
for SGA.

Please let me know if there is anything else required. Otherwise, we start
the vote.

Thank you,
Moaz

[1]
https://lists.apache.org/thread.html/b8b2979a870784ce04f87572e0f44311a1338bc9365e955a80d5248b@1427941853@%3Cprivate.singa.apache.org%3E

On Sun, Sep 1, 2019 at 5:00 AM Dave Fisher  wrote:

> Hi -
>
> I see the discussion that an SGA is not needed about 4/2/2015. [1]
>
> I don’t necessarily see the there was a conclusion to that discussion on
> private@singa. I certainly don’t see anything related to Singapore in the
> grants index in the foundation records. There are plenty of other sgas
> recorded from universities.
>
> Regards,
> Dave
>
> [1]
> https://lists.apache.org/thread.html/b8b2979a870784ce04f87572e0f44311a1338bc9365e955a80d5248b@1427941853@%3Cprivate.singa.apache.org%3E
>
> > On Aug 31, 2019, at 7:35 PM, Alan Gates  wrote:
> >
> > Yes, I saw that, but I can't find those papers.  They should have been
> > filed by the Apache secretary on the page I referenced.  Either they were
> > properly transferred and we need to find them so that they are properly
> > posted in case anyone ever needs them, or, if they weren't sent, then we
> > need to make sure a copy of them is sent.
> >
> > I guess the next step is to email the secretary and ask if he's aware of
> > that transfer having taken place, unless anyone knows somewhere else I
> > should be looking for them.
> >
> > Alan.
> >
> > On Sat, Aug 31, 2019 at 3:48 AM Moaz Reyad  wrote:
> >
> >> Dear Alan,
> >>
> >> The copyright section in the project page [1] has the following item :
> >>
> >> Date: 2015-03-31
> >> Item: Check and make sure that the papers that transfer rights to the
> ASF
> >> been received. It is only necessary to transfer rights for the package,
> the
> >> core code, and any new code produced by the project.
> >>
> >> I believe this answers your question about the transfer rights of the
> code.
> >> Please let me know if there is anything else required.
> >>
> >> We will proceed to vote if no one objects.
> >>
> >> Thank you,
> >> Moaz
> >>
> >> [1] http://incubator.apache.org/projects/singa.html
> >>
> >> On Tue, Aug 27, 2019 at 8:48 PM Alan Gates 
> wrote:
> >>
> >>> Sorry, I brought this up earlier on the dev list but didn't follow
> up.  I
> >>> can't find a copy of the code grant for the code that Singa brought
> into
> >>> the Incubator.  When I look at the Secretary's page[1] that lists all
> of
> >>> the code grants I don't see one for Singa.  Per the initial proposal[2]
> >>> there was code imported from an existing github repo [3], which means
> we
> >>> need to have a code grant from whom ever owned that code (National
> >>> University of Singapore would be my guess).
> >>>
> >>> We need to clear this up before Singa graduates to assure that the ASF
> >> has
> >>> the right to this code.
> >>>
> >>> Alan.
> >>>
> >>> [1] https://incubator.apache.org/ip-clearance/index.html
> >>> [2]
> https://cwiki.apache.org/confluence/display/INCUBATOR/SingaProposal
> >>> [3] https://github.com/nusinga/singa
> >>>
> >>> On Tue, Aug 27, 2019 at 1:34 AM Moaz Reyad  wrote:
> >>>
> >>>> Hi all,
> >>>>
> >>>> In the four and a half years that Apache SINGA (incubating) has
> >>>> been a part of the Apache incubator, the community has grown,
> >>> diversified,
> >>>> and adapted to the Apache Way. We believe that the project is ready to
> >>>> graduate to a TLP.
> >>>>
> >>>> As a community, we have discussed [1] and voted [2] to graduate to a
> >>>> TLP, we have worked through the maturity model [3], notified the IPMC
> >>> that
> >>>> we have the intention to graduate [4] and proposed PMC chair [5].
> >>>>
> >>>> Please see the draft resolution appended below and provide any
> >>>> comments or feedback you have on it.
> >>>>
> >>>> We would like to continue the graduation process and hereby ask you
> >>>> all for your opinion on this. The discussion is open for 72 hours,
> >> after
> >>>> which we will start a [VOTE] on graduation here.
> >&

Re: [Discuss] Graduate Apache SINGA (incubating) as a TLP

[Moaz Reyad]

Dear Alan,

The copyright section in the project page [1] has the following item :

Date: 2015-03-31
Item: Check and make sure that the papers that transfer rights to the ASF
been received. It is only necessary to transfer rights for the package, the
core code, and any new code produced by the project.

I believe this answers your question about the transfer rights of the code.
Please let me know if there is anything else required.

We will proceed to vote if no one objects.

Thank you,
Moaz

[1] http://incubator.apache.org/projects/singa.html

On Tue, Aug 27, 2019 at 8:48 PM Alan Gates  wrote:

> Sorry, I brought this up earlier on the dev list but didn't follow up.  I
> can't find a copy of the code grant for the code that Singa brought into
> the Incubator.  When I look at the Secretary's page[1] that lists all of
> the code grants I don't see one for Singa.  Per the initial proposal[2]
> there was code imported from an existing github repo [3], which means we
> need to have a code grant from whom ever owned that code (National
> University of Singapore would be my guess).
>
> We need to clear this up before Singa graduates to assure that the ASF has
> the right to this code.
>
> Alan.
>
> [1] https://incubator.apache.org/ip-clearance/index.html
> [2] https://cwiki.apache.org/confluence/display/INCUBATOR/SingaProposal
> [3] https://github.com/nusinga/singa
>
> On Tue, Aug 27, 2019 at 1:34 AM Moaz Reyad  wrote:
>
> > Hi all,
> >
> > In the four and a half years that Apache SINGA (incubating) has
> > been a part of the Apache incubator, the community has grown,
> diversified,
> > and adapted to the Apache Way. We believe that the project is ready to
> > graduate to a TLP.
> >
> > As a community, we have discussed [1] and voted [2] to graduate to a
> > TLP, we have worked through the maturity model [3], notified the IPMC
> that
> > we have the intention to graduate [4] and proposed PMC chair [5].
> >
> > Please see the draft resolution appended below and provide any
> > comments or feedback you have on it.
> >
> > We would like to continue the graduation process and hereby ask you
> > all for your opinion on this. The discussion is open for 72 hours, after
> > which we will start a [VOTE] on graduation here.
> >
> > Thanks,
> >
> > --moaz
> > on behalf of the Apache SINGA PPMC
> >
> > [1]
> >
> >
> https://lists.apache.org/thread.html/fd2fe639f3314ff22d2e47d39bd6d4126d61d10e8628fa26f71ef01d@%3Cdev.singa.apache.org%3E
> > [2]
> >
> >
> https://lists.apache.org/thread.html/cb40b73b3fd685b44a129601abd5967e4150db245b3fc6552f106faf@%3Cdev.singa.apache.org%3E
> > [3]
> >
> https://cwiki.apache.org/confluence/display/SINGA/Maturity+model+assessment
> > [4]
> >
> >
> https://lists.apache.org/thread.html/5b5ebefe705084e0a9d67cfaf56f17ff27518273366f8088be19273e@%3Cgeneral.incubator.apache.org%3E
> > [5]
> >
> >
> https://lists.apache.org/thread.html/2903ea94da1b862acf8d706dd4f7cd9ecbc434166d4381d170be731f@%3Cprivate.singa.apache.org%3E
> >
> > Proposed Resolution for the Apache SINGA project for the ASF Board:
> >
> > X. Establish the Apache SINGA Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best
> > interests of the Foundation and consistent with the
> > Foundation's purpose to establish a Project Management
> > Committee charged with the creation and maintenance of
> > open-source software, for distribution at no charge to
> > the public, related to a distributed deep learning platform.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > Committee (PMC), to be known as the "Apache SINGA Project",
> > be and hereby is established pursuant to Bylaws of the
> > Foundation; and be it further
> >
> > RESOLVED, that the Apache SINGA Project be and hereby is
> > responsible for the creation and maintenance of software
> > related to a distributed deep learning platform;
> > and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache SINGA" be
> > and hereby is created, the person holding such office to
> > serve at the direction of the Board of Directors as the chair
> > of the Apache SINGA Project, and to have primary responsibility
> > for management of the projects within the scope of
> > responsibility of the Apache SINGA Project; and be it further
> >
> > RESOLVED, that the persons listed immediately below be and
> > hereby are appointed to serve as the initial members of the
> > Apache SINGA Project:
> >
> > * Thej

[jira] [Commented] (SINGA-485) Code Coverage Analysis

[Moaz Reyad (Jira)]

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

Moaz Reyad commented on SINGA-485:
--

I propose to use codecov with Travis CI integration.

However, the current Travis CI configuration needs some refactoring to improve 
the test coverage.

[The 
configuration|https://github.com/moazreyad/incubator-singa/blob/master/.travis.yml]
 only tests the *build* process on Ubuntu 14.04 (trusty) and macOS 10.11.

The [installation 
page|http://singa.apache.org/docs/installation.html#from-source] says:
{code:html}
The above commands have been tested on Ubuntu 16.04 and Mac OSX. Refer to the 
Travis-CI page for more information.
{code}
But the test was actually done on 14.04 not 16.04.

I am going to add the build test for both Ubuntu 16.04 and Ubuntu 18.04 to the 
Travis configuration.

> Code Coverage Analysis
> --
>
> Key: SINGA-485
> URL: https://issues.apache.org/jira/browse/SINGA-485
> Project: Singa
>  Issue Type: Improvement
>Reporter: Moaz Reyad
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> SINGA development and testing can be improved by using a [code 
> coverage|https://en.wikipedia.org/wiki/Code_coverage] tool.
> Some Apache projects use [codecov|https://codecov.io/gh/apache?page=1], while 
> others use [coverall|https://coveralls.io/github/apache?page=1].
> This issue is open to choose a code coverage tool and add it to SINGA build 
> and test pipeline.
>  



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

[jira] [Created] (SINGA-485) Code Coverage Analysis

[Moaz Reyad (Jira)]

Moaz Reyad created SINGA-485:


 Summary: Code Coverage Analysis
 Key: SINGA-485
 URL: https://issues.apache.org/jira/browse/SINGA-485
 Project: Singa
  Issue Type: Improvement
Reporter: Moaz Reyad


SINGA development and testing can be improved by using a [code 
coverage|https://en.wikipedia.org/wiki/Code_coverage] tool.

Some Apache projects use [codecov|https://codecov.io/gh/apache?page=1], while 
others use [coverall|https://coveralls.io/github/apache?page=1].

This issue is open to choose a code coverage tool and add it to SINGA build and 
test pipeline.

 



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

[Discuss] Graduate Apache SINGA (incubating) as a TLP

[Moaz Reyad]

Hi all,

In the four and a half years that Apache SINGA (incubating) has
been a part of the Apache incubator, the community has grown, diversified,
and adapted to the Apache Way. We believe that the project is ready to
graduate to a TLP.

As a community, we have discussed [1] and voted [2] to graduate to a
TLP, we have worked through the maturity model [3], notified the IPMC that
we have the intention to graduate [4] and proposed PMC chair [5].

Please see the draft resolution appended below and provide any
comments or feedback you have on it.

We would like to continue the graduation process and hereby ask you
all for your opinion on this. The discussion is open for 72 hours, after
which we will start a [VOTE] on graduation here.

Thanks,

--moaz
on behalf of the Apache SINGA PPMC

[1]
https://lists.apache.org/thread.html/fd2fe639f3314ff22d2e47d39bd6d4126d61d10e8628fa26f71ef01d@%3Cdev.singa.apache.org%3E
[2]
https://lists.apache.org/thread.html/cb40b73b3fd685b44a129601abd5967e4150db245b3fc6552f106faf@%3Cdev.singa.apache.org%3E
[3]
https://cwiki.apache.org/confluence/display/SINGA/Maturity+model+assessment
[4]
https://lists.apache.org/thread.html/5b5ebefe705084e0a9d67cfaf56f17ff27518273366f8088be19273e@%3Cgeneral.incubator.apache.org%3E
[5]
https://lists.apache.org/thread.html/2903ea94da1b862acf8d706dd4f7cd9ecbc434166d4381d170be731f@%3Cprivate.singa.apache.org%3E

Proposed Resolution for the Apache SINGA project for the ASF Board:

X. Establish the Apache SINGA Project

WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software, for distribution at no charge to
the public, related to a distributed deep learning platform.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache SINGA Project",
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further

RESOLVED, that the Apache SINGA Project be and hereby is
responsible for the creation and maintenance of software
related to a distributed deep learning platform;
and be it further

RESOLVED, that the office of "Vice President, Apache SINGA" be
and hereby is created, the person holding such office to
serve at the direction of the Board of Directors as the chair
of the Apache SINGA Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache SINGA Project; and be it further

RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache SINGA Project:

* Thejas Nair ( the...@apache.org )
* Alan Gates ( ga...@apache.org )
* Ted Dunning ( tdunn...@apache.org )
* Beng Chin Ooi ( oo...@apache.org )
* Wang Wei ( wang...@apache.org )
* Anh Dinh ( dinh...@apache.org )
* Chen Gang( c...@apache.org )
* Jinyang Gao ( jiny...@apache.org )
* Kian-Lee Tan ( tankian...@apache.org )
* Luo Zhaojing ( zhaoj...@apache.org )
* Xie Zhongle ( zhon...@apache.org )
* Zheng Kaiping ( kaip...@apache.org )
* Moaz Reyad ( m...@apache.org )

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Wang Wei
be appointed to the office of Vice President, Apache SINGA, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification,
or until a successor is appointed; and be it further

RESOLVED, that the initial Apache SINGA PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache SINGA Project; and be it further

RESOLVED, that the Apache SINGA Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator SINGA podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache
Incubator SINGA podling encumbered upon the Apache Incubator
Project are hereafter discharged.

[RESULT][VOTE] Graduate Apache SINGA as TLP

[Moaz Reyad]

The vote has passed with a total of 4 +1 votes from PPMC members:

Wang Wei
Beng Chin OOI
Xie Zhongle
Moaz Reyad

There are no 0 or -1 votes.

I think we can now proceed to the Incubator mail list discussion and vote.

Best regards,
Moaz

Re: New services for SINGA (Mentors help needed)

[Moaz Reyad]

I think there is no need to keep both the code and the website
documentation in one repository.

The website build script can perform "git clone" on the incubator-singa
repository to get both the Python code for the API and the C++ for Doxygen.

Moaz

On Sat, Aug 10, 2019 at 10:58 AM Wang Wei  wrote:

>
> Since Sphinx needs the source Python code to generate the API, I think it
> would be good to put the documentation files in the
> https://github.com/apache/incubator-singa
> .
>
>

Fwd: [VOTE] Graduate Apache SINGA as TLP

[Moaz Reyad]

Dear All,

I would like to notify the incubator general list that the SINGA community
has started the vote for graduation few days ago.

This notification is recommended by the graduation guide (
https://incubator.apache.org/guides/graduation.html#community_graduation_vote
).

Best regards,
Moaz

-- Forwarded message -
From: Moaz Reyad 
Date: Sat, Aug 24, 2019 at 6:01 PM
Subject: Re: [VOTE] Graduate Apache SINGA as TLP
To: 
Cc: 


+1 from me also.

The vote can be closed and I will send the RESULT email soon.

But it will be useful if the mentors participate in this voting before we
close it.

best regards,
Moaz

On Thu, Aug 22, 2019 at 4:34 AM zhongle  wrote:

> +1
>
> Best,
> zl
>
> > On Aug 22, 2019, at 10:24, Beng Chin OOI  wrote:
> >
> >
> > +1
> >
> > regards
> > Beng Chin
> >
> >
> >> On 2019-08-22 10:22, Wang Wei wrote:
> >> +1
> >> Thanks, Moaz!
> >> Regards,
> >> Wei
> >>> On Wed, Aug 21, 2019 at 8:53 PM Moaz Reyad  wrote:
> >>> Dear All,
> >>> Apache SINGA entered the incubator on March 2015. Since then, the
> community
> >>> has grown and several releases were published.
> >>> The last incubator report listed SINGA as "Nearing graduation":
> >>> https://cwiki.apache.org/confluence/display/INCUBATOR/June2019
> >>> The maturity assessment of SINGA can be found here:
> >>>
> https://cwiki.apache.org/confluence/display/SINGA/Maturity+model+assessment
> >>> The graduation resolution can be found here:
> >>>
> https://cwiki.apache.org/confluence/display/SINGA/Graduation+Resolution
> >>> Please take a minute to vote on whether or not Apache SINGA should
> graduate
> >>> to a Top Level Project by responding with one of the following:
> >>> [ ] +1 Apache SINGA should graduate.
> >>> [ ] +0 No opinion
> >>> [ ] -1 Apache SINGA should not graduate (please provide the reason)
> >>> The VOTE is open for a minimum of 72 hours.
> >>> Thank you,
> >>> Moaz
>
>

[jira] [Commented] (SINGA-456) Adding more PGP Keys

[Moaz Reyad (Jira)]

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

Moaz Reyad commented on SINGA-456:
--

reminder: the key will expire next month and it should be extended. Otherwise 
the next release of SINGA can not be correctly signed.

I noticed also that many Apache projects put the KEYS file in GitHub, such as 
[MXNET|https://github.com/apache/incubator-mxnet/blob/master/KEYS], 
[NIFI|https://github.com/apache/nifi/blob/master/KEYS], 
[Tika|https://github.com/apache/tika/blob/master/KEYS], … etc. So it may be a 
good idea to add SINGA KEYS also to GitHub.

> Adding more PGP Keys
> 
>
> Key: SINGA-456
> URL: https://issues.apache.org/jira/browse/SINGA-456
> Project: Singa
>  Issue Type: Improvement
>Reporter: Moaz Reyad
>Priority: Major
> Attachments: KEYS
>
>
> Currently the SINGA [KEYS |https://www.apache.org/dist/incubator/singa/KEYS] 
> file has only one PGP key which is expiring this September (it needs to be 
> updated). This means only one person can sign the releases. While other 
> projects like CouchDB for example, have several keys in the [KEYS 
> |https://www.apache.org/dist/couchdb/KEYS] file.
> It will be useful if every active Apache committer in the team create a PGP 
> key and uploads the Public Key Primary Fingerprint to his account using 
> [Apache Account Utility|https://id.apache.org/]. Then append the new key to 
> the SINGA KEYS file.
> Furthermore, the keys themselves can be signed for more trust. SINGA team can 
> exchange key signatures between them or organize a [key signing 
> party|https://www.apache.org/dev/release-signing#key-signing-party]. This 
> will help adding more SINGA committers into the [Apache Web of 
> Trust|https://www.apache.org/dev/release-signing#web-of-trust]. 
> I attach with this issue the KEYS file with my key appended at the end. 



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

[jira] [Created] (SINGA-484) Code analysis with LGTM

[Moaz Reyad (Jira)]

Moaz Reyad created SINGA-484:


 Summary: Code analysis with LGTM
 Key: SINGA-484
 URL: https://issues.apache.org/jira/browse/SINGA-484
 Project: Singa
  Issue Type: Improvement
Reporter: Moaz Reyad


As the code of SINGA is growing, we need to keep the code quality higher to 
avoid bugs or security issues.

[LGTM|https://lgtm.com/] is a free tool for continuous security analysis.

At the time of creating this issue, the quality of SINGA's C++ and Python code 
are both at [grade|https://lgtm.com/help/lgtm/project-scoring-grading] D 
(between A+ and E, this is a low grade). 

There are some [alerts for 
SINGA|https://lgtm.com/projects/g/apache/incubator-singa/alerts/?mode=list] 
that should be fixed.



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

Re: [VOTE] Graduate Apache SINGA as TLP

[Moaz Reyad]

+1 from me also.

The vote can be closed and I will send the RESULT email soon.

But it will be useful if the mentors participate in this voting before we
close it.

best regards,
Moaz

On Thu, Aug 22, 2019 at 4:34 AM zhongle  wrote:

> +1
>
> Best,
> zl
>
> > On Aug 22, 2019, at 10:24, Beng Chin OOI  wrote:
> >
> >
> > +1
> >
> > regards
> > Beng Chin
> >
> >
> >> On 2019-08-22 10:22, Wang Wei wrote:
> >> +1
> >> Thanks, Moaz!
> >> Regards,
> >> Wei
> >>> On Wed, Aug 21, 2019 at 8:53 PM Moaz Reyad  wrote:
> >>> Dear All,
> >>> Apache SINGA entered the incubator on March 2015. Since then, the
> community
> >>> has grown and several releases were published.
> >>> The last incubator report listed SINGA as "Nearing graduation":
> >>> https://cwiki.apache.org/confluence/display/INCUBATOR/June2019
> >>> The maturity assessment of SINGA can be found here:
> >>>
> https://cwiki.apache.org/confluence/display/SINGA/Maturity+model+assessment
> >>> The graduation resolution can be found here:
> >>>
> https://cwiki.apache.org/confluence/display/SINGA/Graduation+Resolution
> >>> Please take a minute to vote on whether or not Apache SINGA should
> graduate
> >>> to a Top Level Project by responding with one of the following:
> >>> [ ] +1 Apache SINGA should graduate.
> >>> [ ] +0 No opinion
> >>> [ ] -1 Apache SINGA should not graduate (please provide the reason)
> >>> The VOTE is open for a minimum of 72 hours.
> >>> Thank you,
> >>> Moaz
>
>

[VOTE] Graduate Apache SINGA as TLP

[Moaz Reyad]

Dear All,

Apache SINGA entered the incubator on March 2015. Since then, the community
has grown and several releases were published.

The last incubator report listed SINGA as "Nearing graduation":
https://cwiki.apache.org/confluence/display/INCUBATOR/June2019

The maturity assessment of SINGA can be found here:
https://cwiki.apache.org/confluence/display/SINGA/Maturity+model+assessment

The graduation resolution can be found here:
https://cwiki.apache.org/confluence/display/SINGA/Graduation+Resolution

Please take a minute to vote on whether or not Apache SINGA should graduate
to a Top Level Project by responding with one of the following:

 [ ] +1 Apache SINGA should graduate.
 [ ] +0 No opinion
 [ ] -1 Apache SINGA should not graduate (please provide the reason)

The VOTE is open for a minimum of 72 hours.

Thank you,
Moaz

[jira] [Commented] (SINGA-449) Preparing Podling TLP resolution

[Moaz Reyad (Jira)]

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

Moaz Reyad commented on SINGA-449:
--

Please check the resolution 
[here|https://cwiki.apache.org/confluence/display/SINGA/Graduation+Resolution].

If any one from the initial members is not interested in joining the project, 
he can remove his name before the resolution is submitted.

> Preparing Podling TLP resolution
> 
>
> Key: SINGA-449
> URL: https://issues.apache.org/jira/browse/SINGA-449
> Project: Singa
>  Issue Type: Task
>Reporter: Moaz Reyad
>Priority: Major
>
> This issue is for preparing the graduation resolution for SINGA given the 
> [template|https://svn.apache.org/repos/private/committers/board/templates/podling-tlp-resolution.txt].
> The resolution draft for SINGA is 
> [here|https://cwiki.apache.org/confluence/display/SINGA/Graduation+Resolution].
> Please check it and give your feedback.
> SINGA PPMC need to discuss and choose the project Chair (see private mail 
> list).
> We also need to specify initial project members. We can copy all the current 
> members without asking their permission (assuming everyone agrees) or we may 
> ask every member to explicitly agree to be added to the initial project 
> members.



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

[jira] [Comment Edited] (SINGA-449) Preparing Podling TLP resolution

[Moaz Reyad (Jira)]

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

Moaz Reyad edited comment on SINGA-449 at 8/21/19 12:38 PM:


Since no discussion was done on this issue since April, I will assume that the 
initial project members are all the current members (PPMC and mentors). I will 
assume all members agree to join the project and no need to ask for their 
individual permission to be added to the project.

If no one disagrees, I will proceed with updating the graduation resolution by 
adding all the current members as initial project members.


was (Author: moazreyad):
Since no discussion was done on this issue since April, I will assume that the 
initial project members are all the current members (PPMC and Committers). I 
will assume all members agree to join the project and no need to ask for their 
individual permission to be added to the project.

If no one disagrees, I will proceed with updating the graduation resolution by 
adding all the current members as initial project members.

> Preparing Podling TLP resolution
> 
>
> Key: SINGA-449
> URL: https://issues.apache.org/jira/browse/SINGA-449
> Project: Singa
>  Issue Type: Task
>Reporter: Moaz Reyad
>Priority: Major
>
> This issue is for preparing the graduation resolution for SINGA given the 
> [template|https://svn.apache.org/repos/private/committers/board/templates/podling-tlp-resolution.txt].
> The resolution draft for SINGA is 
> [here|https://cwiki.apache.org/confluence/display/SINGA/Graduation+Resolution].
> Please check it and give your feedback.
> SINGA PPMC need to discuss and choose the project Chair (see private mail 
> list).
> We also need to specify initial project members. We can copy all the current 
> members without asking their permission (assuming everyone agrees) or we may 
> ask every member to explicitly agree to be added to the initial project 
> members.



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

[jira] [Commented] (SINGA-449) Preparing Podling TLP resolution

[Moaz Reyad (Jira)]

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

Moaz Reyad commented on SINGA-449:
--

Since no discussion was done on this issue since April, I will assume that the 
initial project members are all the current members (PPMC and Committers). I 
will assume all members agree to join the project and no need to ask for their 
individual permission to be added to the project.

If no one disagrees, I will proceed with updating the graduation resolution by 
adding all the current members as initial project members.

> Preparing Podling TLP resolution
> 
>
> Key: SINGA-449
> URL: https://issues.apache.org/jira/browse/SINGA-449
> Project: Singa
>  Issue Type: Task
>Reporter: Moaz Reyad
>Priority: Major
>
> This issue is for preparing the graduation resolution for SINGA given the 
> [template|https://svn.apache.org/repos/private/committers/board/templates/podling-tlp-resolution.txt].
> The resolution draft for SINGA is 
> [here|https://cwiki.apache.org/confluence/display/SINGA/Graduation+Resolution].
> Please check it and give your feedback.
> SINGA PPMC need to discuss and choose the project Chair (see private mail 
> list).
> We also need to specify initial project members. We can copy all the current 
> members without asking their permission (assuming everyone agrees) or we may 
> ask every member to explicitly agree to be added to the initial project 
> members.



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

Re: [DISCUSS] Graduate SINGA as a TLP

[Moaz Reyad]

Dear All,

Do you think we are ready to vote on graduation now? I can send the VOTE email 
if no one disagree.

For Alan's question, I checked SINGA proposal 
(https://cwiki.apache.org/confluence/display/incubator/SingaProposal) and it 
seems that there was an initial source code at the old repository 
(https://github.com/nusinga/singa). I assume that that source code was owned by 
the initial committers and they donated it to the Apache incubator under the 
Apache license. So there is no need for SGA.

Please correct me if this is not true. Otherwise, we assume this is the answer 
for Alan's question and we proceed with the graduation vote.

Thank you,
Moaz

On 2019/07/18 06:31:18, Moaz Reyad  wrote: 
> Thank you. If everyone agrees, I am going to send a [VOTE] email for
> graduation here in the dev mail list.
> 
> In the meantime, I hope someone from the initial committers can answer
> Alan's question below.
> 
> Also please remember that we need to finish the graduation resolution. (see
> SINGA-449)
> 
> Best regards,
> Moaz
> 
> On Wed, Jul 10, 2019 at 10:42 PM Alan Gates  wrote:
> 
> >
> > You've done releases and you've added new community members, plus you've
> > shown constant progress.  The only question I have left is the Whimsy page
> > notes that there is no Software Grant or IP clearance on file for Singa.
> > Did Singa come into the incubator with already existing software (if I
> > recall correctly it did)?  And if so, was a SGA filed for that?
> >
> > Alan.
> >
> > On 2019/03/08 23:41:36, Moaz Reyad  wrote:
> > > Hi All,
> > >
> > > Given the progress of SINGA graduation from the incubator (
> > > https://issues.apache.org/jira/browse/SINGA-405) and the complete
> > maturity
> > > assessment (
> > >
> > https://github.com/apache/incubator-singa/blob/91a4f7a7b8b913644299c7af48b042a867554290/doc/en/develop/maturity-model-assessment.md
> > ),
> > > I would like to discuss the remaining tasks for graduation.
> > >
> > > Please share your thoughts. Mentors advises are welcome.
> > >
> > > Best regards,
> > > Moaz
> > >
> >
> 

Re: New services for SINGA (Mentors help needed)

[Moaz Reyad]

Hi Wei,

Yes, the repo is : https://github.com/apache/incubator-singa-site

It can be updated using the standard git commands:

git clone https://github.com/apache/incubator-singa-site.git
git commit
and so on...

However, we still did not ask INFRA to update the pubsub to use git instead
of svn. So now the old SVN repository is still active and the new git
repository is not yet connected to the website (singa.apache.org).

We should create a ticket similar to this one:
https://issues.apache.org/jira/browse/INFRA-16990

and specify a git branch and a folder in the repo (
https://github.com/apache/incubator-singa-site) to be used as the main
folder of the website.

For instance, may be we use the master branch to store the "source code" of
the website, and use another branch such as "asf-site" to contain the
actual built website after running Sphinx site build script. Currently, the
source code of the website is at this folder in the original git repo:
https://github.com/apache/incubator-singa/tree/master/doc, and the master
branch of https://github.com/apache/incubator-singa-site contains the built
website.

We can complicate it further by using other git branches in
incubator-singa-site for different versions (1.0.0, 2.0.0, ..) and
different languages (Chinese, Korean, ..). Then the site build script
(build.sh) can be updated to perform "git clone" on them and build all of
them, and finally push them to the asf-site branch.

What do you think?
Moaz
On Sat, Aug 3, 2019 at 4:34 PM Wang Wei  wrote:

> Hi Moaz,
>
> If I want to update incubator-singa-site, what's the upstream to push to?
> Is there a repo at gitbox.apache.org?
> Thanks.
>
> Regards,
> Wei
>
> On Thu, Aug 1, 2019 at 8:33 PM Moaz Reyad  wrote:
>
> > The notebooks were not in the SVN. They are in singa github:
> >
> >
> https://github.com/apache/incubator-singa/tree/master/doc/en/docs/notebook
> >
> > Sphinx generates the website pages which contain links to the URLs in the
> > above folder.
> >
> > Regards,
> > Moaz
> >
> > On Thu, Jul 25, 2019 at 1:00 PM Wang Wei 
> wrote:
> >
> > > Thanks, Moaz!
> > > Github can display notebooks directly. But I cannot find the
> notebooks..
> > > Did Sphinx ignore them?
> > >
> > > Regards,
> > > Wei
> > >
> > > On Thu, Jul 25, 2019 at 6:12 PM Moaz Reyad  wrote:
> > >
> > > > I pushed the current site from SVN to the new repo:
> > > >
> > > > https://github.com/apache/incubator-singa-site
> > > >
> > > > Please check and if everything is fine, we can ask INFRA to perform
> the
> > > > switch to this new repository.
> > > >
> > > > Best regards,
> > > > Moaz
> > > >
> > > > On Thu, Jul 11, 2019 at 3:48 AM Wang Wei 
> > > wrote:
> > > >
> > > > > Thanks, Alan. We will start using the new repo for the website.
> > > > >
> > > > > Regards,
> > > > > Wei
> > > > >
> > > > > On Thu, Jul 11, 2019 at 4:14 AM Alan Gates 
> > > wrote:
> > > > >
> > > > > > I've created incubator-singa-site.git.  You should now be able to
> > > port
> > > > > the
> > > > > > contents over from the SVN site repo and then infra can switch
> your
> > > > > pubsub
> > > > > > from there.
> > > > > >
> > > > > > Alan.
> > > > > >
> > > > > > On Sun, Jun 30, 2019 at 6:41 AM Alan Gates  >
> > > > wrote:
> > > > > >
> > > > > > > I’m out on vacation and won’t be back until July 9th. I’ll be
> > happy
> > > > to
> > > > > do
> > > > > > > it then if one of the other mentors doesn’t get to it first.
> > > > > > >
> > > > > > > Alan.
> > > > > > >
> > > > > > > Sent from my iPhone
> > > > > > >
> > > > > > > > On Jun 30, 2019, at 04:47, Moaz Reyad 
> wrote:
> > > > > > > >
> > > > > > > > Dear Alan,
> > > > > > > >
> > > > > > > > Can we create the new git repository incubator-singa-site ?
> > > > > > > >
> > > > > > > > Thank you,
> > > > > > > > Moaz
> > > > > > > >
> > > > > > > >> On 2019/04/04 16:23:32, Moaz Reyad  wrote:
> >

Re: New services for SINGA (Mentors help needed)

[Moaz Reyad]

The notebooks were not in the SVN. They are in singa github:

https://github.com/apache/incubator-singa/tree/master/doc/en/docs/notebook

Sphinx generates the website pages which contain links to the URLs in the
above folder.

Regards,
Moaz

On Thu, Jul 25, 2019 at 1:00 PM Wang Wei  wrote:

> Thanks, Moaz!
> Github can display notebooks directly. But I cannot find the notebooks..
> Did Sphinx ignore them?
>
> Regards,
> Wei
>
> On Thu, Jul 25, 2019 at 6:12 PM Moaz Reyad  wrote:
>
> > I pushed the current site from SVN to the new repo:
> >
> > https://github.com/apache/incubator-singa-site
> >
> > Please check and if everything is fine, we can ask INFRA to perform the
> > switch to this new repository.
> >
> > Best regards,
> > Moaz
> >
> > On Thu, Jul 11, 2019 at 3:48 AM Wang Wei 
> wrote:
> >
> > > Thanks, Alan. We will start using the new repo for the website.
> > >
> > > Regards,
> > > Wei
> > >
> > > On Thu, Jul 11, 2019 at 4:14 AM Alan Gates 
> wrote:
> > >
> > > > I've created incubator-singa-site.git.  You should now be able to
> port
> > > the
> > > > contents over from the SVN site repo and then infra can switch your
> > > pubsub
> > > > from there.
> > > >
> > > > Alan.
> > > >
> > > > On Sun, Jun 30, 2019 at 6:41 AM Alan Gates 
> > wrote:
> > > >
> > > > > I’m out on vacation and won’t be back until July 9th. I’ll be happy
> > to
> > > do
> > > > > it then if one of the other mentors doesn’t get to it first.
> > > > >
> > > > > Alan.
> > > > >
> > > > > Sent from my iPhone
> > > > >
> > > > > > On Jun 30, 2019, at 04:47, Moaz Reyad  wrote:
> > > > > >
> > > > > > Dear Alan,
> > > > > >
> > > > > > Can we create the new git repository incubator-singa-site ?
> > > > > >
> > > > > > Thank you,
> > > > > > Moaz
> > > > > >
> > > > > >> On 2019/04/04 16:23:32, Moaz Reyad  wrote:
> > > > > >> Dear Alan,
> > > > > >>
> > > > > >> Thank you for the help.
> > > > > >>
> > > > > >> About Gitbox, the INFRA-17328 issue created a git repository for
> > the
> > > > > source
> > > > > >> code but not for the site.
> > > > > >>
> > > > > >> We would like to create a new git repository
> > (incubator-singa-site)
> > > > > instead
> > > > > >> of the current SVN repository (
> > > > > >> https://svn.apache.org/repos/asf/incubator/singa/site/)
> > > > > >>
> > > > > >> Thank you,
> > > > > >> Moaz
> > > > > >>
> > > > > >>> On Wed, Apr 3, 2019 at 7:49 PM Alan Gates 
> > > wrote:
> > > > > >>>
> > > > > >>> https://cwiki.apache.org/confluence/display/SINGA has been
> > > created.
> > > > > >>> Moaz, I've made you the admin, you should be able to add
> others.
> > > > > >>>
> > > > > >>> Regarding gitbox, it appears that is finished based on the
> JIRA.
> > > Is
> > > > > there
> > > > > >>> something more to do?
> > > > > >>>
> > > > > >>> I have submitted a request to create the security email list
> and
> > > made
> > > > > moaz
> > > > > >>> and wangwei the admins.  This is a private list, so you should
> > only
> > > > > accept
> > > > > >>> people on the PPMC or Apache members onto the list.
> > > > > >>>
> > > > > >>> Alan.
> > > > > >>>
> > > > > >>>> On Mon, Apr 1, 2019 at 1:08 AM Moaz Reyad 
> > > wrote:
> > > > > >>>>
> > > > > >>>> Dear SINGA mentors,
> > > > > >>>>
> > > > > >>>> What is your advice about this request to add new services for
> > > > SINGA?
> > > > > >>>>
> > > > > >>>> Best regards
> > > > > >>>&g

Re: New services for SINGA (Mentors help needed)

[Moaz Reyad]

I pushed the current site from SVN to the new repo:

https://github.com/apache/incubator-singa-site

Please check and if everything is fine, we can ask INFRA to perform the
switch to this new repository.

Best regards,
Moaz

On Thu, Jul 11, 2019 at 3:48 AM Wang Wei  wrote:

> Thanks, Alan. We will start using the new repo for the website.
>
> Regards,
> Wei
>
> On Thu, Jul 11, 2019 at 4:14 AM Alan Gates  wrote:
>
> > I've created incubator-singa-site.git.  You should now be able to port
> the
> > contents over from the SVN site repo and then infra can switch your
> pubsub
> > from there.
> >
> > Alan.
> >
> > On Sun, Jun 30, 2019 at 6:41 AM Alan Gates  wrote:
> >
> > > I’m out on vacation and won’t be back until July 9th. I’ll be happy to
> do
> > > it then if one of the other mentors doesn’t get to it first.
> > >
> > > Alan.
> > >
> > > Sent from my iPhone
> > >
> > > > On Jun 30, 2019, at 04:47, Moaz Reyad  wrote:
> > > >
> > > > Dear Alan,
> > > >
> > > > Can we create the new git repository incubator-singa-site ?
> > > >
> > > > Thank you,
> > > > Moaz
> > > >
> > > >> On 2019/04/04 16:23:32, Moaz Reyad  wrote:
> > > >> Dear Alan,
> > > >>
> > > >> Thank you for the help.
> > > >>
> > > >> About Gitbox, the INFRA-17328 issue created a git repository for the
> > > source
> > > >> code but not for the site.
> > > >>
> > > >> We would like to create a new git repository (incubator-singa-site)
> > > instead
> > > >> of the current SVN repository (
> > > >> https://svn.apache.org/repos/asf/incubator/singa/site/)
> > > >>
> > > >> Thank you,
> > > >> Moaz
> > > >>
> > > >>> On Wed, Apr 3, 2019 at 7:49 PM Alan Gates 
> wrote:
> > > >>>
> > > >>> https://cwiki.apache.org/confluence/display/SINGA has been
> created.
> > > >>> Moaz, I've made you the admin, you should be able to add others.
> > > >>>
> > > >>> Regarding gitbox, it appears that is finished based on the JIRA.
> Is
> > > there
> > > >>> something more to do?
> > > >>>
> > > >>> I have submitted a request to create the security email list and
> made
> > > moaz
> > > >>> and wangwei the admins.  This is a private list, so you should only
> > > accept
> > > >>> people on the PPMC or Apache members onto the list.
> > > >>>
> > > >>> Alan.
> > > >>>
> > > >>>> On Mon, Apr 1, 2019 at 1:08 AM Moaz Reyad 
> wrote:
> > > >>>>
> > > >>>> Dear SINGA mentors,
> > > >>>>
> > > >>>> What is your advice about this request to add new services for
> > SINGA?
> > > >>>>
> > > >>>> Best regards
> > > >>>> Moaz
> > > >>>>
> > > >>>> -- Forwarded message -
> > > >>>> From: Moaz Reyad 
> > > >>>> Date: Sat, Mar 9, 2019 at 11:39 AM
> > > >>>> Subject: New services for SINGA (Mentors help needed)
> > > >>>> To: 
> > > >>>>
> > > >>>>
> > > >>>> Hi All,
> > > >>>>
> > > >>>> I would like to propose three new services for SINGA. These
> services
> > > can
> > > >>>> be requested from (https://selfserve.apache.org/) but I do not
> have
> > > >>>> permission to create them. I opened an INFRA ticket (
> > > >>>> https://issues.apache.org/jira/browse/INFRA-17981), but the INFRA
> > > team
> > > >>>> suggested that we ask assistance from mentors.
> > > >>>>
> > > >>>> 1. Confluence wiki:
> > > >>>>
> > > >>>> We need to create a space for SINGA at the Confluence wiki. The
> wiki
> > > is
> > > >>>> required to keep the development pages which are not directly
> useful
> > > to
> > > >>>> SINGA users. For example: the development schedule, how to
> prepare a
> > > >>>> release, maturity assessment, etc.
&

Re: [DISCUSS] Graduate SINGA as a TLP

[Moaz Reyad]

Thank you. If everyone agrees, I am going to send a [VOTE] email for
graduation here in the dev mail list.

In the meantime, I hope someone from the initial committers can answer
Alan's question below.

Also please remember that we need to finish the graduation resolution. (see
SINGA-449)

Best regards,
Moaz

On Wed, Jul 10, 2019 at 10:42 PM Alan Gates  wrote:

>
> You've done releases and you've added new community members, plus you've
> shown constant progress.  The only question I have left is the Whimsy page
> notes that there is no Software Grant or IP clearance on file for Singa.
> Did Singa come into the incubator with already existing software (if I
> recall correctly it did)?  And if so, was a SGA filed for that?
>
> Alan.
>
> On 2019/03/08 23:41:36, Moaz Reyad  wrote:
> > Hi All,
> >
> > Given the progress of SINGA graduation from the incubator (
> > https://issues.apache.org/jira/browse/SINGA-405) and the complete
> maturity
> > assessment (
> >
> https://github.com/apache/incubator-singa/blob/91a4f7a7b8b913644299c7af48b042a867554290/doc/en/develop/maturity-model-assessment.md
> ),
> > I would like to discuss the remaining tasks for graduation.
> >
> > Please share your thoughts. Mentors advises are welcome.
> >
> > Best regards,
> > Moaz
> >
>

[jira] [Commented] (SINGA-466) Installation instructions on Centos7 of SINGA

[Moaz Reyad (JIRA)]

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

Moaz Reyad commented on SINGA-466:
--

Thank you for this information. You may proceed and add them to the 
[installation 
page|https://github.com/apache/incubator-singa/blob/master/doc/en/docs/installation.md]
 in SINGA documentation.

You need to fork the SINGA repo in your local account, make the changes then 
create a pull request. The process is described 
[here|http://singa.apache.org/develop/contribute-code.html#pull-request].

Check [how to contribute 
docs|http://singa.apache.org/develop/contribute-docs.html] page for more 
details.

> Installation instructions on Centos7 of SINGA
> -
>
> Key: SINGA-466
> URL: https://issues.apache.org/jira/browse/SINGA-466
> Project: Singa
>  Issue Type: Task
>  Components: Application
>Reporter: Shreyansh Shrivastava
>Priority: Major
>  Labels: Installation
>
> I installed SINGA on Centos7, the dependencies had to be installed 
> separately. I am listing the commands that I followed. 
> *Dependencies installation*
> **
>  * sudo yum install freetype-devel libXft-devel ncurses-devel openblas-devel 
> blas-devel lapack devel atlas-devel kernel-headers unzip wget pkgconfig zip 
> zlib-devel libcurl-devel cmake curl unzip dh-autoreconf git python-devel 
> glog-devel protobuf-devel
>  * 
> yum group install "Development Tools"
>  * 
> _For installing swig_
> sudo yum install pcre-devel
> wget http://prdownloads.sourceforge.net/swig/swig-3.0.5.tar.gz
> tar xvzf swig-3.0.5.tar.gz
> cd swig-3.0.5.tar.gz
> ./configure --prefix=${RUN}
> make
> make install
>  * _For installing gfortran_
> yum install centos-release-scl-rh
> yum --enablerepo=centos-sclo-rh-testing install devtoolset-7-gcc-gfortran
>  * _For installing pip and other packages_
> sudo yum install epel-release
> sudo yum install python-pip
> pip install matplotlib numpy pandas scikit-learn pydot
> *Installation*
>  * 
> mkdir build
> cd build
> cmake -DUSE_MODULES=ON ..
> make
>  * 
> _Goto python folder_
> pip install -e
> *Testing*
>  * 
> ./bin/test_singa
> If SINGA passes all tests, then you have successfully installed SINGA.



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

Re: New services for SINGA (Mentors help needed)

[Moaz Reyad]

Dear Alan,

Can we create the new git repository incubator-singa-site ?

Thank you,
Moaz

On 2019/04/04 16:23:32, Moaz Reyad  wrote: 
> Dear Alan,
> 
> Thank you for the help.
> 
> About Gitbox, the INFRA-17328 issue created a git repository for the source
> code but not for the site.
> 
> We would like to create a new git repository (incubator-singa-site) instead
> of the current SVN repository (
> https://svn.apache.org/repos/asf/incubator/singa/site/)
> 
> Thank you,
> Moaz
> 
> On Wed, Apr 3, 2019 at 7:49 PM Alan Gates  wrote:
> 
> > https://cwiki.apache.org/confluence/display/SINGA has been created.
> > Moaz, I've made you the admin, you should be able to add others.
> >
> > Regarding gitbox, it appears that is finished based on the JIRA.  Is there
> > something more to do?
> >
> > I have submitted a request to create the security email list and made moaz
> > and wangwei the admins.  This is a private list, so you should only accept
> > people on the PPMC or Apache members onto the list.
> >
> > Alan.
> >
> > On Mon, Apr 1, 2019 at 1:08 AM Moaz Reyad  wrote:
> >
> >> Dear SINGA mentors,
> >>
> >> What is your advice about this request to add new services for SINGA?
> >>
> >> Best regards
> >> Moaz
> >>
> >> -- Forwarded message -
> >> From: Moaz Reyad 
> >> Date: Sat, Mar 9, 2019 at 11:39 AM
> >> Subject: New services for SINGA (Mentors help needed)
> >> To: 
> >>
> >>
> >> Hi All,
> >>
> >> I would like to propose three new services for SINGA. These services can
> >> be requested from (https://selfserve.apache.org/) but I do not have
> >> permission to create them. I opened an INFRA ticket (
> >> https://issues.apache.org/jira/browse/INFRA-17981), but the INFRA team
> >> suggested that we ask assistance from mentors.
> >>
> >> 1. Confluence wiki:
> >>
> >> We need to create a space for SINGA at the Confluence wiki. The wiki is
> >> required to keep the development pages which are not directly useful to
> >> SINGA users. For example: the development schedule, how to prepare a
> >> release, maturity assessment, etc.
> >>
> >> This issue was open before (
> >> https://issues.apache.org/jira/browse/INFRA-9473) but it was not
> >> completed.
> >>
> >> Please add my account:
> >>
> >> Wiki: https://cwiki.apache.org/confluence/display/~moazreyad
> >> Apache ID: moaz
> >>
> >> SINGA team members who would like to contribute to the wiki may share
> >> their wiki account, so they can have the write permission on the wiki 
> >> pages.
> >>
> >> We can also try to enable the GitHub wiki, but I think Apache does not
> >> allow this any more and the ASF encourages the use of Confluence instead.
> >>
> >> 2. GitBox repository for incubator-singa-site:
> >>
> >> This is required to move the singa site from SVN to Git. For more
> >> information see (https://issues.apache.org/jira/browse/INFRA-17328)
> >>
> >> 3. Security mail list:
> >>
> >> We would like to create the private address: secur...@singa.apache.org
> >> for security issues. There are some vulnerabilities already reported to
> >> SINGA and we need to resolve them. The security mail list will help in
> >> handling current and future security issues.
> >>
> >> Please add wang...@apache.org to this private mail list. For more
> >> information see (https://issues.apache.org/jira/browse/SINGA-417). SINGA
> >> team members who would like to join the security team may also share their
> >> email.
> >>
> >> Best regards,
> >> Moaz
> >>
> >
> 

[jira] [Commented] (SINGA-461) June Report Draft

[Moaz Reyad (JIRA)]

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

Moaz Reyad commented on SINGA-461:
--

This issue can be closed now.

p.s. I don't know why I don't have permissions to change status of issues or 
close them, or assign them to myself or to someone.

> June Report Draft
> -
>
> Key: SINGA-461
> URL: https://issues.apache.org/jira/browse/SINGA-461
> Project: Singa
>  Issue Type: Task
>Reporter: wangwei
>Priority: Major
>
> Hi all,
>  
> Here is a draft for June report.
> Pls add your comments here or update the report directly 
> [https://cwiki.apache.org/confluence/display/INCUBATOR/June2019]
>  
> h3. [Three most important unfinished issues to address before 
> graduating:|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#three-most-important-unfinished-issues-to-address-before-graduating-18]
>  # Update the website to be consistent with the latest code and fix some 
> errors.
>  # Integrate the Rafiki component
>  # 
> h3. [Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be 
> aware 
> of?|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#any-issues-that-the-incubator-pmc-ipmc-or-asf-board-wishneed-to-be-aware-of-18]
> N.A
> h3. [How has the community developed since the last 
> report?|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#how-has-the-community-developed-since-the-last-report-18]
>  * SINGA developers participated EU FOSSA Apache Hackathon, and discussed 
> with other Apache projects (e.g., PLC4X) on collaboration and community 
> building. Multiple new contributors from the Hackathon have made pull 
> requests.
>  * SINGA committers are collaborating with SpamAssassin on a GSoC2019 project.
>  * Currently, we have 43 contributors, 1678 starts and 416 forks on github.
> h3. [How has the project developed since the last 
> report?|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#how-has-the-project-developed-since-the-last-report-18]
>  * Version 2.0 has been released.
>  * We have fixed some issues for gradution including the logo, Apache Website 
> Navigation Links Policy, etc.
>  * There are about 90 commits (including Rafiki) since last report.
>  * There are 165, 125 and 92 emails on dev@ list for March, April and May 
> respectively.



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

[jira] [Commented] (SINGA-405) Graduate Apache SINGA (incubating) as a TLP

[Moaz Reyad (JIRA)]

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

Moaz Reyad commented on SINGA-405:
--

This issue is waiting since months for the team to reply and discuss [Graduate 
SINGA as a 
TLP|https://lists.apache.org/thread.html/dc37e2c7614f0f7f0f91d0451ddeff1d253b1d05bfeb3c4797fefa0e@%3Cdev.singa.apache.org%3E].

We can not proceed without the mentors and developers agree and vote to 
continue the graduation. Please everyone participate in the discussion (using 
the mail list thread above) with your opinion and feedback.

> 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
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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)

Re: [jira] [Commented] (SINGA-449) Preparing Podling TLP resolution

[Moaz Reyad]

Hi Wei,

The only requirement I know is that the PMC chair should be one of the PPMC
members.

Best regards,
Moaz

On Thu, Jun 27, 2019 at 7:28 AM Wang Wei  wrote:

>  Hi Moaz,
>
> Any specific requirements or eligibility criteria for the PMC chair?
>
> Regards,
> Wei
>
> On Thu, Jun 27, 2019 at 10:14 AM Moaz Reyad (JIRA) 
> wrote:
>
> >
> > [
> >
> https://issues.apache.org/jira/browse/SINGA-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16873757#comment-16873757
> > ]
> >
> > Moaz Reyad commented on SINGA-449:
> > --
> >
> > This issue is still waiting for discussion. We need to choose the project
> > chair (in the private list) and the initial project members to complete
> the
> > Podling TLP resolution.
> >
> > Should we copy all the current ppmc members to the list of initial
> project
> > members without asking their permission (assuming everyone agrees) or we
> > must ask every member to explicitly agree to be added to the initial
> > project members?
> >
> > > Preparing Podling TLP resolution
> > > 
> > >
> > > Key: SINGA-449
> > > URL: https://issues.apache.org/jira/browse/SINGA-449
> > > Project: Singa
> > >  Issue Type: Task
> > >Reporter: Moaz Reyad
> > >Priority: Major
> > >
> > > This issue is for preparing the graduation resolution for SINGA given
> > the [template|
> >
> https://svn.apache.org/repos/private/committers/board/templates/podling-tlp-resolution.txt
> > ].
> > > The resolution draft for SINGA is [here|
> > https://cwiki.apache.org/confluence/display/SINGA/Graduation+Resolution
> ].
> > > Please check it and give your feedback.
> > > SINGA PPMC need to discuss and choose the project Chair (see private
> > mail list).
> > > We also need to specify initial project members. We can copy all the
> > current members without asking their permission (assuming everyone
> agrees)
> > or we may ask every member to explicitly agree to be added to the initial
> > project members.
> >
> >
> >
> > --
> > This message was sent by Atlassian JIRA
> > (v7.6.3#76005)
> >
>

[jira] [Commented] (SINGA-449) Preparing Podling TLP resolution

[Moaz Reyad (JIRA)]

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

Moaz Reyad commented on SINGA-449:
--

This issue is still waiting for discussion. We need to choose the project chair 
(in the private list) and the initial project members to complete the Podling 
TLP resolution. 

Should we copy all the current ppmc members to the list of initial project 
members without asking their permission (assuming everyone agrees) or we must 
ask every member to explicitly agree to be added to the initial project members?

> Preparing Podling TLP resolution
> 
>
> Key: SINGA-449
> URL: https://issues.apache.org/jira/browse/SINGA-449
> Project: Singa
>  Issue Type: Task
>Reporter: Moaz Reyad
>Priority: Major
>
> This issue is for preparing the graduation resolution for SINGA given the 
> [template|https://svn.apache.org/repos/private/committers/board/templates/podling-tlp-resolution.txt].
> The resolution draft for SINGA is 
> [here|https://cwiki.apache.org/confluence/display/SINGA/Graduation+Resolution].
> Please check it and give your feedback.
> SINGA PPMC need to discuss and choose the project Chair (see private mail 
> list).
> We also need to specify initial project members. We can copy all the current 
> members without asking their permission (assuming everyone agrees) or we may 
> ask every member to explicitly agree to be added to the initial project 
> members.



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

Re: [jira] [Commented] (SINGA-461) June Report Draft

[Moaz Reyad]

Ok. I updated the cwiki. Although the deadline for changes was passed
and the report was already signed. I hope this is fine.

Let's try to finish these three issues, so we can complete the graduation.

Moaz

On 6/6/2019 4:50 AM, Wei Wang wrote:
> Thanks, Moaz!
> Could you update the cwiki website directly?
>
>
>> On 5 Jun 2019, at 7:16 PM, Moaz Reyad (JIRA)  wrote:
>>
>>
>>[ 
>> https://issues.apache.org/jira/browse/SINGA-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16856601#comment-16856601
>>  ] 
>>
>> Moaz Reyad commented on SINGA-461:
>> --
>>
>> I think the [Three most important unfinished issues to address before 
>> graduating 
>> |https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#three-most-important-unfinished-issues-to-address-before-graduating-18]
>>  section should contain issues related to graduating from the incubator and 
>> not general issues like website update and rafiki integration. These general 
>> issues do not block the graduation and they are independent from the 
>> graduation tasks.
>>
>> The most important issues to address before graduation (in my opinion) are:
>> 1. [Choosing the project PMC 
>> chair|https://lists.apache.org/thread.html/ce3c626d22ecf520d73cd5add269cf1993f1d253dd6f6ce13446d44b@%3Cprivate.singa.apache.org%3E].
>> 2. Finalize the [Graduation 
>> Resolution|https://cwiki.apache.org/confluence/display/SINGA/Graduation+Resolution].
>>  Missing parts are marked in red.
>> 3. 
>> [Discuss|https://lists.apache.org/thread.html/dc37e2c7614f0f7f0f91d0451ddeff1d253b1d05bfeb3c4797fefa0e@%3Cdev.singa.apache.org%3E]
>>  and Vote with mentors and team members on the mail list if there is any 
>> other missing issue before graduation.
>>
>>> June Report Draft
>>> -
>>>
>>>Key: SINGA-461
>>>URL: https://issues.apache.org/jira/browse/SINGA-461
>>>Project: Singa
>>> Issue Type: Task
>>>   Reporter: wangwei
>>>   Priority: Major
>>>
>>> Hi all,
>>>  
>>> Here is a draft for June report.
>>> Pls add your comments here or update the report directly 
>>> [https://cwiki.apache.org/confluence/display/INCUBATOR/June2019]
>>>  
>>> h3. [Three most important unfinished issues to address before 
>>> graduating:|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#three-most-important-unfinished-issues-to-address-before-graduating-18]
>>> # Update the website to be consistent with the latest code and fix some 
>>> errors.
>>> # Integrate the Rafiki component
>>> # 
>>> h3. [Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be 
>>> aware 
>>> of?|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#any-issues-that-the-incubator-pmc-ipmc-or-asf-board-wishneed-to-be-aware-of-18]
>>> N.A
>>> h3. [How has the community developed since the last 
>>> report?|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#how-has-the-community-developed-since-the-last-report-18]
>>> * SINGA developers participated EU FOSSA Apache Hackathon, and discussed 
>>> with other Apache projects (e.g., PLC4X) on collaboration and community 
>>> building. Multiple new contributors from the Hackathon have made pull 
>>> requests.
>>> * SINGA committers are collaborating with SpamAssassin on a GSoC2019 
>>> project.
>>> * Currently, we have 43 contributors, 1678 starts and 416 forks on github.
>>> h3. [How has the project developed since the last 
>>> report?|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#how-has-the-project-developed-since-the-last-report-18]
>>> * Version 2.0 has been released.
>>> * We have fixed some issues for gradution including the logo, Apache 
>>> Website Navigation Links Policy, etc.
>>> * There are about 90 commits (including Rafiki) since last report.
>>> * There are 165, 125 and 92 emails on dev@ list for March, April and May 
>>> respectively.
>>
>>
>> --
>> This message was sent by Atlassian JIRA
>> (v7.6.3#76005)

[jira] [Issue Comment Deleted] (SINGA-445) can not run Singa module example

[Moaz Reyad (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SINGA-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Moaz Reyad updated SINGA-445:
-
Comment: was deleted

(was: I think the [Three most important unfinished issues to address before 
graduating 
|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#three-most-important-unfinished-issues-to-address-before-graduating-18]
 section should contain issues related to graduating from the incubator and not 
general issues like website update and rafiki integration. These general issues 
do not block the graduation and they are independent from the graduation tasks.

The most important issues to address before graduation (in my opinion) are:
 1. [Choosing the project PMC 
chair|https://lists.apache.org/thread.html/ce3c626d22ecf520d73cd5add269cf1993f1d253dd6f6ce13446d44b@%3Cprivate.singa.apache.org%3E].
 2. Finalize the [Graduation 
Resolution|https://cwiki.apache.org/confluence/display/SINGA/Graduation+Resolution].
 Missing parts are marked in red.
 3. 
[Discuss|https://lists.apache.org/thread.html/dc37e2c7614f0f7f0f91d0451ddeff1d253b1d05bfeb3c4797fefa0e@%3Cdev.singa.apache.org%3E]
 and Vote with mentors and team members on the mail list if there is any other 
missing issue before graduation.)

> can not run Singa module example
> 
>
> Key: SINGA-445
> URL: https://issues.apache.org/jira/browse/SINGA-445
> Project: Singa
>  Issue Type: Bug
>  Components: Documentation
> Environment: - Ubuntu 18.10
> - python 3.6
>Reporter: thao p nguyen
>Priority: Critical
>
> Following the latest Singa documentation's examples on running modules, below 
> error was found  for running module Metric:
> >>> from singa import tensor
> >>> from singa import metric
> >>> x = tensor.Tensor((3, 5))
> >>> x.uniform(0, 1) # randomly generate the prediction activation
> >>> x = tensor.SoftMax # normalize the prediction into probabilities
> Traceback (most recent call last):
> File "", line 1, in 
> AttributeError: module 'singa.tensor' has no attribute 'SoftMax'
> >>> y = tensor.from_numpy(np.array([0, 1, 3], dtype=np.int)) # set the truth
> Traceback (most recent call last):
> File "", line 1, in 
> NameError: name 'np' is not defined
> >>>
> >>> f = metric.Accuracy()
> >>> acc = f.evaluate(x, y) # averaged accuracy over all 3 samples in x
>  



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

[jira] [Commented] (SINGA-461) June Report Draft

[Moaz Reyad (JIRA)]

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

Moaz Reyad commented on SINGA-461:
--

I think the [Three most important unfinished issues to address before 
graduating 
|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#three-most-important-unfinished-issues-to-address-before-graduating-18]
 section should contain issues related to graduating from the incubator and not 
general issues like website update and rafiki integration. These general issues 
do not block the graduation and they are independent from the graduation tasks.

The most important issues to address before graduation (in my opinion) are:
 1. [Choosing the project PMC 
chair|https://lists.apache.org/thread.html/ce3c626d22ecf520d73cd5add269cf1993f1d253dd6f6ce13446d44b@%3Cprivate.singa.apache.org%3E].
 2. Finalize the [Graduation 
Resolution|https://cwiki.apache.org/confluence/display/SINGA/Graduation+Resolution].
 Missing parts are marked in red.
 3. 
[Discuss|https://lists.apache.org/thread.html/dc37e2c7614f0f7f0f91d0451ddeff1d253b1d05bfeb3c4797fefa0e@%3Cdev.singa.apache.org%3E]
 and Vote with mentors and team members on the mail list if there is any other 
missing issue before graduation.

> June Report Draft
> -
>
> Key: SINGA-461
> URL: https://issues.apache.org/jira/browse/SINGA-461
> Project: Singa
>  Issue Type: Task
>Reporter: wangwei
>Priority: Major
>
> Hi all,
>  
> Here is a draft for June report.
> Pls add your comments here or update the report directly 
> [https://cwiki.apache.org/confluence/display/INCUBATOR/June2019]
>  
> h3. [Three most important unfinished issues to address before 
> graduating:|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#three-most-important-unfinished-issues-to-address-before-graduating-18]
>  # Update the website to be consistent with the latest code and fix some 
> errors.
>  # Integrate the Rafiki component
>  # 
> h3. [Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be 
> aware 
> of?|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#any-issues-that-the-incubator-pmc-ipmc-or-asf-board-wishneed-to-be-aware-of-18]
> N.A
> h3. [How has the community developed since the last 
> report?|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#how-has-the-community-developed-since-the-last-report-18]
>  * SINGA developers participated EU FOSSA Apache Hackathon, and discussed 
> with other Apache projects (e.g., PLC4X) on collaboration and community 
> building. Multiple new contributors from the Hackathon have made pull 
> requests.
>  * SINGA committers are collaborating with SpamAssassin on a GSoC2019 project.
>  * Currently, we have 43 contributors, 1678 starts and 416 forks on github.
> h3. [How has the project developed since the last 
> report?|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#how-has-the-project-developed-since-the-last-report-18]
>  * Version 2.0 has been released.
>  * We have fixed some issues for gradution including the logo, Apache Website 
> Navigation Links Policy, etc.
>  * There are about 90 commits (including Rafiki) since last report.
>  * There are 165, 125 and 92 emails on dev@ list for March, April and May 
> respectively.



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

[jira] [Commented] (SINGA-445) can not run Singa module example

[Moaz Reyad (JIRA)]

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

Moaz Reyad commented on SINGA-445:
--

I think the [Three most important unfinished issues to address before 
graduating 
|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#three-most-important-unfinished-issues-to-address-before-graduating-18]
 section should contain issues related to graduating from the incubator and not 
general issues like website update and rafiki integration. These general issues 
do not block the graduation and they are independent from the graduation tasks.

The most important issues to address before graduation (in my opinion) are:
 1. [Choosing the project PMC 
chair|https://lists.apache.org/thread.html/ce3c626d22ecf520d73cd5add269cf1993f1d253dd6f6ce13446d44b@%3Cprivate.singa.apache.org%3E].
 2. Finalize the [Graduation 
Resolution|https://cwiki.apache.org/confluence/display/SINGA/Graduation+Resolution].
 Missing parts are marked in red.
 3. 
[Discuss|https://lists.apache.org/thread.html/dc37e2c7614f0f7f0f91d0451ddeff1d253b1d05bfeb3c4797fefa0e@%3Cdev.singa.apache.org%3E]
 and Vote with mentors and team members on the mail list if there is any other 
missing issue before graduation.

> can not run Singa module example
> 
>
> Key: SINGA-445
> URL: https://issues.apache.org/jira/browse/SINGA-445
> Project: Singa
>  Issue Type: Bug
>  Components: Documentation
> Environment: - Ubuntu 18.10
> - python 3.6
>Reporter: thao p nguyen
>Priority: Critical
>
> Following the latest Singa documentation's examples on running modules, below 
> error was found  for running module Metric:
> >>> from singa import tensor
> >>> from singa import metric
> >>> x = tensor.Tensor((3, 5))
> >>> x.uniform(0, 1) # randomly generate the prediction activation
> >>> x = tensor.SoftMax # normalize the prediction into probabilities
> Traceback (most recent call last):
> File "", line 1, in 
> AttributeError: module 'singa.tensor' has no attribute 'SoftMax'
> >>> y = tensor.from_numpy(np.array([0, 1, 3], dtype=np.int)) # set the truth
> Traceback (most recent call last):
> File "", line 1, in 
> NameError: name 'np' is not defined
> >>>
> >>> f = metric.Accuracy()
> >>> acc = f.evaluate(x, y) # averaged accuracy over all 3 samples in x
>  



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

[jira] [Commented] (SINGA-455) Adding SINGA logo to Apache logos

[Moaz Reyad (JIRA)]

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

Moaz Reyad commented on SINGA-455:
--

No. I think there is no need to add the incubating word. The incubating 
projects did not add it.

And singa is going to be graduated hopefully soon. I think the graduation 
requirements are satisfied and it is up to the singa team to decide when should 
we proceed with the graduation.

> Adding SINGA logo to Apache logos
> -
>
> Key: SINGA-455
> URL: https://issues.apache.org/jira/browse/SINGA-455
> Project: Singa
>  Issue Type: Task
>Reporter: Moaz Reyad
>Priority: Major
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> SINGA logo is not found in [Apache logos|http://apache.org/logos/].
> We need the SINGA logo in a scalable format (svg, eps, ai, pdf accepted). If 
> this is not available, may be we can ask a graphic designer to prepare it.
> Since SINGA logo is missing, it does not appear in 
> [montages|http://apache.org/logos/montages/] and 
> [powered-by|http://apache.org/logos/poweredby/] collections. It can be missed 
> also from many other places where it is required to have the official 
> scalable logo from Apache printed on posters, banners or large screens. 
>   
>  Fore more information, check [http://apache.org/logos/about.html]
> I suggest to add the project name "SINGA" to the official logo. Almost all 
> the logos in the [Apache logos|http://apache.org/logos/] collection have 
> their name in the logo. We may ask the graphics designer to add SINGA below 
> (or in another place) the logo using a suitable artistic font.



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

[jira] [Commented] (SINGA-455) Adding SINGA logo to Apache logos

[Moaz Reyad (JIRA)]

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

Moaz Reyad commented on SINGA-455:
--

The next step is to update the logo in the [website | http://singa.apache.org] 
and external pages (wikipedia, facebook, linkedin, ..)

We may contact the companies and projects that use the old SINGA logo in their 
websites (e.g. shentilium, foodlg, medilot, ..) and ask them to replace the old 
logo with the [powered by logo|http://www.apache.org/logos/poweredby/singa.png].



> Adding SINGA logo to Apache logos
> -
>
> Key: SINGA-455
> URL: https://issues.apache.org/jira/browse/SINGA-455
> Project: Singa
>  Issue Type: Task
>Reporter: Moaz Reyad
>Priority: Major
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> SINGA logo is not found in [Apache logos|http://apache.org/logos/].
> We need the SINGA logo in a scalable format (svg, eps, ai, pdf accepted). If 
> this is not available, may be we can ask a graphic designer to prepare it.
> Since SINGA logo is missing, it does not appear in 
> [montages|http://apache.org/logos/montages/] and 
> [powered-by|http://apache.org/logos/poweredby/] collections. It can be missed 
> also from many other places where it is required to have the official 
> scalable logo from Apache printed on posters, banners or large screens. 
>   
>  Fore more information, check [http://apache.org/logos/about.html]
> I suggest to add the project name "SINGA" to the official logo. Almost all 
> the logos in the [Apache logos|http://apache.org/logos/] collection have 
> their name in the logo. We may ask the graphics designer to add SINGA below 
> (or in another place) the logo using a suitable artistic font.



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

[jira] [Resolved] (SINGA-455) Adding SINGA logo to Apache logos

[Moaz Reyad (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SINGA-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Moaz Reyad resolved SINGA-455.
--
Resolution: Fixed

The logo is here: http://www.apache.org/logos/#singa

> Adding SINGA logo to Apache logos
> -
>
> Key: SINGA-455
> URL: https://issues.apache.org/jira/browse/SINGA-455
> Project: Singa
>  Issue Type: Task
>    Reporter: Moaz Reyad
>Priority: Major
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> SINGA logo is not found in [Apache logos|http://apache.org/logos/].
> We need the SINGA logo in a scalable format (svg, eps, ai, pdf accepted). If 
> this is not available, may be we can ask a graphic designer to prepare it.
> Since SINGA logo is missing, it does not appear in 
> [montages|http://apache.org/logos/montages/] and 
> [powered-by|http://apache.org/logos/poweredby/] collections. It can be missed 
> also from many other places where it is required to have the official 
> scalable logo from Apache printed on posters, banners or large screens. 
>   
>  Fore more information, check [http://apache.org/logos/about.html]
> I suggest to add the project name "SINGA" to the official logo. Almost all 
> the logos in the [Apache logos|http://apache.org/logos/] collection have 
> their name in the logo. We may ask the graphics designer to add SINGA below 
> (or in another place) the logo using a suitable artistic font.



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

[jira] [Closed] (SINGA-455) Adding SINGA logo to Apache logos

[Moaz Reyad (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SINGA-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Moaz Reyad closed SINGA-455.


> Adding SINGA logo to Apache logos
> -
>
> Key: SINGA-455
> URL: https://issues.apache.org/jira/browse/SINGA-455
> Project: Singa
>  Issue Type: Task
>    Reporter: Moaz Reyad
>Priority: Major
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> SINGA logo is not found in [Apache logos|http://apache.org/logos/].
> We need the SINGA logo in a scalable format (svg, eps, ai, pdf accepted). If 
> this is not available, may be we can ask a graphic designer to prepare it.
> Since SINGA logo is missing, it does not appear in 
> [montages|http://apache.org/logos/montages/] and 
> [powered-by|http://apache.org/logos/poweredby/] collections. It can be missed 
> also from many other places where it is required to have the official 
> scalable logo from Apache printed on posters, banners or large screens. 
>   
>  Fore more information, check [http://apache.org/logos/about.html]
> I suggest to add the project name "SINGA" to the official logo. Almost all 
> the logos in the [Apache logos|http://apache.org/logos/] collection have 
> their name in the logo. We may ask the graphics designer to add SINGA below 
> (or in another place) the logo using a suitable artistic font.



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

[jira] [Commented] (SINGA-455) Adding SINGA logo to Apache logos

[Moaz Reyad (JIRA)]

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

Moaz Reyad commented on SINGA-455:
--

I think it is fine. I will add it to the Apache logos and see if everyone 
agrees on it or if we need to change it.

> Adding SINGA logo to Apache logos
> -
>
> Key: SINGA-455
> URL: https://issues.apache.org/jira/browse/SINGA-455
> Project: Singa
>  Issue Type: Task
>Reporter: Moaz Reyad
>Priority: Major
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> SINGA logo is not found in [Apache logos|http://apache.org/logos/].
> We need the SINGA logo in a scalable format (svg, eps, ai, pdf accepted). If 
> this is not available, may be we can ask a graphic designer to prepare it.
> Since SINGA logo is missing, it does not appear in 
> [montages|http://apache.org/logos/montages/] and 
> [powered-by|http://apache.org/logos/poweredby/] collections. It can be missed 
> also from many other places where it is required to have the official 
> scalable logo from Apache printed on posters, banners or large screens. 
>   
>  Fore more information, check [http://apache.org/logos/about.html]
> I suggest to add the project name "SINGA" to the official logo. Almost all 
> the logos in the [Apache logos|http://apache.org/logos/] collection have 
> their name in the logo. We may ask the graphics designer to add SINGA below 
> (or in another place) the logo using a suitable artistic font.



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

[jira] [Created] (SINGA-459) Remove support for Python 2.7

[Moaz Reyad (JIRA)]

Moaz Reyad created SINGA-459:


 Summary: Remove support for Python 2.7
 Key: SINGA-459
 URL: https://issues.apache.org/jira/browse/SINGA-459
 Project: Singa
  Issue Type: Improvement
Reporter: Moaz Reyad


The [support of Python 2 will end soon|https://pythonclock.org/] and some 
projects already stopped supporting it. (For 
example,[scikit-learn|https://github.com/scikit-learn/scikit-learn#installation]
 0.20 was the last version to support Python2.7).

If everyone agrees, we can plan to remove the Python 2 support from SINGA 
starting from the next release.

This will help in improving the python code and simplifying the building 
process.

For the code improvement: currently the code uses 'future' library to support 
both python 2 and 3. This will not be needed if only python 3 code is 
supported. There is also string encoding code that is complicated by the need 
to be backward compatible with python 2.

For the building process: the build options will contain only python 3 by 
default. The developers will not confuse python 2 and python 3 options and 
dependencies. Testing will be easier because only python 3 scenarios will be 
tested.



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

[jira] [Commented] (SINGA-433) Preparation for V2.0 release

[Moaz Reyad (JIRA)]

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

Moaz Reyad commented on SINGA-433:
--

I think this issue can be closed now.

> Preparation for V2.0 release
> 
>
> Key: SINGA-433
> URL: https://issues.apache.org/jira/browse/SINGA-433
> Project: Singa
>  Issue Type: Task
>Reporter: wangwei
>Priority: Major
>  Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> As discussed in the dev list, we are going to release v2.0 with some news 
> features and API changes. This ticket includes the tasks listed in the 
> [release process 
> page|http://singa.apache.org/en/develop/how-to-release.html]. If you want to 
> take one task, please include the task name and ID in the comments.
>  
> 1. Select a release manager. The release manager (RM) is the coordinator for 
> the release process. It is the RM's signature (.asc) that is uploaded 
> together with the release. The RM generates KEY (RSA 4096-bit) and uploads it 
> to a public key server. The RM needs to get his key endorsed (signed) by 
> other Apache user, to be connected to the web of trust. He should first ask 
> the mentor to help signing his key. 
> [http://www.apache.org/dev/release-signing.html]
>  
> 2. Check
>  * the codebase does not include third-party code which is not compatible to 
> APL;
>  * The dependencies are compatible with APL. GNU-like licenses are NOT 
> compatible; 
>  * All source files written by us MUST include the Apache license header: 
> [http://www.apache.org/legal/src-headers.html]. There's a script in there 
> which helps propagating the header to all files.
>  * 
> 3. Check
>  * The build process is error-free.
>  * Unit tests are included (as much as possible)
>  * The Jupyter notebooks are working with the new release
>  * The online documentation on the Apache website is up to date.
>  * Update the NOTICE file. If we include any third party code in the release 
> package which is not APL, must state it at the end of the NOTICE file.
>  * 
> 4. Prepare the RELEASE_NOTES file. Introduction, Features, Bugs (link to 
> JIRA), Changes (N/A for first erlease), Dependency list, Incompatibility 
> issues. Follow this example: 
> [http://commons.apache.org/proper/commons-digester/commons-digester-3.0/RELEASE-NOTES.txt].
>  Prepare DISCLAIMER file. modify from 
> [http://incubator.apache.org/guides/branding.html#disclaimers]
>  
> 5. Package the release. The release should be packaged into : 
> apache-singa-incubating-xx.xx.xx.tar.gz. The release should not include any 
> binary files including git files. Upload the release. The release is uploaded 
> to the RM’s Apache page: people.apache.org/~ID/.
>  * apache-singa-incubating-xx.xx.xx.tar.gz
>  * KEY
>  * XX.acs
>  * XX.md5
>  Roll out artifacts to mirrors. svn add to “dist/release/incubator/singa”
>  Delete old artifacts (automatically archived)
>  * 
> 6. Update the Download page. The tar.gz file MUST be downloaded from mirror, 
> using closer.cgi script; other artifacts MUST be downloaded from main Apache 
> site
>  Good idea to update EC2 image and make it available for download as well
>  
> 7. Make the internal announcements. Template for singa-dev@ voting:
> {code:java}
> To: dev@singa.incubator.apache.org
>  Subject: [VOTE] Release apache-singa-X.Y.Z-incubating (release candidate N)
> Hi all,
> I have created a build for Apache SINGA X.Y.Z-incubating, release candidate N.
> The artifacts to be voted on are located here:
>  
> [https://dist.apache.org/repos/dist/dev/incubator/singa/apache-singa-X.Y.Z-incubating-rcN/]
> The hashes of the artifacts are as follows:
>  apache-singa-X.Y.Z-incubating.tar.gz.md5 
>  apache-singa-X.Y.Z-incubating.tar.gz.sha256 
> Release artifacts are signed with the following key:
>  [https://people.apache.org/keys/committer/]
> {Apache ID of the Release Manager}
> .asc
> and the signature file is:
>  apache-singa-X.Y.Z-incubating.tar.gz.asc
> Please vote on releasing this package. The vote is open for at least 72 hours 
> and passes if a majority of at least three +1 votes are cast.
> [ ] +1 Release this package as Apache SINGA X.Y.Z-incubating
>  [ ] 0 I don't feel strongly about it, but I'm okay with the release
>  [ ] -1 Do not release this package because...
> Here is my vote:
> +1
> {code}
> Wait at least 48 hours for test responses
> Any PPMC, committer or contributor can test features for releasing, and 
> feedback. Based on that, PPMC will decide whether start a 

[jira] [Commented] (SINGA-457) Error in ONNX backend.py example

[Moaz Reyad (JIRA)]

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

Moaz Reyad commented on SINGA-457:
--

I also tried the default option (with GPU), but the same error happens:

{code:bash}
$ python backend.py 
Using GPU
Traceback (most recent call last):
  File "backend.py", line 42, in 
backend = sonnx.prepare(model, dev)
  File 
"/home/moaz/singa-gpu/venv/local/lib/python2.7/site-packages/singa/sonnx.py", 
line 254, in prepare
stores_grad=stores_grad,
  File 
"/home/moaz/singa-gpu/venv/local/lib/python2.7/site-packages/singa/tensor.py", 
line 96, in __init__
copy_from_numpy(self.data, data)
  File 
"/home/moaz/singa-gpu/venv/local/lib/python2.7/site-packages/singa/tensor.py", 
line 1522, in copy_from_numpy
'tensor shape should be the same'
AssertionError: tensor shape should be the same
{code}


> Error in ONNX backend.py example
> 
>
> Key: SINGA-457
> URL: https://issues.apache.org/jira/browse/SINGA-457
>     Project: Singa
>  Issue Type: Bug
>Reporter: Moaz Reyad
>Priority: Major
>
> I tried to run the file [backend.py | 
> https://github.com/apache/incubator-singa/blob/master/examples/onnx/backend.py]
>  example. I followed the instructions in the file:
> {code:python}
> # load and run the onnx model exported from pytorch
> # 
> https://github.com/onnx/tutorials/blob/master/tutorials/PytorchOnnxExport.ipynb
> {code}
> and executed the file with "use_cpu" option:
> {code:bash}
> python backend.py --use_cpu
> Using CPU
> Traceback (most recent call last):
>   File "backend.py", line 42, in 
> backend = sonnx.prepare(model, dev)
>   File 
> "/home/moaz/singa/venv/local/lib/python2.7/site-packages/singa/sonnx.py", 
> line 254, in prepare
> stores_grad=stores_grad,
>   File 
> "/home/moaz/singa/venv/local/lib/python2.7/site-packages/singa/tensor.py", 
> line 96, in __init__
> copy_from_numpy(self.data, data)
>   File 
> "/home/moaz/singa/venv/local/lib/python2.7/site-packages/singa/tensor.py", 
> line 1522, in copy_from_numpy
> 'tensor shape should be the same'
> AssertionError: tensor shape should be the same
> {code}



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

Re: [jira] [Created] (SINGA-458) ONNX backend test failed

[Moaz Reyad]

We can pass only a subset of the test cases. This subset corresponds to the
SINGA ONNX operator coverage.

See for example the MXNET ONNX operator coverage:

https://cwiki.apache.org/confluence/display/MXNET/ONNX+Operator+Coverage

Moaz

On Tue, May 21, 2019 at 4:30 PM Wang Wei  wrote:

> Do we need to pass all 1116 tests?
>
>
>
> On Tue, May 21, 2019 at 9:14 PM Moaz Reyad (JIRA)  wrote:
>
> > Moaz Reyad created SINGA-458:
> > 
> >
> >  Summary: ONNX backend test failed
> >  Key: SINGA-458
> >  URL: https://issues.apache.org/jira/browse/SINGA-458
> >  Project: Singa
> >   Issue Type: Bug
> > Reporter: Moaz Reyad
> >
> >
> > The test of [SINGA ONNX backend|
> >
> https://github.com/apache/incubator-singa/blob/master/python/singa/sonnx.py#L224
> ]
> > using [onnx.backend.test.BackendTest|
> >
> https://github.com/apache/incubator-singa/pull/462/commits/6dec4b24df8e469255c7399600eef27773f92052
> ]
> > failed.
> >
> > There are 1116 unit tests and all of them fail with the error:
> >
> >
> > {code:sh}
> > Traceback (most recent call last):
> >   File
> >
> "/home/moaz/singa/venv/local/lib/python2.7/site-packages/onnx/backend/test/runner/__init__.py",
> > line 248, in device_test_func
> > return test_func(*args, device=device, **kwargs)
> >   File
> >
> "/home/moaz/singa/venv/local/lib/python2.7/site-packages/onnx/backend/test/runner/__init__.py",
> > line 310, in run
> > outputs = list(prepared_model.run(inputs))
> >   File
> > "/home/moaz/singa/venv/local/lib/python2.7/site-packages/singa/sonnx.py",
> > line 198, in run
> > tensors[x.name] = x
> > AttributeError: 'numpy.ndarray' object has no attribute 'name'
> >
> > --
> >
> > {code}
> >
> >
> >
> >
> >
> > --
> > This message was sent by Atlassian JIRA
> > (v7.6.3#76005)
> >
>

[jira] [Commented] (SINGA-442) can not compile and run Singa on Ubuntu 18

[Moaz Reyad (JIRA)]

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

Moaz Reyad commented on SINGA-442:
--

You installed the dependencies for python3 but you are building for pyhton2.

Either build with option -DUSE-PYTHON3=YES, or install python2 dependencies 
such as python-dev, ..etc. (instead of python3-dev).

> can not compile and run Singa on Ubuntu 18
> --
>
> Key: SINGA-442
> URL: https://issues.apache.org/jira/browse/SINGA-442
> Project: Singa
>  Issue Type: Bug
>  Components: Documentation
> Environment: - Ubuntu 18.10
> - Python 3.6 & 2.7
>Reporter: thao p nguyen
>Priority: Critical
> Attachments: dependencies.txt
>
>
> After successfully installed dependencies from dockerfile (attached file: 
> "dependencies.txt"), I can not run cmake. Below are messages:
> thao@thao-OptiPlex-5060:~/Documents/Singa/incubator-singa/build$ cmake 
> -DUSE_PYTHON=ON ..
> -- The C compiler identification is GNU 8.2.0
> -- The CXX compiler identification is GNU 8.2.0
> -- Check for working C compiler: /usr/bin/cc
> -- Check for working C compiler: /usr/bin/cc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Check for working CXX compiler: /usr/bin/c++
> -- Check for working CXX compiler: /usr/bin/c++ -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Looking for pthread.h
> -- Looking for pthread.h - found
> -- Looking for pthread_create
> -- Looking for pthread_create - not found
> -- Looking for pthread_create in pthreads
> -- Looking for pthread_create in pthreads - not found
> -- Looking for pthread_create in pthread
> -- Looking for pthread_create in pthread - found
> -- Found Threads: TRUE 
> -- Found Protobuf: /usr/lib/x86_64-linux-gnu/libprotobuf.so;-lpthread (found 
> suitable version "3.0.0", minimum required is "3.0")
> -- Found CBLAS: /usr/include/x86_64-linux-gnu 
> -- Found GLOG: /usr/include 
> -- Found PythonInterp: /usr/bin/python2.7 (found suitable version "2.7.15", 
> minimum required is "2.7")
> CMake Error at 
> /usr/share/cmake-3.12/Modules/FindPackageHandleStandardArgs.cmake:137 
> (message):
>   Could NOT find PythonLibs (missing: PYTHON_LIBRARIES PYTHON_INCLUDE_DIRS)
>   (Required is at least version "2.7")
> Call Stack (most recent call first):
>   /usr/share/cmake-3.12/Modules/FindPackageHandleStandardArgs.cmake:378 
> (_FPHSA_FAILURE_MESSAGE)
>   /usr/share/cmake-3.12/Modules/FindPythonLibs.cmake:265 
> (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
>   cmake/Dependencies.cmake:134 (FIND_PACKAGE)
>   CMakeLists.txt:75 (INCLUDE)  
> -- Configuring incomplete, errors occurred!
> See also 
> "/home/thao/Documents/Singa/incubator-singa/build/CMakeFiles/CMakeOutput.log".
> See also 
> "/home/thao/Documents/Singa/incubator-singa/build/CMakeFiles/CMakeError.log".
>  
> thao@thao-OptiPlex-5060:~/Documents/Singa/incubator-singa/build$ cmake 
> -DUSE_MODULES=ON ..
> -- Found Protobuf: /usr/lib/x86_64-linux-gnu/libprotobuf.so;-lpthread (found 
> version "3.0.0")
> CMake Error at 
> /usr/share/cmake-3.12/Modules/FindPackageHandleStandardArgs.cmake:137 
> (message):
>   Could NOT find PythonLibs (missing: PYTHON_LIBRARIES PYTHON_INCLUDE_DIRS)
>   (Required is at least version "2.7")
> Call Stack (most recent call first):
>   /usr/share/cmake-3.12/Modules/FindPackageHandleStandardArgs.cmake:378 
> (_FPHSA_FAILURE_MESSAGE)
>   /usr/share/cmake-3.12/Modules/FindPythonLibs.cmake:265 
> (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
>   cmake/Dependencies.cmake:134 (FIND_PACKAGE)
>   CMakeLists.txt:75 (INCLUDE)
> -- Configuring incomplete, errors occurred!
> See also 
> "/home/thao/Documents/Singa/incubator-singa/build/CMakeFiles/CMakeOutput.log".
> See also 
> "/home/thao/Documents/Singa/incubator-singa/build/CMakeFiles/CMakeError.log".
>  
> thao@thao-OptiPlex-5060:~/Documents/Singa/incubator-singa/build$ cmake 
> -DPACKAGE=ON
> CMake Error: The source directory 
> "/home/thao/Documents/Singa/incubator-singa/build" does not appear to contain 
> CMakeLists.txt.
> Specify --help for usage, or press the help button on the CMake GUI.



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

[jira] [Created] (SINGA-458) ONNX backend test failed

[Moaz Reyad (JIRA)]

Moaz Reyad created SINGA-458:


 Summary: ONNX backend test failed
 Key: SINGA-458
 URL: https://issues.apache.org/jira/browse/SINGA-458
 Project: Singa
  Issue Type: Bug
Reporter: Moaz Reyad


The test of [SINGA ONNX 
backend|https://github.com/apache/incubator-singa/blob/master/python/singa/sonnx.py#L224]
 using 
[onnx.backend.test.BackendTest|https://github.com/apache/incubator-singa/pull/462/commits/6dec4b24df8e469255c7399600eef27773f92052]
 failed.

There are 1116 unit tests and all of them fail with the error:


{code:sh}
Traceback (most recent call last):
  File 
"/home/moaz/singa/venv/local/lib/python2.7/site-packages/onnx/backend/test/runner/__init__.py",
 line 248, in device_test_func
return test_func(*args, device=device, **kwargs)
  File 
"/home/moaz/singa/venv/local/lib/python2.7/site-packages/onnx/backend/test/runner/__init__.py",
 line 310, in run
outputs = list(prepared_model.run(inputs))
  File 
"/home/moaz/singa/venv/local/lib/python2.7/site-packages/singa/sonnx.py", line 
198, in run
tensors[x.name] = x
AttributeError: 'numpy.ndarray' object has no attribute 'name'

--

{code}





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

[jira] [Created] (SINGA-457) Error in ONNX backend.py example

[Moaz Reyad (JIRA)]

Moaz Reyad created SINGA-457:


 Summary: Error in ONNX backend.py example
 Key: SINGA-457
 URL: https://issues.apache.org/jira/browse/SINGA-457
 Project: Singa
  Issue Type: Bug
Reporter: Moaz Reyad


I tried to run the file [backend.py | 
https://github.com/apache/incubator-singa/blob/master/examples/onnx/backend.py] 
example. I followed the instructions in the file:


{code:python}

# load and run the onnx model exported from pytorch
# 
https://github.com/onnx/tutorials/blob/master/tutorials/PytorchOnnxExport.ipynb

{code}

and executed the file with "use_cpu" option:

{code:bash}
python backend.py --use_cpu
Using CPU
Traceback (most recent call last):
  File "backend.py", line 42, in 
backend = sonnx.prepare(model, dev)
  File 
"/home/moaz/singa/venv/local/lib/python2.7/site-packages/singa/sonnx.py", line 
254, in prepare
stores_grad=stores_grad,
  File 
"/home/moaz/singa/venv/local/lib/python2.7/site-packages/singa/tensor.py", line 
96, in __init__
copy_from_numpy(self.data, data)
  File 
"/home/moaz/singa/venv/local/lib/python2.7/site-packages/singa/tensor.py", line 
1522, in copy_from_numpy
'tensor shape should be the same'
AssertionError: tensor shape should be the same
{code}




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

SINGA added to the ONNX tutorials

[Moaz Reyad]

Hi All,

SINGA is added to the ONNX tutorials (https://github.com/onnx/tutorials).

We can add SINGA logo to onnx.ai site after the testing and documentation
of the ONNX module in SINGA are completed and when the new logo becomes
ready. (see https://github.com/onnx/tutorials/pull/122)

Best regards,
Moaz

Re: SINGA team at EU FOSSA Apache Hackathon

[Moaz Reyad]

Hi Anthony,

It is great to hear that you enjoyed the Hakathon weekend and you like to
continue contributing to the project.

The Hakathon was only to give a chance to put your hands on the project and
make small contributions because the time was limited. Please feel free to
continue the tasks that we started in the Hakathon or propose new items
whenever you have some available time.

All contributions are welcome and you can become a SINGA committer also:

http://singa.apache.org/en/develop/how-contribute.html#how-to-become-a-singa-committer

Best regards,
Moaz

On Thu, May 9, 2019 at 11:18 PM A Thomas <1988anthonytho...@gmail.com>
wrote:

> Hi,
>
> Thanks for the support over the weekend, I'd be happy to lend a hand and
> some time to the project in future.
>
>
> Regards,
>
> Anthony
>
> On Sun, 5 May 2019 at 10:11, Moaz Reyad  wrote:
>
>> We have also Chandrakumar who will help in documentation. He is creating
>> a ticket and a pull request now.
>>
>> Moaz
>>
>> On Sat, May 4, 2019 at 4:20 PM Wang Wei  wrote:
>>
>>> Hi all,
>>>
>>> Welcome and looking forward to your contributions!
>>>
>>> Regards,
>>> Wei
>>>
>>> On Sat, May 4, 2019 at 9:50 PM Moaz Reyad  wrote:
>>>
>>> > Dear SINGA dev,
>>> >
>>> > I would like to introduce the team who is working on SINGA in the
>>> Apache
>>> > Hackathon.
>>> >
>>> > May be each one of the hackathon team can reply and introduce himself
>>> and
>>> > what he plans to do, so the dev team can help you with your plan. Some
>>> of
>>> > you already created Jira tickets and pull requests.
>>> >
>>> > Thank you,
>>> > Moaz
>>> >
>>>
>>

[jira] [Commented] (SINGA-455) Adding SINGA logo to Apache logos

[Moaz Reyad (JIRA)]

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

Moaz Reyad commented on SINGA-455:
--

The SVG logo is not vectorized and it is pixelated when zooming in because it 
includes the PNG data:

{code:html}
xlink:href="data:image/png ...
{code}

Also the background is not transparent.



> Adding SINGA logo to Apache logos
> -
>
> Key: SINGA-455
> URL: https://issues.apache.org/jira/browse/SINGA-455
> Project: Singa
>  Issue Type: Task
>Reporter: Moaz Reyad
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> SINGA logo is not found in [Apache logos|http://apache.org/logos/].
> We need the SINGA logo in a scalable format (svg, eps, ai, pdf accepted). If 
> this is not available, may be we can ask a graphic designer to prepare it.
> Since SINGA logo is missing, it does not appear in 
> [montages|http://apache.org/logos/montages/] and 
> [powered-by|http://apache.org/logos/poweredby/] collections. It can be missed 
> also from many other places where it is required to have the official 
> scalable logo from Apache printed on posters, banners or large screens. 
>   
>  Fore more information, check [http://apache.org/logos/about.html]
> I suggest to add the project name "SINGA" to the official logo. Almost all 
> the logos in the [Apache logos|http://apache.org/logos/] collection have 
> their name in the logo. We may ask the graphics designer to add SINGA below 
> (or in another place) the logo using a suitable artistic font.



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

Re: [EU-FOSSA 2 2019 Hackathon] Integration between SINGA and PLC4X

[Moaz Reyad]

A recent thesis on "Orchestration of machine learning workflows on Internet
of Things data" [1] mentioned that Rafiki (a sub module of SINGA) dose not
provide an integrated platform for ML on IoT data (see Table 2.1).

I think the integration with PLC4X will fix this issue and provide a useful
required feature by industry.

Let's start planning for this collaboration.

[1] https://ir.lib.uwo.ca/etd/6150/

Moaz

On Sun, May 5, 2019 at 5:10 PM Wang Wei  wrote:

> Hi all,
>
> +1. Looking forward to the collaborations!
>
> Regards,
> Wei (from SINGA team)
>
> On Sun, May 5, 2019 at 10:33 PM Julian Feinauer <
> j.feina...@pragmaticminds.de> wrote:
>
> > Hi Moaz,
> >
> > Big +1 from me... It really was a pleasure with you! And I guess toddy
> and
> > your lion will make a pretty lovely pair :)
> >
> > Julian
> >
> > Von meinem Mobiltelefon gesendet
> >
> >
> >  Ursprüngliche Nachricht 
> > Betreff: [EU-FOSSA 2 2019 Hackathon] Integration between SINGA and PLC4X
> > Von: Moaz Reyad
> > An: d...@plc4x.apache.org,dev@singa.incubator.apache.org
> > Cc: "Saranjit-Singh.ARORA" ,Suwon Ham ,Sally Khudairi ,Christofer Dutz
> >
> > Dear SINGA and PLC4X dev,
> >
> > I met with Christofer in the EU-FOSSA 2 2019 Hackathon and we discussed a
> > possible collaboration between the two projects.
> >
> > More specifically, we could check the integration between SINGA I/O
> modules
> > and PLC4X which will probably allow better communication between
> industrial
> > IoT and machine learning.
> >
> > PLC4X already implemented (or planned to implemented) integrations with
> > several projects and a deep learning integration module with SINGA can be
> > useful for both projects.
> >
> > Both dev teams are welcome to share their ideas and discuss this further.
> >
> > Best regards,
> > Moaz
> >
>

[jira] [Created] (SINGA-456) Adding more PGP Keys

[Moaz Reyad (JIRA)]

Moaz Reyad created SINGA-456:


 Summary: Adding more PGP Keys
 Key: SINGA-456
 URL: https://issues.apache.org/jira/browse/SINGA-456
 Project: Singa
  Issue Type: Improvement
Reporter: Moaz Reyad
 Attachments: KEYS

Currently the SINGA [KEYS |https://www.apache.org/dist/incubator/singa/KEYS] 
file has only one PGP key which is expiring this September (it needs to be 
updated). This means only one person can sign the releases. While other 
projects like CouchDB for example, have several keys in the [KEYS 
|https://www.apache.org/dist/couchdb/KEYS] file.

It will be useful if every active Apache committer in the team create a PGP key 
and uploads the Public Key Primary Fingerprint to his account using [Apache 
Account Utility|https://id.apache.org/]. Then append the new key to the SINGA 
KEYS file.

Furthermore, the keys themselves can be signed for more trust. SINGA team can 
exchange key signatures between them or organize a [key signing 
party|https://www.apache.org/dev/release-signing#key-signing-party]. This will 
help adding more SINGA committers into the [Apache Web of 
Trust|https://www.apache.org/dev/release-signing#web-of-trust]. 

I attach with this issue the KEYS file with my key appended at the end. 



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

Re: Missing podling logos

[Moaz Reyad]

Hi Justin,

There is already a ticket in Jira for this issue:

https://issues.apache.org/jira/projects/SINGA/issues/SINGA-455

We hope to fix it soon.

Thank you,
Moaz

On Sun, May 12, 2019 at 6:47 AM Justin Mclean 
wrote:

> Hi,
>
> My second list for the logos  [1] had a few errors as it assumed .svg
> files existed for all projects. Try this one instead:
>
> Logos misisng:
> amaterasu
> annotator
> batchee
> brpc
> datasketches
> dlab
> flagon
> gobblin
> hudi
> iotdb
> marvin
> omid
> pinot
> ratis
> rya
> s2graph
> samoa
> sdap
> shardingsphere
> singa
> tamaya
> training
> tephra
> toree
> tuweni
> tvm
> weex
> zipkin
>
> Thanks,
> Justin
>
> 1. http://www.apache.org/logos/
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[jira] [Created] (SINGA-455) Adding SINGA logo to Apache logos

[Moaz Reyad (JIRA)]

Moaz Reyad created SINGA-455:


 Summary: Adding SINGA logo to Apache logos
 Key: SINGA-455
 URL: https://issues.apache.org/jira/browse/SINGA-455
 Project: Singa
  Issue Type: Task
Reporter: Moaz Reyad


SINGA logo is not found in [Apache logos|http://apache.org/logos/].

We need the SINGA logo in a scalable format (svg, eps, ai, pdf accepted). If 
this is not available, may be we can ask a graphic designer to prepare it.

Since SINGA logo is missing, it does not appear in 
[montages|http://apache.org/logos/montages/] and 
[powered-by|http://apache.org/logos/poweredby/] collections. It can be missed 
also from many other places where it is required to have the official scalable 
logo from Apache printed on posters, banners or large screens. 
  
 Fore more information, check [http://apache.org/logos/about.html]

I suggest to add the project name "SINGA" to the official logo. Almost all the 
logos in the [Apache logos|http://apache.org/logos/] collection have their name 
in the logo. We may ask the graphics designer to add SINGA below (or in another 
place) the logo using a suitable artistic font.



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

[EU-FOSSA 2 2019 Hackathon] SINGA and SpamAssassin collaboration in GSoC 2019

[Moaz Reyad]

Dear SINGA and SpamAssassin dev,

I met with Giovanni Bechis in the EU-FOSSA 2 2019 Hackathon and we
discussed a possible collaboration between the two projects.

SpamAssassin has a proposal in Google Summer of Code 2019 about Statistical
Classifier Plugin for spam email detection. If both teams and the student
agree, we may consider building this plugin with SINGA.

The GSoC guide says "Some organizations choose to assign more than one
mentor to each of their students.". This means Apache can assign mentors
from SINGA and SpamAssassin to help in developing this plugin. We have two
mentors from SINGA in GSoC and one or both of them can help in co-mentoring
this project.

Best regards,
Moaz

[EU-FOSSA 2 2019 Hackathon] Integration between SINGA and PLC4X

[Moaz Reyad]

Dear SINGA and PLC4X dev,

I met with Christofer in the EU-FOSSA 2 2019 Hackathon and we discussed a
possible collaboration between the two projects.

More specifically, we could check the integration between SINGA I/O modules
and PLC4X which will probably allow better communication between industrial
IoT and machine learning.

PLC4X already implemented (or planned to implemented) integrations with
several projects and a deep learning integration module with SINGA can be
useful for both projects.

Both dev teams are welcome to share their ideas and discuss this further.

Best regards,
Moaz

Re: SINGA team at EU FOSSA Apache Hackathon

[Moaz Reyad]

We have also Chandrakumar who will help in documentation. He is creating a
ticket and a pull request now.

Moaz

On Sat, May 4, 2019 at 4:20 PM Wang Wei  wrote:

> Hi all,
>
> Welcome and looking forward to your contributions!
>
> Regards,
> Wei
>
> On Sat, May 4, 2019 at 9:50 PM Moaz Reyad  wrote:
>
> > Dear SINGA dev,
> >
> > I would like to introduce the team who is working on SINGA in the Apache
> > Hackathon.
> >
> > May be each one of the hackathon team can reply and introduce himself and
> > what he plans to do, so the dev team can help you with your plan. Some of
> > you already created Jira tickets and pull requests.
> >
> > Thank you,
> > Moaz
> >
>

SINGA team at EU FOSSA Apache Hackathon

[Moaz Reyad]

Dear SINGA dev,

I would like to introduce the team who is working on SINGA in the Apache
Hackathon.

May be each one of the hackathon team can reply and introduce himself and
what he plans to do, so the dev team can help you with your plan. Some of
you already created Jira tickets and pull requests.

Thank you,
Moaz

Re: [jira] [Commented] (SINGA-433) Preparation for V2.0 release

[Moaz Reyad]

I have two comments:

1. This benchmark seems interesting, may be you can also post it with some
explanation on SINGA social media accounts.

2. The update of SINGA website now overrides the code from SINGA-436. This
makes the Apache Podling Website Checks (
https://whimsy.apache.org/pods.cgi/project/singa) to fail again. To fix
this problem, we need to review and merge Pull Request #452 (
https://github.com/apache/incubator-singa/pull/452)

Moaz

On Fri, Apr 26, 2019 at 6:32 AM ASF subversion and git services (JIRA) <
j...@apache.org> wrote:

>
> [
> https://issues.apache.org/jira/browse/SINGA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826633#comment-16826633
> ]
>
> ASF subversion and git services commented on SINGA-433:
> ---
>
> Commit a7027dd34a34f2863036dafe66ae9e7b7b06f084 in incubator-singa's
> branch refs/heads/master from Wang Wei
> [ https://gitbox.apache.org/repos/asf?p=incubator-singa.git;h=a7027dd ]
>
> SINGA-433 Update the website
>
>
> > Preparation for V2.0 release
> > 
> >
> > Key: SINGA-433
> > URL: https://issues.apache.org/jira/browse/SINGA-433
> > Project: Singa
> >  Issue Type: Task
> >Reporter: wangwei
> >Priority: Major
> >  Time Spent: 2h 50m
> >  Remaining Estimate: 0h
> >
> > As discussed in the dev list, we are going to release v2.0 with some
> news features and API changes. This ticket includes the tasks listed in the
> [release process page|
> http://singa.apache.org/en/develop/how-to-release.html]. If you want to
> take one task, please include the task name and ID in the comments.
> >
> > 1. Select a release manager. The release manager (RM) is the coordinator
> for the release process. It is the RM's signature (.asc) that is uploaded
> together with the release. The RM generates KEY (RSA 4096-bit) and uploads
> it to a public key server. The RM needs to get his key endorsed (signed) by
> other Apache user, to be connected to the web of trust. He should first ask
> the mentor to help signing his key. [
> http://www.apache.org/dev/release-signing.html]
> >
> > 2. Check
> >  * the codebase does not include third-party code which is not
> compatible to APL;
> >  * The dependencies are compatible with APL. GNU-like licenses are NOT
> compatible;
> >  * All source files written by us MUST include the Apache license
> header: [http://www.apache.org/legal/src-headers.html]. There's a script
> in there which helps propagating the header to all files.
> >  *
> > 3. Check
> >  * The build process is error-free.
> >  * Unit tests are included (as much as possible)
> >  * The Jupyter notebooks are working with the new release
> >  * The online documentation on the Apache website is up to date.
> >  * Update the NOTICE file. If we include any third party code in the
> release package which is not APL, must state it at the end of the NOTICE
> file.
> >  *
> > 4. Prepare the RELEASE_NOTES file. Introduction, Features, Bugs (link to
> JIRA), Changes (N/A for first erlease), Dependency list, Incompatibility
> issues. Follow this example: [
> http://commons.apache.org/proper/commons-digester/commons-digester-3.0/RELEASE-NOTES.txt].
> Prepare DISCLAIMER file. modify from [
> http://incubator.apache.org/guides/branding.html#disclaimers]
> >
> > 5. Package the release. The release should be packaged into :
> apache-singa-incubating-xx.xx.xx.tar.gz. The release should not include any
> binary files including git files. Upload the release. The release is
> uploaded to the RM’s Apache page: people.apache.org/~ID/.
> >  * apache-singa-incubating-xx.xx.xx.tar.gz
> >  * KEY
> >  * XX.acs
> >  * XX.md5
> >  Roll out artifacts to mirrors. svn add to “dist/release/incubator/singa”
> >  Delete old artifacts (automatically archived)
> >  *
> > 6. Update the Download page. The tar.gz file MUST be downloaded from
> mirror, using closer.cgi script; other artifacts MUST be downloaded from
> main Apache site
> >  Good idea to update EC2 image and make it available for download as well
> >
> > 7. Make the internal announcements. Template for singa-dev@ voting:
> > {code:java}
> > To: dev@singa.incubator.apache.org
> >  Subject: [VOTE] Release apache-singa-X.Y.Z-incubating (release
> candidate N)
> > Hi all,
> > I have created a build for Apache SINGA X.Y.Z-incubating, release
> candidate N.
> > The artifacts to be voted on are located here:
> >  [
> https://dist.apache.org/repos/dist/dev/incubator/singa/apache-singa-X.Y.Z-incubating-rcN/
> ]
> > The hashes of the artifacts are as follows:
> >  apache-singa-X.Y.Z-incubating.tar.gz.md5 
> >  apache-singa-X.Y.Z-incubating.tar.gz.sha256 
> > Release artifacts are signed with the following key:
> >  [https://people.apache.org/keys/committer/]
> > {Apache ID of the Release Manager}
> > .asc
> > and the signature file is:
> >  apache-singa-X.Y.Z-

[jira] [Created] (SINGA-449) Preparing Podling TLP resolution

[Moaz Reyad (JIRA)]

Moaz Reyad created SINGA-449:


 Summary: Preparing Podling TLP resolution
 Key: SINGA-449
 URL: https://issues.apache.org/jira/browse/SINGA-449
 Project: Singa
  Issue Type: Task
Reporter: Moaz Reyad


This issue is for preparing the graduation resolution for SINGA given the 
[template|https://svn.apache.org/repos/private/committers/board/templates/podling-tlp-resolution.txt].

The resolution draft for SINGA is 
[here|https://cwiki.apache.org/confluence/display/SINGA/Graduation+Resolution].

Please check it and give your feedback.

SINGA PPMC need to discuss and choose the project Chair (see private mail list).

We also need to specify initial project members. We can copy all the current 
members without asking their permission (assuming everyone agrees) or we may 
ask every member to explicitly agree to be added to the initial project members.



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

[jira] [Commented] (SINGA-436) Implement Apache Website Navigation Links Policy

[Moaz Reyad (JIRA)]

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

Moaz Reyad commented on SINGA-436:
--

All Apache Podling Website Checks pass now.

> Implement Apache Website Navigation Links Policy
> 
>
> Key: SINGA-436
> URL: https://issues.apache.org/jira/browse/SINGA-436
> Project: Singa
>  Issue Type: Improvement
>Reporter: Moaz Reyad
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The [Apache Website Navigation Links 
> Policy|https://www.apache.org/foundation/marks/pmcs#navigation] requires that 
> SINGA website contains five links to License, Sponsorship, Thanks, Security 
> and main ASF homepage.
> Currently the "index.html" page of SINGA website which is generated by 
> sphinx-doc contains only this line:
> {code:html}
>  type="text/javascript">window.location.href='en/index.html';
> {code}
> This can be found by doing:
> {code:bash}
> wget http://singa.incubator.apache.org/
> cat index.html
> {code}
> This causes the automatic crawl by [Apache Podling Website 
> Checks|https://whimsy.apache.org/pods.cgi/project/singa] to fail.
> The implementation of link policy is required before graduation from the 
> incubator. 



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

[jira] [Resolved] (SINGA-436) Implement Apache Website Navigation Links Policy

[Moaz Reyad (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SINGA-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Moaz Reyad resolved SINGA-436.
--
Resolution: Fixed

> Implement Apache Website Navigation Links Policy
> 
>
> Key: SINGA-436
> URL: https://issues.apache.org/jira/browse/SINGA-436
> Project: Singa
>  Issue Type: Improvement
>    Reporter: Moaz Reyad
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The [Apache Website Navigation Links 
> Policy|https://www.apache.org/foundation/marks/pmcs#navigation] requires that 
> SINGA website contains five links to License, Sponsorship, Thanks, Security 
> and main ASF homepage.
> Currently the "index.html" page of SINGA website which is generated by 
> sphinx-doc contains only this line:
> {code:html}
>  type="text/javascript">window.location.href='en/index.html';
> {code}
> This can be found by doing:
> {code:bash}
> wget http://singa.incubator.apache.org/
> cat index.html
> {code}
> This causes the automatic crawl by [Apache Podling Website 
> Checks|https://whimsy.apache.org/pods.cgi/project/singa] to fail.
> The implementation of link policy is required before graduation from the 
> incubator. 



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

[jira] [Created] (SINGA-446) Move development pages to Confluence

[Moaz Reyad (JIRA)]

Moaz Reyad created SINGA-446:


 Summary: Move development pages to Confluence
 Key: SINGA-446
 URL: https://issues.apache.org/jira/browse/SINGA-446
 Project: Singa
  Issue Type: Improvement
  Components: Documentation
Reporter: Moaz Reyad


The [SINGA wiki space in 
confluence|https://cwiki.apache.org/confluence/display/SINGA/Home] is available 
now.

We may start moving the internal development pages from the main web site and 
github to the wiki.

Pages that we may move are:
 * [How to release|http://singa.apache.org/en/develop/how-to-release.html].
 * [Development Schedule|http://singa.apache.org/en/develop/schedule.html].
 * [Maturity Assessment|https://github.com/apache/incubator-singa/pull/427].
 * Graduation Resolution (WIP).

what else?



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

[jira] [Commented] (SINGA-433) Preparation for V2.0 release

[Moaz Reyad (JIRA)]

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

Moaz Reyad commented on SINGA-433:
--

After the release is completed, may be we can add the following tasks:

* Update the [Development 
Schedule|http://singa.apache.org/en/develop/schedule.html].
* Update information in [Wikipedia 
page|https://en.wikipedia.org/wiki/Apache_SINGA].
* Announce the new release on 
[Facebook|https://www.facebook.com/Apache-SINGA-347284219056544/], 
[Twitter|https://twitter.com/ApacheSinga] and 
[Linkedin|https://www.linkedin.com/groups/13550034/] pages of SINGA. Team 
members and users are encouraged to share the announcement on their profiles 
and relevant groups.


> Preparation for V2.0 release
> 
>
> Key: SINGA-433
> URL: https://issues.apache.org/jira/browse/SINGA-433
> Project: Singa
>  Issue Type: Task
>Reporter: wangwei
>Priority: Major
>  Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> As discussed in the dev list, we are going to release v2.0 with some news 
> features and API changes. This ticket includes the tasks listed in the 
> [release process 
> page|http://singa.apache.org/en/develop/how-to-release.html]. If you want to 
> take one task, please include the task name and ID in the comments.
>  
> 1. Select a release manager. The release manager (RM) is the coordinator for 
> the release process. It is the RM's signature (.asc) that is uploaded 
> together with the release. The RM generates KEY (RSA 4096-bit) and uploads it 
> to a public key server. The RM needs to get his key endorsed (signed) by 
> other Apache user, to be connected to the web of trust. He should first ask 
> the mentor to help signing his key. 
> [http://www.apache.org/dev/release-signing.html]
>  
> 2. Check
>  * the codebase does not include third-party code which is not compatible to 
> APL;
>  * The dependencies are compatible with APL. GNU-like licenses are NOT 
> compatible; 
>  * All source files written by us MUST include the Apache license header: 
> [http://www.apache.org/legal/src-headers.html]. There's a script in there 
> which helps propagating the header to all files.
>  * 
> 3. Check
>  * The build process is error-free.
>  * Unit tests are included (as much as possible)
>  * The Jupyter notebooks are working with the new release
>  * The online documentation on the Apache website is up to date.
>  * Update the NOTICE file. If we include any third party code in the release 
> package which is not APL, must state it at the end of the NOTICE file.
>  * 
> 4. Prepare the RELEASE_NOTES file. Introduction, Features, Bugs (link to 
> JIRA), Changes (N/A for first erlease), Dependency list, Incompatibility 
> issues. Follow this example: 
> [http://commons.apache.org/proper/commons-digester/commons-digester-3.0/RELEASE-NOTES.txt].
>  Prepare DISCLAIMER file. modify from 
> [http://incubator.apache.org/guides/branding.html#disclaimers]
>  
> 5. Package the release. The release should be packaged into : 
> apache-singa-incubating-xx.xx.xx.tar.gz. The release should not include any 
> binary files including git files. Upload the release. The release is uploaded 
> to the RM’s Apache page: people.apache.org/~ID/.
>  * apache-singa-incubating-xx.xx.xx.tar.gz
>  * KEY
>  * XX.acs
>  * XX.md5
>  Roll out artifacts to mirrors. svn add to “dist/release/incubator/singa”
>  Delete old artifacts (automatically archived)
>  * 
> 6. Update the Download page. The tar.gz file MUST be downloaded from mirror, 
> using closer.cgi script; other artifacts MUST be downloaded from main Apache 
> site
>  Good idea to update EC2 image and make it available for download as well
>  
> 7. Make the internal announcements. Template for singa-dev@ voting:
> {code:java}
> To: dev@singa.incubator.apache.org
>  Subject: [VOTE] Release apache-singa-X.Y.Z-incubating (release candidate N)
> Hi all,
> I have created a build for Apache SINGA X.Y.Z-incubating, release candidate N.
> The artifacts to be voted on are located here:
>  
> [https://dist.apache.org/repos/dist/dev/incubator/singa/apache-singa-X.Y.Z-incubating-rcN/]
> The hashes of the artifacts are as follows:
>  apache-singa-X.Y.Z-incubating.tar.gz.md5 
>  apache-singa-X.Y.Z-incubating.tar.gz.sha256 
> Release artifacts are signed with the following key:
>  [https://people.apache.org/keys/committer/]
> {Apache ID of the Release Manager}
> .asc
> and the signature file is:
>  apache-singa-X.Y.Z-incubating.tar.gz.asc
> Please vote on releasing this package. The vote is op

[jira] [Commented] (SINGA-433) Preparation for V2.0 release

[Moaz Reyad (JIRA)]

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

Moaz Reyad commented on SINGA-433:
--

Please note that the template for ANNOUNCE in the "how to release" is missing 
the disclaimer which must be added:

{code:html}
Disclaimer

Apache SINGA (incubating) is an effort undergoing incubation at The Apache
Software Foundation (ASF), sponsored by Apache Incubator. Incubation is
required of all newly accepted projects until a further review indicates
that the infrastructure, communications, and decision making process have
stabilized in a manner consistent with other successful ASF projects. While
incubation status is not necessarily a reflection of the completeness or
stability of the code, it does indicate that the project has yet to be
fully endorsed by the ASF.
{code}

See the [announce email of 1.2.0 
|http://mail-archives.us.apache.org/mod_mbox/www-announce/201806.mbox/%3CCAH%3DWUUafd-T5XO_37XfZzDO6fNR6WcAohLEpj%2BLMQSV-u6se%3Dw%40mail.gmail.com%3E]for
 an example.

> Preparation for V2.0 release
> 
>
> Key: SINGA-433
> URL: https://issues.apache.org/jira/browse/SINGA-433
> Project: Singa
>  Issue Type: Task
>Reporter: wangwei
>Priority: Major
>  Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> As discussed in the dev list, we are going to release v2.0 with some news 
> features and API changes. This ticket includes the tasks listed in the 
> [release process 
> page|http://singa.apache.org/en/develop/how-to-release.html]. If you want to 
> take one task, please include the task name and ID in the comments.
>  
> 1. Select a release manager. The release manager (RM) is the coordinator for 
> the release process. It is the RM's signature (.asc) that is uploaded 
> together with the release. The RM generates KEY (RSA 4096-bit) and uploads it 
> to a public key server. The RM needs to get his key endorsed (signed) by 
> other Apache user, to be connected to the web of trust. He should first ask 
> the mentor to help signing his key. 
> [http://www.apache.org/dev/release-signing.html]
>  
> 2. Check
>  * the codebase does not include third-party code which is not compatible to 
> APL;
>  * The dependencies are compatible with APL. GNU-like licenses are NOT 
> compatible; 
>  * All source files written by us MUST include the Apache license header: 
> [http://www.apache.org/legal/src-headers.html]. There's a script in there 
> which helps propagating the header to all files.
>  * 
> 3. Check
>  * The build process is error-free.
>  * Unit tests are included (as much as possible)
>  * The Jupyter notebooks are working with the new release
>  * The online documentation on the Apache website is up to date.
>  * Update the NOTICE file. If we include any third party code in the release 
> package which is not APL, must state it at the end of the NOTICE file.
>  * 
> 4. Prepare the RELEASE_NOTES file. Introduction, Features, Bugs (link to 
> JIRA), Changes (N/A for first erlease), Dependency list, Incompatibility 
> issues. Follow this example: 
> [http://commons.apache.org/proper/commons-digester/commons-digester-3.0/RELEASE-NOTES.txt].
>  Prepare DISCLAIMER file. modify from 
> [http://incubator.apache.org/guides/branding.html#disclaimers]
>  
> 5. Package the release. The release should be packaged into : 
> apache-singa-incubating-xx.xx.xx.tar.gz. The release should not include any 
> binary files including git files. Upload the release. The release is uploaded 
> to the RM’s Apache page: people.apache.org/~ID/.
>  * apache-singa-incubating-xx.xx.xx.tar.gz
>  * KEY
>  * XX.acs
>  * XX.md5
>  Roll out artifacts to mirrors. svn add to “dist/release/incubator/singa”
>  Delete old artifacts (automatically archived)
>  * 
> 6. Update the Download page. The tar.gz file MUST be downloaded from mirror, 
> using closer.cgi script; other artifacts MUST be downloaded from main Apache 
> site
>  Good idea to update EC2 image and make it available for download as well
>  
> 7. Make the internal announcements. Template for singa-dev@ voting:
> {code:java}
> To: dev@singa.incubator.apache.org
>  Subject: [VOTE] Release apache-singa-X.Y.Z-incubating (release candidate N)
> Hi all,
> I have created a build for Apache SINGA X.Y.Z-incubating, release candidate N.
> The artifacts to be voted on are located here:
>  
> [https://dist.apache.org/repos/dist/dev/incubator/singa/apache-singa-X.Y.Z-incubating-rcN/]
> The hashes of the artifacts are as follows:
>  apache-singa-X.Y.Z-incubating.tar.gz.md5 
>  apache-si

[jira] [Commented] (SINGA-433) Preparation for V2.0 release

[Moaz Reyad (JIRA)]

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

Moaz Reyad commented on SINGA-433:
--

We can also add the list of contributors and their commits with the release 
notes like [Apache Arrow|https://arrow.apache.org/release/0.12.0.html]. This 
will help in showing the project activity and community growth.

{code:sh}
 $ git shortlog -sn 1.2.0..2.0.0rc1

46  xuewanqi
37  Wang Wei
21  Wei Wang
20  shicong
11  Moaz Reyad
 7  wang wei
 6  sheyujian
 4  dcslin
 3  jixin
 3  ShichengChen
 3  wangwei
 3  zmeihui
 2  Kaiping Zheng
 2  Zheng130126
 2  aviral
 2  zhaojing
 2  Wentong-DST
 2  WANG Sheng
 1  chonho
 1  Meihui Zhang
 1  Vaan Ng
 1  WANG Ji
 1  Wentao Huang
 1  YINGHONGBIN
 1  Bourne
 1  huangwentao
 1  joddiy
 1  kaiping
 1  root
 1  slin004
{code}


> Preparation for V2.0 release
> 
>
> Key: SINGA-433
> URL: https://issues.apache.org/jira/browse/SINGA-433
> Project: Singa
>  Issue Type: Task
>Reporter: wangwei
>Priority: Major
>  Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> As discussed in the dev list, we are going to release v2.0 with some news 
> features and API changes. This ticket includes the tasks listed in the 
> [release process 
> page|http://singa.apache.org/en/develop/how-to-release.html]. If you want to 
> take one task, please include the task name and ID in the comments.
>  
> 1. Select a release manager. The release manager (RM) is the coordinator for 
> the release process. It is the RM's signature (.asc) that is uploaded 
> together with the release. The RM generates KEY (RSA 4096-bit) and uploads it 
> to a public key server. The RM needs to get his key endorsed (signed) by 
> other Apache user, to be connected to the web of trust. He should first ask 
> the mentor to help signing his key. 
> [http://www.apache.org/dev/release-signing.html]
>  
> 2. Check
>  * the codebase does not include third-party code which is not compatible to 
> APL;
>  * The dependencies are compatible with APL. GNU-like licenses are NOT 
> compatible; 
>  * All source files written by us MUST include the Apache license header: 
> [http://www.apache.org/legal/src-headers.html]. There's a script in there 
> which helps propagating the header to all files.
>  * 
> 3. Check
>  * The build process is error-free.
>  * Unit tests are included (as much as possible)
>  * The Jupyter notebooks are working with the new release
>  * The online documentation on the Apache website is up to date.
>  * Update the NOTICE file. If we include any third party code in the release 
> package which is not APL, must state it at the end of the NOTICE file.
>  * 
> 4. Prepare the RELEASE_NOTES file. Introduction, Features, Bugs (link to 
> JIRA), Changes (N/A for first erlease), Dependency list, Incompatibility 
> issues. Follow this example: 
> [http://commons.apache.org/proper/commons-digester/commons-digester-3.0/RELEASE-NOTES.txt].
>  Prepare DISCLAIMER file. modify from 
> [http://incubator.apache.org/guides/branding.html#disclaimers]
>  
> 5. Package the release. The release should be packaged into : 
> apache-singa-incubating-xx.xx.xx.tar.gz. The release should not include any 
> binary files including git files. Upload the release. The release is uploaded 
> to the RM’s Apache page: people.apache.org/~ID/.
>  * apache-singa-incubating-xx.xx.xx.tar.gz
>  * KEY
>  * XX.acs
>  * XX.md5
>  Roll out artifacts to mirrors. svn add to “dist/release/incubator/singa”
>  Delete old artifacts (automatically archived)
>  * 
> 6. Update the Download page. The tar.gz file MUST be downloaded from mirror, 
> using closer.cgi script; other artifacts MUST be downloaded from main Apache 
> site
>  Good idea to update EC2 image and make it available for download as well
>  
> 7. Make the internal announcements. Template for singa-dev@ voting:
> {code:java}
> To: dev@singa.incubator.apache.org
>  Subject: [VOTE] Release apache-singa-X.Y.Z-incubating (release candidate N)
> Hi all,
> I have created a build for Apache SINGA X.Y.Z-incubating, release candidate N.
> The artifacts to be voted on are located here:
>  
> [https://dist.apache.org/repos/dist/dev/incubator/singa/apache-singa-X.Y.Z-incubating-rcN/]
> The hashes of the artifacts are as follows:
>  apache-singa-X.Y.Z-incubating.tar.gz.md5 
>  apache-singa-X.Y.Z-incubating.tar.gz.sha256 
> Release artifacts are signed with the following key:
>  [ht

[jira] [Resolved] (SINGA-428) Move Docker images under Apache user name

[Moaz Reyad (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SINGA-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Moaz Reyad resolved SINGA-428.
--
Resolution: Fixed

> Move Docker images under Apache user name
> -
>
> Key: SINGA-428
> URL: https://issues.apache.org/jira/browse/SINGA-428
> Project: Singa
>  Issue Type: Bug
>    Reporter: Moaz Reyad
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The Docker images of SINGA are now on Docker Hub 
> [here|https://hub.docker.com/r/nusdbsystem/singa/]. They are not under the 
> [Apache docker username|https://hub.docker.com/u/apache/].
> To solve this problem, we create a ticket at INFRA to provide the name space 
> SINGA.
> We also need to make sure that the docker images of SINGA are built using 
> official releases and not using latest (master) branch which is not official.



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

[jira] [Commented] (SINGA-440) fail to pull Docker images

[Moaz Reyad (JIRA)]

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

Moaz Reyad commented on SINGA-440:
--

There is not tag 'devel' for apache/singa. You can find the available tags 
[here|https://hub.docker.com/r/apache/singa/tags]

For example, you can use:
{code}
sudo docker pull apache/singa:1.2.0-cpu-devel-ubuntu18.04
{code}
The 
[documentation|https://github.com/apache/incubator-singa/blob/master/tool/docker/README.md]
 needs to be updated.

> fail to pull Docker images
> --
>
> Key: SINGA-440
> URL: https://issues.apache.org/jira/browse/SINGA-440
> Project: Singa
>  Issue Type: Bug
>  Components: Documentation
> Environment: - Docker version 18.09.4
> - Python 3.6.7
> - run on Ubuntu 18.10 
>Reporter: thao p nguyen
>Priority: Major
>
> 1- I can not pull docker images from dockerhub (src: 
> [https://github.com/apache/incubator-singa/tree/master/tool/docker).] Below 
> is command line and error:
> thao@thao-OptiPlex-5060:~$ sudo docker pull apache/singa:devel
> Error response from daemon: manifest for apache/singa:devel not found
> thao@thao-OptiPlex-5060:~$ sudo docker pull apache/singa:devel-cuda
> Error response from daemon: manifest for apache/singa:devel-cuda not found
> 2- Can not create new Docker images from Dockerfile by using the command line 
> format indicated (src: 
> [https://github.com/apache/incubator-singa/tree/master/tool/docker)|https://github.com/apache/incubator-singa/tree/master/tool/docker).].
>  Below is my command line and error:
> thao@thao-OptiPlex-5060:~/Documents/Singa/incubator-singa/tool/docker/devel$ 
> sudo docker build -t singa:cpu -f Dockerfile
> "docker build" requires exactly 1 argument.
> See 'docker build --help'.
> Usage:  docker build [OPTIONS] PATH | URL | -
> Build an image from a Dockerfile
>  
> *** Instead, I tried this command to create new Docker images and it works:
> thao@thao-OptiPlex-5060:~/Documents/Singa/incubator-singa/tool/docker/devel/ubuntu$
>  sudo docker build -t singa:devel cpu
>  



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

Re: [VOTE] Release apache-singa-incubating-2.0.0 (RC1)

[Moaz Reyad]

+1

I run Apache Rat and I built successfully (using one configuration: Ubuntu
16.04/Python 2/CPU Only)

Best regards,
Moaz

On Mon, Apr 8, 2019 at 1:06 AM Anh Dinh  wrote:

> +1 (binding)
>
> I checked signatures and digest.
>
> Anh.
>
>
> On Mon, 8 Apr 2019 at 00:13, Wang Wei  wrote:
>
> > +1 (binding)
> >
> > I have run apache-rat for the license header check.
> >
> > Regards,
> > Wei
> >
> > On Sun, Apr 7, 2019 at 9:20 PM Beng Chin OOI 
> > wrote:
> >
> > >
> > > +1
> > >
> > > regards
> > > beng chin
> > >
> > > On 2019-04-07 15:41, Chonho Lee wrote:
> > > > Hi all,
> > > >
> > > > We have created a build for Apache SINGA 2.0.0-incubating, release
> > > > candidate RC1.
> > > >
> > > > The artifacts to be voted on are located here:
> > > > https://dist.apache.org/repos/dist/dev/incubator/singa/2.0.0/
> > > >
> > > > The hashes of the artifacts are as follows:
> > > > SHA512: D422ED7C 1AD370CA 66D5591B E581DC3C 2513396E 465CF983
> 80785929
> > > > A70189AA 8944452A 1B10AF23 03F781BF 5D4066CE D994FE97 123280A1
> EA34A681
> > > > 3402BA12
> > > >
> > > > Release artifacts are signed with the following key:
> > > > https://people.apache.org/keys/committer/dinhtta.asc
> > > >
> > > > and the signature file is:
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/singa/2.0.0/apache-singa-incubating-2.0.0-RC1.tar.gz.asc
> > > >
> > > >
> > > > The Github tag is at:
> > > > https://github.com/apache/incubator-singa/releases/tag/2.0.0rc1
> > > > commit ID is: 5f14f3dbc005a64fdbc508bff63db92e6d3e05b6
> > > >
> > > > To check the license, you can use the Apache Rat tool as follows:
> > > > 1. download & decompress apache rat from
> > > > http://creadur.apache.org/rat/download_rat.cgi
> > > > 2. run the following command under singa folder:
> > > > java -jar /PATH/TO/RAT/apache-rat-0.11.jar -E rat-excludes -d . >
> > > > rat_check
> > > > 3. check the results in file named "rat_check"
> > > >
> > > > Please check and vote on releasing this package. The vote is open for
> > > > at
> > > > least 72 hours and passes if a majority of at least three +1 votes
> are
> > > > cast.
> > > >
> > > > [ ] +1 Release this package as Apache SINGA 2.0.0-incubating
> > > > [ ]  0 I don't feel strongly about it, but I'm okay with the release
> > > > [ ] -1 Do not release this package because...
> > > >
> > > > Here is my vote:
> > > > +1
> > >
> >
>

Re: New services for SINGA (Mentors help needed)

[Moaz Reyad]

Dear Alan,

Thank you for the help.

About Gitbox, the INFRA-17328 issue created a git repository for the source
code but not for the site.

We would like to create a new git repository (incubator-singa-site) instead
of the current SVN repository (
https://svn.apache.org/repos/asf/incubator/singa/site/)

Thank you,
Moaz

On Wed, Apr 3, 2019 at 7:49 PM Alan Gates  wrote:

> https://cwiki.apache.org/confluence/display/SINGA has been created.
> Moaz, I've made you the admin, you should be able to add others.
>
> Regarding gitbox, it appears that is finished based on the JIRA.  Is there
> something more to do?
>
> I have submitted a request to create the security email list and made moaz
> and wangwei the admins.  This is a private list, so you should only accept
> people on the PPMC or Apache members onto the list.
>
> Alan.
>
> On Mon, Apr 1, 2019 at 1:08 AM Moaz Reyad  wrote:
>
>> Dear SINGA mentors,
>>
>> What is your advice about this request to add new services for SINGA?
>>
>> Best regards
>> Moaz
>>
>> -- Forwarded message -
>> From: Moaz Reyad 
>> Date: Sat, Mar 9, 2019 at 11:39 AM
>> Subject: New services for SINGA (Mentors help needed)
>> To: 
>>
>>
>> Hi All,
>>
>> I would like to propose three new services for SINGA. These services can
>> be requested from (https://selfserve.apache.org/) but I do not have
>> permission to create them. I opened an INFRA ticket (
>> https://issues.apache.org/jira/browse/INFRA-17981), but the INFRA team
>> suggested that we ask assistance from mentors.
>>
>> 1. Confluence wiki:
>>
>> We need to create a space for SINGA at the Confluence wiki. The wiki is
>> required to keep the development pages which are not directly useful to
>> SINGA users. For example: the development schedule, how to prepare a
>> release, maturity assessment, etc.
>>
>> This issue was open before (
>> https://issues.apache.org/jira/browse/INFRA-9473) but it was not
>> completed.
>>
>> Please add my account:
>>
>> Wiki: https://cwiki.apache.org/confluence/display/~moazreyad
>> Apache ID: moaz
>>
>> SINGA team members who would like to contribute to the wiki may share
>> their wiki account, so they can have the write permission on the wiki pages.
>>
>> We can also try to enable the GitHub wiki, but I think Apache does not
>> allow this any more and the ASF encourages the use of Confluence instead.
>>
>> 2. GitBox repository for incubator-singa-site:
>>
>> This is required to move the singa site from SVN to Git. For more
>> information see (https://issues.apache.org/jira/browse/INFRA-17328)
>>
>> 3. Security mail list:
>>
>> We would like to create the private address: secur...@singa.apache.org
>> for security issues. There are some vulnerabilities already reported to
>> SINGA and we need to resolve them. The security mail list will help in
>> handling current and future security issues.
>>
>> Please add wang...@apache.org to this private mail list. For more
>> information see (https://issues.apache.org/jira/browse/SINGA-417). SINGA
>> team members who would like to join the security team may also share their
>> email.
>>
>> Best regards,
>> Moaz
>>
>

[jira] [Resolved] (SINGA-420) C++ Documentation out of date

[Moaz Reyad (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SINGA-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Moaz Reyad resolved SINGA-420.
--
Resolution: Fixed

> C++ Documentation out of date
> -
>
> Key: SINGA-420
> URL: https://issues.apache.org/jira/browse/SINGA-420
> Project: Singa
>  Issue Type: Improvement
>  Components: Documentation
>    Reporter: Moaz Reyad
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> There is a link to SINGA C++ documentation on the [main 
> page|http://singa.apache.org/] that points to an old [C++ 
> API|https://www.comp.nus.edu.sg/~dbsystem/singa/api/]. This API was generated 
> on Thu Feb 9 2017.
> The API should be updated since the C++ code was changed many times since Feb 
> 2017.
> I suggest to move the C++ documentation to the [ASF 
> site|https://svn.apache.org/repos/asf/incubator/singa/site/] and to generate 
> it automatically by adding the doxygen command in 
> [build.sh|https://github.com/apache/incubator-singa/blob/master/doc/build.sh].
> Please note that the [C++ documentation is not 
> complete|https://issues.apache.org/jira/browse/SINGA-336]. There are missing 
> documentation to be completed to increase the documentation coverage.
> This issue is also related to [SINGA graduation from the 
> incubator.|https://issues.apache.org/jira/browse/SINGA-405] Since complete 
> and updated documentation is useful for graduation.



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

[jira] [Created] (SINGA-436) Implement Apache Website Navigation Links Policy

[Moaz Reyad (JIRA)]

Moaz Reyad created SINGA-436:


 Summary: Implement Apache Website Navigation Links Policy
 Key: SINGA-436
 URL: https://issues.apache.org/jira/browse/SINGA-436
 Project: Singa
  Issue Type: Improvement
Reporter: Moaz Reyad


The [Apache Website Navigation Links 
Policy|https://www.apache.org/foundation/marks/pmcs#navigation] requires that 
SINGA website contains five links to License, Sponsorship, Thanks, Security and 
main ASF homepage.

Currently the "index.html" page of SINGA website which is generated by 
sphinx-doc contains only this line:

{code:html}
window.location.href='en/index.html';
{code}

This can be found by doing:

{code:bash}
wget http://singa.incubator.apache.org/
cat index.html
{code}

This causes the automatic crawl by [Apache Podling Website 
Checks|https://whimsy.apache.org/pods.cgi/project/singa] to fail.

The implementation of link policy is required before graduation from the 
incubator. 



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

[jira] [Commented] (SINGA-433) Preparation for V2.0 release

[Moaz Reyad (JIRA)]

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

Moaz Reyad commented on SINGA-433:
--

I can take tasks 6, 7 and 8. Please notify me when the task 5 is done and I 
will complete the rest. I can also test the Jupyter notebooks.

Also please note that the "how to release" steps are not complete. It was just 
a draft and not the final steps. For example, the steps mix the creation of 
release candidates and the creation of final releases. These should be two 
separate processes and the page "how to release" 
([http://singa.apache.org/en/develop/how-to-release.html)] must be updated to 
clarify this.

> Preparation for V2.0 release
> 
>
> Key: SINGA-433
> URL: https://issues.apache.org/jira/browse/SINGA-433
> Project: Singa
>  Issue Type: Task
>Reporter: wangwei
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> As discussed in the dev list, we are going to release v2.0 with some news 
> features and API changes. This ticket includes the tasks listed in the 
> [release process 
> page|http://singa.apache.org/en/develop/how-to-release.html]. If you want to 
> take one task, please include the task name and ID in the comments.
>  
> 1. Select a release manager. The release manager (RM) is the coordinator for 
> the release process. It is the RM's signature (.asc) that is uploaded 
> together with the release. The RM generates KEY (RSA 4096-bit) and uploads it 
> to a public key server. The RM needs to get his key endorsed (signed) by 
> other Apache user, to be connected to the web of trust. He should first ask 
> the mentor to help signing his key. 
> [http://www.apache.org/dev/release-signing.html]
>  
> 2. Check
>  * the codebase does not include third-party code which is not compatible to 
> APL;
>  * The dependencies are compatible with APL. GNU-like licenses are NOT 
> compatible; 
>  * All source files written by us MUST include the Apache license header: 
> [http://www.apache.org/legal/src-headers.html]. There's a script in there 
> which helps propagating the header to all files.
>  * 
> 3. Check
>  * The build process is error-free.
>  * Unit tests are included (as much as possible)
>  * The Jupyter notebooks are working with the new release
>  * The online documentation on the Apache website is up to date.
>  * Update the NOTICE file. If we include any third party code in the release 
> package which is not APL, must state it at the end of the NOTICE file.
>  * 
> 4. Prepare the RELEASE_NOTES file. Introduction, Features, Bugs (link to 
> JIRA), Changes (N/A for first erlease), Dependency list, Incompatibility 
> issues. Follow this example: 
> [http://commons.apache.org/proper/commons-digester/commons-digester-3.0/RELEASE-NOTES.txt].
>  Prepare DISCLAIMER file. modify from 
> [http://incubator.apache.org/guides/branding.html#disclaimers]
>  
> 5. Package the release. The release should be packaged into : 
> apache-singa-incubating-xx.xx.xx.tar.gz. The release should not include any 
> binary files including git files. Upload the release. The release is uploaded 
> to the RM’s Apache page: people.apache.org/~ID/.
>  * apache-singa-incubating-xx.xx.xx.tar.gz
>  * KEY
>  * XX.acs
>  * XX.md5
>  Roll out artifacts to mirrors. svn add to “dist/release/incubator/singa”
>  Delete old artifacts (automatically archived)
>  * 
> 6. Update the Download page. The tar.gz file MUST be downloaded from mirror, 
> using closer.cgi script; other artifacts MUST be downloaded from main Apache 
> site
>  Good idea to update EC2 image and make it available for download as well
>  
> 7. Make the internal announcements. Template for singa-dev@ voting:
> {code:java}
> To: dev@singa.incubator.apache.org
>  Subject: [VOTE] Release apache-singa-X.Y.Z-incubating (release candidate N)
> Hi all,
> I have created a build for Apache SINGA X.Y.Z-incubating, release candidate N.
> The artifacts to be voted on are located here:
>  
> [https://dist.apache.org/repos/dist/dev/incubator/singa/apache-singa-X.Y.Z-incubating-rcN/]
> The hashes of the artifacts are as follows:
>  apache-singa-X.Y.Z-incubating.tar.gz.md5 
>  apache-singa-X.Y.Z-incubating.tar.gz.sha256 
> Release artifacts are signed with the following key:
>  [https://people.apache.org/keys/committer/]
> {Apache ID of the Release Manager}
> .asc
> and the signature file is:
>  apache-singa-X.Y.Z-incubating.tar.gz.asc
> Please vote on releasing this package. The vote is open for at least 72 hours 
> a

Fwd: [jira] [Commented] (PODLINGNAMESEARCH-159) Establish whether "Apache SINGA" is a suitable name

[Moaz Reyad]

Hi All,

The Apache Brand Management has approved the name "Apache SINGA".

Best regards,
Moaz

-- Forwarded message -
From: Mark Thomas (JIRA) 
Date: Sun, Mar 10, 2019 at 11:24 PM
Subject: [jira] [Commented] (PODLINGNAMESEARCH-159) Establish whether
"Apache SINGA" is a suitable name

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

Mark Thomas commented on PODLINGNAMESEARCH-159:
---

Approved.

Mark
VP, Brand Management

> Establish whether "Apache SINGA" is a suitable name
> ---
>
> Key: PODLINGNAMESEARCH-159
> URL:
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-159
> Project: Podling Suitable Names Search
>  Issue Type: Suitable Name Search
>Reporter: Moaz Reyad
>
> SINGA is a distributed deep learning platform which is currently in the
process of graduation from the incubator (
https://issues.apache.org/jira/browse/SINGA-405).
> This issue is open to establish whether "Apache SINGA" is a suitable
name. A name search (https://incubator.apache.org/guides/names.html) is
required to complete the graduation.



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

New services for SINGA (Mentors help needed)

[Moaz Reyad]

Hi All,

I would like to propose three new services for SINGA. These services can be
requested from (https://selfserve.apache.org/) but I do not have permission
to create them. I opened an INFRA ticket (
https://issues.apache.org/jira/browse/INFRA-17981), but the INFRA team
suggested that we ask assistance from mentors.

1. Confluence wiki:

We need to create a space for SINGA at the Confluence wiki. The wiki is
required to keep the development pages which are not directly useful to
SINGA users. For example: the development schedule, how to prepare a
release, maturity assessment, etc.

This issue was open before (https://issues.apache.org/jira/browse/INFRA-9473)
but it was not completed.

Please add my account:

Wiki: https://cwiki.apache.org/confluence/display/~moazreyad
Apache ID: moaz

SINGA team members who would like to contribute to the wiki may share their
wiki account, so they can have the write permission on the wiki pages.

We can also try to enable the GitHub wiki, but I think Apache does not
allow this any more and the ASF encourages the use of Confluence instead.

2. GitBox repository for incubator-singa-site:

This is required to move the singa site from SVN to Git. For more
information see (https://issues.apache.org/jira/browse/INFRA-17328)

3. Security mail list:

We would like to create the private address: secur...@singa.apache.org for
security issues. There are some vulnerabilities already reported to SINGA
and we need to resolve them. The security mail list will help in handling
current and future security issues.

Please add wang...@apache.org to this private mail list. For more
information see (https://issues.apache.org/jira/browse/SINGA-417). SINGA
team members who would like to join the security team may also share their
email.

Best regards,
Moaz

[DISCUSS] Graduate SINGA as a TLP

[Moaz Reyad]

Hi All,

Given the progress of SINGA graduation from the incubator (
https://issues.apache.org/jira/browse/SINGA-405) and the complete maturity
assessment (
https://github.com/apache/incubator-singa/blob/91a4f7a7b8b913644299c7af48b042a867554290/doc/en/develop/maturity-model-assessment.md),
I would like to discuss the remaining tasks for graduation.

Please share your thoughts. Mentors advises are welcome.

Best regards,
Moaz

Re: [jira] [Commented] (SINGA-428) Move Docker images under Apache user name

[Moaz Reyad]

We can push through Jenkins build or by asking INFRA to give permissions to
DockerHub users.

For more details, please check:

https://issues.apache.org/jira/browse/INFRA-17878

Moaz

On Wed, Feb 27, 2019 at 4:46 PM Wang Wei  wrote:

> How can we push to https://hub.docker.com/r/apache/singa?
>
> On Tue, Feb 26, 2019 at 1:40 PM Wang Wei  wrote:
>
> > +1. Rafiki is using docker.
> >
> > On Tue, Feb 26, 2019 at 12:58 PM Moaz Reyad (JIRA) 
> > wrote:
> >
> >>
> >> [
> >>
> https://issues.apache.org/jira/browse/SINGA-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16777577#comment-16777577
> >> ]
> >>
> >> Moaz Reyad commented on SINGA-428:
> >> --
> >>
> >> May be also we can put Rafiki Docker images in [SINGA DockerHub page|
> >> https://hub.docker.com/r/apache/singa/]. This can be done by building
> >> the Admin, Advisor, Predictor and Worker images in the
> Rafiki/dockerfiles
> >> (from an official release of SINGA) and push them to the DockerHub.
> What do
> >> you think?
> >>
> >> > Move Docker images under Apache user name
> >> > -
> >> >
> >> > Key: SINGA-428
> >> > URL: https://issues.apache.org/jira/browse/SINGA-428
> >> > Project: Singa
> >> >  Issue Type: Bug
> >> >Reporter: Moaz Reyad
> >> >Priority: Major
> >> >  Time Spent: 10m
> >> >  Remaining Estimate: 0h
> >> >
> >> > The Docker images of SINGA are now on Docker Hub [here|
> >> https://hub.docker.com/r/nusdbsystem/singa/]. They are not under the
> >> [Apache docker username|https://hub.docker.com/u/apache/].
> >> > To solve this problem, we create a ticket at INFRA to provide the name
> >> space SINGA.
> >> > We also need to make sure that the docker images of SINGA are built
> >> using official releases and not using latest (master) branch which is
> not
> >> official.
> >>
> >>
> >>
> >> --
> >> This message was sent by Atlassian JIRA
> >> (v7.6.3#76005)
> >>
> >
>

[jira] [Commented] (SINGA-428) Move Docker images under Apache user name

[Moaz Reyad (JIRA)]

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

Moaz Reyad commented on SINGA-428:
--

May be also we can put Rafiki Docker images in [SINGA DockerHub 
page|https://hub.docker.com/r/apache/singa/]. This can be done by building the 
Admin, Advisor, Predictor and Worker images in the Rafiki/dockerfiles (from an 
official release of SINGA) and push them to the DockerHub. What do you think?

> Move Docker images under Apache user name
> -
>
> Key: SINGA-428
> URL: https://issues.apache.org/jira/browse/SINGA-428
> Project: Singa
>  Issue Type: Bug
>Reporter: Moaz Reyad
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The Docker images of SINGA are now on Docker Hub 
> [here|https://hub.docker.com/r/nusdbsystem/singa/]. They are not under the 
> [Apache docker username|https://hub.docker.com/u/apache/].
> To solve this problem, we create a ticket at INFRA to provide the name space 
> SINGA.
> We also need to make sure that the docker images of SINGA are built using 
> official releases and not using latest (master) branch which is not official.



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

[jira] [Created] (SINGA-428) Move Docker images under Apache user name

[Moaz Reyad (JIRA)]

Moaz Reyad created SINGA-428:


 Summary: Move Docker images under Apache user name
 Key: SINGA-428
 URL: https://issues.apache.org/jira/browse/SINGA-428
 Project: Singa
  Issue Type: Bug
Reporter: Moaz Reyad


The Docker images of SINGA are now on Docker Hub 
[here|https://hub.docker.com/r/nusdbsystem/singa/]. They are not under the 
[Apache docker username|https://hub.docker.com/u/apache/].

To solve this problem, we create a ticket at INFRA to provide the name space 
SINGA.

We also need to make sure that the docker images of SINGA are built using 
official releases and not using latest (master) branch which is not official.



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

Re: [DISCUSSION] Release Singa 2.0

[Moaz Reyad]

+1

On Mon, Jan 21, 2019 at 5:13 AM Jinyang Gao 
wrote:

> +1
>
> Best Regards
> -Jinyang
>
>
> On Mon, Jan 21, 2019 at 6:47 AM ooibc  wrote:
>
> >
> > +1
> >
> >
> >
> > On 2019-01-21 00:16, zhongle wrote:
> > > +1
> > >
> > >> On Jan 20, 2019, at 23:11, Wang Wei  wrote:
> > >>
> > >> Hi all,
> > >>
> > >> I want to start the discussion of releasing Singa 2.0.
> > >> Since V1.0, we have added many new major features, e.g.,
> > >> 1. autograd
> > >> 2. rafiki
> > >> 3. mkl-dnn (to be merged)
> > >> 4. onnx (to be merged)
> > >>
> > >> I think it is time to release v2.0 (after merging the PRs for mkl-dnn
> > >> and
> > >> onnx).
> > >> May I have your comments?
> > >> Thanks!
> > >>
> > >> Regards,
> > >> Wei
> >
> >
>

[jira] [Commented] (SINGA-418) Unsupportive type 'long' in python3.

[Moaz Reyad (JIRA)]

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

Moaz Reyad commented on SINGA-418:
--

Please do not forget to check also this 
[commit|https://github.com/apache/incubator-singa/commit/8d9eb297dd7c2263b5face4bfcaf80a1a6680be8#r31652823],
 because [this 
line|https://github.com/apache/incubator-singa/blob/master/python/singa/tensor.py#L291]
 can make the same problem.

> Unsupportive type 'long' in python3.
> 
>
> Key: SINGA-418
> URL: https://issues.apache.org/jira/browse/SINGA-418
> Project: Singa
>  Issue Type: Bug
>Reporter: Liu Hui
>Priority: Major
> Attachments: Screenshot from 2018-12-12 11-20-36.png
>
>
> When I trained the mnist of examples, "NameError: name 'long' is not defined" 
> occurred.
> {code:java}
> // python train.py mnist.pkl.gz --use_gpu
> {code}
> Python3.6 is used.



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

[jira] [Created] (SINGA-420) C++ Documentation out of date

[Moaz Reyad (JIRA)]

Moaz Reyad created SINGA-420:


 Summary: C++ Documentation out of date
 Key: SINGA-420
 URL: https://issues.apache.org/jira/browse/SINGA-420
 Project: Singa
  Issue Type: Improvement
  Components: Documentation
Reporter: Moaz Reyad


There is a link to SINGA C++ documentation on the [main 
page|http://singa.apache.org/] that points to an old [C++ 
API|https://www.comp.nus.edu.sg/~dbsystem/singa/api/]. This API was generated 
on Thu Feb 9 2017.

The API should be updated since the C++ code was changed many times since Feb 
2017.

I suggest to move the C++ documentation to the [ASF 
site|https://svn.apache.org/repos/asf/incubator/singa/site/] and to generate it 
automatically by adding the doxygen command in 
[build.sh|https://github.com/apache/incubator-singa/blob/master/doc/build.sh].

Please note that the [C++ documentation is not 
complete|https://issues.apache.org/jira/browse/SINGA-336]. There are missing 
documentation to be completed to increase the documentation coverage.

This issue is also related to [SINGA graduation from the 
incubator.|https://issues.apache.org/jira/browse/SINGA-405] Since complete and 
updated documentation is useful for graduation.



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

[jira] [Commented] (SINGA-418) Unsupportive type 'long' in python3.

[Moaz Reyad (JIRA)]

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

Moaz Reyad commented on SINGA-418:
--

In Python 3, [there is no 
long|https://docs.python.org/3.3/whatsnew/3.0.html#integers]. The problem is in 
[this 
commit|https://github.com/apache/incubator-singa/commit/7d25ed93b4a05ef24ec73b8277945bd24db716d2#r31652793].

This 
[commit|https://github.com/apache/incubator-singa/commit/8d9eb297dd7c2263b5face4bfcaf80a1a6680be8#r31652823]
 also may need to be fixed.

> Unsupportive type 'long' in python3.
> 
>
> Key: SINGA-418
> URL: https://issues.apache.org/jira/browse/SINGA-418
> Project: Singa
>  Issue Type: Bug
>Reporter: Liu Hui
>Priority: Major
> Attachments: Screenshot from 2018-12-12 11-20-36.png
>
>
> When I trained the mnist of examples, "NameError: name 'long' is not defined" 
> occurred.
> {code:java}
> // python train.py mnist.pkl.gz --use_gpu
> {code}
> Python3.6 is used.



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

[jira] [Closed] (SINGA-417) Adding security channel

[Moaz Reyad (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SINGA-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Moaz Reyad closed SINGA-417.

Resolution: Fixed

It seems that the smart commit command "#close" did not work. I close the issue 
manually. 

> Adding security channel
> ---
>
> Key: SINGA-417
> URL: https://issues.apache.org/jira/browse/SINGA-417
> Project: Singa
>  Issue Type: New Feature
>  Components: Documentation
>Reporter: Moaz Reyad
>Priority: Blocker
>
> According to the [Apache Project Maturity 
> Model|https://community.apache.org/apache-way/apache-project-maturity-model.html]:
> ??QU30: The project provides a well-documented, secure and private channel to 
> report security issues, along with a documented way of responding to them.??
> ??Apache projects can just point to [http://www.apache.org/security/] or use 
> their own security contacts page, which should also point to that.??
> This issue can be solved simply by adding a link to Apache Security page to 
> SINGA website.
> However, I would also suggest to :
>  # create a sub team in SINGA (even starting with one person) for security
>  # ask for an email security@singa.apache for project security contacts
>  # create a new page for security in SINGA website
>  # add SINGA security team (page and email) to [ASF Project Security 
> Information page|https://www.apache.org/security/projects.html]
> Machine learning systems like SINGA may work with sensitive data (e.g. 
> medical data, finance, etc.) and SINGA provides distributed training where 
> data and models can be shared in a network. If SINGA security team provides 
> details to ensure the best security practices, this can be an important 
> feature to show in SINGA now or in a future release.



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

Re: [jira] [Commented] (SINGA-415) Moving SINGA to Gitbox

[Moaz Reyad]

Thank you for the vote.

I don't have access to request the website repository from
selfserve.apache.org . It says "You MUST be on the PMC or PPMC of the
project you wish to create a new repository for."

We need someone from the PMC or PPMC to create the singa-site repository
and populate it as described below.

Best,
Moaz

On Mon, Dec 3, 2018 at 3:13 PM Wang Wei  wrote:

> +1
>
> On Mon, Dec 3, 2018 at 6:19 PM Moaz Reyad (JIRA)  wrote:
>
> >
> > [
> >
> https://issues.apache.org/jira/browse/SINGA-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16706942#comment-16706942
> > ]
> >
> > Moaz Reyad commented on SINGA-415:
> > --
> >
> > SINGA code repo is moved to Gitbox, but SINGA site is still in [SVN|[
> > https://svn.apache.org/repos/asf/incubator/singa/site/]. I think it is
> > better to move it also to git to have both repos in gitbox. To do this we
> > need to request a web site repository first.
> >
> > From the INFRA ticket:
> >
> > "For the svn repo for your web site, you'll have to request a web site
> > repository yourself via selfserve.apache.org and populate an asf-site
> > branch with content before we can switch over to gitpubsub."
> >
> > > Moving SINGA to Gitbox
> > > --
> > >
> > >     Key: SINGA-415
> > > URL: https://issues.apache.org/jira/browse/SINGA-415
> > > Project: Singa
> > >  Issue Type: Task
> > >Reporter: Moaz Reyad
> > >Priority: Minor
> > >
> > > This issue collects the internal work which is required in SINGA after
> > [moving to GitBox|https://issues.apache.org/jira/browse/INFRA-17328].
> > > Some modifications are required such as updating the [source
> repository|
> > http://singa.apache.org/en/community/source-repository.html] page in the
> > website.
> >
> >
> >
> > --
> > This message was sent by Atlassian JIRA
> > (v7.6.3#76005)
> >
>

[jira] [Commented] (SINGA-417) Adding security channel

[Moaz Reyad (JIRA)]

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

Moaz Reyad commented on SINGA-417:
--

The dev@ list is public while the security channel should be

??secure and *+private+* channel to report security issues??


> Adding security channel
> ---
>
> Key: SINGA-417
> URL: https://issues.apache.org/jira/browse/SINGA-417
> Project: Singa
>  Issue Type: New Feature
>  Components: Documentation
>    Reporter: Moaz Reyad
>Priority: Blocker
>
> According to the [Apache Project Maturity 
> Model|https://community.apache.org/apache-way/apache-project-maturity-model.html]:
> ??QU30: The project provides a well-documented, secure and private channel to 
> report security issues, along with a documented way of responding to them.??
> ??Apache projects can just point to [http://www.apache.org/security/] or use 
> their own security contacts page, which should also point to that.??
> This issue can be solved simply by adding a link to Apache Security page to 
> SINGA website.
> However, I would also suggest to :
>  # create a sub team in SINGA (even starting with one person) for security
>  # ask for an email security@singa.apache for project security contacts
>  # create a new page for security in SINGA website
>  # add SINGA security team (page and email) to [ASF Project Security 
> Information page|https://www.apache.org/security/projects.html]
> Machine learning systems like SINGA may work with sensitive data (e.g. 
> medical data, finance, etc.) and SINGA provides distributed training where 
> data and models can be shared in a network. If SINGA security team provides 
> details to ensure the best security practices, this can be an important 
> feature to show in SINGA now or in a future release.



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

[jira] [Commented] (SINGA-402) Rafiki - adding Swagger support

[Moaz Reyad (JIRA)]

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

Moaz Reyad commented on SINGA-402:
--

I would like to add also that if we have swagger file for the API, we can use 
[ReDoc|https://github.com/Rebilly/ReDoc] to add the API documentation to  
[SINGA website|http://singa.apache.org/].

See for example the [REST API for Apache 
Pulsar|https://pulsar.apache.org/en/admin-rest-api/].

> Rafiki - adding Swagger support
> ---
>
> Key: SINGA-402
> URL: https://issues.apache.org/jira/browse/SINGA-402
> Project: Singa
>  Issue Type: Improvement
>Reporter: Moaz Reyad
>Priority: Major
> Attachments: rafiki.json
>
>
> [Swagger|http://swagger.io/] is a software tool that helps in design, 
> development, documenting and testing of RESTful web services.
> It is proposed to add Swagger support for Rafiki web API. This will help u

> sers and developers to run the web queries from Swagger UI directly instead 
> of using _curl_ or _python_ commands. It will also help in documentation and 
> testing.
> An example file is provided with this issue to check if this proposal will be 
> useful or not. The attached file has two working examples from the current 
> Rafiki web API: /tokens and /models. 

To run the file:
> {code}
> $ docker run -p 80:8080 -e SWAGGER_JSON=/rafiki-api/rafiki.json -v 
> /{PATH_TO_RAFIKI.JSON}:/rafiki-api swaggerapi/swagger-ui
> {code}
> (Replace / { PATH_TO_RAFIKI.JSON}
> with the path to rafiki.json file in your machine)
> Start Rafiki and open "localhost" in web browser to show Swagger UI for the 
> API.



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

[jira] [Created] (SINGA-417) Adding security channel

[Moaz Reyad (JIRA)]

Moaz Reyad created SINGA-417:


 Summary: Adding security channel
 Key: SINGA-417
 URL: https://issues.apache.org/jira/browse/SINGA-417
 Project: Singa
  Issue Type: New Feature
  Components: Documentation
Reporter: Moaz Reyad


According to the [Apache Project Maturity 
Model|https://community.apache.org/apache-way/apache-project-maturity-model.html]:

??QU30: The project provides a well-documented, secure and private channel to 
report security issues, along with a documented way of responding to them.??

??Apache projects can just point to [http://www.apache.org/security/] or use 
their own security contacts page, which should also point to that.??

This issue can be solved simply by adding a link to Apache Security page to 
SINGA website.

However, I would also suggest to :
 # create a sub team in SINGA (even starting with one person) for security
 # ask for an email security@singa.apache for project security contacts
 # create a new page for security in SINGA website
 # add SINGA security team (page and email) to [ASF Project Security 
Information page|https://www.apache.org/security/projects.html]

Machine learning systems like SINGA may work with sensitive data (e.g. medical 
data, finance, etc.) and SINGA provides distributed training where data and 
models can be shared in a network. If SINGA security team provides details to 
ensure the best security practices, this can be an important feature to show in 
SINGA now or in a future release.



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

[jira] [Created] (SINGA-416) Addinig Jupyter Notebook for Rafiki

[Moaz Reyad (JIRA)]

Moaz Reyad created SINGA-416:


 Summary: Addinig Jupyter Notebook for Rafiki
 Key: SINGA-416
 URL: https://issues.apache.org/jira/browse/SINGA-416
 Project: Singa
  Issue Type: Improvement
  Components: Documentation
Reporter: Moaz Reyad


The [SINGA Jupyter notebook 
page|http://nbviewer.jupyter.org/github/apache/incubator-singa/blob/master/doc/en/docs/notebook/index.ipynb]
 says that Rafiki tutorial is still Work In Progress.

Since a new version of Rafiki is developed now, we can create a notebook 
tutorial for using it. This tutorial can be copied from [Rafiki’s HTML 
Documentation|https://nginyc.github.io/rafiki/docs/latest/] and converted to 
notebook format.



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

[jira] [Commented] (SINGA-405) Graduate Apache SINGA (incubating) as a TLP

[Moaz Reyad (JIRA)]

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

Moaz Reyad commented on SINGA-405:
--

I would like to add that [Griffin was the 199 project to graduate from the 
incubator|http://mail-archives.apache.org/mod_mbox/incubator-general/201811.mbox/%3CB668F9EA-C311-4016-8ACF-10149D358291%40classsoftware.com%3E].
 The next project to graduate will be the 200th top level project and will gain 
more visibility in the ASF publicity.

For this reason, I suggest that all members of SINGA team give priority to the 
graduation tasks to graduate SINGA now before any other incubator project to 
catch this rare marketing opportunity. 

Also the project needs the mentors to help and guide during the graduation 
process.

> 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)

[jira] [Commented] (SINGA-415) Moving SINGA to Gitbox

[Moaz Reyad (JIRA)]

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

Moaz Reyad commented on SINGA-415:
--

SINGA code repo is moved to Gitbox, but SINGA site is still in 
[SVN|[https://svn.apache.org/repos/asf/incubator/singa/site/]. I think it is 
better to move it also to git to have both repos in gitbox. To do this we need 
to request a web site repository first.

>From the INFRA ticket:

"For the svn repo for your web site, you'll have to request a web site 
repository yourself via selfserve.apache.org and populate an asf-site branch 
with content before we can switch over to gitpubsub."

> Moving SINGA to Gitbox
> --
>
> Key: SINGA-415
> URL: https://issues.apache.org/jira/browse/SINGA-415
> Project: Singa
>      Issue Type: Task
>Reporter: Moaz Reyad
>Priority: Minor
>
> This issue collects the internal work which is required in SINGA after 
> [moving to GitBox|https://issues.apache.org/jira/browse/INFRA-17328]. 
> Some modifications are required such as updating the [source 
> repository|http://singa.apache.org/en/community/source-repository.html] page 
> in the website.



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

[jira] [Created] (SINGA-415) Moving SINGA to Gitbox

[Moaz Reyad (JIRA)]

Moaz Reyad created SINGA-415:


 Summary: Moving SINGA to Gitbox
 Key: SINGA-415
 URL: https://issues.apache.org/jira/browse/SINGA-415
 Project: Singa
  Issue Type: Task
Reporter: Moaz Reyad


This issue collects the internal work which is required in SINGA after [moving 
to GitBox|https://issues.apache.org/jira/browse/INFRA-17328]. 

Some modifications are required such as updating the [source 
repository|http://singa.apache.org/en/community/source-repository.html] page in 
the website.





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

[jira] [Commented] (SINGA-405) Graduate Apache SINGA (incubating) as a TLP

[Moaz Reyad (JIRA)]

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

Moaz Reyad commented on SINGA-405:
--

SINGA is moved now to Gitbox. The INFRA ticket is 
[here|https://issues.apache.org/jira/browse/INFRA-17328]. The [old code 
repository|https://git-wip-us.apache.org/repos/asf?p=incubator-singa.git] is 
not valid now. The new code is 
[here|https://gitbox.apache.org/repos/asf?p=incubator-singa.git]. 

However, I can't create a wiki page in github for SINGA. May be I don't have 
permissions for this also. 

> 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)

[RESULT] [VOTE] Move SINGA to Gitbox

[Moaz Reyad]

The vote passes with 3 +1 :

+1 wei
+1 zhongle
+1 moaz

Thank you,
Moaz