brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jose Carrasco <>
Subject Re: Jose's GSOC to support PaaS on Brooklyn
Date Mon, 05 Dec 2016 09:56:43 GMT
Hi all,

Richard, thanks a lot for taking this topic back.  Yes, I wrote the last 
blog entry with the unvaluable Andrea’s help (thanks for that, Andrea Turli).

I will be happy to integrate the code in the Apache repository and continue 
working on that. However, I also understand that this is still a work-in-progress project

and if the community prefers to move it to a non-Apache location, I will also agree with 
that. In any case, I would be pleased to continue working.

I have recorded another video-demo [1] to show the Cloud Foundry Manifest’s properties 
that are currently supported. 



El 02/12/2016, a las 16:14, Richard Downer <> escribió:

> Jose, all,
> I'd like to thank Jose for his work developing PaaS entities for Apache
> Brooklyn this last summer. For those who have not seen his work, please see
> [1] for a summary and lots of links, and [2] for an example and demo video.
> I'd like to consider the next steps for Jose's work, which is currently
> living in a personal GitHub repo and various other external resources. I'd
> like to get as much of this as appropriate into Apache Brooklyn.
> The first question is what is the most appropriate home for the code? The
> options I see are:
> - Integrate it into a current Apache Brooklyn repository (brooklyn-library?)
> - Create a new Apache Brooklyn repository (brooklyn-paas or
> brooklyn-contrib?)
> - A non-Apache location
> As this was an Apache-sponsored GSoC my preference is naturally for the
> first two options. However I appreciate there may be pragmatic reasons to
> keep the code out of the Brooklyn codebase and would like to hear opinions
> on this.
> Jose, I see you have been posting on our list again recently which I am
> delighted to see, and I hope you will continue to be involved in our
> community and in Brooklyn PaaS support!
> Richard.
> [1]
> [2]

View raw message