Re: Podling Graduation Rally

[Marvin Humphrey]

On Tue, Feb 21, 2017 at 12:15 PM, John D. Ament  wrote:
> On Tue, Feb 21, 2017 at 2:52 PM Roman Shaposhnik 
> wrote:

>> I think we all agree on what's going on and I believe (although correct
>> me if I'm putting words in your mouth John) that we all feel the current
>> situation with MADlib is NOT against any policy of ASF.
>>
> Not 100%.  We are saying that code modifications should have been under
> apache license, but they were still under BSD as of the release from last
> year.

What makes you say that?  What do you mean by "they were still under BSD"?
Please point us at a commit.

The podling has received a recommendation from VP Legal.  If you believe that
recommendation was in error, please raise your objection explicitly on
legal-discuss.  If you can't persuade Legal to rescind the recommendation,
then the remaining question is whether the podling is implementing that
recommendation successfully.  I have not yet seen a coherent explanation of
how the podling is failing in this regard.

I'm troubled by how difficult we are making things for MADlib.  They consulted
Legal and got a recommendation.  As far as I know, they're following the
recommendation.  What more can we ask of them?

Marvin Humphrey

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

Re: Podling Graduation Rally

[Upayavira]

I think that nothing is likely to change in the project - it is going to
go on the same as this for a long time. If it is ready, it is right on
the bottom of minimal. It does have enough prospective PMC members, but
just enough - maybe 4 or 5.

It has made a release, and it has just managed a source code donation,
and it has accepted new committers.

I am starting to consider that this has to be sufficient activity to
justify graduation, although it is certainly on the lower limit.

Thoughts?

Upayavira

On Tue, 14 Feb 2017, at 03:16 PM, John D. Ament wrote:
> Upayavira,
> 
> I've pinged the podling in the past about graduation.  *I* think you're
> ready.
> 
> On Mon, Feb 13, 2017 at 6:15 PM Upayavira  wrote:
> 
> > I would appreciate assistance in deciding whether Wave needs more than
> > its current slow, but not stationary, development.
> >
> > Upayavira
> >
> > On Mon, 13 Feb 2017, at 06:07 PM, John D. Ament wrote:
> > > Awesome news, thanks everyone.
> > >
> > > On Mon, Feb 13, 2017 at 12:17 PM Suneel Marthi 
> > > wrote:
> > >
> > > > Streams was also called as 'Ready to graduate' in the December report.
> > > >
> > > > Since Oct 2016, the podling has had 3 releases and another release is
> > > > planned for this weekend.
> > > >
> > > > There have been discussions on the podIing mail lists about graduation
> > > > following the next planned release. I can help push forward Streams
> > > > graduation and the podling has satisfied most of the Apache Maturity
> > > > Assessment -  see
> > > >
> > > >
> > https://cwiki.apache.org/confluence/display/STREAMS/Apache+Maturity+Model+Assessment+for+Streams
> > > >
> > > >
> > > >
> > > >
> > > > On Mon, Feb 13, 2017 at 7:51 AM, Pierre Smits 
> > > > wrote:
> > > >
> > > > > Hi John,
> > > > >
> > > > > Thank you for bringing this to our attention. I guess it should be
> > > > brought
> > > > > back regularly so that participants here stay on the ball.
> > > > >
> > > > > That being said, I believe Trafodion should also be considered to be
> > > > ready.
> > > > >
> > > > > Best regards,
> > > > >
> > > > > Pierre Smits
> > > > >
> > > > > ORRTIZ.COM 
> > > > > OFBiz based solutions & services
> > > > >
> > > > > OFBiz Extensions Marketplace
> > > > > http://oem.ofbizci.net/oci-2/
> > > > >
> > > > > On Mon, Feb 13, 2017 at 1:28 PM, John D. Ament <
> > johndam...@apache.org>
> > > > > wrote:
> > > > >
> > > > > > All,
> > > > > >
> > > > > > As mentioned in this month's report, there are 63 active podlings.
> > > > While
> > > > > > I've been chasing retiring podlings, I think it would be good for
> > the
> > > > > > community as a whole to look closely as podlings and see what we
> > can do
> > > > > to
> > > > > > graduate podlings that seem to be doing well.
> > > > > >
> > > > > > Take a look at the last two reports:
> > > > > >
> > > > > > https://wiki.apache.org/incubator/February2017
> > > > > > https://wiki.apache.org/incubator/January2017
> > > > > >
> > > > > > Last month, I listed 4 podlings that appear to have completed all
> > > > > > graduation requirements, but remain in the incubator (Airflow,
> > BatchEE,
> > > > > > Freemarker, Metron).  I didn't include that in February, but if I
> > had
> > > > to
> > > > > > list the names, it would be: CarbonData, Edgent, Fineract,
> > Guacamole,
> > > > > > PredictionIO, SystemML, Tamaya, Unomi (but that's entirely my
> > > > POV/opinion
> > > > > > unless others want to chime in).
> > > > > >
> > > > > > So I'm curious, what can others do to help these 12 podlings get
> > past
> > > > the
> > > > > > finish line?
> > > > > >
> > > > > > John
> > > > > >
> > > > >
> > > >
> >
> > -
> > 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

Re: Podling Graduation Rally

[Roman Shaposhnik]

On Tue, Feb 21, 2017 at 12:15 PM, John D. Ament  wrote:
> On Tue, Feb 21, 2017 at 2:52 PM Roman Shaposhnik 
> wrote:
>
>> On Tue, Feb 21, 2017 at 10:25 AM, Marvin Humphrey
>>  wrote:
>> > On Tue, Feb 21, 2017 at 6:31 AM, John D. Ament 
>> wrote:
>> >
>> >> So are we saying that the code modifications are sub-licensed? Or
>> >> re-licensed?
>> >
>> > Think of each file as the result of layering changesets on top of each
>> > other.  Each changeset has its own copyright holder and each copyright
>> > holder grants a license.
>> >
>> > When all changesets have the same license, then the end product has
>> > uniform licensing, even though many entities hold continue to hold
>> > copyright.
>> >
>> > However, it is also possible that changesets may be granted under
>> > different licenses -- in which case, the end product has heterogeneous
>> > licensing.  It may not be possible to slice up the file into code blocks
>> > which are under one license exclusively. Instead, if you want clean
>> > divisions by license you have to go back to the changesets.
>> >
>> > For BSD-2-clause files which came in with MADlib but were not relicensed
>> > (because not all authors participated in the SGA), we are saying that
>> > changesets submitted after arrival at the ASF shall be under Apache-2.0.
>>
>> I think we all agree on what's going on and I believe (although correct
>> me if I'm putting words in your mouth John) that we all feel the current
>> situation with MADlib is NOT against any policy of ASF.
>>
>>
> Not 100%.  We are saying that code modifications should have been under
> apache license, but they were still under BSD as of the release from last
> year.  Its nothing that I believe would have put the foundation in any
> negative situation.

The ARE under Apache License -- we are all in agreement there. We simply
lack tools to make this very fine grain statement.

Does it make it clearer? Are we in agreement now?

Thanks,
Roman.

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

Re: Podling Graduation Rally

[John D. Ament]

On Tue, Feb 21, 2017 at 2:52 PM Roman Shaposhnik 
wrote:

> On Tue, Feb 21, 2017 at 10:25 AM, Marvin Humphrey
>  wrote:
> > On Tue, Feb 21, 2017 at 6:31 AM, John D. Ament 
> wrote:
> >
> >> So are we saying that the code modifications are sub-licensed? Or
> >> re-licensed?
> >
> > Think of each file as the result of layering changesets on top of each
> > other.  Each changeset has its own copyright holder and each copyright
> > holder grants a license.
> >
> > When all changesets have the same license, then the end product has
> > uniform licensing, even though many entities hold continue to hold
> > copyright.
> >
> > However, it is also possible that changesets may be granted under
> > different licenses -- in which case, the end product has heterogeneous
> > licensing.  It may not be possible to slice up the file into code blocks
> > which are under one license exclusively. Instead, if you want clean
> > divisions by license you have to go back to the changesets.
> >
> > For BSD-2-clause files which came in with MADlib but were not relicensed
> > (because not all authors participated in the SGA), we are saying that
> > changesets submitted after arrival at the ASF shall be under Apache-2.0.
>
> I think we all agree on what's going on and I believe (although correct
> me if I'm putting words in your mouth John) that we all feel the current
> situation with MADlib is NOT against any policy of ASF.
>
>
Not 100%.  We are saying that code modifications should have been under
apache license, but they were still under BSD as of the release from last
year.  Its nothing that I believe would have put the foundation in any
negative situation.


> The real question is how do we communicate it to a downstream consumer.
>
> There are two tools we have: a LICENSE file at the root of the project tree
> and individual license headers in each of the files. Neither of these tools
> are precise enough to address the subtlety that changesets may be granted
> under different licenses. IOW, there's no perfect solution here and we have
> to unblock the podling by making a decision that will be *less* than
> precise.
>
> I really hope we can all agree on that.
>
> Initially, I was very happy with the solution endorsed by Marvin and VP of
> Legal
> https://s.apache.org/EOT5
> In fact I thought that in conjunction with the statement in LICENSE file
> it would be OK to modify the files and still NOT add ALv2 header (only
> brand new files created throughout the ASF lifetime of the project will
> get the proper AL header).
>
> It seems that this assumption is now being challenged and as such we
> NO LONGER have a path forward for the podling.
>
> John, am I capturing your concerns correctly?
>
>
Yes.  Basically, the notion put forth in the email you linked to is no
longer valid since the podling has modified the code that came in under BSD.

But again, please tell me if I'm misunderstanding the changes that have
gone in.


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

Re: Podling Graduation Rally

[Roman Shaposhnik]

On Tue, Feb 21, 2017 at 10:25 AM, Marvin Humphrey
 wrote:
> On Tue, Feb 21, 2017 at 6:31 AM, John D. Ament  wrote:
>
>> So are we saying that the code modifications are sub-licensed? Or
>> re-licensed?
>
> Think of each file as the result of layering changesets on top of each
> other.  Each changeset has its own copyright holder and each copyright
> holder grants a license.
>
> When all changesets have the same license, then the end product has
> uniform licensing, even though many entities hold continue to hold
> copyright.
>
> However, it is also possible that changesets may be granted under
> different licenses -- in which case, the end product has heterogeneous
> licensing.  It may not be possible to slice up the file into code blocks
> which are under one license exclusively. Instead, if you want clean
> divisions by license you have to go back to the changesets.
>
> For BSD-2-clause files which came in with MADlib but were not relicensed
> (because not all authors participated in the SGA), we are saying that
> changesets submitted after arrival at the ASF shall be under Apache-2.0.

I think we all agree on what's going on and I believe (although correct
me if I'm putting words in your mouth John) that we all feel the current
situation with MADlib is NOT against any policy of ASF.

The real question is how do we communicate it to a downstream consumer.

There are two tools we have: a LICENSE file at the root of the project tree
and individual license headers in each of the files. Neither of these tools
are precise enough to address the subtlety that changesets may be granted
under different licenses. IOW, there's no perfect solution here and we have
to unblock the podling by making a decision that will be *less* than precise.

I really hope we can all agree on that.

Initially, I was very happy with the solution endorsed by Marvin and VP of Legal
https://s.apache.org/EOT5
In fact I thought that in conjunction with the statement in LICENSE file
it would be OK to modify the files and still NOT add ALv2 header (only
brand new files created throughout the ASF lifetime of the project will
get the proper AL header).

It seems that this assumption is now being challenged and as such we
NO LONGER have a path forward for the podling.

John, am I capturing your concerns correctly?

Thanks,
Roman.

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

Re: Podling Graduation Rally

[Marvin Humphrey]

On Tue, Feb 21, 2017 at 6:31 AM, John D. Ament  wrote:

> So are we saying that the code modifications are sub-licensed? Or
> re-licensed?

Think of each file as the result of layering changesets on top of each
other.  Each changeset has its own copyright holder and each copyright
holder grants a license.

When all changesets have the same license, then the end product has
uniform licensing, even though many entities hold continue to hold
copyright.

However, it is also possible that changesets may be granted under
different licenses -- in which case, the end product has heterogeneous
licensing.  It may not be possible to slice up the file into code blocks
which are under one license exclusively. Instead, if you want clean
divisions by license you have to go back to the changesets.

For BSD-2-clause files which came in with MADlib but were not relicensed
(because not all authors participated in the SGA), we are saying that
changesets submitted after arrival at the ASF shall be under Apache-2.0.

PS: This workflow is not possible when the first license has reciprocity
requirements (i.e. it's a "copyleft" license like GPL or MPL),
because a key condition of such licenses is that the copyright
holder for subsequent changesets must make them available under the
original license.  However, BSD licenses do not impose such a
restriction, so it's valid to create an ALv2 changeset to apply on
top of a BSD file.

Marvin Humphrey

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

Re: Podling Graduation Rally

[John D. Ament]

On Tue, Feb 21, 2017 at 1:49 AM Marvin Humphrey 
wrote:

> On Mon, Feb 20, 2017 at 10:47 AM, Mike Jumper 
> wrote:
> > AFAIK, only the copyright holder can relicense a copyrighted work,
> whereas
> > others may sublicense under compatible terms so long as the original
> > license grants that permission (ie: the license of the original work is
> not
> > actually changing).
> >
> > Is that not correct?
>
> Correct, and well said!
>
> When we assert that an Apache release package is available under the
> ALv2 even though it bundles BSD-2-clause licensed code (as is the case
> with MADlib), we are suggesting that the ALv2 "subsumes" the
> BSD-2-clause license -- that fulfilling all the requirements of the
> ALv2 suffices to fulfill all the requirements of the BSD-2-clause
> license.
>
> This is sometimes called "sublicensing", and it only works in one
> direction: a license with more restrictions can subsume one with
> fewer, but not the other way around.
>
> In contrast, "relicensing" is usually taken to mean the original
> copyright holder granting an *additional* license of any type. For
> example, if you're the copyright holder, you can take something which
> is available only under a proprietary license and make it available
> under an open source license.  Or you could take something available
> under the GPL and make it available under the ALv2.
>
> (Of course the difficulty of "relicensing" in the context of open
> source is that there may be many copyright holders who need to
> participate in a relicensing effort -- and if you can't get them all
> on board, you might have to strip out and replace code that couldn't
> be relicensed.)
>
> For more information on combining software under multiple open source
> licenses, I like this article by Luis Villa:
>
>
> https://opensource.com/law/11/9/mpl-20-copyleft-and-license-compatibility
>
> This is outdated but still a good read:
>
>http://www.catb.org/esr/Licensing-HOWTO.html#compatibility
>
> Marvin Humphrey
>


So are we saying that the code modifications are sub-licensed? Or
re-licensed?


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

Re: Podling Graduation Rally

[Marvin Humphrey]

On Mon, Feb 20, 2017 at 10:47 AM, Mike Jumper  wrote:
> AFAIK, only the copyright holder can relicense a copyrighted work, whereas
> others may sublicense under compatible terms so long as the original
> license grants that permission (ie: the license of the original work is not
> actually changing).
>
> Is that not correct?

Correct, and well said!

When we assert that an Apache release package is available under the
ALv2 even though it bundles BSD-2-clause licensed code (as is the case
with MADlib), we are suggesting that the ALv2 "subsumes" the
BSD-2-clause license -- that fulfilling all the requirements of the
ALv2 suffices to fulfill all the requirements of the BSD-2-clause
license.

This is sometimes called "sublicensing", and it only works in one
direction: a license with more restrictions can subsume one with
fewer, but not the other way around.

In contrast, "relicensing" is usually taken to mean the original
copyright holder granting an *additional* license of any type. For
example, if you're the copyright holder, you can take something which
is available only under a proprietary license and make it available
under an open source license.  Or you could take something available
under the GPL and make it available under the ALv2.

(Of course the difficulty of "relicensing" in the context of open
source is that there may be many copyright holders who need to
participate in a relicensing effort -- and if you can't get them all
on board, you might have to strip out and replace code that couldn't
be relicensed.)

For more information on combining software under multiple open source
licenses, I like this article by Luis Villa:

   https://opensource.com/law/11/9/mpl-20-copyleft-and-license-compatibility

This is outdated but still a good read:

   http://www.catb.org/esr/Licensing-HOWTO.html#compatibility

Marvin Humphrey

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

Re: Podling Graduation Rally

[Mike Jumper]

AFAIK, only the copyright holder can relicense a copyrighted work, whereas
others may sublicense under compatible terms so long as the original
license grants that permission (ie: the license of the original work is not
actually changing).

Is that not correct?

- Mike


On Feb 20, 2017 10:35 AM, "John D. Ament"  wrote:

Mike,

I'll point out that sublicense is probably not the right term.  While both
are Cat A, the BSD license is much less restrictive/offers less than the
Apache license.  Re-license is more accurate.  Its still compatible with
BSD, and removes any expectation that one is more/less than the other
license.

On Sun, Feb 19, 2017 at 11:19 PM Mike Jumper 
wrote:

> On Feb 19, 2017 8:01 PM, "Niclas Hedhman"  wrote:
>
> ...
> CatA licenses are CatA because they allow modifications on source and
> re-license...
>
>
> sublicense*
>
> - Mike
>

Re: Podling Graduation Rally

[John D. Ament]

Mike,

I'll point out that sublicense is probably not the right term.  While both
are Cat A, the BSD license is much less restrictive/offers less than the
Apache license.  Re-license is more accurate.  Its still compatible with
BSD, and removes any expectation that one is more/less than the other
license.

On Sun, Feb 19, 2017 at 11:19 PM Mike Jumper 
wrote:

> On Feb 19, 2017 8:01 PM, "Niclas Hedhman"  wrote:
>
> ...
> CatA licenses are CatA because they allow modifications on source and
> re-license...
>
>
> sublicense*
>
> - Mike
>

Re: Podling Graduation Rally

[Roman Shaposhnik]

On Mon, Feb 20, 2017 at 3:30 AM, John D. Ament  wrote:
> On Sun, Feb 19, 2017 at 11:09 PM Roman Shaposhnik 
> wrote:
>
>> On Sun, Feb 19, 2017 at 8:01 PM, Niclas Hedhman  wrote:
>> > I haven't followed this issue, but if we take BSD licensed source and
>> > modifies it (enough to claim copyright on the modifications) we
>> re-license
>> > to ALv2, but leaves the original BSD headers (if any) in the source.
>> >
>> > CatA licenses are CatA because they allow modifications on source and
>> > re-license...
>>
>> Correct. Which seems to make Roy's proposal a superset of what you're
>> talking
>> about. Now, while we can debate whether we can accomplish something similar
>> to what he was suggesting by some other means -- I'd rather vote for
>> simplicity
>> and go ahead with this:
>>
>> https://issues.apache.org/jira/browse/LEGAL-293?focusedCommentId=15873943=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15873943
>>
>> At this point -- I just need to see if there's anybody who's strongly
>> opposed this
>> approach.
>>
>
> Doing what you've outlined was my original request, so I have no qualms.
> It had seemed to me that the preference was to not relicense.  But I am
> glad we are relicensing.

No we are not. See Mike's reply above.

Thanks,
Roman.

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

Re: Podling Graduation Rally

[Mike Jumper]

On Feb 19, 2017 8:01 PM, "Niclas Hedhman"  wrote:

...
CatA licenses are CatA because they allow modifications on source and
re-license...


sublicense*

- Mike

Re: Podling Graduation Rally

[Roman Shaposhnik]

On Sun, Feb 19, 2017 at 8:01 PM, Niclas Hedhman  wrote:
> I haven't followed this issue, but if we take BSD licensed source and
> modifies it (enough to claim copyright on the modifications) we re-license
> to ALv2, but leaves the original BSD headers (if any) in the source.
>
> CatA licenses are CatA because they allow modifications on source and
> re-license...

Correct. Which seems to make Roy's proposal a superset of what you're talking
about. Now, while we can debate whether we can accomplish something similar
to what he was suggesting by some other means -- I'd rather vote for simplicity
and go ahead with this:
 
https://issues.apache.org/jira/browse/LEGAL-293?focusedCommentId=15873943=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15873943

At this point -- I just need to see if there's anybody who's strongly
opposed this
approach.

Thanks,
Roman.

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

Re: Podling Graduation Rally

[Niclas Hedhman]

I haven't followed this issue, but if we take BSD licensed source and
modifies it (enough to claim copyright on the modifications) we re-license
to ALv2, but leaves the original BSD headers (if any) in the source.

CatA licenses are CatA because they allow modifications on source and
re-license...

Niclas

On Feb 20, 2017 04:12, "John D. Ament"  wrote:

> On Sun, Feb 19, 2017 at 3:08 PM Roman Shaposhnik 
> wrote:
>
> > On Sun, Feb 19, 2017 at 5:43 AM, John D. Ament 
> > wrote:
> > > I'm personally still concerned about MADLib's licensing status.
> > > Specifically speaking, where I feel more info is needed around
> > > modifications to the BSD licensed code.  None of that was in the legal
> > > resolution.
> >
> > Can you please suggest how can this be resolved? I've stated my opinion,
> > others stated theirs -- but how do we arrive at a either a consensus or
> > a resolution? What's a mechanism here?
> >
>
> Was there a clear statement on the code modifications?  Last I saw, there
> was an agreement for the imported code, but I thought I saw something
> saying the modifications were apache licensed, which is confusing in the
> current state.
>
> Either way, lets move this to legal discuss.
>
>
> >
> > Thanks,
> > Roman.
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: Podling Graduation Rally

[Roman Shaposhnik]

On Sun, Feb 19, 2017 at 12:12 PM, John D. Ament  wrote:
> On Sun, Feb 19, 2017 at 3:08 PM Roman Shaposhnik 
> wrote:
>
>> On Sun, Feb 19, 2017 at 5:43 AM, John D. Ament 
>> wrote:
>> > I'm personally still concerned about MADLib's licensing status.
>> > Specifically speaking, where I feel more info is needed around
>> > modifications to the BSD licensed code.  None of that was in the legal
>> > resolution.
>>
>> Can you please suggest how can this be resolved? I've stated my opinion,
>> others stated theirs -- but how do we arrive at a either a consensus or
>> a resolution? What's a mechanism here?
>>
>
> Was there a clear statement on the code modifications?  Last I saw, there
> was an agreement for the imported code, but I thought I saw something
> saying the modifications were apache licensed, which is confusing in the
> current state.
>
> Either way, lets move this to legal discuss.

I filed https://issues.apache.org/jira/browse/LEGAL-293 and provided links
to the previous conversations around this subject. If there's a need to re-open
that discussion I'd rather do it on the JIRA.

Thanks,
Roman.

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

Re: Podling Graduation Rally

[John D. Ament]

On Sun, Feb 19, 2017 at 3:08 PM Roman Shaposhnik 
wrote:

> On Sun, Feb 19, 2017 at 5:43 AM, John D. Ament 
> wrote:
> > I'm personally still concerned about MADLib's licensing status.
> > Specifically speaking, where I feel more info is needed around
> > modifications to the BSD licensed code.  None of that was in the legal
> > resolution.
>
> Can you please suggest how can this be resolved? I've stated my opinion,
> others stated theirs -- but how do we arrive at a either a consensus or
> a resolution? What's a mechanism here?
>

Was there a clear statement on the code modifications?  Last I saw, there
was an agreement for the imported code, but I thought I saw something
saying the modifications were apache licensed, which is confusing in the
current state.

Either way, lets move this to legal discuss.


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

Re: Podling Graduation Rally

[Roman Shaposhnik]

On Sun, Feb 19, 2017 at 5:43 AM, John D. Ament  wrote:
> I'm personally still concerned about MADLib's licensing status.
> Specifically speaking, where I feel more info is needed around
> modifications to the BSD licensed code.  None of that was in the legal
> resolution.

Can you please suggest how can this be resolved? I've stated my opinion,
others stated theirs -- but how do we arrive at a either a consensus or
a resolution? What's a mechanism here?

Thanks,
Roman.

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

Re: Podling Graduation Rally

[John D. Ament]

On Sat, Feb 18, 2017 at 10:45 PM Roman Shaposhnik 
wrote:

> Sorry for jumping at this rather tale -- being overwhelmed with
> work and personal stuff :-(
>
> As usual, John, I applaud your focus! A quick comment bellow.
>
> On Mon, Feb 13, 2017 at 4:28 AM, John D. Ament 
> wrote:
> > All,
> >
> > As mentioned in this month's report, there are 63 active podlings.  While
> > I've been chasing retiring podlings, I think it would be good for the
> > community as a whole to look closely as podlings and see what we can do
> to
> > graduate podlings that seem to be doing well.
> >
> > Take a look at the last two reports:
> >
> > https://wiki.apache.org/incubator/February2017
> > https://wiki.apache.org/incubator/January2017
> >
> > Last month, I listed 4 podlings that appear to have completed all
> > graduation requirements, but remain in the incubator (Airflow, BatchEE,
> > Freemarker, Metron).  I didn't include that in February, but if I had to
> > list the names, it would be: CarbonData, Edgent, Fineract, Guacamole,
> > PredictionIO, SystemML, Tamaya, Unomi (but that's entirely my POV/opinion
> > unless others want to chime in).
> >
> > So I'm curious, what can others do to help these 12 podlings get past the
> > finish line?
>
> Out of the podlings I mentor I agree that Fineract is pretty close. But
> I also would like to suggest that MADlib and DataFu. The logic being
> those 3 are at pretty much the same level of maturity/community
> development (although they are different in the community's size).
>
> Could you, folks, please take a look at past reports for these 3 and
> let me know your opinion? Btw, both MADlib and DataFu are working
> on the one more release right now.
>
>
I'm personally still concerned about MADLib's licensing status.
Specifically speaking, where I feel more info is needed around
modifications to the BSD licensed code.  None of that was in the legal
resolution.

I see DataFu just fixed an issue where their binaries didn't include
expected notice/license files.  I suspect if they cut a release, which
includes both source and convenience binary, and that release passes
without any issues, then they are likely ready to graduate.


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

Re: Podling Graduation Rally

[Roman Shaposhnik]

Sorry for jumping at this rather tale -- being overwhelmed with
work and personal stuff :-(

As usual, John, I applaud your focus! A quick comment bellow.

On Mon, Feb 13, 2017 at 4:28 AM, John D. Ament  wrote:
> All,
>
> As mentioned in this month's report, there are 63 active podlings.  While
> I've been chasing retiring podlings, I think it would be good for the
> community as a whole to look closely as podlings and see what we can do to
> graduate podlings that seem to be doing well.
>
> Take a look at the last two reports:
>
> https://wiki.apache.org/incubator/February2017
> https://wiki.apache.org/incubator/January2017
>
> Last month, I listed 4 podlings that appear to have completed all
> graduation requirements, but remain in the incubator (Airflow, BatchEE,
> Freemarker, Metron).  I didn't include that in February, but if I had to
> list the names, it would be: CarbonData, Edgent, Fineract, Guacamole,
> PredictionIO, SystemML, Tamaya, Unomi (but that's entirely my POV/opinion
> unless others want to chime in).
>
> So I'm curious, what can others do to help these 12 podlings get past the
> finish line?

Out of the podlings I mentor I agree that Fineract is pretty close. But
I also would like to suggest that MADlib and DataFu. The logic being
those 3 are at pretty much the same level of maturity/community
development (although they are different in the community's size).

Could you, folks, please take a look at past reports for these 3 and
let me know your opinion? Btw, both MADlib and DataFu are working
on the one more release right now.

Thanks,
Roman.

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

Re: Podling Graduation Rally

[Jean-Baptiste Onofré]

No problem at all. Just to be sure we don't duplicate work ;)

Regards
JB

On Feb 14, 2017, 12:28, at 12:28, Henry Saputra  wrote:
>Ah yes, sorry, totally missed your message.
>
>On Tue, Feb 14, 2017 at 3:02 AM, Jean-Baptiste Onofré 
>wrote:
>
>> Hi
>>
>> I guess you missed my message. I gonna deal with CarbonData.
>>
>> Regards
>> JB
>>
>> On Feb 13, 2017, 19:26, at 19:26, Henry Saputra
>
>> wrote:
>> >Thanks, John. I think CarbonData and SystemML may ready for
>graduation.
>> >
>> >Looks like Luciano will work with SystemML, then I will work with
>> >CarbonData.
>> >
>> >- Henry
>> >
>> >On Mon, Feb 13, 2017 at 4:28 AM, John D. Ament
>
>> >wrote:
>> >
>> >> All,
>> >>
>> >> As mentioned in this month's report, there are 63 active podlings.
>> >While
>> >> I've been chasing retiring podlings, I think it would be good for
>the
>> >> community as a whole to look closely as podlings and see what we
>can
>> >do to
>> >> graduate podlings that seem to be doing well.
>> >>
>> >> Take a look at the last two reports:
>> >>
>> >> https://wiki.apache.org/incubator/February2017
>> >> https://wiki.apache.org/incubator/January2017
>> >>
>> >> Last month, I listed 4 podlings that appear to have completed all
>> >> graduation requirements, but remain in the incubator (Airflow,
>> >BatchEE,
>> >> Freemarker, Metron).  I didn't include that in February, but if I
>had
>> >to
>> >> list the names, it would be: CarbonData, Edgent, Fineract,
>Guacamole,
>> >> PredictionIO, SystemML, Tamaya, Unomi (but that's entirely my
>> >POV/opinion
>> >> unless others want to chime in).
>> >>
>> >> So I'm curious, what can others do to help these 12 podlings get
>past
>> >the
>> >> finish line?
>> >>
>> >> John
>> >>
>>

Re: Podling Graduation Rally

[Henry Saputra]

Ah yes, sorry, totally missed your message.

On Tue, Feb 14, 2017 at 3:02 AM, Jean-Baptiste Onofré 
wrote:

> Hi
>
> I guess you missed my message. I gonna deal with CarbonData.
>
> Regards
> JB
>
> On Feb 13, 2017, 19:26, at 19:26, Henry Saputra 
> wrote:
> >Thanks, John. I think CarbonData and SystemML may ready for graduation.
> >
> >Looks like Luciano will work with SystemML, then I will work with
> >CarbonData.
> >
> >- Henry
> >
> >On Mon, Feb 13, 2017 at 4:28 AM, John D. Ament 
> >wrote:
> >
> >> All,
> >>
> >> As mentioned in this month's report, there are 63 active podlings.
> >While
> >> I've been chasing retiring podlings, I think it would be good for the
> >> community as a whole to look closely as podlings and see what we can
> >do to
> >> graduate podlings that seem to be doing well.
> >>
> >> Take a look at the last two reports:
> >>
> >> https://wiki.apache.org/incubator/February2017
> >> https://wiki.apache.org/incubator/January2017
> >>
> >> Last month, I listed 4 podlings that appear to have completed all
> >> graduation requirements, but remain in the incubator (Airflow,
> >BatchEE,
> >> Freemarker, Metron).  I didn't include that in February, but if I had
> >to
> >> list the names, it would be: CarbonData, Edgent, Fineract, Guacamole,
> >> PredictionIO, SystemML, Tamaya, Unomi (but that's entirely my
> >POV/opinion
> >> unless others want to chime in).
> >>
> >> So I'm curious, what can others do to help these 12 podlings get past
> >the
> >> finish line?
> >>
> >> John
> >>
>

Re: Podling Graduation Rally

[Katherine Marsden]

On 2/13/17 4:28 AM, John D. Ament wrote:
 I didn't include that in February, but if I had to

list the names, it would be: CarbonData, Edgent ...




So I'm curious, what can others do to help these 12 podlings get past the
finish line?



I started a discussion on the Edgent list and included my 
recommendations [1].  Thanks for starting the rally.  It is a great kick 
to do what we need to as you say get to the finish line.


Best

Kathey

[1] 
https://lists.apache.org/thread.html/8f10fa966580b4cc1b6119f287c00906a75a526c14ecb507fdf3e7f4@%3Cdev.edgent.apache.org%3E







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

Re: Podling Graduation Rally

[John D. Ament]

Upayavira,

I've pinged the podling in the past about graduation.  *I* think you're
ready.

On Mon, Feb 13, 2017 at 6:15 PM Upayavira  wrote:

> I would appreciate assistance in deciding whether Wave needs more than
> its current slow, but not stationary, development.
>
> Upayavira
>
> On Mon, 13 Feb 2017, at 06:07 PM, John D. Ament wrote:
> > Awesome news, thanks everyone.
> >
> > On Mon, Feb 13, 2017 at 12:17 PM Suneel Marthi 
> > wrote:
> >
> > > Streams was also called as 'Ready to graduate' in the December report.
> > >
> > > Since Oct 2016, the podling has had 3 releases and another release is
> > > planned for this weekend.
> > >
> > > There have been discussions on the podIing mail lists about graduation
> > > following the next planned release. I can help push forward Streams
> > > graduation and the podling has satisfied most of the Apache Maturity
> > > Assessment -  see
> > >
> > >
> https://cwiki.apache.org/confluence/display/STREAMS/Apache+Maturity+Model+Assessment+for+Streams
> > >
> > >
> > >
> > >
> > > On Mon, Feb 13, 2017 at 7:51 AM, Pierre Smits 
> > > wrote:
> > >
> > > > Hi John,
> > > >
> > > > Thank you for bringing this to our attention. I guess it should be
> > > brought
> > > > back regularly so that participants here stay on the ball.
> > > >
> > > > That being said, I believe Trafodion should also be considered to be
> > > ready.
> > > >
> > > > Best regards,
> > > >
> > > > Pierre Smits
> > > >
> > > > ORRTIZ.COM 
> > > > OFBiz based solutions & services
> > > >
> > > > OFBiz Extensions Marketplace
> > > > http://oem.ofbizci.net/oci-2/
> > > >
> > > > On Mon, Feb 13, 2017 at 1:28 PM, John D. Ament <
> johndam...@apache.org>
> > > > wrote:
> > > >
> > > > > All,
> > > > >
> > > > > As mentioned in this month's report, there are 63 active podlings.
> > > While
> > > > > I've been chasing retiring podlings, I think it would be good for
> the
> > > > > community as a whole to look closely as podlings and see what we
> can do
> > > > to
> > > > > graduate podlings that seem to be doing well.
> > > > >
> > > > > Take a look at the last two reports:
> > > > >
> > > > > https://wiki.apache.org/incubator/February2017
> > > > > https://wiki.apache.org/incubator/January2017
> > > > >
> > > > > Last month, I listed 4 podlings that appear to have completed all
> > > > > graduation requirements, but remain in the incubator (Airflow,
> BatchEE,
> > > > > Freemarker, Metron).  I didn't include that in February, but if I
> had
> > > to
> > > > > list the names, it would be: CarbonData, Edgent, Fineract,
> Guacamole,
> > > > > PredictionIO, SystemML, Tamaya, Unomi (but that's entirely my
> > > POV/opinion
> > > > > unless others want to chime in).
> > > > >
> > > > > So I'm curious, what can others do to help these 12 podlings get
> past
> > > the
> > > > > finish line?
> > > > >
> > > > > John
> > > > >
> > > >
> > >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Podling Graduation Rally

[Pierre Smits]

Hi Upayariva,

Maybe I am kicking an open door, but the mere 'whether Wave needs more than
its current slow, but not stationary, development' indicates that you
believe that it requires more than that to grow and graduate from our
incubator.

What is the focus of the PPMC? How is the project doing promotion-wise?

Best regards,

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Tue, Feb 14, 2017 at 12:15 AM, Upayavira  wrote:

> I would appreciate assistance in deciding whether Wave needs more than
> its current slow, but not stationary, development.
>
> Upayavira
>
> On Mon, 13 Feb 2017, at 06:07 PM, John D. Ament wrote:
> > Awesome news, thanks everyone.
> >
> > On Mon, Feb 13, 2017 at 12:17 PM Suneel Marthi 
> > wrote:
> >
> > > Streams was also called as 'Ready to graduate' in the December report.
> > >
> > > Since Oct 2016, the podling has had 3 releases and another release is
> > > planned for this weekend.
> > >
> > > There have been discussions on the podIing mail lists about graduation
> > > following the next planned release. I can help push forward Streams
> > > graduation and the podling has satisfied most of the Apache Maturity
> > > Assessment -  see
> > >
> > > https://cwiki.apache.org/confluence/display/STREAMS/
> Apache+Maturity+Model+Assessment+for+Streams
> > >
> > >
> > >
> > >
> > > On Mon, Feb 13, 2017 at 7:51 AM, Pierre Smits 
> > > wrote:
> > >
> > > > Hi John,
> > > >
> > > > Thank you for bringing this to our attention. I guess it should be
> > > brought
> > > > back regularly so that participants here stay on the ball.
> > > >
> > > > That being said, I believe Trafodion should also be considered to be
> > > ready.
> > > >
> > > > Best regards,
> > > >
> > > > Pierre Smits
> > > >
> > > > ORRTIZ.COM 
> > > > OFBiz based solutions & services
> > > >
> > > > OFBiz Extensions Marketplace
> > > > http://oem.ofbizci.net/oci-2/
> > > >
> > > > On Mon, Feb 13, 2017 at 1:28 PM, John D. Ament <
> johndam...@apache.org>
> > > > wrote:
> > > >
> > > > > All,
> > > > >
> > > > > As mentioned in this month's report, there are 63 active podlings.
> > > While
> > > > > I've been chasing retiring podlings, I think it would be good for
> the
> > > > > community as a whole to look closely as podlings and see what we
> can do
> > > > to
> > > > > graduate podlings that seem to be doing well.
> > > > >
> > > > > Take a look at the last two reports:
> > > > >
> > > > > https://wiki.apache.org/incubator/February2017
> > > > > https://wiki.apache.org/incubator/January2017
> > > > >
> > > > > Last month, I listed 4 podlings that appear to have completed all
> > > > > graduation requirements, but remain in the incubator (Airflow,
> BatchEE,
> > > > > Freemarker, Metron).  I didn't include that in February, but if I
> had
> > > to
> > > > > list the names, it would be: CarbonData, Edgent, Fineract,
> Guacamole,
> > > > > PredictionIO, SystemML, Tamaya, Unomi (but that's entirely my
> > > POV/opinion
> > > > > unless others want to chime in).
> > > > >
> > > > > So I'm curious, what can others do to help these 12 podlings get
> past
> > > the
> > > > > finish line?
> > > > >
> > > > > John
> > > > >
> > > >
> > >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Podling Graduation Rally

[Jean-Baptiste Onofré]

Hi

I guess you missed my message. I gonna deal with CarbonData.

Regards
JB

On Feb 13, 2017, 19:26, at 19:26, Henry Saputra  wrote:
>Thanks, John. I think CarbonData and SystemML may ready for graduation.
>
>Looks like Luciano will work with SystemML, then I will work with
>CarbonData.
>
>- Henry
>
>On Mon, Feb 13, 2017 at 4:28 AM, John D. Ament 
>wrote:
>
>> All,
>>
>> As mentioned in this month's report, there are 63 active podlings.
>While
>> I've been chasing retiring podlings, I think it would be good for the
>> community as a whole to look closely as podlings and see what we can
>do to
>> graduate podlings that seem to be doing well.
>>
>> Take a look at the last two reports:
>>
>> https://wiki.apache.org/incubator/February2017
>> https://wiki.apache.org/incubator/January2017
>>
>> Last month, I listed 4 podlings that appear to have completed all
>> graduation requirements, but remain in the incubator (Airflow,
>BatchEE,
>> Freemarker, Metron).  I didn't include that in February, but if I had
>to
>> list the names, it would be: CarbonData, Edgent, Fineract, Guacamole,
>> PredictionIO, SystemML, Tamaya, Unomi (but that's entirely my
>POV/opinion
>> unless others want to chime in).
>>
>> So I'm curious, what can others do to help these 12 podlings get past
>the
>> finish line?
>>
>> John
>>

Re: Podling Graduation Rally

[Henry Saputra]

Thanks, John. I think CarbonData and SystemML may ready for graduation.

Looks like Luciano will work with SystemML, then I will work with
CarbonData.

- Henry

On Mon, Feb 13, 2017 at 4:28 AM, John D. Ament 
wrote:

> All,
>
> As mentioned in this month's report, there are 63 active podlings.  While
> I've been chasing retiring podlings, I think it would be good for the
> community as a whole to look closely as podlings and see what we can do to
> graduate podlings that seem to be doing well.
>
> Take a look at the last two reports:
>
> https://wiki.apache.org/incubator/February2017
> https://wiki.apache.org/incubator/January2017
>
> Last month, I listed 4 podlings that appear to have completed all
> graduation requirements, but remain in the incubator (Airflow, BatchEE,
> Freemarker, Metron).  I didn't include that in February, but if I had to
> list the names, it would be: CarbonData, Edgent, Fineract, Guacamole,
> PredictionIO, SystemML, Tamaya, Unomi (but that's entirely my POV/opinion
> unless others want to chime in).
>
> So I'm curious, what can others do to help these 12 podlings get past the
> finish line?
>
> John
>

Re: Podling Graduation Rally

[Upayavira]

I would appreciate assistance in deciding whether Wave needs more than
its current slow, but not stationary, development.

Upayavira

On Mon, 13 Feb 2017, at 06:07 PM, John D. Ament wrote:
> Awesome news, thanks everyone.
> 
> On Mon, Feb 13, 2017 at 12:17 PM Suneel Marthi 
> wrote:
> 
> > Streams was also called as 'Ready to graduate' in the December report.
> >
> > Since Oct 2016, the podling has had 3 releases and another release is
> > planned for this weekend.
> >
> > There have been discussions on the podIing mail lists about graduation
> > following the next planned release. I can help push forward Streams
> > graduation and the podling has satisfied most of the Apache Maturity
> > Assessment -  see
> >
> > https://cwiki.apache.org/confluence/display/STREAMS/Apache+Maturity+Model+Assessment+for+Streams
> >
> >
> >
> >
> > On Mon, Feb 13, 2017 at 7:51 AM, Pierre Smits 
> > wrote:
> >
> > > Hi John,
> > >
> > > Thank you for bringing this to our attention. I guess it should be
> > brought
> > > back regularly so that participants here stay on the ball.
> > >
> > > That being said, I believe Trafodion should also be considered to be
> > ready.
> > >
> > > Best regards,
> > >
> > > Pierre Smits
> > >
> > > ORRTIZ.COM 
> > > OFBiz based solutions & services
> > >
> > > OFBiz Extensions Marketplace
> > > http://oem.ofbizci.net/oci-2/
> > >
> > > On Mon, Feb 13, 2017 at 1:28 PM, John D. Ament 
> > > wrote:
> > >
> > > > All,
> > > >
> > > > As mentioned in this month's report, there are 63 active podlings.
> > While
> > > > I've been chasing retiring podlings, I think it would be good for the
> > > > community as a whole to look closely as podlings and see what we can do
> > > to
> > > > graduate podlings that seem to be doing well.
> > > >
> > > > Take a look at the last two reports:
> > > >
> > > > https://wiki.apache.org/incubator/February2017
> > > > https://wiki.apache.org/incubator/January2017
> > > >
> > > > Last month, I listed 4 podlings that appear to have completed all
> > > > graduation requirements, but remain in the incubator (Airflow, BatchEE,
> > > > Freemarker, Metron).  I didn't include that in February, but if I had
> > to
> > > > list the names, it would be: CarbonData, Edgent, Fineract, Guacamole,
> > > > PredictionIO, SystemML, Tamaya, Unomi (but that's entirely my
> > POV/opinion
> > > > unless others want to chime in).
> > > >
> > > > So I'm curious, what can others do to help these 12 podlings get past
> > the
> > > > finish line?
> > > >
> > > > John
> > > >
> > >
> >

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

Re: Podling Graduation Rally

[John D. Ament]

Awesome news, thanks everyone.

On Mon, Feb 13, 2017 at 12:17 PM Suneel Marthi  wrote:

> Streams was also called as 'Ready to graduate' in the December report.
>
> Since Oct 2016, the podling has had 3 releases and another release is
> planned for this weekend.
>
> There have been discussions on the podIing mail lists about graduation
> following the next planned release. I can help push forward Streams
> graduation and the podling has satisfied most of the Apache Maturity
> Assessment -  see
>
> https://cwiki.apache.org/confluence/display/STREAMS/Apache+Maturity+Model+Assessment+for+Streams
>
>
>
>
> On Mon, Feb 13, 2017 at 7:51 AM, Pierre Smits 
> wrote:
>
> > Hi John,
> >
> > Thank you for bringing this to our attention. I guess it should be
> brought
> > back regularly so that participants here stay on the ball.
> >
> > That being said, I believe Trafodion should also be considered to be
> ready.
> >
> > Best regards,
> >
> > Pierre Smits
> >
> > ORRTIZ.COM 
> > OFBiz based solutions & services
> >
> > OFBiz Extensions Marketplace
> > http://oem.ofbizci.net/oci-2/
> >
> > On Mon, Feb 13, 2017 at 1:28 PM, John D. Ament 
> > wrote:
> >
> > > All,
> > >
> > > As mentioned in this month's report, there are 63 active podlings.
> While
> > > I've been chasing retiring podlings, I think it would be good for the
> > > community as a whole to look closely as podlings and see what we can do
> > to
> > > graduate podlings that seem to be doing well.
> > >
> > > Take a look at the last two reports:
> > >
> > > https://wiki.apache.org/incubator/February2017
> > > https://wiki.apache.org/incubator/January2017
> > >
> > > Last month, I listed 4 podlings that appear to have completed all
> > > graduation requirements, but remain in the incubator (Airflow, BatchEE,
> > > Freemarker, Metron).  I didn't include that in February, but if I had
> to
> > > list the names, it would be: CarbonData, Edgent, Fineract, Guacamole,
> > > PredictionIO, SystemML, Tamaya, Unomi (but that's entirely my
> POV/opinion
> > > unless others want to chime in).
> > >
> > > So I'm curious, what can others do to help these 12 podlings get past
> the
> > > finish line?
> > >
> > > John
> > >
> >
>

Re: Podling Graduation Rally

[Suneel Marthi]

Streams was also called as 'Ready to graduate' in the December report.

Since Oct 2016, the podling has had 3 releases and another release is
planned for this weekend.

There have been discussions on the podIing mail lists about graduation
following the next planned release. I can help push forward Streams
graduation and the podling has satisfied most of the Apache Maturity
Assessment -  see
https://cwiki.apache.org/confluence/display/STREAMS/Apache+Maturity+Model+Assessment+for+Streams




On Mon, Feb 13, 2017 at 7:51 AM, Pierre Smits 
wrote:

> Hi John,
>
> Thank you for bringing this to our attention. I guess it should be brought
> back regularly so that participants here stay on the ball.
>
> That being said, I believe Trafodion should also be considered to be ready.
>
> Best regards,
>
> Pierre Smits
>
> ORRTIZ.COM 
> OFBiz based solutions & services
>
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/
>
> On Mon, Feb 13, 2017 at 1:28 PM, John D. Ament 
> wrote:
>
> > All,
> >
> > As mentioned in this month's report, there are 63 active podlings.  While
> > I've been chasing retiring podlings, I think it would be good for the
> > community as a whole to look closely as podlings and see what we can do
> to
> > graduate podlings that seem to be doing well.
> >
> > Take a look at the last two reports:
> >
> > https://wiki.apache.org/incubator/February2017
> > https://wiki.apache.org/incubator/January2017
> >
> > Last month, I listed 4 podlings that appear to have completed all
> > graduation requirements, but remain in the incubator (Airflow, BatchEE,
> > Freemarker, Metron).  I didn't include that in February, but if I had to
> > list the names, it would be: CarbonData, Edgent, Fineract, Guacamole,
> > PredictionIO, SystemML, Tamaya, Unomi (but that's entirely my POV/opinion
> > unless others want to chime in).
> >
> > So I'm curious, what can others do to help these 12 podlings get past the
> > finish line?
> >
> > John
> >
>

Re: Podling Graduation Rally

[P. Taylor Goetz]

I can help with pushing Metron forward. They have been discussing graduation 
for a while now.

-Taylor


> On Feb 13, 2017, at 7:28 AM, John D. Ament  wrote:
> 
> All,
> 
> As mentioned in this month's report, there are 63 active podlings.  While
> I've been chasing retiring podlings, I think it would be good for the
> community as a whole to look closely as podlings and see what we can do to
> graduate podlings that seem to be doing well.
> 
> Take a look at the last two reports:
> 
> https://wiki.apache.org/incubator/February2017
> https://wiki.apache.org/incubator/January2017
> 
> Last month, I listed 4 podlings that appear to have completed all
> graduation requirements, but remain in the incubator (Airflow, BatchEE,
> Freemarker, Metron).  I didn't include that in February, but if I had to
> list the names, it would be: CarbonData, Edgent, Fineract, Guacamole,
> PredictionIO, SystemML, Tamaya, Unomi (but that's entirely my POV/opinion
> unless others want to chime in).
> 
> So I'm curious, what can others do to help these 12 podlings get past the
> finish line?
> 
> John


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

Re: Podling Graduation Rally

[Donald Szeto]

Thanks John for bringing this up! I will kick off and drive a discussion on
graduating PredictionIO.

Regards,
Donald

On Mon, Feb 13, 2017 at 4:28 AM John D. Ament  wrote:

> All,
>
> As mentioned in this month's report, there are 63 active podlings.  While
> I've been chasing retiring podlings, I think it would be good for the
> community as a whole to look closely as podlings and see what we can do to
> graduate podlings that seem to be doing well.
>
> Take a look at the last two reports:
>
> https://wiki.apache.org/incubator/February2017
> https://wiki.apache.org/incubator/January2017
>
> Last month, I listed 4 podlings that appear to have completed all
> graduation requirements, but remain in the incubator (Airflow, BatchEE,
> Freemarker, Metron).  I didn't include that in February, but if I had to
> list the names, it would be: CarbonData, Edgent, Fineract, Guacamole,
> PredictionIO, SystemML, Tamaya, Unomi (but that's entirely my POV/opinion
> unless others want to chime in).
>
> So I'm curious, what can others do to help these 12 podlings get past the
> finish line?
>
> John
>

Re: Podling Graduation Rally

[Pierre Smits]

The discussion @ Trafodion has been kicked off.

Best regards,

Pierre

On Monday, February 13, 2017, John D. Ament  wrote:

> Pierre,
>
> You're probably correct.  I only went through this month/last month, not
> the prior month so no one from group 3 would have been in my email.
>
> With that said, knowing that you're on Trafodion, what are you doing to
> help Trafodion graduate? Is anyone bringing up the discussion?  My point
> with this email - podlings need to take it upon themselves to graduate, the
> most the IPMC can be doing is nudging along.  We only provide a
> recommendation vote.
>
> John
>
> On Mon, Feb 13, 2017 at 7:52 AM Pierre Smits  > wrote:
>
> > Hi John,
> >
> > Thank you for bringing this to our attention. I guess it should be
> brought
> > back regularly so that participants here stay on the ball.
> >
> > That being said, I believe Trafodion should also be considered to be
> ready.
> >
> > Best regards,
> >
> > Pierre Smits
> >
> > ORRTIZ.COM 
> > OFBiz based solutions & services
> >
> > OFBiz Extensions Marketplace
> > http://oem.ofbizci.net/oci-2/
> >
> > On Mon, Feb 13, 2017 at 1:28 PM, John D. Ament  >
> > wrote:
> >
> > > All,
> > >
> > > As mentioned in this month's report, there are 63 active podlings.
> While
> > > I've been chasing retiring podlings, I think it would be good for the
> > > community as a whole to look closely as podlings and see what we can do
> > to
> > > graduate podlings that seem to be doing well.
> > >
> > > Take a look at the last two reports:
> > >
> > > https://wiki.apache.org/incubator/February2017
> > > https://wiki.apache.org/incubator/January2017
> > >
> > > Last month, I listed 4 podlings that appear to have completed all
> > > graduation requirements, but remain in the incubator (Airflow, BatchEE,
> > > Freemarker, Metron).  I didn't include that in February, but if I had
> to
> > > list the names, it would be: CarbonData, Edgent, Fineract, Guacamole,
> > > PredictionIO, SystemML, Tamaya, Unomi (but that's entirely my
> POV/opinion
> > > unless others want to chime in).
> > >
> > > So I'm curious, what can others do to help these 12 podlings get past
> the
> > > finish line?
> > >
> > > John
> > >
> >
>


-- 
Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

Re: Podling Graduation Rally

[Luciano Resende]

I will start the discussions/process with SystemML.

On Mon, Feb 13, 2017 at 4:29 AM John D. Ament  wrote:

> All,
>
> As mentioned in this month's report, there are 63 active podlings.  While
> I've been chasing retiring podlings, I think it would be good for the
> community as a whole to look closely as podlings and see what we can do to
> graduate podlings that seem to be doing well.
>
> Take a look at the last two reports:
>
> https://wiki.apache.org/incubator/February2017
> https://wiki.apache.org/incubator/January2017
>
> Last month, I listed 4 podlings that appear to have completed all
> graduation requirements, but remain in the incubator (Airflow, BatchEE,
> Freemarker, Metron).  I didn't include that in February, but if I had to
> list the names, it would be: CarbonData, Edgent, Fineract, Guacamole,
> PredictionIO, SystemML, Tamaya, Unomi (but that's entirely my POV/opinion
> unless others want to chime in).
>
> So I'm curious, what can others do to help these 12 podlings get past the
> finish line?
>
> John
>
-- 
Sent from my Mobile device

Re: Podling Graduation Rally

[Pierre Smits]

Hi John,

I am aware that you have a lot on your plate. So don't regard this as
(negative) criticism.

Re: Trafodion and graduation and what I am doing there.
As I am not on the PPMC the only thing I can do is the same as you have
stated to be in the realm of the IPMC: nudging along. So, that is going to
happen shortly (start the discussion again).

Best regards,



Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Mon, Feb 13, 2017 at 2:14 PM, John D. Ament 
wrote:

> Pierre,
>
> You're probably correct.  I only went through this month/last month, not
> the prior month so no one from group 3 would have been in my email.
>
> With that said, knowing that you're on Trafodion, what are you doing to
> help Trafodion graduate? Is anyone bringing up the discussion?  My point
> with this email - podlings need to take it upon themselves to graduate, the
> most the IPMC can be doing is nudging along.  We only provide a
> recommendation vote.
>
> John
>
> On Mon, Feb 13, 2017 at 7:52 AM Pierre Smits 
> wrote:
>
> > Hi John,
> >
> > Thank you for bringing this to our attention. I guess it should be
> brought
> > back regularly so that participants here stay on the ball.
> >
> > That being said, I believe Trafodion should also be considered to be
> ready.
> >
> > Best regards,
> >
> > Pierre Smits
> >
> > ORRTIZ.COM 
> > OFBiz based solutions & services
> >
> > OFBiz Extensions Marketplace
> > http://oem.ofbizci.net/oci-2/
> >
> > On Mon, Feb 13, 2017 at 1:28 PM, John D. Ament 
> > wrote:
> >
> > > All,
> > >
> > > As mentioned in this month's report, there are 63 active podlings.
> While
> > > I've been chasing retiring podlings, I think it would be good for the
> > > community as a whole to look closely as podlings and see what we can do
> > to
> > > graduate podlings that seem to be doing well.
> > >
> > > Take a look at the last two reports:
> > >
> > > https://wiki.apache.org/incubator/February2017
> > > https://wiki.apache.org/incubator/January2017
> > >
> > > Last month, I listed 4 podlings that appear to have completed all
> > > graduation requirements, but remain in the incubator (Airflow, BatchEE,
> > > Freemarker, Metron).  I didn't include that in February, but if I had
> to
> > > list the names, it would be: CarbonData, Edgent, Fineract, Guacamole,
> > > PredictionIO, SystemML, Tamaya, Unomi (but that's entirely my
> POV/opinion
> > > unless others want to chime in).
> > >
> > > So I'm curious, what can others do to help these 12 podlings get past
> the
> > > finish line?
> > >
> > > John
> > >
> >
>

Re: Podling Graduation Rally

[Jean-Baptiste Onofré]

Hi John

Yes for CarbonData we are preparing the graduation resolution proposal.

I try to finalize it for this month report.

I keep you posted.

Regards
JB

On Feb 13, 2017, 08:28, at 08:28, "John D. Ament"  wrote:
>All,
>
>As mentioned in this month's report, there are 63 active podlings.
>While
>I've been chasing retiring podlings, I think it would be good for the
>community as a whole to look closely as podlings and see what we can do
>to
>graduate podlings that seem to be doing well.
>
>Take a look at the last two reports:
>
>https://wiki.apache.org/incubator/February2017
>https://wiki.apache.org/incubator/January2017
>
>Last month, I listed 4 podlings that appear to have completed all
>graduation requirements, but remain in the incubator (Airflow, BatchEE,
>Freemarker, Metron).  I didn't include that in February, but if I had
>to
>list the names, it would be: CarbonData, Edgent, Fineract, Guacamole,
>PredictionIO, SystemML, Tamaya, Unomi (but that's entirely my
>POV/opinion
>unless others want to chime in).
>
>So I'm curious, what can others do to help these 12 podlings get past
>the
>finish line?
>
>John

Re: Podling Graduation Rally

[John D. Ament]

Pierre,

You're probably correct.  I only went through this month/last month, not
the prior month so no one from group 3 would have been in my email.

With that said, knowing that you're on Trafodion, what are you doing to
help Trafodion graduate? Is anyone bringing up the discussion?  My point
with this email - podlings need to take it upon themselves to graduate, the
most the IPMC can be doing is nudging along.  We only provide a
recommendation vote.

John

On Mon, Feb 13, 2017 at 7:52 AM Pierre Smits  wrote:

> Hi John,
>
> Thank you for bringing this to our attention. I guess it should be brought
> back regularly so that participants here stay on the ball.
>
> That being said, I believe Trafodion should also be considered to be ready.
>
> Best regards,
>
> Pierre Smits
>
> ORRTIZ.COM 
> OFBiz based solutions & services
>
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/
>
> On Mon, Feb 13, 2017 at 1:28 PM, John D. Ament 
> wrote:
>
> > All,
> >
> > As mentioned in this month's report, there are 63 active podlings.  While
> > I've been chasing retiring podlings, I think it would be good for the
> > community as a whole to look closely as podlings and see what we can do
> to
> > graduate podlings that seem to be doing well.
> >
> > Take a look at the last two reports:
> >
> > https://wiki.apache.org/incubator/February2017
> > https://wiki.apache.org/incubator/January2017
> >
> > Last month, I listed 4 podlings that appear to have completed all
> > graduation requirements, but remain in the incubator (Airflow, BatchEE,
> > Freemarker, Metron).  I didn't include that in February, but if I had to
> > list the names, it would be: CarbonData, Edgent, Fineract, Guacamole,
> > PredictionIO, SystemML, Tamaya, Unomi (but that's entirely my POV/opinion
> > unless others want to chime in).
> >
> > So I'm curious, what can others do to help these 12 podlings get past the
> > finish line?
> >
> > John
> >
>

Podling Graduation Rally

[John D. Ament]

All,

As mentioned in this month's report, there are 63 active podlings.  While
I've been chasing retiring podlings, I think it would be good for the
community as a whole to look closely as podlings and see what we can do to
graduate podlings that seem to be doing well.

Take a look at the last two reports:

https://wiki.apache.org/incubator/February2017
https://wiki.apache.org/incubator/January2017

Last month, I listed 4 podlings that appear to have completed all
graduation requirements, but remain in the incubator (Airflow, BatchEE,
Freemarker, Metron).  I didn't include that in February, but if I had to
list the names, it would be: CarbonData, Edgent, Fineract, Guacamole,
PredictionIO, SystemML, Tamaya, Unomi (but that's entirely my POV/opinion
unless others want to chime in).

So I'm curious, what can others do to help these 12 podlings get past the
finish line?

John