Catching up fully with this thread, I think its time for starting a PPMC vote. 
I will wait for end of today to see any further open ended concerns, if not I 
will start a vote if no one else beats me by then.

Suresh

On Mar 26, 2014, at 2:19 PM, Paul Fremantle <[email protected]> wrote:

> Noah
> 
> My apologies.
> 
> Removed any names
> 
>    Establish the Apache Stratos 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, for distribution at no charge to
>        the public, related to providing an implementation of a 
>        Platform-as-a-Service Framework.
> 
> 
>        NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>        Committee (PMC), to be known as the "Apache Stratos Project",
>        be and hereby is established pursuant to Bylaws of the
>        Foundation; and be it further
> 
>        RESOLVED, that the Apache Stratos Project be and hereby is
>        responsible for the creation and maintenance of software
>        related to providing an implementation of a Platform-as-a-Service 
>        Framework; and be it further
> 
> 
>        RESOLVED, that the office of "Vice President, Stratos" 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 Stratos Project, and to have primary responsibility
>        for management of the projects within the scope of
>        responsibility of the Apache Stratos 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 Stratos Project:
> 
> 
>        NOW, THEREFORE, BE IT FURTHER RESOLVED, that XXXXXXXXXX
>        be appointed to the office of Vice President, Stratos, 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 Stratos 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 Stratos Project; and be it further
> 
>        RESOLVED, that the Apache Stratos Project be and hereby
>        is tasked with the migration and rationalization of the Apache
>        Incubator Stratos podling; and be it further
> 
>        RESOLVED, that all responsibilities pertaining to the Apache
>        Incubator Stratos podling encumbered upon the Apache Incubator
>        Project are hereafter discharged.
> 
> 
> Paul
> 
> 
> On 26 March 2014 17:13, Noah Slater <[email protected]> wrote:
> As Chip points out, it is premature to include anybody's name here
> yet, even provisionally. It should be removed from the draft, and a
> separate discussion started privately to address that topic.
> 
> On 26 March 2014 16:33, Paul Fremantle <[email protected]> wrote:
> > Updated proposal with the new wording. I've also provisionally put Lakmal's
> > name in place as VP.
> >
> > Paul
> >
> >
> >        Establish the Apache Stratos 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, for distribution at no charge to
> >        the public, related to providing an implementation of a
> >        Platform-as-a-Service Framework.
> >
> >
> >        NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> >        Committee (PMC), to be known as the "Apache Stratos Project",
> >        be and hereby is established pursuant to Bylaws of the
> >        Foundation; and be it further
> >
> >        RESOLVED, that the Apache Stratos Project be and hereby is
> >        responsible for the creation and maintenance of software
> >        related to providing an implementation of a Platform-as-a-Service
> >        Framework; and be it further
> >
> >
> >        RESOLVED, that the office of "Vice President, Stratos" 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 Stratos Project, and to have primary responsibility
> >        for management of the projects within the scope of
> >        responsibility of the Apache Stratos 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 Stratos Project:
> >
> >
> >        NOW, THEREFORE, BE IT FURTHER RESOLVED, that Lakmal Warusawithana
> >
> >        be appointed to the office of Vice President, Stratos, 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 Stratos 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 Stratos Project; and be it further
> >
> >        RESOLVED, that the Apache Stratos Project be and hereby
> >        is tasked with the migration and rationalization of the Apache
> >        Incubator Stratos podling; and be it further
> >
> >        RESOLVED, that all responsibilities pertaining to the Apache
> >        Incubator Stratos podling encumbered upon the Apache Incubator
> >        Project are hereafter discharged.
> >
> > Paul
> >
> >
> > On 26 March 2014 15:04, Chip Childers <[email protected]> wrote:
> >>
> >> On Wed, Mar 26, 2014 at 10:57 AM, Paul Fremantle <[email protected]> wrote:
> >> > Chip
> >> >
> >> > I tried to get round your concern with the phrase PaaS foundation. I
> >> > guess
> >> > an alternative would be PaaS framework?
> >> >
> >> > Paul
> >>
> >> "framework" seems like it might be best (IMO)...  the term's a bit
> >> overused, but it's probably a bit better understood than just
> >> "foundation".
> >
> >
> >
> >
> > --
> > Paul Fremantle
> > CTO and Co-Founder, WSO2
> > OASIS WS-RX TC Co-chair, Apache Member
> >
> > UK: +44 207 096 0336
> > US: +1 646 595 7614
> >
> > blog: http://pzf.fremantle.org
> > twitter.com/pzfreo
> > [email protected]
> >
> > wso2.com Lean Enterprise Middleware
> >
> > Disclaimer: This communication may contain privileged or other confidential
> > information and is intended exclusively for the addressee/s. If you are not
> > the intended recipient/s, or believe that you may have received this
> > communication in error, please reply to the sender indicating that fact and
> > delete the copy you received and in addition, you should not print, copy,
> > retransmit, disseminate, or otherwise use the information contained in this
> > communication. Internet communications cannot be guaranteed to be timely,
> > secure, error or virus-free. The sender does not accept liability for any
> > errors or omissions.
> 
> 
> 
> --
> Noah Slater
> https://twitter.com/nslater
> 
> 
> 
> -- 
> Paul Fremantle
> CTO and Co-Founder, WSO2
> OASIS WS-RX TC Co-chair, Apache Member
> 
> UK: +44 207 096 0336
> US: +1 646 595 7614
> 
> blog: http://pzf.fremantle.org
> twitter.com/pzfreo
> [email protected]
> 
> wso2.com Lean Enterprise Middleware
> 
> Disclaimer: This communication may contain privileged or other confidential 
> information and is intended exclusively for the addressee/s. If you are not 
> the intended recipient/s, or believe that you may have received this 
> communication in error, please reply to the sender indicating that fact and 
> delete the copy you received and in addition, you should not print, copy, 
> retransmit, disseminate, or otherwise use the information contained in this 
> communication. Internet communications cannot be guaranteed to be timely, 
> secure, error or virus-free. The sender does not accept liability for any 
> errors or omissions.

Reply via email to