Re: [DISCUSS] Accept Stratos as an Apache Incubation Project

[Mattmann, Chris A (398J)]

+1 of course from me, with a commitment to doing work to help out
and making sure this doesn't fail; instead that it succeeds which
I'm sure it will.

I'll also sign up for a round of beers at the next ApacheCon. For
sure! :)

Cheers,
Chris

++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattm...@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++






-Original Message-
From: Ross Gardler 
Reply-To: "general@incubator.apache.org" 
Date: Wednesday, June 12, 2013 7:12 PM
To: "general@incubator.apache.org" 
Subject: Re: [DISCUSS] Accept Stratos as an Apache Incubation Project

>So here's a thought...
>
>There have been many discussions about different ways to incubate
>projects. One of the most radical ideas is to dismantle the incubator
>and replace the podling concept with "probationary TLPs" reporting to
>the board. As readers of this list will know I do not support the idea
>of dismantling the IPMC. I believe it does a great job that is not
>easily replaced by a board of nine directors. However, I have always
>acknowledged that the idea has merit under a certain set of
>circumstances.
>
>For me those circumstances are present in the Apache Stratos proposal.
>That is there are sufficient mentors and initial committers who are
>ASF Members that we can be reasonably certain that this project will
>succeed here at the ASF.
>
>I would therefore like to propose that we use Apache Stratos as a test
>case for the "probationary TLP" idea. I've already talked to Chris
>(who is driving the deconstruct the IPMC case) and Ant (who is less
>keen on dismantling the IPMC but wants to see how a probationary TLP
>model will play out). Both have agreed to help with this experiment if
>the IPMC and the Board wish it to proceed. I have not, however,
>discussed it with all the initial comitters or even mentors - I'm
>expecting them to speak up now.
>
>For my part my intention is to get the project set-up and then
>dissolve into the background. I do not intend to monitor the project
>on a day-to-day basis. However, I do promise to help pick up the
>pieces if the experiment should go horribly wrong.
>
>Of course running a single experiment will only allow us to define the
>incubation process for probationary TLPs, It is not going to solve all
>the problems Chris sees in the IPMC. However it will give us an
>opportunity to define the process, ask the board to approve this
>process and thus lay the foundations for other projects wishing to
>follow this path.
>
>So, what do you think?
>
>Ross
>
>
>On 11 June 2013 10:10, Ross Gardler  wrote:
>> It's with great pleasure that I invite the IPMC to review a new
>> proposal [1] for the Apache Incubator. Please let us know if you have
>> any questions or comments - as you will see there are plenty of people
>> on the initial commit list ready and willing to answer your questions.
>>
>> I copy the full text of the proposal for your convenience:
>>
>> = Stratos - A PaaS Framework =
>> == Abstract ==
>> Stratos will be a polyglot
>> [[http://www.gartner.com/it-glossary/platform-as-a-service-paas|PaaS]]
>> framework, providing developers a cloud-based environment for
>> developing, testing, and running scalable applications, and IT
>> providers high utilization rates, automated resource management, and
>> platform-wide insight including monitoring and billing.
>> == Proposal ==
>> The Stratos PaaS framework will encompass four layers:
>>  1. An 
>>[[http://www.gartner.com/it-glossary/infrastructure-as-a-service-iaas/|Ia
>>aS]]-agnostic
>> layer that can interface with a wide variety of IaaS systems to
>> provide elastic resources, and for multiple IaaS infrastructures to be
>> automated at one time (hybrid clouds.)
>>  2. A PaaS Controller with a cloud controller that automates and
>> monitors IaaS runtime interactions, distributes artifacts to the
>> underlying runtimes, deploys workloads, directs runtime traffic to the
>> right runtimes using a tenant-aware elastic load balancer, and
>> provides a portal for monitoring and provisioning of tenants on the
>> system.
>>  3. Foundational Services including security, logging, messaging,
>> registry, storage (relational, file, and noSQL), task management, and
>> billing.  Foundational services will be loosely-coupled to allow
>> swapping in alternate foundational services.
>>  4. A Cartridge Architecture allowing frameworks, servers, and other
>> runtimes to participate in the advantages of the system.  The
>> Cartridge Architecture must support multi-tenant workloads, and
>> provide for various levels of tenant isolation a

Re: [VOTE] Graduation of Apache Mesos

[Roman Shaposhnik]

On Wed, Jun 12, 2013 at 1:03 PM, Mattmann, Chris A (398J)
 wrote:
> Please VOTE to graduate Apache Mesos from the Incubator. Though
> only Incubator PMC member VOTEs are binding, all are welcome to
> voice your opinion. I'll leave the VOTE open for at least 72 hours,
> and hopefully can get enough VOTEs in time to close it by Saturday
> or Sunday in time for the board meeting on 6/19.
>
> [ ] +1 Graduate Apache Mesos from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Mesos from the Incubator because..

+1 (binding).

Thanks,
Roman.

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

Re: [VOTE] Accept Apache HotdoG into the Incubator

[Henry Saputra]

+1 binding.

Good luck guys

- Henry


On Wed, Jun 12, 2013 at 11:22 AM, Ramirez, Paul M (398J) <
paul.m.rami...@jpl.nasa.gov> wrote:

> All,
>
> I'd like to call a VOTE for the acceptance of Apache HotdoG into the
> Incubator. I'll leave the VOTE open for the rest of the week and close it
> out Monday, June 17th early am PT.
>
> [ ] +1 Accept Apache HotdoG into the Incubator
> [ ] +0 Don't care.
> [ ] -1 Don't accept Apache HotdoG because...
>
> Full Proposal is pasted at the end of this email. Only VOTEs from
> Incubator PMC members are binding, but all are welcome to express their
> thoughts.
>
> This is a second pass at this vote as I canceled it to pull in more
> mentors. The following people voted on the first pass:
>
> Henry Saputra +1 (binding)
> Chris Mattmann + 1 (binding)
>
> Thanks!
> Paul Ramirez
>
> P.S. +1 from me (binding)
>
>
> = HotdoG Proposal =
>
> == Abstract ==
>
> The HotdoG project is an effort and suite of tools to convert HDF/HDF-EOS
> format into GeoTIFF format. This is the first of a potential series of
> incoming projects originating from The HDF Group -- the non-profit
> organization is interested in evaluating the ASF as a potential home for
> many of its projects. The HDF Group is an independently funded organization
> that started many years ago with major investment from NASA as the
> Hierarchical Data Format (HDF), version 4 and now version 5, is the ''de
> facto'' remote sensing data format for NASA missions, and an increasing
> number of other disciplines including bio medicine, radio astronomy,
> climate science, and other domains.
>
> HDF is both a data and metadata format, as well as a model for
> representing and access information. There are numerous downstream tools
> that can read and write HDF data, including a growing number of Geospatial
> data tools (ESRI-based, and also OpenGeo and other community led efforts).
> In addition, major interoperability efforts are also occurring between the
> remote sensing community and the climate modeling community (which has
> traditionally favored NetCDF as opposed to HDF) because of the efforts in
> HDF5 to leverage a common data format and model.
>
> HotdoG is poised to be a first of its kind in the form of bringing one of
> the major 2 data formats for science to the ASF (the other being the NetCDF
> format).
>
> == Proposal ==
> HotdoG is a software converter that converts Earth Science data in
> HDF/HDF-EOS format into GeoTIFF format. Doing so easily enables users of
> remote sensing data to interoperate with common GIS tools (like WebGIS, Web
> Processing, image analysis, and geo computational tools). We feel that the
> project is an incremental step, and an appropriate focus with tangible
> success possibilities by restraining our focus to HDF/HDF-EOS to GeoTIFF
> conversion.
>
> There are numerous interesting paths that we can take the toolkit in -- as
> conversion from remotely sensed data to GeoTIFF involves ensuring that the
> HDF-EOS metadata elements can be appropriately represented using GeoTIFF
> headers, and the associated format. Furthermore, capturing the HDF's
> appropriate geo datum in GeoTIFF will be another important challenge.
>
> == Background ==
>
> GeoTIFF is a data and metadata standard for Earth science applications. It
> is based on binary Tagged Image File Format (TIFF).  A GeoTIFF file has
> geographic (or cartographic) data embedded as tags within the TIFF file
> that are used to geo-locate the image. This is required for correct
> integration of the image in Geographic Information Systems (GIS) and other
> popular tools like Google Earth Pro.
>
> In the recent years, GeoTIFF has gained popularity as a visualization
> format among NASA HDF Earth science user communities according to the NASA
> data user's survey. However, the conversion from HDF to GeoTIFF is not
> straightforward for end users because NASA HDF data products are diverse
> and organized in many different ways. For example, go to
> http://hdfeos.org/zoo and you'll see many scripting language examples
> because no single script can correctly visualize all NASA HDF data.
>
> == Rationale ==
>
> The HEG tool is limited to some NASA HDF-EOS2 products (no support for
> HDF-EOS5 products) and it is not an open-source tool. The latest GDAL
> (version 1.9.2 and above) is an open-source tool but it cannot handle many
> non-HDF-EOS NASA HDF products such as TRMM (pure HDF4) and Aquarius (pure
> HDF5) correctly and automatically.
>
> == Initial Goals ==
>
> We'll improve GDAL to support NASA HDF products better by handling
> geo-location information and physical meaning of data correctly and
> automatically.
>
> We'll handle NASA products intelligently so novice users don't have to
> supply many options or figure out the details about the data products. For
> advanced users, we'll give a full control of accessing HDF products in many
> different ways so that the converted GeoTIFF file is scientifically valid
> and meaningful.
>
> We aim t

Re: [VOTE] Graduation of Apache Mesos

[Alan Cabrera]

+1 binding


Regards,
Alan

On Jun 12, 2013, at 1:03 PM, "Mattmann, Chris A (398J)" 
 wrote:

> Hi All,
> 
> The Apache Mesos community is ready to graduate. They have added
> committers and PPMC members while in the Incubator; have made a
> few releases; are discussing their issues on list and in the Apache
> way, and are inclusive and representative of Apache's goals as a
> Foundation.
> 
> I'm extremely happy to put them up for Incubator graduation.
> We've VOTEd as a community to move forward with this:
> 
> DISCUSS thread here: http://s.apache.org/XAu
> VOTE thread here: http://s.apache.org/K8C
> VOTE RESULT: Message-ID: 
> 
> Project Incubator status page here:
> http://incubator.apache.org/projects/mesos.html
> 
> Board resolution pasted at bottom of email.
> 
> Existing tallies from the community VOTE:
> 
> +1
> Chris Mattmann*
> Vinod Kone
> Benjamin Hindman
> Benjamin Mahler
> Yan Xiu
> Deepal Jayasinghe
> Brenden Matthews
> Matei Zaharia
> Ant Elder*
> Konstantin Boudnik
> 
> * - indicates IPMC
> 
> Please VOTE to graduate Apache Mesos from the Incubator. Though
> only Incubator PMC member VOTEs are binding, all are welcome to
> voice your opinion. I'll leave the VOTE open for at least 72 hours,
> and hopefully can get enough VOTEs in time to close it by Saturday
> or Sunday in time for the board meeting on 6/19.
> 
> [ ] +1 Graduate Apache Mesos from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Mesos from the Incubator because..
> 
> Thanks everyone!
> 
> Cheers,
> Chris
> 
> 
> ---board resolution
> WHEREAS, the Board of Directors deems it to be in the best
> interests of the Foundation and consistent with the
> Foundation's purpose to establish a Project Management
> Committee charged with the creation and maintenance of
> open-source software, for distribution at no charge to the
> public, related to efficient cluster management, resource
> isolation and sharing across distributed applications.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Mesos Project", be
> and hereby is established pursuant to Bylaws of the Foundation;
> and be it further
> 
> RESOLVED, that the Apache Mesos Project be and hereby is
> responsible for the creation and maintenance of software
> related to efficient cluster management, resource isolation
> and sharing across distributed applications; and be it further
> RESOLVED, that the office of "Vice President, Apache Mesos" be
> and hereby is created, the person holding such office to serve
> at the direction of the Board of Directors as the chair of the
> Apache Mesos Project, and to have primary responsibility for
> management of the projects within the scope of responsibility
> of the Apache Mesos Project; and be it further
> RESOLVED, that the persons listed immediately below be and
> hereby are appointed to serve as the initial members of the
> Apache Mesos Project:
> 
> * Ali Ghodsi 
> * Andy Konwinski 
> * Benjamin Hindhman 
> * Benjamin Mahler 
> * Brian McCalister 
> * Ian Holsman 
> * Matei Alexandru Zahari 
> * Chris Mattmann 
> * Tom White 
> * Vinod Kone 
> * Brenden Matthews 
> * Thomas Marshall 
> * Charles Reiss 
> 
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Benjamin Hindman be
> appointed to the office of Vice President, Apache Mesos, to
> serve in accordance with and subject to the direction of the
> Board of Directors and the Bylaws of the Foundation until
> death, resignation, retirement, removal or disqualification, or
> until a successor is appointed; and be it further
> 
> RESOLVED, that the Apache Mesos Project be and hereby is
> tasked with the migration and rationalization of the Apache
> Incubator Mesos podling; and be it further
> 
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Mesos podling encumbered upon the Apache Incubator
> Project are hereafter discharged.
> 
> 
> ++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattm...@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++
> 
> 
> 
> 
> 
> -
> 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: [VOTE] Accept Apache HotdoG into the Incubator

[Alan Cabrera]

+1 - binding


Regards,
Alan

On Jun 12, 2013, at 11:22 AM, "Ramirez, Paul M (398J)" 
 wrote:

> All,
> 
> I'd like to call a VOTE for the acceptance of Apache HotdoG into the 
> Incubator. I'll leave the VOTE open for the rest of the week and close it out 
> Monday, June 17th early am PT.
> 
> [ ] +1 Accept Apache HotdoG into the Incubator
> [ ] +0 Don't care.
> [ ] -1 Don't accept Apache HotdoG because...
> 
> Full Proposal is pasted at the end of this email. Only VOTEs from Incubator 
> PMC members are binding, but all are welcome to express their thoughts.
> 
> This is a second pass at this vote as I canceled it to pull in more mentors. 
> The following people voted on the first pass:
> 
> Henry Saputra +1 (binding)
> Chris Mattmann + 1 (binding)
> 
> Thanks!
> Paul Ramirez
> 
> P.S. +1 from me (binding)
> 
> 
> = HotdoG Proposal =
> 
> == Abstract ==
> 
> The HotdoG project is an effort and suite of tools to convert HDF/HDF-EOS 
> format into GeoTIFF format. This is the first of a potential series of 
> incoming projects originating from The HDF Group -- the non-profit 
> organization is interested in evaluating the ASF as a potential home for many 
> of its projects. The HDF Group is an independently funded organization that 
> started many years ago with major investment from NASA as the Hierarchical 
> Data Format (HDF), version 4 and now version 5, is the ''de facto'' remote 
> sensing data format for NASA missions, and an increasing number of other 
> disciplines including bio medicine, radio astronomy, climate science, and 
> other domains.
> 
> HDF is both a data and metadata format, as well as a model for representing 
> and access information. There are numerous downstream tools that can read and 
> write HDF data, including a growing number of Geospatial data tools 
> (ESRI-based, and also OpenGeo and other community led efforts). In addition, 
> major interoperability efforts are also occurring between the remote sensing 
> community and the climate modeling community (which has traditionally favored 
> NetCDF as opposed to HDF) because of the efforts in HDF5 to leverage a common 
> data format and model.
> 
> HotdoG is poised to be a first of its kind in the form of bringing one of the 
> major 2 data formats for science to the ASF (the other being the NetCDF 
> format).
> 
> == Proposal ==
> HotdoG is a software converter that converts Earth Science data in 
> HDF/HDF-EOS format into GeoTIFF format. Doing so easily enables users of 
> remote sensing data to interoperate with common GIS tools (like WebGIS, Web 
> Processing, image analysis, and geo computational tools). We feel that the 
> project is an incremental step, and an appropriate focus with tangible 
> success possibilities by restraining our focus to HDF/HDF-EOS to GeoTIFF 
> conversion.
> 
> There are numerous interesting paths that we can take the toolkit in -- as 
> conversion from remotely sensed data to GeoTIFF involves ensuring that the 
> HDF-EOS metadata elements can be appropriately represented using GeoTIFF 
> headers, and the associated format. Furthermore, capturing the HDF's 
> appropriate geo datum in GeoTIFF will be another important challenge.
> 
> == Background ==
> 
> GeoTIFF is a data and metadata standard for Earth science applications. It is 
> based on binary Tagged Image File Format (TIFF).  A GeoTIFF file has 
> geographic (or cartographic) data embedded as tags within the TIFF file that 
> are used to geo-locate the image. This is required for correct integration of 
> the image in Geographic Information Systems (GIS) and other popular tools 
> like Google Earth Pro.
> 
> In the recent years, GeoTIFF has gained popularity as a visualization format 
> among NASA HDF Earth science user communities according to the NASA data 
> user's survey. However, the conversion from HDF to GeoTIFF is not 
> straightforward for end users because NASA HDF data products are diverse and 
> organized in many different ways. For example, go to http://hdfeos.org/zoo 
> and you'll see many scripting language examples because no single script can 
> correctly visualize all NASA HDF data.
> 
> == Rationale ==
> 
> The HEG tool is limited to some NASA HDF-EOS2 products (no support for 
> HDF-EOS5 products) and it is not an open-source tool. The latest GDAL 
> (version 1.9.2 and above) is an open-source tool but it cannot handle many 
> non-HDF-EOS NASA HDF products such as TRMM (pure HDF4) and Aquarius (pure 
> HDF5) correctly and automatically.
> 
> == Initial Goals ==
> 
> We'll improve GDAL to support NASA HDF products better by handling 
> geo-location information and physical meaning of data correctly and 
> automatically.
> 
> We'll handle NASA products intelligently so novice users don't have to supply 
> many options or figure out the details about the data products. For advanced 
> users, we'll give a full control of accessing HDF products in many different 
> ways so that the converted GeoTIFF file is scientifically val

Re: [DISCUSS] Accept Stratos as an Apache Incubation Project

[Alan Cabrera]

On Jun 12, 2013, at 7:12 PM, Ross Gardler  wrote:

> So here's a thought...
> 
> There have been many discussions about different ways to incubate
> projects. One of the most radical ideas is to dismantle the incubator
> and replace the podling concept with "probationary TLPs" reporting to
> the board. As readers of this list will know I do not support the idea
> of dismantling the IPMC. I believe it does a great job that is not
> easily replaced by a board of nine directors. However, I have always
> acknowledged that the idea has merit under a certain set of
> circumstances.
> 
> For me those circumstances are present in the Apache Stratos proposal.
> That is there are sufficient mentors and initial committers who are
> ASF Members that we can be reasonably certain that this project will
> succeed here at the ASF.
> 
> I would therefore like to propose that we use Apache Stratos as a test
> case for the "probationary TLP" idea. I've already talked to Chris
> (who is driving the deconstruct the IPMC case) and Ant (who is less
> keen on dismantling the IPMC but wants to see how a probationary TLP
> model will play out). Both have agreed to help with this experiment if
> the IPMC and the Board wish it to proceed. I have not, however,
> discussed it with all the initial comitters or even mentors - I'm
> expecting them to speak up now.
> 
> For my part my intention is to get the project set-up and then
> dissolve into the background. I do not intend to monitor the project
> on a day-to-day basis. However, I do promise to help pick up the
> pieces if the experiment should go horribly wrong.
> 
> Of course running a single experiment will only allow us to define the
> incubation process for probationary TLPs, It is not going to solve all
> the problems Chris sees in the IPMC. However it will give us an
> opportunity to define the process, ask the board to approve this
> process and thus lay the foundations for other projects wishing to
> follow this path.
> 
> So, what do you think?

I don't see the need to force Stratos through the Incubator given the current 
proposed membership.  Some points:
Who's responsible for monitoring the probation, the IPMC or the board?  I think 
it should be the IPMC.
What bits must absolutely be done before probation begins?
What minimum criteria does a probationary TLP have to meet to stay in good 
graces?
What happens if the probationary TLP is not in good graces?
What bits must absolutely be done before probation completes?
Fleshing out these and, I'm sure, others' concerns on a wiki, as Joe pointed 
out, would be a great idea.


Regards,
Alan

Re: [DISCUSS] Accept Stratos as an Apache Incubation Project

[Sanjiva Weerawarana]

On Thu, Jun 13, 2013 at 8:27 AM, David Nalley  wrote:

> ccing trademarks@
> Note the mix of public and private lists.
> > Yeah we also thought about that .. if StratosLive is too close to home we
> > can certainly change it. Bit painful but not impossible.
> >
>
> Better to get an answer to the question up front IMO.
>

+1.

> The thinking is to not give that a specific name but rather call it the
> > WSO2 distribution of Apache Stratos (or something like that).
> >
>
> I don't think that's one of the 'sanctioned' uses of marks from:
> In fact, per the below page, it's explicitly forbidden.
> http://www.apache.org/foundation/marks/faq/#products


Hmm that idea was based on how Cloudera is distributing Hadoop:

http://www.cloudera.com/content/cloudera/en/products/cdh.html

Is that also incorrect then? IIRC they've been doing that for years and
presumably ASF is aware of it?

Sanjiva.
-- 
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
650 265 8311
blog: http://sanjiva.weerawarana.org/

Lean . Enterprise . Middleware

Re: [DISCUSS] Accept Stratos as an Apache Incubation Project

[David Nalley]

ccing trademarks@
Note the mix of public and private lists.

On Wed, Jun 12, 2013 at 8:09 PM, Sanjiva Weerawarana  wrote:
> On Thu, Jun 13, 2013 at 5:02 AM, Marvin Humphrey 
> wrote:
>
>> > == Known Risks ==
>> > Stratos has largely been developed by sponsored developers employed at
>> > a single organization - WSO2.  Seeking a broader community of
>> > contributors is a top goal of contributing Stratos to Apache.
>> > WSO2 plans to continue to offer services and commercial support
>> > packages for Stratos, so there is a financial incentive to broaden
>> > Stratos’ appeal.  This may provide the misinterpretation that Stratos
>> > remains merely a WSO2 technology.  However, WSO2’s main business
>> > strategy is to build and support higher level PaaS offerings
>> > (including the WSO2 middleware stack) on top of a common PaaS
>> > framework, as provided by Stratos.  This includes a WSO2 StratosLive
>> > option which is a public PaaS based on WSO2 Stratos.
>>
>> Kudos for the honest self-analysis.
>>
>
> Thanks :-).
>
> I wonder whether Apache Brand Management would cry foul on a trademark like
>> "StratosLive" if such a product were to appear later because of the
>> "confusingly similar name" guideline.  We've seen project founders leave
>> and
>> compete with ASF products while using confusingly similar names before,
>> e.g.
>> CouchBase.
>>
>
> Yeah we also thought about that .. if StratosLive is too close to home we
> can certainly change it. Bit painful but not impossible.
>

Better to get an answer to the question up front IMO.

> If a "top goal" is "seeking a broader community of contributors", the
>> project
>> might benefit if it could find a way to reassure potential contributors on
>> this matter.  Perhaps the name for the WS02 product should be vetted in
>> advance?
>>
>
> Yep can do - our current thinking is to have a WSO2 distribution that
> contains Apache Stratos and includes all of our middleware products (app
> server, esb, etc. etc.). That is, a PaaS built on the PaaS framework from
> Apache.
>
> The thinking is to not give that a specific name but rather call it the
> WSO2 distribution of Apache Stratos (or something like that).
>

I don't think that's one of the 'sanctioned' uses of marks from:
In fact, per the below page, it's explicitly forbidden.
http://www.apache.org/foundation/marks/faq/#products


> Shane do you have thoughts on that? That idea is based on what some others
> do and it seems to me is clear enough that its not just the Apache code
> being redistributed but has more stuff. Analogous to Redhat being a Linux
> distribution.
>
> Cheers,
>
> Sanjiva.
> --
> Sanjiva Weerawarana, Ph.D.
> Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
> email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
> 650 265 8311
> blog: http://sanjiva.weerawarana.org/
>
> Lean . Enterprise . Middleware


--David

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

Re: [DISCUSS] Accept Stratos as an Apache Incubation Project

[Suresh Marru]

Hi Ross,

+ 1 for considering this project for the probationary TLP experiment. Here are 
my 2 cents:

* The initial committers list on the proposal demonstrates diversity. 
* The proposal building process was inclusive (a glimpse of wiki history shows 
some of it). With enough "outsiders" (who were not part of the code donation 
organization), I can see the community building already.
* Along with 7 nominated mentors there are significant number of ASF and IPMC 
members on the initial committers list, so I can trust the PMC to get the 
releases right.

Ofcourse there will be few tasks like podling name search which needs to be 
done upfront, but other wise I see no issues wit this experiment. I can foresee 
this project will quickly cruise incubation, so if the board agrees why not get 
it jumpstarted? 

Cheers,
Suresh


On Jun 12, 2013, at 10:12 PM, Ross Gardler  wrote:

> So here's a thought...
> 
> There have been many discussions about different ways to incubate
> projects. One of the most radical ideas is to dismantle the incubator
> and replace the podling concept with "probationary TLPs" reporting to
> the board. As readers of this list will know I do not support the idea
> of dismantling the IPMC. I believe it does a great job that is not
> easily replaced by a board of nine directors. However, I have always
> acknowledged that the idea has merit under a certain set of
> circumstances.
> 
> For me those circumstances are present in the Apache Stratos proposal.
> That is there are sufficient mentors and initial committers who are
> ASF Members that we can be reasonably certain that this project will
> succeed here at the ASF.
> 
> I would therefore like to propose that we use Apache Stratos as a test
> case for the "probationary TLP" idea. I've already talked to Chris
> (who is driving the deconstruct the IPMC case) and Ant (who is less
> keen on dismantling the IPMC but wants to see how a probationary TLP
> model will play out). Both have agreed to help with this experiment if
> the IPMC and the Board wish it to proceed. I have not, however,
> discussed it with all the initial comitters or even mentors - I'm
> expecting them to speak up now.
> 
> For my part my intention is to get the project set-up and then
> dissolve into the background. I do not intend to monitor the project
> on a day-to-day basis. However, I do promise to help pick up the
> pieces if the experiment should go horribly wrong.
> 
> Of course running a single experiment will only allow us to define the
> incubation process for probationary TLPs, It is not going to solve all
> the problems Chris sees in the IPMC. However it will give us an
> opportunity to define the process, ask the board to approve this
> process and thus lay the foundations for other projects wishing to
> follow this path.
> 
> So, what do you think?
> 
> Ross
> 
> 
> On 11 June 2013 10:10, Ross Gardler  wrote:
>> It's with great pleasure that I invite the IPMC to review a new
>> proposal [1] for the Apache Incubator. Please let us know if you have
>> any questions or comments - as you will see there are plenty of people
>> on the initial commit list ready and willing to answer your questions.
>> 
>> I copy the full text of the proposal for your convenience:
>> 
>> = Stratos - A PaaS Framework =
>> == Abstract ==
>> Stratos will be a polyglot
>> [[http://www.gartner.com/it-glossary/platform-as-a-service-paas|PaaS]]
>> framework, providing developers a cloud-based environment for
>> developing, testing, and running scalable applications, and IT
>> providers high utilization rates, automated resource management, and
>> platform-wide insight including monitoring and billing.
>> == Proposal ==
>> The Stratos PaaS framework will encompass four layers:
>> 1. An 
>> [[http://www.gartner.com/it-glossary/infrastructure-as-a-service-iaas/|IaaS]]-agnostic
>> layer that can interface with a wide variety of IaaS systems to
>> provide elastic resources, and for multiple IaaS infrastructures to be
>> automated at one time (hybrid clouds.)
>> 2. A PaaS Controller with a cloud controller that automates and
>> monitors IaaS runtime interactions, distributes artifacts to the
>> underlying runtimes, deploys workloads, directs runtime traffic to the
>> right runtimes using a tenant-aware elastic load balancer, and
>> provides a portal for monitoring and provisioning of tenants on the
>> system.
>> 3. Foundational Services including security, logging, messaging,
>> registry, storage (relational, file, and noSQL), task management, and
>> billing.  Foundational services will be loosely-coupled to allow
>> swapping in alternate foundational services.
>> 4. A Cartridge Architecture allowing frameworks, servers, and other
>> runtimes to participate in the advantages of the system.  The
>> Cartridge Architecture must support multi-tenant workloads, and
>> provide for various levels of tenant isolation and policy-based
>> control over provisioning.
>> 
>> Together these layers offer a foun

Re: [DISCUSS] Accept Stratos as an Apache Incubation Project

[Ross Gardler]

Chris' proposal is at
http://wiki.apache.org/incubator/IncubatorDeconstructionProposal

This will need some work before it can be made "real" but I think
there is enough meat on the bones to understand the concept.

Ross

On 13 June 2013 03:16, Joe Schaefer  wrote:
> It'd help to know concretely what is meant
> by a "probationary TLP", particularly what
> is different about it from normal incubation.
> I am not looking for yet another email discussion,
> but an URL to a wiki page would be nice.
>
>
>
>>
>> From: Ross Gardler 
>>To: general@incubator.apache.org
>>Sent: Wednesday, June 12, 2013 10:12 PM
>>Subject: Re: [DISCUSS] Accept Stratos as an Apache Incubation Project
>>
>>
>>So here's a thought...
>>
>>There have been many discussions about different ways to incubate
>>projects. One of the most radical ideas is to dismantle the incubator
>>and replace the podling concept with "probationary TLPs" reporting to
>>the board. As readers of this list will know I do not support the idea
>>of dismantling the IPMC. I believe it does a great job that is not
>>easily replaced by a board of nine directors. However, I have always
>>acknowledged that the idea has merit under a certain set of
>>circumstances.
>>
>>For me those circumstances are present in the Apache Stratos proposal.
>>That is there are sufficient mentors and initial committers who are
>>ASF Members that we can be reasonably certain that this project will
>>succeed here at the ASF.
>>
>>I would therefore like to propose that we use Apache Stratos as a test
>>case for the "probationary TLP" idea. I've already talked to Chris
>>(who is driving the deconstruct the IPMC case) and Ant (who is less
>>keen on dismantling the IPMC but wants to see how a probationary TLP
>>model will play out). Both have agreed to help with this experiment if
>>the IPMC and the Board wish it to proceed. I have not, however,
>>discussed it with all the initial comitters or even mentors - I'm
>>expecting them to speak up now.
>>
>>For my part my intention is to get the project set-up and then
>>dissolve into the background. I do not intend to monitor the project
>>on a day-to-day basis. However, I do promise to help pick up the
>>pieces if the experiment should go horribly wrong.
>>
>>Of course running a single experiment will only allow us to define the
>>incubation process for probationary TLPs, It is not going to solve all
>>the problems Chris sees in the IPMC. However it will give us an
>>opportunity to define the process, ask the board to approve this
>>process and thus lay the foundations for other projects wishing to
>>follow this path.
>>
>>So, what do you think?
>>
>>Ross
>>
>>
>>On 11 June 2013 10:10, Ross Gardler  wrote:
>>> It's with great pleasure that I invite the IPMC to review a new
>>> proposal [1] for the Apache Incubator. Please let us know if you have
>>> any questions or comments - as you will see there are plenty of people
>>> on the initial commit list ready and willing to answer your questions.
>>>
>>> I copy the full text of the proposal for your convenience:
>>>
>>> = Stratos - A PaaS Framework =
>>> == Abstract ==
>>> Stratos will be a polyglot
>>> [[http://www.gartner.com/it-glossary/platform-as-a-service-paas|PaaS]]
>>> framework, providing developers a cloud-based environment for
>>> developing, testing, and running scalable applications, and IT
>>> providers high utilization rates, automated resource management, and
>>> platform-wide insight including monitoring and billing.
>>> == Proposal ==
>>> The Stratos PaaS framework will encompass four layers:
>>>  1. An 
>>> [[http://www.gartner.com/it-glossary/infrastructure-as-a-service-iaas/|IaaS]]-agnostic
>>> layer that can interface with a wide variety of IaaS systems to
>>> provide elastic resources, and for multiple IaaS infrastructures to be
>>> automated at one time (hybrid clouds.)
>>>  2. A PaaS Controller with a cloud controller that automates and
>>> monitors IaaS runtime interactions, distributes artifacts to the
>>> underlying runtimes, deploys workloads, directs runtime traffic to the
>>> right runtimes using a tenant-aware elastic load balancer, and
>>> provides a portal for monitoring and provisioning of tenants on the
>>> system.
>>>  3. Foundational Services including security, logging, messaging,
>>> registry, storage (relational, file, and noSQL), task management, and
>>> billing.  Foundational services will be loosely-coupled to allow
>>> swapping in alternate foundational services.
>>>  4. A Cartridge Architecture allowing frameworks, servers, and other
>>> runtimes to participate in the advantages of the system.  The
>>> Cartridge Architecture must support multi-tenant workloads, and
>>> provide for various levels of tenant isolation and policy-based
>>> control over provisioning.
>>>
>>> Together these layers offer a foundational layer upon which
>>> applications and middleware frameworks can be deployed to speed
>>> time-to-market and simplify t

Re: [DISCUSS] Accept Stratos as an Apache Incubation Project

[Joe Schaefer]

It'd help to know concretely what is meant
by a "probationary TLP", particularly what
is different about it from normal incubation.
I am not looking for yet another email discussion,
but an URL to a wiki page would be nice.



>
> From: Ross Gardler 
>To: general@incubator.apache.org 
>Sent: Wednesday, June 12, 2013 10:12 PM
>Subject: Re: [DISCUSS] Accept Stratos as an Apache Incubation Project
> 
>
>So here's a thought...
>
>There have been many discussions about different ways to incubate
>projects. One of the most radical ideas is to dismantle the incubator
>and replace the podling concept with "probationary TLPs" reporting to
>the board. As readers of this list will know I do not support the idea
>of dismantling the IPMC. I believe it does a great job that is not
>easily replaced by a board of nine directors. However, I have always
>acknowledged that the idea has merit under a certain set of
>circumstances.
>
>For me those circumstances are present in the Apache Stratos proposal.
>That is there are sufficient mentors and initial committers who are
>ASF Members that we can be reasonably certain that this project will
>succeed here at the ASF.
>
>I would therefore like to propose that we use Apache Stratos as a test
>case for the "probationary TLP" idea. I've already talked to Chris
>(who is driving the deconstruct the IPMC case) and Ant (who is less
>keen on dismantling the IPMC but wants to see how a probationary TLP
>model will play out). Both have agreed to help with this experiment if
>the IPMC and the Board wish it to proceed. I have not, however,
>discussed it with all the initial comitters or even mentors - I'm
>expecting them to speak up now.
>
>For my part my intention is to get the project set-up and then
>dissolve into the background. I do not intend to monitor the project
>on a day-to-day basis. However, I do promise to help pick up the
>pieces if the experiment should go horribly wrong.
>
>Of course running a single experiment will only allow us to define the
>incubation process for probationary TLPs, It is not going to solve all
>the problems Chris sees in the IPMC. However it will give us an
>opportunity to define the process, ask the board to approve this
>process and thus lay the foundations for other projects wishing to
>follow this path.
>
>So, what do you think?
>
>Ross
>
>
>On 11 June 2013 10:10, Ross Gardler  wrote:
>> It's with great pleasure that I invite the IPMC to review a new
>> proposal [1] for the Apache Incubator. Please let us know if you have
>> any questions or comments - as you will see there are plenty of people
>> on the initial commit list ready and willing to answer your questions.
>>
>> I copy the full text of the proposal for your convenience:
>>
>> = Stratos - A PaaS Framework =
>> == Abstract ==
>> Stratos will be a polyglot
>> [[http://www.gartner.com/it-glossary/platform-as-a-service-paas|PaaS]]
>> framework, providing developers a cloud-based environment for
>> developing, testing, and running scalable applications, and IT
>> providers high utilization rates, automated resource management, and
>> platform-wide insight including monitoring and billing.
>> == Proposal ==
>> The Stratos PaaS framework will encompass four layers:
>>  1. An 
>>[[http://www.gartner.com/it-glossary/infrastructure-as-a-service-iaas/|IaaS]]-agnostic
>> layer that can interface with a wide variety of IaaS systems to
>> provide elastic resources, and for multiple IaaS infrastructures to be
>> automated at one time (hybrid clouds.)
>>  2. A PaaS Controller with a cloud controller that automates and
>> monitors IaaS runtime interactions, distributes artifacts to the
>> underlying runtimes, deploys workloads, directs runtime traffic to the
>> right runtimes using a tenant-aware elastic load balancer, and
>> provides a portal for monitoring and provisioning of tenants on the
>> system.
>>  3. Foundational Services including security, logging, messaging,
>> registry, storage (relational, file, and noSQL), task management, and
>> billing.  Foundational services will be loosely-coupled to allow
>> swapping in alternate foundational services.
>>  4. A Cartridge Architecture allowing frameworks, servers, and other
>> runtimes to participate in the advantages of the system.  The
>> Cartridge Architecture must support multi-tenant workloads, and
>> provide for various levels of tenant isolation and policy-based
>> control over provisioning.
>>
>> Together these layers offer a foundational layer upon which
>> applications and middleware frameworks can be deployed to speed
>> time-to-market and simplify the development of scalable applications,
>> as well as provide a high level of resource sharing and centralized
>> management that can deliver lowest resource, infrastructure, and
>> management costs.
>> == Background ==
>> The Stratos Project has been under development[a] at http://wso2.org
>> under the Apache 2.0 license and the Apache Way governance model since
>>

Re: [DISCUSS] Accept Stratos as an Apache Incubation Project

[Ross Gardler]

So here's a thought...

There have been many discussions about different ways to incubate
projects. One of the most radical ideas is to dismantle the incubator
and replace the podling concept with "probationary TLPs" reporting to
the board. As readers of this list will know I do not support the idea
of dismantling the IPMC. I believe it does a great job that is not
easily replaced by a board of nine directors. However, I have always
acknowledged that the idea has merit under a certain set of
circumstances.

For me those circumstances are present in the Apache Stratos proposal.
That is there are sufficient mentors and initial committers who are
ASF Members that we can be reasonably certain that this project will
succeed here at the ASF.

I would therefore like to propose that we use Apache Stratos as a test
case for the "probationary TLP" idea. I've already talked to Chris
(who is driving the deconstruct the IPMC case) and Ant (who is less
keen on dismantling the IPMC but wants to see how a probationary TLP
model will play out). Both have agreed to help with this experiment if
the IPMC and the Board wish it to proceed. I have not, however,
discussed it with all the initial comitters or even mentors - I'm
expecting them to speak up now.

For my part my intention is to get the project set-up and then
dissolve into the background. I do not intend to monitor the project
on a day-to-day basis. However, I do promise to help pick up the
pieces if the experiment should go horribly wrong.

Of course running a single experiment will only allow us to define the
incubation process for probationary TLPs, It is not going to solve all
the problems Chris sees in the IPMC. However it will give us an
opportunity to define the process, ask the board to approve this
process and thus lay the foundations for other projects wishing to
follow this path.

So, what do you think?

Ross


On 11 June 2013 10:10, Ross Gardler  wrote:
> It's with great pleasure that I invite the IPMC to review a new
> proposal [1] for the Apache Incubator. Please let us know if you have
> any questions or comments - as you will see there are plenty of people
> on the initial commit list ready and willing to answer your questions.
>
> I copy the full text of the proposal for your convenience:
>
> = Stratos - A PaaS Framework =
> == Abstract ==
> Stratos will be a polyglot
> [[http://www.gartner.com/it-glossary/platform-as-a-service-paas|PaaS]]
> framework, providing developers a cloud-based environment for
> developing, testing, and running scalable applications, and IT
> providers high utilization rates, automated resource management, and
> platform-wide insight including monitoring and billing.
> == Proposal ==
> The Stratos PaaS framework will encompass four layers:
>  1. An 
> [[http://www.gartner.com/it-glossary/infrastructure-as-a-service-iaas/|IaaS]]-agnostic
> layer that can interface with a wide variety of IaaS systems to
> provide elastic resources, and for multiple IaaS infrastructures to be
> automated at one time (hybrid clouds.)
>  2. A PaaS Controller with a cloud controller that automates and
> monitors IaaS runtime interactions, distributes artifacts to the
> underlying runtimes, deploys workloads, directs runtime traffic to the
> right runtimes using a tenant-aware elastic load balancer, and
> provides a portal for monitoring and provisioning of tenants on the
> system.
>  3. Foundational Services including security, logging, messaging,
> registry, storage (relational, file, and noSQL), task management, and
> billing.  Foundational services will be loosely-coupled to allow
> swapping in alternate foundational services.
>  4. A Cartridge Architecture allowing frameworks, servers, and other
> runtimes to participate in the advantages of the system.  The
> Cartridge Architecture must support multi-tenant workloads, and
> provide for various levels of tenant isolation and policy-based
> control over provisioning.
>
> Together these layers offer a foundational layer upon which
> applications and middleware frameworks can be deployed to speed
> time-to-market and simplify the development of scalable applications,
> as well as provide a high level of resource sharing and centralized
> management that can deliver lowest resource, infrastructure, and
> management costs.
> == Background ==
> The Stratos Project has been under development[a] at http://wso2.org
> under the Apache 2.0 license and the Apache Way governance model since
> 2010.  It initially was focussed on providing PaaS benefits to the
> users of WSO2 Carbon middleware platform.  In version 2.0, to be
> released in summer 2013, extensive work has been done to clearly
> separate out the PaaS framework from the products (cartridges) that
> run on top of it.  Stratos now has the ability to run arbitrary
> workloads, including Java, PHP, MySQL, Jetty, Tomcat, and many more.
> == Rationale ==
> PaaS is in demand by enterprises and organizations of all sizes.  The
> drive towards instance p

Re: [DISCUSS] Accept Stratos as an Apache Incubation Project

[Ross Gardler]

Good catch on the missing private@ list - thanks

Ross

On 13 June 2013 01:43, Afkham Azeez  wrote:
> On Thu, Jun 13, 2013 at 5:02 AM, Marvin Humphrey 
> wrote:
>
>>
>>
>> > === Mailing Lists ===
>> >  1. d...@stratos.incubator.apache.org - for developer/user discussions,
>> >  JIRA change notifications & continuous build/test notifications
>> >  2. comm...@stratos.incubator.apache.org - for commit mails
>>
>> It's a technicality, but the podling would also need a private@ list.
>> Since there's only a combined dev/user list to start with though, obviously
>> some thought has gone into this. :)
>>
>>
> When we initially created the list of required mailing lists, we requested
> for user & dev lists. We spoke to a few people who have experience with
> bringing projects into the incubator, and were advised to start with a
> combined list so that all discussions happen in one place, and when there
> is a significant user community involvement, we could decide to create a
> user list. I will go ahead & add a private@ list.
>
> Thanks
> Azeez
> *
> *

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

[RESULT] [VOTE] Accept Apache MetaModel into the Apache incubator

[Henry Saputra]

Hi All,

Thank you for everyone for participating and warm welcome for the MetaModel
project proposal.

The VOTE is now officially closed with the result (* means IPMC):

+1s:
Henry Saputra*
Matt Franklin*
Chris Mattmann*
Noah Slater*
Rahul Sharma
Ankit Kumar
Christian Grobmeier*
Arvind Prabhakar*
Kasper Sorensen
Noah Slater*
Manuel Van den Berg
Joe Brockmeier*
Suresh Marru*
Ted Dunning*
Rich Bowen
Alan Cabrera*
Marcel Offermans*
Alex Karasulu*

0s:
None

-1s:
None


This means with 18 +1s (13 binding) and no 0 and -1 the proposal is
accepted.

I will continue with the bootstrap process to bring MetaModel into Apache
incubator.

Thank you again for those participated in the VOTE.


Thanks,

Henry

On Thu, Jun 6, 2013 at 3:30 PM, Henry Saputra wrote:

> Hi All,
>
> I'd like to call a VOTE for acceptance of MetaModel into the Apache
> incubator.
> The vote will close on June 12, 2013 at 6:00 PM (PST).
>
> [] +1 Accept MetaModel into the Apache incubator
> [] +0 Don't care.
> [] -1 Don't accept MetaModel into the incubator because...
>
> Full proposal is pasted at the bottom on this email, and the corresponding 
> wiki
> is:
> http://wiki.apache.org/incubator/MetaModelProposal.
>
> Only VOTEs from Incubator PMC members are binding, but all are welcome to
> express their thoughts.
>
> Thanks,
>
> Henry Saputra
> Champion for Apache MetaModel
>
>
> P.S. Here's my +1 (binding)
>
>
> -
>
> = MetaModel – uniform data access across datastores =
>
> Proposal for Apache Incubator
>
> == Abstract ==
>
> MetaModel is a data access framework, providing a common interface for
> exploration and querying of different types of datastores.
>
> == Proposal ==
>
> MetaModel provides a uniform meta-model for exploring and querying the
> structure of datastores, covering but not limited to relational databases,
> various data file formats, NoSQL databases, Salesforce.com, SugarCRM and
> more. The scope of the project is to stay domain-agnostic, so the
> meta-model will be concerned with schemas, tables, columns, rows,
> relationships etc.
>
> On top of this meta-model a rich querying API is provided which resembles
> SQL, but built using compiler-checked Java language constructs. For
> datastores that do not have a native SQL-compatible query engine, the
> MetaModel project also includes an abstract Java-based query engine
> implementation which individual datastore-modules can adapt to fit the
> concrete datastore.
>
> === Background ===
>
> The MetaModel project was initially developed by eobject.dk to service
> the DataCleaner application (http://datacleaner.org). The main
> requirement was to perform data querying and modification operations on a
> wide range of quite different datastores. Furthermore a programmatic query
> model was needed in order to allow different components to influence the
> query plan.
>
> In 2009, Human Inference acquired the eobjects projects including
> MetaModel. Since then MetaModel has been put to extensive use in the Human
> Inference products. The open source nature of the project was reinforced,
> leading to a significant growth in the community.
>
> MetaModel has successfully been used in a number of other open source
> projects as well as mission critical commercial software from Human
> Inference. Currently MetaModel is hosted at http://metamodel.eobjects.org.
>
> === Rationale ===
>
> Different types of datastores have different characteristics, which always
> lead to the interfaces for these being different from one another.
> Standards like JDBC and the SQL language attempt to standardize data
> access, but for some datastore types like flat files, spreadsheets, NoSQL
> databases and more, such standards are not even implementable.
>
> Specialization in interfaces obviously has merit for optimized usage, but
> for integration tools, batch applications and or generic data modification
> tools, this myriad of specialized interfaces is a big pain. Furthermore,
> being able to query every datastore with a basic set of SQL-like features
> can be a great productivity boost for a wide range of applications.
>
> === Initial goals ===
>
> MetaModel is already a stable project, so initial goals are more oriented
> towards an adaption to the Apache ecosystem than about functional changes.
>
> We are constantly adding more datastore types to the portfolio, but the
> core modules have not had drastic changes for some time.
>
> Our focus will be on making ties with other Apache projects (such as POI,
> Gora, HBase and CouchDB) and potentially renaming the ‘MetaModel’ project
> to something more rememberable.
> This includes comply with Apache Software Foundation license for third
> party dependencies.
>
> == Current status ==
>
> === Meritocracy ===
>
> We intend to do everything we can to encourage a meritocracy in the
> development of MetaModel. Currently most important development and design
> decisions have been made at Human Inference, but with an 

Re: [DISCUSS] Accept Stratos as an Apache Incubation Project

[Afkham Azeez]

On Thu, Jun 13, 2013 at 5:02 AM, Marvin Humphrey wrote:

>
>
> > === Mailing Lists ===
> >  1. d...@stratos.incubator.apache.org - for developer/user discussions,
> >  JIRA change notifications & continuous build/test notifications
> >  2. comm...@stratos.incubator.apache.org - for commit mails
>
> It's a technicality, but the podling would also need a private@ list.
> Since there's only a combined dev/user list to start with though, obviously
> some thought has gone into this. :)
>
>
When we initially created the list of required mailing lists, we requested
for user & dev lists. We spoke to a few people who have experience with
bringing projects into the incubator, and were advised to start with a
combined list so that all discussions happen in one place, and when there
is a significant user community involvement, we could decide to create a
user list. I will go ahead & add a private@ list.

Thanks
Azeez
*
*

Re: [DISCUSS] Accept Stratos as an Apache Incubation Project

[Deepal Jayasinghe]

Great to see WSO2 Stratos coming to Apache, and I would love to join/help
this project.

Deepal


On Tue, Jun 11, 2013 at 5:10 AM, Ross Gardler wrote:

> It's with great pleasure that I invite the IPMC to review a new
> proposal [1] for the Apache Incubator. Please let us know if you have
> any questions or comments - as you will see there are plenty of people
> on the initial commit list ready and willing to answer your questions.
>
> I copy the full text of the proposal for your convenience:
>
> = Stratos - A PaaS Framework =
> == Abstract ==
> Stratos will be a polyglot
> [[http://www.gartner.com/it-glossary/platform-as-a-service-paas|PaaS]]
> framework, providing developers a cloud-based environment for
> developing, testing, and running scalable applications, and IT
> providers high utilization rates, automated resource management, and
> platform-wide insight including monitoring and billing.
> == Proposal ==
> The Stratos PaaS framework will encompass four layers:
>  1. An [[
> http://www.gartner.com/it-glossary/infrastructure-as-a-service-iaas/|IaaS]]-agnostic
> layer that can interface with a wide variety of IaaS systems to
> provide elastic resources, and for multiple IaaS infrastructures to be
> automated at one time (hybrid clouds.)
>  2. A PaaS Controller with a cloud controller that automates and
> monitors IaaS runtime interactions, distributes artifacts to the
> underlying runtimes, deploys workloads, directs runtime traffic to the
> right runtimes using a tenant-aware elastic load balancer, and
> provides a portal for monitoring and provisioning of tenants on the
> system.
>  3. Foundational Services including security, logging, messaging,
> registry, storage (relational, file, and noSQL), task management, and
> billing.  Foundational services will be loosely-coupled to allow
> swapping in alternate foundational services.
>  4. A Cartridge Architecture allowing frameworks, servers, and other
> runtimes to participate in the advantages of the system.  The
> Cartridge Architecture must support multi-tenant workloads, and
> provide for various levels of tenant isolation and policy-based
> control over provisioning.
>
> Together these layers offer a foundational layer upon which
> applications and middleware frameworks can be deployed to speed
> time-to-market and simplify the development of scalable applications,
> as well as provide a high level of resource sharing and centralized
> management that can deliver lowest resource, infrastructure, and
> management costs.
> == Background ==
> The Stratos Project has been under development[a] at http://wso2.org
> under the Apache 2.0 license and the Apache Way governance model since
> 2010.  It initially was focussed on providing PaaS benefits to the
> users of WSO2 Carbon middleware platform.  In version 2.0, to be
> released in summer 2013, extensive work has been done to clearly
> separate out the PaaS framework from the products (cartridges) that
> run on top of it.  Stratos now has the ability to run arbitrary
> workloads, including Java, PHP, MySQL, Jetty, Tomcat, and many more.
> == Rationale ==
> PaaS is in demand by enterprises and organizations of all sizes.  The
> drive towards instance provisioning, high resource utilization and
> thus low cost, combined with a wide platform of general-purpose
> services to build on, PaaS has the opportunity to accelerate the
> development cycle and innovation index of a new class of applications,
> services, and business models.
>
> PaaS offerings are widely diversified but largely associated with
> powerful corporate interests.  With the commencement of the Stratos
> project at Apache, vendors and users will have a neutral community
> free from corporate governance restrictions, with which to collaborate
> and accelerate the development of a platform that provides wide
> benefits across the industry.  As a flexible framework, we expect a
> wide variety of platforms to leverage the technology to fill specific
> niches and needs.
> == Current Status ==
> Stratos has been in development since 2010 at WSO2, under the Apache
> License and under the Apache Way.  Contribution to Apache, from which
> many of the core components are sourced, should be very
> straightforward.
> == Meritocracy ==
> The contributors have a longstanding commitment and practice of
> meritocracy in their personal and professional capacities. Many of the
> committers on the existing project are already Apache Committers.
> == Community ==
> The committers recognize the need to support more significant
> contributions from a broad swath of the industry and community.
> Apache is the obvious choice for a project that already embodies
> Apache values and is driven by developers who are committers on many
> other Apache projects.
>
> Stratos has appeal, and should attract community members, from among a
> number of constituencies:
>  * Private PaaS deployment within an enterprise to benefit enterprise
> application deployment.
>  * PaaS p

Re: [DISCUSS] Accept Stratos as an Apache Incubation Project

[Davanum Srinivas]

+1

-- dims

On Tue, Jun 11, 2013 at 5:10 AM, Ross Gardler
 wrote:
> It's with great pleasure that I invite the IPMC to review a new
> proposal [1] for the Apache Incubator. Please let us know if you have
> any questions or comments - as you will see there are plenty of people
> on the initial commit list ready and willing to answer your questions.
>
> I copy the full text of the proposal for your convenience:
>
> = Stratos - A PaaS Framework =
> == Abstract ==
> Stratos will be a polyglot
> [[http://www.gartner.com/it-glossary/platform-as-a-service-paas|PaaS]]
> framework, providing developers a cloud-based environment for
> developing, testing, and running scalable applications, and IT
> providers high utilization rates, automated resource management, and
> platform-wide insight including monitoring and billing.
> == Proposal ==
> The Stratos PaaS framework will encompass four layers:
>  1. An 
> [[http://www.gartner.com/it-glossary/infrastructure-as-a-service-iaas/|IaaS]]-agnostic
> layer that can interface with a wide variety of IaaS systems to
> provide elastic resources, and for multiple IaaS infrastructures to be
> automated at one time (hybrid clouds.)
>  2. A PaaS Controller with a cloud controller that automates and
> monitors IaaS runtime interactions, distributes artifacts to the
> underlying runtimes, deploys workloads, directs runtime traffic to the
> right runtimes using a tenant-aware elastic load balancer, and
> provides a portal for monitoring and provisioning of tenants on the
> system.
>  3. Foundational Services including security, logging, messaging,
> registry, storage (relational, file, and noSQL), task management, and
> billing.  Foundational services will be loosely-coupled to allow
> swapping in alternate foundational services.
>  4. A Cartridge Architecture allowing frameworks, servers, and other
> runtimes to participate in the advantages of the system.  The
> Cartridge Architecture must support multi-tenant workloads, and
> provide for various levels of tenant isolation and policy-based
> control over provisioning.
>
> Together these layers offer a foundational layer upon which
> applications and middleware frameworks can be deployed to speed
> time-to-market and simplify the development of scalable applications,
> as well as provide a high level of resource sharing and centralized
> management that can deliver lowest resource, infrastructure, and
> management costs.
> == Background ==
> The Stratos Project has been under development[a] at http://wso2.org
> under the Apache 2.0 license and the Apache Way governance model since
> 2010.  It initially was focussed on providing PaaS benefits to the
> users of WSO2 Carbon middleware platform.  In version 2.0, to be
> released in summer 2013, extensive work has been done to clearly
> separate out the PaaS framework from the products (cartridges) that
> run on top of it.  Stratos now has the ability to run arbitrary
> workloads, including Java, PHP, MySQL, Jetty, Tomcat, and many more.
> == Rationale ==
> PaaS is in demand by enterprises and organizations of all sizes.  The
> drive towards instance provisioning, high resource utilization and
> thus low cost, combined with a wide platform of general-purpose
> services to build on, PaaS has the opportunity to accelerate the
> development cycle and innovation index of a new class of applications,
> services, and business models.
>
> PaaS offerings are widely diversified but largely associated with
> powerful corporate interests.  With the commencement of the Stratos
> project at Apache, vendors and users will have a neutral community
> free from corporate governance restrictions, with which to collaborate
> and accelerate the development of a platform that provides wide
> benefits across the industry.  As a flexible framework, we expect a
> wide variety of platforms to leverage the technology to fill specific
> niches and needs.
> == Current Status ==
> Stratos has been in development since 2010 at WSO2, under the Apache
> License and under the Apache Way.  Contribution to Apache, from which
> many of the core components are sourced, should be very
> straightforward.
> == Meritocracy ==
> The contributors have a longstanding commitment and practice of
> meritocracy in their personal and professional capacities. Many of the
> committers on the existing project are already Apache Committers.
> == Community ==
> The committers recognize the need to support more significant
> contributions from a broad swath of the industry and community.
> Apache is the obvious choice for a project that already embodies
> Apache values and is driven by developers who are committers on many
> other Apache projects.
>
> Stratos has appeal, and should attract community members, from among a
> number of constituencies:
>  * Private PaaS deployment within an enterprise to benefit enterprise
> application deployment.
>  * PaaS providers wishing to leverage a PaaS toolkit to build a PaaS
> customized to their par

Re: [DISCUSS] Accept Stratos as an Apache Incubation Project

[Sanjiva Weerawarana]

On Thu, Jun 13, 2013 at 5:02 AM, Marvin Humphrey wrote:

> > == Known Risks ==
> > Stratos has largely been developed by sponsored developers employed at
> > a single organization - WSO2.  Seeking a broader community of
> > contributors is a top goal of contributing Stratos to Apache.
> > WSO2 plans to continue to offer services and commercial support
> > packages for Stratos, so there is a financial incentive to broaden
> > Stratos’ appeal.  This may provide the misinterpretation that Stratos
> > remains merely a WSO2 technology.  However, WSO2’s main business
> > strategy is to build and support higher level PaaS offerings
> > (including the WSO2 middleware stack) on top of a common PaaS
> > framework, as provided by Stratos.  This includes a WSO2 StratosLive
> > option which is a public PaaS based on WSO2 Stratos.
>
> Kudos for the honest self-analysis.
>

Thanks :-).

I wonder whether Apache Brand Management would cry foul on a trademark like
> "StratosLive" if such a product were to appear later because of the
> "confusingly similar name" guideline.  We've seen project founders leave
> and
> compete with ASF products while using confusingly similar names before,
> e.g.
> CouchBase.
>

Yeah we also thought about that .. if StratosLive is too close to home we
can certainly change it. Bit painful but not impossible.

If a "top goal" is "seeking a broader community of contributors", the
> project
> might benefit if it could find a way to reassure potential contributors on
> this matter.  Perhaps the name for the WS02 product should be vetted in
> advance?
>

Yep can do - our current thinking is to have a WSO2 distribution that
contains Apache Stratos and includes all of our middleware products (app
server, esb, etc. etc.). That is, a PaaS built on the PaaS framework from
Apache.

The thinking is to not give that a specific name but rather call it the
WSO2 distribution of Apache Stratos (or something like that).

Shane do you have thoughts on that? That idea is based on what some others
do and it seems to me is clear enough that its not just the Apache code
being redistributed but has more stuff. Analogous to Redhat being a Linux
distribution.

Cheers,

Sanjiva.
-- 
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
650 265 8311
blog: http://sanjiva.weerawarana.org/

Lean . Enterprise . Middleware

Re: [DISCUSS] Accept Stratos as an Apache Incubation Project

[Marvin Humphrey]

On Tue, Jun 11, 2013 at 2:10 AM, Ross Gardler
 wrote:
> It's with great pleasure that I invite the IPMC to review a new
> proposal [1] for the Apache Incubator. Please let us know if you have
> any questions or comments - as you will see there are plenty of people
> on the initial commit list ready and willing to answer your questions.

It is certainly a large group and a thoroughly prepared proposal with a lot of
resources behind it.

> == Known Risks ==
> Stratos has largely been developed by sponsored developers employed at
> a single organization - WSO2.  Seeking a broader community of
> contributors is a top goal of contributing Stratos to Apache.
> WSO2 plans to continue to offer services and commercial support
> packages for Stratos, so there is a financial incentive to broaden
> Stratos’ appeal.  This may provide the misinterpretation that Stratos
> remains merely a WSO2 technology.  However, WSO2’s main business
> strategy is to build and support higher level PaaS offerings
> (including the WSO2 middleware stack) on top of a common PaaS
> framework, as provided by Stratos.  This includes a WSO2 StratosLive
> option which is a public PaaS based on WSO2 Stratos.

Kudos for the honest self-analysis.

I wonder whether Apache Brand Management would cry foul on a trademark like
"StratosLive" if such a product were to appear later because of the
"confusingly similar name" guideline.  We've seen project founders leave and
compete with ASF products while using confusingly similar names before, e.g.
CouchBase.

If a "top goal" is "seeking a broader community of contributors", the project
might benefit if it could find a way to reassure potential contributors on
this matter.  Perhaps the name for the WS02 product should be vetted in
advance?

  http://www.apache.org/foundation/marks/

> === Mailing Lists ===
>  1. d...@stratos.incubator.apache.org - for developer/user discussions,
>  JIRA change notifications & continuous build/test notifications
>  2. comm...@stratos.incubator.apache.org - for commit mails

It's a technicality, but the podling would also need a private@ list.
Since there's only a combined dev/user list to start with though, obviously
some thought has gone into this. :)

Marvin Humphrey

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

Re: [VOTE] Graduation of Apache Mesos

[Mattmann, Chris A (398J)]

Woot awesome Andy!

Sent from my iPhone

On Jun 12, 2013, at 3:48 PM, "Benjamin Hindman"  wrote:

> Thanks Andy!
> 
> 
> On Wed, Jun 12, 2013 at 3:35 PM, Andy Konwinski 
> wrote:
> 
>> I've regenerated the incubator website and clutch so that the following
>> live pages are now up to date:
>> * our status page 
>> * the list of projects page 
>> * our entry on the clutch page ,
>> which shows all green except for our somewhat large # days in incubation,
>> which implies it is about time we graduate!
>> 
>> Andy
>> 
>> On Wed, Jun 12, 2013 at 3:13 PM, Andy Konwinski >> wrote:
>> 
>>> Thanks Joe for pointing this out,
>>> 
>>> Chris, I beat you to it. I updated the files that the status page<
>> http://incubator.apache.org/projects/mesos.html>
>>> and list of projects page 
>> (which lists
>>> our mentors) are generated from in SVN.
>>> 
>>> Andy
>>> 
>>> 
>>> On Wed, Jun 12, 2013 at 3:11 PM, Mattmann, Chris A (398J) <
>>> chris.a.mattm...@jpl.nasa.gov> wrote:
>>> 
 Hi Joe,
 
 Thanks, I'll update the status page, the canonical set of
 Mesos committers/PPMC members is here (and also part of the
 proposed resolution below):
 
 http://people.apache.org/committers-by-project.html#mesos
 
 
 Cheers,
 Chris
 
 ++
 Chris Mattmann, Ph.D.
 Senior Computer Scientist
 NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
 Office: 171-266B, Mailstop: 171-246
 Email: chris.a.mattm...@nasa.gov
 WWW:  http://sunset.usc.edu/~mattmann/
 ++
 Adjunct Assistant Professor, Computer Science Department
 University of Southern California, Los Angeles, CA 90089 USA
 ++
 
 
 
 
 
 
 -Original Message-
 From: Joe Brockmeier 
 Reply-To: "general@incubator.apache.org" 
 Date: Wednesday, June 12, 2013 1:31 PM
 To: "general@incubator.apache.org" 
 Subject: Re: [VOTE] Graduation of Apache Mesos
 
> Have you updated your Incubator status page prior to this? I think
>> there
> must be quite a few committers added since the proposal that are
>> missing
> there.
> 
> On Wed, Jun 12, 2013, at 03:03 PM, Mattmann, Chris A (398J) wrote:
>> Hi All,
>> 
>> The Apache Mesos community is ready to graduate. They have added
>> committers and PPMC members while in the Incubator; have made a
>> few releases; are discussing their issues on list and in the Apache
>> way, and are inclusive and representative of Apache's goals as a
>> Foundation.
>> 
>> I'm extremely happy to put them up for Incubator graduation.
>> We've VOTEd as a community to move forward with this:
>> 
>> DISCUSS thread here: http://s.apache.org/XAu
>> VOTE thread here: http://s.apache.org/K8C
>> VOTE RESULT: Message-ID: <
>> cdde1f13.d6ea1%chris.a.mattm...@jpl.nasa.gov
> 
>> 
>> Project Incubator status page here:
>> http://incubator.apache.org/projects/mesos.html
>> 
>> Board resolution pasted at bottom of email.
>> 
>> Existing tallies from the community VOTE:
>> 
>> +1
>> Chris Mattmann*
>> Vinod Kone
>> Benjamin Hindman
>> Benjamin Mahler
>> Yan Xiu
>> Deepal Jayasinghe
>> Brenden Matthews
>> Matei Zaharia
>> Ant Elder*
>> Konstantin Boudnik
>> 
>> * - indicates IPMC
>> 
>> Please VOTE to graduate Apache Mesos from the Incubator. Though
>> only Incubator PMC member VOTEs are binding, all are welcome to
>> voice your opinion. I'll leave the VOTE open for at least 72 hours,
>> and hopefully can get enough VOTEs in time to close it by Saturday
>> or Sunday in time for the board meeting on 6/19.
>> 
>> [ ] +1 Graduate Apache Mesos from the Incubator.
>> [ ] +0 Don't care.
>> [ ] -1 Don't graduate Apache Mesos from the Incubator because..
>> 
>> Thanks everyone!
>> 
>> Cheers,
>> Chris
>> 
>> 
>> ---board resolution
>> WHEREAS, the Board of Directors deems it to be in the best
>> interests of the Foundation and consistent with the
>> Foundation's purpose to establish a Project Management
>> Committee charged with the creation and maintenance of
>> open-source software, for distribution at no charge to the
>> public, related to efficient cluster management, resource
>> isolation and sharing across distributed applications.
>> 
>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>> Committee (PMC), to be known as the "Apache Mesos Project", be
>> and hereby is established pursuant to Bylaws of the Foundat

Re: [VOTE] Graduation of Apache Mesos

[Mattmann, Chris A (398J)]

Hi Joe,

Thanks, I'll update the status page, the canonical set of
Mesos committers/PPMC members is here (and also part of the
proposed resolution below):

http://people.apache.org/committers-by-project.html#mesos


Cheers,
Chris

++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattm...@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++






-Original Message-
From: Joe Brockmeier 
Reply-To: "general@incubator.apache.org" 
Date: Wednesday, June 12, 2013 1:31 PM
To: "general@incubator.apache.org" 
Subject: Re: [VOTE] Graduation of Apache Mesos

>Have you updated your Incubator status page prior to this? I think there
>must be quite a few committers added since the proposal that are missing
>there. 
>
>On Wed, Jun 12, 2013, at 03:03 PM, Mattmann, Chris A (398J) wrote:
>> Hi All,
>> 
>> The Apache Mesos community is ready to graduate. They have added
>> committers and PPMC members while in the Incubator; have made a
>> few releases; are discussing their issues on list and in the Apache
>> way, and are inclusive and representative of Apache's goals as a
>> Foundation.
>> 
>> I'm extremely happy to put them up for Incubator graduation.
>> We've VOTEd as a community to move forward with this:
>> 
>> DISCUSS thread here: http://s.apache.org/XAu
>> VOTE thread here: http://s.apache.org/K8C
>> VOTE RESULT: Message-ID: 
>> 
>> Project Incubator status page here:
>> http://incubator.apache.org/projects/mesos.html
>> 
>> Board resolution pasted at bottom of email.
>> 
>> Existing tallies from the community VOTE:
>> 
>> +1
>> Chris Mattmann*
>> Vinod Kone
>> Benjamin Hindman
>> Benjamin Mahler
>> Yan Xiu
>> Deepal Jayasinghe
>> Brenden Matthews
>> Matei Zaharia
>> Ant Elder*
>> Konstantin Boudnik
>> 
>> * - indicates IPMC
>> 
>> Please VOTE to graduate Apache Mesos from the Incubator. Though
>> only Incubator PMC member VOTEs are binding, all are welcome to
>> voice your opinion. I'll leave the VOTE open for at least 72 hours,
>> and hopefully can get enough VOTEs in time to close it by Saturday
>> or Sunday in time for the board meeting on 6/19.
>> 
>> [ ] +1 Graduate Apache Mesos from the Incubator.
>> [ ] +0 Don't care.
>> [ ] -1 Don't graduate Apache Mesos from the Incubator because..
>> 
>> Thanks everyone!
>> 
>> Cheers,
>> Chris
>> 
>> 
>> ---board resolution
>> WHEREAS, the Board of Directors deems it to be in the best
>> interests of the Foundation and consistent with the
>> Foundation's purpose to establish a Project Management
>> Committee charged with the creation and maintenance of
>> open-source software, for distribution at no charge to the
>> public, related to efficient cluster management, resource
>> isolation and sharing across distributed applications.
>> 
>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>> Committee (PMC), to be known as the "Apache Mesos Project", be
>> and hereby is established pursuant to Bylaws of the Foundation;
>> and be it further
>> 
>> RESOLVED, that the Apache Mesos Project be and hereby is
>> responsible for the creation and maintenance of software
>> related to efficient cluster management, resource isolation
>> and sharing across distributed applications; and be it further
>> RESOLVED, that the office of "Vice President, Apache Mesos" be
>> and hereby is created, the person holding such office to serve
>> at the direction of the Board of Directors as the chair of the
>> Apache Mesos Project, and to have primary responsibility for
>> management of the projects within the scope of responsibility
>> of the Apache Mesos Project; and be it further
>> RESOLVED, that the persons listed immediately below be and
>> hereby are appointed to serve as the initial members of the
>> Apache Mesos Project:
>> 
>>  * Ali Ghodsi 
>> * Andy Konwinski 
>> * Benjamin Hindhman 
>> * Benjamin Mahler 
>> * Brian McCalister 
>> * Ian Holsman 
>> * Matei Alexandru Zahari 
>> * Chris Mattmann 
>> * Tom White 
>> * Vinod Kone 
>> * Brenden Matthews 
>> * Thomas Marshall 
>> * Charles Reiss 
>> 
>> 
>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Benjamin Hindman be
>> appointed to the office of Vice President, Apache Mesos, to
>> serve in accordance with and subject to the direction of the
>> Board of Directors and the Bylaws of the Foundation until
>> death, resignation, retirement, removal or disqualification, or
>> until a successor is appointed; and be it further
>> 
>> RESOLVED, that the Apache Mesos Project be and hereby is
>> tasked with the migration and rationalization of the Apache
>> Incubator Mesos podling; and be it further
>> 
>> RESOLVED, that a

Re: [VOTE] Graduation of Apache Mesos

[Henry Saputra]

+1 binding

Awesome work guys =)


- Henry


On Wed, Jun 12, 2013 at 1:03 PM, Mattmann, Chris A (398J) <
chris.a.mattm...@jpl.nasa.gov> wrote:

> Hi All,
>
> The Apache Mesos community is ready to graduate. They have added
> committers and PPMC members while in the Incubator; have made a
> few releases; are discussing their issues on list and in the Apache
> way, and are inclusive and representative of Apache's goals as a
> Foundation.
>
> I'm extremely happy to put them up for Incubator graduation.
> We've VOTEd as a community to move forward with this:
>
> DISCUSS thread here: http://s.apache.org/XAu
> VOTE thread here: http://s.apache.org/K8C
> VOTE RESULT: Message-ID: 
>
> Project Incubator status page here:
> http://incubator.apache.org/projects/mesos.html
>
> Board resolution pasted at bottom of email.
>
> Existing tallies from the community VOTE:
>
> +1
> Chris Mattmann*
> Vinod Kone
> Benjamin Hindman
> Benjamin Mahler
> Yan Xiu
> Deepal Jayasinghe
> Brenden Matthews
> Matei Zaharia
> Ant Elder*
> Konstantin Boudnik
>
> * - indicates IPMC
>
> Please VOTE to graduate Apache Mesos from the Incubator. Though
> only Incubator PMC member VOTEs are binding, all are welcome to
> voice your opinion. I'll leave the VOTE open for at least 72 hours,
> and hopefully can get enough VOTEs in time to close it by Saturday
> or Sunday in time for the board meeting on 6/19.
>
> [ ] +1 Graduate Apache Mesos from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Mesos from the Incubator because..
>
> Thanks everyone!
>
> Cheers,
> Chris
>
>
> ---board resolution
> WHEREAS, the Board of Directors deems it to be in the best
> interests of the Foundation and consistent with the
> Foundation's purpose to establish a Project Management
> Committee charged with the creation and maintenance of
> open-source software, for distribution at no charge to the
> public, related to efficient cluster management, resource
> isolation and sharing across distributed applications.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Mesos Project", be
> and hereby is established pursuant to Bylaws of the Foundation;
> and be it further
>
> RESOLVED, that the Apache Mesos Project be and hereby is
> responsible for the creation and maintenance of software
> related to efficient cluster management, resource isolation
> and sharing across distributed applications; and be it further
> RESOLVED, that the office of "Vice President, Apache Mesos" be
> and hereby is created, the person holding such office to serve
> at the direction of the Board of Directors as the chair of the
> Apache Mesos Project, and to have primary responsibility for
> management of the projects within the scope of responsibility
> of the Apache Mesos Project; and be it further
> RESOLVED, that the persons listed immediately below be and
> hereby are appointed to serve as the initial members of the
> Apache Mesos Project:
>
>  * Ali Ghodsi 
> * Andy Konwinski 
> * Benjamin Hindhman 
> * Benjamin Mahler 
> * Brian McCalister 
> * Ian Holsman 
> * Matei Alexandru Zahari 
> * Chris Mattmann 
> * Tom White 
> * Vinod Kone 
> * Brenden Matthews 
> * Thomas Marshall 
> * Charles Reiss 
>
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Benjamin Hindman be
> appointed to the office of Vice President, Apache Mesos, to
> serve in accordance with and subject to the direction of the
> Board of Directors and the Bylaws of the Foundation until
> death, resignation, retirement, removal or disqualification, or
> until a successor is appointed; and be it further
>
> RESOLVED, that the Apache Mesos Project be and hereby is
> tasked with the migration and rationalization of the Apache
> Incubator Mesos podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Mesos podling encumbered upon the Apache Incubator
> Project are hereafter discharged.
>
>
> ++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattm...@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++
>
>
>
>
>

Re: [VOTE] Graduation of Apache Mesos

[Tom White]

+1

Tom

On Wed, Jun 12, 2013 at 9:03 PM, Mattmann, Chris A (398J)
 wrote:
> Hi All,
>
> The Apache Mesos community is ready to graduate. They have added
> committers and PPMC members while in the Incubator; have made a
> few releases; are discussing their issues on list and in the Apache
> way, and are inclusive and representative of Apache's goals as a
> Foundation.
>
> I'm extremely happy to put them up for Incubator graduation.
> We've VOTEd as a community to move forward with this:
>
> DISCUSS thread here: http://s.apache.org/XAu
> VOTE thread here: http://s.apache.org/K8C
> VOTE RESULT: Message-ID: 
>
> Project Incubator status page here:
> http://incubator.apache.org/projects/mesos.html
>
> Board resolution pasted at bottom of email.
>
> Existing tallies from the community VOTE:
>
> +1
> Chris Mattmann*
> Vinod Kone
> Benjamin Hindman
> Benjamin Mahler
> Yan Xiu
> Deepal Jayasinghe
> Brenden Matthews
> Matei Zaharia
> Ant Elder*
> Konstantin Boudnik
>
> * - indicates IPMC
>
> Please VOTE to graduate Apache Mesos from the Incubator. Though
> only Incubator PMC member VOTEs are binding, all are welcome to
> voice your opinion. I'll leave the VOTE open for at least 72 hours,
> and hopefully can get enough VOTEs in time to close it by Saturday
> or Sunday in time for the board meeting on 6/19.
>
> [ ] +1 Graduate Apache Mesos from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Mesos from the Incubator because..
>
> Thanks everyone!
>
> Cheers,
> Chris
>
>
> ---board resolution
> WHEREAS, the Board of Directors deems it to be in the best
> interests of the Foundation and consistent with the
> Foundation's purpose to establish a Project Management
> Committee charged with the creation and maintenance of
> open-source software, for distribution at no charge to the
> public, related to efficient cluster management, resource
> isolation and sharing across distributed applications.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Mesos Project", be
> and hereby is established pursuant to Bylaws of the Foundation;
> and be it further
>
> RESOLVED, that the Apache Mesos Project be and hereby is
> responsible for the creation and maintenance of software
> related to efficient cluster management, resource isolation
> and sharing across distributed applications; and be it further
> RESOLVED, that the office of "Vice President, Apache Mesos" be
> and hereby is created, the person holding such office to serve
> at the direction of the Board of Directors as the chair of the
> Apache Mesos Project, and to have primary responsibility for
> management of the projects within the scope of responsibility
> of the Apache Mesos Project; and be it further
> RESOLVED, that the persons listed immediately below be and
> hereby are appointed to serve as the initial members of the
> Apache Mesos Project:
>
>  * Ali Ghodsi 
> * Andy Konwinski 
> * Benjamin Hindhman 
> * Benjamin Mahler 
> * Brian McCalister 
> * Ian Holsman 
> * Matei Alexandru Zahari 
> * Chris Mattmann 
> * Tom White 
> * Vinod Kone 
> * Brenden Matthews 
> * Thomas Marshall 
> * Charles Reiss 
>
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Benjamin Hindman be
> appointed to the office of Vice President, Apache Mesos, to
> serve in accordance with and subject to the direction of the
> Board of Directors and the Bylaws of the Foundation until
> death, resignation, retirement, removal or disqualification, or
> until a successor is appointed; and be it further
>
> RESOLVED, that the Apache Mesos Project be and hereby is
> tasked with the migration and rationalization of the Apache
> Incubator Mesos podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Mesos podling encumbered upon the Apache Incubator
> Project are hereafter discharged.
>
>
> ++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattm...@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++
>
>
>
>
>
> -
> 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: [VOTE] Accept Apache HotdoG into the Incubator

[Suresh Marru]

+ 1 (binding).

Suresh

On Jun 12, 2013, at 2:22 PM, "Ramirez, Paul M (398J)" 
 wrote:

> All,
> 
> I'd like to call a VOTE for the acceptance of Apache HotdoG into the 
> Incubator. I'll leave the VOTE open for the rest of the week and close it out 
> Monday, June 17th early am PT.
> 
> [ ] +1 Accept Apache HotdoG into the Incubator
> [ ] +0 Don't care.
> [ ] -1 Don't accept Apache HotdoG because...
> 
> Full Proposal is pasted at the end of this email. Only VOTEs from Incubator 
> PMC members are binding, but all are welcome to express their thoughts.
> 
> This is a second pass at this vote as I canceled it to pull in more mentors. 
> The following people voted on the first pass:
> 
> Henry Saputra +1 (binding)
> Chris Mattmann + 1 (binding)
> 
> Thanks!
> Paul Ramirez
> 
> P.S. +1 from me (binding)
> 
> 
> = HotdoG Proposal =
> 
> == Abstract ==
> 
> The HotdoG project is an effort and suite of tools to convert HDF/HDF-EOS 
> format into GeoTIFF format. This is the first of a potential series of 
> incoming projects originating from The HDF Group -- the non-profit 
> organization is interested in evaluating the ASF as a potential home for many 
> of its projects. The HDF Group is an independently funded organization that 
> started many years ago with major investment from NASA as the Hierarchical 
> Data Format (HDF), version 4 and now version 5, is the ''de facto'' remote 
> sensing data format for NASA missions, and an increasing number of other 
> disciplines including bio medicine, radio astronomy, climate science, and 
> other domains.
> 
> HDF is both a data and metadata format, as well as a model for representing 
> and access information. There are numerous downstream tools that can read and 
> write HDF data, including a growing number of Geospatial data tools 
> (ESRI-based, and also OpenGeo and other community led efforts). In addition, 
> major interoperability efforts are also occurring between the remote sensing 
> community and the climate modeling community (which has traditionally favored 
> NetCDF as opposed to HDF) because of the efforts in HDF5 to leverage a common 
> data format and model.
> 
> HotdoG is poised to be a first of its kind in the form of bringing one of the 
> major 2 data formats for science to the ASF (the other being the NetCDF 
> format).
> 
> == Proposal ==
> HotdoG is a software converter that converts Earth Science data in 
> HDF/HDF-EOS format into GeoTIFF format. Doing so easily enables users of 
> remote sensing data to interoperate with common GIS tools (like WebGIS, Web 
> Processing, image analysis, and geo computational tools). We feel that the 
> project is an incremental step, and an appropriate focus with tangible 
> success possibilities by restraining our focus to HDF/HDF-EOS to GeoTIFF 
> conversion.
> 
> There are numerous interesting paths that we can take the toolkit in -- as 
> conversion from remotely sensed data to GeoTIFF involves ensuring that the 
> HDF-EOS metadata elements can be appropriately represented using GeoTIFF 
> headers, and the associated format. Furthermore, capturing the HDF's 
> appropriate geo datum in GeoTIFF will be another important challenge.
> 
> == Background ==
> 
> GeoTIFF is a data and metadata standard for Earth science applications. It is 
> based on binary Tagged Image File Format (TIFF).  A GeoTIFF file has 
> geographic (or cartographic) data embedded as tags within the TIFF file that 
> are used to geo-locate the image. This is required for correct integration of 
> the image in Geographic Information Systems (GIS) and other popular tools 
> like Google Earth Pro.
> 
> In the recent years, GeoTIFF has gained popularity as a visualization format 
> among NASA HDF Earth science user communities according to the NASA data 
> user's survey. However, the conversion from HDF to GeoTIFF is not 
> straightforward for end users because NASA HDF data products are diverse and 
> organized in many different ways. For example, go to http://hdfeos.org/zoo 
> and you'll see many scripting language examples because no single script can 
> correctly visualize all NASA HDF data.
> 
> == Rationale ==
> 
> The HEG tool is limited to some NASA HDF-EOS2 products (no support for 
> HDF-EOS5 products) and it is not an open-source tool. The latest GDAL 
> (version 1.9.2 and above) is an open-source tool but it cannot handle many 
> non-HDF-EOS NASA HDF products such as TRMM (pure HDF4) and Aquarius (pure 
> HDF5) correctly and automatically.
> 
> == Initial Goals ==
> 
> We'll improve GDAL to support NASA HDF products better by handling 
> geo-location information and physical meaning of data correctly and 
> automatically.
> 
> We'll handle NASA products intelligently so novice users don't have to supply 
> many options or figure out the details about the data products. For advanced 
> users, we'll give a full control of accessing HDF products in many different 
> ways so that the converted GeoTIFF file is scientifically valid and 

Re: [VOTE] Accept Apache HotdoG into the Incubator

[Roman Shaposhnik]

On Wed, Jun 12, 2013 at 11:22 AM, Ramirez, Paul M (398J)
 wrote:
> All,
>
> I'd like to call a VOTE for the acceptance of Apache HotdoG into the 
> Incubator. I'll leave the VOTE open for the rest of the week and close it out 
> Monday, June 17th early am PT.
>
> [ ] +1 Accept Apache HotdoG into the Incubator
> [ ] +0 Don't care.
> [ ] -1 Don't accept Apache HotdoG because...

+1 (binding)

Thanks,
Roman.

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

Re: [VOTE] Graduation of Apache Mesos

[Joe Brockmeier]

Have you updated your Incubator status page prior to this? I think there
must be quite a few committers added since the proposal that are missing
there. 

On Wed, Jun 12, 2013, at 03:03 PM, Mattmann, Chris A (398J) wrote:
> Hi All,
> 
> The Apache Mesos community is ready to graduate. They have added
> committers and PPMC members while in the Incubator; have made a
> few releases; are discussing their issues on list and in the Apache
> way, and are inclusive and representative of Apache's goals as a
> Foundation.
> 
> I'm extremely happy to put them up for Incubator graduation.
> We've VOTEd as a community to move forward with this:
> 
> DISCUSS thread here: http://s.apache.org/XAu
> VOTE thread here: http://s.apache.org/K8C
> VOTE RESULT: Message-ID: 
> 
> Project Incubator status page here:
> http://incubator.apache.org/projects/mesos.html
> 
> Board resolution pasted at bottom of email.
> 
> Existing tallies from the community VOTE:
> 
> +1
> Chris Mattmann*
> Vinod Kone
> Benjamin Hindman
> Benjamin Mahler
> Yan Xiu
> Deepal Jayasinghe
> Brenden Matthews
> Matei Zaharia
> Ant Elder*
> Konstantin Boudnik
> 
> * - indicates IPMC
> 
> Please VOTE to graduate Apache Mesos from the Incubator. Though
> only Incubator PMC member VOTEs are binding, all are welcome to
> voice your opinion. I'll leave the VOTE open for at least 72 hours,
> and hopefully can get enough VOTEs in time to close it by Saturday
> or Sunday in time for the board meeting on 6/19.
> 
> [ ] +1 Graduate Apache Mesos from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Mesos from the Incubator because..
> 
> Thanks everyone!
> 
> Cheers,
> Chris
> 
> 
> ---board resolution
> WHEREAS, the Board of Directors deems it to be in the best
> interests of the Foundation and consistent with the
> Foundation's purpose to establish a Project Management
> Committee charged with the creation and maintenance of
> open-source software, for distribution at no charge to the
> public, related to efficient cluster management, resource
> isolation and sharing across distributed applications.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Mesos Project", be
> and hereby is established pursuant to Bylaws of the Foundation;
> and be it further
> 
> RESOLVED, that the Apache Mesos Project be and hereby is
> responsible for the creation and maintenance of software
> related to efficient cluster management, resource isolation
> and sharing across distributed applications; and be it further
> RESOLVED, that the office of "Vice President, Apache Mesos" be
> and hereby is created, the person holding such office to serve
> at the direction of the Board of Directors as the chair of the
> Apache Mesos Project, and to have primary responsibility for
> management of the projects within the scope of responsibility
> of the Apache Mesos Project; and be it further
> RESOLVED, that the persons listed immediately below be and
> hereby are appointed to serve as the initial members of the
> Apache Mesos Project:
> 
>  * Ali Ghodsi 
> * Andy Konwinski 
> * Benjamin Hindhman 
> * Benjamin Mahler 
> * Brian McCalister 
> * Ian Holsman 
> * Matei Alexandru Zahari 
> * Chris Mattmann 
> * Tom White 
> * Vinod Kone 
> * Brenden Matthews 
> * Thomas Marshall 
> * Charles Reiss 
> 
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Benjamin Hindman be
> appointed to the office of Vice President, Apache Mesos, to
> serve in accordance with and subject to the direction of the
> Board of Directors and the Bylaws of the Foundation until
> death, resignation, retirement, removal or disqualification, or
> until a successor is appointed; and be it further
> 
> RESOLVED, that the Apache Mesos Project be and hereby is
> tasked with the migration and rationalization of the Apache
> Incubator Mesos podling; and be it further
> 
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Mesos podling encumbered upon the Apache Incubator
> Project are hereafter discharged.
> 
> 
> ++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattm...@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++
> 
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


Best,

jzb
-- 
Joe Brockmeier
j...@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/

-

[VOTE] Graduation of Apache Mesos

[Mattmann, Chris A (398J)]

Hi All,

The Apache Mesos community is ready to graduate. They have added
committers and PPMC members while in the Incubator; have made a
few releases; are discussing their issues on list and in the Apache
way, and are inclusive and representative of Apache's goals as a
Foundation.

I'm extremely happy to put them up for Incubator graduation.
We've VOTEd as a community to move forward with this:

DISCUSS thread here: http://s.apache.org/XAu
VOTE thread here: http://s.apache.org/K8C
VOTE RESULT: Message-ID: 

Project Incubator status page here:
http://incubator.apache.org/projects/mesos.html

Board resolution pasted at bottom of email.

Existing tallies from the community VOTE:

+1
Chris Mattmann*
Vinod Kone
Benjamin Hindman
Benjamin Mahler
Yan Xiu
Deepal Jayasinghe
Brenden Matthews
Matei Zaharia
Ant Elder*
Konstantin Boudnik

* - indicates IPMC

Please VOTE to graduate Apache Mesos from the Incubator. Though
only Incubator PMC member VOTEs are binding, all are welcome to
voice your opinion. I'll leave the VOTE open for at least 72 hours,
and hopefully can get enough VOTEs in time to close it by Saturday
or Sunday in time for the board meeting on 6/19.

[ ] +1 Graduate Apache Mesos from the Incubator.
[ ] +0 Don't care.
[ ] -1 Don't graduate Apache Mesos from the Incubator because..

Thanks everyone!

Cheers,
Chris


---board resolution
WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software, for distribution at no charge to the
public, related to efficient cluster management, resource
isolation and sharing across distributed applications.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache Mesos Project", be
and hereby is established pursuant to Bylaws of the Foundation;
and be it further

RESOLVED, that the Apache Mesos Project be and hereby is
responsible for the creation and maintenance of software
related to efficient cluster management, resource isolation
and sharing across distributed applications; and be it further
RESOLVED, that the office of "Vice President, Apache Mesos" be
and hereby is created, the person holding such office to serve
at the direction of the Board of Directors as the chair of the
Apache Mesos Project, and to have primary responsibility for
management of the projects within the scope of responsibility
of the Apache Mesos Project; and be it further
RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache Mesos Project:

 * Ali Ghodsi 
* Andy Konwinski 
* Benjamin Hindhman 
* Benjamin Mahler 
* Brian McCalister 
* Ian Holsman 
* Matei Alexandru Zahari 
* Chris Mattmann 
* Tom White 
* Vinod Kone 
* Brenden Matthews 
* Thomas Marshall 
* Charles Reiss 


NOW, THEREFORE, BE IT FURTHER RESOLVED, that Benjamin Hindman be
appointed to the office of Vice President, Apache Mesos, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification, or
until a successor is appointed; and be it further

RESOLVED, that the Apache Mesos Project be and hereby is
tasked with the migration and rationalization of the Apache
Incubator Mesos podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache
Incubator Mesos podling encumbered upon the Apache Incubator
Project are hereafter discharged.


++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattm...@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++





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

Re: [DISCUSS] Accept Stratos as an Apache Incubation Project

[Chip Childers]

On Wed, Jun 12, 2013 at 09:53:22PM +0200, Mohammad Nour El-Din wrote:
> Hi
> 
> The proposal is well detailed and very informative, the purpose of the
> projects fits ASF's Cloud Ecosystem and the community is very promising
> already reminds me with the one of ACS. Very looking forward to start
> rolling the podling tasks

+1 - looking forward to seeing the VOTE start, and for us to get going
on building an ACS provider plugin ;-)

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

Re: [VOTE] Accept Apache HotdoG into the Incubator

[Joe Brockmeier]

On Wed, Jun 12, 2013, at 01:22 PM, Ramirez, Paul M (398J) wrote:
> I'd like to call a VOTE for the acceptance of Apache HotdoG into the
> Incubator. I'll leave the VOTE open for the rest of the week and close it
> out Monday, June 17th early am PT.
> 
> [ ] +1 Accept Apache HotdoG into the Incubator
> [ ] +0 Don't care.
> [ ] -1 Don't accept Apache HotdoG because...
> 
> Full Proposal is pasted at the end of this email. Only VOTEs from
> Incubator PMC members are binding, but all are welcome to express their
> thoughts.

+1 (binding)

Best,

jzb
-- 
Joe Brockmeier
j...@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/

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

Re: [DISCUSS] Accept Stratos as an Apache Incubation Project

[Mohammad Nour El-Din]

Hi

The proposal is well detailed and very informative, the purpose of the
projects fits ASF's Cloud Ecosystem and the community is very promising
already reminds me with the one of ACS. Very looking forward to start
rolling the podling tasks


On Tue, Jun 11, 2013 at 11:46 AM, Christian Grobmeier
wrote:

> Impressive proposal. Reminds me on RH OpenShift actually.
>
> Please note the first two links are broken in gmail.
> They are:
>
> * http://www.gartner.com/it-glossary/platform-as-a-service-paas
> * http://www.gartner.com/it-glossary/infrastructure-as-a-service-iaas
>
> Anyway, proposal looks really good for me.
>
>
> On Tue, Jun 11, 2013 at 11:10 AM, Ross Gardler
>  wrote:
> > It's with great pleasure that I invite the IPMC to review a new
> > proposal [1] for the Apache Incubator. Please let us know if you have
> > any questions or comments - as you will see there are plenty of people
> > on the initial commit list ready and willing to answer your questions.
> >
> > I copy the full text of the proposal for your convenience:
> >
> > = Stratos - A PaaS Framework =
> > == Abstract ==
> > Stratos will be a polyglot
> > [[http://www.gartner.com/it-glossary/platform-as-a-service-paas|PaaS]]
> > framework, providing developers a cloud-based environment for
> > developing, testing, and running scalable applications, and IT
> > providers high utilization rates, automated resource management, and
> > platform-wide insight including monitoring and billing.
> > == Proposal ==
> > The Stratos PaaS framework will encompass four layers:
> >  1. An [[
> http://www.gartner.com/it-glossary/infrastructure-as-a-service-iaas/|IaaS]]-agnostic
> > layer that can interface with a wide variety of IaaS systems to
> > provide elastic resources, and for multiple IaaS infrastructures to be
> > automated at one time (hybrid clouds.)
> >  2. A PaaS Controller with a cloud controller that automates and
> > monitors IaaS runtime interactions, distributes artifacts to the
> > underlying runtimes, deploys workloads, directs runtime traffic to the
> > right runtimes using a tenant-aware elastic load balancer, and
> > provides a portal for monitoring and provisioning of tenants on the
> > system.
> >  3. Foundational Services including security, logging, messaging,
> > registry, storage (relational, file, and noSQL), task management, and
> > billing.  Foundational services will be loosely-coupled to allow
> > swapping in alternate foundational services.
> >  4. A Cartridge Architecture allowing frameworks, servers, and other
> > runtimes to participate in the advantages of the system.  The
> > Cartridge Architecture must support multi-tenant workloads, and
> > provide for various levels of tenant isolation and policy-based
> > control over provisioning.
> >
> > Together these layers offer a foundational layer upon which
> > applications and middleware frameworks can be deployed to speed
> > time-to-market and simplify the development of scalable applications,
> > as well as provide a high level of resource sharing and centralized
> > management that can deliver lowest resource, infrastructure, and
> > management costs.
> > == Background ==
> > The Stratos Project has been under development[a] at http://wso2.org
> > under the Apache 2.0 license and the Apache Way governance model since
> > 2010.  It initially was focussed on providing PaaS benefits to the
> > users of WSO2 Carbon middleware platform.  In version 2.0, to be
> > released in summer 2013, extensive work has been done to clearly
> > separate out the PaaS framework from the products (cartridges) that
> > run on top of it.  Stratos now has the ability to run arbitrary
> > workloads, including Java, PHP, MySQL, Jetty, Tomcat, and many more.
> > == Rationale ==
> > PaaS is in demand by enterprises and organizations of all sizes.  The
> > drive towards instance provisioning, high resource utilization and
> > thus low cost, combined with a wide platform of general-purpose
> > services to build on, PaaS has the opportunity to accelerate the
> > development cycle and innovation index of a new class of applications,
> > services, and business models.
> >
> > PaaS offerings are widely diversified but largely associated with
> > powerful corporate interests.  With the commencement of the Stratos
> > project at Apache, vendors and users will have a neutral community
> > free from corporate governance restrictions, with which to collaborate
> > and accelerate the development of a platform that provides wide
> > benefits across the industry.  As a flexible framework, we expect a
> > wide variety of platforms to leverage the technology to fill specific
> > niches and needs.
> > == Current Status ==
> > Stratos has been in development since 2010 at WSO2, under the Apache
> > License and under the Apache Way.  Contribution to Apache, from which
> > many of the core components are sourced, should be very
> > straightforward.
> > == Meritocracy ==
> > The contributors have a longstanding com

Re: [VOTE] Accept Apache HotdoG into the Incubator

[Mattmann, Chris A (398J)]

+1 binding.

Cheers,
Chris

++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattm...@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++






-Original Message-
From: , "Paul M   (398J)" 
Reply-To: "general@incubator.apache.org" 
Date: Wednesday, June 12, 2013 11:22 AM
To: "general@incubator.apache.org" 
Subject: [VOTE] Accept Apache HotdoG into the Incubator

>All,
>
>I'd like to call a VOTE for the acceptance of Apache HotdoG into the
>Incubator. I'll leave the VOTE open for the rest of the week and close it
>out Monday, June 17th early am PT.
>
>[ ] +1 Accept Apache HotdoG into the Incubator
>[ ] +0 Don't care.
>[ ] -1 Don't accept Apache HotdoG because...
>
>Full Proposal is pasted at the end of this email. Only VOTEs from
>Incubator PMC members are binding, but all are welcome to express their
>thoughts.
>
>This is a second pass at this vote as I canceled it to pull in more
>mentors. The following people voted on the first pass:
>
>Henry Saputra +1 (binding)
>Chris Mattmann + 1 (binding)
>
>Thanks!
>Paul Ramirez
>
>P.S. +1 from me (binding)
>
>
>= HotdoG Proposal =
>
>== Abstract ==
>
>The HotdoG project is an effort and suite of tools to convert HDF/HDF-EOS
>format into GeoTIFF format. This is the first of a potential series of
>incoming projects originating from The HDF Group -- the non-profit
>organization is interested in evaluating the ASF as a potential home for
>many of its projects. The HDF Group is an independently funded
>organization that started many years ago with major investment from NASA
>as the Hierarchical Data Format (HDF), version 4 and now version 5, is
>the ''de facto'' remote sensing data format for NASA missions, and an
>increasing number of other disciplines including bio medicine, radio
>astronomy, climate science, and other domains.
>
>HDF is both a data and metadata format, as well as a model for
>representing and access information. There are numerous downstream tools
>that can read and write HDF data, including a growing number of
>Geospatial data tools (ESRI-based, and also OpenGeo and other community
>led efforts). In addition, major interoperability efforts are also
>occurring between the remote sensing community and the climate modeling
>community (which has traditionally favored NetCDF as opposed to HDF)
>because of the efforts in HDF5 to leverage a common data format and model.
>
>HotdoG is poised to be a first of its kind in the form of bringing one of
>the major 2 data formats for science to the ASF (the other being the
>NetCDF format).
>
>== Proposal ==
>HotdoG is a software converter that converts Earth Science data in
>HDF/HDF-EOS format into GeoTIFF format. Doing so easily enables users of
>remote sensing data to interoperate with common GIS tools (like WebGIS,
>Web Processing, image analysis, and geo computational tools). We feel
>that the project is an incremental step, and an appropriate focus with
>tangible success possibilities by restraining our focus to HDF/HDF-EOS to
>GeoTIFF conversion.
>
>There are numerous interesting paths that we can take the toolkit in --
>as conversion from remotely sensed data to GeoTIFF involves ensuring that
>the HDF-EOS metadata elements can be appropriately represented using
>GeoTIFF headers, and the associated format. Furthermore, capturing the
>HDF's appropriate geo datum in GeoTIFF will be another important
>challenge.
>
>== Background ==
>
>GeoTIFF is a data and metadata standard for Earth science applications.
>It is based on binary Tagged Image File Format (TIFF).  A GeoTIFF file
>has geographic (or cartographic) data embedded as tags within the TIFF
>file that are used to geo-locate the image. This is required for correct
>integration of the image in Geographic Information Systems (GIS) and
>other popular tools like Google Earth Pro.
>
>In the recent years, GeoTIFF has gained popularity as a visualization
>format among NASA HDF Earth science user communities according to the
>NASA data user's survey. However, the conversion from HDF to GeoTIFF is
>not straightforward for end users because NASA HDF data products are
>diverse and organized in many different ways. For example, go to
>http://hdfeos.org/zoo and you'll see many scripting language examples
>because no single script can correctly visualize all NASA HDF data.
>
>== Rationale ==
>
>The HEG tool is limited to some NASA HDF-EOS2 products (no support for
>HDF-EOS5 products) and it is not an open-source tool. The latest GDAL
>(version 1.9.2 and above) is an open-source tool but it cannot handle
>many non-HDF-EOS NASA HDF products such as TRMM 

Re: [VOTE] Accept Apache HotdoG into the Incubator

[Andrew Hart]

+1 (binding)

Best,
Andrew.


On 06/12/2013 11:22 AM, Ramirez, Paul M (398J) wrote:

All,

I'd like to call a VOTE for the acceptance of Apache HotdoG into the Incubator. 
I'll leave the VOTE open for the rest of the week and close it out Monday, June 
17th early am PT.

[ ] +1 Accept Apache HotdoG into the Incubator
[ ] +0 Don't care.
[ ] -1 Don't accept Apache HotdoG because...

Full Proposal is pasted at the end of this email. Only VOTEs from Incubator PMC 
members are binding, but all are welcome to express their thoughts.

This is a second pass at this vote as I canceled it to pull in more mentors. 
The following people voted on the first pass:

Henry Saputra +1 (binding)
Chris Mattmann + 1 (binding)

Thanks!
Paul Ramirez

P.S. +1 from me (binding)


= HotdoG Proposal =

== Abstract ==

The HotdoG project is an effort and suite of tools to convert HDF/HDF-EOS 
format into GeoTIFF format. This is the first of a potential series of incoming 
projects originating from The HDF Group -- the non-profit organization is 
interested in evaluating the ASF as a potential home for many of its projects. 
The HDF Group is an independently funded organization that started many years 
ago with major investment from NASA as the Hierarchical Data Format (HDF), 
version 4 and now version 5, is the ''de facto'' remote sensing data format for 
NASA missions, and an increasing number of other disciplines including bio 
medicine, radio astronomy, climate science, and other domains.

HDF is both a data and metadata format, as well as a model for representing and 
access information. There are numerous downstream tools that can read and write 
HDF data, including a growing number of Geospatial data tools (ESRI-based, and 
also OpenGeo and other community led efforts). In addition, major 
interoperability efforts are also occurring between the remote sensing 
community and the climate modeling community (which has traditionally favored 
NetCDF as opposed to HDF) because of the efforts in HDF5 to leverage a common 
data format and model.

HotdoG is poised to be a first of its kind in the form of bringing one of the 
major 2 data formats for science to the ASF (the other being the NetCDF format).

== Proposal ==
HotdoG is a software converter that converts Earth Science data in HDF/HDF-EOS 
format into GeoTIFF format. Doing so easily enables users of remote sensing 
data to interoperate with common GIS tools (like WebGIS, Web Processing, image 
analysis, and geo computational tools). We feel that the project is an 
incremental step, and an appropriate focus with tangible success possibilities 
by restraining our focus to HDF/HDF-EOS to GeoTIFF conversion.

There are numerous interesting paths that we can take the toolkit in -- as 
conversion from remotely sensed data to GeoTIFF involves ensuring that the 
HDF-EOS metadata elements can be appropriately represented using GeoTIFF 
headers, and the associated format. Furthermore, capturing the HDF's 
appropriate geo datum in GeoTIFF will be another important challenge.

== Background ==

GeoTIFF is a data and metadata standard for Earth science applications. It is 
based on binary Tagged Image File Format (TIFF).  A GeoTIFF file has geographic 
(or cartographic) data embedded as tags within the TIFF file that are used to 
geo-locate the image. This is required for correct integration of the image in 
Geographic Information Systems (GIS) and other popular tools like Google Earth 
Pro.

In the recent years, GeoTIFF has gained popularity as a visualization format 
among NASA HDF Earth science user communities according to the NASA data user's 
survey. However, the conversion from HDF to GeoTIFF is not straightforward for 
end users because NASA HDF data products are diverse and organized in many 
different ways. For example, go to http://hdfeos.org/zoo and you'll see many 
scripting language examples because no single script can correctly visualize 
all NASA HDF data.

== Rationale ==

The HEG tool is limited to some NASA HDF-EOS2 products (no support for HDF-EOS5 
products) and it is not an open-source tool. The latest GDAL (version 1.9.2 and 
above) is an open-source tool but it cannot handle many non-HDF-EOS NASA HDF 
products such as TRMM (pure HDF4) and Aquarius (pure HDF5) correctly and 
automatically.

== Initial Goals ==

We'll improve GDAL to support NASA HDF products better by handling geo-location 
information and physical meaning of data correctly and automatically.

We'll handle NASA products intelligently so novice users don't have to supply 
many options or figure out the details about the data products. For advanced 
users, we'll give a full control of accessing HDF products in many different 
ways so that the converted GeoTIFF file is scientifically valid and meaningful.

We aim to provide command line tools first and evolve them into a GUI tool.


== Current Status ==

We're looking for people interested in HotdoG and to move the project into the 
Apache Community.

[VOTE] Accept Apache HotdoG into the Incubator

[Ramirez, Paul M (398J)]

All,

I'd like to call a VOTE for the acceptance of Apache HotdoG into the Incubator. 
I'll leave the VOTE open for the rest of the week and close it out Monday, June 
17th early am PT.

[ ] +1 Accept Apache HotdoG into the Incubator
[ ] +0 Don't care.
[ ] -1 Don't accept Apache HotdoG because...

Full Proposal is pasted at the end of this email. Only VOTEs from Incubator PMC 
members are binding, but all are welcome to express their thoughts.

This is a second pass at this vote as I canceled it to pull in more mentors. 
The following people voted on the first pass:

Henry Saputra +1 (binding)
Chris Mattmann + 1 (binding)

Thanks!
Paul Ramirez

P.S. +1 from me (binding)


= HotdoG Proposal =

== Abstract ==

The HotdoG project is an effort and suite of tools to convert HDF/HDF-EOS 
format into GeoTIFF format. This is the first of a potential series of incoming 
projects originating from The HDF Group -- the non-profit organization is 
interested in evaluating the ASF as a potential home for many of its projects. 
The HDF Group is an independently funded organization that started many years 
ago with major investment from NASA as the Hierarchical Data Format (HDF), 
version 4 and now version 5, is the ''de facto'' remote sensing data format for 
NASA missions, and an increasing number of other disciplines including bio 
medicine, radio astronomy, climate science, and other domains.

HDF is both a data and metadata format, as well as a model for representing and 
access information. There are numerous downstream tools that can read and write 
HDF data, including a growing number of Geospatial data tools (ESRI-based, and 
also OpenGeo and other community led efforts). In addition, major 
interoperability efforts are also occurring between the remote sensing 
community and the climate modeling community (which has traditionally favored 
NetCDF as opposed to HDF) because of the efforts in HDF5 to leverage a common 
data format and model.

HotdoG is poised to be a first of its kind in the form of bringing one of the 
major 2 data formats for science to the ASF (the other being the NetCDF format).

== Proposal ==
HotdoG is a software converter that converts Earth Science data in HDF/HDF-EOS 
format into GeoTIFF format. Doing so easily enables users of remote sensing 
data to interoperate with common GIS tools (like WebGIS, Web Processing, image 
analysis, and geo computational tools). We feel that the project is an 
incremental step, and an appropriate focus with tangible success possibilities 
by restraining our focus to HDF/HDF-EOS to GeoTIFF conversion.

There are numerous interesting paths that we can take the toolkit in -- as 
conversion from remotely sensed data to GeoTIFF involves ensuring that the 
HDF-EOS metadata elements can be appropriately represented using GeoTIFF 
headers, and the associated format. Furthermore, capturing the HDF's 
appropriate geo datum in GeoTIFF will be another important challenge.

== Background ==

GeoTIFF is a data and metadata standard for Earth science applications. It is 
based on binary Tagged Image File Format (TIFF).  A GeoTIFF file has geographic 
(or cartographic) data embedded as tags within the TIFF file that are used to 
geo-locate the image. This is required for correct integration of the image in 
Geographic Information Systems (GIS) and other popular tools like Google Earth 
Pro.

In the recent years, GeoTIFF has gained popularity as a visualization format 
among NASA HDF Earth science user communities according to the NASA data user's 
survey. However, the conversion from HDF to GeoTIFF is not straightforward for 
end users because NASA HDF data products are diverse and organized in many 
different ways. For example, go to http://hdfeos.org/zoo and you'll see many 
scripting language examples because no single script can correctly visualize 
all NASA HDF data.

== Rationale ==

The HEG tool is limited to some NASA HDF-EOS2 products (no support for HDF-EOS5 
products) and it is not an open-source tool. The latest GDAL (version 1.9.2 and 
above) is an open-source tool but it cannot handle many non-HDF-EOS NASA HDF 
products such as TRMM (pure HDF4) and Aquarius (pure HDF5) correctly and 
automatically.

== Initial Goals ==

We'll improve GDAL to support NASA HDF products better by handling geo-location 
information and physical meaning of data correctly and automatically.

We'll handle NASA products intelligently so novice users don't have to supply 
many options or figure out the details about the data products. For advanced 
users, we'll give a full control of accessing HDF products in many different 
ways so that the converted GeoTIFF file is scientifically valid and meaningful.

We aim to provide command line tools first and evolve them into a GUI tool.


== Current Status ==

We're looking for people interested in HotdoG and to move the project into the 
Apache Community.

=== Meritocracy ===
We will discuss the milestone and the future plan in an open forum

Re: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1)

[Alex Karasulu]

No worries on the checksum. Looking good ...

+1 (binding)


On Wed, Jun 12, 2013 at 7:45 PM, Mattmann, Chris A (398J) <
chris.a.mattm...@jpl.nasa.gov> wrote:

> Hey Henry,
>
> Either way I don't think it's doctrine -- I've seen releases and voted on
> them with or without.
> I think it's nice to have a sha or sha1, but not required.
>
> Cheers,
> Chris
>
> ++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattm...@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++
>
>
>
>
>
>
> -Original Message-
> From: Henry Saputra 
> Reply-To: "general@incubator.apache.org" 
> Date: Tuesday, June 11, 2013 12:12 PM
> To: "general@incubator.apache.org" 
> Subject: Re: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1)
>
> >Does an incubator project release requires sha1 checksum too?
> >
> >From: http://www.apache.org/dev/release-signing.html:
> >
> >"An SHA checksum *should* also be created and *must* be suffixed .sha"
> >
> >Looks like it should but not required?
> >
> >- Henry
> >
> >
> >On Mon, Jun 10, 2013 at 5:05 PM, Benjamin Mahler
> >wrote:
> >
> >> Please vote on releasing the following candidate as Apache Mesos
> >> (incubating) version 0.12.0. This will be the fourth incubator release
> >>for
> >> Mesos in Apache.
> >>
> >> The candidate for Mesos 0.12.0-incubating release is available at:
> >>
> >>
> >>http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12
> .
> >>0-incubating.tar.gz
> >>
> >> The tag to be voted on is 0.12.0-rc1:
> >>
> >>
> >>
> https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=57d
> >>7b9719dce662881b162eba10b5765a807d53c
> >>
> >> The MD5 checksum of the tarball can be found at:
> >>
> >>
> >>http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12
> .
> >>0-incubating.tar.gz.md5
> >>
> >> The signature of the tarball can be found at:
> >>
> >>
> >>http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12
> .
> >>0-incubating.tar.gz.asc
> >>
> >> PGP key used to sign the release:
> >> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD0BEBB95D141A5B6
> >>
> >> Please vote on releasing this package as Apache Mesos 0.12.0-incubating!
> >>
> >> The vote is open until Thursday, June 13th at 00:00 UTC and passes if
> >> a majority
> >> of at least 3 +1 IPMC votes are cast.
> >>
> >> [ ] +1 Release this package as Apache Mesos 0.12.0-incubating
> >> [ ] -1 Do not release this package because ...
> >>
> >> To learn more about Apache Mesos, please see
> >> http://incubator.apache.org/mesos.
> >>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Best Regards,
-- Alex

Re: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1)

[Henry Saputra]

Ah ok thanks for the clarification Chris!

- Henry


On Wed, Jun 12, 2013 at 9:45 AM, Mattmann, Chris A (398J) <
chris.a.mattm...@jpl.nasa.gov> wrote:

> Hey Henry,
>
> Either way I don't think it's doctrine -- I've seen releases and voted on
> them with or without.
> I think it's nice to have a sha or sha1, but not required.
>
> Cheers,
> Chris
>
> ++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattm...@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++
>
>
>
>
>
>
> -Original Message-
> From: Henry Saputra 
> Reply-To: "general@incubator.apache.org" 
> Date: Tuesday, June 11, 2013 12:12 PM
> To: "general@incubator.apache.org" 
> Subject: Re: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1)
>
> >Does an incubator project release requires sha1 checksum too?
> >
> >From: http://www.apache.org/dev/release-signing.html:
> >
> >"An SHA checksum *should* also be created and *must* be suffixed .sha"
> >
> >Looks like it should but not required?
> >
> >- Henry
> >
> >
> >On Mon, Jun 10, 2013 at 5:05 PM, Benjamin Mahler
> >wrote:
> >
> >> Please vote on releasing the following candidate as Apache Mesos
> >> (incubating) version 0.12.0. This will be the fourth incubator release
> >>for
> >> Mesos in Apache.
> >>
> >> The candidate for Mesos 0.12.0-incubating release is available at:
> >>
> >>
> >>http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12
> .
> >>0-incubating.tar.gz
> >>
> >> The tag to be voted on is 0.12.0-rc1:
> >>
> >>
> >>
> https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=57d
> >>7b9719dce662881b162eba10b5765a807d53c
> >>
> >> The MD5 checksum of the tarball can be found at:
> >>
> >>
> >>http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12
> .
> >>0-incubating.tar.gz.md5
> >>
> >> The signature of the tarball can be found at:
> >>
> >>
> >>http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12
> .
> >>0-incubating.tar.gz.asc
> >>
> >> PGP key used to sign the release:
> >> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD0BEBB95D141A5B6
> >>
> >> Please vote on releasing this package as Apache Mesos 0.12.0-incubating!
> >>
> >> The vote is open until Thursday, June 13th at 00:00 UTC and passes if
> >> a majority
> >> of at least 3 +1 IPMC votes are cast.
> >>
> >> [ ] +1 Release this package as Apache Mesos 0.12.0-incubating
> >> [ ] -1 Do not release this package because ...
> >>
> >> To learn more about Apache Mesos, please see
> >> http://incubator.apache.org/mesos.
> >>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Error collecting infrastructure for Openmeetings

[Alexei Fedotov]

Sebastian,
I believe as for now, the decision is *not to include* the code into
release. I opposed this initially, yet it seems I have to step down
here. There were no strong support for this from anyone other then me.
--
With best regards / с наилучшими пожеланиями,
Alexei Fedotov / Алексей Федотов,
http://dataved.ru/
+7 916 562 8095


On Wed, Jun 12, 2013 at 3:16 AM, seba.wag...@gmail.com
 wrote:
> *AFAIK,
> many Apache projects do use Google Analytics already.*
> => The next question will be: Which projects do you Google Analytics?
>
> I doubt that any Apache product includes a UA code in its release packages.
>
> Sebastian
>
>
> 2013/6/10 Alexei Fedotov 
>
>> [added general@ for vivid discussion]
>>
>> Hello Sebastian,
>>
>> I'm glad that the statement that this infrastructure is needed is not
>> questioned.
>>
>> We technically can use either CGI script, or existing Confluence API.
>> The intention for using Google Analytics is minimum effort. AFAIK,
>> many Apache projects do use Google Analytics already.
>>
>> The goal for the request is to avoid inventing a project-wide policy
>> where foundation-wide policy is needed.
>>
>> With best regards, Alexei
>>
>> --
>> With best regards / с наилучшими пожеланиями,
>> Alexei Fedotov / Алексей Федотов,
>> http://dataved.ru/
>> +7 916 562 8095
>>
>>
>> On Mon, Jun 10, 2013 at 7:03 AM, seba.wag...@gmail.com
>>  wrote:
>> > Hi Alexei,
>> >
>> > what about a simple CGI script that takes the input and send an email to
>> the
>> > mailing list?
>> > I think some more simple approach would do the same and does not have
>> such a
>> > deep impact on the whole infrastructure. Some legal and privacy aspects
>> are
>> > still tbc.
>> >
>> > However no matter what we do it is unlikely that including the actual UA
>> > code or any kind of real pwd / hash in a release is a good idea. It is
>> quite
>> > easy to manipulate that.
>> >
>> > Also the question rises if the OpenMeetings server is in a public
>> network at
>> > all. Just sending request blindly without knowing if they ever reach
>> their
>> > destination is kind of odd.
>> >
>> > It should be some subscribe mechanism where an OpenMeetings admin can
>> > activate the error collecting. The activation could then subscribe and
>> load
>> > a hash that will auth that server for error collecting.
>> >
>> > If you put that activation in the installer with appropriate
>> explenations I
>> > think it has better chances to find a wider positive reaction in devs and
>> > users.
>> >
>> > Maybe it would be enough to give some kind of more general feedback from
>> > @legal and @infra and we can then in the OpenMeetings PMC create a more
>> > detailed spec of that component.
>> >
>> > @legal: Do you have general constraints regarding error collecting ?
>> >
>> > @infra: What kind of advices can you give us? I guess some CGI scripts
>> are
>> > not that big deal. Is there any process who would review and activate /
>> make
>> > them executable?
>> >
>> > Thanks,
>> > Sebastian
>> >
>> > Am 06.06.2013 19:38 schrieb "Alexei Fedotov" :
>> >
>> >> [added Shane for reputation issues]
>> >>
>> >> Hello, Infra and Legal folks,
>> >>
>> >> We ask you for advice on the automated error collection
>> >> infrastructure. Any helpful ideas are appreciated.
>> >>
>> >> 1. Our users are tainted with iphones and other reliable and fancy
>> >> staff. They start wanting openmeetings to work reliably. This makes us
>> >> think of a global error collecting infrastructure to plan important
>> >> bug fixes. Here is an example by Firefox [1].
>> >>
>> >> We believe collecting user errors is generally ok if proper
>> >> preparations are made. Is it generally possible to implement error
>> >> collecting infrastructure as a part of Apache project? If not, we can
>> >> try to do it as a commercial company, yet Firefox example shows a
>> >> non-commercial org can be behind that error collection.
>> >>
>> >> 2. Could we use Google Analytics to store collected errors? The
>> >> general Apache practice is to use Apache infrastructure. Google
>> >> Analytics allows us storing 50 mln. events for free. The comparable
>> >> thing won't be free for Apache for sure.
>> >>
>> >> Once can use JIRA, or Confluence via API, this will be a heavy load.
>> >> Are you ok with using third party for storing error & environment
>> >> messages and associated risks?
>> >>
>> >> The code we are talking about is below:
>> >>try {
>> >>_gaq = _gaq || [];
>> >>_gaq.push(['_setAccount', 'UA-13024987-1']); // PMC id
>> >>_gaq.push(['_trackPageview']);
>> >>_gaq.push(['_trackEvent', 'Openmeetings client error',
>> >> message, '', 0, true]);
>> >>} catch (exception) {
>> >>alert(exception);
>> >>}
>> >>
>> >> 3. Is it ok for PMC to share Google Analytics id? Should we use some
>> >> Apache Id instead?
>> >>
>> >> 4. Which preparations should be done to start this error collection
>>

Re: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1)

[Mattmann, Chris A (398J)]

Hey Henry,

Either way I don't think it's doctrine -- I've seen releases and voted on
them with or without.
I think it's nice to have a sha or sha1, but not required.

Cheers,
Chris

++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattm...@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++






-Original Message-
From: Henry Saputra 
Reply-To: "general@incubator.apache.org" 
Date: Tuesday, June 11, 2013 12:12 PM
To: "general@incubator.apache.org" 
Subject: Re: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1)

>Does an incubator project release requires sha1 checksum too?
>
>From: http://www.apache.org/dev/release-signing.html:
>
>"An SHA checksum *should* also be created and *must* be suffixed .sha"
>
>Looks like it should but not required?
>
>- Henry
>
>
>On Mon, Jun 10, 2013 at 5:05 PM, Benjamin Mahler
>wrote:
>
>> Please vote on releasing the following candidate as Apache Mesos
>> (incubating) version 0.12.0. This will be the fourth incubator release
>>for
>> Mesos in Apache.
>>
>> The candidate for Mesos 0.12.0-incubating release is available at:
>>
>> 
>>http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.
>>0-incubating.tar.gz
>>
>> The tag to be voted on is 0.12.0-rc1:
>>
>> 
>>https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=57d
>>7b9719dce662881b162eba10b5765a807d53c
>>
>> The MD5 checksum of the tarball can be found at:
>>
>> 
>>http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.
>>0-incubating.tar.gz.md5
>>
>> The signature of the tarball can be found at:
>>
>> 
>>http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.
>>0-incubating.tar.gz.asc
>>
>> PGP key used to sign the release:
>> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD0BEBB95D141A5B6
>>
>> Please vote on releasing this package as Apache Mesos 0.12.0-incubating!
>>
>> The vote is open until Thursday, June 13th at 00:00 UTC and passes if
>> a majority
>> of at least 3 +1 IPMC votes are cast.
>>
>> [ ] +1 Release this package as Apache Mesos 0.12.0-incubating
>> [ ] -1 Do not release this package because ...
>>
>> To learn more about Apache Mesos, please see
>> http://incubator.apache.org/mesos.
>>


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

Re: Apache HotdoG interest?

[Adam Estrada]

+1 this sounds great! If I get an ACK, I will add myself to the project
wiki ASAP!

Thanks in advance,
Adam.


On Wed, Jun 5, 2013 at 10:51 AM, Mattmann, Chris A (398J) <
chris.a.mattm...@jpl.nasa.gov> wrote:

> Hey Adam,
>
> I noticed you were interested in Apache HotdoG -- would you like
> to join the project as an initial committer and PPMC member? I know
> you are interested in being a mentor; which requires you to be a
> member of the IPMC which at present you are not.
>
> That being said there is nothing stopping you from doing "mentor"-ish
> roles and tasks. Meaning, you can still help out with IPMC HotdoG
> reporting (should the project be accepted into the Incubator after
> our restarted VOTE and after we get a 3rd mentor from the IPMC to
> sign up ;) ); with the community for HotdoG and bringing new contributors
> to it; and of course with the code!
>
> Demonstration of these types of qualities is precisely the types of
> things we look for in a mentor and an IPMC member and there is nothing
> stopping you from doing that to help out HotdoG. Suggestion:
>
> (if the rest of the Hotdog community members have no objection;
> which are present during discussion they have not)
>
> 1. Adam adds himself as PPMC member and committer to:
> http://wiki.apache.org/incubator/HotdoGProposal
>
>
> 2. Should HotdoG be accepted as Apache Incubator project; Adam
> does mentor roles and participates that way.
>
> Adam that sound good?
>
> Thanks for your interest!
>
> Cheers,
> Chris
>
>
> ++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattm...@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++
>
>
>
>
>

Re: [VOTE] Apache Spark for the Incubator

[Matei Zaharia]

+1 (non-binding)

Matei

On Jun 8, 2013, at 12:25 AM, Hitesh Shah  wrote:

> +1 (non-binding)
> 
> -- Hitesh
> 
> On Jun 7, 2013, at 10:34 PM, Mattmann, Chris A (398J) wrote:
> 
>> Hi Folks,
>> 
>> OK discussion has died down, time to VOTE to accept Spark into the
>> Apache Incubator. I'll let the VOTE run for at least a week.
>> 
>> So far I've heard +1s from the following folks, so no need for them
>> to VOTE again unless they want to change their VOTE:
>> 
>> +1
>> 
>> Chris Mattmann*
>> Konstantin Boudnik
>> Henry Saputra*
>> Reynold Xin
>> Pei Chen
>> Roman Shaposhnik*
>> Suresh Marru*
>> 
>> * -indicates IPMC
>> 
>> [ ] +1 Accept Spark into the Apache Incubator.
>> [ ] +0 Don't care.
>> [ ] -1 Don't accept Spark into the Apache Incubator because..
>> 
>> Proposal text is below.
>> 
>> === Abstract ===
>> Spark is an open source system for large-scale data analysis on clusters.
>> 
>> === Proposal ===
>> Spark is an open source system for fast and flexible large-scale data
>> analysis. Spark provides a general purpose runtime that supports
>> low-latency execution in several forms. These include interactive
>> exploration of very large datasets, near real-time stream processing, and
>> ad-hoc SQL analytics (through higher layer extensions). Spark interfaces
>> with HDFS, HBase, Cassandra and several other storage storage layers, and
>> exposes APIs in Scala, Java and Python.
>> Background
>> Spark started as U.C. Berkeley research project, designed to efficiently
>> run machine learning algorithms on large datasets. Over time, it has
>> evolved into a general computing engine as outlined above. Spark¹s
>> developer community has also grown to include additional institutions,
>> such as universities, research labs, and corporations. Funding has been
>> provided by various institutions including the U.S. National Science
>> Foundation, DARPA, and a number of industry sponsors. See:
>> https://amplab.cs.berkeley.edu/sponsors/ for full details.
>> 
>> === Rationale ===
>> As the number of contributors to Spark has grown, we have sought for a
>> long-term home for the project, and we believe the Apache foundation would
>> be a great fit. Spark is a natural fit for the Apache foundation: Spark
>> already interoperates with several existing Apache projects (HDFS, HBase,
>> Hive, Cassandra, Avro and Flume to name a few). The Spark team is familiar
>> with the Apache process and and subscribes to the Apache mission - the
>> team includes multiple Apache committers already. Finally, joining Apache
>> will help coordinate the development effort of the growing number of
>> organizations which contribute to Spark.
>> 
>> == Initial Goals ==
>> The initial goals will most likely be to move the existing codebase to
>> Apache and integrate with the Apache development process. Furthermore, we
>> plan for incremental development, and releases along with the Apache
>> guidelines.
>> 
>> === Current Status ===
>> == Meritocracy ==
>> The Spark project already operates on meritocratic principles. Today,
>> Spark has several developers and has accepted multiple major patches from
>> outside of U.C. Berkeley. While this process has remained mostly informal
>> (we do not have an official committer list), an implicit organization
>> exists in which individuals who contribute major components act as
>> maintainers for those modules. If accepted, the Spark project would
>> include several of these participants as committers from the onset. We
>> will work to identify all committers and PPMC members for the project and
>> to operate under the ASF meritocratic principles.
>> 
>> === Community ===
>> Acceptance into the Apache foundation would bolster the already strong
>> user and developer community around Spark. That community includes dozens
>> of contributors from several institutions, a meetup group with several
>> hundred members, and an active mailing list composed of hundreds of users.
>> Core Developers
>> The core developers of our project are listed in our contributors and
>> initial PPMC below. Though many exist at UC Berkeley, there is a
>> representative cross sampling of other organizations including Quantifind,
>> Microsoft, Yahoo!, ClearStory Data, Bizo, Intel, Tagged and Webtrends.
>> 
>> 
>> === Alignment ===
>> Our proposed effort aligns with several ongoing BIGDATA and U.S. National
>> priority funding interests including the NSF and its Expeditions program,
>> and the DARPA XDATA project. Our industry partners and collaborators are
>> well aligned with our code base.
>> 
>> There are also a number of related Apache projects and dependencies, that
>> will be mentioned in the Relationships with Other Apache products section.
>> 
>> == Known Risks ==
>> 
>> === Orphaned Products ===
>> Given the current level of investment in Spark - the risk of the project
>> being abandoned is minimal. There are several constituents who are highly
>> incentivized to continue development. The U.C. Berkeley AMPLab relies on
>> 

Re: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1)

[Vinod Kone]

+1 (non-binding)


On Mon, Jun 10, 2013 at 6:50 PM, Benjamin Mahler
wrote:

> Correction on the tag link:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=5332ade3c403b4d9fcdcd9194ee86d3fa99eca17
>
>
> On Mon, Jun 10, 2013 at 5:05 PM, Benjamin Mahler
> wrote:
>
> > Please vote on releasing the following candidate as Apache Mesos
> > (incubating) version 0.12.0. This will be the fourth incubator release
> > for Mesos in Apache.
> >
> > The candidate for Mesos 0.12.0-incubating release is available at:
> >
> >
> http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0-incubating.tar.gz
> >
> > The tag to be voted on is 0.12.0-rc1:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=57d7b9719dce662881b162eba10b5765a807d53c
> >
> > The MD5 checksum of the tarball can be found at:
> >
> >
> http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0-incubating.tar.gz.md5
> >
> > The signature of the tarball can be found at:
> >
> >
> http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0-incubating.tar.gz.asc
> >
> > PGP key used to sign the release:
> > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD0BEBB95D141A5B6
> >
> > Please vote on releasing this package as Apache Mesos 0.12.0-incubating!
> >
> > The vote is open until Thursday, June 13th at 00:00 UTC and passes if a
> majority
> > of at least 3 +1 IPMC votes are cast.
> >
> > [ ] +1 Release this package as Apache Mesos 0.12.0-incubating
> > [ ] -1 Do not release this package because ...
> >
> > To learn more about Apache Mesos, please see
> > http://incubator.apache.org/mesos.
> >
>

Re: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1)

[Yan Xu]

+1 (non-binding)

--
Jiang Yan Xu  @xujyan 


On Tue, Jun 11, 2013 at 10:16 AM, Vinod Kone  wrote:

> +1 (non-binding)
>
>
> On Mon, Jun 10, 2013 at 6:50 PM, Benjamin Mahler
> wrote:
>
> > Correction on the tag link:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=5332ade3c403b4d9fcdcd9194ee86d3fa99eca17
> >
> >
> > On Mon, Jun 10, 2013 at 5:05 PM, Benjamin Mahler
> > wrote:
> >
> > > Please vote on releasing the following candidate as Apache Mesos
> > > (incubating) version 0.12.0. This will be the fourth incubator release
> > > for Mesos in Apache.
> > >
> > > The candidate for Mesos 0.12.0-incubating release is available at:
> > >
> > >
> >
> http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0-incubating.tar.gz
> > >
> > > The tag to be voted on is 0.12.0-rc1:
> > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=57d7b9719dce662881b162eba10b5765a807d53c
> > >
> > > The MD5 checksum of the tarball can be found at:
> > >
> > >
> >
> http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0-incubating.tar.gz.md5
> > >
> > > The signature of the tarball can be found at:
> > >
> > >
> >
> http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0-incubating.tar.gz.asc
> > >
> > > PGP key used to sign the release:
> > > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD0BEBB95D141A5B6
> > >
> > > Please vote on releasing this package as Apache Mesos
> 0.12.0-incubating!
> > >
> > > The vote is open until Thursday, June 13th at 00:00 UTC and passes if a
> > majority
> > > of at least 3 +1 IPMC votes are cast.
> > >
> > > [ ] +1 Release this package as Apache Mesos 0.12.0-incubating
> > > [ ] -1 Do not release this package because ...
> > >
> > > To learn more about Apache Mesos, please see
> > > http://incubator.apache.org/mesos.
> > >
> >
>