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

[Niclas Hedhman]

Sure, but in this case it is;
  1. Singa depends on Glog
  2. Glog is BSD licensed
  3. Glog use a build tool chain that is GPL'd and includes a build script
to compensate for missing toolchain tools.
  4. Singa doesn't use Glog's build toolchain

Your (John) argument is that Glog is incorrectly licensed and should have
been GPL'd. I think that reasoning is incorrect, and that Glog is licensed
correctly and hence it is not relevant whether it is optional or not for
Singa.

Given that we have both belt and suspenders for this, I think the -1 can be
withdrawn regarding the Glog dependency.

Cheers
Niclas

On Mon, Feb 6, 2017 at 10:49 AM, John D. Ament 
wrote:

> We actually just had a discussion recently on legal-discuss on this type of
> topic.  Specifically, Cat-X and optional vs required dependencies.  Henri
> and I settled on the wording you'll find at [1] as the final result.
> Basically, you can rely on Cat-X but only for optional features.
>
> We can probably follow up with legal on whether this does fall into the GPL
> bucket though.
>
> John
>
> [1]: https://www.apache.org/legal/resolved.html#optional
>
> On Sun, Feb 5, 2017 at 9:45 PM Niclas Hedhman  wrote:
>
> > I think that ends up being a build time dependency in GLOG, i.e. the
> > equivalent of Systems Requirement, and not in itself viral to the ASF
> > software. I assume that Google is much more worried about this and may
> even
> > have checked with their Legal team...
> >
> > Want to check with legal-discuss@ ? Is my memory failing me, or hasn't
> FSF
> > stated that the build output is not bound by GPL of the build toolchain?
> > (otherwise they can't release their own LGPL stuff)
> >
> > Cheers
> > Niclas
> >
> > On Mon, Feb 6, 2017 at 10:27 AM, John D. Ament 
> > wrote:
> >
> > > -1 at least I think there's an issue.
> > >
> > > While the source code all looks good, the resulting binary is not
> valid.
> > > There's no how to build doc, so I looked at your .travis.yml.  It
> > confirmed
> > > what I suspected for make, but then I started looking at your required
> > > packages.
> > >
> > > You require glog [1], which I can't find a license for.  However, glog
> > > includes [2] which is GPL, which makes glog GPL and as a result, your
> > code.
> > >
> > > [1]: https://github.com/google/glog
> > > [2]: https://github.com/google/glog/blob/master/missing
> > >
> > > - John
> > >
> > > On Sun, Jan 29, 2017 at 8:24 PM Wang Wei  wrote:
> > >
> > > > Hi all,
> > > >
> > > > The SINGA community has voted on and approved a proposal to release
> > > Apache
> > > > SINGA 1.1.0 (incubating).
> > > >
> > > > The vote thread is at:
> > > > http://mail-archives.apache.org/mod_mbox/singa-dev/201701.mbox/%
> > > > 3CCAJz0iLvAaEd5AgCqaWFD1M4-D_3EBh%3DUHbeZu-MRn%3DcKuQiX-Q%4
> > > 0mail.gmail.com
> > > > %3E
> > > >
> > > > and the result is at:
> > > >
> > > > http://mail-archives.apache.org/mod_mbox/singa-dev/201701.mbox/%
> > > 3ccajz0ilspborscstawuraowwetidb4cn14ak5sgdyb8umxoj...@mail.gmail.com
> %3e
> > > >
> > > > We ask the IPMC to vote on this release.
> > > >
> > > > The artifacts to be voted on are located here:
> > > > https://dist.apache.org/repos/dist/dev/incubator/singa/1.1.0/
> > > >
> > > > The hashes of the artifacts are as follows:
> > > > MD5:  08 CA 31 10 4E 79 02 16  A1 D7 3F 20 2D 60 21 BB
> > > >
> > > > Release artifacts are signed with the following key:
> > > > https://people.apache.org/keys/committer/dinhtta.asc
> > > >
> > > > and the signature file is:
> > > > https://dist.apache.org/repos/dist/dev/incubator/singa/1.1.0
> > > > /apache-singa-incubating-1.1.0-RC1.tar.gz.asc
> > > >
> > > > The Github tag is at:
> > > > https://github.com/apache/incubator-singa/releases/tag/v1.1.0-rc1
> > > > commit ID is: 59ca44a7ce38ce4f965511c805cda074d0b8e360
> > > >
> > > > To check the license, you can use the Apache Rat tool as follows:
> > > > 1. download & decompress apache rat from
> > http://creadur.apache.org/rat/
> > > > download_rat.cgi
> > > > 2. run the following command under singa folder:
> > > > java -jar /PATH/TO/RAT/apache-rat-0.11.jar -E rat-excludes -d .
> >
> > > > rat_check
> > > > 3. check the results in file named "rat_check"
> > > >
> > > > Please check and vote on releasing this package. The vote is open for
> > at
> > > > least 72 hours and passes if a majority of at least three +1 votes
> are
> > > > cast.
> > > >
> > > > [ ] +1 Release this package as Apache SINGA 1.0.0-incubating
> > > > [ ]  0 I don't feel strongly about it, but I'm okay with the release
> > > > [ ] -1 Do not release this package because...
> > > >
> > > > Best,
> > > > Wei
> > > >
> > >
> >
> >
> >
> > --
> > Niclas Hedhman, Software Developer
> > http://polygene.apache.org  - New Energy for
> Java
> >
>



-- 
Niclas Hedhman, Software Developer
http://polygene.apache.org  - New Energy for Java

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

[Wang Wei]

Hi John,

Thank you for checking the license of Glog.
The document building instructions are here
https://github.com/apache/incubator-singa/blob/master/doc/README.md
Glog is an optional dependency, which is declared in the installation page
http://singa.apache.org/en/docs/installation.html#from-source.
We would make it more clear in the LICENSE file and remove it from the
travis.yml file.
Can we pass this release considering Glog is an optional dependency?

Regards,
Wei


On Mon, Feb 6, 2017 at 10:49 AM, John D. Ament 
wrote:

> We actually just had a discussion recently on legal-discuss on this type of
> topic.  Specifically, Cat-X and optional vs required dependencies.  Henri
> and I settled on the wording you'll find at [1] as the final result.
> Basically, you can rely on Cat-X but only for optional features.
>
> We can probably follow up with legal on whether this does fall into the GPL
> bucket though.
>
> John
>
> [1]: https://www.apache.org/legal/resolved.html#optional
>
> On Sun, Feb 5, 2017 at 9:45 PM Niclas Hedhman  wrote:
>
> > I think that ends up being a build time dependency in GLOG, i.e. the
> > equivalent of Systems Requirement, and not in itself viral to the ASF
> > software. I assume that Google is much more worried about this and may
> even
> > have checked with their Legal team...
> >
> > Want to check with legal-discuss@ ? Is my memory failing me, or hasn't
> FSF
> > stated that the build output is not bound by GPL of the build toolchain?
> > (otherwise they can't release their own LGPL stuff)
> >
> > Cheers
> > Niclas
> >
> > On Mon, Feb 6, 2017 at 10:27 AM, John D. Ament 
> > wrote:
> >
> > > -1 at least I think there's an issue.
> > >
> > > While the source code all looks good, the resulting binary is not
> valid.
> > > There's no how to build doc, so I looked at your .travis.yml.  It
> > confirmed
> > > what I suspected for make, but then I started looking at your required
> > > packages.
> > >
> > > You require glog [1], which I can't find a license for.  However, glog
> > > includes [2] which is GPL, which makes glog GPL and as a result, your
> > code.
> > >
> > > [1]: https://github.com/google/glog
> > > [2]: https://github.com/google/glog/blob/master/missing
> > >
> > > - John
> > >
> > > On Sun, Jan 29, 2017 at 8:24 PM Wang Wei  wrote:
> > >
> > > > Hi all,
> > > >
> > > > The SINGA community has voted on and approved a proposal to release
> > > Apache
> > > > SINGA 1.1.0 (incubating).
> > > >
> > > > The vote thread is at:
> > > > http://mail-archives.apache.org/mod_mbox/singa-dev/201701.mbox/%
> > > > 3CCAJz0iLvAaEd5AgCqaWFD1M4-D_3EBh%3DUHbeZu-MRn%3DcKuQiX-Q%4
> > > 0mail.gmail.com
> > > > %3E
> > > >
> > > > and the result is at:
> > > >
> > > > http://mail-archives.apache.org/mod_mbox/singa-dev/201701.mbox/%
> > > 3ccajz0ilspborscstawuraowwetidb4cn14ak5sgdyb8umxoj...@mail.gmail.com
> %3e
> > > >
> > > > We ask the IPMC to vote on this release.
> > > >
> > > > The artifacts to be voted on are located here:
> > > > https://dist.apache.org/repos/dist/dev/incubator/singa/1.1.0/
> > > >
> > > > The hashes of the artifacts are as follows:
> > > > MD5:  08 CA 31 10 4E 79 02 16  A1 D7 3F 20 2D 60 21 BB
> > > >
> > > > Release artifacts are signed with the following key:
> > > > https://people.apache.org/keys/committer/dinhtta.asc
> > > >
> > > > and the signature file is:
> > > > https://dist.apache.org/repos/dist/dev/incubator/singa/1.1.0
> > > > /apache-singa-incubating-1.1.0-RC1.tar.gz.asc
> > > >
> > > > The Github tag is at:
> > > > https://github.com/apache/incubator-singa/releases/tag/v1.1.0-rc1
> > > > commit ID is: 59ca44a7ce38ce4f965511c805cda074d0b8e360
> > > >
> > > > To check the license, you can use the Apache Rat tool as follows:
> > > > 1. download & decompress apache rat from
> > http://creadur.apache.org/rat/
> > > > download_rat.cgi
> > > > 2. run the following command under singa folder:
> > > > java -jar /PATH/TO/RAT/apache-rat-0.11.jar -E rat-excludes -d .
> >
> > > > rat_check
> > > > 3. check the results in file named "rat_check"
> > > >
> > > > Please check and vote on releasing this package. The vote is open for
> > at
> > > > least 72 hours and passes if a majority of at least three +1 votes
> are
> > > > cast.
> > > >
> > > > [ ] +1 Release this package as Apache SINGA 1.0.0-incubating
> > > > [ ]  0 I don't feel strongly about it, but I'm okay with the release
> > > > [ ] -1 Do not release this package because...
> > > >
> > > > Best,
> > > > Wei
> > > >
> > >
> >
> >
> >
> > --
> > Niclas Hedhman, Software Developer
> > http://polygene.apache.org  - New Energy for
> Java
> >
>

[discuss] Apache Gobblin Incubator Proposal

[Olivier Lamy]

Hello everyone,
I would like to submit to you a proposal to bring Gooblin to the Apache
Software Foundation.
The text of the proposal is included below and available as a draft here in
the Wiki: https://wiki.apache.org/incubator/GobblinProposal

We will appreciate any feedback and input.

Olivier on behalf of the Gobblin community


= Apache Gobblin Proposal =
== Abstract ==
Gobblin is a distributed data integration framework that simplifies common
aspects of big data integration such as data ingestion, replication,
organization and lifecycle management for both streaming and batch data
ecosystems.

== Proposal ==

Gobblin is a universal data integration framework. The framework has been
used to build a variety of big data applications such as ingestion,
replication, and data retention. The fundamental constructs provided by the
Gobblin framework are:

 1. An expandable set of connectors that allow data to be integrated from a
variety of sources and sinks. The range of connectors already available in
Gobblin are quite diverse and are an ever expanding set. To highlight just
a few examples, connectors exist for databases (e.g., MySQL, Oracle
Teradata, Couchbase etc.), web based technologies (REST APIs, FTP/SFTP
servers, Filers), scalable storage (HDFS, S3, Ambry etc,), streaming data
(Kafka, EventHubs etc.), and a variety of proprietary data sources and
sinks (e.g.Salesforce, Google Analytics, Google Webmaster etc.). Similarly,
Gobblin has a rich library of converters that allow for conversion of data
from one format to another as data moves across system boundaries (e.g.
AVRO in HDFS to JSON in another system).


 2. Gobblin has a well defined and customizable state management layer that
allows writing stateful applications. These are particularly useful when
solving problems like bulk incremental ingest and keeping several clusters
replicated in sync. The ability to record work that has been completed and
what remains in a scalable manner is critical to writing such diverse
applications successfully.


 3. Gobblin is agnostic to the underlying execution engine. It can be
tailored to run ontop of a variety of execution frameworks ranging from
multiple processes on a single node, to open source execution engines like
MapReduce, Spark or Samza, natively on top of raw containers like Yarn or
Mesos, and the public cloud like Amazon AWS or Microsoft Azure. We are
extending Gobblin to run on top of a self managed cluster when security is
vital.  This allows different applications that require different degrees
of scalability, latency or security to be customized to for their specific
needs. For example, highly latency sensitive applications can be executed
in a streaming environment while batch based execution might benefit
applications where the priority might be geared towards optimal container
utilization.

 4.Gobblin comes out of the box with several diagnosability features like
Gobblin metrics and error handling. Collectively, these features allow
Gobblin to operate at the scale of petabytes of data. To give just one
example, the ability to quarantine a few bad records from an isolated Kafka
topic without stopping the entire flow from continued execution is vital
when the number of Kafka topics range in the thousands and the collective
data handled is in the petabytes.

Gobblin thus provides crisply defined software constructs that can be used
to build a vast array of data integration applications customizable for
varied user needs. It has become a preferred technology for data
integration use-cases by many organizations worldwide (see a partial list
here).

== Background ==

Over the last decade, data integration has evolved use case by use case in
most companies. For example, at LinkedIn, when Kafka became a significant
part of the data ecosystem, a system called Camus was built to ingest this
data for analytics processing on Hadoop. Similarly, we had custom pipelines
to ingest data from Salesforce, Oracle and myriad other sources. This
pattern became the norm rather than the exception and one point, LinkedIn
was running at least fifteen different types of ingestion pipelines. This
fragmentation has several unfortunate implications. Operational costs scale
with the number of pipelines even if the myriad pipelines share a vasty
array of common features. Bug fixes and performance optimizations cannot be
shared across the pipelines. A common set of practices around debugging and
deployment does not emerge. Each pipeline operator will continue to invest
in his little silo of the data integration world completely oblivious to
the challenges of his fellow operator sitting five tables down.

These experiences were the genesis behind the design and implementation of
Gobblin. Gobblin thus started out as a universal data ingestion framework
focussed on extracting, transforming, and synchronizing large volumes of
data between different data sources and sinks. Not surprisingly, given its
origins, the initial design 

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

[John D. Ament]

We actually just had a discussion recently on legal-discuss on this type of
topic.  Specifically, Cat-X and optional vs required dependencies.  Henri
and I settled on the wording you'll find at [1] as the final result.
Basically, you can rely on Cat-X but only for optional features.

We can probably follow up with legal on whether this does fall into the GPL
bucket though.

John

[1]: https://www.apache.org/legal/resolved.html#optional

On Sun, Feb 5, 2017 at 9:45 PM Niclas Hedhman  wrote:

> I think that ends up being a build time dependency in GLOG, i.e. the
> equivalent of Systems Requirement, and not in itself viral to the ASF
> software. I assume that Google is much more worried about this and may even
> have checked with their Legal team...
>
> Want to check with legal-discuss@ ? Is my memory failing me, or hasn't FSF
> stated that the build output is not bound by GPL of the build toolchain?
> (otherwise they can't release their own LGPL stuff)
>
> Cheers
> Niclas
>
> On Mon, Feb 6, 2017 at 10:27 AM, John D. Ament 
> wrote:
>
> > -1 at least I think there's an issue.
> >
> > While the source code all looks good, the resulting binary is not valid.
> > There's no how to build doc, so I looked at your .travis.yml.  It
> confirmed
> > what I suspected for make, but then I started looking at your required
> > packages.
> >
> > You require glog [1], which I can't find a license for.  However, glog
> > includes [2] which is GPL, which makes glog GPL and as a result, your
> code.
> >
> > [1]: https://github.com/google/glog
> > [2]: https://github.com/google/glog/blob/master/missing
> >
> > - John
> >
> > On Sun, Jan 29, 2017 at 8:24 PM Wang Wei  wrote:
> >
> > > Hi all,
> > >
> > > The SINGA community has voted on and approved a proposal to release
> > Apache
> > > SINGA 1.1.0 (incubating).
> > >
> > > The vote thread is at:
> > > http://mail-archives.apache.org/mod_mbox/singa-dev/201701.mbox/%
> > > 3CCAJz0iLvAaEd5AgCqaWFD1M4-D_3EBh%3DUHbeZu-MRn%3DcKuQiX-Q%4
> > 0mail.gmail.com
> > > %3E
> > >
> > > and the result is at:
> > >
> > > http://mail-archives.apache.org/mod_mbox/singa-dev/201701.mbox/%
> > 3ccajz0ilspborscstawuraowwetidb4cn14ak5sgdyb8umxoj...@mail.gmail.com%3e
> > >
> > > We ask the IPMC to vote on this release.
> > >
> > > The artifacts to be voted on are located here:
> > > https://dist.apache.org/repos/dist/dev/incubator/singa/1.1.0/
> > >
> > > The hashes of the artifacts are as follows:
> > > MD5:  08 CA 31 10 4E 79 02 16  A1 D7 3F 20 2D 60 21 BB
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/dinhtta.asc
> > >
> > > and the signature file is:
> > > https://dist.apache.org/repos/dist/dev/incubator/singa/1.1.0
> > > /apache-singa-incubating-1.1.0-RC1.tar.gz.asc
> > >
> > > The Github tag is at:
> > > https://github.com/apache/incubator-singa/releases/tag/v1.1.0-rc1
> > > commit ID is: 59ca44a7ce38ce4f965511c805cda074d0b8e360
> > >
> > > To check the license, you can use the Apache Rat tool as follows:
> > > 1. download & decompress apache rat from
> http://creadur.apache.org/rat/
> > > download_rat.cgi
> > > 2. run the following command under singa folder:
> > > java -jar /PATH/TO/RAT/apache-rat-0.11.jar -E rat-excludes -d . >
> > > rat_check
> > > 3. check the results in file named "rat_check"
> > >
> > > Please check and vote on releasing this package. The vote is open for
> at
> > > least 72 hours and passes if a majority of at least three +1 votes are
> > > cast.
> > >
> > > [ ] +1 Release this package as Apache SINGA 1.0.0-incubating
> > > [ ]  0 I don't feel strongly about it, but I'm okay with the release
> > > [ ] -1 Do not release this package because...
> > >
> > > Best,
> > > Wei
> > >
> >
>
>
>
> --
> Niclas Hedhman, Software Developer
> http://polygene.apache.org  - New Energy for Java
>

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

[Niclas Hedhman]

I think that ends up being a build time dependency in GLOG, i.e. the
equivalent of Systems Requirement, and not in itself viral to the ASF
software. I assume that Google is much more worried about this and may even
have checked with their Legal team...

Want to check with legal-discuss@ ? Is my memory failing me, or hasn't FSF
stated that the build output is not bound by GPL of the build toolchain?
(otherwise they can't release their own LGPL stuff)

Cheers
Niclas

On Mon, Feb 6, 2017 at 10:27 AM, John D. Ament 
wrote:

> -1 at least I think there's an issue.
>
> While the source code all looks good, the resulting binary is not valid.
> There's no how to build doc, so I looked at your .travis.yml.  It confirmed
> what I suspected for make, but then I started looking at your required
> packages.
>
> You require glog [1], which I can't find a license for.  However, glog
> includes [2] which is GPL, which makes glog GPL and as a result, your code.
>
> [1]: https://github.com/google/glog
> [2]: https://github.com/google/glog/blob/master/missing
>
> - John
>
> On Sun, Jan 29, 2017 at 8:24 PM Wang Wei  wrote:
>
> > Hi all,
> >
> > The SINGA community has voted on and approved a proposal to release
> Apache
> > SINGA 1.1.0 (incubating).
> >
> > The vote thread is at:
> > http://mail-archives.apache.org/mod_mbox/singa-dev/201701.mbox/%
> > 3CCAJz0iLvAaEd5AgCqaWFD1M4-D_3EBh%3DUHbeZu-MRn%3DcKuQiX-Q%4
> 0mail.gmail.com
> > %3E
> >
> > and the result is at:
> >
> > http://mail-archives.apache.org/mod_mbox/singa-dev/201701.mbox/%
> 3ccajz0ilspborscstawuraowwetidb4cn14ak5sgdyb8umxoj...@mail.gmail.com%3e
> >
> > We ask the IPMC to vote on this release.
> >
> > The artifacts to be voted on are located here:
> > https://dist.apache.org/repos/dist/dev/incubator/singa/1.1.0/
> >
> > The hashes of the artifacts are as follows:
> > MD5:  08 CA 31 10 4E 79 02 16  A1 D7 3F 20 2D 60 21 BB
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/dinhtta.asc
> >
> > and the signature file is:
> > https://dist.apache.org/repos/dist/dev/incubator/singa/1.1.0
> > /apache-singa-incubating-1.1.0-RC1.tar.gz.asc
> >
> > The Github tag is at:
> > https://github.com/apache/incubator-singa/releases/tag/v1.1.0-rc1
> > commit ID is: 59ca44a7ce38ce4f965511c805cda074d0b8e360
> >
> > To check the license, you can use the Apache Rat tool as follows:
> > 1. download & decompress apache rat from http://creadur.apache.org/rat/
> > download_rat.cgi
> > 2. run the following command under singa folder:
> > java -jar /PATH/TO/RAT/apache-rat-0.11.jar -E rat-excludes -d . >
> > rat_check
> > 3. check the results in file named "rat_check"
> >
> > Please check and vote on releasing this package. The vote is open for at
> > least 72 hours and passes if a majority of at least three +1 votes are
> > cast.
> >
> > [ ] +1 Release this package as Apache SINGA 1.0.0-incubating
> > [ ]  0 I don't feel strongly about it, but I'm okay with the release
> > [ ] -1 Do not release this package because...
> >
> > Best,
> > Wei
> >
>



-- 
Niclas Hedhman, Software Developer
http://polygene.apache.org  - New Energy for Java

Re: [jira] [Created] (INCUBATOR-171) Submission: Anonymous-21

[Niclas Hedhman]

I think it was said to be ok, as the total number of issues in Incubator
project itself is quite small. The current "flood" related to a new logo is
not "normal".

On Sun, Feb 5, 2017 at 10:22 PM, Carlos Santana 
wrote:

> Is this normal to get all this issues notifications from JIRA to the
> general@ list instead of a issues@ mailing list?
>
> Makes it hard to keep up with the general@ list.
>
> Just curious to know and providing feedback
>
> - Carlos Santana
> @csantanapr
>
> > On Feb 5, 2017, at 9:19 AM, Sally Khudairi (JIRA) 
> wrote:
> >
> > Sally Khudairi created INCUBATOR-171:
> > 
> >
> > Summary: Submission: Anonymous-21
> > Key: INCUBATOR-171
> > URL: https://issues.apache.org/jira/browse/INCUBATOR-171
> > Project: Incubator
> >  Issue Type: Task
> >  Components: LogoSubmission
> >Reporter: Sally Khudairi
> > Attachments: Anonymous-21.png
> >
> > Submission for Anonymous-21
> >
> >
> >
> > --
> > This message was sent by Atlassian JIRA
> > (v6.3.15#6346)
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Niclas Hedhman, Software Developer
http://polygene.apache.org  - New Energy for Java

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

[John D. Ament]

-1 at least I think there's an issue.

While the source code all looks good, the resulting binary is not valid.
There's no how to build doc, so I looked at your .travis.yml.  It confirmed
what I suspected for make, but then I started looking at your required
packages.

You require glog [1], which I can't find a license for.  However, glog
includes [2] which is GPL, which makes glog GPL and as a result, your code.

[1]: https://github.com/google/glog
[2]: https://github.com/google/glog/blob/master/missing

- John

On Sun, Jan 29, 2017 at 8:24 PM Wang Wei  wrote:

> Hi all,
>
> The SINGA community has voted on and approved a proposal to release Apache
> SINGA 1.1.0 (incubating).
>
> The vote thread is at:
> http://mail-archives.apache.org/mod_mbox/singa-dev/201701.mbox/%
> 3CCAJz0iLvAaEd5AgCqaWFD1M4-D_3EBh%3DUHbeZu-MRn%3DcKuQiX-Q%40mail.gmail.com
> %3E
>
> and the result is at:
>
> http://mail-archives.apache.org/mod_mbox/singa-dev/201701.mbox/%3ccajz0ilspborscstawuraowwetidb4cn14ak5sgdyb8umxoj...@mail.gmail.com%3e
>
> We ask the IPMC to vote on this release.
>
> The artifacts to be voted on are located here:
> https://dist.apache.org/repos/dist/dev/incubator/singa/1.1.0/
>
> The hashes of the artifacts are as follows:
> MD5:  08 CA 31 10 4E 79 02 16  A1 D7 3F 20 2D 60 21 BB
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/dinhtta.asc
>
> and the signature file is:
> https://dist.apache.org/repos/dist/dev/incubator/singa/1.1.0
> /apache-singa-incubating-1.1.0-RC1.tar.gz.asc
>
> The Github tag is at:
> https://github.com/apache/incubator-singa/releases/tag/v1.1.0-rc1
> commit ID is: 59ca44a7ce38ce4f965511c805cda074d0b8e360
>
> To check the license, you can use the Apache Rat tool as follows:
> 1. download & decompress apache rat from http://creadur.apache.org/rat/
> download_rat.cgi
> 2. run the following command under singa folder:
> java -jar /PATH/TO/RAT/apache-rat-0.11.jar -E rat-excludes -d . >
> rat_check
> 3. check the results in file named "rat_check"
>
> Please check and vote on releasing this package. The vote is open for at
> least 72 hours and passes if a majority of at least three +1 votes are
> cast.
>
> [ ] +1 Release this package as Apache SINGA 1.0.0-incubating
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
> Best,
> Wei
>

[DRAFT] Incubator PMC Board Report - February 2017

[John D. Ament]

All,

Below please find the Incubator board report.  I've CC'd podlings missing
sign off as a nudge to provide sign off.  As is expected, there is a higher
amount of mentors signing off on reports this month.

John

Incubator PMC report for February 2017

The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.

There are presently 63 podlings incubating.  We had one new PMC member and
had one podling retire.  There were seven podling releases in the month of
January.

* Community

  New IPMC members:

  - Markus Weimer

  People who left the IPMC:

  - N/A

* New Podlings

  - MXNet
  - Ratis

* Graduations

  The board has motions for the following:

  - None

* Retiring Podlings

  - Climate Model Data Analyzer

* Releases

  The following releases entered distribution during the month of
  January:

  - 2017-01-03 Apache Juneau 6.0.1
  - 2017-01-17 Apache Fineract 0.6.0
  - 2017-01-20 Apahce Impala 2.8.0
  - 2017-01-24 Apache Gossip 0.1.1
  - 2017-01-24 Apache Mnemonic 0.4.0
  - 2017-01-28 Apache Atlas 0.7.1
  - 2017-01-28 Apache Carbondata 1.0.0


* IP Clearance

  - Henri Yandell has stepped up to help revise the IP Clearance page,
improve wording to not sound so closely tied to corporate donations.

* Miscellaneous

  - An updated format of the Incubator report will be rolling out in the
March report.  A preview based on the February template can be found at
https://wiki.apache.org/incubator/testpage
  - We have begun pushing a hard review of both active podlings and mentors
associated.  A number of mentors have stepped down from their roles, and
a few podlings have been contacted to begin thinking about retirement.
  - Report formatting continues to be an issue until a fix is applied to
whimsy.

* Credits

  - Report Manager:

 Summary of podling reports 

* Still getting started at the Incubator

  - MXNet
  - OpenWhisk
  - Ratis
  - RocketMQ

* Not yet ready to graduate

  No release:

  - DistributedLog
  - iota
  - Joshua
  - SensSoft
  - Toree

  Community growth:

  - CarbonData
  - Edgent
  - Fineract
  - Guacamole
  - Impala
  - PredictionIO
  - S2Graph
  - SystemML
  - Tamaya
  - Unomi

* In Danger

  - Blur
  - Sirona
  - Milagro
  - Toree

* Missing Sign Off

  - DataFu
  - Fineract
  - ODF Toolkit
  - OpenWhisk
  - Spot


* Ready to graduate

  The Board has motions for the following:

  - None

* Did not report, expected next month

  - Sirona
  - Weex

--
   Table of Contents
Blur
CarbonData
DataFu
DistributedLog
Edgent
Fineract
Fluo
Guacamole
Impala
iota
Joshua
Milagro
MXNet
ODF Toolkit
OpenWhisk
PredictionIO
Ratis
RocketMQ
S2Graph
SensSoft
Slider
Spot
SystemML
Tamaya
Toree
Unomi

--


Blur

Blur is a search platform capable of searching massive amounts of data
in a cloud computing environment.

Blur has been incubating since 2012-07-24.

Three most important issues to address in the move towards graduation:

  1. Greater community involvement.
  2. Produce releases.
  3.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

  Lack of community involvement has brought the topic of retirement to the
  blur-dev list.


http://mail-archives.apache.org/mod_mbox/incubator-blur-dev/201702.mbox/%3Cpony-4f6911432c0e56d59d8abe5b65087e9956a6af1e-bfe4bfa9a663176fde9c80c2d11c9dc3c6e81311%40blur-dev.incubator.apache.org%3E

  We feel that the board should be aware of a potential retirement to the
  project.

How has the community developed since the last report?

  Subscriptions: user@ - 61[-1]; dev@ - 77[-1]
  The community involvement has not really changed over the past few
  months.

How has the project developed since the last report?

  - Nothing has changed since the last report.

Date of last release:

  2014-07-29

When were the last committers or PMC members elected?

  2014-07-28

Signed-off-by:

  [ ](blur) Doug Cutting
  [X](blur) Patrick Hunt
  [ ](blur) Tim Williams

Shepherd/Mentor notes:

  John D. Ament:

Sent a note to the podling RE lack of change in status.  Asked to
contemplate retirement.


Apache CarbonData is an indexed columnar data format for fast analytics on
big data platform, e.g.Apache Hadoop, Apache Spark, etc.

CarbonData has been incubating since 2016-06-02.

Three most important issues to address in the move towards graduation:

  1. Already finished 4 apache releases and all driven by different release
 managers.
  2. The community is growing well:
 a. There are more than 60+ contributors from different organizations,
increasing the diversity.
 b. Increased mailing list activity, the solutions be discussed by
mailing list and users can get efficient helps to quickly 

[RESULT] (was Re: [VOTE] Retire the Climate Model Data Analyzer Podling)

[John D. Ament]

Results:
The IPMC has accepted to retire the CMDA podling.  +1's from Ted, James,
Hadrian, myself, as well as on the podling's lists: Chirs Mattmann and
Michael Joyce.

I'll begin processing the paperwork, etc.

John

On Thu, Feb 2, 2017 at 7:20 PM John D. Ament  wrote:

> All,
>
> Due to the lack of progress made by the CMDA podling I am calling a vote
> to retire them.  A discussion and vote thread [1] have occurred on the
> podling's lists.  It was confirmed that development activities happen
> outside the ASF.
>
> I'm considering this a 72 hour lazy consensus vote since 3 IPMC members
> voted +1 on the podling's list.  My +1 is implied due to the fact that I've
> been monitoring them and am calling this vote.
>
> John
>
> [1]:
> https://lists.apache.org/thread.html/ac4de53d2b16afb91142449d7832f6713f54eb9a1fd2d9c6c3efaffb@%3Cdev.cmda.apache.org%3E
>

Re: [VOTE] Retire the Climate Model Data Analyzer Podling

[John D. Ament]

On Fri, Feb 3, 2017 at 12:07 PM Ted Dunning  wrote:

> On Fri, Feb 3, 2017 at 8:31 AM, toki  wrote:
>
> > Does retirement mean that source code is no longer available?
> >
>
>
> No.
>
> But any current versions of the code will need to be gotten from whoever
> maintains the project outside Apache. Since CMDA is ongoing (just not in an
> Apache way) the project maintainers will be the key contacts.
>

Specific to CMDA: their source code is hard to find.  They don't have
proper git mirrors.  As a result, you can only find it on git-wip-us.
https://git-wip-us.apache.org/repos/asf?p=incubator-cmda.git

- John

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

[Justin Mclean]

Hi,

+1 binding

I checked:
- name contains incubating
- signatures and hashes good (you might consider using something other than md5 
for the hash)
- DISCLAIMER exists
- LICENSE and NOTICE good
- All source files have ASF headers
- No unexpected binary files
- Can't compile from source but likely my setup

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Created] (INCUBATOR-176) Submission: Anonymous-26

[Sally Khudairi (JIRA)]

Sally Khudairi created INCUBATOR-176:


 Summary: Submission: Anonymous-26
 Key: INCUBATOR-176
 URL: https://issues.apache.org/jira/browse/INCUBATOR-176
 Project: Incubator
  Issue Type: Task
  Components: LogoSubmission
Reporter: Sally Khudairi
 Attachments: Anonymous-26.png

Submission for Anonymous-26



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Created] (INCUBATOR-175) Submission: Anonymous-25

[Sally Khudairi (JIRA)]

Sally Khudairi created INCUBATOR-175:


 Summary: Submission: Anonymous-25
 Key: INCUBATOR-175
 URL: https://issues.apache.org/jira/browse/INCUBATOR-175
 Project: Incubator
  Issue Type: Task
  Components: LogoSubmission
Reporter: Sally Khudairi
 Attachments: Anonymous-25.png

Submission for Anonymous-25



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Created] (INCUBATOR-174) Submission: Anonymous-24

[Sally Khudairi (JIRA)]

Sally Khudairi created INCUBATOR-174:


 Summary: Submission: Anonymous-24
 Key: INCUBATOR-174
 URL: https://issues.apache.org/jira/browse/INCUBATOR-174
 Project: Incubator
  Issue Type: Task
  Components: LogoSubmission
Reporter: Sally Khudairi
 Attachments: Anonymous24.png

Submission for Anonymous-24



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [jira] [Created] (INCUBATOR-171) Submission: Anonymous-21

[Carlos Santana]

Is this normal to get all this issues notifications from JIRA to the general@ 
list instead of a issues@ mailing list?

Makes it hard to keep up with the general@ list. 

Just curious to know and providing feedback

- Carlos Santana
@csantanapr

> On Feb 5, 2017, at 9:19 AM, Sally Khudairi (JIRA)  wrote:
> 
> Sally Khudairi created INCUBATOR-171:
> 
> 
> Summary: Submission: Anonymous-21
> Key: INCUBATOR-171
> URL: https://issues.apache.org/jira/browse/INCUBATOR-171
> Project: Incubator
>  Issue Type: Task
>  Components: LogoSubmission
>Reporter: Sally Khudairi
> Attachments: Anonymous-21.png
> 
> Submission for Anonymous-21
> 
> 
> 
> --
> This message was sent by Atlassian JIRA
> (v6.3.15#6346)
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Created] (INCUBATOR-173) Submission: Anonymous-23

[Sally Khudairi (JIRA)]

Sally Khudairi created INCUBATOR-173:


 Summary: Submission: Anonymous-23
 Key: INCUBATOR-173
 URL: https://issues.apache.org/jira/browse/INCUBATOR-173
 Project: Incubator
  Issue Type: Task
  Components: LogoSubmission
Reporter: Sally Khudairi
 Attachments: Anonymous-23.jpg

Submission for Anonymous-23



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Created] (INCUBATOR-172) Submission: Anonymous-22

[Sally Khudairi (JIRA)]

Sally Khudairi created INCUBATOR-172:


 Summary: Submission: Anonymous-22
 Key: INCUBATOR-172
 URL: https://issues.apache.org/jira/browse/INCUBATOR-172
 Project: Incubator
  Issue Type: Task
  Components: LogoSubmission
Reporter: Sally Khudairi
 Attachments: Anonymous-22.png

Submission for Anonymous-22



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Created] (INCUBATOR-170) Submission: Anonymous-20

[Sally Khudairi (JIRA)]

Sally Khudairi created INCUBATOR-170:


 Summary: Submission: Anonymous-20
 Key: INCUBATOR-170
 URL: https://issues.apache.org/jira/browse/INCUBATOR-170
 Project: Incubator
  Issue Type: Task
  Components: LogoSubmission
Reporter: Sally Khudairi
 Attachments: Anonymous-20.jpg

Submission for Anonymous-20



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Created] (INCUBATOR-171) Submission: Anonymous-21

[Sally Khudairi (JIRA)]

Sally Khudairi created INCUBATOR-171:


 Summary: Submission: Anonymous-21
 Key: INCUBATOR-171
 URL: https://issues.apache.org/jira/browse/INCUBATOR-171
 Project: Incubator
  Issue Type: Task
  Components: LogoSubmission
Reporter: Sally Khudairi
 Attachments: Anonymous-21.png

Submission for Anonymous-21



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Created] (INCUBATOR-168) Submission: Anonymous-18

[Sally Khudairi (JIRA)]

Sally Khudairi created INCUBATOR-168:


 Summary: Submission: Anonymous-18
 Key: INCUBATOR-168
 URL: https://issues.apache.org/jira/browse/INCUBATOR-168
 Project: Incubator
  Issue Type: Task
  Components: LogoSubmission
Reporter: Sally Khudairi
 Attachments: Anonymous-18.jpg

Submission for Anonymous-18



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Created] (INCUBATOR-169) Submission: Anonymous-19

[Sally Khudairi (JIRA)]

Sally Khudairi created INCUBATOR-169:


 Summary: Submission: Anonymous-19
 Key: INCUBATOR-169
 URL: https://issues.apache.org/jira/browse/INCUBATOR-169
 Project: Incubator
  Issue Type: Task
  Components: LogoSubmission
Reporter: Sally Khudairi
 Attachments: Anonymous-19.jpg

Submission for Anonymous-19



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Created] (INCUBATOR-167) Submission: Anonymous-17

[Sally Khudairi (JIRA)]

Sally Khudairi created INCUBATOR-167:


 Summary: Submission: Anonymous-17
 Key: INCUBATOR-167
 URL: https://issues.apache.org/jira/browse/INCUBATOR-167
 Project: Incubator
  Issue Type: Task
  Components: LogoSubmission
Reporter: Sally Khudairi
 Attachments: Anonymous-17.jpg

Submission for Anonymous-17



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org