Re: [VOTE] Usergrid BaaS Stack for Apache Incubator

[Senaka Fernando]

+1 (binding)

Thanks,
Senaka.


On Tue, Sep 24, 2013 at 6:49 PM, Olivier Lamy  wrote:

> +1
>
> On 23 September 2013 22:44, Jim Jagielski  wrote:
> > After a useful and successful proposal cycle, I would like to propose
> > a VOTE on accepting Usergrid, a multi-tenant Backend-as-a-Service
> > stack for web & mobile applications based on RESTful APIs, as an Apache
> > Incubator podling.
> >
> > Voting to run for 72+ hours...
> >
> > Here is a link to the 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+
> > participan

Re: [VOTE] Graduate Nuvem as a sub-project under Apache Tuscany

[Senaka Fernando]

+1

Thanks,
Senaka.

On Tue, Nov 20, 2012 at 11:11 AM, Luciano Resende wrote:

> Apache Nuvem will define an open application programming interface
> for common cloud application services, allowing applications to be
> easily ported across the most popular cloud platforms. It is
> currently composed of multiple cloud SCA components (Data, Queue, Chat),
> and supports multiple cloud platforms such as AWS, GAE, etc as well
> as standalone deployment. Nuvem was accepted for Incubation on June, 2010,
> and several of the active committers are already part of the Tuscany PMC.
>
> Nuvem was accepted for Incubation on June 2010, and is currently a small
> community, where the contributions are 100% done by volunteers in their own
> free time, which makes the level of activity
> low, compared to what is required for graduating it as a TLP.
>
> Having said that, Nuvem has a great synergy with Apache Tuscany, and after
> discussion between the two projects, we are seeking IPMC approval to allow
> graduation of Apache Nuvem as a sub-project under Apache Tuscany.
>
> Nuvem Graduation Vote thread
> *http://s.apache.org/nuvem-graduation*
> *http://s.apache.org/nuvem-graduation-result*
>
> Tuscany Graduation Vote thread
> *http://s.apache.org/tuscany-accept-nuvem*
> *http://s.apache.org/tuscany-accept-nuvem-result*
>
> Please cast your votes:
>
> [ ] +1 Graduate Nuvem as a sub-project under Apache Tuscany
>
> [ ] - 1 Nuvem is not ready to graduate as a sub-project under Apache
> Tuscany, because ...
>
>
> --
> Luciano Resende
> http://people.apache.org/~lresende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>

Re: [PROPOSAL][VOTE] Subversion

[Senaka Fernando]

+1

Thanks,
Senaka.

On Thu, Nov 5, 2009 at 1:42 AM, Greg Stein  wrote:

>  Subversion is a version control system.  You probably know it well as
> it is the version control system employed by the Apache Software
> Foundation.
>
>  The Subversion project would like to join the Apache Software
> Foundation to remove the overhead of having to run its own
> corporation.  The Subversion project is already run quite like an
> Apache project, and already counts a number of ASF Members amongst
> its committers.
>
>  Work on Subversion was originally started at CollabNet; Karl Fogel
> was hired in January 2000.  Jim Blandy, at RedHat, already had an
> initial design for the storage system, which was incorporated into the
> FS design.  In February Brian Behlendorf invited Greg Stein to
> contribute his WebDAV experience to Subversion.  Ben Colins-Sussman
> was hired in April 2000 to work on the project.  In that same month
> the first "all hands" meeting was held, where a number of "interested
> people" came together to talk about the project.
>
>  Subversion was run as an open source project since the early days.
> Now, more than nine years later, it retains a healthy community,
> and has a good number of committers.  In the life span of Subversion,
> several committers have switched employers and have maintained involvement.
> The committership is diverse, both geographically as well as in terms of
> employment.
>
>  The equivalent of the PMC consists of all the full committers to the
> Subversion project (currently around 55 people).  The community uses the
> voting process also used at the ASF.  Releases are signed off by gathering
> votes/digital signatures of each committer who verified the release
> candidate.
>
>  We feel the ASF and Subversion communities are very compatible,
> witness the cross interest that already exists. There is both a
> vibrant developer as well as a large and active user community.
> Technology-wise, Subversion builds on APR, and implements two Apache
> HTTP Server modules.
>
>  Note that Subversion has a number of related projects, which are not
> part of this proposal (e.g. cvs2svn, TortoiseSVN, Subclipse).
>
>  More information on Subversion can be found at
> http://www.subversion.org/ and http://subversion.tigris.org/.
>
>  The Subversion Corporation has a license to all source code, and has
> CLAs on file for nearly all it's committers.  That is, we have all but
> one or two full committers, and some percentage of partial committers.
>
>  We have a number of *user-configurable* dependencies which are not
> compatible with the AL:
>  - Neon, a HTTP client library, used by libsvn_ra_neon, is LGPL.
>   (An alternative HTTP client library, libsvn_ra_serf uses the Serf
>library under ALv2.)
>
>  - Qt, KDE and GNOME libraries are also under LGPL-2.1. D-Bus (which
> is also used by libsvn_auth_gnome_keyring and libsvn_auth_kwallet) is
> under Academic Free License 2.1 or >=GPL-2.
>   (This support is for integration for KDE and GNOME's authentication
>providers.)
>
>  - libintl
>   (This library provides translation support for systems without
>a proper internationalization library.)
>
>  - BDB
>   (This is used by the libsvn_fs_base system which stores its data
>in BDB; an alternative repository system called fs_fs does not
>have this dependency.)
>
> ---
> Required Resources
>  - Mailing lists
>   - dev
>   - issues
>   - users
>   - private
>   - commits
>   - announce
>   - breakage (see
> http://subversion.tigris.org/ds/viewForumSummary.do?dsForumId=552)
>   - We will work with the Infrastructure team to transfer the subscriber
> listings to the new destinations.
>  - Subversion:
>   - We have not made a decision whether we prefer Subversion should be
> imported into the main ASF Subversion repository or be hosted as a
> separate repository to enable early testing of the repository code.  We
> intend to discuss this during the Incubation process before the code is
> imported.  It is also understood that ASF infrastructure team may be
> willing to run custom pre-release Subversion server builds for the
> entire ASF, so this separate repository option may not be required.
>   - The Subversion source code can be found at:
> http://svn.collab.net/repos/svn/.
>  - Issue tracking
>   - We haven't made a decision between JIRA or Bugzilla at this time and
> expect this decision to be made as part of the Incubation process.  Our
> current issue tracking system uses Issuezilla (a fork of Bugzilla) and
> we have not yet decided whether we want to import our previous issues
> into the new system and will decide this in the course of the
> Incubation
> process.
>   - Our current issue tracker is at
> http://subversion.tigris.org/issue-tracker.html.
>  - Buildbot
>   - We currently use buildbot across a number of platforms and
> configurations
> for automated builds and testing.  Over time, we would like to migrate

Re: [PROPOSAL] Zeta Components

[Senaka Fernando]

+1 (non-binding).

Thanks,
Senaka.

On Mon, Apr 19, 2010 at 7:22 PM, Tobias Schlitt  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi all,
>
> please find below our proposal for Zeta Components. The proposal is also
> available in the wiki:
>
>http://wiki.apache.org/incubator/ZetaComponentsProposal
>
> Regards,
> Toby
>
> =
> Proposal: Zeta Components
> =
>
> Zeta Components is a high-quality library of loosely coupled PHP
> components.
>
> - 
> Proposal
> - 
>
> The Zeta project was originally named *eZ Components* [1]_ and was
> developed as an open source project under New BSD license by eZ Systems
> AS [2]_. Involving a name change, eZ Systems is willing relicense the
> source code basis and documentation and to donate it to the Apache
> Software Foundation.
>
> The goal of the project is to provide high-quality, loosely coupled
> components for the development of applications based on PHP version 5.1
> and above. On the one hand, Zeta contains standard components for e.g.
> database abstraction, templating, email, image manipulation and more, on
> the other hand there are modules which are unique in the PHP world, like
> a document format conversion component, a WebDAV server module and a
> workflow based programming framework.
>
> The project is developed with a strong focus on code and documentation
> quality, as well as on backwards compatibility. It follows a
> well-defined development process with extensive architecture and design
> discussions and prescribes a test driven development approach.
>
> - --
> Background
> - --
>
> PHP is the most common language for developing web applications, but is
> also in use in other areas. While the language itself already ships with
> many libraries to solve different tasks, there is still a need for user
> land libraries to provide more complex repetitive functionality.
>
> Zeta provides components dedicated to such functionality. An example for
> a tasks that can be solved using Zeta are processing and sending of
> email. This is already possible from within pure PHP. But working with
> multi-part MIME emails is not easily possible and a real pain when doing
> that on your own. For that reason, a module [5]_ exists in Zeta which
> allows the developer to easily create and send such emails and to
> receive and process them.
>
> The Zeta project currently consists of the following components:
>
> - - Archive
> - - Authentication
> - - AuthenticationDatabaseTiein
> - - Base
> - - Cache
> - - Configuration
> - - ConsoleTools
> - - Database
> - - DatabaseSchema
> - - Debug
> - - Document
> - - EventLog
> - - EventLogDatabaseTiein
> - - Execution
> - - Feed
> - - File
> - - Framework
> - - Graph
> - - GraphDatabaseTiein
> - - ImageAnalysis
> - - ImageConversion
> - - Mail
> - - MvcAuthenticationTiein
> - - MvcFeedTiein
> - - MvcMailTiein
> - - MvcTemplateTiein
> - - MvcTools
> - - PersistentObject
> - - PersistentObjectDatabaseSchemaTiein
> - - PhpGenerator
> - - Search
> - - SignalSlot
> - - SystemInformation
> - - Template
> - - TemplateTranslationTiein
> - - Translation
> - - TranslationCacheTiein
> - - Tree
> - - TreeDatabaseTiein
> - - TreePersistentObjectTiein
> - - Url
> - - UserInput
> - - Webdav
> - - Workflow
> - - WorkflowDatabaseTiein
> - - WorkflowEventLogTiein
> - - WorkflowSignalSlotTiein
>
> As can be seen, there are typical web-application modules included, such
> as the Feed component - which allows users to generate and consume
> different types of aggregation feeds -, the already mentioned Mail
> component, a template component for website templates and a WebDAV
> server component. Beside that, the library also contains many modules
> which are not only suitable for web applications, like a component for
> managing various archive file formats, multiple layers of database
> abstraction, tools for image manipulation, basic interfaces and
> implementations of a model-view-controller [17]_ structure and more.
>
> In contrast to other frameworks, the components in Zeta are loosely
> coupled and there are almost no hard inter-dependencies between them.
> Instead, if a component can be integrated with another one, a so-called
> *Tiein* component is provided, supplying the classes necessary to couple
> the components. This allows users to cherry pick the components they
> need, without the need of using the whole stack. That is especially
> useful for using the provided modules in legacy code or when there is a
> standard framework to build new applications on.
>
> - -
> Rationale
> - -
>
> Zeta is a library of high-quality, loosely coupled components for
> application development on basis of PHP. The project existed for five
> years now under the New BSD license, named eZ Components. It has been
> developed so far as a product of eZ Systems AS by a team of lately 4
> core developers and received various contributions from 3rd part

Re: [PROPOSAL] Deltacloud Project

[Senaka Fernando]

+1. I too would like to contribute to this project.

Thanks,
Senaka.

On Fri, May 7, 2010 at 1:11 AM, David Lutterkort  wrote:

> Hi,
>
> I would like to propose the Deltacloud API[1] for addition to the Apache
> incubator.
>
> I have added the initial proposal to the Wiki[2]; it is also included
> below for convenience.
>
> There are a few additional people that have expressed interest in
> becoming initial committers; I am waiting for their express consent to
> list them as committers, and will add them to the Wiki as I get that.
>
> We are looking forward to any and all feedback and/or questions on the
> proposal. We already have two mentors, but would very much welcome
> additional volunteers to help steer Deltacloud through the incubation
> process.
>
> David
>
> [1] http://deltacloud.org/
> [2] http://wiki.apache.org/incubator/DeltacloudProposal
>
>
> Deltacloud, a cross-cloud web service API
> =
>
> Abstract
> 
>
> Deltacloud defines a web service API for interacting with cloud service
> providers and resources in those clouds in a unified manner. In addition,
> it consists of a number of implementations of this API for the most popular
> clouds.
>
> Proposal
> 
>
>  * Define a REST-based API for managing and manipulating cloud resources
>in a manner that isolates the API client as much as possible from the
>particulars of specific cloud API's
>  * Provide an open API definition for cloud providers for their IaaS
>clouds and a basis on which PaaS providers can layer their offering
>  * Provide image management and directory capabilities as part of the API
>  * The current implementation allows instance lifecycle management
>(create, start, stop, destroy, reboot), and querying of related
>resources like available images, instance sizes, and allowed instance
>actions for a number of public and private clouds
>  * Currently supported are Amazon EC2, Eucalyptus, Rackspace, RimuHosting,
>GoGrid, OpenNebula, and RHEV-M
>  * Future enhancements should broaden the scope of the API to include
>networking, firewalling, authentication, accounting, and image
>management
>
> Background
> --
>
> An important issue for cloud users is that of avoiding lock-in to a
> specific cloud. By providing a cross-cloud API for
> infrastructure-as-a-service (IaaS) clouds, Deltacloud addresses this
> concern and strives to provide the best possible API for writing
> cloud-management applications that can target multiple clouds.
>
> There are also no efforts currently to define a truly open-source cloud
> API, one for which there is a proper upstream, independent of any specific
> cloud provider. Deltacloud API strives to create a community around
> building an open-source cloud API in a manner that fully allows for
> tried-and-true open source mechanisms such as user-driven innovation.
>
> By providing a web-service API, Deltacloud is language agnostic, and one of
> its subordinated goals is to provide a practical vocabulary for talking
> about IaaS cloud resources and operations on them.
>
> Rationale
> -
>
> IaaS clouds provide numerous advantages to their users, for example,
> making provisioning new servers more agile. If users directly use the
> 'native' cloud API's, they risk locking themselves in to the API of a
> specific cloud provider.
>
> There is therefore a strong need for an API that can be used across a wide
> range of public and private clouds, and that can serve as the basis for
> developing cloud management applications; in contrast to several existing
> language-specific efforts in this direction, Deltacloud is conceived as a
> web service.
>
> This will allow the project to attract a broad community of users of the
> API and cloud providers interested in offering a truly open-source API,
> with a proper upstream community.
>
> We strongly believe that the best way to drive such an API effort is by
> developing the API and open-source implementations of the API side-by-side.
>
> Initial Goals
> -
>
> Deltacloud is an existing open source project; initially started by Red
> Hat, it has attracted a number of outside contributors. We look at moving
> this project to the ASF as the next step to broaden the community, and put
> the project on solid footing since the ASF governance model is well suited
> for the Deltacloud project goals. The ASF is a great location for
> Deltacloud to build a community and will benefit from ASL licensing.
>
> Current Status
> --
>
> Deltacloud API is licensed under the LGPL:
>
>  * Deltacloud Website (http://deltacloud.org) There are two projects
> hosted there: the API under consideration here and the Aggregator (not part
> of this proposal, though also open source)
>  * Deltacloud git repository (
> http://git.fedorahosted.org/git/?p=deltacloud/core.git;a=summary)
>  * Deltacloud mailing lists
>- users (https://fedorahosted.org/mailman/listinfo/d

Re: Cross Cloud TLP, was Re: [PROPOSAL] Deltacloud Project

[Senaka Fernando]

On Wed, May 12, 2010 at 10:31 PM, Luciano Resende wrote:

> On Wed, May 12, 2010 at 9:58 AM, Raymond Feng  wrote:
> > +1. Some existing Apache projects such as Tuscany also have interests in
> this space.
> >
>
> +1 For Paul's suggestion and Raymond's remakrs.
>

+1. Indeed it makes a lot of sense in the user community PoV.

Thanks,
Senaka.

>
>
>
> --
> Luciano Resende
> http://people.apache.org/~lresende 
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Deltacloud Project

[Senaka Fernando]

+1.

Thanks,
Senaka.

On Thu, May 13, 2010 at 7:58 PM, Gurkan Erdogdu wrote:

> +1 (binding)
>
>
> --Gurkan
>
>
> 
> From: David Lutterkort 
> To: general@incubator.apache.org
> Sent: Thu, May 13, 2010 3:45:08 AM
> Subject: [VOTE] Deltacloud Project
>
> Hi all,
>
> after the discussion so far [1], I'd like to put Detlacloud for a vote
> for acceptance into the Apache Incubator according to the proposal[2]
>
> I _think_ I've added everybody who expressed interest in being a mentor
> or initial committer to the proposal - if I have forgotten anybody,
> please holler.
>
> Please reply to this mail with your vote.
>
> David
>
> [1]
> http://mail-archives.apache.org/mod_mbox/incubator-general/201005.mbox/%3c1273174879.7253.99.ca...@avon.watzmann.net%3e
> [2] http://wiki.apache.org/incubator/DeltacloudProposal
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [PROPOSAL] Nuvem Project

[Senaka Fernando]

+1, I'd like to contribute to this project.

Thanks,
Senaka.

On Thu, Jun 10, 2010 at 12:36 AM, Luciano Resende wrote:

> Hi,
>
> I would like to propose the Nuvem project for addition to the Apache
> incubator.
>
> The initial proposal is available at the the Wiki[1], and it is also
> included below for convenience.
>
> We are looking forward to any and all feedback and/or questions on the
> proposal. We are also looking for a Champion and mentors, and would
> very much welcome additional volunteers to help steer Nuvem through
> the incubation process.
>
>
> [1] http://wiki.apache.org/incubator/Nuvem
>
> Apache Nuvem, a cross-cloud application programming interface
> =
>
> Abstract
> ---
>
> Nuvem will define an open application programming interface for common
> cloud application services, allowing applications to be easily ported
> across the most popular cloud platforms.
>
> Proposal
> ---
>
>  * Define an open API that abstracts common cloud platform services to
> help decouple the application logic from the particulars of a specific
> proprietary cloud.
>  * Implement the Nuvem API for popular clouds such as Google
> AppEngine, Amazon EC2 and Microsoft Azure.
>  * Initially focus on User Authentication and Authorization,
> Distributed Cache, Data Store, Queuing; then extend to other services
> such as Chat, Logging, and Debugging.
>
> Background
> 
>
> An important issue for application developers is to avoid lock-in to a
> specific cloud application platform. By providing a cross-cloud
> application programming interface that abstracts common cloud platform
> services, Nuvem addresses this concern and strives to help make
> applications easily portable across multiple clouds.
>
> In mixed cloud deployments, applications need to access platform
> services across cloud boundaries. Nuvem will make this possible by
> providing a remote API for these cloud application platform services.
>
> Rationale
> -
>
> There are currently no efforts to define a truly open-source API to
> abstract common cloud platform services. Nuvem strives to create a
> community around building an open-source cloud application programming
> interface in a manner that fully allows for tried-and-true open source
> mechanisms such as user-driven innovation.
>
> Initial Goals
> ---
>
> A Nuvem prototype is currently being developed in an Apache Tuscany
> sandbox, providing initial support for some cloud platform services
> from Google AppEngine and Amazon EC2. We look at moving this prototype
> to the Apache Incubator as the next step to broaden the community,
> expand the API to support more services and cloud platforms.
>
> Current Status
> ---
>
> The initial code has been developed under the Apache Software License
> 2.0 by current Apache committers.
>
> Meritocracy
> ---
>
> We recognize the importance of running the project as a meritocracy.
> We are eager to engage other members of the community and operate to
> the standard of meritocracy that Apache emphasizes; we believe this is
> the most effective method of growing our community and enabling
> widespread adoption.
>
> Community
> ---
>
> The initial committer list consists of a couple of independent
> developers. We expect that the project will greatly increase in
> contribution base, and this is one aspect the project will monitor in
> becoming ready for graduation.
>
> Alignment
> -
>
> Currently, there are no other Apache projects concerned with building
> a cross-cloud API for application platform services. We feel that it
> would be a good complement to the set of Apache projects and could
> provide them with an API for interacting with cloud application
> platforms.
>
> Nuvem complements Apache libCloud and Deltacloud projects (which both
> cover provisioning and elasticity in the cloud), providing portability
> of applications and application services   across heterogeneous cloud
> environments.
>
> Orphaned Products
> --
>
> The Nuvem developers have a long-term interest in use and maintenance
> of the code and there is also hope that different cloud providers will
> be interested in providing support for the Nuvem API and will join the
> project. We feel that it is important to put formal governance in
> place both for the project and the contributors as the project
> expands. We feel the ASF is the best location for this.
>
> Inexperience with Open Source
> ---
>
> Luciano Resende have been involved with Open Source Software for
> several years; he has actively contributed to Apache Tuscany, Apache
> PhotArk and contributed to and/or mentored other Apache podlings. He
> is also part of the Apache Community Development PMC and
> Admin/co-Admin for the Google Summer of Code mentoring project.
> Raymond Fend, is also a long time committer and PMC m

Re: [VOTE] Nuvem Project

[Senaka Fernando]

On Sat, Jun 19, 2010 at 8:38 PM, Luciano Resende wrote:

> On Sat, Jun 19, 2010 at 8:07 AM, Luciano Resende 
> wrote:
> > After initial discussion [1], please vote on the acceptance of Nuvem
> > Project for incubation at the Apache Incubator. The full proposal is
> > available at the end of this message and on the wiki at
> >
> >   http://wiki.apache.org/incubator/Nuvem
> >
> > We ask the Incubator PMC to sponsor the project with Luciano Resende
> > as the Champion and Jean-Frederic Clere, Paul Fremantle, Ant Elder and
> > Donald Woods volunteering to be mentors.
> >
> > Please cast your votes:
> >
> > [ ] +1, bring Nuvem into Incubator
> > [ ] +0, I don't care either way
> > [ ] -1, do not bring Nuvem into Incubator, because...
> >
> > The vote is open for the next 72 hours and only votes from the
> > Incubator PMC are binding.
>
>
> +1, bring Nuvem into Incubator
>

+1.

Thanks,
Senaka.

>
> --
> Luciano Resende
> http://people.apache.org/~lresende 
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: VOTE: Release Apache RAT 0.7

[Senaka Fernando]

+1. Looks good.

Thanks,
Senaka.

On Thu, Aug 5, 2010 at 4:35 PM, Jochen Wiedmann
wrote:

> Hi,
>
> the RAT developer team would like your approvement for a release of
> Apache RAT 0.7.
>
> The distribution files (binary and source) are here:
>
>
> https://repository.apache.org/content/repositories/orgapacherat-051/org/apache/rat/apache-rat/0.7/
>
> The proposed site and the KEYS file are here:
>
>  
> http://people.apache.org/~jochen/rat/site/
>  
> http://people.apache.org/~jochen/rat/KEYS
>
> The SVN tag:
>
>
> https://svn.apache.org/repos/asf/incubator/rat/main/tags/apache-rat-project-0.7/
>
> The list of resolved issues is here:
>
>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310750&status=5&status=6&fixfor=12313890&sorter/field=issuekey&sorter/order=DESC
>
> Please, cast your vote.
>
> [ ] +1
> [ ] =0
> [ ] -1
>
> Thanks,
>
> Jochen
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Kitty to Enter the Incubator

[Senaka Fernando]

+1.

Matthew, by the way, I'd like to contribute to this project.

Thanks,
Senaka.

On Wed, Sep 15, 2010 at 12:50 PM, msacks  wrote:

> At the advisement of the list, we have created a brand-new thread here
> for voting on the kitty proposal.
> The wiki page is located at:
> http://wiki.apache.org/incubator/KittyProposal
>
> Thanks.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [RESULT] [VOTE] Kitty to Enter the Incubator

[Senaka Fernando]

Hi Matthew,

You can consider my vote binding, as I'm part of the IPMC, and just FYR, you
have added Niclas twice.

Thanks and Best Regards,
Senaka.

On Sat, Oct 2, 2010 at 4:02 AM,  wrote:

> Corrected. Thanks for the catch!
>
> -Original Message-
> From: "Mark Struberg" 
> Sent: Friday, October 1, 2010 5:55pm
> To: general@incubator.apache.org
> Subject: Re: [RESULT] [VOTE] Kitty to Enter the Incubator
>
> you even have one more, since Niclas is also a member and IPMC [1] ;)
>
> LieGrue,
> strub
>
> [1] http://people.apache.org/committer-index.html
>
> --- On Fri, 10/1/10, matt...@matthewsacks.com 
> wrote:
>
> > From: matt...@matthewsacks.com 
> > Subject: Re: [RESULT] [VOTE] Kitty to Enter the Incubator
> > To: general@incubator.apache.org
> > Date: Friday, October 1, 2010, 9:40 PM
> > I am calling this vote as suggested:
> >
> > IPMC Binding:
> >
> > +1
> >
> > Jim Jagielski
> > Kevan Miller
> > Davanum Srinivas
> > Niclas Hedhman
> > Julien Vermillard
> > Alan D. Cabrera
> > Mark Struberg
> > Niclas Hedhman
> >
> > (my apologies to anyone I may have missed)
> >
> > Non-binding:
> >
> > Stuart Williams
> > Rainer Jung
> > Mohammad Nour El-Din
> >
> > (my apologies to any folks I may have missed)
> >
> > I will do follow-ups and Wiki page finessing next week.
> >
> >
> > Thanks to all,
> > Matthew Sacks
> > Bitsource, GlassCode, et al.
> >
> >
> >
> > -Original Message-
> > From: "Kevan Miller" 
> > Sent: Wednesday, September 29, 2010 6:52pm
> > To: general@incubator.apache.org
> > Subject: Re: [VOTE] Kitty to Enter the Incubator
> >
> >
> > On Sep 29, 2010, at 3:24 PM, matt...@matthewsacks.com
> > wrote:
> >
> > > Hi List,
> > > I would like to do a quick sanity check on this
> > thread.
> > > Please correct me if I am wrong, but we have 2 binding
> > PMC votes, 2 new contributors (Rainer Jung and Senaka
> > Fernando) and 1 new mentor (Kevan Miller).
> >
> > More binding votes than that... Senaka, Jim, Kevan, Niclas,
> > Julien, Alan (apologies if I'm missing . You also now have
> > Dims and Mark.
> >
> > >
> > > I believe my facts to be accurate. I plan on updating
> > the Wiki next week to reflect this when I complete some
> > travels, and create a fork for a Groovy port to begin that
> > work.
> >
> > IMO, time to call this vote and start podling setup
> > activities.
> >
> > --kevan
> > -
> > 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
> >
> >
>
>
>
>
> -
> 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] Apache ACE as a TLP

[Senaka Fernando]

+1 (binding)

Thanks,
Senaka.

On Sat, Dec 17, 2011 at 5:25 PM, Marcel Offermans <
marcel.offerm...@luminis.nl> wrote:

> Hello all,
>
> As the discussion about the resolution [1] offered no further feedback, it
> is time for the Apache ACE community to request that the IPMC vote on
> recommending this resolution [2] to the ASF board.
>
> Please cast your vote:
>
> [ ] +1 to recommend ACE's graduation
> [ ]  0 don't care
> [ ] -1 no, don't recommend yet, (because...)
>
> The vote will be open for 72 hours.
>
> Greetings, Marcel
>
>
> [1] http://markmail.org/thread/wfrvwmnu3y22oxys
>
> [2] see below:
>
> ## Resolution to create a TLP from graduating Incubator podling
>
>X. Establish the Apache ACE Project
>
>   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 related to the management and deployment
>   of OSGi based and other software artifacts for distribution
>   at no charge to the public.
>
>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>   Committee (PMC), to be known as the "Apache ACE Project",
>   be and hereby is established pursuant to Bylaws of the
>   Foundation; and be it further
>
>   RESOLVED, that the Apache ACE Project be and hereby is
>   responsible for the creation and maintenance of software
>   related to the management and deployment of OSGi based and
>   other software artifacts;
>   and be it further
>
>   RESOLVED, that the office of "Vice President, Apache ACE" 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 ACE Project, and to have primary responsibility
>   for management of the projects within the scope of
>   responsibility of the Apache ACE 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 ACE Project:
>
> * Angelo van der Sijpt 
> * Brian Topping
> * Clement Escoffier
> * Carsten Ziegeler 
> * Jean-Baptiste Onofre 
> * Karl Pauls   
> * Marcel Offermans 
> * Toni Menzel  
>
>   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Marcel Offermans
>   be appointed to the office of Vice President, Apache ACE, 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 initial Apache ACE PMC be and hereby is
>   tasked with the creation of a set of bylaws intended to
>   encourage open development and increased participation in the
>   Apache ACE Project; and be it further
>
>   RESOLVED, that the Apache ACE Project be and hereby
>   is tasked with the migration and rationalization of the Apache
>   Incubator ACE podling; and be it further
>
>   RESOLVED, that all responsibilities pertaining to the Apache
>   Incubator ACE podling encumbered upon the Apache Incubator
>   Project are hereafter discharged.
>
>
> Note to moderators: I sent this message before, over 24 hours ago, with my
> apache e-mail address (that is not subscribed to this list). It's still
> stuck in moderation, which is why I'm sending it again today. If ultimately
> both end up on the list, my apologies, I will summarize the responses over
> both messages.
>
>

Re: [PROPOSAL] Stonehenge

[Senaka Fernando]

Hi Paul,

Seems that this would become the most happening WS project @ Apache in the
future.

+1,
I'm interested.

Regards,
Senaka

On Wed, Nov 5, 2008 at 4:10 AM, Paul Fremantle <[EMAIL PROTECTED]> wrote:

> FYI
>
> Please jump in on [EMAIL PROTECTED] if you are interested in this
> proposal.
>
> Thanks
> Paul
>
> -- Forwarded message --
> From: Paul Fremantle <[EMAIL PROTECTED]>
> Date: Tue, Nov 4, 2008 at 4:34 PM
> Subject: [PROPOSAL] Stonehenge
> To: general@incubator.apache.org
>
>
> I'd like to propose Stonehenge as an incubator proposal.
>
> Stonehenge is a set of example applications for Service Oriented
> Architecture that spans languages and platforms and demonstrates best
> practise and interoperability.
>
> The full proposal is here:
> http://wiki.apache.org/incubator/StonehengeProposal
>
> As ever, all feedback, positive or negative is welcome. Also, any
> further mentors are more than welcome!
>
> Paul
>
> --
> Paul Fremantle
> Co-Founder and CTO, WSO2
> Apache Synapse PMC Chair
> OASIS WS-RX TC Co-chair
>
> blog: http://pzf.fremantle.org
> [EMAIL PROTECTED]
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
>
>
> --
> Paul Fremantle
> Co-Founder and CTO, WSO2
> Apache Synapse PMC Chair
> OASIS WS-RX TC Co-chair
>
> blog: http://pzf.fremantle.org
> [EMAIL PROTECTED]
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: [PROPOSAL] Stonehenge

[Senaka Fernando]

On Sat, Nov 15, 2008 at 9:24 PM, Robert Burrell Donkin <
[EMAIL PROTECTED]> wrote:

> On Thu, Nov 13, 2008 at 4:20 PM, Michael Champion
> <[EMAIL PROTECTED]> wrote:
> > I'd also point out that there are free SDKs and Express versions of most
> of the Microsoft development tools [1], targeted at non-commercial
> developers.  See  [2] for a neutral discussion of what has been left out of
> the Express editions.
> >
> > So, while these tools are not open source, there are no barriers that I
> know of against using them to build and test open source software.
> >
> > [1] http://www.microsoft.com/express/ (Designed for, but usable without
> Silverlight)
> > [2] http://en.wikipedia.org/wiki/Microsoft_Visual_Studio_Express
>
> great
>
> creating a short guide to getting involved in open source on .NET
> might help stronehenge encourage contributors


+1. Also, there are some ASF projects that use .NET technologies as of
present (ex:- Lucene, [1]), that might IMHO, be worth taking a look at.

[1] http://incubator.apache.org/projects/lucene.net.html

Regards,
Senaka

>
>
> - robert
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: Qpid graduates as TLP

[Senaka Fernando]

Congratulations!

Regards,
Senaka

On Mon, Dec 1, 2008 at 8:36 PM, Carl Trieloff <[EMAIL PROTECTED]> wrote:

>
> I want to take a few minutes to thank everyone involved on our graduation.
> The Apache board
> has approved our graduation and we will begin the post graduation
> transition.
>
> Congratulations to the project and many thanks to all those that have taken
> an interest in Qpid
>
> regards
> Carl.
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>