Re: [DISCUSS] Dormant/Inactive KIPs

2017-01-05 Thread Grant Henke
Thanks for following up on this Ismael!

On Thu, Jan 5, 2017 at 6:46 AM, Ismael Juma  wrote:

> Thanks for the feedback. I went ahead and moved the mentioned KIPs as well
> as KIP-59, KIP-64, KIP-69 and KIP-76 to a dormant/inactive table. Note that
> this is not a permanent change, people are welcome to move a KIP back to
> the "Under discussion" table if it's not inactive/dormant.
>
> Ismael
>
> On Tue, Dec 13, 2016 at 11:53 AM, Ismael Juma  wrote:
>
> > Hi all,
> >
> > A while back Grant proposed moving inactive/dormant KIPs to a separate
> > table in the wiki. I think this is a good idea as it will make it easier
> > for people to see the KIPs that are actually active. The list that Grant
> > proposed then was:
> >
> > - KIP-6 - New reassignment partition logic for rebalancing (dormant)
> >> - KIP-14 - Tools standardization (dormant)
> >> - KIP-17 - Add HighwaterMarkOffset to OffsetFetchResponse (dormant)
> >> - KIP-18 - JBOD Support (dormant)
> >> - KIP-23 - Add JSON/CSV output and looping options to
> ConsumerGroupCommand
> >> (dormant)
> >> - KIP-27 - Conditional Publish (dormant)
> >>  - KIP-30 - Allow for brokers to have plug-able consensus and meta data
> storage
> >> sub systems (dormant)
> >>  - KIP-39: Pinning controller to broker (dormant)
> >>  - KIP-44 - Allow Kafka to have a customized security protocol (dormant)
> >>  - KIP-46 - Self Healing (dormant)
> >>  - KIP-47 - Add timestamp-based log deletion policy (blocked - by
> KIP-33)
> >>  - KIP-53 - Add custom policies for reconnect attempts to NetworkdClient
> >>  - KIP-58 - Make Log Compaction Point Configurable (blocked - by KIP-33)
> >>  - KIP-61: Add a log retention parameter for maximum disk space usage
> >>percentage (dormant)
> >>  - KIP-68 Add a consumed log retention before log retention (dormant)
> >
> >
> > KIP-58 was adopted since then and it probably makes sense to add KIP-10
> to
> > the list.
> >
> > Are people OK with this? Feel free to suggest KIPs that should or should
> > not be in the inactive/dormant list.
> >
> > Ismael
> >
>



-- 
Grant Henke
Software Engineer | Cloudera
gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke


Re: [DISCUSS] Dormant/Inactive KIPs

2017-01-05 Thread Ismael Juma
Thanks for the feedback. I went ahead and moved the mentioned KIPs as well
as KIP-59, KIP-64, KIP-69 and KIP-76 to a dormant/inactive table. Note that
this is not a permanent change, people are welcome to move a KIP back to
the "Under discussion" table if it's not inactive/dormant.

Ismael

On Tue, Dec 13, 2016 at 11:53 AM, Ismael Juma  wrote:

> Hi all,
>
> A while back Grant proposed moving inactive/dormant KIPs to a separate
> table in the wiki. I think this is a good idea as it will make it easier
> for people to see the KIPs that are actually active. The list that Grant
> proposed then was:
>
> - KIP-6 - New reassignment partition logic for rebalancing (dormant)
>> - KIP-14 - Tools standardization (dormant)
>> - KIP-17 - Add HighwaterMarkOffset to OffsetFetchResponse (dormant)
>> - KIP-18 - JBOD Support (dormant)
>> - KIP-23 - Add JSON/CSV output and looping options to ConsumerGroupCommand
>> (dormant)
>> - KIP-27 - Conditional Publish (dormant)
>>  - KIP-30 - Allow for brokers to have plug-able consensus and meta data 
>> storage
>> sub systems (dormant)
>>  - KIP-39: Pinning controller to broker (dormant)
>>  - KIP-44 - Allow Kafka to have a customized security protocol (dormant)
>>  - KIP-46 - Self Healing (dormant)
>>  - KIP-47 - Add timestamp-based log deletion policy (blocked - by KIP-33)
>>  - KIP-53 - Add custom policies for reconnect attempts to NetworkdClient
>>  - KIP-58 - Make Log Compaction Point Configurable (blocked - by KIP-33)
>>  - KIP-61: Add a log retention parameter for maximum disk space usage
>>percentage (dormant)
>>  - KIP-68 Add a consumed log retention before log retention (dormant)
>
>
> KIP-58 was adopted since then and it probably makes sense to add KIP-10 to
> the list.
>
> Are people OK with this? Feel free to suggest KIPs that should or should
> not be in the inactive/dormant list.
>
> Ismael
>


Re: [DISCUSS] Dormant/Inactive KIPs

2017-01-03 Thread Guozhang Wang
+1 as well.

On Tue, Jan 3, 2017 at 11:43 AM, Neha Narkhede  wrote:

> +1. This is a good idea as we have a lot of KIPs in flight.
>
> On Tue, Dec 13, 2016 at 3:53 AM Ismael Juma  wrote:
>
> > Hi all,
> >
> > A while back Grant proposed moving inactive/dormant KIPs to a separate
> > table in the wiki. I think this is a good idea as it will make it easier
> > for people to see the KIPs that are actually active. The list that Grant
> > proposed then was:
> >
> > - KIP-6 - New reassignment partition logic for rebalancing (dormant)
> > > - KIP-14 - Tools standardization (dormant)
> > > - KIP-17 - Add HighwaterMarkOffset to OffsetFetchResponse (dormant)
> > > - KIP-18 - JBOD Support (dormant)
> > > - KIP-23 - Add JSON/CSV output and looping options to
> > ConsumerGroupCommand
> > > (dormant)
> > > - KIP-27 - Conditional Publish (dormant)
> > >  - KIP-30 - Allow for brokers to have plug-able consensus and meta data
> > storage
> > > sub systems (dormant)
> > >  - KIP-39: Pinning controller to broker (dormant)
> > >  - KIP-44 - Allow Kafka to have a customized security protocol
> (dormant)
> > >  - KIP-46 - Self Healing (dormant)
> > >  - KIP-47 - Add timestamp-based log deletion policy (blocked - by
> KIP-33)
> > >  - KIP-53 - Add custom policies for reconnect attempts to
> NetworkdClient
> > >  - KIP-58 - Make Log Compaction Point Configurable (blocked - by
> KIP-33)
> > >  - KIP-61: Add a log retention parameter for maximum disk space usage
> > >percentage (dormant)
> > >  - KIP-68 Add a consumed log retention before log retention (dormant)
> >
> >
> > KIP-58 was adopted since then and it probably makes sense to add KIP-10
> to
> > the list.
> >
> > Are people OK with this? Feel free to suggest KIPs that should or should
> > not be in the inactive/dormant list.
> >
> > Ismael
> >
> --
> Thanks,
> Neha
>



-- 
-- Guozhang


Re: [DISCUSS] Dormant/Inactive KIPs

2017-01-03 Thread Neha Narkhede
+1. This is a good idea as we have a lot of KIPs in flight.

On Tue, Dec 13, 2016 at 3:53 AM Ismael Juma  wrote:

> Hi all,
>
> A while back Grant proposed moving inactive/dormant KIPs to a separate
> table in the wiki. I think this is a good idea as it will make it easier
> for people to see the KIPs that are actually active. The list that Grant
> proposed then was:
>
> - KIP-6 - New reassignment partition logic for rebalancing (dormant)
> > - KIP-14 - Tools standardization (dormant)
> > - KIP-17 - Add HighwaterMarkOffset to OffsetFetchResponse (dormant)
> > - KIP-18 - JBOD Support (dormant)
> > - KIP-23 - Add JSON/CSV output and looping options to
> ConsumerGroupCommand
> > (dormant)
> > - KIP-27 - Conditional Publish (dormant)
> >  - KIP-30 - Allow for brokers to have plug-able consensus and meta data
> storage
> > sub systems (dormant)
> >  - KIP-39: Pinning controller to broker (dormant)
> >  - KIP-44 - Allow Kafka to have a customized security protocol (dormant)
> >  - KIP-46 - Self Healing (dormant)
> >  - KIP-47 - Add timestamp-based log deletion policy (blocked - by KIP-33)
> >  - KIP-53 - Add custom policies for reconnect attempts to NetworkdClient
> >  - KIP-58 - Make Log Compaction Point Configurable (blocked - by KIP-33)
> >  - KIP-61: Add a log retention parameter for maximum disk space usage
> >percentage (dormant)
> >  - KIP-68 Add a consumed log retention before log retention (dormant)
>
>
> KIP-58 was adopted since then and it probably makes sense to add KIP-10 to
> the list.
>
> Are people OK with this? Feel free to suggest KIPs that should or should
> not be in the inactive/dormant list.
>
> Ismael
>
-- 
Thanks,
Neha


[DISCUSS] Dormant/Inactive KIPs

2016-12-13 Thread Ismael Juma
Hi all,

A while back Grant proposed moving inactive/dormant KIPs to a separate
table in the wiki. I think this is a good idea as it will make it easier
for people to see the KIPs that are actually active. The list that Grant
proposed then was:

- KIP-6 - New reassignment partition logic for rebalancing (dormant)
> - KIP-14 - Tools standardization (dormant)
> - KIP-17 - Add HighwaterMarkOffset to OffsetFetchResponse (dormant)
> - KIP-18 - JBOD Support (dormant)
> - KIP-23 - Add JSON/CSV output and looping options to ConsumerGroupCommand
> (dormant)
> - KIP-27 - Conditional Publish (dormant)
>  - KIP-30 - Allow for brokers to have plug-able consensus and meta data 
> storage
> sub systems (dormant)
>  - KIP-39: Pinning controller to broker (dormant)
>  - KIP-44 - Allow Kafka to have a customized security protocol (dormant)
>  - KIP-46 - Self Healing (dormant)
>  - KIP-47 - Add timestamp-based log deletion policy (blocked - by KIP-33)
>  - KIP-53 - Add custom policies for reconnect attempts to NetworkdClient
>  - KIP-58 - Make Log Compaction Point Configurable (blocked - by KIP-33)
>  - KIP-61: Add a log retention parameter for maximum disk space usage
>percentage (dormant)
>  - KIP-68 Add a consumed log retention before log retention (dormant)


KIP-58 was adopted since then and it probably makes sense to add KIP-10 to
the list.

Are people OK with this? Feel free to suggest KIPs that should or should
not be in the inactive/dormant list.

Ismael