+1

On Wed, Oct 30, 2019 at 8:57 AM William Shen <wills...@marinsoftware.com>
wrote:

> +1!
>
> On Wed, Oct 30, 2019 at 8:27 AM Josh Elser <els...@apache.org> wrote:
>
> > Hi,
> >
> > As was previously discussed[1][2], there is a motion to "adopt" the
> > Tephra and Omid podlings as sub-projects to Apache Phoenix. A
> > sub-project is a distinct software project from some top-level project
> > (TLP) but operates under the guidance of a TLP (e.g. the TLP's PMC)
> >
> > Per the Incubator guidelines[3], we need to have a formal vote to adopt
> > them. While we still need details from these two podlings, I believe we
> > can have a VOTE now to keep things moving.
> >
> > Actions:
> > * Phoenix will incorporate Omid and Tephra as sub-projects and they will
> > continue to function under the Apache Phoenix PMC guidance.
> > * Any current podling member may request to be added as a Phoenix
> > committer. Podling members would be expected to demonstrate the normal
> > level of commitment to grow from a committer to a PMC member.
> >
> > Stating what I see as an implicit decision (but to alleviate any
> > possible confusion): all new community members will be expected to
> > function in the way that Phoenix currently does today (e.g
> > review-then-commit). Future Omid and Tephra development would happen in
> > the same way that Phoenix development happens today.
> >
> > Please vote:
> >
> > +1: to accept Omid and Tephra as Phoenix sub-projects and to allow any
> > PPMC to become Phoenix committers.
> >
> > -1/-0/+0: No and why..
> >
> > Here is my +1 (binding)
> >
> > This vote will be open for at least 72hrs (2019/11/02 1600 UTC).
> >
> >
> > [1]
> >
> >
> https://lists.apache.org/thread.html/ec00615cbbb4225885e3776f1e8fd071600a9c50f35769f453b8a779@%3Cdev.phoenix.apache.org%3E
> > [2]
> >
> >
> https://lists.apache.org/thread.html/692a030a27067c20b9228602af502199cd4d80eb0aa8ed6461ebe1ee@%3Cgeneral.incubator.apache.org%3E
> > [3]
> >
> >
> https://incubator.apache.org/guides/graduation.html#graduating_to_a_subproject
> >
>

Reply via email to