Re: Possible ASF Incubator Project transfer..

[William A Rowe Jr]

On Thu, Mar 3, 2016 at 5:39 PM, Reza Rahman  wrote:

> Yep, understood. We will give it an honest effort
>

No doubt, we appreciate the sincerity.

Note that there are multiple aspect that would require license grants and
provisions
that complicate any Java-ecosystem grant to the ASF.  It isn't strictly
limited to a
given library or framework.  The TCK license terms themselves effectively
killed
more than one ASF effort, and make the consideration/donation of JSR-related
works nearly impossible, at least not as implementation of "named"
specifications
within that ecosystem.  Even a completely renamed/rescoped 'fork' is
questionable.

I find this all highly improbable, but stranger things have happened over
the past
10 years, so if you would like to pursue this, we have the resources to
facilitate
and help frame the scope of grants required to make such an offer happen.

Cheers,

Bill

Re: Update on Apache Toree and LGPL dependency

[Henri Yandell]

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

Re: Possible ASF Incubator Project transfer..

[Greg Stein]

To be clear, we are talking about: http://www.apache.org/licenses/#grants

On Thu, Mar 3, 2016 at 5:39 PM, Reza Rahman  wrote:

> Yep, understood. We will give it an honest effort.
>
> Sent from my iPhone
>
> > On Mar 3, 2016, at 6:30 PM, John D. Ament  wrote:
> >
> > You need to start with convincing oracle to provide an SGA for the
> entire glassfish codebase.  Your best bet is to start that before you leave
> oracle.
> >
> > John
> >
> >> On Thu, Mar 3, 2016 at 4:08 PM Reza Rahman 
> wrote:
> >> Obviously I need to take this up in earnest after Friday. In the
> meanwhile let me know what I need to do in order to get myself setup for
> this.
> >>
> >> Anything that is worth it is never easy. This matters enough to try and
> there are many that will be with us, even inside Oracle.
> >>
> >>> On Mar 3, 2016, at 3:57 PM, John D. Ament 
> wrote:
> >>>
> >>> Hi Martin, Reza,
> >>>
> >>> The biggest hurdle would likely be Oracle signing an SGA for the
> glassfish codebase.  Not to mention that all dependencies are currently
> GPL/CDDL dual licensed.
> >>>
> >>> John
> >>>
>  On Thu, Mar 3, 2016 at 3:17 PM Martin Gainty 
> wrote:
>  Looking for procedures for transferring control of currently
> un-maintained glassfish J2EE Server from Oracle to ASF incubator project
> 
>  Thanks and Regards
>  Martin Gainty
> 
> 
>  Subject: Re: [gf-users] Re: Farewell to Oracle
>  To: mgai...@hotmail.com
>  From: reza_rah...@lycos.com
>  Date: Thu, 3 Mar 2016 13:56:02 -0500
> 
> 
> 
> 
> 
> 
>  That sounds just about right. How can I
>    get involved?
> 
> 
> 
>    On 3/3/2016 1:53 PM, Martin Gainty wrote:
> 
> 
> 
> 
>    Feel free to join Marcus and myself to transfer
>  Glassfish to ASF  ..
> 
> 
> 
> 
> 
> 
>    > To: us...@glassfish.java.net
> 
>  > From: reza_rah...@lycos.com
> 
>  > Date: Thu, 3 Mar 2016 12:51:49 -0500
> 
>  > Subject: [gf-users] Farewell to Oracle
> 
>  >
> 
>  > Folks,
> 
>  >
> 
>  > I am leaving Oracle behind on Friday. I have no doubt
>  whatsoever that
> 
>  > this was one of the top five hardest decisions of my
>  life. I am also at
> 
>  > this stage equally certain that this is the way I
>  personally can best
> 
>  > help continue to advance the Java and Java EE
>  communities. I will be
> 
>  > resuming the community work I have been part of for the
>  better part of a
> 
>  > decade in earnest as soon as possible post-Oracle.
> 
>  >
> 
>  > At Oracle folks like my colleagues David Delabassee and
>  Bruno Borges
> 
>  > will continue their roles in the Java EE ecosystem. I
>  certainly wish the
> 
>  > many good folks at Oracle nothing but the best of luck.
>  They have a very
> 
>  > hard job to do and they will continue to need our
>  support, perhaps now
> 
>  > more than ever.
> 
>  >
> 
>  > As always anyone is absolutely welcome to reach out to
>  me on just about
> 
>  > anything. Below are all my contact points.
> 
>  >
> 
>  > Cheers,
> 
>  > Reza
> 
>  >
> 
>  > Email: reza_rah...@lycos.com
> 
>  > Cell: 717-329-8149
> 
>  > Home Office: 215-736-1208
> 
>  > Google/Skype: m.reza.rahman
> 
>  > Twitter: @reza_rahman
> 
>  > https://www.linkedin.com/in/javareza
> 
>  > http://blog.rahmannet.net/
> 
>  > http://cargotracker.java.net
> 
> 
> 
> 
> 
> 
> 
>

Re: Need access to Incubator Wiki

[Nick Burch]

On Wed, 2 Mar 2016, Gino Bustelo wrote:

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


If you can let us know your username for the incubator wiki (register if 
you haven't already - it doesn't use your main apache credentials), then 
one of us can grant you the karma


Nick

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

Re: Update on Apache Toree and LGPL dependency

[John D. Ament]

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

Re: Update on Apache Toree and LGPL dependency

[John D. Ament]

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

Re: [VOTE] Release taverna-language-0.15.1-incubating-RC5 and taverna-osgi-0.2.1-incubating-RC5

[Justin Mclean]

Hi,

Sorry it -1 binding due to Category B software in a source release. [10]

I checked:
- artefacts contain incubating
- signature and hashes good
- DISCLAIMER exists
- LICENSE is good however it lists Category B software
- NOTICE is good
- There are a couple of binary files (under the test directory) do these need 
to be zipped?
- All source files have headers


There are some licensing issues:
- Several items [3][4][5][6] are licensed under W3C document license, this is 
not a category A license and looks like they can only be included in binary 
release [2]. (i.e. Category B but it's not listed) You may need to clarify this 
on legal discuss.
- Files [8][9][16][17][18][19][20] licensed under CC-BY-3 can only be included 
in a binary release. [10]
- I assume CC-A [11][12] would also need to be handled the same way.
- It is unclear how [13] is licensed.
- Looks like [14][15] are not licensed under a Category A license. Again 
probably needs to be discussed on legal discuss.

The LICENSE and NOTICE in ./taverna-tavlang-tool/src/main/resources/META-INF/ 
may need updating, looks like the contents don’t match the top level license 
and year is incorrect.

Also:
- Please consider signed the artefacts with an apache email address.
- The workflowrun.bundle.zip [1] file contains a LICENSE which is missing the 
appendix

Thanks,
Justin

1. 
apache-taverna-language-0.15.1-incubating/taverna-robundle/src/test/resources/workflowrun.bundle.zip
2. https://issues.apache.org/jira/browse/LEGAL-111
3. 
./taverna-scufl2-schemas/src/main/resources/org/apache/taverna/scufl2/rdfxml/xsd/xml.xsd
4. ./taverna-robundle/src/main/resources/ontologies/prov-aq.rdf
5. ./taverna-robundle/src/main/resources/ontologies/prov-o.rdf
6. ./taverna-robundle/src/main/resources/ontologies/prov-o.rdf
7. ./taverna-robundle/src/main/resources/ontologies/dcam.owl
8. ./taverna-robundle/src/main/resources/ontologies/dcam.owl
9. ./taverna-robundle/src/main/resources/ontologies/dcterms_od.owl
10. http://www.apache.org/legal/resolved.html#category-b
11. ./taverna-robundle/src/main/resources/ontologies/foaf.rdf
12. ./taverna-scufl2-wfdesc/src/main/resources/com/xmlns/foaf/foaf.rdf
13. ./taverna-robundle/src/main/xsd/xenc-schema.xsd
14. ./taverna-robundle/src/main/resources/ontologies/oa.rdf
15. ./taverna-robundle/src/main/resources/ontologies/ro.owl
16. 
./taverna-scufl2-wfdesc/src/main/resources/org/purl/wf4ever/wfdesc/wfdesc.ttl
17. 
./taverna-scufl2-wfdesc/src/main/resources/org/purl/wf4ever/wfdesc/wfprov.ttl
18. 
./taverna-scufl2-wfdesc/src/main/resources/org/purl/wf4ever/wfdesc/roterms.ttl
19. 
./taverna-scufl2-wfdesc/src/main/resources/org/purl/wf4ever/wfdesc/wf4ever.ttl
20 
./taverna-scufl2-schemas/src/main/resources/org/apache/taverna/scufl2/rdfxml/xsd/roevo.xsd

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

Re: Possible ASF Incubator Project transfer..

[Reza Rahman]

Obviously I need to take this up in earnest after Friday. In the meanwhile let 
me know what I need to do in order to get myself setup for this.

Anything that is worth it is never easy. This matters enough to try and there 
are many that will be with us, even inside Oracle.

> On Mar 3, 2016, at 3:57 PM, John D. Ament  wrote:
> 
> Hi Martin, Reza,
> 
> The biggest hurdle would likely be Oracle signing an SGA for the glassfish 
> codebase.  Not to mention that all dependencies are currently GPL/CDDL dual 
> licensed.
> 
> John
> 
>> On Thu, Mar 3, 2016 at 3:17 PM Martin Gainty  wrote:
>> Looking for procedures for transferring control of currently un-maintained 
>> glassfish J2EE Server from Oracle to ASF incubator project
>> 
>> Thanks and Regards
>> Martin Gainty
>> 
>> 
>> Subject: Re: [gf-users] Re: Farewell to Oracle
>> To: mgai...@hotmail.com
>> From: reza_rah...@lycos.com
>> Date: Thu, 3 Mar 2016 13:56:02 -0500
>> 
>> 
>> 
>> 
>> 
>> 
>> That sounds just about right. How can I
>>   get involved?
>> 
>> 
>> 
>>   On 3/3/2016 1:53 PM, Martin Gainty wrote:
>> 
>> 
>> 
>> 
>>   Feel free to join Marcus and myself to transfer
>> Glassfish to ASF  ..
>> 
>> 
>> 
>> 
>> 
>> 
>>   > To: us...@glassfish.java.net
>> 
>> > From: reza_rah...@lycos.com
>> 
>> > Date: Thu, 3 Mar 2016 12:51:49 -0500
>> 
>> > Subject: [gf-users] Farewell to Oracle
>> 
>> >
>> 
>> > Folks,
>> 
>> >
>> 
>> > I am leaving Oracle behind on Friday. I have no doubt
>> whatsoever that
>> 
>> > this was one of the top five hardest decisions of my
>> life. I am also at
>> 
>> > this stage equally certain that this is the way I
>> personally can best
>> 
>> > help continue to advance the Java and Java EE
>> communities. I will be
>> 
>> > resuming the community work I have been part of for the
>> better part of a
>> 
>> > decade in earnest as soon as possible post-Oracle.
>> 
>> >
>> 
>> > At Oracle folks like my colleagues David Delabassee and
>> Bruno Borges
>> 
>> > will continue their roles in the Java EE ecosystem. I
>> certainly wish the
>> 
>> > many good folks at Oracle nothing but the best of luck.
>> They have a very
>> 
>> > hard job to do and they will continue to need our
>> support, perhaps now
>> 
>> > more than ever.
>> 
>> >
>> 
>> > As always anyone is absolutely welcome to reach out to
>> me on just about
>> 
>> > anything. Below are all my contact points.
>> 
>> >
>> 
>> > Cheers,
>> 
>> > Reza
>> 
>> >
>> 
>> > Email: reza_rah...@lycos.com
>> 
>> > Cell: 717-329-8149
>> 
>> > Home Office: 215-736-1208
>> 
>> > Google/Skype: m.reza.rahman
>> 
>> > Twitter: @reza_rahman
>> 
>> > https://www.linkedin.com/in/javareza
>> 
>> > http://blog.rahmannet.net/
>> 
>> > http://cargotracker.java.net

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: Possible ASF Incubator Project transfer..

[Reza Rahman]

Yep, understood. We will give it an honest effort.

Sent from my iPhone

> On Mar 3, 2016, at 6:30 PM, John D. Ament  wrote:
> 
> You need to start with convincing oracle to provide an SGA for the entire 
> glassfish codebase.  Your best bet is to start that before you leave oracle.  
> 
> John
> 
>> On Thu, Mar 3, 2016 at 4:08 PM Reza Rahman  wrote:
>> Obviously I need to take this up in earnest after Friday. In the meanwhile 
>> let me know what I need to do in order to get myself setup for this.
>> 
>> Anything that is worth it is never easy. This matters enough to try and 
>> there are many that will be with us, even inside Oracle.
>> 
>>> On Mar 3, 2016, at 3:57 PM, John D. Ament  wrote:
>>> 
>>> Hi Martin, Reza,
>>> 
>>> The biggest hurdle would likely be Oracle signing an SGA for the glassfish 
>>> codebase.  Not to mention that all dependencies are currently GPL/CDDL dual 
>>> licensed.
>>> 
>>> John
>>> 
 On Thu, Mar 3, 2016 at 3:17 PM Martin Gainty  wrote:
 Looking for procedures for transferring control of currently un-maintained 
 glassfish J2EE Server from Oracle to ASF incubator project
 
 Thanks and Regards
 Martin Gainty
 
 
 Subject: Re: [gf-users] Re: Farewell to Oracle
 To: mgai...@hotmail.com
 From: reza_rah...@lycos.com
 Date: Thu, 3 Mar 2016 13:56:02 -0500
 
 
 
 
 
 
 That sounds just about right. How can I
   get involved?
 
 
 
   On 3/3/2016 1:53 PM, Martin Gainty wrote:
 
 
 
 
   Feel free to join Marcus and myself to transfer
 Glassfish to ASF  ..
 
 
 
 
 
 
   > To: us...@glassfish.java.net
 
 > From: reza_rah...@lycos.com
 
 > Date: Thu, 3 Mar 2016 12:51:49 -0500
 
 > Subject: [gf-users] Farewell to Oracle
 
 >
 
 > Folks,
 
 >
 
 > I am leaving Oracle behind on Friday. I have no doubt
 whatsoever that
 
 > this was one of the top five hardest decisions of my
 life. I am also at
 
 > this stage equally certain that this is the way I
 personally can best
 
 > help continue to advance the Java and Java EE
 communities. I will be
 
 > resuming the community work I have been part of for the
 better part of a
 
 > decade in earnest as soon as possible post-Oracle.
 
 >
 
 > At Oracle folks like my colleagues David Delabassee and
 Bruno Borges
 
 > will continue their roles in the Java EE ecosystem. I
 certainly wish the
 
 > many good folks at Oracle nothing but the best of luck.
 They have a very
 
 > hard job to do and they will continue to need our
 support, perhaps now
 
 > more than ever.
 
 >
 
 > As always anyone is absolutely welcome to reach out to
 me on just about
 
 > anything. Below are all my contact points.
 
 >
 
 > Cheers,
 
 > Reza
 
 >
 
 > Email: reza_rah...@lycos.com
 
 > Cell: 717-329-8149
 
 > Home Office: 215-736-1208
 
 > Google/Skype: m.reza.rahman
 
 > Twitter: @reza_rahman
 
 > https://www.linkedin.com/in/javareza
 
 > http://blog.rahmannet.net/
 
 > http://cargotracker.java.net