The Apache Software Foundation
The Apache Software Foundation Incubator

Codebase IP Clearance TEMPLATE

CloudStack GCE API Interface Codebase Intellectual Property (IP) Clearance Status


gstack is an API wrapper that maps the Google Cloud Platform compute engine (GCE) API to the CloudStack API. It consist in a Python Flask application that implements a web server that serves a GCE compatible API. The API calls are mapped to the CloudStack API. It serves as an API proxy and translater to allow users of Google GCE to use the GCE client to issue API calls to a CloudStack public or private cloud. The code contains the server and API routes, as well as unit tests.

Project info

  • Which PMC will be responsible for the code: CloudStack PMC
  • Into which existing project/module: Apache CloudStack
  • Officer or member managing donation: Sebastien Goasguen

Completed tasks are shown by the completion date (YYYY-MM-dd).

Identify the codebase

date item
2015-04-27 If applicable, make sure that any associated name does not already exist and is not already trademarked for an existing software product. We will need to change the name as it already exists
2015-04-27 1.1.2 tag at

MD5 or SHA1 sum for donated software: (Note versioned software used to calculate sum in parentheses).

date item
2014-04-18 Check and make sure that the papers that transfer rights to the ASF been received. It is only necessary to transfer rights for the package, the core code, and any new code produced by the project.
2015-04-15 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright.

Identify name recorded for software grant: the name of the grant as record in the grants.txt document so that the grant can be easily identified

Verify distribution rights

Corporations and individuals holding existing distribution rights:

  • Sebastien Goasguen
  • Ian Duffy
  • Darren Brogan
date item
2015-04-13 Check that all active committers have a signed CLA on record.
N/A Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is required to authorize their contributions under their individual CLA.
2015-04-15 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute.
2015-04-13 Check and make sure that all items depended upon by the project is covered by one or more of the following approved licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms.

Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License.

Organizational acceptance of responsibility for the project

Related VOTEs:

  • The VOTE thread accepting the donation can be found on or: