Re: Omid and Tephra graduating into Phoenix
Hi Alan,
Thanks. I’ll assist when the time comes.
Regards,
Dave
> On Nov 8, 2019, at 2:49 PM, Alan Gates wrote:
>
> I've reverted the change for now to avoid breaking any builds. Once we've
> either sorted out how to mark these as graduating or Phoenix has finished
> it's work and we have a link to resolve to, then I'll redo this.
>
> Alan.
>
> On Fri, Nov 8, 2019 at 2:26 PM Alan Gates wrote:
>
>> Sorry, I don't mean I won't fix it, I'm just not sure how to fix it at
>> this point.
>>
>> Alan.
>>
>> On Fri, Nov 8, 2019 at 2:21 PM Alan Gates wrote:
>>
>>> I found the instructions for that here:
>>> https://incubator.apache.org/guides/transferring.html
>>> I didn't put in the resolution link yet because there's no such link
>>> yet.
>>>
>>> Alan.
>>>
>>> On Fri, Nov 8, 2019 at 1:44 PM Dave Fisher wrote:
>>>
Hi Alan,
The podlings.xml change is not really correct. It’s not documented but
instead of you need to have a something like this for each:
https://phoenix.apache.org/omid/“/>
This creates the a link on the table on
https://incubator.apache.org/projects
Also, there is no “graduating” status.
>>> sponsor="Incubator" startdate="2016-03-28”>
must be
>>> sponsor="Incubator" startdate="2016-03-28” enddate=“2019-11-8”>
Whimsy may very well break unless this is fixed. The daily Incubator
site update may break as well.
Regards,
Dave
> On Nov 8, 2019, at 1:25 PM, Alan Gates wrote:
>
> I've updated the status of Omid and Tephra to 'graduating' in
> podlings.xml. I've also updated the projects/${podling}.xml for each
of
> them with info on the SGAs (which hadn't been put there) and on their
> status as graduating into Phoenix.
>
> I'll let the Phoenix PMC deal with github, JIRA, mailing lists, etc.
Once
> this is done I can update the status to 'graduated' in podlings.xml.
>
> Alan.
>
> On Tue, Nov 5, 2019 at 6:08 PM Justin Mclean
> wrote:
>
>> Hi,
>>
>>> I don't think so. I'll wait the 72 hours for the comment period to
end
>>> (started this morning) and then add a note to the report that Omid
and
>>> Tephra are graduating into Phoenix, unless Justin prefers something
else.
>>
>>
>> That's fine I’ve already note this in the report.
>>
>> Thanks,
>> Justin
>> -
>> 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: Omid and Tephra graduating into Phoenix
I've reverted the change for now to avoid breaking any builds. Once we've
either sorted out how to mark these as graduating or Phoenix has finished
it's work and we have a link to resolve to, then I'll redo this.
Alan.
On Fri, Nov 8, 2019 at 2:26 PM Alan Gates wrote:
> Sorry, I don't mean I won't fix it, I'm just not sure how to fix it at
> this point.
>
> Alan.
>
> On Fri, Nov 8, 2019 at 2:21 PM Alan Gates wrote:
>
>> I found the instructions for that here:
>> https://incubator.apache.org/guides/transferring.html
>> I didn't put in the resolution link yet because there's no such link
>> yet.
>>
>> Alan.
>>
>> On Fri, Nov 8, 2019 at 1:44 PM Dave Fisher wrote:
>>
>>> Hi Alan,
>>>
>>> The podlings.xml change is not really correct. It’s not documented but
>>> instead of you need to have a something like this for each:
>>>
>>> https://phoenix.apache.org/omid/“/>
>>>
>>> This creates the a link on the table on
>>> https://incubator.apache.org/projects
>>>
>>> Also, there is no “graduating” status.
>>>
>>> >> sponsor="Incubator" startdate="2016-03-28”>
>>>
>>> must be
>>>
>>> >> sponsor="Incubator" startdate="2016-03-28” enddate=“2019-11-8”>
>>>
>>> Whimsy may very well break unless this is fixed. The daily Incubator
>>> site update may break as well.
>>>
>>> Regards,
>>> Dave
>>>
>>> > On Nov 8, 2019, at 1:25 PM, Alan Gates wrote:
>>> >
>>> > I've updated the status of Omid and Tephra to 'graduating' in
>>> > podlings.xml. I've also updated the projects/${podling}.xml for each
>>> of
>>> > them with info on the SGAs (which hadn't been put there) and on their
>>> > status as graduating into Phoenix.
>>> >
>>> > I'll let the Phoenix PMC deal with github, JIRA, mailing lists, etc.
>>> Once
>>> > this is done I can update the status to 'graduated' in podlings.xml.
>>> >
>>> > Alan.
>>> >
>>> > On Tue, Nov 5, 2019 at 6:08 PM Justin Mclean >> >
>>> > wrote:
>>> >
>>> >> Hi,
>>> >>
>>> >>> I don't think so. I'll wait the 72 hours for the comment period to
>>> end
>>> >>> (started this morning) and then add a note to the report that Omid
>>> and
>>> >>> Tephra are graduating into Phoenix, unless Justin prefers something
>>> else.
>>> >>
>>> >>
>>> >> That's fine I’ve already note this in the report.
>>> >>
>>> >> Thanks,
>>> >> Justin
>>> >> -
>>> >> 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: Omid and Tephra graduating into Phoenix
Sorry, I don't mean I won't fix it, I'm just not sure how to fix it at this
point.
Alan.
On Fri, Nov 8, 2019 at 2:21 PM Alan Gates wrote:
> I found the instructions for that here:
> https://incubator.apache.org/guides/transferring.html
> I didn't put in the resolution link yet because there's no such link yet.
>
> Alan.
>
> On Fri, Nov 8, 2019 at 1:44 PM Dave Fisher wrote:
>
>> Hi Alan,
>>
>> The podlings.xml change is not really correct. It’s not documented but
>> instead of you need to have a something like this for each:
>>
>> https://phoenix.apache.org/omid/“/>
>>
>> This creates the a link on the table on
>> https://incubator.apache.org/projects
>>
>> Also, there is no “graduating” status.
>>
>> > sponsor="Incubator" startdate="2016-03-28”>
>>
>> must be
>>
>> > sponsor="Incubator" startdate="2016-03-28” enddate=“2019-11-8”>
>>
>> Whimsy may very well break unless this is fixed. The daily Incubator site
>> update may break as well.
>>
>> Regards,
>> Dave
>>
>> > On Nov 8, 2019, at 1:25 PM, Alan Gates wrote:
>> >
>> > I've updated the status of Omid and Tephra to 'graduating' in
>> > podlings.xml. I've also updated the projects/${podling}.xml for each of
>> > them with info on the SGAs (which hadn't been put there) and on their
>> > status as graduating into Phoenix.
>> >
>> > I'll let the Phoenix PMC deal with github, JIRA, mailing lists, etc.
>> Once
>> > this is done I can update the status to 'graduated' in podlings.xml.
>> >
>> > Alan.
>> >
>> > On Tue, Nov 5, 2019 at 6:08 PM Justin Mclean
>> > wrote:
>> >
>> >> Hi,
>> >>
>> >>> I don't think so. I'll wait the 72 hours for the comment period to
>> end
>> >>> (started this morning) and then add a note to the report that Omid and
>> >>> Tephra are graduating into Phoenix, unless Justin prefers something
>> else.
>> >>
>> >>
>> >> That's fine I’ve already note this in the report.
>> >>
>> >> Thanks,
>> >> Justin
>> >> -
>> >> 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: Omid and Tephra graduating into Phoenix
I found the instructions for that here:
https://incubator.apache.org/guides/transferring.html
I didn't put in the resolution link yet because there's no such link yet.
Alan.
On Fri, Nov 8, 2019 at 1:44 PM Dave Fisher wrote:
> Hi Alan,
>
> The podlings.xml change is not really correct. It’s not documented but
> instead of you need to have a something like this for each:
>
> https://phoenix.apache.org/omid/“/>
>
> This creates the a link on the table on
> https://incubator.apache.org/projects
>
> Also, there is no “graduating” status.
>
> sponsor="Incubator" startdate="2016-03-28”>
>
> must be
>
> sponsor="Incubator" startdate="2016-03-28” enddate=“2019-11-8”>
>
> Whimsy may very well break unless this is fixed. The daily Incubator site
> update may break as well.
>
> Regards,
> Dave
>
> > On Nov 8, 2019, at 1:25 PM, Alan Gates wrote:
> >
> > I've updated the status of Omid and Tephra to 'graduating' in
> > podlings.xml. I've also updated the projects/${podling}.xml for each of
> > them with info on the SGAs (which hadn't been put there) and on their
> > status as graduating into Phoenix.
> >
> > I'll let the Phoenix PMC deal with github, JIRA, mailing lists, etc.
> Once
> > this is done I can update the status to 'graduated' in podlings.xml.
> >
> > Alan.
> >
> > On Tue, Nov 5, 2019 at 6:08 PM Justin Mclean
> > wrote:
> >
> >> Hi,
> >>
> >>> I don't think so. I'll wait the 72 hours for the comment period to end
> >>> (started this morning) and then add a note to the report that Omid and
> >>> Tephra are graduating into Phoenix, unless Justin prefers something
> else.
> >>
> >>
> >> That's fine I’ve already note this in the report.
> >>
> >> Thanks,
> >> Justin
> >> -
> >> 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: Omid and Tephra graduating into Phoenix
Hi Alan, The podlings.xml change is not really correct. It’s not documented but instead of you need to have a something like this for each: https://phoenix.apache.org/omid/“/> This creates the a link on the table on https://incubator.apache.org/projects Also, there is no “graduating” status.
Re: Omid and Tephra graduating into Phoenix
I've updated the status of Omid and Tephra to 'graduating' in
podlings.xml. I've also updated the projects/${podling}.xml for each of
them with info on the SGAs (which hadn't been put there) and on their
status as graduating into Phoenix.
I'll let the Phoenix PMC deal with github, JIRA, mailing lists, etc. Once
this is done I can update the status to 'graduated' in podlings.xml.
Alan.
On Tue, Nov 5, 2019 at 6:08 PM Justin Mclean
wrote:
> Hi,
>
> > I don't think so. I'll wait the 72 hours for the comment period to end
> > (started this morning) and then add a note to the report that Omid and
> > Tephra are graduating into Phoenix, unless Justin prefers something else.
>
>
> That's fine I’ve already note this in the report.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>
Re: Omid and Tephra graduating into Phoenix
Hi, > I don't think so. I'll wait the 72 hours for the comment period to end > (started this morning) and then add a note to the report that Omid and > Tephra are graduating into Phoenix, unless Justin prefers something else. That's fine I’ve already note this in the report. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Omid and Tephra graduating into Phoenix
I don't think so. I'll wait the 72 hours for the comment period to end (started this morning) and then add a note to the report that Omid and Tephra are graduating into Phoenix, unless Justin prefers something else. Alan. On Tue, Nov 5, 2019 at 5:14 PM Andreas Neumann wrote: > Should Tephra still file a podling report this month? > -Andreas > > On Tue, Nov 5, 2019 at 12:00 PM Dave Fisher wrote: > > > For the changes to podlings.xml one example of a graduation to a > > subproject is DistributedLog. > > > > Regards, > > Dave > > > > Sent from my iPhone > > > > > On Nov 5, 2019, at 11:50 AM, Alan Gates wrote: > > > > > > Omid[1] and Tephra[2] have voted to join the Phoenix community as > > > sub-projects. Phoenix has voted to accept them[3]. Per the > instructions > > > at [4], this email is notice of that. Unless any objections are raised > > in > > > 72 hours the graduation will be considered accepted and both podlings > > will > > > move ahead with the details. > > > > > > Alan. > > > > > > 1. > > > > > > https://lists.apache.org/thread.html/d996692f30b30eea68c1e8db3c5095d6eb4877f7b358e401851130b2@%3Cdev.omid.apache.org%3E > > > 2. > > > > > > https://lists.apache.org/thread.html/33487013c347fe15f43a55cc2281613e1cce4f0cd07d27280ddad9bb@%3Cdev.tephra.apache.org%3E > > > 3. > > > > > > https://lists.apache.org/thread.html/29111aa8b59fe38ca11d6ca2f029009c437ed6986d6dcf2fb6fc5b2f@%3Cdev.phoenix.apache.org%3E > > > 4. > > > > > > https://incubator.apache.org/guides/graduation.html#graduating_to_a_subproject > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > >
Re: Omid and Tephra graduating into Phoenix
Should Tephra still file a podling report this month? -Andreas On Tue, Nov 5, 2019 at 12:00 PM Dave Fisher wrote: > For the changes to podlings.xml one example of a graduation to a > subproject is DistributedLog. > > Regards, > Dave > > Sent from my iPhone > > > On Nov 5, 2019, at 11:50 AM, Alan Gates wrote: > > > > Omid[1] and Tephra[2] have voted to join the Phoenix community as > > sub-projects. Phoenix has voted to accept them[3]. Per the instructions > > at [4], this email is notice of that. Unless any objections are raised > in > > 72 hours the graduation will be considered accepted and both podlings > will > > move ahead with the details. > > > > Alan. > > > > 1. > > > https://lists.apache.org/thread.html/d996692f30b30eea68c1e8db3c5095d6eb4877f7b358e401851130b2@%3Cdev.omid.apache.org%3E > > 2. > > > https://lists.apache.org/thread.html/33487013c347fe15f43a55cc2281613e1cce4f0cd07d27280ddad9bb@%3Cdev.tephra.apache.org%3E > > 3. > > > https://lists.apache.org/thread.html/29111aa8b59fe38ca11d6ca2f029009c437ed6986d6dcf2fb6fc5b2f@%3Cdev.phoenix.apache.org%3E > > 4. > > > https://incubator.apache.org/guides/graduation.html#graduating_to_a_subproject > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: Omid and Tephra graduating into Phoenix
For the changes to podlings.xml one example of a graduation to a subproject is DistributedLog. Regards, Dave Sent from my iPhone > On Nov 5, 2019, at 11:50 AM, Alan Gates wrote: > > Omid[1] and Tephra[2] have voted to join the Phoenix community as > sub-projects. Phoenix has voted to accept them[3]. Per the instructions > at [4], this email is notice of that. Unless any objections are raised in > 72 hours the graduation will be considered accepted and both podlings will > move ahead with the details. > > Alan. > > 1. > https://lists.apache.org/thread.html/d996692f30b30eea68c1e8db3c5095d6eb4877f7b358e401851130b2@%3Cdev.omid.apache.org%3E > 2. > https://lists.apache.org/thread.html/33487013c347fe15f43a55cc2281613e1cce4f0cd07d27280ddad9bb@%3Cdev.tephra.apache.org%3E > 3. > https://lists.apache.org/thread.html/29111aa8b59fe38ca11d6ca2f029009c437ed6986d6dcf2fb6fc5b2f@%3Cdev.phoenix.apache.org%3E > 4. > https://incubator.apache.org/guides/graduation.html#graduating_to_a_subproject - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Omid and Tephra
https://svn.apache.org/repos/private/documents/grants/caskdata-tephra On Wed, 30 Oct 2019 at 15:16, Alan Gates wrote: > > Regarding SGAs, here's the JIRA for Omid: > https://issues.apache.org/jira/browse/OMID-2 > According to > https://svn.apache.org/repos/private/foundation/officers/grants.txt Cask > (original creators of Tephra) submitted a SGA for it and it's one file, but > I don't know where the referenced file is kept. > > Alan. > > On Wed, Oct 30, 2019 at 10:32 AM Alan Gates wrote: > > > Bertand, thanks for bringing this up. I'll chase those down. > > > > Alan. > > > > On Wed, Oct 30, 2019 at 8:46 AM Bertrand Delacretaz < > > bdelacre...@codeconsult.ch> wrote: > > > >> Hi, > >> > >> On Wed, Oct 30, 2019 at 3:55 PM Josh Elser wrote: > >> > ...My current expectation is that we'd just rename the existing Git > >> > repositories and change the LDAP group which are used to determine write > >> > access... > >> > >> From the Incubator's point of view, I think an additional step is to > >> confirm and document if any Software Grants were needed for these > >> projects code and if yes if they've been filed as needed. > >> > >> This can be just a jira or other ticket documenting the move and > >> including this info. > >> > >> -Bertrand > >> > >> - > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >> For additional commands, e-mail: general-h...@incubator.apache.org > >> > >> -- Matt Sicker - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Omid and Tephra
Regarding SGAs, here's the JIRA for Omid: https://issues.apache.org/jira/browse/OMID-2 According to https://svn.apache.org/repos/private/foundation/officers/grants.txt Cask (original creators of Tephra) submitted a SGA for it and it's one file, but I don't know where the referenced file is kept. Alan. On Wed, Oct 30, 2019 at 10:32 AM Alan Gates wrote: > Bertand, thanks for bringing this up. I'll chase those down. > > Alan. > > On Wed, Oct 30, 2019 at 8:46 AM Bertrand Delacretaz < > bdelacre...@codeconsult.ch> wrote: > >> Hi, >> >> On Wed, Oct 30, 2019 at 3:55 PM Josh Elser wrote: >> > ...My current expectation is that we'd just rename the existing Git >> > repositories and change the LDAP group which are used to determine write >> > access... >> >> From the Incubator's point of view, I think an additional step is to >> confirm and document if any Software Grants were needed for these >> projects code and if yes if they've been filed as needed. >> >> This can be just a jira or other ticket documenting the move and >> including this info. >> >> -Bertrand >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >>
Re: Omid and Tephra
Bertand, thanks for bringing this up. I'll chase those down. Alan. On Wed, Oct 30, 2019 at 8:46 AM Bertrand Delacretaz < bdelacre...@codeconsult.ch> wrote: > Hi, > > On Wed, Oct 30, 2019 at 3:55 PM Josh Elser wrote: > > ...My current expectation is that we'd just rename the existing Git > > repositories and change the LDAP group which are used to determine write > > access... > > From the Incubator's point of view, I think an additional step is to > confirm and document if any Software Grants were needed for these > projects code and if yes if they've been filed as needed. > > This can be just a jira or other ticket documenting the move and > including this info. > > -Bertrand > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: Omid and Tephra
Hi, On Wed, Oct 30, 2019 at 3:55 PM Josh Elser wrote: > ...My current expectation is that we'd just rename the existing Git > repositories and change the LDAP group which are used to determine write > access... >From the Incubator's point of view, I think an additional step is to confirm and document if any Software Grants were needed for these projects code and if yes if they've been filed as needed. This can be just a jira or other ticket documenting the move and including this info. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Omid and Tephra
I like the idea of opt-in for committership for the current podling membership (without any "time to respond" limitation). I don't foresee any concerns doing that, but will shout if that becomes an issue. On 10/28/19 3:09 PM, Justin Mclean wrote: Hi, According to [4] the first step of graduating into a sub-project of an existing TLP is a vote by the podling. Given that both podlings have very low activity I am not sure we will get the necessary votes to make this happen. I would try and see what happens - the mentors have binding votes so hopefully they will vote. If we don’t get enough votes or if someone raises an objection we’ll decide what to do then. One question that I'd like to see resolved as part of this vote is what status Phoenix plans to grant to Tephra and Omid committers and PPMC members. I would ask all PPMC and committers if they want to be part of Phoenix PMC/committers and grant those who reply. But if the Phoenix PMC has other ideas they could also be considered. If someone at a later point decides to “opt-in” you may want to consider that as well. Thanks, Justin - 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: Omid and Tephra
(w/ VP Phoenix hat) My current expectation is that we'd just rename the existing Git repositories and change the LDAP group which are used to determine write access. In other words, your Git repos will exist just as they do now, but only at different coordinates. On 10/25/19 12:27 AM, Ohad Shacham wrote: +1, Thanks Alan. Just wanted to verify that adopt means Omid and Tephra will sit in the same repo as Phoenix but will be able to checkout separately as well. I assume this is Phoenix folks decision. I know that in Yahoo Omid is used internally. On Fri, Oct 25, 2019 at 2:36 AM Gary Helmling wrote: +1 this seems like the best option. On Thu, Oct 24, 2019 at 2:29 PM Andrew Purtell wrote: +1 this would be a good outcome. Both Tephra and OMID are good technologies, with respective pros and cons, and Phoenix can make good use of both of them, should they choose to accept ownership of the code. On Wed, Oct 23, 2019 at 11:26 AM Alan Gates wrote: Justin and mentors of Omid and Tephra, As Justin noted in his emails to these podlings this month both are very low activity, struggling to even file their reports, and appear to be candidates for retirement. The situation here is somewhat special because Phoenix uses one or both of these technologies (they are both transaction managers on top of HBase), so they may have an interest in their continued survival. Tephra briefly discussed this last June[1], though nothing came of it. My conclusion is there is not enough momentum left for these podlings to vote themselves into Phoenix without an external push. So before we push them into retirement I believe we should involve the Phoenix PMC and see if they want to adopt either or both of these, with the knowledge that they will likely be getting minimal contributions from current members of those projects going forward. If others are ok with this I can contact the Phoenix PMC and see if they wish to take any action on this. Alan. 1. https://lists.apache.org/thread.html/87ace080ef8a967b238781979a8d9a0cb9607ac4a195d5937756ec66@%3Cdev.tephra.apache.org%3E -- Best regards, Andrew Words like orphans lost among the crosstalk, meaning torn from truth's decrepit hands - A23, Crosstalk - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Omid and Tephra
Makes sense. I've replied to the discussion in the Phoenix community so we know what terms Tephra and Omid are voting on. As soon as I hear from them I'll start votes in both communities. Alan. On Tue, Oct 29, 2019 at 3:47 PM Andreas Neumann wrote: > I agree with Justin, I think we get - at least in the Tephra community - a > quorum. > -Andreas > > On Mon, Oct 28, 2019 at 12:09 PM Justin Mclean > wrote: > > > Hi, > > > > > According to [4] the first step of graduating into a sub-project of an > > > existing TLP is a vote by the podling. Given that both podlings have > > very > > > low activity I am not sure we will get the necessary votes to make this > > > happen. > > > > I would try and see what happens - the mentors have binding votes so > > hopefully they will vote. If we don’t get enough votes or if someone > raises > > an objection we’ll decide what to do then. > > > > > One question that I'd like to see resolved as part of this vote > > > is what status Phoenix plans to grant to Tephra and Omid committers and > > > PPMC members. > > > > I would ask all PPMC and committers if they want to be part of Phoenix > > PMC/committers and grant those who reply. But if the Phoenix PMC has > other > > ideas they could also be considered. > > > > If someone at a later point decides to “opt-in” you may want to consider > > that as well. > > > > Thanks, > > Justin > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > >
Re: Omid and Tephra
I agree with Justin, I think we get - at least in the Tephra community - a quorum. -Andreas On Mon, Oct 28, 2019 at 12:09 PM Justin Mclean wrote: > Hi, > > > According to [4] the first step of graduating into a sub-project of an > > existing TLP is a vote by the podling. Given that both podlings have > very > > low activity I am not sure we will get the necessary votes to make this > > happen. > > I would try and see what happens - the mentors have binding votes so > hopefully they will vote. If we don’t get enough votes or if someone raises > an objection we’ll decide what to do then. > > > One question that I'd like to see resolved as part of this vote > > is what status Phoenix plans to grant to Tephra and Omid committers and > > PPMC members. > > I would ask all PPMC and committers if they want to be part of Phoenix > PMC/committers and grant those who reply. But if the Phoenix PMC has other > ideas they could also be considered. > > If someone at a later point decides to “opt-in” you may want to consider > that as well. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: Omid and Tephra
Hi, > According to [4] the first step of graduating into a sub-project of an > existing TLP is a vote by the podling. Given that both podlings have very > low activity I am not sure we will get the necessary votes to make this > happen. I would try and see what happens - the mentors have binding votes so hopefully they will vote. If we don’t get enough votes or if someone raises an objection we’ll decide what to do then. > One question that I'd like to see resolved as part of this vote > is what status Phoenix plans to grant to Tephra and Omid committers and > PPMC members. I would ask all PPMC and committers if they want to be part of Phoenix PMC/committers and grant those who reply. But if the Phoenix PMC has other ideas they could also be considered. If someone at a later point decides to “opt-in” you may want to consider that as well. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Omid and Tephra
There appears to be consensus on this thread, as well as in the Phoenix community[1] that it makes sense for Phoenix to adopt both Omid and Tephra. My mails to the Tephra and Omid communities[2][3] have gone unanswered, so I assume silence implies consent. According to [4] the first step of graduating into a sub-project of an existing TLP is a vote by the podling. Given that both podlings have very low activity I am not sure we will get the necessary votes to make this happen. I can start the vote threads in each podling, but I believe we should be ready to move forward without these votes passing due to lack of participation. The next step is for the Phoenix PMC to formally vote to accept the podlings. One question that I'd like to see resolved as part of this vote is what status Phoenix plans to grant to Tephra and Omid committers and PPMC members. Normally I would expect that all podling committers become TLP committers, but given the low participation it may make sense for Phoenix to use an opt-in where podling committers need to affirm their desire to continue on the project before being made committers. Alan. 1. https://lists.apache.org/thread.html/ec00615cbbb4225885e3776f1e8fd071600a9c50f35769f453b8a779@%3Cdev.phoenix.apache.org%3E 2. https://lists.apache.org/thread.html/21deb9e6fe0e929af38b9b712cc0a0779b170f6617b6dee21cfbc356@%3Cdev.tephra.apache.org%3E 3. https://lists.apache.org/thread.html/3fda8fe4517e7d78e4a38b75cce0d77e4514529d50249c190fcb3bda@%3Cdev.omid.apache.org%3E 4. https://incubator.apache.org/guides/graduation.html#graduating_to_a_subproject On Fri, Oct 25, 2019 at 10:35 AM Ohad Shacham wrote: > +1, Thanks Alan. > Just wanted to verify that adopt means Omid and Tephra will sit in the same > repo as Phoenix but will be able to checkout separately as well. I assume > this is Phoenix folks decision. > I know that in Yahoo Omid is used internally. > > On Fri, Oct 25, 2019 at 2:36 AM Gary Helmling wrote: > > > +1 this seems like the best option. > > > > On Thu, Oct 24, 2019 at 2:29 PM Andrew Purtell > > wrote: > > > > > +1 this would be a good outcome. Both Tephra and OMID are good > > > technologies, with respective pros and cons, and Phoenix can make good > > use > > > of both of them, should they choose to accept ownership of the code. > > > > > > On Wed, Oct 23, 2019 at 11:26 AM Alan Gates > > wrote: > > > > > > > Justin and mentors of Omid and Tephra, > > > > > > > > As Justin noted in his emails to these podlings this month both are > > very > > > > low activity, struggling to even file their reports, and appear to be > > > > candidates for retirement. > > > > > > > > The situation here is somewhat special because Phoenix uses one or > both > > > of > > > > these technologies (they are both transaction managers on top of > > HBase), > > > so > > > > they may have an interest in their continued survival. Tephra > briefly > > > > discussed this last June[1], though nothing came of it. My > conclusion > > is > > > > there is not enough momentum left for these podlings to vote > themselves > > > > into Phoenix without an external push. > > > > > > > > So before we push them into retirement I believe we should involve > the > > > > Phoenix PMC and see if they want to adopt either or both of these, > with > > > the > > > > knowledge that they will likely be getting minimal contributions from > > > > current members of those projects going forward. If others are ok > with > > > > this I can contact the Phoenix PMC and see if they wish to take any > > > action > > > > on this. > > > > > > > > Alan. > > > > > > > > 1. > > > > > > > > > > > > > > https://lists.apache.org/thread.html/87ace080ef8a967b238781979a8d9a0cb9607ac4a195d5937756ec66@%3Cdev.tephra.apache.org%3E > > > > > > > > > > > > > -- > > > Best regards, > > > Andrew > > > > > > Words like orphans lost among the crosstalk, meaning torn from truth's > > > decrepit hands > > >- A23, Crosstalk > > > > > >
Re: Omid and Tephra
+1, Thanks Alan. Just wanted to verify that adopt means Omid and Tephra will sit in the same repo as Phoenix but will be able to checkout separately as well. I assume this is Phoenix folks decision. I know that in Yahoo Omid is used internally. On Fri, Oct 25, 2019 at 2:36 AM Gary Helmling wrote: > +1 this seems like the best option. > > On Thu, Oct 24, 2019 at 2:29 PM Andrew Purtell > wrote: > > > +1 this would be a good outcome. Both Tephra and OMID are good > > technologies, with respective pros and cons, and Phoenix can make good > use > > of both of them, should they choose to accept ownership of the code. > > > > On Wed, Oct 23, 2019 at 11:26 AM Alan Gates > wrote: > > > > > Justin and mentors of Omid and Tephra, > > > > > > As Justin noted in his emails to these podlings this month both are > very > > > low activity, struggling to even file their reports, and appear to be > > > candidates for retirement. > > > > > > The situation here is somewhat special because Phoenix uses one or both > > of > > > these technologies (they are both transaction managers on top of > HBase), > > so > > > they may have an interest in their continued survival. Tephra briefly > > > discussed this last June[1], though nothing came of it. My conclusion > is > > > there is not enough momentum left for these podlings to vote themselves > > > into Phoenix without an external push. > > > > > > So before we push them into retirement I believe we should involve the > > > Phoenix PMC and see if they want to adopt either or both of these, with > > the > > > knowledge that they will likely be getting minimal contributions from > > > current members of those projects going forward. If others are ok with > > > this I can contact the Phoenix PMC and see if they wish to take any > > action > > > on this. > > > > > > Alan. > > > > > > 1. > > > > > > > > > https://lists.apache.org/thread.html/87ace080ef8a967b238781979a8d9a0cb9607ac4a195d5937756ec66@%3Cdev.tephra.apache.org%3E > > > > > > > > > -- > > Best regards, > > Andrew > > > > Words like orphans lost among the crosstalk, meaning torn from truth's > > decrepit hands > >- A23, Crosstalk > > >
Re: Omid and Tephra
+1 this seems like the best option. On Thu, Oct 24, 2019 at 2:29 PM Andrew Purtell wrote: > +1 this would be a good outcome. Both Tephra and OMID are good > technologies, with respective pros and cons, and Phoenix can make good use > of both of them, should they choose to accept ownership of the code. > > On Wed, Oct 23, 2019 at 11:26 AM Alan Gates wrote: > > > Justin and mentors of Omid and Tephra, > > > > As Justin noted in his emails to these podlings this month both are very > > low activity, struggling to even file their reports, and appear to be > > candidates for retirement. > > > > The situation here is somewhat special because Phoenix uses one or both > of > > these technologies (they are both transaction managers on top of HBase), > so > > they may have an interest in their continued survival. Tephra briefly > > discussed this last June[1], though nothing came of it. My conclusion is > > there is not enough momentum left for these podlings to vote themselves > > into Phoenix without an external push. > > > > So before we push them into retirement I believe we should involve the > > Phoenix PMC and see if they want to adopt either or both of these, with > the > > knowledge that they will likely be getting minimal contributions from > > current members of those projects going forward. If others are ok with > > this I can contact the Phoenix PMC and see if they wish to take any > action > > on this. > > > > Alan. > > > > 1. > > > > > https://lists.apache.org/thread.html/87ace080ef8a967b238781979a8d9a0cb9607ac4a195d5937756ec66@%3Cdev.tephra.apache.org%3E > > > > > -- > Best regards, > Andrew > > Words like orphans lost among the crosstalk, meaning torn from truth's > decrepit hands >- A23, Crosstalk >
Re: Omid and Tephra
+1 this would be a good outcome. Both Tephra and OMID are good technologies, with respective pros and cons, and Phoenix can make good use of both of them, should they choose to accept ownership of the code. On Wed, Oct 23, 2019 at 11:26 AM Alan Gates wrote: > Justin and mentors of Omid and Tephra, > > As Justin noted in his emails to these podlings this month both are very > low activity, struggling to even file their reports, and appear to be > candidates for retirement. > > The situation here is somewhat special because Phoenix uses one or both of > these technologies (they are both transaction managers on top of HBase), so > they may have an interest in their continued survival. Tephra briefly > discussed this last June[1], though nothing came of it. My conclusion is > there is not enough momentum left for these podlings to vote themselves > into Phoenix without an external push. > > So before we push them into retirement I believe we should involve the > Phoenix PMC and see if they want to adopt either or both of these, with the > knowledge that they will likely be getting minimal contributions from > current members of those projects going forward. If others are ok with > this I can contact the Phoenix PMC and see if they wish to take any action > on this. > > Alan. > > 1. > > https://lists.apache.org/thread.html/87ace080ef8a967b238781979a8d9a0cb9607ac4a195d5937756ec66@%3Cdev.tephra.apache.org%3E > -- Best regards, Andrew Words like orphans lost among the crosstalk, meaning torn from truth's decrepit hands - A23, Crosstalk
Re: Omid and Tephra
On 2019/10/23 18:16:31, Alan Gates wrote: > Justin and mentors of Omid and Tephra, > > As Justin noted in his emails to these podlings this month both are very > low activity, struggling to even file their reports, and appear to be > candidates for retirement. > > The situation here is somewhat special because Phoenix uses one or both of > these technologies (they are both transaction managers on top of HBase), so > they may have an interest in their continued survival. Tephra briefly > discussed this last June[1], though nothing came of it. My conclusion is > there is not enough momentum left for these podlings to vote themselves > into Phoenix without an external push. > > So before we push them into retirement I believe we should involve the > Phoenix PMC and see if they want to adopt either or both of these, with the > knowledge that they will likely be getting minimal contributions from > current members of those projects going forward. If others are ok with > this I can contact the Phoenix PMC and see if they wish to take any action > on this. > > Alan. > > 1. > https://lists.apache.org/thread.html/87ace080ef8a967b238781979a8d9a0cb9607ac4a195d5937756ec66@%3Cdev.tephra.apache.org%3E > +1 Looks like a good idea to me - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Omid and Tephra
Hi, > So before we push them into retirement I believe we should involve the > Phoenix PMC and see if they want to adopt either or both of these, with the > knowledge that they will likely be getting minimal contributions from > current members of those projects going forward. If others are ok with > this I can contact the Phoenix PMC and see if they wish to take any action > on this. Sounds like an excellent plan. +1 Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Omid and Tephra
+1 It seems to be the best option. -Andreas On Thu, Oct 24, 2019 at 6:47 AM Furkan KAMACI wrote: > Hi, > > +1 > > Kind Regards, > Furkan KAMACI > > 24 Eki 2019 Per, saat 07:11 tarihinde Jean-Baptiste Onofré < > j...@nanthrax.net> > şunu yazdı: > > > +1, good idea. > > > > Regards > > JB > > > > On 23/10/2019 20:16, Alan Gates wrote: > > > Justin and mentors of Omid and Tephra, > > > > > > As Justin noted in his emails to these podlings this month both are > very > > > low activity, struggling to even file their reports, and appear to be > > > candidates for retirement. > > > > > > The situation here is somewhat special because Phoenix uses one or both > > of > > > these technologies (they are both transaction managers on top of > HBase), > > so > > > they may have an interest in their continued survival. Tephra briefly > > > discussed this last June[1], though nothing came of it. My conclusion > is > > > there is not enough momentum left for these podlings to vote themselves > > > into Phoenix without an external push. > > > > > > So before we push them into retirement I believe we should involve the > > > Phoenix PMC and see if they want to adopt either or both of these, with > > the > > > knowledge that they will likely be getting minimal contributions from > > > current members of those projects going forward. If others are ok with > > > this I can contact the Phoenix PMC and see if they wish to take any > > action > > > on this. > > > > > > Alan. > > > > > > 1. > > > > > > https://lists.apache.org/thread.html/87ace080ef8a967b238781979a8d9a0cb9607ac4a195d5937756ec66@%3Cdev.tephra.apache.org%3E > > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > >
Re: Omid and Tephra
Hi, +1 Kind Regards, Furkan KAMACI 24 Eki 2019 Per, saat 07:11 tarihinde Jean-Baptiste Onofré şunu yazdı: > +1, good idea. > > Regards > JB > > On 23/10/2019 20:16, Alan Gates wrote: > > Justin and mentors of Omid and Tephra, > > > > As Justin noted in his emails to these podlings this month both are very > > low activity, struggling to even file their reports, and appear to be > > candidates for retirement. > > > > The situation here is somewhat special because Phoenix uses one or both > of > > these technologies (they are both transaction managers on top of HBase), > so > > they may have an interest in their continued survival. Tephra briefly > > discussed this last June[1], though nothing came of it. My conclusion is > > there is not enough momentum left for these podlings to vote themselves > > into Phoenix without an external push. > > > > So before we push them into retirement I believe we should involve the > > Phoenix PMC and see if they want to adopt either or both of these, with > the > > knowledge that they will likely be getting minimal contributions from > > current members of those projects going forward. If others are ok with > > this I can contact the Phoenix PMC and see if they wish to take any > action > > on this. > > > > Alan. > > > > 1. > > > https://lists.apache.org/thread.html/87ace080ef8a967b238781979a8d9a0cb9607ac4a195d5937756ec66@%3Cdev.tephra.apache.org%3E > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: Omid and Tephra
+1, good idea. Regards JB On 23/10/2019 20:16, Alan Gates wrote: Justin and mentors of Omid and Tephra, As Justin noted in his emails to these podlings this month both are very low activity, struggling to even file their reports, and appear to be candidates for retirement. The situation here is somewhat special because Phoenix uses one or both of these technologies (they are both transaction managers on top of HBase), so they may have an interest in their continued survival. Tephra briefly discussed this last June[1], though nothing came of it. My conclusion is there is not enough momentum left for these podlings to vote themselves into Phoenix without an external push. So before we push them into retirement I believe we should involve the Phoenix PMC and see if they want to adopt either or both of these, with the knowledge that they will likely be getting minimal contributions from current members of those projects going forward. If others are ok with this I can contact the Phoenix PMC and see if they wish to take any action on this. Alan. 1. https://lists.apache.org/thread.html/87ace080ef8a967b238781979a8d9a0cb9607ac4a195d5937756ec66@%3Cdev.tephra.apache.org%3E - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Omid and Tephra
+1. That seems like the best course of action IMHO. On Wed, Oct 23, 2019 at 12:54 PM Flavio Junqueira wrote: > +1 > > -Flavio > > > On 23 Oct 2019, at 21:08, Terence Yim wrote: > > > > +1 on this > > > > On Wed, Oct 23, 2019 at 11:36 Dave Fisher wrote: > > > >> +1. That’s a good idea. > >> > >> Sent from my iPhone > >> > >>> On Oct 23, 2019, at 11:26 AM, Alan Gates wrote: > >>> > >>> Justin and mentors of Omid and Tephra, > >>> > >>> As Justin noted in his emails to these podlings this month both are > very > >>> low activity, struggling to even file their reports, and appear to be > >>> candidates for retirement. > >>> > >>> The situation here is somewhat special because Phoenix uses one or both > >> of > >>> these technologies (they are both transaction managers on top of > HBase), > >> so > >>> they may have an interest in their continued survival. Tephra briefly > >>> discussed this last June[1], though nothing came of it. My conclusion > is > >>> there is not enough momentum left for these podlings to vote themselves > >>> into Phoenix without an external push. > >>> > >>> So before we push them into retirement I believe we should involve the > >>> Phoenix PMC and see if they want to adopt either or both of these, with > >> the > >>> knowledge that they will likely be getting minimal contributions from > >>> current members of those projects going forward. If others are ok with > >>> this I can contact the Phoenix PMC and see if they wish to take any > >> action > >>> on this. > >>> > >>> Alan. > >>> > >>> 1. > >>> > >> > https://lists.apache.org/thread.html/87ace080ef8a967b238781979a8d9a0cb9607ac4a195d5937756ec66@%3Cdev.tephra.apache.org%3E > >> > >> > >> - > >> 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: Omid and Tephra
+1 -Flavio > On 23 Oct 2019, at 21:08, Terence Yim wrote: > > +1 on this > > On Wed, Oct 23, 2019 at 11:36 Dave Fisher wrote: > >> +1. That’s a good idea. >> >> Sent from my iPhone >> >>> On Oct 23, 2019, at 11:26 AM, Alan Gates wrote: >>> >>> Justin and mentors of Omid and Tephra, >>> >>> As Justin noted in his emails to these podlings this month both are very >>> low activity, struggling to even file their reports, and appear to be >>> candidates for retirement. >>> >>> The situation here is somewhat special because Phoenix uses one or both >> of >>> these technologies (they are both transaction managers on top of HBase), >> so >>> they may have an interest in their continued survival. Tephra briefly >>> discussed this last June[1], though nothing came of it. My conclusion is >>> there is not enough momentum left for these podlings to vote themselves >>> into Phoenix without an external push. >>> >>> So before we push them into retirement I believe we should involve the >>> Phoenix PMC and see if they want to adopt either or both of these, with >> the >>> knowledge that they will likely be getting minimal contributions from >>> current members of those projects going forward. If others are ok with >>> this I can contact the Phoenix PMC and see if they wish to take any >> action >>> on this. >>> >>> Alan. >>> >>> 1. >>> >> https://lists.apache.org/thread.html/87ace080ef8a967b238781979a8d9a0cb9607ac4a195d5937756ec66@%3Cdev.tephra.apache.org%3E >> >> >> - >> 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: Omid and Tephra
+1 on this On Wed, Oct 23, 2019 at 11:36 Dave Fisher wrote: > +1. That’s a good idea. > > Sent from my iPhone > > > On Oct 23, 2019, at 11:26 AM, Alan Gates wrote: > > > > Justin and mentors of Omid and Tephra, > > > > As Justin noted in his emails to these podlings this month both are very > > low activity, struggling to even file their reports, and appear to be > > candidates for retirement. > > > > The situation here is somewhat special because Phoenix uses one or both > of > > these technologies (they are both transaction managers on top of HBase), > so > > they may have an interest in their continued survival. Tephra briefly > > discussed this last June[1], though nothing came of it. My conclusion is > > there is not enough momentum left for these podlings to vote themselves > > into Phoenix without an external push. > > > > So before we push them into retirement I believe we should involve the > > Phoenix PMC and see if they want to adopt either or both of these, with > the > > knowledge that they will likely be getting minimal contributions from > > current members of those projects going forward. If others are ok with > > this I can contact the Phoenix PMC and see if they wish to take any > action > > on this. > > > > Alan. > > > > 1. > > > https://lists.apache.org/thread.html/87ace080ef8a967b238781979a8d9a0cb9607ac4a195d5937756ec66@%3Cdev.tephra.apache.org%3E > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: Omid and Tephra
+1. That’s a good idea. Sent from my iPhone > On Oct 23, 2019, at 11:26 AM, Alan Gates wrote: > > Justin and mentors of Omid and Tephra, > > As Justin noted in his emails to these podlings this month both are very > low activity, struggling to even file their reports, and appear to be > candidates for retirement. > > The situation here is somewhat special because Phoenix uses one or both of > these technologies (they are both transaction managers on top of HBase), so > they may have an interest in their continued survival. Tephra briefly > discussed this last June[1], though nothing came of it. My conclusion is > there is not enough momentum left for these podlings to vote themselves > into Phoenix without an external push. > > So before we push them into retirement I believe we should involve the > Phoenix PMC and see if they want to adopt either or both of these, with the > knowledge that they will likely be getting minimal contributions from > current members of those projects going forward. If others are ok with > this I can contact the Phoenix PMC and see if they wish to take any action > on this. > > Alan. > > 1. > https://lists.apache.org/thread.html/87ace080ef8a967b238781979a8d9a0cb9607ac4a195d5937756ec66@%3Cdev.tephra.apache.org%3E - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
