[VOTE] Usergrid BaaS Stack for Apache Incubator (revised proposal)

[Dave]

I would like to call for a new vote on Usergrid, a multi-tenant
Backend-as-a-Service stack for web & mobile applications based on RESTful
APIs, as an Apache Incubator podling.

The original proposal has been revised to name Dave Johnson as the Champion
and to bring Jim Jagielski back in as a Mentor and to add John Lewis
Mcgibbney as a Mentor. I also add some text to the Initial Committers
section and a new Interested Contributors section to list those who have
expressed interest in contributing.

Here is a link to the revised proposal:
   https://wiki.apache.org/incubator/UsergridProposal

It is also pasted below:


= Usergrid Proposal =

== Abstract ==

Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile
applications, based on RESTful APIs.


== Proposal ==

Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”)
composed of an integrated distributed NoSQL database, application layer and
client tier with SDKs for developers looking to rapidly build web and/or
mobile applications. It provides elementary services (user registration &
management, data storage, file storage, queues) and retrieval features
(full text search, geolocation search, joins) to power common app features.

It is a multi-tenant system designed for deployment to public cloud
environments (such as Amazon Web Services, Rackspace, etc.) or to run on
traditional server infrastructures so that anyone can run their own private
BaaS deployment.

For architects and back-end teams, it aims to provide a distributed, easily
extendable, operationally predictable and highly scalable solution.
For front-end developers, it aims to simplify the development process by
enabling them to rapidly build and operate mobile and web applications
without requiring backend expertise.


== Background ==

Developing web or mobile applications obviously necessitates writing and
maintaining more than just front-end code. Even simple applications can
implicitly rely on server code being run to store users, perform database
queries, serve images and video files, etc. Developing and maintaining such
backend services requires skills not always available or expected of app
development teams. Beyond that, the proliferation of apps inside of
companies leads to the creation of many different, ad-hoc, unequally
maintained backend solutions created by employees and contractors alike and
hosted on a wide variety of environments. This is causing poor resource
usage, operational issues, as well as security, privacy & compliance
concerns.

In response to this problem, companies have long tried to standardize their
server-side stack or unify them behind an ESB or API strategy.
Backends-as-a-Service follow a similar approach but their unique
characteristic is strongly tying  1) a persistence tier (typically a
database), 2) a server-side application tier delivering a set of common
services and 3) a set of client-side application interface mechanisms. For
example, a BaaS could package 1) MongoDB with 2) a node.js application that
offers access through 3) WebSockets. In the case of Usergrid, the trifecta
is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API.

The Backend-as-a-Service approach has steadily gained popularity in the
last few years with cloud providers such Parse.com, Stackmob.com and
Kinvey.com, each operating tens of thousands of apps for tens of thousands
of developers. The trend has already reached large organizations as well,
with global companies such as Korea Telecom internally building a
privately-run BaaS platform. But so far, there have been limited options
for developers that want a non-proprietary, open option for hosting and
providing these services themselves, or for enterprise and government users
who want to provide these capabilities from their own data centers,
especially on a very large scale.


== Rationale ==

The issue this proposal deals with is implicit in the name.
Backend-as-a-Service platforms are usually offered solely as proprietary
cloud services. They are typically closed sourced, hosted on public clouds,
and require subscription payment. Usergrid opens the playing field, by
making a fully-featured BaaS platform freely available to all. This
includes developers that previously could not afford them, such as mobile
enthusiasts, small boutiques, and cost-sensitive startups. This also
includes large companies that benefit from a reference implementation they
can deploy in trust, or extend to their needs without losing time writing
less-vetted, less-performant boilerplate functionality.

Usergrid has been open source since 2011 and has grown as an independent
project, garnering 11 primary committers, 35 total contributors, 260+
participants on its mailing list, with 3,700+ commits, 200+ external
contributions, 350+ stars and 100+ forks on Github, not to mention several
large scale production deployments at major global companies in the media,
retail, telecommunication and government spaces.

The Apache Software Fou

Re: [VOTE] Usergrid BaaS Stack for Apache Incubator (revised proposal)

[Henry Saputra]

+1 (binding)

Good luck guys

- Henry

On Mon, Sep 30, 2013 at 12:27 PM, Dave  wrote:
> I would like to call for a new vote on Usergrid, a multi-tenant
> Backend-as-a-Service stack for web & mobile applications based on RESTful
> APIs, as an Apache Incubator podling.
>
> The original proposal has been revised to name Dave Johnson as the Champion
> and to bring Jim Jagielski back in as a Mentor and to add John Lewis
> Mcgibbney as a Mentor. I also add some text to the Initial Committers
> section and a new Interested Contributors section to list those who have
> expressed interest in contributing.
>
> Here is a link to the revised proposal:
>https://wiki.apache.org/incubator/UsergridProposal
>
> It is also pasted below:
>
>
> = Usergrid Proposal =
>
> == Abstract ==
>
> Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile
> applications, based on RESTful APIs.
>
>
> == Proposal ==
>
> Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”)
> composed of an integrated distributed NoSQL database, application layer and
> client tier with SDKs for developers looking to rapidly build web and/or
> mobile applications. It provides elementary services (user registration &
> management, data storage, file storage, queues) and retrieval features
> (full text search, geolocation search, joins) to power common app features.
>
> It is a multi-tenant system designed for deployment to public cloud
> environments (such as Amazon Web Services, Rackspace, etc.) or to run on
> traditional server infrastructures so that anyone can run their own private
> BaaS deployment.
>
> For architects and back-end teams, it aims to provide a distributed, easily
> extendable, operationally predictable and highly scalable solution.
> For front-end developers, it aims to simplify the development process by
> enabling them to rapidly build and operate mobile and web applications
> without requiring backend expertise.
>
>
> == Background ==
>
> Developing web or mobile applications obviously necessitates writing and
> maintaining more than just front-end code. Even simple applications can
> implicitly rely on server code being run to store users, perform database
> queries, serve images and video files, etc. Developing and maintaining such
> backend services requires skills not always available or expected of app
> development teams. Beyond that, the proliferation of apps inside of
> companies leads to the creation of many different, ad-hoc, unequally
> maintained backend solutions created by employees and contractors alike and
> hosted on a wide variety of environments. This is causing poor resource
> usage, operational issues, as well as security, privacy & compliance
> concerns.
>
> In response to this problem, companies have long tried to standardize their
> server-side stack or unify them behind an ESB or API strategy.
> Backends-as-a-Service follow a similar approach but their unique
> characteristic is strongly tying  1) a persistence tier (typically a
> database), 2) a server-side application tier delivering a set of common
> services and 3) a set of client-side application interface mechanisms. For
> example, a BaaS could package 1) MongoDB with 2) a node.js application that
> offers access through 3) WebSockets. In the case of Usergrid, the trifecta
> is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API.
>
> The Backend-as-a-Service approach has steadily gained popularity in the
> last few years with cloud providers such Parse.com, Stackmob.com and
> Kinvey.com, each operating tens of thousands of apps for tens of thousands
> of developers. The trend has already reached large organizations as well,
> with global companies such as Korea Telecom internally building a
> privately-run BaaS platform. But so far, there have been limited options
> for developers that want a non-proprietary, open option for hosting and
> providing these services themselves, or for enterprise and government users
> who want to provide these capabilities from their own data centers,
> especially on a very large scale.
>
>
> == Rationale ==
>
> The issue this proposal deals with is implicit in the name.
> Backend-as-a-Service platforms are usually offered solely as proprietary
> cloud services. They are typically closed sourced, hosted on public clouds,
> and require subscription payment. Usergrid opens the playing field, by
> making a fully-featured BaaS platform freely available to all. This
> includes developers that previously could not afford them, such as mobile
> enthusiasts, small boutiques, and cost-sensitive startups. This also
> includes large companies that benefit from a reference implementation they
> can deploy in trust, or extend to their needs without losing time writing
> less-vetted, less-performant boilerplate functionality.
>
> Usergrid has been open source since 2011 and has grown as an independent
> project, garnering 11 primary committers, 35 total contributors, 260+
> participants on its mailing list,

Re: [VOTE] Usergrid BaaS Stack for Apache Incubator (revised proposal)

[Marvin Humphrey]

On Mon, Sep 30, 2013 at 12:27 PM, Dave  wrote:
> I would like to call for a new vote on Usergrid, a multi-tenant
> Backend-as-a-Service stack for web & mobile applications based on RESTful
> APIs, as an Apache Incubator podling.

+1 (binding)

Good luck!

Marvin Humphrey

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

Re: [VOTE] Usergrid BaaS Stack for Apache Incubator (revised proposal)

[Afkham Azeez]

+1 (binding)

Azeez


On Tue, Oct 1, 2013 at 12:57 AM, Dave  wrote:

> I would like to call for a new vote on Usergrid, a multi-tenant
> Backend-as-a-Service stack for web & mobile applications based on RESTful
> APIs, as an Apache Incubator podling.
>
> The original proposal has been revised to name Dave Johnson as the Champion
> and to bring Jim Jagielski back in as a Mentor and to add John Lewis
> Mcgibbney as a Mentor. I also add some text to the Initial Committers
> section and a new Interested Contributors section to list those who have
> expressed interest in contributing.
>
> Here is a link to the revised proposal:
>https://wiki.apache.org/incubator/UsergridProposal
>
> It is also pasted below:
>
>
> = Usergrid Proposal =
>
> == Abstract ==
>
> Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile
> applications, based on RESTful APIs.
>
>
> == Proposal ==
>
> Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”)
> composed of an integrated distributed NoSQL database, application layer and
> client tier with SDKs for developers looking to rapidly build web and/or
> mobile applications. It provides elementary services (user registration &
> management, data storage, file storage, queues) and retrieval features
> (full text search, geolocation search, joins) to power common app features.
>
> It is a multi-tenant system designed for deployment to public cloud
> environments (such as Amazon Web Services, Rackspace, etc.) or to run on
> traditional server infrastructures so that anyone can run their own private
> BaaS deployment.
>
> For architects and back-end teams, it aims to provide a distributed, easily
> extendable, operationally predictable and highly scalable solution.
> For front-end developers, it aims to simplify the development process by
> enabling them to rapidly build and operate mobile and web applications
> without requiring backend expertise.
>
>
> == Background ==
>
> Developing web or mobile applications obviously necessitates writing and
> maintaining more than just front-end code. Even simple applications can
> implicitly rely on server code being run to store users, perform database
> queries, serve images and video files, etc. Developing and maintaining such
> backend services requires skills not always available or expected of app
> development teams. Beyond that, the proliferation of apps inside of
> companies leads to the creation of many different, ad-hoc, unequally
> maintained backend solutions created by employees and contractors alike and
> hosted on a wide variety of environments. This is causing poor resource
> usage, operational issues, as well as security, privacy & compliance
> concerns.
>
> In response to this problem, companies have long tried to standardize their
> server-side stack or unify them behind an ESB or API strategy.
> Backends-as-a-Service follow a similar approach but their unique
> characteristic is strongly tying  1) a persistence tier (typically a
> database), 2) a server-side application tier delivering a set of common
> services and 3) a set of client-side application interface mechanisms. For
> example, a BaaS could package 1) MongoDB with 2) a node.js application that
> offers access through 3) WebSockets. In the case of Usergrid, the trifecta
> is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API.
>
> The Backend-as-a-Service approach has steadily gained popularity in the
> last few years with cloud providers such Parse.com, Stackmob.com and
> Kinvey.com, each operating tens of thousands of apps for tens of thousands
> of developers. The trend has already reached large organizations as well,
> with global companies such as Korea Telecom internally building a
> privately-run BaaS platform. But so far, there have been limited options
> for developers that want a non-proprietary, open option for hosting and
> providing these services themselves, or for enterprise and government users
> who want to provide these capabilities from their own data centers,
> especially on a very large scale.
>
>
> == Rationale ==
>
> The issue this proposal deals with is implicit in the name.
> Backend-as-a-Service platforms are usually offered solely as proprietary
> cloud services. They are typically closed sourced, hosted on public clouds,
> and require subscription payment. Usergrid opens the playing field, by
> making a fully-featured BaaS platform freely available to all. This
> includes developers that previously could not afford them, such as mobile
> enthusiasts, small boutiques, and cost-sensitive startups. This also
> includes large companies that benefit from a reference implementation they
> can deploy in trust, or extend to their needs without losing time writing
> less-vetted, less-performant boilerplate functionality.
>
> Usergrid has been open source since 2011 and has grown as an independent
> project, garnering 11 primary committers, 35 total contributors, 260+
> participants on its mailing list, with 3,700+ comm

Re: [VOTE] Usergrid BaaS Stack for Apache Incubator (revised proposal)

[Bertrand Delacretaz]

+1

Bertrand

Re: [VOTE] Usergrid BaaS Stack for Apache Incubator (revised proposal)

[Chip Childers]

On Mon, Sep 30, 2013 at 03:27:24PM -0400, Dave wrote:
> I would like to call for a new vote on Usergrid, a multi-tenant
> Backend-as-a-Service stack for web & mobile applications based on RESTful
> APIs, as an Apache Incubator podling.

+1 (binding)

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

Re: [VOTE] Usergrid BaaS Stack for Apache Incubator (revised proposal)

[Lieven Govaerts]

On Mon, Sep 30, 2013 at 9:27 PM, Dave  wrote:
> I would like to call for a new vote on Usergrid, a multi-tenant
> Backend-as-a-Service stack for web & mobile applications based on RESTful
> APIs, as an Apache Incubator podling.
>
+1 (non-binding)

I hope to be able to contribute to this project during incubation.

Lieven

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

Re: [VOTE] Usergrid BaaS Stack for Apache Incubator (revised proposal)

[Jim Jagielski]

+1 (binding)

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

Re: [VOTE] Usergrid BaaS Stack for Apache Incubator (revised proposal)

[Alan D. Cabrera]

+1 binding

Regards,
Alan


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

Re: [VOTE] Usergrid BaaS Stack for Apache Incubator (revised proposal)

[larry mccay]

+1 (non-binding)


On Tue, Oct 1, 2013 at 1:09 AM, Lieven Govaerts
wrote:

> On Mon, Sep 30, 2013 at 9:27 PM, Dave  wrote:
> > I would like to call for a new vote on Usergrid, a multi-tenant
> > Backend-as-a-Service stack for web & mobile applications based on RESTful
> > APIs, as an Apache Incubator podling.
> >
> +1 (non-binding)
>
> I hope to be able to contribute to this project during incubation.
>
> Lieven
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Usergrid BaaS Stack for Apache Incubator (revised proposal)

[Raminder Singh]

+1 (non-binding). 

Thanks
Raminder

On Sep 30, 2013, at 3:27 PM, Dave  wrote:

> I would like to call for a new vote on Usergrid, a multi-tenant
> Backend-as-a-Service stack for web & mobile applications based on RESTful
> APIs, as an Apache Incubator podling.
> 
> The original proposal has been revised to name Dave Johnson as the Champion
> and to bring Jim Jagielski back in as a Mentor and to add John Lewis
> Mcgibbney as a Mentor. I also add some text to the Initial Committers
> section and a new Interested Contributors section to list those who have
> expressed interest in contributing.
> 
> Here is a link to the revised proposal:
>   https://wiki.apache.org/incubator/UsergridProposal
> 
> It is also pasted below:
> 
> 
> = Usergrid Proposal =
> 
> == Abstract ==
> 
> Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile
> applications, based on RESTful APIs.
> 
> 
> == Proposal ==
> 
> Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”)
> composed of an integrated distributed NoSQL database, application layer and
> client tier with SDKs for developers looking to rapidly build web and/or
> mobile applications. It provides elementary services (user registration &
> management, data storage, file storage, queues) and retrieval features
> (full text search, geolocation search, joins) to power common app features.
> 
> It is a multi-tenant system designed for deployment to public cloud
> environments (such as Amazon Web Services, Rackspace, etc.) or to run on
> traditional server infrastructures so that anyone can run their own private
> BaaS deployment.
> 
> For architects and back-end teams, it aims to provide a distributed, easily
> extendable, operationally predictable and highly scalable solution.
> For front-end developers, it aims to simplify the development process by
> enabling them to rapidly build and operate mobile and web applications
> without requiring backend expertise.
> 
> 
> == Background ==
> 
> Developing web or mobile applications obviously necessitates writing and
> maintaining more than just front-end code. Even simple applications can
> implicitly rely on server code being run to store users, perform database
> queries, serve images and video files, etc. Developing and maintaining such
> backend services requires skills not always available or expected of app
> development teams. Beyond that, the proliferation of apps inside of
> companies leads to the creation of many different, ad-hoc, unequally
> maintained backend solutions created by employees and contractors alike and
> hosted on a wide variety of environments. This is causing poor resource
> usage, operational issues, as well as security, privacy & compliance
> concerns.
> 
> In response to this problem, companies have long tried to standardize their
> server-side stack or unify them behind an ESB or API strategy.
> Backends-as-a-Service follow a similar approach but their unique
> characteristic is strongly tying  1) a persistence tier (typically a
> database), 2) a server-side application tier delivering a set of common
> services and 3) a set of client-side application interface mechanisms. For
> example, a BaaS could package 1) MongoDB with 2) a node.js application that
> offers access through 3) WebSockets. In the case of Usergrid, the trifecta
> is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API.
> 
> The Backend-as-a-Service approach has steadily gained popularity in the
> last few years with cloud providers such Parse.com, Stackmob.com and
> Kinvey.com, each operating tens of thousands of apps for tens of thousands
> of developers. The trend has already reached large organizations as well,
> with global companies such as Korea Telecom internally building a
> privately-run BaaS platform. But so far, there have been limited options
> for developers that want a non-proprietary, open option for hosting and
> providing these services themselves, or for enterprise and government users
> who want to provide these capabilities from their own data centers,
> especially on a very large scale.
> 
> 
> == Rationale ==
> 
> The issue this proposal deals with is implicit in the name.
> Backend-as-a-Service platforms are usually offered solely as proprietary
> cloud services. They are typically closed sourced, hosted on public clouds,
> and require subscription payment. Usergrid opens the playing field, by
> making a fully-featured BaaS platform freely available to all. This
> includes developers that previously could not afford them, such as mobile
> enthusiasts, small boutiques, and cost-sensitive startups. This also
> includes large companies that benefit from a reference implementation they
> can deploy in trust, or extend to their needs without losing time writing
> less-vetted, less-performant boilerplate functionality.
> 
> Usergrid has been open source since 2011 and has grown as an independent
> project, garnering 11 primary committers, 35 total contributors, 260+
> participants on its

Re: [VOTE] Usergrid BaaS Stack for Apache Incubator (revised proposal)

[Alex Karasulu]

+1 (binding)


On Tue, Oct 1, 2013 at 6:03 PM, Raminder Singh  wrote:

> +1 (non-binding).
>
> Thanks
> Raminder
>
> On Sep 30, 2013, at 3:27 PM, Dave  wrote:
>
> > I would like to call for a new vote on Usergrid, a multi-tenant
> > Backend-as-a-Service stack for web & mobile applications based on RESTful
> > APIs, as an Apache Incubator podling.
> >
> > The original proposal has been revised to name Dave Johnson as the
> Champion
> > and to bring Jim Jagielski back in as a Mentor and to add John Lewis
> > Mcgibbney as a Mentor. I also add some text to the Initial Committers
> > section and a new Interested Contributors section to list those who have
> > expressed interest in contributing.
> >
> > Here is a link to the revised proposal:
> >   https://wiki.apache.org/incubator/UsergridProposal
> >
> > It is also pasted below:
> >
> >
> > = Usergrid Proposal =
> >
> > == Abstract ==
> >
> > Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile
> > applications, based on RESTful APIs.
> >
> >
> > == Proposal ==
> >
> > Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”)
> > composed of an integrated distributed NoSQL database, application layer
> and
> > client tier with SDKs for developers looking to rapidly build web and/or
> > mobile applications. It provides elementary services (user registration &
> > management, data storage, file storage, queues) and retrieval features
> > (full text search, geolocation search, joins) to power common app
> features.
> >
> > It is a multi-tenant system designed for deployment to public cloud
> > environments (such as Amazon Web Services, Rackspace, etc.) or to run on
> > traditional server infrastructures so that anyone can run their own
> private
> > BaaS deployment.
> >
> > For architects and back-end teams, it aims to provide a distributed,
> easily
> > extendable, operationally predictable and highly scalable solution.
> > For front-end developers, it aims to simplify the development process by
> > enabling them to rapidly build and operate mobile and web applications
> > without requiring backend expertise.
> >
> >
> > == Background ==
> >
> > Developing web or mobile applications obviously necessitates writing and
> > maintaining more than just front-end code. Even simple applications can
> > implicitly rely on server code being run to store users, perform database
> > queries, serve images and video files, etc. Developing and maintaining
> such
> > backend services requires skills not always available or expected of app
> > development teams. Beyond that, the proliferation of apps inside of
> > companies leads to the creation of many different, ad-hoc, unequally
> > maintained backend solutions created by employees and contractors alike
> and
> > hosted on a wide variety of environments. This is causing poor resource
> > usage, operational issues, as well as security, privacy & compliance
> > concerns.
> >
> > In response to this problem, companies have long tried to standardize
> their
> > server-side stack or unify them behind an ESB or API strategy.
> > Backends-as-a-Service follow a similar approach but their unique
> > characteristic is strongly tying  1) a persistence tier (typically a
> > database), 2) a server-side application tier delivering a set of common
> > services and 3) a set of client-side application interface mechanisms.
> For
> > example, a BaaS could package 1) MongoDB with 2) a node.js application
> that
> > offers access through 3) WebSockets. In the case of Usergrid, the
> trifecta
> > is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API.
> >
> > The Backend-as-a-Service approach has steadily gained popularity in the
> > last few years with cloud providers such Parse.com, Stackmob.com and
> > Kinvey.com, each operating tens of thousands of apps for tens of
> thousands
> > of developers. The trend has already reached large organizations as well,
> > with global companies such as Korea Telecom internally building a
> > privately-run BaaS platform. But so far, there have been limited options
> > for developers that want a non-proprietary, open option for hosting and
> > providing these services themselves, or for enterprise and government
> users
> > who want to provide these capabilities from their own data centers,
> > especially on a very large scale.
> >
> >
> > == Rationale ==
> >
> > The issue this proposal deals with is implicit in the name.
> > Backend-as-a-Service platforms are usually offered solely as proprietary
> > cloud services. They are typically closed sourced, hosted on public
> clouds,
> > and require subscription payment. Usergrid opens the playing field, by
> > making a fully-featured BaaS platform freely available to all. This
> > includes developers that previously could not afford them, such as mobile
> > enthusiasts, small boutiques, and cost-sensitive startups. This also
> > includes large companies that benefit from a reference implementation
> they
> > can deploy in trust, or exte

Re: [VOTE] Usergrid BaaS Stack for Apache Incubator (revised proposal)

[David Nalley]

On Mon, Sep 30, 2013 at 3:27 PM, Dave  wrote:
> I would like to call for a new vote on Usergrid, a multi-tenant
> Backend-as-a-Service stack for web & mobile applications based on RESTful
> APIs, as an Apache Incubator podling.
>

+1 (binding)

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

Re: [VOTE] Usergrid BaaS Stack for Apache Incubator (revised proposal)

[Ate Douma]

+1 (binding)

Ate

On 09/30/2013 09:27 PM, Dave wrote:

I would like to call for a new vote on Usergrid, a multi-tenant
Backend-as-a-Service stack for web & mobile applications based on RESTful
APIs, as an Apache Incubator podling.

The original proposal has been revised to name Dave Johnson as the Champion
and to bring Jim Jagielski back in as a Mentor and to add John Lewis
Mcgibbney as a Mentor. I also add some text to the Initial Committers
section and a new Interested Contributors section to list those who have
expressed interest in contributing.

Here is a link to the revised proposal:
https://wiki.apache.org/incubator/UsergridProposal

It is also pasted below:


= Usergrid Proposal =

== Abstract ==

Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile
applications, based on RESTful APIs.


== Proposal ==

Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”)
composed of an integrated distributed NoSQL database, application layer and
client tier with SDKs for developers looking to rapidly build web and/or
mobile applications. It provides elementary services (user registration &
management, data storage, file storage, queues) and retrieval features
(full text search, geolocation search, joins) to power common app features.

It is a multi-tenant system designed for deployment to public cloud
environments (such as Amazon Web Services, Rackspace, etc.) or to run on
traditional server infrastructures so that anyone can run their own private
BaaS deployment.

For architects and back-end teams, it aims to provide a distributed, easily
extendable, operationally predictable and highly scalable solution.
For front-end developers, it aims to simplify the development process by
enabling them to rapidly build and operate mobile and web applications
without requiring backend expertise.


== Background ==

Developing web or mobile applications obviously necessitates writing and
maintaining more than just front-end code. Even simple applications can
implicitly rely on server code being run to store users, perform database
queries, serve images and video files, etc. Developing and maintaining such
backend services requires skills not always available or expected of app
development teams. Beyond that, the proliferation of apps inside of
companies leads to the creation of many different, ad-hoc, unequally
maintained backend solutions created by employees and contractors alike and
hosted on a wide variety of environments. This is causing poor resource
usage, operational issues, as well as security, privacy & compliance
concerns.

In response to this problem, companies have long tried to standardize their
server-side stack or unify them behind an ESB or API strategy.
Backends-as-a-Service follow a similar approach but their unique
characteristic is strongly tying  1) a persistence tier (typically a
database), 2) a server-side application tier delivering a set of common
services and 3) a set of client-side application interface mechanisms. For
example, a BaaS could package 1) MongoDB with 2) a node.js application that
offers access through 3) WebSockets. In the case of Usergrid, the trifecta
is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API.

The Backend-as-a-Service approach has steadily gained popularity in the
last few years with cloud providers such Parse.com, Stackmob.com and
Kinvey.com, each operating tens of thousands of apps for tens of thousands
of developers. The trend has already reached large organizations as well,
with global companies such as Korea Telecom internally building a
privately-run BaaS platform. But so far, there have been limited options
for developers that want a non-proprietary, open option for hosting and
providing these services themselves, or for enterprise and government users
who want to provide these capabilities from their own data centers,
especially on a very large scale.


== Rationale ==

The issue this proposal deals with is implicit in the name.
Backend-as-a-Service platforms are usually offered solely as proprietary
cloud services. They are typically closed sourced, hosted on public clouds,
and require subscription payment. Usergrid opens the playing field, by
making a fully-featured BaaS platform freely available to all. This
includes developers that previously could not afford them, such as mobile
enthusiasts, small boutiques, and cost-sensitive startups. This also
includes large companies that benefit from a reference implementation they
can deploy in trust, or extend to their needs without losing time writing
less-vetted, less-performant boilerplate functionality.

Usergrid has been open source since 2011 and has grown as an independent
project, garnering 11 primary committers, 35 total contributors, 260+
participants on its mailing list, with 3,700+ commits, 200+ external
contributions, 350+ stars and 100+ forks on Github, not to mention several
large scale production deployments at major global companies in the media,
retail, telecom

Re: [VOTE] Usergrid BaaS Stack for Apache Incubator (revised proposal)

[Luciano Resende]

On Mon, Sep 30, 2013 at 12:27 PM, Dave  wrote:

> I would like to call for a new vote on Usergrid, a multi-tenant
> Backend-as-a-Service stack for web & mobile applications based on RESTful
> APIs, as an Apache Incubator podling.
>
> The original proposal has been revised to name Dave Johnson as the Champion
> and to bring Jim Jagielski back in as a Mentor and to add John Lewis
> Mcgibbney as a Mentor. I also add some text to the Initial Committers
> section and a new Interested Contributors section to list those who have
> expressed interest in contributing.
>
> Here is a link to the revised proposal:
>https://wiki.apache.org/incubator/UsergridProposal
>
> It is also pasted below:
>
>
> = Usergrid Proposal =
>
> == Abstract ==
>
> Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile
> applications, based on RESTful APIs.
>
>
> == Proposal ==
>
> Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”)
> composed of an integrated distributed NoSQL database, application layer and
> client tier with SDKs for developers looking to rapidly build web and/or
> mobile applications. It provides elementary services (user registration &
> management, data storage, file storage, queues) and retrieval features
> (full text search, geolocation search, joins) to power common app features.
>
> It is a multi-tenant system designed for deployment to public cloud
> environments (such as Amazon Web Services, Rackspace, etc.) or to run on
> traditional server infrastructures so that anyone can run their own private
> BaaS deployment.
>
> For architects and back-end teams, it aims to provide a distributed, easily
> extendable, operationally predictable and highly scalable solution.
> For front-end developers, it aims to simplify the development process by
> enabling them to rapidly build and operate mobile and web applications
> without requiring backend expertise.
>
>
> == Background ==
>
> Developing web or mobile applications obviously necessitates writing and
> maintaining more than just front-end code. Even simple applications can
> implicitly rely on server code being run to store users, perform database
> queries, serve images and video files, etc. Developing and maintaining such
> backend services requires skills not always available or expected of app
> development teams. Beyond that, the proliferation of apps inside of
> companies leads to the creation of many different, ad-hoc, unequally
> maintained backend solutions created by employees and contractors alike and
> hosted on a wide variety of environments. This is causing poor resource
> usage, operational issues, as well as security, privacy & compliance
> concerns.
>
> In response to this problem, companies have long tried to standardize their
> server-side stack or unify them behind an ESB or API strategy.
> Backends-as-a-Service follow a similar approach but their unique
> characteristic is strongly tying  1) a persistence tier (typically a
> database), 2) a server-side application tier delivering a set of common
> services and 3) a set of client-side application interface mechanisms. For
> example, a BaaS could package 1) MongoDB with 2) a node.js application that
> offers access through 3) WebSockets. In the case of Usergrid, the trifecta
> is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API.
>
> The Backend-as-a-Service approach has steadily gained popularity in the
> last few years with cloud providers such Parse.com, Stackmob.com and
> Kinvey.com, each operating tens of thousands of apps for tens of thousands
> of developers. The trend has already reached large organizations as well,
> with global companies such as Korea Telecom internally building a
> privately-run BaaS platform. But so far, there have been limited options
> for developers that want a non-proprietary, open option for hosting and
> providing these services themselves, or for enterprise and government users
> who want to provide these capabilities from their own data centers,
> especially on a very large scale.
>
>
> == Rationale ==
>
> The issue this proposal deals with is implicit in the name.
> Backend-as-a-Service platforms are usually offered solely as proprietary
> cloud services. They are typically closed sourced, hosted on public clouds,
> and require subscription payment. Usergrid opens the playing field, by
> making a fully-featured BaaS platform freely available to all. This
> includes developers that previously could not afford them, such as mobile
> enthusiasts, small boutiques, and cost-sensitive startups. This also
> includes large companies that benefit from a reference implementation they
> can deploy in trust, or extend to their needs without losing time writing
> less-vetted, less-performant boilerplate functionality.
>
> Usergrid has been open source since 2011 and has grown as an independent
> project, garnering 11 primary committers, 35 total contributors, 260+
> participants on its mailing list, with 3,700+ commits, 200+ external
> 

Re: [VOTE] Usergrid BaaS Stack for Apache Incubator (revised proposal)

[Dave]

Thanks for all the votes, folks! I think our 72 hour voting period is
almost over and I'll call and end to voting later today.

One small note about minor changes to the proposal:
- I changed Shaozhuang Liu affiliation because he will be contributing as
an independent
- I removed the Interested Developers section from the proposal, those
listed asked to be removed

Thanks,
Dave


On Mon, Sep 30, 2013 at 3:27 PM, Dave  wrote:

> I would like to call for a new vote on Usergrid, a multi-tenant
> Backend-as-a-Service stack for web & mobile applications based on RESTful
> APIs, as an Apache Incubator podling.
>
> The original proposal has been revised to name Dave Johnson as the
> Champion and to bring Jim Jagielski back in as a Mentor and to add John
> Lewis Mcgibbney as a Mentor. I also add some text to the Initial
> Committers section and a new Interested Contributors section to list those
> who have expressed interest in contributing.
>
> Here is a link to the revised proposal:
>https://wiki.apache.org/incubator/UsergridProposal
>
> It is also pasted below:
>
>
> = Usergrid Proposal =
>
> == Abstract ==
>
> Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile
> applications, based on RESTful APIs.
>
>
> == Proposal ==
>
> Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”)
> composed of an integrated distributed NoSQL database, application layer and
> client tier with SDKs for developers looking to rapidly build web and/or
> mobile applications. It provides elementary services (user registration &
> management, data storage, file storage, queues) and retrieval features
> (full text search, geolocation search, joins) to power common app features.
>
> It is a multi-tenant system designed for deployment to public cloud
> environments (such as Amazon Web Services, Rackspace, etc.) or to run on
> traditional server infrastructures so that anyone can run their own private
> BaaS deployment.
>
> For architects and back-end teams, it aims to provide a distributed,
> easily extendable, operationally predictable and highly scalable solution.
> For front-end developers, it aims to simplify the development process by
> enabling them to rapidly build and operate mobile and web applications
> without requiring backend expertise.
>
>
> == Background ==
>
> Developing web or mobile applications obviously necessitates writing and
> maintaining more than just front-end code. Even simple applications can
> implicitly rely on server code being run to store users, perform database
> queries, serve images and video files, etc. Developing and maintaining such
> backend services requires skills not always available or expected of app
> development teams. Beyond that, the proliferation of apps inside of
> companies leads to the creation of many different, ad-hoc, unequally
> maintained backend solutions created by employees and contractors alike and
> hosted on a wide variety of environments. This is causing poor resource
> usage, operational issues, as well as security, privacy & compliance
> concerns.
>
> In response to this problem, companies have long tried to standardize
> their server-side stack or unify them behind an ESB or API strategy.
> Backends-as-a-Service follow a similar approach but their unique
> characteristic is strongly tying  1) a persistence tier (typically a
> database), 2) a server-side application tier delivering a set of common
> services and 3) a set of client-side application interface mechanisms. For
> example, a BaaS could package 1) MongoDB with 2) a node.js application that
> offers access through 3) WebSockets. In the case of Usergrid, the trifecta
> is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API.
>
> The Backend-as-a-Service approach has steadily gained popularity in the
> last few years with cloud providers such Parse.com, Stackmob.com and
> Kinvey.com, each operating tens of thousands of apps for tens of thousands
> of developers. The trend has already reached large organizations as well,
> with global companies such as Korea Telecom internally building a
> privately-run BaaS platform. But so far, there have been limited options
> for developers that want a non-proprietary, open option for hosting and
> providing these services themselves, or for enterprise and government users
> who want to provide these capabilities from their own data centers,
> especially on a very large scale.
>
>
> == Rationale ==
>
> The issue this proposal deals with is implicit in the name.
> Backend-as-a-Service platforms are usually offered solely as proprietary
> cloud services. They are typically closed sourced, hosted on public clouds,
> and require subscription payment. Usergrid opens the playing field, by
> making a fully-featured BaaS platform freely available to all. This
> includes developers that previously could not afford them, such as mobile
> enthusiasts, small boutiques, and cost-sensitive startups. This also
> includes large companies that benefit from a refe

Re: [VOTE] Usergrid BaaS Stack for Apache Incubator (revised proposal)

[Marvin Humphrey]

On Wed, Oct 2, 2013 at 5:15 AM, Dave  wrote:
> Thanks for all the votes, folks! I think our 72 hour voting period is
> almost over and I'll call and end to voting later today.

Looking forward to the arrival of a promising new podling. :)

> One small note about minor changes to the proposal:

For the record: the wiki page may have changed, but as discussed in a long and
heated general@incubator thread from June (which I hope not to revisit) votes
cast in this thread count against the version embedded in the message which
kicked off the VOTE.  I don't see any problems arising as a result of this
technicality if nobody else does, so please carry on.

Marvin Humphrey

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

Re: [VOTE] Usergrid BaaS Stack for Apache Incubator (revised proposal)

[Lewis John Mcgibbney]

Hi All,

+1

On Tue, Oct 1, 2013 at 9:24 PM, wrote:

>
> On 09/30/2013 09:27 PM, Dave wrote:
>
>> I would like to call for a new vote on Usergrid, a multi-tenant
>> Backend-as-a-Service stack for web & mobile applications based on RESTful
>> APIs, as an Apache Incubator podling.
>>
>> The original proposal has been revised to name Dave Johnson as the
>> Champion
>> and to bring Jim Jagielski back in as a Mentor and to add John Lewis
>> Mcgibbney as a Mentor. I also add some text to the Initial Committers
>> section and a new Interested Contributors section to list those who have
>> expressed interest in contributing.
>>
>> Here is a link to the revised proposal:
>> 
>> https://wiki.apache.org/**incubator/UsergridProposal
>>
>> It is also pasted below:
>>
>>
>> = Usergrid Proposal =
>>
>> == Abstract ==
>>
>> Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile
>> applications, based on RESTful APIs.
>>
>>
>> == Proposal ==
>>
>> Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”)
>> composed of an integrated distributed NoSQL database, application layer
>> and
>> client tier with SDKs for developers looking to rapidly build web and/or
>> mobile applications. It provides elementary services (user registration &
>> management, data storage, file storage, queues) and retrieval features
>> (full text search, geolocation search, joins) to power common app
>> features.
>>
>> It is a multi-tenant system designed for deployment to public cloud
>> environments (such as Amazon Web Services, Rackspace, etc.) or to run on
>> traditional server infrastructures so that anyone can run their own
>> private
>> BaaS deployment.
>>
>> For architects and back-end teams, it aims to provide a distributed,
>> easily
>> extendable, operationally predictable and highly scalable solution.
>> For front-end developers, it aims to simplify the development process by
>> enabling them to rapidly build and operate mobile and web applications
>> without requiring backend expertise.
>>
>>
>> == Background ==
>>
>> Developing web or mobile applications obviously necessitates writing and
>> maintaining more than just front-end code. Even simple applications can
>> implicitly rely on server code being run to store users, perform database
>> queries, serve images and video files, etc. Developing and maintaining
>> such
>> backend services requires skills not always available or expected of app
>> development teams. Beyond that, the proliferation of apps inside of
>> companies leads to the creation of many different, ad-hoc, unequally
>> maintained backend solutions created by employees and contractors alike
>> and
>> hosted on a wide variety of environments. This is causing poor resource
>> usage, operational issues, as well as security, privacy & compliance
>> concerns.
>>
>> In response to this problem, companies have long tried to standardize
>> their
>> server-side stack or unify them behind an ESB or API strategy.
>> Backends-as-a-Service follow a similar approach but their unique
>> characteristic is strongly tying  1) a persistence tier (typically a
>> database), 2) a server-side application tier delivering a set of common
>> services and 3) a set of client-side application interface mechanisms. For
>> example, a BaaS could package 1) MongoDB with 2) a node.js application
>> that
>> offers access through 3) WebSockets. In the case of Usergrid, the trifecta
>> is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API.
>>
>> The Backend-as-a-Service approach has steadily gained popularity in the
>> last few years with cloud providers such Parse.com, Stackmob.com and
>> Kinvey.com, each operating tens of thousands of apps for tens of thousands
>> of developers. The trend has already reached large organizations as well,
>> with global companies such as Korea Telecom internally building a
>> privately-run BaaS platform. But so far, there have been limited options
>> for developers that want a non-proprietary, open option for hosting and
>> providing these services themselves, or for enterprise and government
>> users
>> who want to provide these capabilities from their own data centers,
>> especially on a very large scale.
>>
>>
>> == Rationale ==
>>
>> The issue this proposal deals with is implicit in the name.
>> Backend-as-a-Service platforms are usually offered solely as proprietary
>> cloud services. They are typically closed sourced, hosted on public
>> clouds,
>> and require subscription payment. Usergrid opens the playing field, by
>> making a fully-featured BaaS platform freely available to all. This
>> includes developers that previously could not afford them, such as mobile
>> enthusiasts, small boutiques, and cost-sensitive startups. This also
>> includes large companies that benefit from a reference implementation they
>> can deploy in trust, or extend to their needs without losing time writing
>> less-vetted, less-performant boilerplate funct

[RESULT][VOTE] Usergrid BaaS Stack for Apache Incubator (revised proposal)

[David Crossley]

Adjusting the email Subject to "[RESULT][VOTE] ..."
to enable the voting status monitor:
http://incubator.apache.org/facilities.html#voting-status

-David

Dave wrote:
> I am officially closing the vote. We have 11 binding +1 votes, 4
> non-binding votes and no -1 notes. Usergrid is now officially part of the
> Apache Incubator. Thanks to everybody who helped put together the proposal,
> those who joined the discussion, those who voted and the Usergrid community.
> 
> +1 binding votes
> 
>Afkham Azeez
>Alan D. Cabrera
>Alex Karasulu
>Ate Douma
>Bertrand Delacretaz
>Chip Childers
>David Nalley
>Henry Saputra
>Jim Jagielski
>Luciano Resende
>Marvin Humphrey
> 
> +1 non-binding
> 
>Larry McCay
>Lewis John Mcgibbney
>Lieven Govaerts
>Raminder Singh
> 
> Totals
> 
>11 binding +1 votes
>4 non-binding +1 votes
>0 -1 votes
> 
> Thanks,
> Dave
> 
> 
> PS. this also happens to be the 2nd anniversary of the day that Usergrid
> was released on Github. Happy Birthday Usergrid!

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

Re: [RESULT][VOTE] Usergrid BaaS Stack for Apache Incubator (revised proposal)

[Chris Mattmann]

Hi David,

Just an FYI I also VOTEd +1 on this.
Congrats and good luck!

Cheers,
Chris


-Original Message-
From: David Crossley 
Reply-To: "general@incubator.apache.org" 
Date: Friday, October 4, 2013 5:08 PM
To: "general@incubator.apache.org" 
Subject: [RESULT][VOTE] Usergrid BaaS Stack for Apache Incubator (revised
proposal)

>Adjusting the email Subject to "[RESULT][VOTE] ..."
>to enable the voting status monitor:
>http://incubator.apache.org/facilities.html#voting-status
>
>-David
>
>Dave wrote:
>> I am officially closing the vote. We have 11 binding +1 votes, 4
>> non-binding votes and no -1 notes. Usergrid is now officially part of
>>the
>> Apache Incubator. Thanks to everybody who helped put together the
>>proposal,
>> those who joined the discussion, those who voted and the Usergrid
>>community.
>> 
>> +1 binding votes
>> 
>>Afkham Azeez
>>Alan D. Cabrera
>>Alex Karasulu
>>Ate Douma
>>Bertrand Delacretaz
>>Chip Childers
>>David Nalley
>>Henry Saputra
>>Jim Jagielski
>>Luciano Resende
>>Marvin Humphrey
>> 
>> +1 non-binding
>> 
>>Larry McCay
>>Lewis John Mcgibbney
>>Lieven Govaerts
>>Raminder Singh
>> 
>> Totals
>> 
>>11 binding +1 votes
>>4 non-binding +1 votes
>>0 -1 votes
>> 
>> Thanks,
>> Dave
>> 
>> 
>> PS. this also happens to be the 2nd anniversary of the day that Usergrid
>> was released on Github. Happy Birthday Usergrid!
>
>-
>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