Re: [Incubator Wiki] Update of "October2016" by GinoBustelo

[Gino Bustelo]

Rookie mistake. I did not see the Final notice and the top and thought I
could add our update.

On Mon, Oct 10, 2016 at 10:20 AM John D. Ament 
wrote:

> Yesterday was the last day for sign off.  Could someone from Toree explain
> the addition?
>
> On Oct 10, 2016 11:13, "Apache Wiki"  wrote:
>
> > Dear Wiki user,
> >
> > You have subscribed to a wiki page or wiki category on "Incubator Wiki"
> > for change notification.
> >
> > The "October2016" page has been changed by GinoBustelo:
> >
> https://wiki.apache.org/incubator/October2016?action=diff=54=55
> >
> >   ||[none] ||Quickstep ||
> >   ||[none] ||Rya ||
> >   ||[none] ||Tamaya ||
> > + ||[none] ||Toree ||
> >
> >
> >   === Report content ===
> > @@ -174, +175 @@
> >
> >   Streams
> >   Tamaya
> >   Traffic Control
> > + Toree
> >
> >   --
> >
> > @@ -1396, +1398 @@
> >
> >   The project has room to improve.  With the loss of mentors and
> > existing committers, need help mentoring this project.
> >
> >   
> > + Toree
> > +
> > + Toree provides applications with a mechanism to interactively and
> > remotely
> > + access Apache Spark. It enables interactive workloads between
> > applications
> > + and a Spark cluster. As a Jupyter Notebook extension, it provides the
> > user
> > + with a preconfigured environment for interacting with Spark using
> Scala,
> > + Python, R or SQL.
> > +
> > + Toree has been incubating since 2015-12-02.
> > +
> > + Three most important issues to address in the move towards graduation:
> > +
> > +   1. Resolve LGPL dependency: RESOLVED! Library is not released as MPL
> > v2 and necessary changes made in Toree
> > +   2. Make a release: 0.1.x branch should be ready for release. Master
> has
> > +  moved to start support for Spark 2.0
> > +   3. Grow a diverse community: We should put some emphasis on growing
> the
> > +  community and making it diverse (the rule is at least three
> > independent
> > +  contributors) In process. Got one new candidate for committer.
> > +
> > + Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > + aware of?
> > +
> > +   TOREE-262 - Progress on removal of LGPL dependency - Awaiting MPL
> > release
> > +   of JeroMQ. RESOLVED!
> > +
> > + How has the community developed since the last report?
> > +
> > +   1. Active communication in mailing list and gitter with early
> adopters
> > +   2. Still working on transitioning users from Spark Kernel project
> into
> > +  Toree. Making significant progress here.
> > +   3. More external contributions being made. Spark 2 port done by
> > outside contributor and merged into master
> > +
> > + How has the project developed since the last report?
> > +
> > +   1. JeroMQ community has finalized work to transition to MPL. Release
> > available and changes made in Toree src
> > +   2. Addressing issues opened by community
> > +
> > + Date of last release:
> > +
> > +   None since incubation.
> > +
> > + When were the last committers or PMC members elected?
> > +
> > +   No new additions since incubation
> > +
> > + Signed-off-by:
> > +
> > +   [ ](toree) Luciano Resende
> > +   [ ](toree) Reynold Xin
> > +   [ ](toree) Hitesh Shah
> > +   [ ](toree) Julien Le Dem
> > +
> > + 
> >   Traffic Control
> >
> >   Traffic Control allows you to build a large scale content delivery
> > network
> >
> > -
> > To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: cvs-h...@incubator.apache.org
> >
> >
>

Re: [DRAFT] Incubator PMC Board Report - October 2016

[Gino Bustelo]

Guys,

I'm sorry if this cause great confusion. I skimmed the wiki and noticed
that it still was not marked final. Rookie mistake to edit it.

On Mon, Oct 10, 2016 at 11:04 AM John D. Ament 
wrote:

> Generally speaking, the first report is always a series of "Still getting
> started."  At this point, I'd prefer to not add new reports (not
> comfortable with the Toree change), since the deadline was last Wednesday.
> But others can voice their opinions as well.
>
> John
>
> On Mon, Oct 10, 2016 at 3:12 AM Bertrand Delacretaz <
> bdelacre...@apache.org>
> wrote:
>
> > Hi,
> >
> >
> >
> > On Sun, Oct 9, 2016 at 10:09 PM, John D. Ament 
> > wrote:
> >
> > > ...Below is the current draft of the board report...
> >
> >
> >
> > If you want I can add a brief report about NetBeans but there's not
> >
> > much to say, it's really just getting started, the code grant is not
> >
> > in yet so we'll have more to say next month.
> >
> >
> >
> > -Bertrand
> >
> >
> >
> > -
> >
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
> >
> >
>

Toree's LGPL Dependency resolved!

[Gino Bustelo]

Just wanted to announce that the Apache Toree team was able to work with
the JeroMQ (https://github.com/zeromq/jeromq) team to get their library
relicensed as MPL v2. This is a key milestone for the Toree project, as it
allow us to produce regular releases.

This is a great example of inter-OSS communities working together.

Github Mirror

[Gino Bustelo]

Not sure what I'm missing, but I did some branch cleanup on the Toree repo
and I'm not seeing them taking effect on the github mirror.

I confirms that other users can fetch upstream and see my new branch, but I
do not see it in github. What am I missing?

Thanks,
Gino

Re: Toree's One Release Constraint

[Gino Bustelo]

@shane

As part of building, we put together a more comprehensive LICENSE and
NOTICE file that includes the extra information under
https://github.com/apache/incubator-toree/blob/master/etc/legal/LICENSE_extras.
The installer of the pip package prints out the LGPL disclaimer during
installation. We could certainly also place a more prominent statement in
the README. The website is still under development and we can also provide
a disclaimer there. I take any other recommendations.



On Fri, May 20, 2016 at 2:37 PM, Shane Curcuru <a...@shanecurcuru.org> wrote:

> Gino Bustelo wrote on 5/19/16 12:30 PM:
> ...
> > In Toree we have an LGPL dependency that is not a simple rip an replace.
> > The library is JeroMQ and it is a JVM binding to 0MQ. This is THE
> protocol
> > layer used in Jupyter between clients and kernels (Toree serves as a
> > Jupyter kernel). Over the past months, we've worked with the JeroMQ
> > community to help move along a license change to MPL v2 (
> > https://github.com/zeromq/jeromq/issues/327). The progress showed huge
> > promised at the start and we are down to 3 committers out of 31 who have
> > not responded. The JeroMQ community is moving towards code remediation.
>
> If LGPL code is included either in your source tree or in your existing
> release(s), why isn't that reflected in a top-level LICENSE and NOTICE
> file?
>
> From reading the homepage of the website and quickly browsing the source
> tree, the only reference is in DISCLAIMER, which is awfully small.  It
> wasn't obvious to me besides that tiny bit that you include some LGPL code.
>
> Or am I missing how this dependency works?
>
> Yes, I agree that incubation is a process, and there is great progress
> both here and in the other project towards an Apache-license-harmonious
> outcome.  But we need to be very careful that end-users have a
> crystal-clear understanding that there is copyleft style licenses in
> releases or dependencies of anything at Apache.
>
> - Shane
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Toree's One Release Constraint

[Gino Bustelo]

"one release constraint" as in we can only have one release with the LGPL
dependency. No other release until that dependency is resolved.

On Thu, May 19, 2016 at 1:33 PM, Mike Jumper <mike.jum...@guac-dev.org>
wrote:

> On May 19, 2016 10:30 AM, "Gino Bustelo" <g...@bustelos.com> wrote:
> >
> > I write this to start a discussion about the "One release constraint"
> > placed on Toree and what I feel is an unreasonable constraint on a
> project
> > that is undergoing incubation. A brief background first...
> >
> > In Toree we have an LGPL dependency that is not a simple rip an replace.
> > The library is JeroMQ and it is a JVM binding to 0MQ. This is THE
> protocol
> > layer used in Jupyter between clients and kernels (Toree serves as a
> > Jupyter kernel). Over the past months, we've worked with the JeroMQ
> > community to help move along a license change to MPL v2 (
> > https://github.com/zeromq/jeromq/issues/327). The progress showed huge
> > promised at the start and we are down to 3 committers out of 31 who have
> > not responded. The JeroMQ community is moving towards code remediation.
> >
> > In my opinion, this effort shows great inter-OS community cooperation and
> > something that should be valued by Apache. Why rewrite and maintain code
> > that already exist? Why not allow the process to take place? Isn't that
> > what the incubation period is for? Allow projects to resolve concerns
> > before they graduate?
> >
> > So my question is, why one release? This has been our biggest impediment
> in
> > putting an official incubation release out. We are ready. We have all the
> > disclaimer in place alerting the user that Toree contains LGPL code. The
> > biggest concern is releasing and discovering a defect that we would not
> be
> > able to fix due to the "One release constraint".
> >
> > Again... I just wish to start the discussion and find a resolution that
> > will allow Toree to properly grow and move forward with its incubation.
> >
> > Thanks,
> > Gino
>
> Hi Gino,
>
> What "one release constraint" are you referring to?
>
> Thanks,
>
> - Mike
>

Toree's One Release Constraint

[Gino Bustelo]

I write this to start a discussion about the "One release constraint"
placed on Toree and what I feel is an unreasonable constraint on a project
that is undergoing incubation. A brief background first...

In Toree we have an LGPL dependency that is not a simple rip an replace.
The library is JeroMQ and it is a JVM binding to 0MQ. This is THE protocol
layer used in Jupyter between clients and kernels (Toree serves as a
Jupyter kernel). Over the past months, we've worked with the JeroMQ
community to help move along a license change to MPL v2 (
https://github.com/zeromq/jeromq/issues/327). The progress showed huge
promised at the start and we are down to 3 committers out of 31 who have
not responded. The JeroMQ community is moving towards code remediation.

In my opinion, this effort shows great inter-OS community cooperation and
something that should be valued by Apache. Why rewrite and maintain code
that already exist? Why not allow the process to take place? Isn't that
what the incubation period is for? Allow projects to resolve concerns
before they graduate?

So my question is, why one release? This has been our biggest impediment in
putting an official incubation release out. We are ready. We have all the
disclaimer in place alerting the user that Toree contains LGPL code. The
biggest concern is releasing and discovering a defect that we would not be
able to fix due to the "One release constraint".

Again... I just wish to start the discussion and find a resolution that
will allow Toree to properly grow and move forward with its incubation.

Thanks,
Gino

Re: Need access to Incubator Wiki

[Gino Bustelo]

Ok... so then lets try it with user 'GinoBustelo'

On Mon, Apr 4, 2016 at 1:33 PM, Nick Burch <n...@apache.org> wrote:

> On Mon, 4 Apr 2016, Gino Bustelo wrote:
>
>> I tried to log in with 'lbustelo'. I don't have a password so I asked it
>> to be sent this morning. Still no mail.
>>
>
> Normally the process is to create an account, setting your password at
> that time, then ask us to grant that new account wiki karma
>
> What happens when you try with the password you gave when you regsitered
> for a wiki account?
>
> (Note - the wiki doesn't use the main Apache ID ldap database!)
>
>
> Nick
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Need access to Incubator Wiki

[Gino Bustelo]

Nick,

I tried to log in with 'lbustelo'. I don't have a password so I asked it to
be sent this morning. Still no mail.

On Thu, Mar 3, 2016 at 10:07 AM, Nick Burch <apa...@gagravarr.org> wrote:

> On Thu, 3 Mar 2016, Gino Bustelo wrote:
>
>> lbustelo
>>
>
> Karma granted, enjoy editing!
>
>
> Nick
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: About docker images

[Gino Bustelo]

Thanks Jake. I'll reach out once we are closer to being ready. 

Gino B.

> On Mar 31, 2016, at 8:38 PM, Jake Farrell <jfarr...@apache.org> wrote:
> 
> We do not enable direct push to Docker hub, we can setup the automated hook
> for building a given Dockerfile at a set path for master or tags, but there
> are no plans to allow direct push at this time. We do have a Bintray
> account which is available for ASF use and we can host Docker images there
> that projects can control if the automated route does not fit the needed
> solution. If you have any questions please let me know
> 
> -Jake
> 
>> On Thu, Mar 31, 2016 at 5:36 PM, Gino Bustelo <g...@bustelos.com> wrote:
>> 
>> What would be the process to push Docker images for an incubator project to
>> https://hub.docker.com/r/apache/?
>> 

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

About docker images

[Gino Bustelo]

What would be the process to push Docker images for an incubator project to
https://hub.docker.com/r/apache/?

Re: Update on Apache Toree and LGPL dependency

[Gino Bustelo]

@john The 0mq ecosystem is made up of many projects of different sizes and 
maturity. In the case of JeroMQ, the committers are showing an overwhelming 
momentum to transition to MPL. I don't see any reason for us to consider any 
other alternative at this juncture. 

Gino B.

> On Mar 5, 2016, at 11:42 PM, Henri Yandell <bay...@apache.org> wrote:
> 
> Having chatted around the 0mq community in the past; I've confidence in
> their desire to move to MPL; and 26/32 committers is a great step forward.
> You raise a good reservation though John - if you remove the blocker on the
> usage side, it's easy for the licensing to remain as is.
> 
> 
> I'm +1 for releasing, with a prominent note of the LGPL dependency (along
> with a note of the resolution plan). It might be that the Toree committers
> may be motivated to rewrite code over at 0mq if there ends up being any
> committers who are unavailable or unwilling to relicense.
> 
> Hen
> 
>> On Sat, Mar 5, 2016 at 3:45 PM, John D. Ament <johndam...@apache.org> wrote:
>> 
>> Sorry, misread the revision I was looking at.  The intent to move to MPL
>> was done on March 22 2014, 2 years ago this month, not December 2013.
>> 
>> John
>> 
>> On Sat, Mar 5, 2016 at 6:41 PM John D. Ament <johndam...@apache.org>
>> wrote:
>> 
>>> I have some reservations with what you're proposing, and would like you
>> to
>>> consult w/ legal-discuss on this first.
>>> 
>>> There's a difference between what Mynewt did and what you're proposing.
>>> Specifically, this was a transitive dependency that they relied upon
>>> indirectly, so its more of a call out for the library that was leveraging
>>> it.  They also intended to replace the library.
>>> 
>>> In your case, you're directly tied to a presently LGPL'd library.  You
>>> have no intentions (from what I can see) of moving off of the library.
>>> 
>>> I'm also doubting their long term goals of moving to MPL.  If you look at
>>> [1], you'll see that the page hasn't been updated since October 2014.  In
>>> addition, looking at the pages revision history (the beauty of wikis),
>> the
>>> intent to move to MPL was published in December 2013, making the
>> statement
>>> over 2 years old.
>>> 
>>> I think while this might be OK for an initial incubator release, the
>>> project needs to weigh very heavily if it wants to continue to leverage
>>> ZeroMQ or not going forward.
>>> 
>>> [1]: http://zeromq.org/area:licensing
>>> 
>>> 
>>>> On Sat, Mar 5, 2016 at 5:06 PM Gino Bustelo <g...@bustelos.com> wrote:
>>>> 
>>>> Wanted to give folks an update on our progress with dealing with JeroMQ,
>>>> an
>>>> LGPL package that enables us to communicate via 0MQ. The 0MQ community
>> is
>>>> very aware of the issues with LGPL (LGPLv3 + static link exception) and
>> it
>>>> is their intention to try to move projects to MPL v2. This is not an
>> easy
>>>> task depending on the age and size of the projects.
>>>> 
>>>> Apache Toree's API access point is through the 0MQ transport layer
>> (using
>>>> JeroMQ) and that is how Apache Toree connects out-of-the-box with
>> Jupyter,
>>>> a very common way of consuming Apache Toree that is already in
>> production.
>>>> 
>>>> At this point, the JeroMQ project is still released under LGPL, but our
>>>> team initiated communications in mid-February with members of the JeroMQ
>>>> community to begin their transition to MPL v2 (
>>>> https://github.com/zeromq/jeromq/issues/326). The JeroMQ community
>>>> reacted
>>>> very positively and quickly began the process of collecting votes from
>>>> their committers (https://github.com/zeromq/jeromq/issues/327). After
>> 15
>>>> days, the current tally stands at 26 out of 32 committers have agreed to
>>>> switch license.
>>>> 
>>>> Apache Toree has a JIRA (
>> https://issues.apache.org/jira/browse/TOREE-262)
>>>> where we keep all the relevant links and update with the latest
>>>> information. As that process is underway, we will move forward with
>> plans
>>>> to release a 0.1.0 version of Apache Toree based on the precedence set
>> by
>>>> Apache Mynewt (
>> http://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3C5F118AA0-4ADA-403B-A6EB-4A85F0B30651%40me.com%3E
>>>> ).
>>>> 
>>>> Thanks,
>>>> Gino
>> 

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

Update on Apache Toree and LGPL dependency

[Gino Bustelo]

Wanted to give folks an update on our progress with dealing with JeroMQ, an
LGPL package that enables us to communicate via 0MQ. The 0MQ community is
very aware of the issues with LGPL (LGPLv3 + static link exception) and it
is their intention to try to move projects to MPL v2. This is not an easy
task depending on the age and size of the projects.

Apache Toree's API access point is through the 0MQ transport layer (using
JeroMQ) and that is how Apache Toree connects out-of-the-box with Jupyter,
a very common way of consuming Apache Toree that is already in production.

At this point, the JeroMQ project is still released under LGPL, but our
team initiated communications in mid-February with members of the JeroMQ
community to begin their transition to MPL v2 (
https://github.com/zeromq/jeromq/issues/326). The JeroMQ community reacted
very positively and quickly began the process of collecting votes from
their committers (https://github.com/zeromq/jeromq/issues/327). After 15
days, the current tally stands at 26 out of 32 committers have agreed to
switch license.

Apache Toree has a JIRA (https://issues.apache.org/jira/browse/TOREE-262)
where we keep all the relevant links and update with the latest
information. As that process is underway, we will move forward with plans
to release a 0.1.0 version of Apache Toree based on the precedence set by
Apache Mynewt (
http://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3C5F118AA0-4ADA-403B-A6EB-4A85F0B30651%40me.com%3E
).

Thanks,
Gino

Need access to Incubator Wiki

[Gino Bustelo]

I need access to be able to push Apache Toree updates.

Re: Update on Apache Toree and LGPL dependency

[Gino Bustelo]

Thanks @stian. I was trying to sell them on the bigger picture that being
able to consume 0MQ within Apache projects would increase their user base.

On Fri, Mar 4, 2016 at 11:13 AM, Stian Soiland-Reyes <st...@apache.org>
wrote:

> I know software licensing can be a difficult thing to investigate, not
> to mention change!
>
> So very well done for managing to influence another open source
> project!  Apache projects don't live in isolation, and participating
> in the wider community is also an important aspect of open
> development.
>
> I guess this might also be a good opportunity to promote Apache Toree
> within 0MQ community :)
>
>
> On 3 March 2016 at 14:58, Gino Bustelo <g...@bustelos.com> wrote:
> > Wanted to give folks an update on our progress with dealing with JeroMQ,
> an
> > LGPL package that enables us to communicate via 0MQ. The 0MQ community is
> > very aware of the issues with LGPL (LGPLv3 + static link exception) and
> it
> > is their intention to try to move projects to MPL v2. This is not an easy
> > task depending on the age and size of the projects.
> >
> > Apache Toree's API access point is through the 0MQ transport layer (using
> > JeroMQ) and that is how Apache Toree connects out-of-the-box with
> Jupyter,
> > a very common way of consuming Apache Toree that is already in
> production.
> >
> > At this point, the JeroMQ project is still released under LGPL, but our
> > team initiated communications in mid-February with members of the JeroMQ
> > community to begin their transition to MPL v2 (
> > https://github.com/zeromq/jeromq/issues/326). The JeroMQ community
> reacted
> > very positively and quickly began the process of collecting votes from
> > their committers (https://github.com/zeromq/jeromq/issues/327). After 15
> > days, the current tally stands at 26 out of 32 committers have agreed to
> > switch license.
> >
> > Apache Toree has a JIRA (https://issues.apache.org/jira/browse/TOREE-262
> )
> > where we keep all the relevant links and update with the latest
> > information. As that process is underway, we will move forward with plans
> > to release a 0.1.0 version of Apache Toree based on the precedence set by
> > Apache Mynewt (
> >
> http://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3C5F118AA0-4ADA-403B-A6EB-4A85F0B30651%40me.com%3E
> > ).
> >
> > Thanks,
> > Gino
>
>
>
> --
> Stian Soiland-Reyes
> Apache Taverna (incubating), Apache Commons RDF (incubating)
> http://orcid.org/-0001-9842-9718
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Need access to Incubator Wiki

[Gino Bustelo]

lbustelo

On Thu, Mar 3, 2016 at 9:07 AM, Nick Burch <apa...@gagravarr.org> wrote:

> On Thu, 3 Mar 2016, Gino Bustelo wrote:
>
>> I need access to be able to push Apache Toree updates.
>>
>
> You'll need to tell us your Incubator wiki username if we're to be able to
> help!
>
> Nick
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Update on Apache Toree and LGPL dependency

[Gino Bustelo]

Wanted to give folks an update on our progress with dealing with JeroMQ, an
LGPL package that enables us to communicate via 0MQ. The 0MQ community is
very aware of the issues with LGPL (LGPLv3 + static link exception) and it
is their intention to try to move projects to MPL v2. This is not an easy
task depending on the age and size of the projects.

Apache Toree's API access point is through the 0MQ transport layer (using
JeroMQ) and that is how Apache Toree connects out-of-the-box with Jupyter,
a very common way of consuming Apache Toree that is already in production.

At this point, the JeroMQ project is still released under LGPL, but our
team initiated communications in mid-February with members of the JeroMQ
community to begin their transition to MPL v2 (
https://github.com/zeromq/jeromq/issues/326). The JeroMQ community reacted
very positively and quickly began the process of collecting votes from
their committers (https://github.com/zeromq/jeromq/issues/327). After 15
days, the current tally stands at 26 out of 32 committers have agreed to
switch license.

Apache Toree has a JIRA (https://issues.apache.org/jira/browse/TOREE-262)
where we keep all the relevant links and update with the latest
information. As that process is underway, we will move forward with plans
to release a 0.1.0 version of Apache Toree based on the precedence set by
Apache Mynewt (
http://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3C5F118AA0-4ADA-403B-A6EB-4A85F0B30651%40me.com%3E
).

Thanks,
Gino

Need access to Incubator Wiki

[Gino Bustelo]

I need access to be able to push Apache Toree updates.