You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by Stack <st...@duboce.net> on 2014/01/07 20:19:40 UTC
Podling report proposal
I was going to send this in as our first podling report this afternoon (I'm
late!). Let me know if anything else I should add? Thanks,
St.Ack
Phoenix is an open source SQL query engine for Apache HBase, a NoSQL data
store. It is accessed as a JDBC driver and enables querying and managing
HBase tables using SQL.
Phoenix has been incubating since 12/11/2013.
Three most important issues to address in the move towards graduation:
1) Get the necessary IP clearance from Salesforce to import and re-license
existing open source project under pheoenix.incubator.apache.org.
2) Get verification that our project name is acceptable [1].
3) Perform first release out of apache incubator
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
This is our first report. No issues at this time.
How has the community developed since the last report?
Questions are starting to come in on the apache dev and user mailing lists.
No new committers.
How has the project developed since the last report?
* The proposal committers have all been setup with Apache accounts.
* Website is up [2]
* Mailing lists and source repo have all set up (thanks to INFRA).
* Working toward a 3.0.0 release in our existing open source project while
we wait for on 1.) above.
Date of last release:
No release yet.
When were the last committers or PMC members elected?
No new committers or PMC members.
1. https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-44?filter=-2
2. http://phoenix.incubator.apache.org/
Re: Podling report proposal
Posted by Andrew Purtell <ap...@apache.org>.
Ok, thanks.
On Thursday, January 9, 2014, Stack wrote:
> Sorry about that Andrew. It looks like we are to make these markings
> ourselves and Marvin helped out by filling in a few of the lads meantime
> till we got w/ the program.
>
> I went to Edit the report and it has this on the top:
>
> "[image: /!\] *FINAL* [image: /!\]
>
> This report has been submitted to the Board. Please do not edit further."
>
>
> Another report is due next month. We can do it right next time around?
>
> St.Ack
>
>
> On Thu, Jan 9, 2014 at 12:37 PM, Andrew Purtell <apurtell@apache.org<javascript:;>>
> wrote:
>
> > And I would like the signed-off-by state of the current report fixed.
> > Thanks again.
> >
> >
> > On Thu, Jan 9, 2014 at 12:28 PM, Andrew Purtell <apurtell@apache.org<javascript:;>
> >
> > wrote:
> >
> > > I gave a +1 for this report on private@phoenix yet was left off the
> > > signed-off-by list. That is not acceptable, I am committed to being
> > > diligent here. Are we going to do these on private@ or on dev@?
> Thanks.
> > >
> > >
> > > On Thu, Jan 9, 2014 at 8:56 AM, James Taylor Gmail <
> > > giacomotaylor@gmail.com <javascript:;>> wrote:
> > >
> > >> No update: waiting on paperwork from Intel which is expected today or
> > >> tomorrow.
> > >>
> > >> On Jan 9, 2014, at 5:18 AM, Steven Noels <stevenn@apache.org<javascript:;>>
> wrote:
> > >>
> > >> > On Wed, Jan 8, 2014, at 09:02 PM, James Taylor wrote:
> > >> >
> > >> >> My thinking is that having the dev traffic come through our Apache
> > >> >> mailing
> > >> >> list, but pointing folks back to our github repo would be
> confusing.
> > >> The
> > >> >> current plan is to get this done early next week. If it drags on
> > >> longer,
> > >> >> we
> > >> >> can always change plans.
> > >> >>
> > >> >> Sound reasonable?
> > >> >
> > >> > Makes perfect sense, thanks. Any update on the IP clearance bit?
> > >> >
> > >> > Steven.
> > >>
> > >
> > >
> > >
> > > --
> > > Best regards,
> > >
> > > - Andy
> > >
> > > Problems worthy of attack prove their worth by hitting back. - Piet
> Hein
> > > (via Tom White)
> > >
> >
> >
> >
> > --
> > Best regards,
> >
> > - Andy
> >
> > Problems worthy of attack prove their worth by hitting back. - Piet Hein
> > (via Tom White)
> >
>
--
Best regards,
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)
Re: Podling report proposal
Posted by Stack <st...@duboce.net>.
Sorry about that Andrew. It looks like we are to make these markings
ourselves and Marvin helped out by filling in a few of the lads meantime
till we got w/ the program.
I went to Edit the report and it has this on the top:
"[image: /!\] *FINAL* [image: /!\]
This report has been submitted to the Board. Please do not edit further."
Another report is due next month. We can do it right next time around?
St.Ack
On Thu, Jan 9, 2014 at 12:37 PM, Andrew Purtell <ap...@apache.org> wrote:
> And I would like the signed-off-by state of the current report fixed.
> Thanks again.
>
>
> On Thu, Jan 9, 2014 at 12:28 PM, Andrew Purtell <ap...@apache.org>
> wrote:
>
> > I gave a +1 for this report on private@phoenix yet was left off the
> > signed-off-by list. That is not acceptable, I am committed to being
> > diligent here. Are we going to do these on private@ or on dev@? Thanks.
> >
> >
> > On Thu, Jan 9, 2014 at 8:56 AM, James Taylor Gmail <
> > giacomotaylor@gmail.com> wrote:
> >
> >> No update: waiting on paperwork from Intel which is expected today or
> >> tomorrow.
> >>
> >> On Jan 9, 2014, at 5:18 AM, Steven Noels <st...@apache.org> wrote:
> >>
> >> > On Wed, Jan 8, 2014, at 09:02 PM, James Taylor wrote:
> >> >
> >> >> My thinking is that having the dev traffic come through our Apache
> >> >> mailing
> >> >> list, but pointing folks back to our github repo would be confusing.
> >> The
> >> >> current plan is to get this done early next week. If it drags on
> >> longer,
> >> >> we
> >> >> can always change plans.
> >> >>
> >> >> Sound reasonable?
> >> >
> >> > Makes perfect sense, thanks. Any update on the IP clearance bit?
> >> >
> >> > Steven.
> >>
> >
> >
> >
> > --
> > Best regards,
> >
> > - Andy
> >
> > Problems worthy of attack prove their worth by hitting back. - Piet Hein
> > (via Tom White)
> >
>
>
>
> --
> Best regards,
>
> - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>
Re: Podling report proposal
Posted by Andrew Purtell <ap...@apache.org>.
And I would like the signed-off-by state of the current report fixed.
Thanks again.
On Thu, Jan 9, 2014 at 12:28 PM, Andrew Purtell <ap...@apache.org> wrote:
> I gave a +1 for this report on private@phoenix yet was left off the
> signed-off-by list. That is not acceptable, I am committed to being
> diligent here. Are we going to do these on private@ or on dev@? Thanks.
>
>
> On Thu, Jan 9, 2014 at 8:56 AM, James Taylor Gmail <
> giacomotaylor@gmail.com> wrote:
>
>> No update: waiting on paperwork from Intel which is expected today or
>> tomorrow.
>>
>> On Jan 9, 2014, at 5:18 AM, Steven Noels <st...@apache.org> wrote:
>>
>> > On Wed, Jan 8, 2014, at 09:02 PM, James Taylor wrote:
>> >
>> >> My thinking is that having the dev traffic come through our Apache
>> >> mailing
>> >> list, but pointing folks back to our github repo would be confusing.
>> The
>> >> current plan is to get this done early next week. If it drags on
>> longer,
>> >> we
>> >> can always change plans.
>> >>
>> >> Sound reasonable?
>> >
>> > Makes perfect sense, thanks. Any update on the IP clearance bit?
>> >
>> > Steven.
>>
>
>
>
> --
> Best regards,
>
> - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>
--
Best regards,
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)
Re: Podling report proposal
Posted by Andrew Purtell <ap...@apache.org>.
I gave a +1 for this report on private@phoenix yet was left off the
signed-off-by list. That is not acceptable, I am committed to being
diligent here. Are we going to do these on private@ or on dev@? Thanks.
On Thu, Jan 9, 2014 at 8:56 AM, James Taylor Gmail
<gi...@gmail.com>wrote:
> No update: waiting on paperwork from Intel which is expected today or
> tomorrow.
>
> On Jan 9, 2014, at 5:18 AM, Steven Noels <st...@apache.org> wrote:
>
> > On Wed, Jan 8, 2014, at 09:02 PM, James Taylor wrote:
> >
> >> My thinking is that having the dev traffic come through our Apache
> >> mailing
> >> list, but pointing folks back to our github repo would be confusing. The
> >> current plan is to get this done early next week. If it drags on longer,
> >> we
> >> can always change plans.
> >>
> >> Sound reasonable?
> >
> > Makes perfect sense, thanks. Any update on the IP clearance bit?
> >
> > Steven.
>
--
Best regards,
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)
Re: Podling report proposal
Posted by James Taylor Gmail <gi...@gmail.com>.
No update: waiting on paperwork from Intel which is expected today or tomorrow.
On Jan 9, 2014, at 5:18 AM, Steven Noels <st...@apache.org> wrote:
> On Wed, Jan 8, 2014, at 09:02 PM, James Taylor wrote:
>
>> My thinking is that having the dev traffic come through our Apache
>> mailing
>> list, but pointing folks back to our github repo would be confusing. The
>> current plan is to get this done early next week. If it drags on longer,
>> we
>> can always change plans.
>>
>> Sound reasonable?
>
> Makes perfect sense, thanks. Any update on the IP clearance bit?
>
> Steven.
Re: Podling report proposal
Posted by Steven Noels <st...@apache.org>.
On Wed, Jan 8, 2014, at 09:02 PM, James Taylor wrote:
> My thinking is that having the dev traffic come through our Apache
> mailing
> list, but pointing folks back to our github repo would be confusing. The
> current plan is to get this done early next week. If it drags on longer,
> we
> can always change plans.
>
> Sound reasonable?
Makes perfect sense, thanks. Any update on the IP clearance bit?
Steven.
Re: Podling report proposal
Posted by Stack <st...@duboce.net>.
It does to me. If it drags let us revisit
On Jan 8, 2014 9:03 PM, "James Taylor" <ja...@apache.org> wrote:
> We're working on switching over to our Apache home (and looking forward to
> having more committers help with answering questions from our existing user
> base). We're waiting on a bit of paperwork for the IP clearance and we'll
> do the cutover. I'd like to make a clean break with
> - source code on Apache
> - quick initial release of our existing stable release repackaged and
> relicensed.
> - continue working on our next release, but from our master branch in our
> Apache git repo
> My thinking is that having the dev traffic come through our Apache mailing
> list, but pointing folks back to our github repo would be confusing. The
> current plan is to get this done early next week. If it drags on longer, we
> can always change plans.
>
> Sound reasonable?
>
> Thanks,
> James
>
>
> On Wed, Jan 8, 2014 at 11:44 AM, Stack <st...@duboce.net> wrote:
>
> > On Wed, Jan 8, 2014 at 12:24 AM, Steven Noels <st...@apache.org>
> wrote:
> >
> > > On Tue, Jan 7, 2014, at 11:19 AM, Stack wrote:
> > > > I was going to send this in as our first podling report this
> afternoon
> > > > (I'm
> > > > late!). Let me know if anything else I should add? Thanks,
> > > > St.Ack
> > >
> > > Looks good Stack.
> > >
> > > With lists set up, shouldn't we gently push all discussion (user- dev-
> > > private-) to ASF lists (unless that's the case already).
> > >
> >
> > Is Steve's suggestion happening James?
> > Thanks,
> > St.Ack
> >
>
Re: Podling report proposal
Posted by James Taylor <ja...@apache.org>.
We're working on switching over to our Apache home (and looking forward to
having more committers help with answering questions from our existing user
base). We're waiting on a bit of paperwork for the IP clearance and we'll
do the cutover. I'd like to make a clean break with
- source code on Apache
- quick initial release of our existing stable release repackaged and
relicensed.
- continue working on our next release, but from our master branch in our
Apache git repo
My thinking is that having the dev traffic come through our Apache mailing
list, but pointing folks back to our github repo would be confusing. The
current plan is to get this done early next week. If it drags on longer, we
can always change plans.
Sound reasonable?
Thanks,
James
On Wed, Jan 8, 2014 at 11:44 AM, Stack <st...@duboce.net> wrote:
> On Wed, Jan 8, 2014 at 12:24 AM, Steven Noels <st...@apache.org> wrote:
>
> > On Tue, Jan 7, 2014, at 11:19 AM, Stack wrote:
> > > I was going to send this in as our first podling report this afternoon
> > > (I'm
> > > late!). Let me know if anything else I should add? Thanks,
> > > St.Ack
> >
> > Looks good Stack.
> >
> > With lists set up, shouldn't we gently push all discussion (user- dev-
> > private-) to ASF lists (unless that's the case already).
> >
>
> Is Steve's suggestion happening James?
> Thanks,
> St.Ack
>
Re: Podling report proposal
Posted by Stack <st...@duboce.net>.
On Wed, Jan 8, 2014 at 12:24 AM, Steven Noels <st...@apache.org> wrote:
> On Tue, Jan 7, 2014, at 11:19 AM, Stack wrote:
> > I was going to send this in as our first podling report this afternoon
> > (I'm
> > late!). Let me know if anything else I should add? Thanks,
> > St.Ack
>
> Looks good Stack.
>
> With lists set up, shouldn't we gently push all discussion (user- dev-
> private-) to ASF lists (unless that's the case already).
>
Is Steve's suggestion happening James?
Thanks,
St.Ack
Re: Podling report proposal
Posted by Steven Noels <st...@apache.org>.
On Tue, Jan 7, 2014, at 11:19 AM, Stack wrote:
> I was going to send this in as our first podling report this afternoon
> (I'm
> late!). Let me know if anything else I should add? Thanks,
> St.Ack
Looks good Stack.
With lists set up, shouldn't we gently push all discussion (user- dev-
private-) to ASF lists (unless that's the case already).
Thanks,
Steven.
Re: Podling report proposal
Posted by Jesse Yates <je...@gmail.com>.
+1
On Wednesday, January 8, 2014, Devaraj Das wrote:
> +1
>
> On Tue, Jan 7, 2014 at 1:12 PM, James Taylor <jamestaylor@apache.org<javascript:;>>
> wrote:
> > +1
> >
> >
> > On Tue, Jan 7, 2014 at 12:30 PM, Enis Söztutar <enis@apache.org<javascript:;>>
> wrote:
> >
> >> Looks good.
> >>
> >>
> >> On Tue, Jan 7, 2014 at 11:19 AM, Stack <stack@duboce.net <javascript:;>>
> wrote:
> >>
> >> > I was going to send this in as our first podling report this afternoon
> >> (I'm
> >> > late!). Let me know if anything else I should add? Thanks,
> >> > St.Ack
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > Phoenix is an open source SQL query engine for Apache HBase, a NoSQL
> data
> >> > store. It is accessed as a JDBC driver and enables querying and
> managing
> >> > HBase tables using SQL.
> >> >
> >> > Phoenix has been incubating since 12/11/2013.
> >> >
> >> > Three most important issues to address in the move towards graduation:
> >> >
> >> > 1) Get the necessary IP clearance from Salesforce to import and
> >> re-license
> >> > existing open source project under pheoenix.incubator.apache.org.
> >> > 2) Get verification that our project name is acceptable [1].
> >> > 3) Perform first release out of apache incubator
> >> >
> >> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> >> > aware of?
> >> >
> >> > This is our first report. No issues at this time.
> >> >
> >> > How has the community developed since the last report?
> >> >
> >> > Questions are starting to come in on the apache dev and user mailing
> >> > lists.
> >> >
> >> > No new committers.
> >> >
> >> > How has the project developed since the last report?
> >> >
> >> > * The proposal committers have all been setup with Apache accounts.
> >> > * Website is up [2]
> >> > * Mailing lists and source repo have all set up (thanks to INFRA).
> >> > * Working toward a 3.0.0 release in our existing open source project
> >> while
> >> > we wait for on 1.) above.
> >> >
> >> > Date of last release:
> >> >
> >> > No release yet.
> >> >
> >> > When were the last committers or PMC members elected?
> >> >
> >> > No new committers or PMC members.
> >> >
> >> >
> >> > 1.
> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-44?filter=-2
> >> > 2. http://phoenix.incubator.apache.org/
> >> >
> >>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
--
-------------------
Jesse Yates
@jesse_yates
jyates.github.com
Re: Podling report proposal
Posted by Devaraj Das <dd...@hortonworks.com>.
+1
On Tue, Jan 7, 2014 at 1:12 PM, James Taylor <ja...@apache.org> wrote:
> +1
>
>
> On Tue, Jan 7, 2014 at 12:30 PM, Enis Söztutar <en...@apache.org> wrote:
>
>> Looks good.
>>
>>
>> On Tue, Jan 7, 2014 at 11:19 AM, Stack <st...@duboce.net> wrote:
>>
>> > I was going to send this in as our first podling report this afternoon
>> (I'm
>> > late!). Let me know if anything else I should add? Thanks,
>> > St.Ack
>> >
>> >
>> >
>> >
>> >
>> > Phoenix is an open source SQL query engine for Apache HBase, a NoSQL data
>> > store. It is accessed as a JDBC driver and enables querying and managing
>> > HBase tables using SQL.
>> >
>> > Phoenix has been incubating since 12/11/2013.
>> >
>> > Three most important issues to address in the move towards graduation:
>> >
>> > 1) Get the necessary IP clearance from Salesforce to import and
>> re-license
>> > existing open source project under pheoenix.incubator.apache.org.
>> > 2) Get verification that our project name is acceptable [1].
>> > 3) Perform first release out of apache incubator
>> >
>> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>> > aware of?
>> >
>> > This is our first report. No issues at this time.
>> >
>> > How has the community developed since the last report?
>> >
>> > Questions are starting to come in on the apache dev and user mailing
>> > lists.
>> >
>> > No new committers.
>> >
>> > How has the project developed since the last report?
>> >
>> > * The proposal committers have all been setup with Apache accounts.
>> > * Website is up [2]
>> > * Mailing lists and source repo have all set up (thanks to INFRA).
>> > * Working toward a 3.0.0 release in our existing open source project
>> while
>> > we wait for on 1.) above.
>> >
>> > Date of last release:
>> >
>> > No release yet.
>> >
>> > When were the last committers or PMC members elected?
>> >
>> > No new committers or PMC members.
>> >
>> >
>> > 1. https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-44?filter=-2
>> > 2. http://phoenix.incubator.apache.org/
>> >
>>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: Podling report proposal
Posted by James Taylor <ja...@apache.org>.
+1
On Tue, Jan 7, 2014 at 12:30 PM, Enis Söztutar <en...@apache.org> wrote:
> Looks good.
>
>
> On Tue, Jan 7, 2014 at 11:19 AM, Stack <st...@duboce.net> wrote:
>
> > I was going to send this in as our first podling report this afternoon
> (I'm
> > late!). Let me know if anything else I should add? Thanks,
> > St.Ack
> >
> >
> >
> >
> >
> > Phoenix is an open source SQL query engine for Apache HBase, a NoSQL data
> > store. It is accessed as a JDBC driver and enables querying and managing
> > HBase tables using SQL.
> >
> > Phoenix has been incubating since 12/11/2013.
> >
> > Three most important issues to address in the move towards graduation:
> >
> > 1) Get the necessary IP clearance from Salesforce to import and
> re-license
> > existing open source project under pheoenix.incubator.apache.org.
> > 2) Get verification that our project name is acceptable [1].
> > 3) Perform first release out of apache incubator
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware of?
> >
> > This is our first report. No issues at this time.
> >
> > How has the community developed since the last report?
> >
> > Questions are starting to come in on the apache dev and user mailing
> > lists.
> >
> > No new committers.
> >
> > How has the project developed since the last report?
> >
> > * The proposal committers have all been setup with Apache accounts.
> > * Website is up [2]
> > * Mailing lists and source repo have all set up (thanks to INFRA).
> > * Working toward a 3.0.0 release in our existing open source project
> while
> > we wait for on 1.) above.
> >
> > Date of last release:
> >
> > No release yet.
> >
> > When were the last committers or PMC members elected?
> >
> > No new committers or PMC members.
> >
> >
> > 1. https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-44?filter=-2
> > 2. http://phoenix.incubator.apache.org/
> >
>
Re: Podling report proposal
Posted by Enis Söztutar <en...@apache.org>.
Looks good.
On Tue, Jan 7, 2014 at 11:19 AM, Stack <st...@duboce.net> wrote:
> I was going to send this in as our first podling report this afternoon (I'm
> late!). Let me know if anything else I should add? Thanks,
> St.Ack
>
>
>
>
>
> Phoenix is an open source SQL query engine for Apache HBase, a NoSQL data
> store. It is accessed as a JDBC driver and enables querying and managing
> HBase tables using SQL.
>
> Phoenix has been incubating since 12/11/2013.
>
> Three most important issues to address in the move towards graduation:
>
> 1) Get the necessary IP clearance from Salesforce to import and re-license
> existing open source project under pheoenix.incubator.apache.org.
> 2) Get verification that our project name is acceptable [1].
> 3) Perform first release out of apache incubator
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> This is our first report. No issues at this time.
>
> How has the community developed since the last report?
>
> Questions are starting to come in on the apache dev and user mailing
> lists.
>
> No new committers.
>
> How has the project developed since the last report?
>
> * The proposal committers have all been setup with Apache accounts.
> * Website is up [2]
> * Mailing lists and source repo have all set up (thanks to INFRA).
> * Working toward a 3.0.0 release in our existing open source project while
> we wait for on 1.) above.
>
> Date of last release:
>
> No release yet.
>
> When were the last committers or PMC members elected?
>
> No new committers or PMC members.
>
>
> 1. https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-44?filter=-2
> 2. http://phoenix.incubator.apache.org/
>
Re: Podling report proposal
Posted by lars hofhansl <la...@apache.org>.
+1
________________________________
From: Stack <st...@duboce.net>
To: dev@phoenix.incubator.apache.org
Sent: Tuesday, January 7, 2014 11:19 AM
Subject: Podling report proposal
I was going to send this in as our first podling report this afternoon (I'm
late!). Let me know if anything else I should add? Thanks,
St.Ack
Phoenix is an open source SQL query engine for Apache HBase, a NoSQL data
store. It is accessed as a JDBC driver and enables querying and managing
HBase tables using SQL.
Phoenix has been incubating since 12/11/2013.
Three most important issues to address in the move towards graduation:
1) Get the necessary IP clearance from Salesforce to import and re-license
existing open source project under pheoenix.incubator.apache.org.
2) Get verification that our project name is acceptable [1].
3) Perform first release out of apache incubator
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
This is our first report. No issues at this time.
How has the community developed since the last report?
Questions are starting to come in on the apache dev and user mailing lists.
No new committers.
How has the project developed since the last report?
* The proposal committers have all been setup with Apache accounts.
* Website is up [2]
* Mailing lists and source repo have all set up (thanks to INFRA).
* Working toward a 3.0.0 release in our existing open source project while
we wait for on 1.) above.
Date of last release:
No release yet.
When were the last committers or PMC members elected?
No new committers or PMC members.
1. https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-44?filter=-2
2. http://phoenix.incubator.apache.org/