Re: Next Steps in the graduation process

[Luciano Resende]

FYI, I have started the Graduation discussion on the general list

https://www.mail-archive.com/general@incubator.apache.org/msg59666.html

On Thu, Apr 6, 2017 at 4:03 PM, Berthold Reinwald <reinw...@us.ibm.com>
wrote:

> just to complete this email thread ... Maturity model assessment has been
> posted at: http://systemml.apache.org/maturity
>
>
> Regards,
> Berthold Reinwald
> IBM Almaden Research Center
> office: (408) 927 2208; T/L: 457 2208
> e-mail: reinw...@us.ibm.com
>
>
>
> From:   Henry Saputra <henry.sapu...@gmail.com>
> To: dev@systemml.incubator.apache.org
> Date:   03/16/2017 11:39 PM
> Subject:Re: Next Steps in the graduation process
>
>
>
> It is actually not mandatory. But, it would help us go through evaluation
> from IPMCs when we ask for VOTE in the general@ list.
>
> Also self evaluation for the podlng itself.
>
> - Henry
>
> On Thu, Mar 16, 2017 at 1:45 PM, Berthold Reinwald <reinw...@us.ibm.com>
> wrote:
>
> > i'm working on it.
> >
> >
> > Regards,
> > Berthold Reinwald
> > IBM Almaden Research Center
> > office: (408) 927 2208; T/L: 457 2208
> > e-mail: reinw...@us.ibm.com
> >
> >
> >
> > From:   Matthias Boehm <mboe...@googlemail.com>
> > To: dev@systemml.incubator.apache.org
> > Date:   03/16/2017 01:41 PM
> > Subject:Re: Next Steps in the graduation process
> >
> >
> >
> > well, then this was a misunderstanding - I took your statement "We might
> > also need a Maturity Model assessment" just as a heads-up for something
> > that might not necessarily be required. Anyway, I could look into it
> > tonight, unless someone else volunteers who could do it immediately.
> >
> > Regards,
> > Matthias
> >
> > On Thu, Mar 16, 2017 at 12:48 PM, Luciano Resende <luckbr1...@gmail.com>
> > wrote:
> >
> > > Has anyone been able to work on the Maturity Model?
> > > I believe this is one of the last things we are waiting for.
> > >
> > > On Tue, Mar 7, 2017 at 10:48 PM, Matthias Boehm
> <mboe...@googlemail.com>
> > > wrote:
> > >
> > > > I could help doing this assessment. Btw, here is a working link:
> > > > https://community.apache.org/apache-way/apache-project-
> > > maturity-model.html
> > > >
> > > > Regards,
> > > > Matthias
> > > >
> > > > On Tue, Mar 7, 2017 at 1:38 PM, Luciano Resende
> <luckbr1...@gmail.com>
> > > > wrote:
> > > >
> > > > > On Tue, Mar 7, 2017 at 11:59 AM, Arvind Surve
> > <ac...@yahoo.com.invalid
> > > >
> > > > > wrote:
> > > > >
> > > > > > I will start looking at discussion and drafting a board
> resolution
> > > for
> > > > > > SystemML as a TLP project Arvind Surve | Spark Technology Center
> |
> > > > > > http://www.spark.tc/
> > > > > >
> > > > > >
> > > > > Thank you,
> > > > >
> > > > > We might also need a Maturity Model assessment, any other
> volunteer
> > > that
> > > > > could help with the task?
> > > > >
> > > > > Here is some documentation about MM
> > > > > https://community.apache.org/apache-way/apache-project-
> > > > maturity-model.htm
> > > > >
> > > > > And here is an example from another podling that is working on
> > > graduating
> > > > > as well
> > > > > https://cwiki.apache.org/confluence/pages/viewpage.
> > > > action?pageId=68714623
> > > > >
> > > > > --
> > > > > Luciano Resende
> > > > > http://twitter.com/lresende1975
> > > > > http://lresende.blogspot.com/
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Luciano Resende
> > > http://twitter.com/lresende1975
> > > http://lresende.blogspot.com/
> > >
> >
> >
> >
> >
> >
>
>
>
>
>


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [DISCUSS] Board resolution for SystemML as a TLP project

[Luciano Resende]

Updating with Felix as he has recently been elected as project PPMC

Resolution draft:

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 declarative,
large-scale machine learning that compiles to hybrid runtime
execution plans ranging from single node, in-memory computations,
to distributed computations such as on Apache Hadoop MapReduce or
Apache Spark.

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

RESOLVED, that the Apache SystemML Project be and hereby is
responsible for the creation and maintenance of software related to
declarative, large-scale machine learning; and be it further

RESOLVED, that the office of "Vice President, Apache SystemML" 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
SystemML Project, and to have primary responsibility for management of
the projects within the scope of responsibility of the Apache SystemML
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 SystemML
Project:
 * Alexandre V Evfimievski   <ae2...@apache.org>
* Arvind Surve  <ac...@apache.org>
* Berthold Reinwald <reinw...@apache.org>
* DB Tsai   <dbt...@apache.org>
* Deron Eriksson<de...@apache.org>
* Faraz Makari  <fmak...@apache.org>
* Felix Schueler
* Fred Reiss<fre...@apache.org>
* Glenn Weidner <gweid...@apache.org>
* Henry Saputra <hsapu...@apache.org>
* Holden Karau  <hol...@apache.org>
* Joseph Bradley<jkbrad...@apache.org>
* Luciano Resende   <lrese...@apache.org>
* Matthias Boehm<mboe...@apache.org>*
Nakul Jindal  <naku...@apache.org>* Mike
Dusenberry   <dusenberr...@apache.org>
* Niketan Pansare   <niketanpans...@apache.org>
* Patrick Wendell   <pwend...@apache.org>
* Prithviraj Sen<prit...@apache.org>
* Reynold Xin   <r...@apache.org>
* Rich Bowen<rbo...@apache.org>
* Shirish Tatikonda <shiri...@apache.org>
* Xiangrui Meng <m...@apache.org>

NOW, THEREFORE, BE IT FURTHER RESOLVED, that XXX be appointed to the
office of Vice President, Apache SystemML, 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 SystemML 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 SystemML
Project; and be it further

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

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



On Thu, Mar 9, 2017 at 1:14 AM, Berthold Reinwald <reinw...@us.ibm.com>
wrote:

> Thanks, Henry. We added in your comment.
>
> Arvind actually had in a comment like that before but we removed it as we
> didn't want to over-constrain the resolution.
>
>
> Resolution draft:
>
> 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 declarative,
> large-scale machine learning that compiles to hybrid runtime
> execution plans ranging from single node, in-memory computations,
> to distributed computations such as on Apache Hadoop MapReduce or
> Apache Spark.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Manage

Re: Branch 0.14 based on SystemML-0.14 RC1 has been deleted

[Luciano Resende]

+1

On Thu, Apr 6, 2017 at 9:03 AM, Arvind Surve <ac...@yahoo.com.invalid>
wrote:

> Hi,
> Branch 0.14 based on SystemML-0.14 RC1 has been deleted.
> Going forward unless there is immediate need for a branch, branch based on
>  Release Candidate (RC) won't be created until RC build gets approved.
> -Arvind Arvind Surve | Spark Technology Center  | http://www.spark.tc/




-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Java compiler for code generation

[Luciano Resende]

Is dependency really an issue today, particularly when we bundle the
dependencies with the SystemML jar ? I'd rather include a dependency then
reinventing the wheel and create some code again (unless the dependency
code is flawed).

Also, +1 for continuously reviewing / updating / triming out dependencies.

On Mon, Apr 3, 2017 at 11:04 AM, <dusenberr...@gmail.com> wrote:

> Using Janino sounds like a great idea.  As for the footprint size for
> Java-only execution modes, it might make sense to do an audit of our
> current dependencies to see if anything can be removed to make up for the
> additional amount.  Then we could just use it in all scenarios without
> worry.
>
> --
>
> Mike Dusenberry
> GitHub: github.com/dusenberrymw
> LinkedIn: linkedin.com/in/mikedusenberry
>
> Sent from my iPhone.
>
>
> > On Mar 31, 2017, at 9:25 PM, Matthias Boehm <mboe...@googlemail.com>
> wrote:
> >
> > that is a good question. Yes, if we want to enable code generation in
> such
> > a scenario it would also need Janino, which increases our footprint by
> > roughly 0.6MB.
> >
> > Btw, Janino fits much better into such an in-memory deployment because it
> > compiles classes in-memory without the need to write class files into a
> > local working directory. The same could be done for
> > javax.tools.JavaCompiler, but would require to custom in-memory
> > JavaFileManager.
> >
> > Regards,
> > Matthias
> >
> > On Fri, Mar 31, 2017 at 9:14 PM, Berthold Reinwald <reinw...@us.ibm.com>
> > wrote:
> >
> >> Sounds like a good idea.
> >>
> >> Wrt codegen, in a pure Java scoring environment w/o Spark and Hadoop,
> will
> >> the dependency on Janino still be there (that question applies to JDK as
> >> well), and what is the footprint?
> >>
> >> Regards,
> >> Berthold Reinwald
> >> IBM Almaden Research Center
> >> office: (408) 927 2208; T/L: 457 2208
> >> e-mail: reinw...@us.ibm.com
> >>
> >>
> >>
> >> From:   Matthias Boehm <mboe...@googlemail.com>
> >> To: dev@systemml.incubator.apache.org
> >> Date:   03/31/2017 08:17 PM
> >> Subject:Java compiler for code generation
> >>
> >>
> >>
> >> Hi all,
> >>
> >> currently, our new code generator for operator fusion, uses the
> >> programmatic javax.tools.JavaCompiler, which is Java's standard API for
> >> compilation. Despite a plan cache that mitigates unnecessary compilation
> >> and recompilation overheads, we still see significant end-to-end
> overhead
> >> especially for small input data.
> >>
> >> Moving forward, I'd like to switch to Janino
> >> (org.codehaus.janino.SimpleCompiler), which is a fast in-memory Java
> >> compiler with restricted language support. The advantages are
> >>
> >> (1) Reduced compilation overhead: On end-to-end scenarios for L2SVM,
> GLM,
> >> and MLogreg, Janino improved total javac compilation time from 2.039 to
> >> 0.195 (14 operators), from 8.134 to 0.411 (82 operators), and from 4.854
> >> to
> >> 0.283 (46 operators), respectively. At the same time, there was no
> >> measurable impact on runtime efficiency, but even slightly reduced JIT
> >> compilation overhead.
> >>
> >> (2) Removed JDK requirement: Using the standard javax.tools.JavaCompiler
> >> requires the existence of a JDK, while Janino only requires a JRE, which
> >> means it makes it easier to apply code generation by default.
> >>
> >> However, I'm raising this here as Janino would add another explicit
> >> dependency (with BSD license). Fortunately, Spark also uses Janino for
> >> whole-stage-codegen. So we should be able to mark Janino as provided
> >> library. The only issue is a pure Hadoop environment, where we still
> want
> >> to use code generation for CP operations. To simplify the build, I could
> >> imagine using the javax.tools.JavaCompiler for hadoop execution types,
> but
> >> Janino by default.
> >>
> >> If you have any concerns, please let me know by Monday; otherwise I'd
> like
> >> to push this change into our upcoming 0.14 release.
> >>
> >>
> >> Regards,
> >> Matthias
> >>
> >>
> >>
> >>
> >>
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: SystemML 0.14 release build plan

[Luciano Resende]

Ok, I looked in the "Release Cadence" thread and found the recent
discussions for 0.14

Here is a link to recent conversation for the benefit of others

https://www.mail-archive.com/dev@systemml.incubator.apache.org/msg01518.html



On Wed, Mar 29, 2017 at 5:20 PM, Luciano Resende <luckbr1...@gmail.com>
wrote:

> What is planned for 0.14?
> When the contents and dates where discussed?
>
> On Wed, Mar 29, 2017 at 4:02 PM Arvind Surve <ac...@yahoo.com.invalid>
> wrote:
>
>> Hi,
>> We will be building SystemML 0.14 on Monday 04/03/2017 PST.
>> Please plan on getting your changes by EOW 04/02/2017 PST
>> Thanks,
>> Arvind Surve | Spark Technology Center  | http://www.spark.tc/
>>
>>
>>
>
> --
> Sent from my Mobile device
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: SystemML 0.14 release build plan

[Luciano Resende]

What is planned for 0.14?
When the contents and dates where discussed?

On Wed, Mar 29, 2017 at 4:02 PM Arvind Surve 
wrote:

> Hi,
> We will be building SystemML 0.14 on Monday 04/03/2017 PST.
> Please plan on getting your changes by EOW 04/02/2017 PST
> Thanks,
> Arvind Surve | Spark Technology Center  | http://www.spark.tc/
>
>
>

-- 
Sent from my Mobile device

Re: Next Steps in the graduation process

[Luciano Resende]

Has anyone been able to work on the Maturity Model?
I believe this is one of the last things we are waiting for.

On Tue, Mar 7, 2017 at 10:48 PM, Matthias Boehm <mboe...@googlemail.com>
wrote:

> I could help doing this assessment. Btw, here is a working link:
> https://community.apache.org/apache-way/apache-project-maturity-model.html
>
> Regards,
> Matthias
>
> On Tue, Mar 7, 2017 at 1:38 PM, Luciano Resende <luckbr1...@gmail.com>
> wrote:
>
> > On Tue, Mar 7, 2017 at 11:59 AM, Arvind Surve <ac...@yahoo.com.invalid>
> > wrote:
> >
> > > I will start looking at discussion and drafting a board resolution for
> > > SystemML as a TLP project Arvind Surve | Spark Technology Center  |
> > > http://www.spark.tc/
> > >
> > >
> > Thank you,
> >
> > We might also need a Maturity Model assessment, any other volunteer that
> > could help with the task?
> >
> > Here is some documentation about MM
> > https://community.apache.org/apache-way/apache-project-
> maturity-model.htm
> >
> > And here is an example from another podling that is working on graduating
> > as well
> > https://cwiki.apache.org/confluence/pages/viewpage.
> action?pageId=68714623
> >
> > --
> > Luciano Resende
> > http://twitter.com/lresende1975
> > http://lresende.blogspot.com/
> >
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Next Steps in the graduation process

[Luciano Resende]

We have done that prior to entering Incubator
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-89

On Fri, Mar 10, 2017 at 4:07 PM, Henry Saputra <henry.sapu...@gmail.com>
wrote:

> We need name check for TLP.
> Has JIRA for check for SystemML has been done/approved by ASF legal?
>
> - Henry
>
> On Fri, Mar 10, 2017 at 2:14 PM, Luciano Resende <luckbr1...@gmail.com>
> wrote:
>
> > I have updated the community/project portion of the SystemML podling page
> >
> > http://incubator.apache.org/projects/systemml.html
> >
> > Please take a look and let me know if I missed anything.
> >
> >
> > On Wed, Mar 8, 2017 at 11:47 AM, Luciano Resende <luckbr1...@gmail.com>
> > wrote:
> >
> > > Great, thank you for the link correction...
> > >
> > > On Tue, Mar 7, 2017 at 10:48 PM, Matthias Boehm <
> mboe...@googlemail.com>
> > > wrote:
> > >
> > >> I could help doing this assessment. Btw, here is a working link:
> > >> https://community.apache.org/apache-way/apache-project-matur
> > >> ity-model.html
> > >>
> > >> Regards,
> > >> Matthias
> > >>
> > >> On Tue, Mar 7, 2017 at 1:38 PM, Luciano Resende <luckbr1...@gmail.com
> >
> > >> wrote:
> > >>
> > >> > On Tue, Mar 7, 2017 at 11:59 AM, Arvind Surve
> <ac...@yahoo.com.invalid
> > >
> > >> > wrote:
> > >> >
> > >> > > I will start looking at discussion and drafting a board resolution
> > for
> > >> > > SystemML as a TLP project Arvind Surve | Spark Technology Center
> |
> > >> > > http://www.spark.tc/
> > >> > >
> > >> > >
> > >> > Thank you,
> > >> >
> > >> > We might also need a Maturity Model assessment, any other volunteer
> > that
> > >> > could help with the task?
> > >> >
> > >> > Here is some documentation about MM
> > >> > https://community.apache.org/apache-way/apache-project-matur
> > >> ity-model.htm
> > >> >
> > >> > And here is an example from another podling that is working on
> > >> graduating
> > >> > as well
> > >> > https://cwiki.apache.org/confluence/pages/viewpage.action?
> > >> pageId=68714623
> > >> >
> > >> > --
> > >> > Luciano Resende
> > >> > http://twitter.com/lresende1975
> > >> > http://lresende.blogspot.com/
> > >> >
> > >>
> > >
> > >
> > >
> > > --
> > > Luciano Resende
> > > http://twitter.com/lresende1975
> > > http://lresende.blogspot.com/
> > >
> >
> >
> >
> > --
> > Luciano Resende
> > http://twitter.com/lresende1975
> > http://lresende.blogspot.com/
> >
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Next Steps in the graduation process

[Luciano Resende]

Thanks, fixed.

On Fri, Mar 10, 2017 at 2:29 PM, Arvind Surve <ac...@yahoo.com.invalid>
wrote:

> There is typo in last name of DB, instead of Tsai its listed as Tsa
> -- Arvind Surve | Spark
> Technology Center  | http://www.spark.tc/
>
>   From: Luciano Resende <luckbr1...@gmail.com>
>  To: dev@systemml.incubator.apache.org
>  Sent: Friday, March 10, 2017 2:14 PM
>  Subject: Re: Next Steps in the graduation process
>
> I have updated the community/project portion of the SystemML podling page
>
> http://incubator.apache.org/projects/systemml.html
>
> Please take a look and let me know if I missed anything.
>
>
> On Wed, Mar 8, 2017 at 11:47 AM, Luciano Resende <luckbr1...@gmail.com>
> wrote:
>
> > Great, thank you for the link correction...
> >
> > On Tue, Mar 7, 2017 at 10:48 PM, Matthias Boehm <mboe...@googlemail.com>
> > wrote:
> >
> >> I could help doing this assessment. Btw, here is a working link:
> >> https://community.apache.org/apache-way/apache-project-matur
> >> ity-model.html
> >>
> >> Regards,
> >> Matthias
> >>
> >> On Tue, Mar 7, 2017 at 1:38 PM, Luciano Resende <luckbr1...@gmail.com>
> >> wrote:
> >>
> >> > On Tue, Mar 7, 2017 at 11:59 AM, Arvind Surve <ac...@yahoo.com.invalid
> >
> >> > wrote:
> >> >
> >> > > I will start looking at discussion and drafting a board resolution
> for
> >> > > SystemML as a TLP project Arvind Surve | Spark Technology Center  |
> >> > > http://www.spark.tc/
> >> > >
> >> > >
> >> > Thank you,
> >> >
> >> > We might also need a Maturity Model assessment, any other volunteer
> that
> >> > could help with the task?
> >> >
> >> > Here is some documentation about MM
> >> > https://community.apache.org/apache-way/apache-project-matur
> >> ity-model.htm
> >> >
> >> > And here is an example from another podling that is working on
> >> graduating
> >> > as well
> >> > https://cwiki.apache.org/confluence/pages/viewpage.action?
> >> pageId=68714623
> >> >
> >> > --
> >> > Luciano Resende
> >> > http://twitter.com/lresende1975
> >> > http://lresende.blogspot.com/
> >> >
> >>
> >
> >
> >
> > --
> > Luciano Resende
> > http://twitter.com/lresende1975
> > http://lresende.blogspot.com/
> >
>
>
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>
>
>
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Next Steps in the graduation process

[Luciano Resende]

I have updated the community/project portion of the SystemML podling page

http://incubator.apache.org/projects/systemml.html

Please take a look and let me know if I missed anything.


On Wed, Mar 8, 2017 at 11:47 AM, Luciano Resende <luckbr1...@gmail.com>
wrote:

> Great, thank you for the link correction...
>
> On Tue, Mar 7, 2017 at 10:48 PM, Matthias Boehm <mboe...@googlemail.com>
> wrote:
>
>> I could help doing this assessment. Btw, here is a working link:
>> https://community.apache.org/apache-way/apache-project-matur
>> ity-model.html
>>
>> Regards,
>> Matthias
>>
>> On Tue, Mar 7, 2017 at 1:38 PM, Luciano Resende <luckbr1...@gmail.com>
>> wrote:
>>
>> > On Tue, Mar 7, 2017 at 11:59 AM, Arvind Surve <ac...@yahoo.com.invalid>
>> > wrote:
>> >
>> > > I will start looking at discussion and drafting a board resolution for
>> > > SystemML as a TLP project Arvind Surve | Spark Technology Center  |
>> > > http://www.spark.tc/
>> > >
>> > >
>> > Thank you,
>> >
>> > We might also need a Maturity Model assessment, any other volunteer that
>> > could help with the task?
>> >
>> > Here is some documentation about MM
>> > https://community.apache.org/apache-way/apache-project-matur
>> ity-model.htm
>> >
>> > And here is an example from another podling that is working on
>> graduating
>> > as well
>> > https://cwiki.apache.org/confluence/pages/viewpage.action?
>> pageId=68714623
>> >
>> > --
>> > Luciano Resende
>> > http://twitter.com/lresende1975
>> > http://lresende.blogspot.com/
>> >
>>
>
>
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [DISCUSS] Board resolution for SystemML as a TLP project

[Luciano Resende]

Minor change on first paragraph:



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 declarative, large-scale machine learning.


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

RESOLVED, that the Apache SystemML Project be and hereby is
responsible for the creation and maintenance of software related to
declarative, large-scale machine learning.

RESOLVED, that the office of "Vice President, Apache SystemML" 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
SystemML Project, and to have primary responsibility for management of
the projects within the scope of responsibility of the Apache SystemML
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 SystemML
Project:

* Alexandre V Evfimievski   <ae2...@apache.org>
* Arvind Surve  <ac...@apache.org>
* Berthold Reinwald <reinw...@apache.org>
* DB Tsai   <dbt...@apache.org>
* Deron Eriksson<de...@apache.org>
* Faraz Makari  <fmak...@apache.org>
* Fred Reiss<fre...@apache.org>
* Glenn Weidner <gweid...@apache.org>
* Henry Saputra <hsapu...@apache.org>
* Holden Karau  <hol...@apache.org>
* Joseph Bradley<jkbrad...@apache.org>
* Luciano Resende   <lrese...@apache.org>
* Matthias Boehm<mboe...@apache.org>
* Mike Dusenberry   <dusenberr...@apache.org>
* Niketan Pansare   <niketanpans...@apache.org>
* Patrick Wendell   <pwend...@apache.org>
* Prithviraj Sen<prit...@apache.org>
* Reynold Xin   <r...@apache.org>
* Rich Bowen<rbo...@apache.org>
* Shirish Tatikonda <shiri...@apache.org>
* Xiangrui Meng <m...@apache.org>

NOW, THEREFORE, BE IT FURTHER RESOLVED, that XXX be appointed to the
office of Vice President, Apache SystemML, 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 SystemML 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 SystemML
Project; and be it further

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

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


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Dropping Java 6 and 7 support

[Luciano Resende]

+1

On Mon, Mar 6, 2017 at 10:57 PM, Matthias Boehm <mboe...@googlemail.com>
wrote:

> Hi all,
>
> I'd like to drop the support for Java 6 and 7 in our SystemML 1.0 release.
> Our build still refers to a java compliance level 6, which has not been
> changed for more than 5 years now. Spark >= 1.5 anyway requires Java 7 and
> there has been some discussion on removing Java 7 as well because it
> reached end of life in April 2015. Moving to Java 8 would allow us to
> modernize the code base going forward and the 1.0 release would be the
> perfect time for this change.
>
> Regards,
> Matthias
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Next Steps in the graduation process

[Luciano Resende]

On Tue, Mar 7, 2017 at 11:59 AM, Arvind Surve <ac...@yahoo.com.invalid>
wrote:

> I will start looking at discussion and drafting a board resolution for
> SystemML as a TLP project Arvind Surve | Spark Technology Center  |
> http://www.spark.tc/
>
>
Thank you,

We might also need a Maturity Model assessment, any other volunteer that
could help with the task?

Here is some documentation about MM
https://community.apache.org/apache-way/apache-project-maturity-model.htm

And here is an example from another podling that is working on graduating
as well
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=68714623

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Next Steps in the graduation process

[Luciano Resende]

I am going to start a formal community vote for graduation, and in
parallel, update our project incubator page.

Could someone please help with the discussion and drafting a board
resolution for SystemML as a TLP project (see details below)

http://incubator.apache.org/guides/graduation.html#tlp-resolution


We will also need to identify a project chair (see responsibilities below)

https://www.apache.org/dev/pmc.html#chair

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Release cadence

[Luciano Resende]

 dev@systemml.incubator.apache.org
> > >  Sent: Saturday, January 7, 2017 1:35 AM
> > >  Subject: Re: Release cadence
> > >
> > > I think that a 2 month cycle would be a good compromise for major/minor
> > > releases. Fixpack release could be at a 1 month cycle.
> > >
> > >
> > > Regards,
> > > Berthold Reinwald
> > > IBM Almaden Research Center
> > > office: (408) 927 2208; T/L: 457 2208
> > > e-mail: reinw...@us.ibm.com
> > >
> > >
> > >
> > > From:  Deron Eriksson <deroneriks...@gmail.com>
> > > To:dev@systemml.incubator.apache.org
> > > Date:  01/05/2017 02:14 PM
> > > Subject:Re: Release cadence
> > >
> > >
> > >
> > > +1 for trying out a 1 month release cycle.
> > >
> > > However, I highly agree with Matthias that there is a lot of overhead
> > with
> > > releases, so it would be good if we can work to streamline/automate the
> > > process as much as possible. Also, it would be good to distribute the
> > > tasks
> > > around as much as possible. This can result in cross-training and help
> > > avoid overburdening the same contributors each month.
> > >
> > > If the overhead slows us down too much, then we can go to a slower
> > release
> > > cycle.
> > >
> > > Deron
> > >
> > >
> > >
> > >
> > > On Thu, Jan 5, 2017 at 1:50 PM, <dusenberr...@gmail.com> wrote:
> > >
> > > > +1 for adopting a 1 month release cycle.
> > > >
> > > > --
> > > >
> > > > Mike Dusenberry
> > > > GitHub: github.com/dusenberrymw
> > > > LinkedIn: linkedin.com/in/mikedusenberry
> > > >
> > > > Sent from my iPhone.
> > > >
> > > >
> > > > > On Jan 5, 2017, at 1:35 PM, Luciano Resende <luckbr1...@gmail.com>
> > > > wrote:
> > > > >
> > > > > On Thu, Jan 5, 2017 at 6:05 AM, Matthias Boehm
> > > <mboe...@googlemail.com>
> > > > > wrote:
> > > > >
> > > > >> In general, I like the idea of aiming for consistent release
> cycles.
> > > > >> However, every month is just too much, at least for me. There is a
> > > > >> considerable overhead associated with each release for end-to-end
> > > > >> performance tests, tests on different environments, code freeze
> for
> > > new
> > > > >> features, etc. Hence, a too short release cycle would not be
> "agile"
> > > but
> > > > >> would actually slow us down. From my perspective, a realistic
> > release
> > > > >> cadence would be 2-3 months, maybe a bit more for major releases.
> > > > >>
> > > > >>
> > > > > 2-3 months of release cadence for an open source is probably a long
> > > > > stretch, particular for a project that does not have very large set
> > of
> > > > 3rd
> > > > > party dependencies.
> > > > >
> > > > > As for some of the overhead issues you mentioned, they are probably
> > > easy
> > > > to
> > > > > workaround:
> > > > >
> > > > > - code-freeze timeframe can be resolved with branches
> > > > > - end-to-end performance regressions can be avoided by better code
> > > > review,
> > > > > and if you were willing to go with 2-3 months without performing
> > these
> > > > > tests, we could perform them only for major releases, and
> proactively
> > > > > quickly build a minor release with the patch when a user report any
> > > > > performance regression.
> > > > >
> > > > >
> > > > > Anyway, I would really like to see SystemML more agile with regards
> > to
> > > > its
> > > > > release process because, as I mentioned before, the release early,
> > > > release
> > > > > often mantra is good to increase community interest, generate more
> > > > traffic
> > > > > to the list as developers discuss the roadmap and release blockers,
> > > and
> > > > > also enable users to provide feedback sooner on the areas we are
> > > > developing.
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Luciano Resende
> > > > > http://twitter.com/lresende1975
> > > > > http://lresende.blogspot.com/
> > > >
> > >
> > >
> > >
> > > --
> > > Deron Eriksson
> > > Spark Technology Center
> > > http://www.spark.tc/
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
>
>
>
> --
> Deron Eriksson
> Spark Technology Center
> http://www.spark.tc/
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

[DISCUSS] SystemML Graduation

[Luciano Resende]

It has been an exciting 16 months so far, and the project has accomplished
4 official Apache Releases and is currently requesting the IPMC to approve
the 5th release. We have voted 3 new committers and PPMC members and
welcomed a new Mentor. The community continues to evangelize the project at
universities, blog posts, public webcasts, and in multiple conferences
which culminate in the project being awarded 'Best Paper' at VLDB 2016. And
last, but not least, the Incubator has asked us to evaluate and possibly
start the graduation process [1].

For now, I would like to get the community to take a quick look at the
'Graduation Guide' [2] and use this thread to discuss your opinion about
SystemML graduation.

In parallel, I will start working on updating the project page [3] with
milestones, and other details.

[1] http://www.mail-archive.com/general@incubator.apache.org/msg58614.html
[2] http://incubator.apache.org/guides/graduation.html
[3] http://incubator.apache.org/projects/systemml.html

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: SystemML 0.13 Release plan

[Luciano Resende]

What do you mean by frozen ? A branch will be created from the 0.13 rc tag
if needed ? or master will be frozen?

On Thu, Feb 16, 2017 at 8:29 AM, Arvind Surve <ac...@yahoo.com.invalid>
wrote:

> Hi,
> We are planning to get SystemML 0.13 release out. One of the major purpose
> of this release is to provide supporting SystemML on Spark 2.1.0.We will
> plan to do Release Candidate (RC) build by end of this week. After RC
> build, verification will be done to get code ready for publish.
> Once RC build gets started code for SystemML 0.13 will be frozen other
> than any stop shipment issues.If you are working on any critical issue/s,
> please try to get in change/s by EOD Friday (2/17/2017) PST.
>
> ThanksArvind
>  -- Arvind Surve Spark Technology Center
> http://www.spark.tc/




-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Corrupt SystemML 0.12 release download

[Luciano Resende]

Note that we Must not just update the artifact, as whatever we publish
should be voted.

I would suggest just doing a 0.12.1 release

On Wed, Feb 15, 2017 at 10:14 PM Berthold Reinwald 
wrote:

> yes, that is the current consensus. It is probably a bug in the release
> scripts.
>
> Regards,
> Berthold Reinwald
> IBM Almaden Research Center
> office: (408) 927 2208; T/L: 457 2208
> e-mail: reinw...@us.ibm.com
>
>
>
> From:   Matthias Boehm 
> To: dev@systemml.incubator.apache.org
> Date:   02/15/2017 09:25 PM
> Subject:Corrupt SystemML 0.12 release download
>
>
>
> Just in case you have not seen the issue described in [1], the download of
> our 0.12 release is currently corrupted as the included SystemML.jar does
> not contain the antlr-runtime and wink-json libraries. Hence, without
> modifying the jar, SystemML fails with ClassNotFoundExceptions.
>
> I agree with Felix that we should fix this ASAP, potentially just fixing
> the links. Furthermore, I'd like to understand why there is a difference
> between the artifacts in the maven repository (which contain these
> libraries) and our download page. Could anyone clarify this discrepancy,
> please?
>
> Regards,
> Matthias
>
> [1] https://issues.apache.org/jira/browse/SYSTEMML-1250
>
>
>
>
> --
Sent from my Mobile device

Re: Pull Request Reviews

[Luciano Resende]

Apache usually have two ways for revieweing: REview then commit, Commit
then review.

If review is becoming a bottleneck, just use CTR,  maybe waiting for a PR
build to be green.


On Mon, Feb 13, 2017 at 10:03 AM  wrote:

> Thanks, Deron, for bringing up this topic!  PRs, and the associated
> discussions, are a critical part of any modern, successful open source
> project.  As Deron stated, anyone in the community should feel free to
> review PRs -- we want your thoughts and opinions and greatly appreciate
> your help!
>
> - Mike
>
> --
>
> Mike Dusenberry
> GitHub: github.com/dusenberrymw
> LinkedIn: linkedin.com/in/mikedusenberry
>
> Sent from my iPhone.
>
>
> > On Feb 3, 2017, at 6:55 PM, Deron Eriksson 
> wrote:
> >
> > Hi,
> >
> > Reviewing pull requests is a great way to contribute to the success of
> > SystemML. If you are involved in any way with SystemML, please consider
> > reviewing pull requests. Everyone can review pull requests, and it is a
> > great way to gain experience with the project.
> >
> > Thanks!
> > Deron
> >
> >
> > Username PRs Reviewed
> > mboehm7 134
> > dusenberrymw 112
> > deroneriksson 110
> > niketanpansare 40
> > gweidner 31
> > shirisht 26
> > akchinSTC 25
> > nakul02 23
> > bertholdreinwald 15
> > lresende 12
> > frreiss 12
> > fschueler 9
> > Wenpei 7
> > asurve 5
> > iyounus 4
> > MechCoder 3
> > MadisonJMyers 3
> > oza 2
> > fmakari 2
> > rightwaitforyou 2
> > ethanyxu 1
> > ckadner 1
> > petro-rudenko 1
> > hsaputra 1
> > FelixNeutatz 1
> > nishi-t 0
> > sandeep-n 0
> > romeokienzler 0
> > tgamal 0
> > taasawat 0
> > sourav-mazumder 0
> > kevin-bates 0
> > kakal 0
> > GrapeBaBa 0
> > objectadjective 0
> > nmanchev 0
> > jodersky 0
> > jdyer1 0
> > gmlewis 0
> > aloknsingh 0
> > akunft 0
> > ahmaurya 0
> >
> >
> > --
> > Deron Eriksson
> > Spark Technology Center
> > http://www.spark.tc/
>
-- 
Sent from my Mobile device

Re: 0.12.0 Votes

[Luciano Resende]

Done.

On Mon, Feb 6, 2017 at 4:50 PM, Deron Eriksson <deroneriks...@gmail.com>
wrote:

> Hi,
>
> I see we are up to two +1 votes (Justin and Sergio) already on the general
> incubator list! I've updates our NOTICE files on master to reflect the
> non-blocking 2017 updates mentioned by Justin and Sergio.
>
> Would any of our active mentors (Luciano, Henry, Reynold) be available to
> review the 0.12.0 release?
>
> Thanks!
> Deron
>
> --
> Deron Eriksson
> Spark Technology Center
> http://www.spark.tc/
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: February Podling Report

[Luciano Resende]

On Tue, Jan 31, 2017 at 10:30 PM, Deron Eriksson <deroneriks...@gmail.com>
wrote:

> Hi,
>
> I posted our SystemML podling report for February to:
> https://wiki.apache.org/incubator/February2017
>
>
>
It looks ok to me, but in the issues to address before graduation, I would
have reduced to only the last one.

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Building releases now that we have branches

[Luciano Resende]

On Fri, Jan 20, 2017 at 4:51 PM, <fschue...@posteo.de> wrote:

> Yes, this commit probably shouldn't have gone to master...
> Can one of the commiters revert it?
>
>
I would leave for the Release manager to revert it


> Now, for the RC2, we will probably need to make the RC based on the commit
>> hash from the top of the 0.12 branch and do a little
>> investigation/research
>> if there is any other changes to make the release prepare to modify the
>> pom
>> from the branch and google is probably your friend here.
>>
>
> Not sure what you mean here - can't we tag a new release candidate on the
> branch-0.12? What (except for the tag) would have to change in the pom?
>
> -Felix
>
>
We currently use a script to create the release, and it will call maven
release:prepare which change the pom version to release version, and them
modify to the new development version. I just want to make sure it will
make these changes on the branch and not on master. Not sure if maven needs
any additional magic for that, it will be our first time running the script
on a branch.

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Building releases now that we have branches

[Luciano Resende]

I just saw a commit into master :
[maven-release-plugin] prepare release v0.12.0-incubating-rc2” --tag

Please be very careful with what we are trying to do. After 0.12 RC, we
have moved the development of 0.12 wich is based on Spark 1.6.x to a 0.12
branch, but the commit info above makes me think that we are trying to cut
a 0.12 RC2 from master which then will bring the Spark 2.0 support which is
not desirable and is scheduled for 0.12.

Also note that master is now in a corrupted state, where the pom is
corrupted (particularly the scmelement)

 scm:git:g...@github.com:apache/incubator-systemml scm:git:
https://git-wip-us.apache.org/repos/asf/incubator-systemml 
https://git-wip-us.apache.org/repos/asf?p=incubator-systemml.git
v0.12.0-incubating-rc2”
--tag 

Please revert the  commit in master
(083c9c4ca0bc3deeb04f2552470a9e187b80bcf4)


Now, for the RC2, we will probably need to make the RC based on the commit
hash from the top of the 0.12 branch and do a little investigation/research
if there is any other changes to make the release prepare to modify the pom
from the branch and google is probably your friend here.

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: SystemML Branch for any fixes related to Spark 1.6x

[Luciano Resende]

The changes here are related to 1.x spark releases, right? So the idea here
is that this becomes a dev stream for Spark 1.6 support and you guys can
have 0.13, 0.14, 0.15, as required from this branch.

If you guys want to change, I don't have any objections, please go ahead
and change.

On Fri, Jan 13, 2017 at 1:55 PM, <dusenberr...@gmail.com> wrote:

> Thanks, Luciano for creating the branch. Could we rename it to
> "branch-0.12" to better reflect that any changes that are added would only
> apply to future bug fix releases on the 0.12.x line?  This would be more in
> line with the naming scheme that Spark uses for its branches, and should
> cause less confusion.
>
> --
>
> Mike Dusenberry
> GitHub: github.com/dusenberrymw
> LinkedIn: linkedin.com/in/mikedusenberry
>
> Sent from my iPhone.
>
>
> > On Jan 13, 2017, at 1:50 PM, Luciano Resende <luckbr1...@gmail.com>
> wrote:
> >
> > We have created the following branch to track Spark 1.6 fixes :
> > origin/branch-systemml-spark-1.6
> >
> > Note that, fixes that go into master, and are also affecting 1.6, they
> > should be cherry-picked to the 1.6 branch as well.
> >
> > As for checking out, you will need to do something like the steps below
> > (your preference might change some steps)
> >
> > git checkout -b branch-systemml-spark-1.6 origin/branch-systemml-spark-
> 1.6
> > git branch --set-upstream-to origin/branch-systemml-spark-1.6
> > branch-systemml-spark-1.6
> >
> > this last one is like:
> >
> > git branch --set-upstream-to origin/my_remote_branch my_local_branch
> >
> > For creating dev branches for 1.6, first go to you local 1.6 branch and
> > continue with your regular steps such as git branch -b JIRA-222
> >
> > And good luck !!!
> >
> > --
> > Luciano Resende
> > http://twitter.com/lresende1975
> > http://lresende.blogspot.com/
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

SystemML Branch for any fixes related to Spark 1.6x

[Luciano Resende]

We have created the following branch to track Spark 1.6 fixes :
origin/branch-systemml-spark-1.6

Note that, fixes that go into master, and are also affecting 1.6, they
should be cherry-picked to the 1.6 branch as well.

As for checking out, you will need to do something like the steps below
(your preference might change some steps)

git checkout -b branch-systemml-spark-1.6 origin/branch-systemml-spark-1.6
git branch --set-upstream-to origin/branch-systemml-spark-1.6
branch-systemml-spark-1.6

this last one is like:

git branch --set-upstream-to origin/my_remote_branch my_local_branch

For creating dev branches for 1.6, first go to you local 1.6 branch and
continue with your regular steps such as git branch -b JIRA-222

And good luck !!!

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Release cadence

[Luciano Resende]

On Thu, Jan 5, 2017 at 6:05 AM, Matthias Boehm <mboe...@googlemail.com>
wrote:

> In general, I like the idea of aiming for consistent release cycles.
> However, every month is just too much, at least for me. There is a
> considerable overhead associated with each release for end-to-end
> performance tests, tests on different environments, code freeze for new
> features, etc. Hence, a too short release cycle would not be "agile" but
> would actually slow us down. From my perspective, a realistic release
> cadence would be 2-3 months, maybe a bit more for major releases.
>
>
2-3 months of release cadence for an open source is probably a long
stretch, particular for a project that does not have very large set of 3rd
party dependencies.

As for some of the overhead issues you mentioned, they are probably easy to
workaround:

- code-freeze timeframe can be resolved with branches
- end-to-end performance regressions can be avoided by better code review,
and if you were willing to go with 2-3 months without performing these
tests, we could perform them only for major releases, and proactively
quickly build a minor release with the patch when a user report any
performance regression.


Anyway, I would really like to see SystemML more agile with regards to its
release process because, as I mentioned before, the release early, release
often mantra is good to increase community interest, generate more traffic
to the list as developers discuss the roadmap and release blockers, and
also enable users to provide feedback sooner on the areas we are developing.



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [DISCUSS] Roadmap SystemML 1.0

[Luciano Resende]

On Tue, Jan 3, 2017 at 11:50 AM, Matthias Boehm <mboe...@googlemail.com>
wrote:

> I'd like to initiate the discussion of a concrete roadmap for our next
> release. According, to previous discussions, I'd think it's fair to say
> that we agree on calling it SystemML 1.0. We should carefully plan this
> release as it's an opportunity to change APIs and remove some older
> deprecated features. I'd like to encourage not just developers but also the
> broader community to participate in this discussion.
>
> Personally, I think a target date of Q2/2017 is realistic. Let's start
> with collecting the major features and changes that potentially affect
> users. Here is an initial list, but please feel free to add and up- or
> down-vote the individual items.
>
> 1) APIs and Language:
> * Cleanup new MLContext (matrix/frame data types, move tests, etc)
> * Remove old MLContext
> * Consolidate MLContext and JMLC
> * Full support for Scala/Python DSLs
> * Remove old file-based transform
> * Scala/Python wrappers for all existing algorithms
> * Data converters (additional formats: e.g., libsvm; performance)
>
> 2) Updated Dependencies:
> * Spark 2.0 support
> * Matrix block library (isolated jar)
>
> 3) Compiler/Runtime Features:
> * GPU support (full compiler and runtime support)
> * Compressed linear algebra v2
> * Code generation (automatic operator fusion)
> * Extended parfor (full spark exploitation, micro-batch support)
> * Scale-up architecture (large dense blocks, numa)?
>
> 4) Tools
> * Extended stats (task locality, shuffle, etc)
> * Cloud resource advisor (extended resource optimizer)?
>
> 5) Algorithms
> * Graduate "staging" algorithms (robustness/performance)
> * Perftest: include all algorithms into automated performance tests
> * Simplify usage decision trees, random forest, mlogreg, msvm
> (preprocessing, label representation, etc)
>
> Items marked with a ? can potentially be moved out to subsequent releases.
>
>
> Regards,
> Matthias
>

My understanding is that most of the items in 1 and 2 are going to break
backward compatibility, while the others can be done incrementally. Is this
assumption correct? If so, can we finish 1 and 2 and do a 1.0 release. and
them, continue with 3, 4, 5, etc ? as I don't think we should wait for
2017/Q2 to do a 1.0 release. I believe in release early, release often,
particularly to attract new users, that can help verifying and contributing
to specific releases.

Thoughts ?

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

[RESULT][VOTE] Apache SystemML 0.11.0-incubating (RC5)

[Luciano Resende]

I should have changed the subject to [RESULT]

On Fri, Nov 4, 2016 at 7:34 AM, Luciano Resende <luckbr1...@gmail.com>
wrote:

>
>
> On Tue, Nov 1, 2016 at 5:08 PM, Luciano Resende <luckbr1...@gmail.com>
> wrote:
>
>>
>> Please vote on releasing the following candidate as Apache SystemML
>> version 0.11.0-incubating !
>>
>> The vote is open for at least 72 hours and passes if a majority of at
>> least 3 +1 PMC votes are cast.
>>
>> [ ] +1 Release this package as Apache SystemML 0.11.0-incubating
>> [ ] -1 Do not release this package because ...
>>
>> To learn more about Apache SystemML, please see
>> http://systemml.apache.org/
>>
>> The tag to be voted on is v0.11.0-incubating-rc4
>> (c2e1670c2745863195d4789f1f77ed01ec11af5e)
>>
>> https://github.com/apache/incubator-systemml/tree/c2e1670c27
>> 45863195d4789f1f77ed01ec11af5e
>>
>> The release artifacts can be found at :
>>
>> https://dist.apache.org/repos/dist/dev/incubator/systemml/0.
>> 11.0-incubating-rc5/
>>
>> The maven release artifacts, including signatures, digests, etc. can be
>> found at:
>>
>> https://repository.apache.org/content/repositories/orgapache
>> systemml-1011/
>>
>>
>> =
>> == Apache Incubator release policy ==
>> =
>> Please find below the guide to release management during incubation:
>> http://incubator.apache.org/guides/releasemanagement.html
>>
>> ===
>> == How can I help test this release? ==
>> ===
>> If you are a SystemML user, you can help us test this release by taking
>> an existing Algorithm or workload and running on this release candidate,
>> then reporting any regressions.
>>
>> 
>> == What justifies a -1 vote for this release? ==
>> 
>> -1 votes should only occur for significant stop-ship bugs or legal
>> related issues (e.g. wrong license, missing header files, etc). Minor bugs
>> or regressions should not block this release.
>>
>
>
> Vote has passed with 6 (binding) +1 from
> Glenn Weidner
> Niketan Pansare
> Arvind Surve
> Deron Eriksson
> Mike Dusenbery
> Luciano Resende
>
> And 2 (non-binding) +1 from
> Nakul Jindal
> Sourav Mazunder
>
> I will start the IPMC vote shortly.
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [DRAFT] November monthly report

[Luciano Resende]

+1, Reviewed on the wiki as a mentor

On Wed, Nov 2, 2016 at 8:45 AM, Deron Eriksson <deroneriks...@gmail.com>
wrote:

> Thank you for the feedback Mike. I added the VLDB paper award.
>
> I added the monthly report to the Apache incubator wiki at
> https://wiki.apache.org/incubator/November2016.
>
> Deron
>
>
> On Tue, Nov 1, 2016 at 5:07 PM, <dusenberr...@gmail.com> wrote:
>
> > Looks good. We should also include the VLDB paper award.
> >
> > --
> >
> > Mike Dusenberry
> > GitHub: github.com/dusenberrymw
> > LinkedIn: linkedin.com/in/mikedusenberry
> >
> > Sent from my iPhone.
> >
> >
> > > On Nov 1, 2016, at 4:43 PM, Deron Eriksson <deroneriks...@gmail.com>
> > wrote:
> > >
> > > Hello,
> > >
> > > Here is a draft of the November monthly report due tomorrow that Felix
> > and
> > > I put together. Feedback is welcome.
> > >
> > > Deron
> > >
> > > 
> > >
> > > SystemML
> > >
> > > SystemML provides declarative large-scale machine learning (ML) that
> > aims at
> > > flexible specification of ML algorithms and automatic generation of
> > hybrid
> > > runtime plans ranging from single node, in-memory computations, to
> > > distributed
> > > computations running on Apache Hadoop MapReduce and Apache Spark.
> > >
> > > SystemML has been incubating since 2015-11-02.
> > >
> > > Three most important issues to address in the move towards graduation:
> > >
> > > - Grow SystemML community: increase mailing list activity,
> > >   increase adoption of SystemML for scalable machine learning,
> encourage
> > >   data scientists to adopt DML and PyDML algorithm scripts, respond to
> > >   user feedback to ensure SystemML meets the requirements of real-world
> > >   situations, write papers, and present talks about SystemML.
> > > - Continue to produce releases.
> > > - Increase the diversity of our project's contributors and committers.
> > >
> > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware
> > > of?
> > >
> > > NONE.
> > >
> > > How has the community developed since the last report?
> > > Our mailing list from August through October had 375 messages on a wide
> > > range
> > > of topics. We have gained 4 new contributors to the main project since
> > > August
> > > 1st. Our website has been redesigned with the help of several design
> > > engineers
> > > and we have commits from 3 new contributors to the website project. On
> > > GitHub,
> > > the project has been starred 417 times and forked 156 times.
> > >
> > > Niketan Pansare gave a talk with the title "Apache SystemML -
> Declarative
> > > Machine Learning at Scale" on October 7th in the CS graduate seminar at
> > UC
> > > Merced. Matthias Boehm gave a talk on "Compressed Linear Algebra for
> > Large-
> > > Scale Machine Learning" at TU Dresden on August 30th. We presented the
> > > papers
> > > "Compressed Linear Algebra for Large-Scale Machine Learning" (research
> > > paper +
> > > poster) and "SystemML: Declarative Machine Learning on Spark" (industry
> > > paper)
> > > at VLDB'16, gave two 90 minute tutorials at the BOSS'16 workshop,
> > > co-located
> > > with VLDB'16, and our paper "SPOOF: Sum-Product Optimization and
> Operator
> > > Fusion for Large- Scale Machine Learning" has been accepted at CIDR'17.
> > >
> > > How has the project developed since the last report?
> > > The main project has had 213 commits since August 1. The website
> project
> > > has
> > > had 51 commits since August 1. Since August 1, 241 issues have been
> > > reported
> > > on our JIRA site and 137 issues have been resolved or closed. 79 pull
> > > requests
> > > have been created since August 1, and 72 pull requests have been
> closed.
> > >
> > > Date of last release:
> > >
> > > 2016-06-15 (version 0.10.0-incubating)
> > >
> > > When were the last committers or PMC members elected?
> > >
> > > 2016-05-07 Glenn Weidner
> > > 2016-05-07 Faraz Makari Manshadi
> > >
> > > 
> >
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

[VOTE] Apache SystemML 0.11.0-incubating (RC5)

[Luciano Resende]

Please vote on releasing the following candidate as Apache SystemML version
0.11.0-incubating !

The vote is open for at least 72 hours and passes if a majority of at least
3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache SystemML 0.11.0-incubating
[ ] -1 Do not release this package because ...

To learn more about Apache SystemML, please see http://systemml.apache.org/

The tag to be voted on is v0.11.0-incubating-rc4 (
c2e1670c2745863195d4789f1f77ed01ec11af5e)

https://github.com/apache/incubator-systemml/tree/
c2e1670c2745863195d4789f1f77ed01ec11af5e

The release artifacts can be found at :

https://dist.apache.org/repos/dist/dev/incubator/systemml/0.
11.0-incubating-rc5/

The maven release artifacts, including signatures, digests, etc. can be
found at:

https://repository.apache.org/content/repositories/orgapachesystemml-1011/


=
== Apache Incubator release policy ==
=
Please find below the guide to release management during incubation:
http://incubator.apache.org/guides/releasemanagement.html

===
== How can I help test this release? ==
===
If you are a SystemML user, you can help us test this release by taking an
existing Algorithm or workload and running on this release candidate, then
reporting any regressions.


== What justifies a -1 vote for this release? ==

-1 votes should only occur for significant stop-ship bugs or legal related
issues (e.g. wrong license, missing header files, etc). Minor bugs or
regressions should not block this release.


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

SystemML 0.11.0-incubating RC4 feedback

[Luciano Resende]

Please see IPMC feedback on our RC4:
https://www.mail-archive.com/general@incubator.apache.org/msg56892.html

Please help address these issues, as we are going to have to start a new RC
vote asap.

Also, I am pretty sure some of these issues have been addressed in the
past, so we need to figure out what is causing some of these regressions.

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [VOTE] Apache SystemML 0.11.0-incubating (RC4)

[Luciano Resende]

Off course, my +1.

On Mon, Oct 24, 2016 at 4:11 PM, Luciano Resende <luckbr1...@gmail.com>
wrote:

> Please vote on releasing the following candidate as Apache SystemML
> version 0.11.0-incubating !
>
> The vote is open for at least 72 hours and passes if a majority of at
> least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache SystemML 0.11.0-incubating
> [ ] -1 Do not release this package because ...
>
> To learn more about Apache SystemML, please see
> http://systemml.apache.org/
>
> The tag to be voted on is v0.11.0-incubating-rc4 (
> 6937683b01a13458990e698b0cf04f4f6ccecde3)
>
> https://github.com/apache/incubator-systemml/tree/
> 6937683b01a13458990e698b0cf04f4f6ccecde3
>
> The release artifacts can be found at :
>
> https://dist.apache.org/repos/dist/dev/incubator/systemml/0.
> 11.0-incubating-rc4/
>
> The maven release artifacts, including signatures, digests, etc. can be
> found at:
>
> https://repository.apache.org/content/repositories/orgapachesystemml-1010/
>
>
> =
> == Apache Incubator release policy ==
> =
> Please find below the guide to release management during incubation:
> http://incubator.apache.org/guides/releasemanagement.html
>
> ===
> == How can I help test this release? ==
> ===
> If you are a SystemML user, you can help us test this release by taking an
> existing Algorithm or workload and running on this release candidate, then
> reporting any regressions.
>
> 
> == What justifies a -1 vote for this release? ==
> 
> -1 votes should only occur for significant stop-ship bugs or legal
> related issues (e.g. wrong license, missing header files, etc). Minor bugs
> or regressions should not block this release.
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Couple of questions on website contents

[Luciano Resende]

I made that change, as I think we need to ve able to list all available
mailing lists, but I didn't want to use the obsolete docs page.

Thinking more about this, maybe a meet in the middle approach is to use the
full details on the community page, and revert the front page to focus on
the dev list ?

Tgoughts ?

On Wednesday, October 26, 2016, Jason Azares <jason.aza...@gmail.com> wrote:

> Hi Deron,
>
> Thanks for publishing the updates, and the site looks great! One thing I
> noticed is that the "Subscribe to Our Mailing Lists" section does not
> reflect what the design team originally had. I'm not sure if you were aware
> of this discrepancy.
>
> [image: Inline image 1]
>
> On Tue, Oct 25, 2016 at 9:53 PM, Deron Eriksson <deroneriks...@gmail.com
> <javascript:_e(%7B%7D,'cvml','deroneriks...@gmail.com');>> wrote:
>
>> Hi Luciano,
>>
>> Since the current website updates are major improvements, I have gone
>> ahead
>> and published the new updates. I think we can now start publishing more
>> frequently since important parts of the codebase have stabilized.
>>
>> Deron
>>
>>
>> On Tue, Oct 25, 2016 at 5:40 PM, Deron Eriksson <deroneriks...@gmail.com
>> <javascript:_e(%7B%7D,'cvml','deroneriks...@gmail.com');>>
>> wrote:
>>
>> > Hi Luciano,
>> >
>> > Several updates to the website were merged today. I think we're at the
>> > point where we can publish the new website updates. Do you agree?
>> >
>> > Deron
>> >
>> >
>> > On Tue, Oct 25, 2016 at 11:02 AM, Jason Azares <jason.aza...@gmail.com
>> <javascript:_e(%7B%7D,'cvml','jason.aza...@gmail.com');>>
>> > wrote:
>> >
>> >> Hi Luciano,
>> >>
>> >> Initial page:
>> >> >  - What's the intention of the section just above the social banner
>> ? I
>> >> > noticed it was actually a copy of a section from the community page,
>> >> but it
>> >> > looks like the content was duplicated and not extracted to a banner,
>> >> and I
>> >> > have changed the one in community to what I think it better clarifies
>> >> the
>> >> > mailing list, but I am not sure if that's the same intent of the
>> banner
>> >> on
>> >> > the initial page.
>> >>
>> >>
>> >> Thanks for bringing this point to our attention. The content on the
>> >> initial
>> >> page is different from the community page. We wanted to have a call to
>> >> action to get users to subscribe to the mailing list. We are currently
>> >> designing this section and will send a pull request once completed.
>> >>
>> >> Navigation Menu:
>> >> > - The community navigation seems to have gone wild with a few
>> >> duplications.
>> >> > We have source code and github links, which are both the same. We
>> also
>> >> have
>> >> > the community get involved link that includes a list of committers
>> using
>> >> > the new design format, but there is also a link to project committers
>> >> that
>> >> > include the old page listing all committers.
>> >>
>> >>
>> >> Dexter is currently working to resolve this issue. He will send his
>> >> updates
>> >> once they are finished.
>> >>
>> >> Hope this clears things up!
>> >>
>> >> Best,
>> >> Jason
>> >>
>> >> On Mon, Oct 24, 2016 at 7:09 PM, Luciano Resende <luckbr1...@gmail.com
>> <javascript:_e(%7B%7D,'cvml','luckbr1...@gmail.com');>>
>> >> wrote:
>> >>
>> >> > I have a few questions on the contents of the website in the master
>> >> branch
>> >> > :
>> >> >
>> >> > Initial page:
>> >> >
>> >> >  - What's the intention of the section just above the social banner
>> ? I
>> >> > noticed it was actually a copy of a section from the community page,
>> >> but it
>> >> > looks like the content was duplicated and not extracted to a banner,
>> >> and I
>> >> > have changed the one in community to what I think it better clarifies
>> >> the
>> >> > mailing list, but I am not sure if that's the same intent of the
>> banner
>> >> on
>> >> > the initial page.
>> >> >
>> >> > Navigation Menu:
>> >> > - The community navigation seems to have gone wild with a few
>> >> duplications.
>> >> > We have source code and github links, which are both the same. We
>> also
>> >> have
>> >> > the community get involved link that includes a list of committers
>> using
>> >> > the new design format, but there is also a link to project committers
>> >> that
>> >> > include the old page listing all committers.
>> >> >
>> >> >
>> >> > Once we resolve the items above (which are more like cleanups), I
>> think
>> >> we
>> >> > might be at a point where we could publish these latest updates to
>> the
>> >> live
>> >> > website.
>> >> >
>> >> > Thoughts ?
>> >> >
>> >> > --
>> >> > Luciano Resende
>> >> > http://twitter.com/lresende1975
>> >> > http://lresende.blogspot.com/
>> >> >
>> >>
>> >
>> >
>>
>
>

-- 
Sent from my Mobile device

Re: SystemML Medium Blog

[Luciano Resende]

On Tue, Oct 25, 2016 at 7:32 PM, Madison Myers <madisonjmy...@gmail.com>
wrote:

> Hey everyone,
>
> Just a thought on expanding visibility of SystemML: I know lots of us have
> written some blogs and articles on SystemML and I think it would be great
> to get these all in the same spot (and also write more)! I've started a
> SystemML Medium blog for this and would love to:
>
> 1. republish existing blogs on Medium
> 2. have volunteers write new blogs
>
> The idea would be to have these be linked directly from the website. If you
> wouldn't mind, I'd love your feedback! If you're up for me republishing
> articles that you've already written on the SystemML medium account (the
> author's name will still be yours), please let me know! Also, if you have
> ideas on topics that the SystemML community should be writing on and/or are
> up for writing an article or two, let me know as well!
>
> Luciano, do you see any issues from an Apache standpoint?
>
> Thanks!
> Madison


+1, just make sure "republish" are done by the blog authors or with their
explicit permission archived on this mailing list.

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Couple of questions on website contents

[Luciano Resende]

I have a few questions on the contents of the website in the master branch :

Initial page:

 - What's the intention of the section just above the social banner ? I
noticed it was actually a copy of a section from the community page, but it
looks like the content was duplicated and not extracted to a banner, and I
have changed the one in community to what I think it better clarifies the
mailing list, but I am not sure if that's the same intent of the banner on
the initial page.

Navigation Menu:
- The community navigation seems to have gone wild with a few duplications.
We have source code and github links, which are both the same. We also have
the community get involved link that includes a list of committers using
the new design format, but there is also a link to project committers that
include the old page listing all committers.


Once we resolve the items above (which are more like cleanups), I think we
might be at a point where we could publish these latest updates to the live
website.

Thoughts ?

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

[VOTE] Apache SystemML 0.11.0-incubating (RC4)

[Luciano Resende]

Please vote on releasing the following candidate as Apache SystemML version
0.11.0-incubating !

The vote is open for at least 72 hours and passes if a majority of at least
3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache SystemML 0.11.0-incubating
[ ] -1 Do not release this package because ...

To learn more about Apache SystemML, please see http://systemml.apache.org/

The tag to be voted on is v0.11.0-incubating-rc4
(6937683b01a13458990e698b0cf04f4f6ccecde3)

https://github.com/apache/incu
bator-systemml/tree/6937683b01a13458990e698b0cf04f4f6ccecde3

The release artifacts can be found at :

https://dist.apache.org/repos/dist/dev/incubator/systemml/0.
11.0-incubating-rc4/

The maven release artifacts, including signatures, digests, etc. can be
found at:

https://repository.apache.org/content/repositories/orgapachesystemml-1010/


=
== Apache Incubator release policy ==
=
Please find below the guide to release management during incubation:
http://incubator.apache.org/guides/releasemanagement.html

===
== How can I help test this release? ==
===
If you are a SystemML user, you can help us test this release by taking an
existing Algorithm or workload and running on this release candidate, then
reporting any regressions.


== What justifies a -1 vote for this release? ==

-1 votes should only occur for significant stop-ship bugs or legal related
issues (e.g. wrong license, missing header files, etc). Minor bugs or
regressions should not block this release.

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [VOTE] SystemML New Logo Ideas

[Luciano Resende]

On Fri, Oct 21, 2016 at 11:27 AM, Frederick R Reiss <frre...@us.ibm.com>
wrote:

> These are awesome! I'm more a fan of option #4 myself.
>
>
I like option $4 myself as well.


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [VOTE] Apache SystemML 0.11.0-incubating (RC3)

[Luciano Resende]

if tests are consistently failing, then we should cancel the RC and either
fix the test or mark it as @ignored.

Intermittent fails might be ok, but it's a community decision.

On Wed, Oct 19, 2016 at 10:50 AM, Deron Eriksson <deroneriks...@gmail.com>
wrote:

> I believe that for an Apache release, our test suite is supposed to pass
> (although I'm pretty sure random test fails can be ignored).
>
> See 2.1 of Release Check List here:
> http://incubator.apache.org/guides/releasemanagement.html#check-list
>
> "2.1 Build is successful including automated tests.
> The expanded source archive is expected to build and pass tests."
>
> Luciano, do you happen to know if some test failures are acceptable since
> our test suite is so enormous (6300+ tests)?
>
> Deron
>
>
>
> On Wed, Oct 19, 2016 at 3:24 AM, Glenn Weidner <gweid...@us.ibm.com>
> wrote:
>
> > It's a nice-to-have but not a release blocker.
> >
> > Thanks,
> > Glenn
> >
> > [image: Inactive hide details for Niketan Pansare---10/18/2016 05:38:26
> > PM---Glenn: Would you prefer to have https://github.com/apache/]Niketan
> > Pansare---10/18/2016 05:38:26 PM---Glenn: Would you prefer to have
> > https://github.com/apache/incubator-systemml/pull/269 in 0.11 releas
> >
> > From: Niketan Pansare/Almaden/IBM@IBMUS
> > To: dev@systemml.incubator.apache.org
> > Date: 10/18/2016 05:38 PM
> > Subject: Re: [VOTE] Apache SystemML 0.11.0-incubating (RC3)
> > --
> >
> >
> >
> > Glenn: Would you prefer to have
> > *https://github.com/apache/incubator-systemml/pull/269*
> > <https://github.com/apache/incubator-systemml/pull/269> in 0.11 release
> ?
> >
> > Thanks,
> >
> > Niketan Pansare
> > IBM Almaden Research Center
> > E-mail: npansar At us.ibm.com
> > *http://researcher.watson.ibm.com/researcher/view.php?person=us-npansar*
> > <http://researcher.watson.ibm.com/researcher/view.php?person=us-npansar>
> >
> > Luciano Resende ---10/17/2016 09:06:30 PM---Please note the minor
> > correction on the RC tag name (the actual tag hash is correct):
> >
> > From: Luciano Resende <luckbr1...@gmail.com>
> > To: dev@systemml.incubator.apache.org
> > Date: 10/17/2016 09:06 PM
> > Subject: Re: [VOTE] Apache SystemML 0.11.0-incubating (RC3)
> > ----------
> >
> >
> >
> > Please note the minor correction on the RC tag name (the actual tag hash
> is
> > correct):
> >
> > The tag to be voted on is v0.11.0-incubating-rc3 (
> > 1baebfde400134b3af6d373c254ee084a6d28cc3)
> >
> >
> > And off course, my +1
> >
> >
> > On Sat, Oct 15, 2016 at 12:27 PM, Luciano Resende <luckbr1...@gmail.com>
> > wrote:
> >
> > >
> > > Please vote on releasing the following candidate as Apache SystemML
> > > version 0.11.0-incubating !
> > >
> > > The vote is open for at least 72 hours and passes if a majority of at
> > > least 3 +1 PMC votes are cast.
> > >
> > > [ ] +1 Release this package as Apache SystemML 0.11.0-incubating
> > > [ ] -1 Do not release this package because ...
> > >
> > > To learn more about Apache SystemML, please see
> > > *http://systemml.apache.org/* <http://systemml.apache.org/>
> > >
> > > The tag to be voted on is v0.11.0-incubating-rc1 (
> > > 1baebfde400134b3af6d373c254ee084a6d28cc3)
> > >
> > > *https://github.com/apache/incubator-systemml/tree/1baebfde40*
> > <https://github.com/apache/incubator-systemml/tree/1baebfde40>
> > > 0134b3af6d373c254ee084a6d28cc3
> > >
> > > The release artifacts can be found at :
> > >
> > > *https://dist.apache.org/repos/dist/dev/incubator/systemml/0*
> > <https://dist.apache.org/repos/dist/dev/incubator/systemml/0>.
> > > 11.0-incubating-rc3/
> > >
> > > The maven release artifacts, including signatures, digests, etc. can be
> > > found at:
> > >
> > >
> > *https://repository.apache.org/content/repositories/
> orgapachesystemml-1009/*
> > <https://repository.apache.org/content/repositories/
> orgapachesystemml-1009/>
> > >
> > >
> > > =
> > > == Apache Incubator release policy ==
> > > =
> > > Please find below the guide to release management during incubation:
> > > *http://incubator.apache.org/guides/releasemanag

Re: UX Research

[Luciano Resende]

Great guys !!! I think having the UX roadmap published is fine, and we
could just create a roadmap page where we have sections for development and
ux and fixing SYSTEMML-972 (particularly SYSTEMML-974) will make it much
simpler to add more contents to the website.


https://issues.apache.org/jira/browse/SYSTEMML-972
https://issues.apache.org/jira/browse/SYSTEMML-974

On Mon, Oct 17, 2016 at 5:42 PM, Jeremy Anderson <jer...@objectadjective.com
> wrote:

> Thanks Madison and Felix. To your point Felix, I think you're on the nose.
> I am hoping actionable items for both design and dev will emerge from user
> research. Ideally, I'd love to see a clear direction and roadmap for the
> future of SystemML begin to take shape. This thread is a great start, but
> it might also be helpful to start a UX roadmap wiki page. Who can I reach
> out to for access to publish to the wiki?
>
> Jeremy
>
> ...
>
> Jeremy Anderson
> https://twitter.com/ObjectAdjective
> http://www.linkedin.com/in/objectadjective
>
> On 17 October 2016 at 16:33, <fschue...@posteo.de> wrote:
>
> > Jeremy and others, thanks for the detailed presentation!
> > The storyboards look great and it would be nice to see SystemML getting
> to
> > a point where those scenarios just work!
> >
> > From the point of development I wonder how much is adding new features
> > (that enhance user experience) versus making it more stable/reliable and
> > compiling/editing resources and documentation.
> > It seems to me that what's currently missing are the easy entry points
> > both in documentation and user interfaces (API's, notebooks, quickstart
> > guides, ...) that are so perfectly depicted in those storyboards.
> >
> > I hope to see an outcome of actionable items for developers from this UX
> > research that we can manifest in concrete Jiras to work on.
> >
> > Felix
> >
> >
> >
> >
> > Am 18.10.2016 00:39 schrieb Jeremy Anderson:
> >
> >> Hi all,
> >>
> >> I began working with a few designers on UX research for SystemML. We
> >> synthesized some of our early findings to share with everyone. From some
> >> of
> >> the pain points that surfaced in our research, we began storyboarding
> user
> >> scenarios and look for ways we might be able to improve user experience
> >> and
> >> increase adoption. I wanted to start a discussion around this UX and
> >> research. Here's a link to the research we've synthesized so. I'd love
> >> input/thoughts from everyone.
> >>
> >> https://drive.google.com/file/d/0B2__Aw0kKn-uTWJ4S0ZvcHhhTE0/view
> >>
> >> Cheers,
> >>
> >> Jeremy
> >>
> >> ...
> >>
> >> Jeremy Anderson
> >> https://twitter.com/ObjectAdjective
> >> http://www.linkedin.com/in/objectadjective
> >>
> >
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [VOTE] Apache SystemML 0.11.0-incubating (RC3)

[Luciano Resende]

Please note the minor correction on the RC tag name (the actual tag hash is
correct):

The tag to be voted on is v0.11.0-incubating-rc3 (
1baebfde400134b3af6d373c254ee084a6d28cc3)


And off course, my +1


On Sat, Oct 15, 2016 at 12:27 PM, Luciano Resende <luckbr1...@gmail.com>
wrote:

>
> Please vote on releasing the following candidate as Apache SystemML
> version 0.11.0-incubating !
>
> The vote is open for at least 72 hours and passes if a majority of at
> least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache SystemML 0.11.0-incubating
> [ ] -1 Do not release this package because ...
>
> To learn more about Apache SystemML, please see
> http://systemml.apache.org/
>
> The tag to be voted on is v0.11.0-incubating-rc1 (
> 1baebfde400134b3af6d373c254ee084a6d28cc3)
>
> https://github.com/apache/incubator-systemml/tree/1baebfde40
> 0134b3af6d373c254ee084a6d28cc3
>
> The release artifacts can be found at :
>
> https://dist.apache.org/repos/dist/dev/incubator/systemml/0.
> 11.0-incubating-rc3/
>
> The maven release artifacts, including signatures, digests, etc. can be
> found at:
>
> https://repository.apache.org/content/repositories/orgapachesystemml-1009/
>
>
> =
> == Apache Incubator release policy ==
> =
> Please find below the guide to release management during incubation:
> http://incubator.apache.org/guides/releasemanagement.html
>
> ===
> == How can I help test this release? ==
> ===
> If you are a SystemML user, you can help us test this release by taking an
> existing Algorithm or workload and running on this release candidate, then
> reporting any regressions.
>
> 
> == What justifies a -1 vote for this release? ==
> 
> -1 votes should only occur for significant stop-ship bugs or legal
> related issues (e.g. wrong license, missing header files, etc). Minor bugs
> or regressions should not block this release.
>
>

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

[VOTE] Apache SystemML 0.11.0-incubating (RC3)

[Luciano Resende]

Please vote on releasing the following candidate as Apache SystemML version
0.11.0-incubating !

The vote is open for at least 72 hours and passes if a majority of at least
3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache SystemML 0.11.0-incubating
[ ] -1 Do not release this package because ...

To learn more about Apache SystemML, please see http://systemml.apache.org/

The tag to be voted on is v0.11.0-incubating-rc1
(1baebfde400134b3af6d373c254ee084a6d28cc3)

https://github.com/apache/incubator-systemml/tree/
1baebfde400134b3af6d373c254ee084a6d28cc3

The release artifacts can be found at :

https://dist.apache.org/repos/dist/dev/incubator/systemml/0.
11.0-incubating-rc3/

The maven release artifacts, including signatures, digests, etc. can be
found at:

https://repository.apache.org/content/repositories/orgapachesystemml-1009/


=
== Apache Incubator release policy ==
=
Please find below the guide to release management during incubation:
http://incubator.apache.org/guides/releasemanagement.html

===
== How can I help test this release? ==
===
If you are a SystemML user, you can help us test this release by taking an
existing Algorithm or workload and running on this release candidate, then
reporting any regressions.


== What justifies a -1 vote for this release? ==

-1 votes should only occur for significant stop-ship bugs or legal related
issues (e.g. wrong license, missing header files, etc). Minor bugs or
regressions should not block this release.


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Getting new users to adopt SystemML

[Luciano Resende]

On Fri, Oct 7, 2016 at 5:43 PM, Jeremy Anderson <jer...@objectadjective.com>
wrote:

> > Although this is unavoidable, if the projects are closely associated with
> > SystemML it might be better to have it collocated in the project, as it
> > might make it simpler for users to discover and consistently use.
>
> Thanks Luciano. I'm starting to think this may be the way we want to go,
> creating a research directory in the main apache repo. Our original
> thinking was we wanted to create one centralized repo for all data related
> ux research. I do love this idea, but our research to date is very specific
> to SystemML. We are hoping to link research findings to pull requests. Over
> time, this would provide context for why certain features/changes were made
> and make it easier for future development. If anyone has thoughts on how to
> best handle this, I'd love to hear. :)
>

+1 to incorporate this as one page in the systemml website or doc

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [VOTE] Apache SystemML 0.11.0-incubating (RC1)

[Luciano Resende]

Ok, so looks like we are down to waiting on SYSTEMML-1009.

On Tue, Oct 4, 2016 at 4:44 PM, <dusenberr...@gmail.com> wrote:

> The Python test failure issue has been resolved in SYSTEMML-1005. From my
> end, we are ready to go.
>
> -Mike
>
> --
>
> Mike Dusenberry
> GitHub: github.com/dusenberrymw
> LinkedIn: linkedin.com/in/mikedusenberry
>
> Sent from my iPhone.
>
>
> > On Oct 4, 2016, at 2:02 PM, Matthias Boehm <mbo...@us.ibm.com> wrote:
> >
> > apart from the recently resolved SYSTEMML-1004 and SYSTEMML-1008, there
> is one more performance fix I'd like to get in: SYSTEMML-1009.
> >
> > Regards,
> > Matthias
> >
> > Luciano Resende ---10/04/2016 12:29:12 PM---Mike, are these Python
> failures still blocking the next RC ? Please let me know, as I am waiting
> for
> >
> > From: Luciano Resende <luckbr1...@gmail.com>
> > To: dev@systemml.incubator.apache.org
> > Date: 10/04/2016 12:29 PM
> > Subject: Re: [VOTE] Apache SystemML 0.11.0-incubating (RC1)
> >
> >
> >
> >
> > Mike, are these Python failures still blocking the next RC ? Please let
> me
> > know, as I am waiting for the green light to cut the RC2.
> >
> > On Mon, Oct 3, 2016 at 9:41 AM, <dusenberr...@gmail.com> wrote:
> >
> > > Yeah I can confirm that all of those issues are now resolved, which is
> > > great!  However, I'm seeing a test failure in the Python mllearn tests
> > > today that I want to look into before we cut.
> > >
> > > -Mike
> > >
> > > --
> > >
> > > Mike Dusenberry
> > > GitHub: github.com/dusenberrymw
> > > LinkedIn: linkedin.com/in/mikedusenberry
> > >
> > > Sent from my iPhone.
> > >
> > >
> > > > On Oct 2, 2016, at 8:35 PM, Matthias Boehm <mbo...@us.ibm.com>
> wrote:
> > > >
> > > > yes, I just closed them - I left them open for Mike to confirm, but
> we
> > > resolved all known issues yesterday together. We should be good to go.
> > > >
> > > > Regards,
> > > > Matthias
> > > >
> > > > Luciano Resende ---10/02/2016 08:30:37 PM---I still see the following
> > > jiras, which were mentioned on this thread, open:
> https://issues.apache.or
> > > >
> > > > From: Luciano Resende <luckbr1...@gmail.com>
> > > > To: dev@systemml.incubator.apache.org
> > > > Date: 10/02/2016 08:30 PM
> > > > Subject: Re: [VOTE] Apache SystemML 0.11.0-incubating (RC1)
> > > >
> > > >
> > > >
> > > >
> > > > I still see the following jiras, which were mentioned on this thread,
> > > open:
> > > >
> > > > https://issues.apache.org/jira/browse/SYSTEMML-993
> > > > https://issues.apache.org/jira/browse/SYSTEMML-994
> > > > https://issues.apache.org/jira/browse/SYSTEMML-995
> > > >
> > > > Did folks forgot to clode the jiras ? Or are there things that still
> need
> > > > to be handled here ?
> > > >
> > > >
> > > > On Sat, Oct 1, 2016 at 2:41 PM, Matthias Boehm <mbo...@us.ibm.com>
> > > wrote:
> > > >
> > > > > ok the blocking issues SYSTEMML-993, 994, and 995 have been
> resolved -
> > > > > from my perspective we're ready to cut a new RC.
> > > > >
> > > > > Regards,
> > > > > Matthias
> > > > >
> > > > > [image: Inactive hide details for Matthias Boehm---09/29/2016
> 10:44:51
> > > > > PM---just a quick update: SYSTEMML-969 has been resolved too.
> > > Th]Matthias
> > > > > Boehm---09/29/2016 10:44:51 PM---just a quick update: SYSTEMML-969
> has
> > > been
> > > > > resolved too. The open issues are SYSTEMML-993, SYSTEMML-
> > > > >
> > > > > From: Matthias Boehm/Almaden/IBM@IBMUS
> > > > > To: dev@systemml.incubator.apache.org
> > > > > Date: 09/29/2016 10:44 PM
> > > > > Subject: Re: [VOTE] Apache SystemML 0.11.0-incubating (RC1)
> > > > > --
> > > > >
> > > > >
> > > > >
> > > > > just a quick update: SYSTEMML-969 has been resolved too. The open
> > > issues
> > > > > are SYSTEMML-993, SYSTEMML-994, and the new SYSTEMML-995. We
> should be
> > > able
> > > > > to resolve them by tomorrow

Re: [VOTE] Apache SystemML 0.11.0-incubating (RC1)

[Luciano Resende]

Mike, are these Python failures still blocking the next RC ? Please let me
know, as I am waiting for the green light to cut the RC2.

On Mon, Oct 3, 2016 at 9:41 AM, <dusenberr...@gmail.com> wrote:

> Yeah I can confirm that all of those issues are now resolved, which is
> great!  However, I'm seeing a test failure in the Python mllearn tests
> today that I want to look into before we cut.
>
> -Mike
>
> --
>
> Mike Dusenberry
> GitHub: github.com/dusenberrymw
> LinkedIn: linkedin.com/in/mikedusenberry
>
> Sent from my iPhone.
>
>
> > On Oct 2, 2016, at 8:35 PM, Matthias Boehm <mbo...@us.ibm.com> wrote:
> >
> > yes, I just closed them - I left them open for Mike to confirm, but we
> resolved all known issues yesterday together. We should be good to go.
> >
> > Regards,
> > Matthias
> >
> > Luciano Resende ---10/02/2016 08:30:37 PM---I still see the following
> jiras, which were mentioned on this thread, open: https://issues.apache.or
> >
> > From: Luciano Resende <luckbr1...@gmail.com>
> > To: dev@systemml.incubator.apache.org
> > Date: 10/02/2016 08:30 PM
> > Subject: Re: [VOTE] Apache SystemML 0.11.0-incubating (RC1)
> >
> >
> >
> >
> > I still see the following jiras, which were mentioned on this thread,
> open:
> >
> > https://issues.apache.org/jira/browse/SYSTEMML-993
> > https://issues.apache.org/jira/browse/SYSTEMML-994
> > https://issues.apache.org/jira/browse/SYSTEMML-995
> >
> > Did folks forgot to clode the jiras ? Or are there things that still need
> > to be handled here ?
> >
> >
> > On Sat, Oct 1, 2016 at 2:41 PM, Matthias Boehm <mbo...@us.ibm.com>
> wrote:
> >
> > > ok the blocking issues SYSTEMML-993, 994, and 995 have been resolved -
> > > from my perspective we're ready to cut a new RC.
> > >
> > > Regards,
> > > Matthias
> > >
> > > [image: Inactive hide details for Matthias Boehm---09/29/2016 10:44:51
> > > PM---just a quick update: SYSTEMML-969 has been resolved too.
> Th]Matthias
> > > Boehm---09/29/2016 10:44:51 PM---just a quick update: SYSTEMML-969 has
> been
> > > resolved too. The open issues are SYSTEMML-993, SYSTEMML-
> > >
> > > From: Matthias Boehm/Almaden/IBM@IBMUS
> > > To: dev@systemml.incubator.apache.org
> > > Date: 09/29/2016 10:44 PM
> > > Subject: Re: [VOTE] Apache SystemML 0.11.0-incubating (RC1)
> > > --
> > >
> > >
> > >
> > > just a quick update: SYSTEMML-969 has been resolved too. The open
> issues
> > > are SYSTEMML-993, SYSTEMML-994, and the new SYSTEMML-995. We should be
> able
> > > to resolve them by tomorrow to give everybody a chance of testing a
> new RC
> > > over the weekend.
> > >
> > > Regards,
> > > Matthias
> > >
> > > Acs S ---09/29/2016 05:31:23 PM---SYSTEMML-964 being addressed (I added
> > > changes and with UTF support Matthias added he reverted change
> > >
> > > From: Acs S <ac...@yahoo.com.INVALID>
> > > To: "dev@systemml.incubator.apache.org" <dev@systemml.incubator.
> apache.org
> > > >
> > > Date: 09/29/2016 05:31 PM
> > > Subject: Re: [VOTE] Apache SystemML 0.11.0-incubating (RC1)
> > > --
> > >
> > >
> > >
> > > SYSTEMML-964 being addressed (I added changes and with UTF support
> > > Matthias added he reverted changes)
> > >
> > > -Arvind
> > >
> > > From: "dusenberr...@gmail.com" <dusenberr...@gmail.com>
> > > To: dev@systemml.incubator.apache.org
> > > Sent: Thursday, September 29, 2016 2:31 PM
> > > Subject: Re: [VOTE] Apache SystemML 0.11.0-incubating (RC1)
> > >
> > > I've also opened SYSTEMML-993 that relates to poor performance for
> vector
> > > DataFrame conversions, as well as SYSTEMML-994 for GC OOM on SystemML
> > > matrix to frame conversions that would both be good to work on.
> > >
> > > --
> > >
> > > Mike Dusenberry
> > > GitHub: github.com/dusenberrymw
> > > LinkedIn: linkedin.com/in/mikedusenberry
> > >
> > > Sent from my iPhone.
> > >
> > >
> > > > On Sep 29, 2016, at 12:32 PM, Luciano Resende <luckbr1...@gmail.com>
> > > wrote:
> > > >
> > > >> On Thu, Sep 29, 2016 at 11:11 AM, Matthias Boehm <mbo...@us.ibm.com
> >
> > > wrote:
> > > >>
> > > >> SYSTEMML-968 has been resolved too but we're still waiting for
> > > >> SYSTEMML-964. Furthermore, there is also a nice-to-have feature we
> want
> > > to
> > > >> get it in: SYSTEMML-969 (extended dataframe - frame converter).
> > > >>
> > > >> Regards,
> > > >> Matthias
> > > > Great progress !!!
> > > >
> > > > Matthias, please let us know when these issues get resolved and I
> will
> > > work
> > > > on RC2.
> > > >
> > > > --
> > > > Luciano Resende
> > > > *http://twitter.com/lresende1975* <http://twitter.com/lresende1975>
> > > > *http://lresende.blogspot.com/* <http://lresende.blogspot.com/>
> > >
> > >
> > >
> > >
> > >
> >
> >
> > --
> > Luciano Resende
> > http://twitter.com/lresende1975
> > http://lresende.blogspot.com/
> >
> >
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [VOTE] Apache SystemML 0.11.0-incubating (RC1)

[Luciano Resende]

I still see the following jiras, which were mentioned on this thread, open:

https://issues.apache.org/jira/browse/SYSTEMML-993
https://issues.apache.org/jira/browse/SYSTEMML-994
https://issues.apache.org/jira/browse/SYSTEMML-995

Did folks forgot to clode the jiras ? Or are there things that still need
to be handled here ?


On Sat, Oct 1, 2016 at 2:41 PM, Matthias Boehm <mbo...@us.ibm.com> wrote:

> ok the blocking issues SYSTEMML-993, 994, and 995 have been resolved -
> from my perspective we're ready to cut a new RC.
>
> Regards,
> Matthias
>
> [image: Inactive hide details for Matthias Boehm---09/29/2016 10:44:51
> PM---just a quick update: SYSTEMML-969 has been resolved too. Th]Matthias
> Boehm---09/29/2016 10:44:51 PM---just a quick update: SYSTEMML-969 has been
> resolved too. The open issues are SYSTEMML-993, SYSTEMML-
>
> From: Matthias Boehm/Almaden/IBM@IBMUS
> To: dev@systemml.incubator.apache.org
> Date: 09/29/2016 10:44 PM
> Subject: Re: [VOTE] Apache SystemML 0.11.0-incubating (RC1)
> --
>
>
>
> just a quick update: SYSTEMML-969 has been resolved too. The open issues
> are SYSTEMML-993, SYSTEMML-994, and the new SYSTEMML-995. We should be able
> to resolve them by tomorrow to give everybody a chance of testing a new RC
> over the weekend.
>
> Regards,
> Matthias
>
> Acs S ---09/29/2016 05:31:23 PM---SYSTEMML-964 being addressed (I added
> changes and with UTF support Matthias added he reverted change
>
> From: Acs S <ac...@yahoo.com.INVALID>
> To: "dev@systemml.incubator.apache.org" <dev@systemml.incubator.apache.org
> >
> Date: 09/29/2016 05:31 PM
> Subject: Re: [VOTE] Apache SystemML 0.11.0-incubating (RC1)
> --
>
>
>
> SYSTEMML-964 being addressed (I added changes and with UTF support
> Matthias added he reverted changes)
>
> -Arvind
>
> From: "dusenberr...@gmail.com" <dusenberr...@gmail.com>
> To: dev@systemml.incubator.apache.org
> Sent: Thursday, September 29, 2016 2:31 PM
> Subject: Re: [VOTE] Apache SystemML 0.11.0-incubating (RC1)
>
> I've also opened SYSTEMML-993 that relates to poor performance for vector
> DataFrame conversions, as well as SYSTEMML-994 for GC OOM on SystemML
> matrix to frame conversions that would both be good to work on.
>
> --
>
> Mike Dusenberry
> GitHub: github.com/dusenberrymw
> LinkedIn: linkedin.com/in/mikedusenberry
>
> Sent from my iPhone.
>
>
> > On Sep 29, 2016, at 12:32 PM, Luciano Resende <luckbr1...@gmail.com>
> wrote:
> >
> >> On Thu, Sep 29, 2016 at 11:11 AM, Matthias Boehm <mbo...@us.ibm.com>
> wrote:
> >>
> >> SYSTEMML-968 has been resolved too but we're still waiting for
> >> SYSTEMML-964. Furthermore, there is also a nice-to-have feature we want
> to
> >> get it in: SYSTEMML-969 (extended dataframe - frame converter).
> >>
> >> Regards,
> >> Matthias
> > Great progress !!!
> >
> > Matthias, please let us know when these issues get resolved and I will
> work
> > on RC2.
> >
> > --
> > Luciano Resende
> > *http://twitter.com/lresende1975* <http://twitter.com/lresende1975>
> > *http://lresende.blogspot.com/* <http://lresende.blogspot.com/>
>
>
>
>
>


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Enhancing SystemML JavaDocs

[Luciano Resende]

Currently we have a bunch of wrong, incomplete or obsolete javadocs on our
APIs, and this continue o grow because we have the following configuration
in our build:



ignore-doclint-warnings-for-javadocs-on-java-8

[1.8,)


-Xdoclint:none




I know we are very close to 0.11 release to fix this, but I would like to
make this issue as blocker for our next release (1.0 release), and thus
would like to get everybody to give it a try by removing this configuration
and trying to build SystemML and fix a few of the Javadoc issues.

If we can get a few PRs per week, we can fix this very quick for the next
release.

Thoughts ?


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Continuing development on the website

[Luciano Resende]

On Wed, Sep 28, 2016 at 5:51 PM, Luciano Resende <luckbr1...@gmail.com>
wrote:

> Ok, master now have the "in progress" version of the refactored jekyll
> website and the previous working version has been tagged as v0.1.
>
>
I am also trying to list the remaining website items as sub tasks within
SYSTEMML-972. Feel free to grab them and submit PRs.

https://issues.apache.org/jira/browse/SYSTEMML-972


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Continuing development on the website

[Luciano Resende]

Ok, master now have the "in progress" version of the refactored jekyll
website and the previous working version has been tagged as v0.1.

On Wed, Sep 28, 2016 at 2:13 PM, Deron Eriksson <deroneriks...@gmail.com>
wrote:

> Hello Luciano,
>
> I would prefer doing fixes on master for the website. However, I do not
> feel strongly about this issue.
>
> Anyone else any thoughts?
>
> Deron
>
>
> On Wed, Sep 28, 2016 at 1:28 PM, Luciano Resende <luckbr1...@gmail.com>
> wrote:
>
> > I have created a PR [1] porting the Jekyll based website to use the new
> > design contributed via SYSTEMML-892. Currently it has a few small issues
> > that needs to be resolved before we can start using it as the source of
> the
> > website again.
> >
> > Now, to resolve these issues, we can either create a branch and, as a
> > community, address the remaining issues, or tag the current version of
> > master, and start doing development/fixes on master.
> >
> > What would the preference of the community ?
> >
> >
> > [1] https://github.com/apache/incubator-systemml-website/pull/2
> > [2] https://issues.apache.org/jira/browse/SYSTEMML-892
> >
> > --
> > Luciano Resende
> > http://twitter.com/lresende1975
> > http://lresende.blogspot.com/
> >
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Scala support ?

[Luciano Resende]

On Wed, Sep 28, 2016 at 2:29 PM, Niketan Pansare <npan...@us.ibm.com> wrote:

> That is correct. Again, it is a good idea to make the scala version
> explicit either in jar naming or in the release notes.
>
> I am not sure what is the recommended practice in Spark community for
> developing applications.
> - Should one release two jars with explicit scala versions (scala 2.10 and
> scala 2.11) and let user download the correct version OR
> - Only release one jar (by sticking to some rule: "scala version matches
> the default scala version of the supported spark version") and provide
> instructions to compile with different scala version. Spark follows this
> option.
>
> For compiling with different scala version, isn't it as simple as
> providing a flag (-Dscala.version=2.11) to mvn rather than modifying the
> pom itself ?
>
>
There is usually one version of the jar on the distribution (e.g. the
default like _2.10), but then, during release, they make the two versions
published to maven, so in case of building applications, you don't have to
actually have to build the framework with the version of Scala being used.


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [VOTE] Apache SystemML 0.11.0-incubating (RC1)

[Luciano Resende]

On Wed, Sep 28, 2016 at 3:14 PM, Matthias Boehm <mbo...@us.ibm.com> wrote:

> -1, unfortunately, SYSTEMML-964 and SYSTEMML-968 are blocking the release
> right now but we should be able to resolve them by tomorrow.
>
> Regards,
> Matthias
>

Thanks Matthias.

Others, please make sure you review this RC as well, so we get all issues
fixed by RC2.


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Continuing development on the website

[Luciano Resende]

I have created a PR [1] porting the Jekyll based website to use the new
design contributed via SYSTEMML-892. Currently it has a few small issues
that needs to be resolved before we can start using it as the source of the
website again.

Now, to resolve these issues, we can either create a branch and, as a
community, address the remaining issues, or tag the current version of
master, and start doing development/fixes on master.

What would the preference of the community ?


[1] https://github.com/apache/incubator-systemml-website/pull/2
[2] https://issues.apache.org/jira/browse/SYSTEMML-892

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Scala support ?

[Luciano Resende]

On Wed, Sep 28, 2016 at 12:55 PM, Niketan Pansare <npan...@us.ibm.com>
wrote:

> I think making scala version explicit is a good idea. Implicitly we are
> consistent with spark version supported in the release.
>
>
Implicitly only if the user does not choose to build Spark release with
Scala 2.11, which then will be a mismatch and the user will have to hack
it's way to be able to change the necessary places in the pom and rebuild
it.



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Scala support ?

[Luciano Resende]

We are currently compiling some scala code inside the SystemML Jar and we
are currently not really identifying in any way which version it was used
to build the jar.

Should we start prefixing the jar with _2.10 and documenting how to build
with scala 2.11 ?

Also, during release, should we publish both _2.10 and _2.11 versions to
maven ?

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Building a community around SystemML

[Luciano Resende]

One of the remaining things that SystemML needs to do in order to graduate
is to build a better community around the project.

Some ideas are:

- Be more open with mailing lists discussions particularly with high level
designs that sometimes just get buried in PRs.
- Identify and participate on projects where more experienced community
members would mentor students or others interested in
participating/contributing to the project (e.g. GSoC)
- Identify top two main personas that would be interested in the project,
and bring up visibility on documentation based on these personas to make
their first experience with the project very smooth and without much
problems.
- Create simple JIRAs and flag them for initial contributors (e.g.
documentation, simple fix, etc)

Any other ideas ? And how do we execute this with some priority to get us
to graduate ?

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

[VOTE] Apache SystemML 0.11.0-incubating (RC1)

[Luciano Resende]

Please vote on releasing the following candidate as Apache SystemML version
0.11.0-incubating !

The vote is open for at least 72 hours and will close on Saturday,
Wednesday 25 and passes if a majority of at least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache SystemML 0.11.0-incubating
[ ] -1 Do not release this package because ...

To learn more about Apache SystemML, please see http://systemml.apache.org/

The tag to be voted on is v0.11.0-incubating-rc1
(3afb0c9e650f14d30bf4a938b7780806c9d049d1)

https://github.com/apache/incubator-systemml/tree/
3afb0c9e650f14d30bf4a938b7780806c9d049d1

The release artifacts can be found at :

https://dist.apache.org/repos/dist/dev/incubator/systemml/0.
11.0-incubating-rc1/

The maven release artifacts, including signatures, digests, etc. can be
found at:

https://repository.apache.org/content/repositories/orgapachesystemml-1007/


=
== Apache Incubator release policy ==
=
Please find below the guide to release management during incubation:
http://incubator.apache.org/guides/releasemanagement.html

===
== How can I help test this release? ==
===
If you are a SystemML user, you can help us test this release by taking an
existing Algorithm or workload and running on this release candidate, then
reporting any regressions.


== What justifies a -1 vote for this release? ==

-1 votes should only occur for significant stop-ship bugs or legal related
issues (e.g. wrong license, missing header files, etc). Minor bugs or
regressions should not block this release.

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [VOTE] Please vote to have Apache SystemML 0.11 release

[Luciano Resende]

On Wed, Sep 21, 2016 at 11:35 AM, Acs S <ac...@yahoo.com.invalid> wrote:

> Please vote on making Apache SystemML 0.11 release available
>
> -Arvind


What are we voting on ? Where are the artifacts that need to be reviewed ?
RC tag, etc ?

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: New SystemML website design

[Luciano Resende]

The new design for the website is now live as the main site.

I have made a few modifications:
- Properly use the Incubator disclaimer footer
- Use download on the top level "get started"  button
- Added links to Python and R getting started guides on the "getting
started section"

One more time, thanks Jeremy

Please file jiras you find any issues...

I am still working on integrating this into jekyll website structure.


On Sun, Sep 4, 2016 at 12:53 PM, Deron Eriksson <deroneriks...@gmail.com>
wrote:

> Perhaps for today we can go with the current setup and in the near future
> create a new updated Getting Started page as Arvind suggests. Ideally
> someone new to the site can download SystemML and get started in 5 minutes
> or less. I definitely agree with Niketan that it would be great to go to a
> page where I download and see how to run SystemML ("Getting Started"). We
> have much of this content already but I think it needs to be reorganized.
>
> Deron
>
>
>
>
> On Sun, Sep 4, 2016 at 12:30 PM, Acs S <ac...@yahoo.com.invalid> wrote:
>
> > Yes, its very nice redesign (for landing page). Thanks Jeremy for your
> > effort in short period of time, and rest of the team to provide needed
> > resources.
> > Given a limited time, effort was to focus on first page when visitors
> > visit home page.There is lot to be done to re-organize rest of the
> pages, I
> > hope it will follow based on available resources.
> > Niketan, "Get Started" link to "Beginner's Guide" is a good idea, but I
> > would recommend after redesigning whole site, unless we update "Get
> > Started" page to accommodate this suggestion.For now, only these two
> pages
> > are redesigned. Hopefully we can redesign "Get Started" page soon to
> > accommodate this suggestion.
> > -Arvind
> >
> >
> >   From: Niketan Pansare <npan...@us.ibm.com>
> >  To: dev@systemml.incubator.apache.org
> >  Sent: Sunday, September 4, 2016 12:06 PM
> >  Subject: Re: New SystemML website design
> >
> >
> >
> > Thanks Jeremy. The website looks awesome !!
> >
> > Deron/Luciano: Do you think we should change the 'Get Started' link to
> > point to one of the beginner's guide rather than point to the Download
> > page ? Alternatively we can add a link in Download page instructing what
> > the user should do next after downloading.
> >
> > Again, absolutely love the new website :) :)
> >
> > Thanks,
> >
> > Niketan
> >
> > > On Sep 4, 2016, at 11:22 AM, Deron Eriksson <deroneriks...@gmail.com>
> > wrote:
> > >
> > > Wow, these updates really look incredible! Thank you Jeremy Anderson
> for
> > > this amazing contribution!
> > >
> > > Deron
> > >
> > >
> > > On Sun, Sep 4, 2016 at 11:13 AM, Luciano Resende <luckbr1...@gmail.com
> >
> > > wrote:
> > >
> > >> Jeremy Anderson has been so kind to spend few days on a new design for
> > the
> > >> Apache SystemML website, and this is now attached to :
> > >>
> > >> https://issues.apache.org/jira/browse/SYSTEMML-892
> > >>
> > >> If you are eager to check how it looks, while we do some minor
> > adjustments
> > >> to integrate to our website build, I have published a in-progress
> > version
> > >> at:
> > >>
> > >> http://home.apache.org/~lresende/systemml/
> > >>
> > >> --
> > >> Luciano Resende
> > >> http://twitter.com/lresende1975
> > >> http://lresende.blogspot.com/
> > >>
> >
> >
> >
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

New SystemML website design

[Luciano Resende]

Jeremy Anderson has been so kind to spend few days on a new design for the
Apache SystemML website, and this is now attached to :

https://issues.apache.org/jira/browse/SYSTEMML-892

If you are eager to check how it looks, while we do some minor adjustments
to integrate to our website build, I have published a in-progress version
at:

http://home.apache.org/~lresende/systemml/

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Support for 'pip install SystemML'

[Luciano Resende]

On Thu, Aug 25, 2016 at 6:38 PM, Niketan Pansare <npan...@us.ibm.com> wrote:

>
>
> Hi all,
>
> As part of the PR https://github.com/apache/incubator-systemml/pull/197, I
> have created a setup.py and also uploaded a preview version of the SystemML
> Python package on PyPI (If interested, you can try it by following the
> instructions given in
> http://niketanpansare.github.io/incubator-systemml/beginners-guide-python#
> install-systemml
> ). This package packs the content of our distribution (license, notice,
> readme, SystemML.jar and algorithms) along with the python files and is
> also flagged with Apache 2.0 license in setup.py.
>

Very good addition to SystemML.

Note that, putting SystemML artifacts into PyPI is similar to putting
SystemML artifacts into a maven repository and should only be done
officially when a release is done, or periodically as dev, which I believe
is similar to the concept of SNAPSHOTS in maven (see
https://pypi.python.org/pypi/toree).


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [DISCUSS] Apache SystemML Release 1.0.0

[Luciano Resende]

On Thu, Aug 25, 2016 at 4:01 PM, Deron Eriksson <deroneriks...@gmail.com>
wrote:

> Luciano,
>
> Yes, I like the idea of the next release being SystemML 1.0. Given the
> significance of the version, it would be a good idea to not rush the
> release so that we can make this a truly great release.
>
> Deron
>
>
>
I am not suggesting to rush a release, just that we would not call 0.11 and
1.0. The time frame is based on when we are ready.

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [DISCUSS] SystemML with Spark 2.0 support and roadmap

[Luciano Resende]

On Tue, Aug 23, 2016 at 3:51 PM, Deron Eriksson <deroneriks...@gmail.com>
wrote:

> To simplify release candidate validation, I would like to propose that the
> distribution profile only builds the following 7 (out of the current
> included 10) artifacts:
>
> systemml-0.11.0-incubating-SNAPSHOT-javadoc.jar
> systemml-0.11.0-incubating-SNAPSHOT-sources.jar
> systemml-0.11.0-incubating-SNAPSHOT-src.tar.gz
> systemml-0.11.0-incubating-SNAPSHOT-src.zip
> systemml-0.11.0-incubating-SNAPSHOT-standalone.tar.gz (rename w/o
> "-standalone")
> systemml-0.11.0-incubating-SNAPSHOT-standalone.zip (rename w/o
> "-standalone")
> systemml-0.11.0-incubating-SNAPSHOT.jar
>
> The following could still be built using maven profiles but would not be in
> the distribution profile:
>
> systemml-0.11.0-incubating-SNAPSHOT-standalone.jar
> systemml-0.11.0-incubating-SNAPSHOT.tar.gz (also rename)
> systemml-0.11.0-incubating-SNAPSHOT.zip (also rename)
>
> This would decrease the number of our artifacts by 30% which means that we
> can validate the release faster, and the release candidate will also be
> more likely to pass external validation/voting.
>
> Deron
>
>
+1


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Preview tag, was Re: [2/2] incubator-systemml git commit: Preparing SystemML development version 0.11.0-incubating-SNAPSHOT.

[Luciano Resende]

Great, thanks.

On Wed, Aug 17, 2016 at 2:32 PM, <dusenberr...@gmail.com> wrote:

> Thanks, Luciano for pointing this out. As you mentioned, the intent was
> definitely just to tag a commit that was known to be stable on the Spark
> 1.x line. I've deleted the existing tag, and created a new
> "spark-1.x-stable" tag simply pointing to a previous commit that was tested
> on Spark 1.x.
>
> Thanks!
>
> -Mike
>
> --
>
> Mike Dusenberry
> GitHub: github.com/dusenberrymw
> LinkedIn: linkedin.com/in/mikedusenberry
>
> Sent from my iPhone.
>
>
> > On Aug 17, 2016, at 11:18 AM, Luciano Resende <luckbr1...@gmail.com>
> wrote:
> >
> > -1
> >
> > Sorry Folks, this isn't a voted release and thus creating a tag without
> > SNAPSHOT is not valid. Please delete this tag.
> >
> > If what is wanted is to have a stable point in the codebase where folks
> can
> > go back if a release is needed for 1.x, then just create a branch/tag
> with
> > a descriptive name (e.g. spark_1.x_stable).
> >
> > If you actually want a release, there is a need to follow the Apache
> > Release vote process (e.g. see
> > https://www.mail-archive.com/dev%40spark.apache.org/msg14223.html for
> Spark
> > preview release vote)
> >
> > Thanks
> >
> >
> >> On Wed, Aug 17, 2016 at 1:21 PM, <dusenberr...@apache.org> wrote:
> >>
> >> Preparing SystemML development version 0.11.0-incubating-SNAPSHOT.
> >>
> >>
> >> Project: http://git-wip-us.apache.org/repos/asf/incubator-systemml/repo
> >> Commit: http://git-wip-us.apache.org/repos/asf/incubator-systemml/
> >> commit/b6bde0d4
> >> Tree: http://git-wip-us.apache.org/repos/asf/incubator-systemml/
> >> tree/b6bde0d4
> >> Diff: http://git-wip-us.apache.org/repos/asf/incubator-systemml/
> >> diff/b6bde0d4
> >>
> >> Branch: refs/heads/master
> >> Commit: b6bde0d4599d551cf1dc903c72662888abc22787
> >> Parents: 05b6da0
> >> Author: Mike Dusenberry <mwdus...@us.ibm.com>
> >> Authored: Wed Aug 17 10:17:52 2016 -0700
> >> Committer: Mike Dusenberry <mwdus...@us.ibm.com>
> >> Committed: Wed Aug 17 10:17:52 2016 -0700
> >>
> >> --
> >> pom.xml | 4 ++--
> >> 1 file changed, 2 insertions(+), 2 deletions(-)
> >> --
> >>
> >>
> >> http://git-wip-us.apache.org/repos/asf/incubator-systemml/
> >> blob/b6bde0d4/pom.xml
> >> --
> >> diff --git a/pom.xml b/pom.xml
> >> index aba8808..a4c66a1 100644
> >> --- a/pom.xml
> >> +++ b/pom.xml
> >> @@ -25,7 +25,7 @@
> >>18
> >>
> >>org.apache.systemml
> >> -   0.11.0-incubating-preview
> >> +   0.11.0-incubating-SNAPSHOT
> >>    systemml
> >>jar
> >>SystemML
> >> @@ -41,7 +41,7 @@
> >>scm:git:g...@github.com:apache/incubator-
> >> systemml
> >>scm:git:h
> >> ttps://git-wip-us.apache.org/repos/asf/incubator-systemml >> developerConnection>
> >>https://git-wip-us.apache.org/repos/asf?p=
> >> incubator-systemml.git
> >> -   0.11.0-incubating-preview
> >> +   HEAD
> >>
> >>
> >>JIRA
> >
> >
> > --
> > Luciano Resende
> > http://twitter.com/lresende1975
> > http://lresende.blogspot.com/
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Preview tag, was Re: [2/2] incubator-systemml git commit: Preparing SystemML development version 0.11.0-incubating-SNAPSHOT.

[Luciano Resende]

-1

Sorry Folks, this isn't a voted release and thus creating a tag without
SNAPSHOT is not valid. Please delete this tag.

If what is wanted is to have a stable point in the codebase where folks can
go back if a release is needed for 1.x, then just create a branch/tag with
a descriptive name (e.g. spark_1.x_stable).

If you actually want a release, there is a need to follow the Apache
Release vote process (e.g. see
https://www.mail-archive.com/dev%40spark.apache.org/msg14223.html for Spark
preview release vote)

Thanks


On Wed, Aug 17, 2016 at 1:21 PM, <dusenberr...@apache.org> wrote:

> Preparing SystemML development version 0.11.0-incubating-SNAPSHOT.
>
>
> Project: http://git-wip-us.apache.org/repos/asf/incubator-systemml/repo
> Commit: http://git-wip-us.apache.org/repos/asf/incubator-systemml/
> commit/b6bde0d4
> Tree: http://git-wip-us.apache.org/repos/asf/incubator-systemml/
> tree/b6bde0d4
> Diff: http://git-wip-us.apache.org/repos/asf/incubator-systemml/
> diff/b6bde0d4
>
> Branch: refs/heads/master
> Commit: b6bde0d4599d551cf1dc903c72662888abc22787
> Parents: 05b6da0
> Author: Mike Dusenberry <mwdus...@us.ibm.com>
> Authored: Wed Aug 17 10:17:52 2016 -0700
> Committer: Mike Dusenberry <mwdus...@us.ibm.com>
> Committed: Wed Aug 17 10:17:52 2016 -0700
>
> --
>  pom.xml | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> --
>
>
> http://git-wip-us.apache.org/repos/asf/incubator-systemml/
> blob/b6bde0d4/pom.xml
> --
> diff --git a/pom.xml b/pom.xml
> index aba8808..a4c66a1 100644
> --- a/pom.xml
> +++ b/pom.xml
> @@ -25,7 +25,7 @@
> 18
> 
> org.apache.systemml
> -   0.11.0-incubating-preview
> +   0.11.0-incubating-SNAPSHOT
> systemml
> jar
> SystemML
> @@ -41,7 +41,7 @@
> scm:git:g...@github.com:apache/incubator-
> systemml
> scm:git:h
> ttps://git-wip-us.apache.org/repos/asf/incubator-systemml developerConnection>
> https://git-wip-us.apache.org/repos/asf?p=
> incubator-systemml.git
> -   0.11.0-incubating-preview
> +   HEAD
> 
> 
> JIRA
>
>


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [DISCUSS] Migration to Spark 2.0.0

[Luciano Resende]

That was going to be my suggestion... In Zeppelin, we just introduced
support for different versions of scala and added support for spark 2.0
based on profiles and a bit of reflections...

Do we have to do anything related to Scala versions as well ?

On Thursday, August 4, 2016, Matthias Boehm  wrote:

> I would recommend to start an investigation if we could support both the
> 1.x and 2.x lines with a single code base. It seems feasible to refactor
> the code a bit, compile against 2.0 (or with profiles), and run on either
> 1.6 or 2.0. For example, by creating a wrapper that implements both
> Iterable and Iterator, we could overcome the Iterator API change as shown
> by our LazyIterableIterator which did not require any change in related
> functions. Btw, we did the same for MRv1 and Yarn by ensuring that on MRv1,
> we don't touch Yarn related APIs. Similarly on Spark, we already support
> both legacy and >=1.6 memory management. I think this kind of platform
> independence is really valuable but it obviously adds complexity.
>
> Regards,
> Matthias
>
>
> [image: Inactive hide details for Niketan Pansare---08/03/2016 05:15:21
> PM---I am in favor of having one more release against Spark 1.6]Niketan
> Pansare---08/03/2016 05:15:21 PM---I am in favor of having one more release
> against Spark 1.6. Since default scala version for Spark 1.
>
> From: Niketan Pansare/Almaden/IBM@IBMUS
> To: dev@systemml.incubator.apache.org
> 
> Date: 08/03/2016 05:15 PM
> Subject: Re: [DISCUSS] Migration to Spark 2.0.0
> --
>
>
>
> I am in favor of having one more release against Spark 1.6. Since default
> scala version for Spark 1.6 is 2.10, I recommend either having SystemML
> compiled and released with Scala 2.10 profile or having two release
> candidates.
>
> Thanks,
>
> Niketan Pansare
> IBM Almaden Research Center
> E-mail: npansar At us.ibm.com
> *http://researcher.watson.ibm.com/researcher/view.php?person=us-npansar*
> 
>
> Frederick R Reiss---08/03/2016 03:58:17 PM---While I agree that getting
> onto Spark 2.0 quickly ought to be a priority, there are existing early u
>
> From: Frederick R Reiss/Almaden/IBM@IBMUS
> To: dev@systemml.incubator.apache.org
> 
> Date: 08/03/2016 03:58 PM
> Subject: Re: [DISCUSS] Migration to Spark 2.0.0
> --
>
>
>
> While I agree that getting onto Spark 2.0 quickly ought to be a priority,
> there are existing early users of SystemML who are likely stuck on Spark
> 1.6.x for the next few months. Those users could want some of the new
> experimental features since 0.10 (specifically frames, the prototype Python
> DSL, and the new MLContext) and it would be good to have a Spark 1.6 branch
> of our version tree where we can backport the debugged versions of these
> features if needed.
>
> I would recommend that we do one more SystemML release against Spark 1.6,
> then switch the head version of SystemML over to Spark 2.0, then
> immediately perform a second SystemML release. Thoughts?
>
> Fred
>
> Deron Eriksson ---08/02/2016 12:13:07 PM---I would definitely be in favor
> of moving to Spark 2.0 as early as possible. This will allow SystemML
>
> From: Deron Eriksson  >
> To: dev@systemml.incubator.apache.org
> 
> Date: 08/02/2016 12:13 PM
> Subject: Re: [DISCUSS] Migration to Spark 2.0.0
> --
>
>
>
> I would definitely be in favor of moving to Spark 2.0 as early as possible.
> This will allow SystemML to be current with cutting edge Spark. It would be
> nice to focus our efforts on the latest Spark.
>
> Deron
>
>
> On Tue, Aug 2, 2016 at 12:05 PM,  > wrote:
>
> > I'm in favor of moving to Spark 2.0 now, meaning that our upcoming
> release
> > would include both new features and 2.0 support.  0.10 has plenty of
> > functionality for any existing 1.x users.
> >
> > -Mike
> >
> > --
> >
> > Mike Dusenberry
> > GitHub: github.com/dusenberrymw
> > LinkedIn: linkedin.com/in/mikedusenberry
> >
> > Sent from my iPhone.
> >
> >
> > > On Aug 2, 2016, at 11:44 AM, Glenn Weidner  > wrote:
> > >
> > >
> > >
> > > In the "[DISCUSS] SystemML 0.11 release" thread, native frame support
> and
> > > API updates such as new MLContext were identified as main new features
> > for
> > > the release.  In addition, support for Spark 2.0.0 was targeted.
> > > Note code changes required for Spark 2.0.0 are not backward compatible
> to
> > > earlier Spark versions (e.g., 1.6.2) so starting separate mail thread
> for

[RESULT][VOTE] Apache SystemML 0.10.0-incubating (RC2)

[Luciano Resende]

On Tue, May 31, 2016 at 10:05 PM, Luciano Resende <luckbr1...@gmail.com>
wrote:

> Please vote on releasing the following candidate as Apache SystemML
> version 0.10.0-incubating !
>
> The vote is open for at least 72 hours and will close on Saturday,
> Wednesday 25 and passes if a majority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache SystemML 0.10.0-incubating
> [ ] -1 Do not release this package because ...
>
> To learn more about Apache SystemML, please see
> http://systemml.apache.org/
>
> The tag to be voted on is v0.10.0-incubating-rc2
> (3d5f9b11741f6d6ecc6af7cbaa1069cde32be838)
>
>
> https://github.com/apache/incubator-systemml/tree/3d5f9b11741f6d6ecc6af7cbaa1069cde32be838
>
> The release artifacts can be found at :
>
>
> https://dist.apache.org/repos/dist/dev/incubator/systemml/0.10.0-incubating-rc2/
>
> The maven release artifacts, including signatures, digests, etc. can be
> found at:
>
> https://repository.apache.org/content/repositories/orgapachesystemml-1006/
>
>
> =
> == Apache Incubator release policy ==
> =
> Please find below the guide to release management during incubation:
> http://incubator.apache.org/guides/releasemanagement.html
>
> ===
> == How can I help test this release? ==
> ===
> If you are a SystemML user, you can help us test this release by taking an
> existing Algorithm or workload and running on this release candidate, then
> reporting any regressions.
>
> 
> == What justifies a -1 vote for this release? ==
> 
> -1 votes should only occur for significant stop-ship bugs or legal related
> issues (e.g. wrong license, missing header files, etc). Minor bugs or
> regressions should not block this release.
>


Vote passed with 10 +1 from
Matthias Boehm
Shirish Tatikonda
Arvind Surve
Niketan Pansare
Glenn Weidner
Berthold Reinwald
Frederick Reiss
Deron Eriksson
Mike Dusenberry
Luciano Resende

Tatsuya Nishiyama (non-binding)

Thank you all

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [VOTE] Apache SystemML 0.10.0-incubating (RC2)

[Luciano Resende]

Off course, my +1.

On Tue, May 31, 2016 at 10:05 PM, Luciano Resende <luckbr1...@gmail.com>
wrote:

> Please vote on releasing the following candidate as Apache SystemML
> version 0.10.0-incubating !
>
> The vote is open for at least 72 hours and will close on Saturday,
> Wednesday 25 and passes if a majority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache SystemML 0.10.0-incubating
> [ ] -1 Do not release this package because ...
>
> To learn more about Apache SystemML, please see
> http://systemml.apache.org/
>
> The tag to be voted on is v0.10.0-incubating-rc2
> (3d5f9b11741f6d6ecc6af7cbaa1069cde32be838)
>
>
> https://github.com/apache/incubator-systemml/tree/3d5f9b11741f6d6ecc6af7cbaa1069cde32be838
>
> The release artifacts can be found at :
>
>
> https://dist.apache.org/repos/dist/dev/incubator/systemml/0.10.0-incubating-rc2/
>
> The maven release artifacts, including signatures, digests, etc. can be
> found at:
>
> https://repository.apache.org/content/repositories/orgapachesystemml-1006/
>
>
> =
> == Apache Incubator release policy ==
> =
> Please find below the guide to release management during incubation:
> http://incubator.apache.org/guides/releasemanagement.html
>
> ===
> == How can I help test this release? ==
> ===
> If you are a SystemML user, you can help us test this release by taking an
> existing Algorithm or workload and running on this release candidate, then
> reporting any regressions.
>
> 
> == What justifies a -1 vote for this release? ==
> 
> -1 votes should only occur for significant stop-ship bugs or legal related
> issues (e.g. wrong license, missing header files, etc). Minor bugs or
> regressions should not block this release.
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

[VOTE] Apache SystemML 0.10.0-incubating (RC2)

[Luciano Resende]

Please vote on releasing the following candidate as Apache SystemML version
0.10.0-incubating !

The vote is open for at least 72 hours and will close on Saturday,
Wednesday 25 and passes if a majority of at least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache SystemML 0.10.0-incubating
[ ] -1 Do not release this package because ...

To learn more about Apache SystemML, please see http://systemml.apache.org/

The tag to be voted on is v0.10.0-incubating-rc2
(3d5f9b11741f6d6ecc6af7cbaa1069cde32be838)

https://github.com/apache/incubator-systemml/tree/3d5f9b11741f6d6ecc6af7cbaa1069cde32be838

The release artifacts can be found at :

https://dist.apache.org/repos/dist/dev/incubator/systemml/0.10.0-incubating-rc2/

The maven release artifacts, including signatures, digests, etc. can be
found at:

https://repository.apache.org/content/repositories/orgapachesystemml-1006/


=
== Apache Incubator release policy ==
=
Please find below the guide to release management during incubation:
http://incubator.apache.org/guides/releasemanagement.html

===
== How can I help test this release? ==
===
If you are a SystemML user, you can help us test this release by taking an
existing Algorithm or workload and running on this release candidate, then
reporting any regressions.


== What justifies a -1 vote for this release? ==

-1 votes should only occur for significant stop-ship bugs or legal related
issues (e.g. wrong license, missing header files, etc). Minor bugs or
regressions should not block this release.

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [VOTE] Apache SystemML 0.10.0-incubating (RC1)

[Luciano Resende]

On Fri, May 20, 2016 at 10:45 PM, Luciano Resende <luckbr1...@gmail.com>
wrote:

> Please vote on releasing the following candidate as Apache SystemML
> version 0.10.0-incubating !
>
> The vote is open for at least 72 hours and will close on Saturday,
> Wednesday 25 and passes if a majority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache SystemML 0.10.0-incubating
> [ ] -1 Do not release this package because ...
>
> To learn more about Apache SystemML, please see
> http://systemml.apache.org/
>
> The tag to be voted on is v0.10.0-incubating-rc1
> (ddf0e0941afe5d9c2cc7c574a6983aadd98c1fc3)
>
>
> https://github.com/apache/incubator-systemml/tree/ddf0e0941afe5d9c2cc7c574a6983aadd98c1fc3
>
> The release artifacts can be found at :
>
>
> https://dist.apache.org/repos/dist/dev/incubator/systemml/0.10.0-incubating-rc1/
>
>
> The maven release artifacts, including signatures, digests, etc. can be
> found at:
>
> https://repository.apache.org/content/repositories/orgapachesystemml-1005/
>
>
> =
> == Apache Incubator release policy ==
> =
> Please find below the guide to release management during incubation:
> http://incubator.apache.org/guides/releasemanagement.html
>
> ===
> == How can I help test this release? ==
> ===
> If you are a SystemML user, you can help us test this release by taking an
> existing Algorithm or workload and running on this release candidate, then
> reporting any regressions.
>
> 
> == What justifies a -1 vote for this release? ==
> 
> -1 votes should only occur for significant stop-ship bugs or legal related
> issues (e.g. wrong license, missing header files, etc). Minor bugs or
> regressions should not block this release.
>
>
Vote passed with +1 from :
Matthias Boehm,
Mike Dusenberry,
Luciano Resende,
Deron Eriksson.


I will send this to IPMC now, thanks.

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: missing release candidate checksums?

[Luciano Resende]

Thanks, they should all be on the staging site now.

On Wed, May 25, 2016 at 11:10 AM, Deron Eriksson <deroneriks...@gmail.com>
wrote:

> and maybe:
> ? systemml-0.10.0-incubating.pom.md5
>
> Also, the previous release had sha1 checksums. Do we need those too or is
> that overkill?
>
> Deron
>
>
> On Wed, May 25, 2016 at 10:16 AM, Luciano Resende <luckbr1...@gmail.com>
> wrote:
>
> > On Tue, May 24, 2016 at 5:20 PM, Deron Eriksson <deroneriks...@gmail.com
> >
> > wrote:
> >
> > > Hi,
> > >
> > > I noticed that not all the artifacts at
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/systemml/0.10.0-incubating-rc1/
> > > have md5 checksums.
> > >
> > > Also, the previous release (see
> > >
> > >
> >
> https://repo1.maven.org/maven2/org/apache/systemml/systemml/0.9.0-incubating/
> > > )
> > > featured sha1 checksums but the current release candidate doesn't have
> > sha1
> > > checksums.
> > >
> > > Deron
> > >
> >
> >
> > Are these the only ones missing ?
> >
> > ?   systemml-0.10.0-incubating-inmemory.jar.md5
> > ?   systemml-0.10.0-incubating-javadoc.jar.md5
> > ?   systemml-0.10.0-incubating-sources.jar.md5
> > ?   systemml-0.10.0-incubating-standalone.jar.md5
> > ?   systemml-0.10.0-incubating.jar.md5
> >
> >
> > --
> > Luciano Resende
> > http://twitter.com/lresende1975
> > http://lresende.blogspot.com/
> >
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Discussion on GPU backend

[Luciano Resende]

On Wed, May 25, 2016 at 6:03 AM, Berthold Reinwald <reinw...@us.ibm.com>
wrote:

> the discussion is less about (1), (2), or (3). As practiced so far, (3) is
> the way to go.
>
> The question is about (A) or (B). Curious was the Apache suggested
> practice is.
>
>
Apache is key on fostering open collaboration, so specifically about
branching, having a SystemML branch that is used for
collaboration/experimentation is probably preferable, as it gives
visibility to others on the community, enables iterative development trough
review of small patches, while shield the trunk of issues these experiments
can cause.

I would just recommend to avoid making the branch stale, and keep rebasing
it with latest master, which will make integration much easier in the
future.



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: branch for 0.10?

[Luciano Resende]

Do you have any specific thing to fix on 0.10 rc ? Otherwise I was going to
create the branch when we needed it


On Mon, May 23, 2016 at 10:31 AM, Deron Eriksson <deroneriks...@gmail.com>
wrote:

> Should there be a branch-0.10 on GitHub? The current pom.xml on master is
> referring to the 0.11.0-SNAPSHOT.
>
> Deron
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Properly closing JIRAs

[Luciano Resende]

Could people help verify that all closed JIRAs have proper affected
version, you can find some of those at:

https://issues.apache.org/jira/browse/SYSTEMML-354?jql=project%20%3D%20SYSTEMML%20AND%20status%20in%20%28Resolved%2C%20Closed%29%20AND%20fixVersion%20%3D%20EMPTY

Also, in the future, would be good to set these when closing the jiras.

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

[VOTE] Apache SystemML 0.10.0-incubating (RC1)

[Luciano Resende]

Please vote on releasing the following candidate as Apache SystemML version
0.10.0-incubating !

The vote is open for at least 72 hours and will close on Saturday,
Wednesday 25 and passes if a majority of at least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache SystemML 0.10.0-incubating
[ ] -1 Do not release this package because ...

To learn more about Apache SystemML, please see http://systemml.apache.org/

The tag to be voted on is v0.10.0-incubating-rc1
(ddf0e0941afe5d9c2cc7c574a6983aadd98c1fc3)

https://github.com/apache/incubator-systemml/tree/ddf0e0941afe5d9c2cc7c574a6983aadd98c1fc3

The release artifacts can be found at :

https://dist.apache.org/repos/dist/dev/incubator/systemml/0.10.0-incubating-rc1/

The maven release artifacts, including signatures, digests, etc. can be
found at:

https://repository.apache.org/content/repositories/orgapachesystemml-1005/


=
== Apache Incubator release policy ==
=
Please find below the guide to release management during incubation:
http://incubator.apache.org/guides/releasemanagement.html

===
== How can I help test this release? ==
===
If you are a SystemML user, you can help us test this release by taking an
existing Algorithm or workload and running on this release candidate, then
reporting any regressions.


== What justifies a -1 vote for this release? ==

-1 votes should only occur for significant stop-ship bugs or legal related
issues (e.g. wrong license, missing header files, etc). Minor bugs or
regressions should not block this release.


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Starting a SystemML 0.10 release?

[Luciano Resende]

Ok, thanks for letting me know... I was about to cut a RC1, so I will wait
a bit more...

On Fri, May 20, 2016 at 2:54 PM, Deron Eriksson <deroneriks...@gmail.com>
wrote:

> BTW, I am investigating. I believe the issue is caused because of my update
> to add an assembly (for the proper LICENSE and NOTICE) for the main jar.
>
> Deron
>
>
> On Fri, May 20, 2016 at 2:24 PM, Deron Eriksson <deroneriks...@gmail.com>
> wrote:
>
> > Hi,
> >
> > Luciano, before starting the RC, I think I found an issue. The current
> > SystemML.jar apparently doesn't specify a main class in the MANIFEST.MF
> > (which it did in the previous 0.9.0-incubating release).  Therefore
> > something like:
> >$SPARK_HOME/bin/spark-submit SystemML.jar -s "print('hello world');"
> > -exec hybrid_spark
> > will generate the following error rather than executing:
> >   Error: No main class set in JAR; please specify one with --class
> >
> > Deron
> >
> >
> > On Thu, May 19, 2016 at 3:22 PM, Deron Eriksson <deroneriks...@gmail.com
> >
> > wrote:
> >
> >> Hi,
> >>
> >> PR162 and PR167 have been merged. Thank you Glenn for all the help
> >> testing PR167.
> >>
> >> Deron
> >>
> >>
> >> On Thu, May 19, 2016 at 12:43 AM, Matthias Boehm <mbo...@us.ibm.com>
> >> wrote:
> >>
> >>> sounds good to me - in addition to PR167, I'd also like to get PR162
> >>> into this release. Furthermore, it would be good to run our full
> >>> performance testsuite (at least up to 80GB) but this could be done on
> the
> >>> RC too. Thanks guys for taking care of the release again.
> >>>
> >>> Regards,
> >>> Matthias
> >>>
> >>>
> >>> [image: Inactive hide details for Luciano Resende ---05/18/2016
> 06:06:46
> >>> PM---On Wed, May 18, 2016 at 5:49 PM, Deron Eriksson <deroneri]Luciano
> >>> Resende ---05/18/2016 06:06:46 PM---On Wed, May 18, 2016 at 5:49 PM,
> Deron
> >>> Eriksson <deroneriks...@gmail.com> wrote:
> >>>
> >>> From: Luciano Resende <luckbr1...@gmail.com>
> >>> To: dev@systemml.incubator.apache.org
> >>> Date: 05/18/2016 06:06 PM
> >>> Subject: Re: Starting a SystemML 0.10 release?
> >>> --
> >>>
> >>>
> >>>
> >>> On Wed, May 18, 2016 at 5:49 PM, Deron Eriksson <
> deroneriks...@gmail.com
> >>> >
> >>> wrote:
> >>>
> >>> > Hi,
> >>> >
> >>> > I've looked over all the release packages and the NOTICE and LICENSES
> >>> are
> >>> > looking much better. I believe we have addressed all of the issues
> >>> brought
> >>> > up during the 0.9 release and have fixed many additional issues.
> >>> >
> >>>
> >>> Great, thanks for helping here.
> >>>
> >>>
> >>> >
> >>> > Are we about ready for our next release, 0.10? I believe it would be
> >>> nice
> >>> > for PR167 (https://github.com/apache/incubator-systemml/pull/167) to
> >>> be
> >>> > included since it updates the dml script packaging. Should any other
> >>> > updates be included? Does anyone have any additional concerns?
> >>> >
> >>> >
> >>> Please let me know when this is in then.
> >>>
> >>>
> >>> > Luciano, would you be available as RM for this SystemML release?
> >>> >
> >>>
> >>> Sure.
> >>>
> >>>
> >>> >
> >>> > Deron
> >>> >
> >>>
> >>>
> >>>
> >>> --
> >>> Luciano Resende
> >>> http://twitter.com/lresende1975
> >>> http://lresende.blogspot.com/
> >>>
> >>>
> >>>
> >>
> >
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Starting a SystemML 0.10 release?

[Luciano Resende]

On Wed, May 18, 2016 at 5:49 PM, Deron Eriksson <deroneriks...@gmail.com>
wrote:

> Hi,
>
> I've looked over all the release packages and the NOTICE and LICENSES are
> looking much better. I believe we have addressed all of the issues brought
> up during the 0.9 release and have fixed many additional issues.
>

Great, thanks for helping here.


>
> Are we about ready for our next release, 0.10? I believe it would be nice
> for PR167 (https://github.com/apache/incubator-systemml/pull/167) to be
> included since it updates the dml script packaging. Should any other
> updates be included? Does anyone have any additional concerns?
>
>
Please let me know when this is in then.


> Luciano, would you be available as RM for this SystemML release?
>

Sure.


>
> Deron
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

ALS Algorithm

[Luciano Resende]

I was playing with the ALS algorithm (scripts/algorithms/ALS-CG.dml) and
was trying to update it to track overall losses, but I was always getting
IndexOutOfBounds. After some investigation I noticed that we define
max_iter but the code is actually as.integer(it/2) < max_iter which always
make it runs max_iter * 2.

Is there any reason for this behavior ? Otherwise let me know and I can
create a jira/fix.

Thanks

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Discussion SYSTEMML-593 MLContext Resign

[Luciano Resende]

On Sat, Apr 2, 2016 at 9:34 PM, Matthias Boehm <mbo...@us.ibm.com> wrote:

>
>
> thanks Deron for initiating the discussion around the rework of our
> MLContext API (https://issues.apache.org/jira/browse/SYSTEMML-593). Here
> are a couple of thoughts:
>
> (1) Simplicity: Given that the primary usecase of MLContext calls a script
> exactly once, I'm wondering if the separation into Script, ScriptFactory,
> ScriptExecutor and MLContext adds unnecessary complexity by requiring more
> code to setup. It would be great to see old vs new examples side by side.
> Also rather than introducing another exception class, couldn't we just
> reuse DMLException by making it an uncaught exception?
>

Simplicity and easy of use will, in my view, dictate use adoption. One way
I usually do to accomplish this is to start by building an app or test
scenario and use that to model the user experience when using the APIs.
This might help identify how many steps the user needs to handle before
actually using the api (e.g. Script, ScriptFactory, etc) and if those steps
are really necessary... But, to be successful with this approach, you
really need to come with a clean mind, and really think as a user trying to
use the API.

Having said that, sometimes we do need a fine grained api, but sometimes
that might be used internally (private apis) and be exposed to the user
with a more coarse grained api that hides much of the details and expose a
simple programming model to the user.

Also, I like the option to have a fluent API, which makes the code more
readable and easy to use.

https://en.wikipedia.org/wiki/Fluent_interface#Java


>
> (2) Compilation: ScriptExecutor would also be yet another replicate of our
> compilation chain (beside DMLScript, Debugger, JMLC, MLContext). Please,
> keep in mind that we are about to consolidate this, centralizing these
> calls via a configurable compilation chain because it really becomes a
> maintenance nightmare (as recently seen when we reworked our thread-local
> configuration management).
>
> (3) Data Representation / Converters: Making data conversions and
> input/output handling easier is certainly useful. However, isn't this new
> class hierarchy redundant to our already existing hierarchy of Data,
> MatrixObject, FrameObject, and ScalarObject?
>

Is there a way to hide some of the input/output registration calls by some
convention over api calls ?


>
> (4) Consolidating MLContext and JMLC: This is a good idea since MLContext
> is anyway "derived" from JMLC and both rely on the same concepts for
> input/output handling and program modification (see JMLCUtils). Down the
> road I would like to see a convergence to something like Script and
> PreparedScript in the spirit of JDBC's Statement and PreparedStatement
> (btw, that's how we created JMLC). Let's keep in mind that there are
> already a number of users working against both MLContext and JMLC, so we
> should support them separately until our major 1.0 release.
>
>
> Regards,
> Matthias
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Creating a new SystemML maintenance release: 0.9.1

[Luciano Resende]

bator-systemml/commit/2d753e60151095f24b76acd81226a88f8a25f081>
> *
> https://github.com/apache/incubator-systemml/commit/71a3fde27f800576d746c50ae9694aad75276b4e
> <https://github.com/apache/incubator-systemml/commit/71a3fde27f800576d746c50ae9694aad75276b4e>
> *
> https://github.com/apache/incubator-systemml/commit/61183f24ba2a9c3cd185ad0c579debf508c07ea8
> <https://github.com/apache/incubator-systemml/commit/61183f24ba2a9c3cd185ad0c579debf508c07ea8>
>
>
> Regards,
> Matthias
>
> [image: Inactive hide details for Luciano Resende ---03/18/2016 03:02:39
> PM---On Fri, Mar 18, 2016 at 2:45 PM, Frederick R Reiss <frrei]Luciano
> Resende ---03/18/2016 03:02:39 PM---On Fri, Mar 18, 2016 at 2:45 PM,
> Frederick R Reiss <frre...@us.ibm.com> wrote:
>
> From: Luciano Resende <luckbr1...@gmail.com>
> To: dev@systemml.incubator.apache.org
> Date: 03/18/2016 03:02 PM
> Subject: Re: Creating a new SystemML maintenance release: 0.9.1
> --
>
>
>
> On Fri, Mar 18, 2016 at 2:45 PM, Frederick R Reiss <frre...@us.ibm.com>
> wrote:
>
> >
> > Hi all,
> >
> > Since we have fixed a number of issues since the 0.9.0 release, it's
> about
> > time to do a maintenance release of SystemML. As a reminder, the release
> > process goes as follows:
> >
> > Step 1: Identify the full set of fixes to be backported into the 0.9.x
> > branch.
> >
> > Step 2: Backport the fixes and their associated regression tests to the
> > 0.9.x branch.
> >
> > Step 3: Run all automated regression tests on the 0.9.x branch.
> >
> > Step 4: Use the script dev/release/release-build.sh to create release
> > packages.
> >
> > Step 5: Post the release packages on repository.apache.org.
> >
> > Step 6: Simultaneously hold a vote on the release and manually test the
> > release.
> >
> > Step 7: Make the release public.
> >
> >
> Note that you need to get the released approved in the IPMC before making
> it public. This means another vote on general@a.o
>
>
>
> > We are currently at step 1. Please reply to this thread with (a) JIRA IDs
> > of resolved issues that you believe should be in the mainentance release
> > and (b) JIRA ids of open issues that must be fixed before we can do the
> > maintenance release.
> >
> > Fred
> >
>
>
>
> --
> Luciano Resende
> http://people.apache.org/~lresende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>
>
>


-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Creating a new SystemML maintenance release: 0.9.1

[Luciano Resende]

On Fri, Mar 18, 2016 at 2:45 PM, Frederick R Reiss <frre...@us.ibm.com>
wrote:

>
> Hi all,
>
> Since we have fixed a number of issues since the 0.9.0 release, it's about
> time to do a maintenance release of SystemML. As a reminder, the release
> process goes as follows:
>
> Step 1: Identify the full set of fixes to be backported into the 0.9.x
> branch.
>
> Step 2: Backport the fixes and their associated regression tests to the
> 0.9.x branch.
>
> Step 3: Run all automated regression tests on the 0.9.x branch.
>
> Step 4: Use the script dev/release/release-build.sh to create release
> packages.
>
> Step 5: Post the release packages on repository.apache.org.
>
> Step 6: Simultaneously hold a vote on the release and manually test the
> release.
>
> Step 7: Make the release public.
>
>
Note that you need to get the released approved in the IPMC before making
it public. This means another vote on general@a.o



> We are currently at step 1. Please reply to this thread with (a) JIRA IDs
> of resolved issues that you believe should be in the mainentance release
> and (b) JIRA ids of open issues that must be fixed before we can do the
> maintenance release.
>
> Fred
>



-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: SystemML Notebook docker image

[Luciano Resende]

Sourav,

To make things simple, if you could create a jira and attach the notebook,
I will handle the rest.

On Mon, Feb 15, 2016 at 11:54 AM, Sourav Mazumder <
sourav.mazumde...@gmail.com> wrote:

> Hi Deron,
>
> I tried following your instruction. But while pushing my changes back I'm
> getting the error saying
>
> git push --set-upstream origin systemml-zeppelin-spark-example
> Username for 'https://github.com': sourav.mazumde...@gmail.com
> Password for 'https://sourav.mazumde...@gmail.com@github.com
> remote: Permission to apache/incubator-systemml.git denied to
> sourav-mazumder.
>
> Alternatively if someone can create a folder for my notebook ("2BCHR4T1Q")
> under
> incubator-systemml <https://github.com/sourav-mazumder/incubator-systemml
> >/
> samples
> <https://github.com/sourav-mazumder/incubator-systemml/tree/master/samples
> >/
> zeppelin-notebooks
> <
> https://github.com/sourav-mazumder/incubator-systemml/tree/master/samples/zeppelin-notebooks
> >*
> then I can add a file under that folder without the need of pushing the
> branch back. Right now main problem in this approach is that I'm not able
> to create a new folder under *
> incubator-systemml <https://github.com/sourav-mazumder/incubator-systemml
> >/
> samples
> <https://github.com/sourav-mazumder/incubator-systemml/tree/master/samples
> >/
> zeppelin-notebooks
> <
> https://github.com/sourav-mazumder/incubator-systemml/tree/master/samples/zeppelin-notebooks
> >
> /.
>
>
> Regards,
> Sourav
>
> On Fri, Feb 12, 2016 at 10:19 AM, Deron Eriksson <deroneriks...@gmail.com>
> wrote:
>
> > Hi Sourav,
> >
> > I recently created a "Contributing to SystemML" document that describes
> > working with Git (
> >
> >
> http://apache.github.io/incubator-systemml/contributing-to-systemml.html#systemml-on-github
> > ).
> > The workflow described in the document may help you out.
> >
> > Also, in case it helps, I found the open-source Pro Git book to be very
> > useful when I started working with Git (https://progit.org/).
> >
> > Luciano recently created a samples/zeppelin-notebooks directory, so that
> is
> > the place to put your example notebook.
> >
> > By the way, thank you for your great feedback with regards to SystemML!
> It
> > was detailed and excellent.
> >
> > Deron
> >
> >
> >
> > On Fri, Feb 12, 2016 at 10:07 AM, Luciano Resende <luckbr1...@gmail.com>
> > wrote:
> >
> > > You need to git add the folder you are trying to submit as a PR
> > > Something like the steps below
> > >
> > > cd samples/zeppelin-notebooks
> > > mkdir foo
> > > cp foo.json foo
> > > git add foo  -> this will add the folder and it's contents
> > > git commit -a -m"Some message"
> > > git push origin branch-name
> > >
> > >
> > >
> > >
> > > On Fri, Feb 12, 2016 at 9:27 AM, Sourav Mazumder <
> > > sourav.mazumde...@gmail.com> wrote:
> > >
> > > > Hi Deron,
> > > >
> > > > I created a Pull request (#69) for the same.
> > > >
> > > > But I'm little lost how do I add a new folder and within that the
> json
> > > file
> > > > for the notebook I want to upload. I tried creating a new folder
> under
> > > > incubator-systemml <https://github.com/apache/incubator-systemml
> > > >/samples
> > > > <https://github.com/apache/incubator-systemml/tree/master/samples>/
> > > > *zeppelin-notebooks*/ in my branch but was not able to.
> > > >
> > > > When I tried the url you provided I found that it lands to a
> discussion
> > > > thread..
> > > >
> > > > I'm little new to github. Please bear with my ignorance.
> > > >
> > > > Regards,
> > > > Sourav
> > > >
> > > > On Sat, Feb 6, 2016 at 11:55 AM, Luciano Resende <
> luckbr1...@gmail.com
> > >
> > > > wrote:
> > > >
> > > > > On Fri, Feb 5, 2016 at 5:26 PM, Sourav Mazumder <
> > > > > sourav.mazumde...@gmail.com
> > > > > > wrote:
> > > > >
> > > > > > Hi Deron,
> > > > > >
> > > > > > I can surely share that. Can I upload it somewhere in the
> > SystemML's
> > > > > site ?
> > > > > >
> > > > >
> > > > > I have created a place in the source code for sample notebooks
> > > > >
> > > > >
> > >
> https://www.mail-archive.com/general@incubator.apache.org/msg53110.html
> > > > >
> > > > > Please add a pull request with your notebook when you have a
> chance,
> > > > others
> > > > > feel free to contribute other examples as well.
> > > > >
> > > > > --
> > > > > Luciano Resende
> > > > > http://people.apache.org/~lresende
> > > > > http://twitter.com/lresende1975
> > > > > http://lresende.blogspot.com/
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Luciano Resende
> > > http://people.apache.org/~lresende
> > > http://twitter.com/lresende1975
> > > http://lresende.blogspot.com/
> > >
> >
>



-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Fwd: Google Summer of Code 2016 is coming

[Luciano Resende]

Please see information about Google Summer of Code program that Apache has
been participating every year. I would encourage folks to volunteer as
mentors and start selecting ideas into jira asap to start attracting
students interest.

-- Forwarded message --
From: Ulrich Stärk <u...@apache.org>
Date: Wed, Feb 10, 2016 at 12:16 PM
Subject: Google Summer of Code 2016 is coming
To: ment...@community.apache.org


Hello PMCs (incubator Mentors, please forward this email to your podlings),

Google Summer of Code [1] is a program sponsored by Google allowing
students to spend their summer
working on open source software. Students will receive stipends for
developing open source software
full-time for three months. Projects will provide mentoring and project
ideas, and in return have
the chance to get new code developed and - most importantly - to identify
and bring in new committers.

The ASF will apply as a participating organization meaning individual
projects don't have to apply
separately.

If you want to participate with your project we ask you to do the following
things as soon as
possible but by no later than 2016-02-19:

1. understand what it means to be a mentor [2].

2. record your project ideas.

Just create issues in JIRA, label them with gsoc2016, and they will show up
at [3]. Please be as
specific as possible when describing your idea. Include the programming
language, the tools and
skills required, but try not to scare potential students away. They are
supposed to learn what's
required before the program starts.

Use labels, e.g. for the programming language (java, c, c++, erlang,
python, brainfuck, ...) or
technology area (cloud, xml, web, foo, bar, ...) and record them at [5].

Please use the COMDEV JIRA project for recording your ideas if your project
doesn't use JIRA (e.g.
httpd, ooo). Contact d...@community.apache.org if you need assistance.

[4] contains some additional information (will be updated for 2016 shortly).

3. subscribe to ment...@community.apache.org; restricted to potential
mentors, meant to be used as a
private list - general discussions on the public d...@community.apache.org
list as much as possible
please). Use a recognized address when subscribing (@apache.org or one of
your alias addresses on
record).

Note that the ASF isn't accepted as a participating organization yet,
nevertheless you *have to*
start recording your ideas now or we will not get accepted.

Over the years we were able to complete hundreds of projects successfully.
Some of our prior
students are active contributors now! Let's make this year a success again!

Cheers,

Uli


[1] https://summerofcode.withgoogle.com/
[2] http://community.apache.org/guide-to-being-a-mentor.html
[3] http://s.apache.org/gsoc2016ideas
[4] http://community.apache.org/gsoc.html




-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Project folder structure

[Luciano Resende]

I would like to propose we follow more closely the project structure Spark
is using, where we clearly define a folder for samples, another for dev
utilities, etc instead of getting everything buried  inside the /scripts
folder where it might be confusing/hard for users to find what they are
looking for.

Also, I would like to suggest creating a README.md on some of these folders
(e.g. samples) that describes what the contents of the folder are.

Thoughts ?

-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Project folder structure

[Luciano Resende]

On Tue, Feb 9, 2016 at 12:43 PM, Matthias Boehm <mbo...@us.ibm.com> wrote:

> -1
>
> I don't see a compelling argument for this unnecessary change to a more
> complex project structure just to follow Spark which is not directly
> comparable - both in project size and content. For example, our algorithms
> are at the same time a library of algorithms as well as samples for how to
> write new algorithms. From my perspective, our major goal should be
> "simplicity via minimality" not "simplicity via common structure" because
> the latter would always require us to stay in sync.
>
> Regards,
> Matthias
>
>
I just don't see why it would make sense to add "notebooks" and "bash
release scripts" all inside scripts which to me is currently filled with ML
Algorithms in different stages or for different purposes.

I am not keen on "simplicity via minimality" neither "simplicity via common
structure"... I am keen on what makes sense I (and thus drive adoption) for
someone that is first trying to look trough SystemML code, particularly
folks that are already used to some best practices or with some other
projects on the same area.

-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Project folder structure

[Luciano Resende]

On Tue, Feb 9, 2016 at 1:25 PM, Niketan Pansare <npan...@us.ibm.com> wrote:

> -1 for changing the folder structure. I don't think the current setup is
> confusing for the end user and also agree with Matthias that our project
> structure does not have to be in sync with Spark.
> +1 for having README on user-facing folders like script or samples (which
> might demo JMLC/MLContext/MLPipeline/Python MLContext).
>
>
So, you are saying that moving
https://github.com/apache/incubator-systemml/blob/master/dev/release/release-build.sh

to scripts, will be very user friendly, particularly with all other ml
algorithms already there ?


-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

SystemML Notebook docker image

[Luciano Resende]

I started experimenting with some nice ways to enable data scientists to
get started with SystemML with the minimum setup and a pleasant user
experience.

Following the guide published in the SystemML project documentation page
[1], I created a docker image containing the necessary infrastructure for
running SystemML in a cluster mode, and also installed and configured
Zeppelin with SystemML and the sample notebook available.

Please see more detailed instructions to use it at

https://github.com/lresende/docker-systemml-notebook

If people start to find this very useful we could move this to SystemML
project itself and start making more scenarios available as sample Notebooks

[1]
http://apache.github.io/incubator-systemml/spark-mlcontext-programming-guide.html#zeppelin-notebook-example---linear-regression-algorithm

[2] https://github.com/lresende/docker-systemml-notebook

-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

SystemML 0.9.0 IPMC Release Approval is underway

[Luciano Resende]

Just FYI, the IPMC release approval is underway and folks that are not
subscribed to general@a.o can follow the thread at

https://www.mail-archive.com/general@incubator.apache.org/msg53110.html

-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: February 2016 SystemML Incubator Podling Report - Draft

[Luciano Resende]

On Wed, Feb 3, 2016 at 4:08 PM, Deron Eriksson <deroneriks...@gmail.com>
wrote:

> I see you edited the report on the incubator wiki. Thank you!
>
>
I had to review as a mentor, did a quick update.


-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Release source package

[Luciano Resende]

On Wed, Jan 20, 2016 at 12:30 PM, Deron Eriksson <deroneriks...@gmail.com>
wrote:

> I have a question (mostly for Luciano).
>
> I'm examining the release candidate files to try to verify that our
> candidate files are compliant with the Apache release management policy (
> http://incubator.apache.org/guides/releasemanagement.html).
>
> I see under the Release Check List (
> http://incubator.apache.org/guides/releasemanagement.html#check-list), the
> following:
>
> "3.6 Release consists of source code only, no binaries.
> Each Apache release must contain a source package. This package may not
> contain compiled components (such as "jar" files) because compiled
> components are not open source, even if they were built from open source."
>
> Is this referring to -sources.jar or -src.tar.gz/-src.zip?
>

-src.tar.gz or -src.zip mostly


> In system-ml-0.9.0-incubating-src.tar.gz, there
> is src/test/config/hadoop_bin_windows/bin/winutils.exe. Does this need to
> be removed?


Most likely, I really would like to get us out of having this in our git
repository, particularly because of the issues mentioned above, but also
because it makes us stick to one given Hadoop build.


> Or is the "source package" referring to the -sources.jar? Since
> it says each release must contain a source package, and -sources.jar is a
> source package, I assume we are fine. Is that correct?
>
>
This should be ok...


> Deron
>

Please create a sub-task under SYSTEMML-463 to track this issue.

https://issues.apache.org/jira/browse/SYSTEMML-463


-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: SystemML Hadoop version support

[Luciano Resende]

On Wed, Jan 20, 2016 at 12:50 PM, Deron Eriksson <deroneriks...@gmail.com>
wrote:

> Does SystemML still support Hadoop 1?
>
> I see in MRConfigurationNames a static initialization block for Hadoop
> v1/v2 properties. I'd like to remove the current deprecated property
> warnings (log messages in the console) that we get with Hadoop v2.4.1 and I
> was wondering if I should add the old v1 and new v2 versions to
> MRConfigurationNames or if I can just add the new v2 versions and the v1
> versions can be removed.
>
> If we still support Hadoop v1, we might want to update the pom with
> profiles for Hadoop 1 and 2.
>
> Deron
>

Even Spark is moving away of supporting some old versions of Hadoop, etc...

I would really like us to be moving kind of together with other
dependencies, in the sense of supporting Hadoop 2.6 and up, and Spark 1.6
and maybe 1.5.2 as well.

-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [VOTE] Release SystemML 0.9-incubating (RC1)

[Luciano Resende]

This vote is canceled.

Please create tasks under the umbrela jira for us to track the issues being
raised.

https://issues.apache.org/jira/browse/SYSTEMML-463



On Wed, Jan 20, 2016 at 1:36 PM, Mike Dusenberry <dusenberr...@gmail.com>
wrote:

> Upon further review, I've found multiple issues with the "standalone"
> package that should block this release candidate.
>
>
>
>
> 1.  The "readme.txt" in the "standalone" distribution refers to a
> "jSystemML.jar" file that will be generated for the user to allow the use
> of "java -jar jSystemML.jar".  However, we do not package a single jar, and
> instead provide a "lib" folder with all dependency jars and a base SystemML
> jar named "system-ml-0.9.0-incubating.jar".  Thus, a longer Java invocation
> using the lib classpath is needed, or the provided
> "runStandaloneSystemML.sh" script is needed, with the later being the only
> obvious route for the user.  This leads us to item 2.
>
> 2.  The provided "runStandaloneSystemML.sh" is unusable due to containing
> only Windows-style carriage returns, rather than the correct Unix newline
> characters.  Thus, the script has to be edited to remove the former
> Windows-style characters and replace them with the later Unix styled ones
> before the script will run.  This will affect any Unix derivative, such as
> Linux and OS X.  Additionally, the inclusion of Windows-styled carriage
> returns in our codebase is a huge concern, aside from Windows-specific
> files such as ".bat" or ".exe" files.  I'll open a separate thread to
> discuss this, but I believe we can fix it with the addition of a Git config
> setting in the project that forces Unix-style newlines upon checkin, and
> still allows for OS-specific characters on local machines.
>
>
>
>
> Overall, the "standalone" package is broken in this release candidate, so
> we should fix that.  In general, we need to clean up the execution paths of
> SystemML anyway, but for now I say we quickly fix this issue, and then work
> on a real solution (such as the single "SystemML.jar" for all execution
> types/modes that was discussed on one of the recent PRs) for the next
> release.
>
>
>
>
>
> - Mike
>
>
>
>
> --
>
>
>
> Michael W. Dusenberry
> LinkedIn: linkedin.com/in/mikedusenberry
>
>
> GitHub: github.com/dusenberrymw
>
> On Wed, Jan 20, 2016 at 10:44 AM, Niketan Pansare <npan...@us.ibm.com>
> wrote:
>
> > +1
> > Niketan Pansare
> > IBM Almaden Research Center
> > E-mail: npansar At us.ibm.com
> > http://researcher.watson.ibm.com/researcher/view.php?person=us-npansar
> > From: dusenberr...@gmail.com
> > To:   dev@systemml.incubator.apache.org
> > Date: 01/20/2016 05:30 AM
> > Subject:  Re: [VOTE] Release SystemML 0.9-incubating (RC1)
> > +1
> > --
> > Mike Dusenberry
> > GitHub: github.com/dusenberrymw
> > LinkedIn: linkedin.com/in/mikedusenberry
> > Sent from my iPhone.
> >> On Jan 20, 2016, at 3:39 AM, Frederick R Reiss <frre...@us.ibm.com>
> > wrote:
> >>
> >>
> >> +1
> >>
> >> Sent from my iPhone
> >>
> >>>> On Jan 20, 2016, at 11:06 AM, Shirish Tatikonda
> >>> <shirish.tatiko...@gmail.com> wrote:
> >>>
> >>> +1
> >>>
> >>>
> >>>
> >>> On Tue, Jan 19, 2016 at 9:46 PM, Luciano Resende <luckbr1...@gmail.com
> >
> >>> wrote:
> >>>
> >>>> Please vote on releasing the following candidate as Apache SystemML
> >> version
> >>>> 0.9.0!
> >>>>
> >>>> The vote is open for at least 72 hours and will close on Saturday,
> >> January
> >>>> 23 and passes if a majority of at least 3 +1 PMC votes are cast.
> >>>>
> >>>> [ ] +1 Release this package as Apache SystemML 0.9.0
> >>>> [ ] -1 Do not release this package because ...
> >>>>
> >>>> To learn more about Apache SystemML, please see
> >>>> http://systemml.apache.org/
> >>>>
> >>>> The tag to be voted on is v0.9.0-rc1
> >>>> (3e7e5cf6ca697ec247a7dc4e005a7f7b1cb18856)
> >>
> >
> https://github.com/apache/incubator-systemml/tree/3e7e5cf6ca697ec247a7dc4e005a7f7b1cb18856
> >>
> >>>>
> >>>> The release files, including signatures, digests, etc. can be found
> at:
> >>
> >
> https://repository.apache.org/content/repos

Re: Workflow for assigning issues to users

[Luciano Resende]

On Mon, Jan 18, 2016 at 1:54 PM, Deron Eriksson <deroneriks...@gmail.com>
wrote:

> What is our workflow for assigning JIRA issues to users?
>
> For instance, Nakul Jindal asked in the comments to work on
> https://issues.apache.org/jira/browse/SYSTEMML-456. What's our workflow?
>
> For instance, one possible workflow:
>
> 1) User asks to work on issue.
> 2) If new user, we add user as project contributor (Contributor role).
> 3) We set user as Assignee for the issue.
> 4) User submits pull request.
> 5) Resolve and close issue.
>
> It would be good to settle on such a workflow now that our JIRA server is
> up to avoid confusion.
>
> Luciano, is there an Apache standard that we should be following?
>
> Deron
>


There is no Apache standard, each project can discuss their preference.


-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Starting a SystemML 0.9 release

[Luciano Resende]

On Sun, Jan 17, 2016 at 8:41 PM, Matthias Boehm <mbo...@us.ibm.com> wrote:

> In my opinion, our release process takes too long but that's ok for the
> second release - we just need to improve upon it. Instead of waiting for
> https://issues.apache.org/jira/browse/INFRA-11084,
> <https://issues.apache.org/jira/browse/INFRA-11084> I would suggest to
> create a branch for 0.9 and move on. This would also be useful for pure
> maintenance releases we want to do. So maybe we could make this a general
> policy. Any objections?
>
> Regards,
> Matthias
>
>
Most of the wait time on the release is either waiting for other jiras to
get fixed or for infra issues, as the release process is very quick.
Anyway, branch 0.9 created

https://git-wip-us.apache.org/repos/asf?p=incubator-systemml.git


-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: SystemML JIRA Site Is Live!

[Luciano Resende]

-1 for disabling it all

With this, we get no notification weather a jira is created, etc. An
example is that I created SYSTEMML-462 and the list archives has no
indication of the jira created.

We should get some indication of jira workflow on our mailing lists. If
people does not want to flood the dev list with this, I can create a issues
mailing list and folks can subscribe to that list as appropriate.



On Wed, Jan 13, 2016 at 7:36 AM, Deron Eriksson <deroneriks...@gmail.com>
wrote:

> The "Single Email Address (dev@systemml.incubator.apache.org)" entries
> have
> been removed from the notifications scheme. See
> https://issues.apache.org/jira/browse/INFRA-11071
>
> Deron
>
>
> On Tue, Jan 12, 2016 at 10:52 PM, Deron Eriksson <deroneriks...@gmail.com>
> wrote:
>
> > Sorry for the spam. I just noticed that
> > https://issues.apache.org/jira/browse/INFRA-10714 has Resolution "Fixed"
> > and Status "Closed". I will add a comment to 10714 and then file a new
> JIRA
> > to remove the email notifications to the dev list.
> >
> > Deron
> >
> > On Tue, Jan 12, 2016 at 10:40 PM, Deron Eriksson <
> deroneriks...@gmail.com>
> > wrote:
> >
> >> I guess my preferred course of action is to:
> >> (1) Remove "Single Email Address" entries from scheme.
> >> (2) Close 10714!
> >> (3) In the future, if the notification scheme doesn't meet our needs,
> >> file a new INFRA ticket to update notification scheme.
> >>
> >>
> >>
> >> On Tue, Jan 12, 2016 at 10:22 PM, Deron Eriksson <
> deroneriks...@gmail.com
> >> > wrote:
> >>
> >>> I would be in favor of not having these notifications going to the dev
> >>> list. I definitely want to be notified if I am watching an issue, or
> am a
> >>> reporter, or am the assignee, but I would prefer these to go to my
> personal
> >>> email rather than the dev list. I was very happy with the old scheme
> with
> >>> regards to the notifications. I posted the old scheme to the
> INFRA-10714
> >>> comments.
> >>>
> >>> Sounds like there is a general consensus regarding the notifications.
> 15
> >>> minutes ago I added a comment on
> >>> https://issues.apache.org/jira/browse/INFRA-10714 to remove all the
> "Single
> >>> Email Address" entries, since I was concerned about too many
> notifications
> >>> going to the email list, and with time zone delays I thought it was a
> good
> >>> idea to get things rolling as soon as possible. We can add further
> comments
> >>> if they are required.
> >>>
> >>> Deron
> >>>
> >>>
> >>>
> >>> On Tue, Jan 12, 2016 at 10:04 PM, Matthias Boehm <mbo...@us.ibm.com>
> >>> wrote:
> >>>
> >>>> sure, let's agree on the scheme. I'm strongly in favor of removing the
> >>>> dev list from this scheme (yes, that would affect all the "Single
> Email
> >>>> Address" entries) because it would create a lot of traffic and we
> don't
> >>>> want every description update persistent in our mail archive. Thanks.
> >>>>
> >>>> Regards,
> >>>> Matthias
> >>>>
> >>>> [image: Inactive hide details for Luciano Resende ---01/12/2016
> >>>> 09:55:16 PM---Can we have consensus on what we want first ? Why
> notific]Luciano
> >>>> Resende ---01/12/2016 09:55:16 PM---Can we have consensus on what we
> want
> >>>> first ? Why notification updates are an issue ?
> >>>>
> >>>> From: Luciano Resende <luckbr1...@gmail.com>
> >>>> To: dev@systemml.incubator.apache.org
> >>>> Date: 01/12/2016 09:55 PM
> >>>> Subject: Re: SystemML JIRA Site Is Live!
> >>>> --
> >>>>
> >>>>
> >>>>
> >>>> Can we have consensus on what we want first ?
> >>>>
> >>>> Why notification updates are an issue ?
> >>>> Should we disable or use a different list (e.g. issues@s.a.o) to
> >>>> receive
> >>>> these notes ?
> >>>> If we disable, how do you get to know there there is updates ?
> >>>>
> >>>> On Tue, Jan 12, 2016 at 9:50 PM, Deron Eriksson <
> >>>> deroneriks...@gmail.com>
> >>>> wrote:
> >>>>
> >

Re: SystemML Daily Test Builds

[Luciano Resende]

Should we enable notifications sent to dev list in case of failures ?


On Wed, Jan 13, 2016 at 11:21 AM, Deron Eriksson <deroneriks...@gmail.com>
wrote:

> This is very useful. Thank you Alex!
>
> Deron
>
>
> On Wed, Jan 13, 2016 at 11:16 AM, Mike Dusenberry <dusenberr...@gmail.com>
> wrote:
>
> > Hi all,
> >
> > Just FYI, Alex at the STC set up some daily test builds for us on Jenkins
> > that will run every day at ~12 AM and ~12 PM.  The tests will run against
> > the current master branch at that moment, and will list all commits added
> > since the previous build.  Once everything looks okay, one possibility
> > would be to have Jenkins email the dev list on any failures.  The builds
> > can be found here: [
> > https://sparktc.ibmcloud.com/jenkins/job/SystemML-DailyTest/].
> >
> > Thanks to Alex!
> >
> >
> > -Mike
> > --
> > Mike Dusenberry
> > GitHub: github.com/dusenberrymw
> > LinkedIn: linkedin.com/in/mikedusenberry
> >
> > Sent from my iPhone.
> >
>



-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: SystemML JIRA Site Is Live!

[Luciano Resende]

Can we have consensus on what we want first ?

Why notification updates are an issue ?
Should we disable or use a different list (e.g. issues@s.a.o) to receive
these notes ?
If we disable, how do you get to know there there is updates ?

On Tue, Jan 12, 2016 at 9:50 PM, Deron Eriksson <deroneriks...@gmail.com>
wrote:

> I will go ahead and ask that the "Single Email Address (
> dev@systemml.incubator.apache.org)" entries are removed from the
> notifications scheme to try to get them removed as soon as possible. I'll
> ask at https://issues.apache.org/jira/browse/INFRA-10714 . Please add a
> comment if this is not OK.
>
> Deron
>
>
> On Tue, Jan 12, 2016 at 9:47 PM, Deron Eriksson <deroneriks...@gmail.com>
> wrote:
>
> > A notifications scheme was created today by the infrastructure team as
> > part of https://issues.apache.org/jira/browse/INFRA-10714. It can be
> seen
> > at
> >
> https://issues.apache.org/jira/plugins/servlet/project-config/SYSTEMML/notifications
> >
> > Should we ask to remove all the "Single Email Address (
> > dev@systemml.incubator.apache.org)" entries?
> >
> > Here was our notifications scheme prior to incubation.
> > The following events had notifications for All Watchers, Current
> Assignee,
> > and Reporter:
> >   Issue Created
> >   Issue Updated
> >   Issue Assigned
> >   Issue Resolved
> >   Issue Closed
> >   Issue Commented
> >   Issue Comment Edited
> >   Issue Reopened
> >   Issue Deleted
> >   Issue Moved
> >   Work Logged On Issue
> >   Work Started On Issue
> >   Work Stopped On Issue
> >   Issue Worklog Updated
> >   Issue Worklog Deleted
> >   Generic Event
> > The following event had no notifications:
> >   Issue Comment Deleted
> >
> > Deron
> >
> >
> > On Tue, Jan 12, 2016 at 7:59 PM, Matthias Boehm <mbo...@us.ibm.com>
> wrote:
> >
> >> Could we please disable sending notifications for every JIRA update to
> >> our dev list? Thanks.
> >>
> >> Regards,
> >> Matthias
> >>
> >>
> >> [image: Inactive hide details for Deron Eriksson ---01/08/2016 01:31:48
> >> PM---Apparently it is being handled by https://issues.apache.or]Deron
> >> Eriksson ---01/08/2016 01:31:48 PM---Apparently it is being handled by
> >> https://issues.apache.org/jira/browse/INFRA-10714 and I did not se
> >>
> >> From: Deron Eriksson <deroneriks...@gmail.com>
> >> To: dev@systemml.incubator.apache.org
> >> Date: 01/08/2016 01:31 PM
> >> Subject: Re: SystemML JIRA Site Is Live!
> >> --
> >>
> >>
> >>
> >> Apparently it is being handled by
> >> https://issues.apache.org/jira/browse/INFRA-10714 and I did not see the
> >> comment. I will request the notifications scheme in the 10714 comments.
> >>
> >> Deron
> >>
> >>
> >> On Fri, Jan 8, 2016 at 1:26 PM, Deron Eriksson <deroneriks...@gmail.com
> >
> >> wrote:
> >>
> >> > I submitted a request for a notifications scheme. See status at
> >> > https://issues.apache.org/jira/browse/INFRA-11050
> >> >
> >> > Deron
> >> >
> >> >
> >> > On Fri, Jan 8, 2016 at 12:36 PM, Luciano Resende <
> luckbr1...@gmail.com>
> >> > wrote:
> >> >
> >> >> On Fri, Jan 8, 2016 at 11:09 AM, Deron Eriksson <
> >> deroneriks...@gmail.com>
> >> >> wrote:
> >> >>
> >> >> > Hi Luciano,
> >> >> >
> >> >> > Right now there is no notification scheme for the project. See
> >> >> >
> >> >> >
> >> >>
> >>
> https://issues.apache.org/jira/plugins/servlet/project-config/SYSTEMML/notifications
> >> >> >
> >> >> > I don't see an option to create or modify a notification scheme.
> >> >> >
> >> >> > Do you happen to know if we need to submit a request to INFRA to do
> >> >> this?
> >> >> >
> >> >> >
> >> >> Yes, please.
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Luciano Resende
> >> >> http://people.apache.org/~lresende
> >> >> http://twitter.com/lresende1975
> >> >> http://lresende.blogspot.com/
> >> >>
> >> >
> >> >
> >>
> >>
> >>
> >
>



-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Cleanup SparkTC/systemml repository

[Luciano Resende]

On Wednesday, January 6, 2016, Matthias Boehm <mbo...@us.ibm.com> wrote:

> Actually, I'd like to propose to release 0.8.1 as a maintenance release
> under our Apache github repo this week. From my perspective, it would be
> the perfect time for that because meanwhile our Spark backend has been
> stabilized.
>
> Regards,
> Matthias
>
>
>
> [image: Inactive hide details for Deron Eriksson ---01/06/2016 05:05:52
> PM---One other issue. Is it possible to download the SystemML 0]Deron
> Eriksson ---01/06/2016 05:05:52 PM---One other issue. Is it possible to
> download the SystemML 0.8.0 binary release from anywhere besides
>
> From: Deron Eriksson <deroneriks...@gmail.com
> <javascript:_e(%7B%7D,'cvml','deroneriks...@gmail.com');>>
> To: dev@systemml.incubator.apache.org
> <javascript:_e(%7B%7D,'cvml','dev@systemml.incubator.apache.org');>
> Date: 01/06/2016 05:05 PM
> Subject: Re: Cleanup SparkTC/systemml repository
>

+1


> --
>
>
>
> One other issue. Is it possible to download the SystemML 0.8.0 binary
> release from anywhere besides
> https://github.com/SparkTC/systemml/releases?
> If the repo is private, users can't download these binaries. So perhaps we
> need to migrate the 0.8.0 binaries to the new site until 0.9.0 is ready?
>
>
>
>
> On Wed, Jan 6, 2016 at 4:54 PM, Deron Eriksson <deroneriks...@gmail.com
> <javascript:_e(%7B%7D,'cvml','deroneriks...@gmail.com');>>
> wrote:
>
> > Hi Luciano,
> >
> > Thank you for making the SparkTC/systemml repository private. This will
> > definitely lead to less confusion.
> >
> > It turns out that there is information in some of the pull request
> > conversations from the old repository that I would like to consult (with
> > regards to the JIRA issues that I'm cleaning up because of the problems
> > with the import to Apache JIRA). Could you please grant me access to see
> > the private repository?
> >
> > Thanks!
> > Deron
> >
> >
> > On Sun, Jan 3, 2016 at 9:32 PM, Luciano Resende <luckbr1...@gmail.com
> <javascript:_e(%7B%7D,'cvml','luckbr1...@gmail.com');>>
> > wrote:
> >
> >> On Sat, Jan 2, 2016 at 12:11 PM, Matthias Boehm <mbo...@us.ibm.com
> <javascript:_e(%7B%7D,'cvml','mbo...@us.ibm.com');>>
> >> wrote:
> >>
> >> >
> >> > Hi all,
> >> >
> >> > I'd like to delete our old SparkTC/systemml repository because it's
> >> causing
> >> > unnecessary confusion and it's anyway outdated. For example, even
> >> > "developerWorks Open" is still referring to the old repository.
> >> >
> >> > @Luciano: Could you please delete the SparkTC/systemml repository if
> >> nobody
> >> > objects by this Friday? Thanks.
> >> >
> >> >
> >> > Regards,
> >> > Matthias
> >> >
> >>
> >> I have made the repository private, will delete after couple weeks if
> >> nobody objects.
> >>
> >> --
> >> Luciano Resende
> >> http://people.apache.org/~lresende
> >> http://twitter.com/lresende1975
> >> http://lresende.blogspot.com/
> >>
> >
> >
>
>
>

-- 
Sent from my Mobile device

Re: Cleanup SparkTC/systemml repository

[Luciano Resende]

On Sat, Jan 2, 2016 at 12:11 PM, Matthias Boehm <mbo...@us.ibm.com> wrote:

>
> Hi all,
>
> I'd like to delete our old SparkTC/systemml repository because it's causing
> unnecessary confusion and it's anyway outdated. For example, even
> "developerWorks Open" is still referring to the old repository.
>
> @Luciano: Could you please delete the SparkTC/systemml repository if nobody
> objects by this Friday? Thanks.
>
>
> Regards,
> Matthias
>

I have made the repository private, will delete after couple weeks if
nobody objects.

-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Closing pull requests

[Luciano Resende]

On Sunday, December 20, 2015, Reynold Xin  wrote:

> Unfortunately only the PR submitter or the ASF infra team can close them.
>
> You can also push a commit to master and close it by using the "close #xxx"
> message.
>
>
+1, i guess there isn't much more we can do.



>
> On Sun, Dec 13, 2015 at 1:04 PM, Deron Eriksson  >
> wrote:
>
> > Hi Luciano and others,
> >
> > I just merged my first pull request from another user into SystemML.
> > Previously, before pushing to Apache master I've been doing a "commit
> > --amend" to add a "Closes #[PR-NUM]." to the end of the commit message so
> > as to let asfgit close the pull request. However, because of the sync
> > issues from Apache to GitHub (2 of my last 5 commits seemed to hang the
> > propagation), I decided to hold off on the "commit --amend" to try to
> keep
> > things as simple as possible to avoid any kind of sync issue.
> >
> > So, the PR merged cleanly and the update shows up on the SystemML project
> > on GitHub as expected. However, the PR is not closed because asfgit
> didn't
> > close it and I don't have permissions to close it.
> >
> > So, at this stage, does the user close the pull request, or is it
> possible
> > for me to have permissions to close the pull request?
> >
> > Thank you,
> > Deron
> >
>


-- 
Sent from my Mobile device

Re: Incubator logo on project website

[Luciano Resende]

On Mon, Dec 7, 2015 at 10:53 AM, Deron Eriksson <deroneriks...@gmail.com>
wrote:

> On the incubator-general mailing list, there was a discussion regarding
> podling branding, and I saw it mentioned that we should include the Apache
> Incubator logo on the project website (this is a SHOULD and not a MUST).
>
> As we update the website, we should keep in mind the branding and website
> guidelines, as described here:
>
> http://incubator.apache.org/guides/branding.html
> http://incubator.apache.org/guides/sites.html
>
> Deron
>

Yes, as we are based on the apache-website-template, we got most of the
guidelines from free, the missing one, which is optional, is the incubator
logo... I will see if I can incorporate in the template to resolve this
issue for us.


-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Runtime package refactoring

[Luciano Resende]

On Sat, Dec 5, 2015 at 3:17 PM, Matthias Boehm <mbo...@us.ibm.com> wrote:

> yes, these changes are all local to 'org.apache.sysml.runtime'. Other
> than binary format incompatibility, there are no other side effects for MR
> or Spark. These changes are primarily a cleanup of a historically grown
> package structure and a preparation step. For now, there will be still just
> one assembly - down the road however, this allows us to create a separate
> artifact of the core runtime library (which is already used by all three
> CP/MR/Spark runtime backends) for external usage too.
>
>
> Regards,
> Matthias
>
> Thanks for the clarification

And please, when implementing, please follow the steps below to make sure
we don't loose file history.

- Perform the refactor on your own fork (not on apache git)
- Move the files as one git commit
- Do all the file content changes as a second git commit (imports, docs,
javadocs, etc)
- Create a full build to make sure there is no breakages
- Let the team review to make sure we are not loosing history on the files
or something similar.

Thanks

-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/