[RESULT] [VOTE] Accept DistributedLog into the Apache Incubator

[Sijie Guo]

The results are in and voting is now closed. The votes were ...

[15] +1 Accept DistributedLog into the Apache Incubator

Sijie Guo
Jia Zhai
Naresh Agarwal
Debo Dutta
Tsuyoshi (ozawa@)
Flavio Junqueira (binding)
Chris Douglas (binding)
Henry Saputra (binding)
Josh Elser (binding)
Mahak Patidar
Dave Rusek
Stevo Slavic
Chris Nauroth (binding)
Suneel Marthi (binding)
Jakob Homan (binding)

[0] +0 Abstain.
[0] -1 Do not accept DistributedLog into the Apache Incubator because ...

DistributedLog has been accepted into the Incubator!

Thanks everyone who took time to look at the project and vote!

The vote thread can be found there:

http://mail-archives.apache.org/mod_mbox/incubator-general/201606.mbox/%3CCAO2yDyamYeMZ892GdwjxGn_J-WKgUcOLqfudA4YyU4nqZVmaKA%40mail.gmail.com%3E


-- Forwarded message --
From: Sijie Guo <si...@apache.org>
Date: Mon, Jun 20, 2016 at 10:11 PM
Subject: [VOTE] Accept DistributedLog into the Apache Incubator
To: general@incubator.apache.org


Hello All,

Following the discussion thread, I would like to call a VOTE on accepting
DistributedLog into the Apache Incubator.

[] +1 Accept DistributedLog into the Apache Incubator
[] +0 Abstain.
[] -1 Do not accept DistributedLog into the Apache Incubator because ...

This vote will be open for at least 72 hours.

The proposal follows, you can also access the wiki page:
https://wiki.apache.org/incubator/DistributedLogProposal

Here is my +1.

Thanks,
Sijie

= Abstract =
DistributedLog is a high-performance replicated log service. It offers
durability, replication and strong consistency, which provides a
fundamental building block for building reliable distributed systems, e.g
replicated-state-machines, general pub/sub systems, distributed databases,
distributed queues and etc.

See “Building Distributedlog - Twitter’s high performance replicated log
service” for details:
https://blog.twitter.com/2015/building-distributedlog-twitter-s-high-performance-replicated-log-service

= Proposal =
We propose to contribute DistributedLog codebase and associated artifacts
(e.g. documentation, web-site content etc.) to the Apache Software
Foundation with the intent of forming a productive, meritocratic and open
community around DistributedLog’s continued development, according to the
‘Apache Way’.

= Background =
Engineers at Twitter began developing DistributedLog in early 2013.
DistributedLog is described in a Twitter engineering blog post and
presented at the Messaging Meetup in Sep 2015. It has been released as an
Apache-licensed open-source project on GitHub in May 2016.

DistributedLog is a high-performance replicated log service, which provides
simple stream-oriented abstractions over log-segments and offers
durability, replication and strong consistency for building reliable
distributed systems. The features offered by DistributedLog includes:

 * Simple high-level, stream oriented interface
 * Naming and metadata scheme for managing streams and other entities
 * Log data management policies, include data segmentation and data
retention
 * Fast write pipeline leveraging batching and compression
 * Fast read mechanism leveraging long-poll and read-ahead caching
 * Service tiers supporting writer fan-in and reader fan-out
 * Geo-replicated logs

DistributedLog’s most important benefit is high-performance with a strong
durability guarantee, making it extremely appropriate for running different
workloads from distributed database journaling to real-time stream
computing. Its modern, layered architecture makes it easy to run the
service tiers in multi-tenant datacenter environments such as Apache Mesos
or cloud environments such as EC2.

= Rationale =
DistributedLog is designed to provide core fundamental features like
high-performance, durability and strong consistency to anyone who is
building reliable distributed systems, in a simple and efficient way.

We believe that the ASF is the right venue to foster an open-source
community around DistributedLog’s development. We expect that
DistributedLog will benefit from collaboration with related Apache
projects, and under the auspices of the ASF will attract talented
contributors who will push DistributedLog’s development forward at a faster
pace.

We believe that the timing is right for DistributedLog’s development to
move to the ASF: DistributedLog has already run in production at Twitter
for 3 years and served various workloads including a distributed database
journal, reliable cross datacenter replication, search ingestion,
andgeneral pub/sub messaging. The project is stable. We are excited to see
where an ASF-based community can take DistributedLog.

= Current Status =
DistributedLog is a stable project that has been used in production at
Twitter for 3 years. The source code is public at github.com/twitter, which
will seed the Apache git repository.

= Meritocracy =
We understand the central importance of meritocracy to the Apache Way. We
will work to establish a welcoming

Re: [VOTE] Accept DistributedLog into the Apache Incubator

[Jakob Homan]

+1 (binding)
-jg


On 22 June 2016 at 09:45, Suneel Marthi  wrote:
> +1 (binding)
>
> On Tue, Jun 21, 2016 at 1:11 AM, Sijie Guo  wrote:
>
>> Hello All,
>>
>> Following the discussion thread, I would like to call a VOTE on accepting
>> DistributedLog into the Apache Incubator.
>>
>> [] +1 Accept DistributedLog into the Apache Incubator
>> [] +0 Abstain.
>> [] -1 Do not accept DistributedLog into the Apache Incubator because ...
>>
>> This vote will be open for at least 72 hours.
>>
>> The proposal follows, you can also access the wiki page:
>> https://wiki.apache.org/incubator/DistributedLogProposal
>>
>> Here is my +1.
>>
>> Thanks,
>> Sijie
>>
>> = Abstract =
>> DistributedLog is a high-performance replicated log service. It offers
>> durability, replication and strong consistency, which provides a
>> fundamental building block for building reliable distributed systems, e.g
>> replicated-state-machines, general pub/sub systems, distributed databases,
>> distributed queues and etc.
>>
>> See “Building Distributedlog - Twitter’s high performance replicated log
>> service” for details:
>>
>> https://blog.twitter.com/2015/building-distributedlog-twitter-s-high-performance-replicated-log-service
>>
>> = Proposal =
>> We propose to contribute DistributedLog codebase and associated artifacts
>> (e.g. documentation, web-site content etc.) to the Apache Software
>> Foundation with the intent of forming a productive, meritocratic and open
>> community around DistributedLog’s continued development, according to the
>> ‘Apache Way’.
>>
>> = Background =
>> Engineers at Twitter began developing DistributedLog in early 2013.
>> DistributedLog is described in a Twitter engineering blog post and
>> presented at the Messaging Meetup in Sep 2015. It has been released as an
>> Apache-licensed open-source project on GitHub in May 2016.
>>
>> DistributedLog is a high-performance replicated log service, which provides
>> simple stream-oriented abstractions over log-segments and offers
>> durability, replication and strong consistency for building reliable
>> distributed systems. The features offered by DistributedLog includes:
>>
>>  * Simple high-level, stream oriented interface
>>  * Naming and metadata scheme for managing streams and other entities
>>  * Log data management policies, include data segmentation and data
>> retention
>>  * Fast write pipeline leveraging batching and compression
>>  * Fast read mechanism leveraging long-poll and read-ahead caching
>>  * Service tiers supporting writer fan-in and reader fan-out
>>  * Geo-replicated logs
>>
>> DistributedLog’s most important benefit is high-performance with a strong
>> durability guarantee, making it extremely appropriate for running different
>> workloads from distributed database journaling to real-time stream
>> computing. Its modern, layered architecture makes it easy to run the
>> service tiers in multi-tenant datacenter environments such as Apache Mesos
>> or cloud environments such as EC2.
>>
>> = Rationale =
>> DistributedLog is designed to provide core fundamental features like
>> high-performance, durability and strong consistency to anyone who is
>> building reliable distributed systems, in a simple and efficient way.
>>
>> We believe that the ASF is the right venue to foster an open-source
>> community around DistributedLog’s development. We expect that
>> DistributedLog will benefit from collaboration with related Apache
>> projects, and under the auspices of the ASF will attract talented
>> contributors who will push DistributedLog’s development forward at a faster
>> pace.
>>
>> We believe that the timing is right for DistributedLog’s development to
>> move to the ASF: DistributedLog has already run in production at Twitter
>> for 3 years and served various workloads including a distributed database
>> journal, reliable cross datacenter replication, search ingestion,
>> andgeneral pub/sub messaging. The project is stable. We are excited to see
>> where an ASF-based community can take DistributedLog.
>>
>> = Current Status =
>> DistributedLog is a stable project that has been used in production at
>> Twitter for 3 years. The source code is public at github.com/twitter,
>> which
>> will seed the Apache git repository.
>>
>> = Meritocracy =
>> We understand the central importance of meritocracy to the Apache Way. We
>> will work to establish a welcoming, fair and meritocratic community.
>> Several companies have already expressed interest in this project, and we
>> intend to invite additional developers to participate. We look forward to
>> growing a rich user and developer community.
>>
>> = Community =
>> There is a large need for a performant replicated log service for
>> applications such as distributed databases, distributed transactional
>> systems, replicated-state-machines and pub/sub messaging/queuing. We want
>> to attract more developers to the project, and we believe that the ASF’s
>> open and 

Re: [VOTE] Accept DistributedLog into the Apache Incubator

[Suneel Marthi]

+1 (binding)

On Tue, Jun 21, 2016 at 1:11 AM, Sijie Guo  wrote:

> Hello All,
>
> Following the discussion thread, I would like to call a VOTE on accepting
> DistributedLog into the Apache Incubator.
>
> [] +1 Accept DistributedLog into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept DistributedLog into the Apache Incubator because ...
>
> This vote will be open for at least 72 hours.
>
> The proposal follows, you can also access the wiki page:
> https://wiki.apache.org/incubator/DistributedLogProposal
>
> Here is my +1.
>
> Thanks,
> Sijie
>
> = Abstract =
> DistributedLog is a high-performance replicated log service. It offers
> durability, replication and strong consistency, which provides a
> fundamental building block for building reliable distributed systems, e.g
> replicated-state-machines, general pub/sub systems, distributed databases,
> distributed queues and etc.
>
> See “Building Distributedlog - Twitter’s high performance replicated log
> service” for details:
>
> https://blog.twitter.com/2015/building-distributedlog-twitter-s-high-performance-replicated-log-service
>
> = Proposal =
> We propose to contribute DistributedLog codebase and associated artifacts
> (e.g. documentation, web-site content etc.) to the Apache Software
> Foundation with the intent of forming a productive, meritocratic and open
> community around DistributedLog’s continued development, according to the
> ‘Apache Way’.
>
> = Background =
> Engineers at Twitter began developing DistributedLog in early 2013.
> DistributedLog is described in a Twitter engineering blog post and
> presented at the Messaging Meetup in Sep 2015. It has been released as an
> Apache-licensed open-source project on GitHub in May 2016.
>
> DistributedLog is a high-performance replicated log service, which provides
> simple stream-oriented abstractions over log-segments and offers
> durability, replication and strong consistency for building reliable
> distributed systems. The features offered by DistributedLog includes:
>
>  * Simple high-level, stream oriented interface
>  * Naming and metadata scheme for managing streams and other entities
>  * Log data management policies, include data segmentation and data
> retention
>  * Fast write pipeline leveraging batching and compression
>  * Fast read mechanism leveraging long-poll and read-ahead caching
>  * Service tiers supporting writer fan-in and reader fan-out
>  * Geo-replicated logs
>
> DistributedLog’s most important benefit is high-performance with a strong
> durability guarantee, making it extremely appropriate for running different
> workloads from distributed database journaling to real-time stream
> computing. Its modern, layered architecture makes it easy to run the
> service tiers in multi-tenant datacenter environments such as Apache Mesos
> or cloud environments such as EC2.
>
> = Rationale =
> DistributedLog is designed to provide core fundamental features like
> high-performance, durability and strong consistency to anyone who is
> building reliable distributed systems, in a simple and efficient way.
>
> We believe that the ASF is the right venue to foster an open-source
> community around DistributedLog’s development. We expect that
> DistributedLog will benefit from collaboration with related Apache
> projects, and under the auspices of the ASF will attract talented
> contributors who will push DistributedLog’s development forward at a faster
> pace.
>
> We believe that the timing is right for DistributedLog’s development to
> move to the ASF: DistributedLog has already run in production at Twitter
> for 3 years and served various workloads including a distributed database
> journal, reliable cross datacenter replication, search ingestion,
> andgeneral pub/sub messaging. The project is stable. We are excited to see
> where an ASF-based community can take DistributedLog.
>
> = Current Status =
> DistributedLog is a stable project that has been used in production at
> Twitter for 3 years. The source code is public at github.com/twitter,
> which
> will seed the Apache git repository.
>
> = Meritocracy =
> We understand the central importance of meritocracy to the Apache Way. We
> will work to establish a welcoming, fair and meritocratic community.
> Several companies have already expressed interest in this project, and we
> intend to invite additional developers to participate. We look forward to
> growing a rich user and developer community.
>
> = Community =
> There is a large need for a performant replicated log service for
> applications such as distributed databases, distributed transactional
> systems, replicated-state-machines and pub/sub messaging/queuing. We want
> to attract more developers to the project, and we believe that the ASF’s
> open and meritocratic philosophy will help us with this. We note the
> success of other similar projects already part of the ASF, like Kafka.
>
> = Core Developers =
> DistributedLog is actively developed within 

Re: [VOTE] Accept DistributedLog into the Apache Incubator

[Chris Nauroth]

+1 (binding)

--Chris Nauroth




On 6/20/16, 10:11 PM, "Sijie Guo"  wrote:

>Hello All,
>
>Following the discussion thread, I would like to call a VOTE on accepting
>DistributedLog into the Apache Incubator.
>
>[] +1 Accept DistributedLog into the Apache Incubator
>[] +0 Abstain.
>[] -1 Do not accept DistributedLog into the Apache Incubator because ...
>
>This vote will be open for at least 72 hours.
>
>The proposal follows, you can also access the wiki page:
>https://wiki.apache.org/incubator/DistributedLogProposal
>
>Here is my +1.
>
>Thanks,
>Sijie
>
>= Abstract =
>DistributedLog is a high-performance replicated log service. It offers
>durability, replication and strong consistency, which provides a
>fundamental building block for building reliable distributed systems, e.g
>replicated-state-machines, general pub/sub systems, distributed databases,
>distributed queues and etc.
>
>See ³Building Distributedlog - Twitter¹s high performance replicated log
>service² for details:
>https://blog.twitter.com/2015/building-distributedlog-twitter-s-high-perfo
>rmance-replicated-log-service
>
>= Proposal =
>We propose to contribute DistributedLog codebase and associated artifacts
>(e.g. documentation, web-site content etc.) to the Apache Software
>Foundation with the intent of forming a productive, meritocratic and open
>community around DistributedLog¹s continued development, according to the
>ŒApache Way¹.
>
>= Background =
>Engineers at Twitter began developing DistributedLog in early 2013.
>DistributedLog is described in a Twitter engineering blog post and
>presented at the Messaging Meetup in Sep 2015. It has been released as an
>Apache-licensed open-source project on GitHub in May 2016.
>
>DistributedLog is a high-performance replicated log service, which
>provides
>simple stream-oriented abstractions over log-segments and offers
>durability, replication and strong consistency for building reliable
>distributed systems. The features offered by DistributedLog includes:
>
> * Simple high-level, stream oriented interface
> * Naming and metadata scheme for managing streams and other entities
> * Log data management policies, include data segmentation and data
>retention
> * Fast write pipeline leveraging batching and compression
> * Fast read mechanism leveraging long-poll and read-ahead caching
> * Service tiers supporting writer fan-in and reader fan-out
> * Geo-replicated logs
>
>DistributedLog¹s most important benefit is high-performance with a strong
>durability guarantee, making it extremely appropriate for running
>different
>workloads from distributed database journaling to real-time stream
>computing. Its modern, layered architecture makes it easy to run the
>service tiers in multi-tenant datacenter environments such as Apache Mesos
>or cloud environments such as EC2.
>
>= Rationale =
>DistributedLog is designed to provide core fundamental features like
>high-performance, durability and strong consistency to anyone who is
>building reliable distributed systems, in a simple and efficient way.
>
>We believe that the ASF is the right venue to foster an open-source
>community around DistributedLog¹s development. We expect that
>DistributedLog will benefit from collaboration with related Apache
>projects, and under the auspices of the ASF will attract talented
>contributors who will push DistributedLog¹s development forward at a
>faster
>pace.
>
>We believe that the timing is right for DistributedLog¹s development to
>move to the ASF: DistributedLog has already run in production at Twitter
>for 3 years and served various workloads including a distributed database
>journal, reliable cross datacenter replication, search ingestion,
>andgeneral pub/sub messaging. The project is stable. We are excited to see
>where an ASF-based community can take DistributedLog.
>
>= Current Status =
>DistributedLog is a stable project that has been used in production at
>Twitter for 3 years. The source code is public at github.com/twitter,
>which
>will seed the Apache git repository.
>
>= Meritocracy =
>We understand the central importance of meritocracy to the Apache Way. We
>will work to establish a welcoming, fair and meritocratic community.
>Several companies have already expressed interest in this project, and we
>intend to invite additional developers to participate. We look forward to
>growing a rich user and developer community.
>
>= Community =
>There is a large need for a performant replicated log service for
>applications such as distributed databases, distributed transactional
>systems, replicated-state-machines and pub/sub messaging/queuing. We want
>to attract more developers to the project, and we believe that the ASF¹s
>open and meritocratic philosophy will help us with this. We note the
>success of other similar projects already part of the ASF, like Kafka.
>
>= Core Developers =
>DistributedLog is actively developed within Twitter. Most of the
>developers
>are from Twitter. Many of them are 

Re: [VOTE] Accept DistributedLog into the Apache Incubator

[Stevo Slavić]

+1 (non-binding)

On Wed, Jun 22, 2016 at 5:41 PM, Dave Rusek 
wrote:

> +1
>
> On Tue, Jun 21, 2016 at 9:49 PM, Mahak Patidar  wrote:
>
> > +1
> > On Jun 21, 2016 7:06 PM, "Josh Elser"  wrote:
> >
> > > +1 (binding)
> > >
> > > Good luck!
> > >
> > > Sijie Guo wrote:
> > >
> > >> Hello All,
> > >>
> > >> Following the discussion thread, I would like to call a VOTE on
> > accepting
> > >> DistributedLog into the Apache Incubator.
> > >>
> > >> [] +1 Accept DistributedLog into the Apache Incubator
> > >> [] +0 Abstain.
> > >> [] -1 Do not accept DistributedLog into the Apache Incubator because
> ...
> > >>
> > >> This vote will be open for at least 72 hours.
> > >>
> > >> The proposal follows, you can also access the wiki page:
> > >> https://wiki.apache.org/incubator/DistributedLogProposal
> > >>
> > >> Here is my +1.
> > >>
> > >> Thanks,
> > >> Sijie
> > >>
> > >> = Abstract =
> > >> DistributedLog is a high-performance replicated log service. It offers
> > >> durability, replication and strong consistency, which provides a
> > >> fundamental building block for building reliable distributed systems,
> > e.g
> > >> replicated-state-machines, general pub/sub systems, distributed
> > databases,
> > >> distributed queues and etc.
> > >>
> > >> See “Building Distributedlog - Twitter’s high performance replicated
> log
> > >> service” for details:
> > >>
> > >>
> >
> https://blog.twitter.com/2015/building-distributedlog-twitter-s-high-performance-replicated-log-service
> > >>
> > >> = Proposal =
> > >> We propose to contribute DistributedLog codebase and associated
> > artifacts
> > >> (e.g. documentation, web-site content etc.) to the Apache Software
> > >> Foundation with the intent of forming a productive, meritocratic and
> > open
> > >> community around DistributedLog’s continued development, according to
> > the
> > >> ‘Apache Way’.
> > >>
> > >> = Background =
> > >> Engineers at Twitter began developing DistributedLog in early 2013.
> > >> DistributedLog is described in a Twitter engineering blog post and
> > >> presented at the Messaging Meetup in Sep 2015. It has been released as
> > an
> > >> Apache-licensed open-source project on GitHub in May 2016.
> > >>
> > >> DistributedLog is a high-performance replicated log service, which
> > >> provides
> > >> simple stream-oriented abstractions over log-segments and offers
> > >> durability, replication and strong consistency for building reliable
> > >> distributed systems. The features offered by DistributedLog includes:
> > >>
> > >>   * Simple high-level, stream oriented interface
> > >>   * Naming and metadata scheme for managing streams and other entities
> > >>   * Log data management policies, include data segmentation and data
> > >> retention
> > >>   * Fast write pipeline leveraging batching and compression
> > >>   * Fast read mechanism leveraging long-poll and read-ahead caching
> > >>   * Service tiers supporting writer fan-in and reader fan-out
> > >>   * Geo-replicated logs
> > >>
> > >> DistributedLog’s most important benefit is high-performance with a
> > strong
> > >> durability guarantee, making it extremely appropriate for running
> > >> different
> > >> workloads from distributed database journaling to real-time stream
> > >> computing. Its modern, layered architecture makes it easy to run the
> > >> service tiers in multi-tenant datacenter environments such as Apache
> > Mesos
> > >> or cloud environments such as EC2.
> > >>
> > >> = Rationale =
> > >> DistributedLog is designed to provide core fundamental features like
> > >> high-performance, durability and strong consistency to anyone who is
> > >> building reliable distributed systems, in a simple and efficient way.
> > >>
> > >> We believe that the ASF is the right venue to foster an open-source
> > >> community around DistributedLog’s development. We expect that
> > >> DistributedLog will benefit from collaboration with related Apache
> > >> projects, and under the auspices of the ASF will attract talented
> > >> contributors who will push DistributedLog’s development forward at a
> > >> faster
> > >> pace.
> > >>
> > >> We believe that the timing is right for DistributedLog’s development
> to
> > >> move to the ASF: DistributedLog has already run in production at
> Twitter
> > >> for 3 years and served various workloads including a distributed
> > database
> > >> journal, reliable cross datacenter replication, search ingestion,
> > >> andgeneral pub/sub messaging. The project is stable. We are excited to
> > see
> > >> where an ASF-based community can take DistributedLog.
> > >>
> > >> = Current Status =
> > >> DistributedLog is a stable project that has been used in production at
> > >> Twitter for 3 years. The source code is public at github.com/twitter,
> > >> which
> > >> will seed the Apache git repository.
> > >>
> > >> = Meritocracy =
> > >> We understand the central importance of meritocracy to the 

Re: [VOTE] Accept DistributedLog into the Apache Incubator

[Dave Rusek]

+1

On Tue, Jun 21, 2016 at 9:49 PM, Mahak Patidar  wrote:

> +1
> On Jun 21, 2016 7:06 PM, "Josh Elser"  wrote:
>
> > +1 (binding)
> >
> > Good luck!
> >
> > Sijie Guo wrote:
> >
> >> Hello All,
> >>
> >> Following the discussion thread, I would like to call a VOTE on
> accepting
> >> DistributedLog into the Apache Incubator.
> >>
> >> [] +1 Accept DistributedLog into the Apache Incubator
> >> [] +0 Abstain.
> >> [] -1 Do not accept DistributedLog into the Apache Incubator because ...
> >>
> >> This vote will be open for at least 72 hours.
> >>
> >> The proposal follows, you can also access the wiki page:
> >> https://wiki.apache.org/incubator/DistributedLogProposal
> >>
> >> Here is my +1.
> >>
> >> Thanks,
> >> Sijie
> >>
> >> = Abstract =
> >> DistributedLog is a high-performance replicated log service. It offers
> >> durability, replication and strong consistency, which provides a
> >> fundamental building block for building reliable distributed systems,
> e.g
> >> replicated-state-machines, general pub/sub systems, distributed
> databases,
> >> distributed queues and etc.
> >>
> >> See “Building Distributedlog - Twitter’s high performance replicated log
> >> service” for details:
> >>
> >>
> https://blog.twitter.com/2015/building-distributedlog-twitter-s-high-performance-replicated-log-service
> >>
> >> = Proposal =
> >> We propose to contribute DistributedLog codebase and associated
> artifacts
> >> (e.g. documentation, web-site content etc.) to the Apache Software
> >> Foundation with the intent of forming a productive, meritocratic and
> open
> >> community around DistributedLog’s continued development, according to
> the
> >> ‘Apache Way’.
> >>
> >> = Background =
> >> Engineers at Twitter began developing DistributedLog in early 2013.
> >> DistributedLog is described in a Twitter engineering blog post and
> >> presented at the Messaging Meetup in Sep 2015. It has been released as
> an
> >> Apache-licensed open-source project on GitHub in May 2016.
> >>
> >> DistributedLog is a high-performance replicated log service, which
> >> provides
> >> simple stream-oriented abstractions over log-segments and offers
> >> durability, replication and strong consistency for building reliable
> >> distributed systems. The features offered by DistributedLog includes:
> >>
> >>   * Simple high-level, stream oriented interface
> >>   * Naming and metadata scheme for managing streams and other entities
> >>   * Log data management policies, include data segmentation and data
> >> retention
> >>   * Fast write pipeline leveraging batching and compression
> >>   * Fast read mechanism leveraging long-poll and read-ahead caching
> >>   * Service tiers supporting writer fan-in and reader fan-out
> >>   * Geo-replicated logs
> >>
> >> DistributedLog’s most important benefit is high-performance with a
> strong
> >> durability guarantee, making it extremely appropriate for running
> >> different
> >> workloads from distributed database journaling to real-time stream
> >> computing. Its modern, layered architecture makes it easy to run the
> >> service tiers in multi-tenant datacenter environments such as Apache
> Mesos
> >> or cloud environments such as EC2.
> >>
> >> = Rationale =
> >> DistributedLog is designed to provide core fundamental features like
> >> high-performance, durability and strong consistency to anyone who is
> >> building reliable distributed systems, in a simple and efficient way.
> >>
> >> We believe that the ASF is the right venue to foster an open-source
> >> community around DistributedLog’s development. We expect that
> >> DistributedLog will benefit from collaboration with related Apache
> >> projects, and under the auspices of the ASF will attract talented
> >> contributors who will push DistributedLog’s development forward at a
> >> faster
> >> pace.
> >>
> >> We believe that the timing is right for DistributedLog’s development to
> >> move to the ASF: DistributedLog has already run in production at Twitter
> >> for 3 years and served various workloads including a distributed
> database
> >> journal, reliable cross datacenter replication, search ingestion,
> >> andgeneral pub/sub messaging. The project is stable. We are excited to
> see
> >> where an ASF-based community can take DistributedLog.
> >>
> >> = Current Status =
> >> DistributedLog is a stable project that has been used in production at
> >> Twitter for 3 years. The source code is public at github.com/twitter,
> >> which
> >> will seed the Apache git repository.
> >>
> >> = Meritocracy =
> >> We understand the central importance of meritocracy to the Apache Way.
> We
> >> will work to establish a welcoming, fair and meritocratic community.
> >> Several companies have already expressed interest in this project, and
> we
> >> intend to invite additional developers to participate. We look forward
> to
> >> growing a rich user and developer community.
> >>
> >> = Community =
> >> There is a large 

Re: [VOTE] Accept DistributedLog into the Apache Incubator

[Mahak Patidar]

+1
On Jun 21, 2016 7:06 PM, "Josh Elser"  wrote:

> +1 (binding)
>
> Good luck!
>
> Sijie Guo wrote:
>
>> Hello All,
>>
>> Following the discussion thread, I would like to call a VOTE on accepting
>> DistributedLog into the Apache Incubator.
>>
>> [] +1 Accept DistributedLog into the Apache Incubator
>> [] +0 Abstain.
>> [] -1 Do not accept DistributedLog into the Apache Incubator because ...
>>
>> This vote will be open for at least 72 hours.
>>
>> The proposal follows, you can also access the wiki page:
>> https://wiki.apache.org/incubator/DistributedLogProposal
>>
>> Here is my +1.
>>
>> Thanks,
>> Sijie
>>
>> = Abstract =
>> DistributedLog is a high-performance replicated log service. It offers
>> durability, replication and strong consistency, which provides a
>> fundamental building block for building reliable distributed systems, e.g
>> replicated-state-machines, general pub/sub systems, distributed databases,
>> distributed queues and etc.
>>
>> See “Building Distributedlog - Twitter’s high performance replicated log
>> service” for details:
>>
>> https://blog.twitter.com/2015/building-distributedlog-twitter-s-high-performance-replicated-log-service
>>
>> = Proposal =
>> We propose to contribute DistributedLog codebase and associated artifacts
>> (e.g. documentation, web-site content etc.) to the Apache Software
>> Foundation with the intent of forming a productive, meritocratic and open
>> community around DistributedLog’s continued development, according to the
>> ‘Apache Way’.
>>
>> = Background =
>> Engineers at Twitter began developing DistributedLog in early 2013.
>> DistributedLog is described in a Twitter engineering blog post and
>> presented at the Messaging Meetup in Sep 2015. It has been released as an
>> Apache-licensed open-source project on GitHub in May 2016.
>>
>> DistributedLog is a high-performance replicated log service, which
>> provides
>> simple stream-oriented abstractions over log-segments and offers
>> durability, replication and strong consistency for building reliable
>> distributed systems. The features offered by DistributedLog includes:
>>
>>   * Simple high-level, stream oriented interface
>>   * Naming and metadata scheme for managing streams and other entities
>>   * Log data management policies, include data segmentation and data
>> retention
>>   * Fast write pipeline leveraging batching and compression
>>   * Fast read mechanism leveraging long-poll and read-ahead caching
>>   * Service tiers supporting writer fan-in and reader fan-out
>>   * Geo-replicated logs
>>
>> DistributedLog’s most important benefit is high-performance with a strong
>> durability guarantee, making it extremely appropriate for running
>> different
>> workloads from distributed database journaling to real-time stream
>> computing. Its modern, layered architecture makes it easy to run the
>> service tiers in multi-tenant datacenter environments such as Apache Mesos
>> or cloud environments such as EC2.
>>
>> = Rationale =
>> DistributedLog is designed to provide core fundamental features like
>> high-performance, durability and strong consistency to anyone who is
>> building reliable distributed systems, in a simple and efficient way.
>>
>> We believe that the ASF is the right venue to foster an open-source
>> community around DistributedLog’s development. We expect that
>> DistributedLog will benefit from collaboration with related Apache
>> projects, and under the auspices of the ASF will attract talented
>> contributors who will push DistributedLog’s development forward at a
>> faster
>> pace.
>>
>> We believe that the timing is right for DistributedLog’s development to
>> move to the ASF: DistributedLog has already run in production at Twitter
>> for 3 years and served various workloads including a distributed database
>> journal, reliable cross datacenter replication, search ingestion,
>> andgeneral pub/sub messaging. The project is stable. We are excited to see
>> where an ASF-based community can take DistributedLog.
>>
>> = Current Status =
>> DistributedLog is a stable project that has been used in production at
>> Twitter for 3 years. The source code is public at github.com/twitter,
>> which
>> will seed the Apache git repository.
>>
>> = Meritocracy =
>> We understand the central importance of meritocracy to the Apache Way. We
>> will work to establish a welcoming, fair and meritocratic community.
>> Several companies have already expressed interest in this project, and we
>> intend to invite additional developers to participate. We look forward to
>> growing a rich user and developer community.
>>
>> = Community =
>> There is a large need for a performant replicated log service for
>> applications such as distributed databases, distributed transactional
>> systems, replicated-state-machines and pub/sub messaging/queuing. We want
>> to attract more developers to the project, and we believe that the ASF’s
>> open and meritocratic philosophy will help us with 

Re: [VOTE] Accept DistributedLog into the Apache Incubator

[Josh Elser]

+1 (binding)

Good luck!

Sijie Guo wrote:

Hello All,

Following the discussion thread, I would like to call a VOTE on accepting
DistributedLog into the Apache Incubator.

[] +1 Accept DistributedLog into the Apache Incubator
[] +0 Abstain.
[] -1 Do not accept DistributedLog into the Apache Incubator because ...

This vote will be open for at least 72 hours.

The proposal follows, you can also access the wiki page:
https://wiki.apache.org/incubator/DistributedLogProposal

Here is my +1.

Thanks,
Sijie

= Abstract =
DistributedLog is a high-performance replicated log service. It offers
durability, replication and strong consistency, which provides a
fundamental building block for building reliable distributed systems, e.g
replicated-state-machines, general pub/sub systems, distributed databases,
distributed queues and etc.

See “Building Distributedlog - Twitter’s high performance replicated log
service” for details:
https://blog.twitter.com/2015/building-distributedlog-twitter-s-high-performance-replicated-log-service

= Proposal =
We propose to contribute DistributedLog codebase and associated artifacts
(e.g. documentation, web-site content etc.) to the Apache Software
Foundation with the intent of forming a productive, meritocratic and open
community around DistributedLog’s continued development, according to the
‘Apache Way’.

= Background =
Engineers at Twitter began developing DistributedLog in early 2013.
DistributedLog is described in a Twitter engineering blog post and
presented at the Messaging Meetup in Sep 2015. It has been released as an
Apache-licensed open-source project on GitHub in May 2016.

DistributedLog is a high-performance replicated log service, which provides
simple stream-oriented abstractions over log-segments and offers
durability, replication and strong consistency for building reliable
distributed systems. The features offered by DistributedLog includes:

  * Simple high-level, stream oriented interface
  * Naming and metadata scheme for managing streams and other entities
  * Log data management policies, include data segmentation and data
retention
  * Fast write pipeline leveraging batching and compression
  * Fast read mechanism leveraging long-poll and read-ahead caching
  * Service tiers supporting writer fan-in and reader fan-out
  * Geo-replicated logs

DistributedLog’s most important benefit is high-performance with a strong
durability guarantee, making it extremely appropriate for running different
workloads from distributed database journaling to real-time stream
computing. Its modern, layered architecture makes it easy to run the
service tiers in multi-tenant datacenter environments such as Apache Mesos
or cloud environments such as EC2.

= Rationale =
DistributedLog is designed to provide core fundamental features like
high-performance, durability and strong consistency to anyone who is
building reliable distributed systems, in a simple and efficient way.

We believe that the ASF is the right venue to foster an open-source
community around DistributedLog’s development. We expect that
DistributedLog will benefit from collaboration with related Apache
projects, and under the auspices of the ASF will attract talented
contributors who will push DistributedLog’s development forward at a faster
pace.

We believe that the timing is right for DistributedLog’s development to
move to the ASF: DistributedLog has already run in production at Twitter
for 3 years and served various workloads including a distributed database
journal, reliable cross datacenter replication, search ingestion,
andgeneral pub/sub messaging. The project is stable. We are excited to see
where an ASF-based community can take DistributedLog.

= Current Status =
DistributedLog is a stable project that has been used in production at
Twitter for 3 years. The source code is public at github.com/twitter, which
will seed the Apache git repository.

= Meritocracy =
We understand the central importance of meritocracy to the Apache Way. We
will work to establish a welcoming, fair and meritocratic community.
Several companies have already expressed interest in this project, and we
intend to invite additional developers to participate. We look forward to
growing a rich user and developer community.

= Community =
There is a large need for a performant replicated log service for
applications such as distributed databases, distributed transactional
systems, replicated-state-machines and pub/sub messaging/queuing. We want
to attract more developers to the project, and we believe that the ASF’s
open and meritocratic philosophy will help us with this. We note the
success of other similar projects already part of the ASF, like Kafka.

= Core Developers =
DistributedLog is actively developed within Twitter. Most of the developers
are from Twitter. Many of them are committers or PMC members of Apache
BookKeeper. Others aren’t currently affiliated with ASF so they will
require new ICLAs.

= Alignment =
DistributedLog is 

Re: [VOTE] Accept DistributedLog into the Apache Incubator

[Henry Saputra]

+1 (binding)

On Tue, Jun 21, 2016 at 12:11 PM, Sijie Guo  wrote:

> Hello All,
>
> Following the discussion thread, I would like to call a VOTE on accepting
> DistributedLog into the Apache Incubator.
>
> [] +1 Accept DistributedLog into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept DistributedLog into the Apache Incubator because ...
>
> This vote will be open for at least 72 hours.
>
> The proposal follows, you can also access the wiki page:
> https://wiki.apache.org/incubator/DistributedLogProposal
>
> Here is my +1.
>
> Thanks,
> Sijie
>
> = Abstract =
> DistributedLog is a high-performance replicated log service. It offers
> durability, replication and strong consistency, which provides a
> fundamental building block for building reliable distributed systems, e.g
> replicated-state-machines, general pub/sub systems, distributed databases,
> distributed queues and etc.
>
> See “Building Distributedlog - Twitter’s high performance replicated log
> service” for details:
>
> https://blog.twitter.com/2015/building-distributedlog-twitter-s-high-performance-replicated-log-service
>
> = Proposal =
> We propose to contribute DistributedLog codebase and associated artifacts
> (e.g. documentation, web-site content etc.) to the Apache Software
> Foundation with the intent of forming a productive, meritocratic and open
> community around DistributedLog’s continued development, according to the
> ‘Apache Way’.
>
> = Background =
> Engineers at Twitter began developing DistributedLog in early 2013.
> DistributedLog is described in a Twitter engineering blog post and
> presented at the Messaging Meetup in Sep 2015. It has been released as an
> Apache-licensed open-source project on GitHub in May 2016.
>
> DistributedLog is a high-performance replicated log service, which provides
> simple stream-oriented abstractions over log-segments and offers
> durability, replication and strong consistency for building reliable
> distributed systems. The features offered by DistributedLog includes:
>
>  * Simple high-level, stream oriented interface
>  * Naming and metadata scheme for managing streams and other entities
>  * Log data management policies, include data segmentation and data
> retention
>  * Fast write pipeline leveraging batching and compression
>  * Fast read mechanism leveraging long-poll and read-ahead caching
>  * Service tiers supporting writer fan-in and reader fan-out
>  * Geo-replicated logs
>
> DistributedLog’s most important benefit is high-performance with a strong
> durability guarantee, making it extremely appropriate for running different
> workloads from distributed database journaling to real-time stream
> computing. Its modern, layered architecture makes it easy to run the
> service tiers in multi-tenant datacenter environments such as Apache Mesos
> or cloud environments such as EC2.
>
> = Rationale =
> DistributedLog is designed to provide core fundamental features like
> high-performance, durability and strong consistency to anyone who is
> building reliable distributed systems, in a simple and efficient way.
>
> We believe that the ASF is the right venue to foster an open-source
> community around DistributedLog’s development. We expect that
> DistributedLog will benefit from collaboration with related Apache
> projects, and under the auspices of the ASF will attract talented
> contributors who will push DistributedLog’s development forward at a faster
> pace.
>
> We believe that the timing is right for DistributedLog’s development to
> move to the ASF: DistributedLog has already run in production at Twitter
> for 3 years and served various workloads including a distributed database
> journal, reliable cross datacenter replication, search ingestion,
> andgeneral pub/sub messaging. The project is stable. We are excited to see
> where an ASF-based community can take DistributedLog.
>
> = Current Status =
> DistributedLog is a stable project that has been used in production at
> Twitter for 3 years. The source code is public at github.com/twitter,
> which
> will seed the Apache git repository.
>
> = Meritocracy =
> We understand the central importance of meritocracy to the Apache Way. We
> will work to establish a welcoming, fair and meritocratic community.
> Several companies have already expressed interest in this project, and we
> intend to invite additional developers to participate. We look forward to
> growing a rich user and developer community.
>
> = Community =
> There is a large need for a performant replicated log service for
> applications such as distributed databases, distributed transactional
> systems, replicated-state-machines and pub/sub messaging/queuing. We want
> to attract more developers to the project, and we believe that the ASF’s
> open and meritocratic philosophy will help us with this. We note the
> success of other similar projects already part of the ASF, like Kafka.
>
> = Core Developers =
> DistributedLog is actively developed 

Re: [VOTE] Accept DistributedLog into the Apache Incubator

[Chris Douglas]

+1 (binding) -C

On Mon, Jun 20, 2016 at 10:11 PM, Sijie Guo  wrote:
> Hello All,
>
> Following the discussion thread, I would like to call a VOTE on accepting
> DistributedLog into the Apache Incubator.
>
> [] +1 Accept DistributedLog into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept DistributedLog into the Apache Incubator because ...
>
> This vote will be open for at least 72 hours.
>
> The proposal follows, you can also access the wiki page:
> https://wiki.apache.org/incubator/DistributedLogProposal
>
> Here is my +1.
>
> Thanks,
> Sijie
>
> = Abstract =
> DistributedLog is a high-performance replicated log service. It offers
> durability, replication and strong consistency, which provides a
> fundamental building block for building reliable distributed systems, e.g
> replicated-state-machines, general pub/sub systems, distributed databases,
> distributed queues and etc.
>
> See “Building Distributedlog - Twitter’s high performance replicated log
> service” for details:
> https://blog.twitter.com/2015/building-distributedlog-twitter-s-high-performance-replicated-log-service
>
> = Proposal =
> We propose to contribute DistributedLog codebase and associated artifacts
> (e.g. documentation, web-site content etc.) to the Apache Software
> Foundation with the intent of forming a productive, meritocratic and open
> community around DistributedLog’s continued development, according to the
> ‘Apache Way’.
>
> = Background =
> Engineers at Twitter began developing DistributedLog in early 2013.
> DistributedLog is described in a Twitter engineering blog post and
> presented at the Messaging Meetup in Sep 2015. It has been released as an
> Apache-licensed open-source project on GitHub in May 2016.
>
> DistributedLog is a high-performance replicated log service, which provides
> simple stream-oriented abstractions over log-segments and offers
> durability, replication and strong consistency for building reliable
> distributed systems. The features offered by DistributedLog includes:
>
>  * Simple high-level, stream oriented interface
>  * Naming and metadata scheme for managing streams and other entities
>  * Log data management policies, include data segmentation and data
> retention
>  * Fast write pipeline leveraging batching and compression
>  * Fast read mechanism leveraging long-poll and read-ahead caching
>  * Service tiers supporting writer fan-in and reader fan-out
>  * Geo-replicated logs
>
> DistributedLog’s most important benefit is high-performance with a strong
> durability guarantee, making it extremely appropriate for running different
> workloads from distributed database journaling to real-time stream
> computing. Its modern, layered architecture makes it easy to run the
> service tiers in multi-tenant datacenter environments such as Apache Mesos
> or cloud environments such as EC2.
>
> = Rationale =
> DistributedLog is designed to provide core fundamental features like
> high-performance, durability and strong consistency to anyone who is
> building reliable distributed systems, in a simple and efficient way.
>
> We believe that the ASF is the right venue to foster an open-source
> community around DistributedLog’s development. We expect that
> DistributedLog will benefit from collaboration with related Apache
> projects, and under the auspices of the ASF will attract talented
> contributors who will push DistributedLog’s development forward at a faster
> pace.
>
> We believe that the timing is right for DistributedLog’s development to
> move to the ASF: DistributedLog has already run in production at Twitter
> for 3 years and served various workloads including a distributed database
> journal, reliable cross datacenter replication, search ingestion,
> andgeneral pub/sub messaging. The project is stable. We are excited to see
> where an ASF-based community can take DistributedLog.
>
> = Current Status =
> DistributedLog is a stable project that has been used in production at
> Twitter for 3 years. The source code is public at github.com/twitter, which
> will seed the Apache git repository.
>
> = Meritocracy =
> We understand the central importance of meritocracy to the Apache Way. We
> will work to establish a welcoming, fair and meritocratic community.
> Several companies have already expressed interest in this project, and we
> intend to invite additional developers to participate. We look forward to
> growing a rich user and developer community.
>
> = Community =
> There is a large need for a performant replicated log service for
> applications such as distributed databases, distributed transactional
> systems, replicated-state-machines and pub/sub messaging/queuing. We want
> to attract more developers to the project, and we believe that the ASF’s
> open and meritocratic philosophy will help us with this. We note the
> success of other similar projects already part of the ASF, like Kafka.
>
> = Core Developers =
> DistributedLog is actively developed within 

Re: [VOTE] Accept DistributedLog into the Apache Incubator

[Flavio Junqueira]

+1 (binding)

> On 21 Jun 2016, at 08:29, oz...@apache.org wrote:
> 
> +1(non-binding)
> 
> Looking forward to DistributedLog project's joining Apache Incubator!
> 
> Thanks,
> - Tsuyoshi
> 
>> -Original Message-
>> From: Sijie Guo [mailto:si...@apache.org]
>> Sent: Tuesday, June 21, 2016 2:12 PM
>> To: general@incubator.apache.org
>> Subject: [VOTE] Accept DistributedLog into the Apache Incubator
>> 
>> Hello All,
>> 
>> Following the discussion thread, I would like to call a VOTE on accepting
>> DistributedLog into the Apache Incubator.
>> 
>> [] +1 Accept DistributedLog into the Apache Incubator [] +0 Abstain.
>> [] -1 Do not accept DistributedLog into the Apache Incubator because ...
>> 
>> This vote will be open for at least 72 hours.
>> 
>> The proposal follows, you can also access the wiki page:
>> https://wiki.apache.org/incubator/DistributedLogProposal
>> 
>> Here is my +1.
>> 
>> Thanks,
>> Sijie
>> 
>> = Abstract =
>> DistributedLog is a high-performance replicated log service. It offers
>> durability, replication and strong consistency, which provides a
>> fundamental building block for building reliable distributed systems, e.g
>> replicated-state-machines, general pub/sub systems, distributed databases,
>> distributed queues and etc.
>> 
>> See “Building Distributedlog - Twitter’s high performance replicated log
>> service” for details:
>> https://blog.twitter.com/2015/building-distributedlog-twitter-s-high-p
>> erformance-replicated-log-service
>> 
>> = Proposal =
>> We propose to contribute DistributedLog codebase and associated artifacts
>> (e.g. documentation, web-site content etc.) to the Apache Software
>> Foundation with the intent of forming a productive, meritocratic and open
>> community around DistributedLog’s continued development, according to the
>> ‘Apache Way’.
>> 
>> = Background =
>> Engineers at Twitter began developing DistributedLog in early 2013.
>> DistributedLog is described in a Twitter engineering blog post and presented
>> at the Messaging Meetup in Sep 2015. It has been released as an
>> Apache-licensed open-source project on GitHub in May 2016.
>> 
>> DistributedLog is a high-performance replicated log service, which provides
>> simple stream-oriented abstractions over log-segments and offers
>> durability, replication and strong consistency for building reliable
>> distributed systems. The features offered by DistributedLog includes:
>> 
>> * Simple high-level, stream oriented interface
>> * Naming and metadata scheme for managing streams and other entities
>> * Log data management policies, include data segmentation and data
>> retention
>> * Fast write pipeline leveraging batching and compression
>> * Fast read mechanism leveraging long-poll and read-ahead caching
>> * Service tiers supporting writer fan-in and reader fan-out
>> * Geo-replicated logs
>> 
>> DistributedLog’s most important benefit is high-performance with a strong
>> durability guarantee, making it extremely appropriate for running different
>> workloads from distributed database journaling to real-time stream
>> computing. Its modern, layered architecture makes it easy to run the service
>> tiers in multi-tenant datacenter environments such as Apache Mesos or cloud
>> environments such as EC2.
>> 
>> = Rationale =
>> DistributedLog is designed to provide core fundamental features like
>> high-performance, durability and strong consistency to anyone who is
>> building reliable distributed systems, in a simple and efficient way.
>> 
>> We believe that the ASF is the right venue to foster an open-source community
>> around DistributedLog’s development. We expect that DistributedLog will
>> benefit from collaboration with related Apache projects, and under the
>> auspices of the ASF will attract talented contributors who will push
>> DistributedLog’s development forward at a faster pace.
>> 
>> We believe that the timing is right for DistributedLog’s development to
>> move to the ASF: DistributedLog has already run in production at Twitter
>> for 3 years and served various workloads including a distributed database
>> journal, reliable cross datacenter replication, search ingestion,
>> andgeneral pub/sub messaging. The project is stable. We are excited to see
>> where an ASF-based community can take DistributedLog.
>> 
>> = Current Status =
>> DistributedLog is a stable project that has been used in production at
>> Tw

RE: [VOTE] Accept DistributedLog into the Apache Incubator

[ozawa]

+1(non-binding)

Looking forward to DistributedLog project's joining Apache Incubator!

Thanks,
- Tsuyoshi

> -Original Message-
> From: Sijie Guo [mailto:si...@apache.org]
> Sent: Tuesday, June 21, 2016 2:12 PM
> To: general@incubator.apache.org
> Subject: [VOTE] Accept DistributedLog into the Apache Incubator
> 
> Hello All,
> 
> Following the discussion thread, I would like to call a VOTE on accepting
> DistributedLog into the Apache Incubator.
> 
> [] +1 Accept DistributedLog into the Apache Incubator [] +0 Abstain.
> [] -1 Do not accept DistributedLog into the Apache Incubator because ...
> 
> This vote will be open for at least 72 hours.
> 
> The proposal follows, you can also access the wiki page:
> https://wiki.apache.org/incubator/DistributedLogProposal
> 
> Here is my +1.
> 
> Thanks,
> Sijie
> 
> = Abstract =
> DistributedLog is a high-performance replicated log service. It offers
> durability, replication and strong consistency, which provides a
> fundamental building block for building reliable distributed systems, e.g
> replicated-state-machines, general pub/sub systems, distributed databases,
> distributed queues and etc.
> 
> See “Building Distributedlog - Twitter’s high performance replicated log
> service” for details:
> https://blog.twitter.com/2015/building-distributedlog-twitter-s-high-p
> erformance-replicated-log-service
> 
> = Proposal =
> We propose to contribute DistributedLog codebase and associated artifacts
> (e.g. documentation, web-site content etc.) to the Apache Software
> Foundation with the intent of forming a productive, meritocratic and open
> community around DistributedLog’s continued development, according to the
> ‘Apache Way’.
> 
> = Background =
> Engineers at Twitter began developing DistributedLog in early 2013.
> DistributedLog is described in a Twitter engineering blog post and presented
> at the Messaging Meetup in Sep 2015. It has been released as an
> Apache-licensed open-source project on GitHub in May 2016.
> 
> DistributedLog is a high-performance replicated log service, which provides
> simple stream-oriented abstractions over log-segments and offers
> durability, replication and strong consistency for building reliable
> distributed systems. The features offered by DistributedLog includes:
> 
>  * Simple high-level, stream oriented interface
>  * Naming and metadata scheme for managing streams and other entities
>  * Log data management policies, include data segmentation and data
> retention
>  * Fast write pipeline leveraging batching and compression
>  * Fast read mechanism leveraging long-poll and read-ahead caching
>  * Service tiers supporting writer fan-in and reader fan-out
>  * Geo-replicated logs
> 
> DistributedLog’s most important benefit is high-performance with a strong
> durability guarantee, making it extremely appropriate for running different
> workloads from distributed database journaling to real-time stream
> computing. Its modern, layered architecture makes it easy to run the service
> tiers in multi-tenant datacenter environments such as Apache Mesos or cloud
> environments such as EC2.
> 
> = Rationale =
> DistributedLog is designed to provide core fundamental features like
> high-performance, durability and strong consistency to anyone who is
> building reliable distributed systems, in a simple and efficient way.
> 
> We believe that the ASF is the right venue to foster an open-source community
> around DistributedLog’s development. We expect that DistributedLog will
> benefit from collaboration with related Apache projects, and under the
> auspices of the ASF will attract talented contributors who will push
> DistributedLog’s development forward at a faster pace.
> 
> We believe that the timing is right for DistributedLog’s development to
> move to the ASF: DistributedLog has already run in production at Twitter
> for 3 years and served various workloads including a distributed database
> journal, reliable cross datacenter replication, search ingestion,
> andgeneral pub/sub messaging. The project is stable. We are excited to see
> where an ASF-based community can take DistributedLog.
> 
> = Current Status =
> DistributedLog is a stable project that has been used in production at
> Twitter for 3 years. The source code is public at github.com/twitter, which
> will seed the Apache git repository.
> 
> = Meritocracy =
> We understand the central importance of meritocracy to the Apache Way. We
> will work to establish a welcoming, fair and meritocratic community.
> Several companies have already expressed interest in this project, and we
> intend to invite additional developers to participate. We look forward to
> growing a r

Re: [VOTE] Accept DistributedLog into the Apache Incubator

[Debo Dutta (dedutta)]

+1




On 6/20/16, 10:11 PM, "Sijie Guo"  wrote:

>Hello All,
>
>Following the discussion thread, I would like to call a VOTE on accepting
>DistributedLog into the Apache Incubator.
>
>[] +1 Accept DistributedLog into the Apache Incubator
>[] +0 Abstain.
>[] -1 Do not accept DistributedLog into the Apache Incubator because ...
>
>This vote will be open for at least 72 hours.
>
>The proposal follows, you can also access the wiki page:
>https://wiki.apache.org/incubator/DistributedLogProposal
>
>Here is my +1.
>
>Thanks,
>Sijie
>
>= Abstract =
>DistributedLog is a high-performance replicated log service. It offers
>durability, replication and strong consistency, which provides a
>fundamental building block for building reliable distributed systems, e.g
>replicated-state-machines, general pub/sub systems, distributed databases,
>distributed queues and etc.
>
>See “Building Distributedlog - Twitter’s high performance replicated log
>service” for details:
>https://blog.twitter.com/2015/building-distributedlog-twitter-s-high-performance-replicated-log-service
>
>= Proposal =
>We propose to contribute DistributedLog codebase and associated artifacts
>(e.g. documentation, web-site content etc.) to the Apache Software
>Foundation with the intent of forming a productive, meritocratic and open
>community around DistributedLog’s continued development, according to the
>‘Apache Way’.
>
>= Background =
>Engineers at Twitter began developing DistributedLog in early 2013.
>DistributedLog is described in a Twitter engineering blog post and
>presented at the Messaging Meetup in Sep 2015. It has been released as an
>Apache-licensed open-source project on GitHub in May 2016.
>
>DistributedLog is a high-performance replicated log service, which provides
>simple stream-oriented abstractions over log-segments and offers
>durability, replication and strong consistency for building reliable
>distributed systems. The features offered by DistributedLog includes:
>
> * Simple high-level, stream oriented interface
> * Naming and metadata scheme for managing streams and other entities
> * Log data management policies, include data segmentation and data
>retention
> * Fast write pipeline leveraging batching and compression
> * Fast read mechanism leveraging long-poll and read-ahead caching
> * Service tiers supporting writer fan-in and reader fan-out
> * Geo-replicated logs
>
>DistributedLog’s most important benefit is high-performance with a strong
>durability guarantee, making it extremely appropriate for running different
>workloads from distributed database journaling to real-time stream
>computing. Its modern, layered architecture makes it easy to run the
>service tiers in multi-tenant datacenter environments such as Apache Mesos
>or cloud environments such as EC2.
>
>= Rationale =
>DistributedLog is designed to provide core fundamental features like
>high-performance, durability and strong consistency to anyone who is
>building reliable distributed systems, in a simple and efficient way.
>
>We believe that the ASF is the right venue to foster an open-source
>community around DistributedLog’s development. We expect that
>DistributedLog will benefit from collaboration with related Apache
>projects, and under the auspices of the ASF will attract talented
>contributors who will push DistributedLog’s development forward at a faster
>pace.
>
>We believe that the timing is right for DistributedLog’s development to
>move to the ASF: DistributedLog has already run in production at Twitter
>for 3 years and served various workloads including a distributed database
>journal, reliable cross datacenter replication, search ingestion,
>andgeneral pub/sub messaging. The project is stable. We are excited to see
>where an ASF-based community can take DistributedLog.
>
>= Current Status =
>DistributedLog is a stable project that has been used in production at
>Twitter for 3 years. The source code is public at github.com/twitter, which
>will seed the Apache git repository.
>
>= Meritocracy =
>We understand the central importance of meritocracy to the Apache Way. We
>will work to establish a welcoming, fair and meritocratic community.
>Several companies have already expressed interest in this project, and we
>intend to invite additional developers to participate. We look forward to
>growing a rich user and developer community.
>
>= Community =
>There is a large need for a performant replicated log service for
>applications such as distributed databases, distributed transactional
>systems, replicated-state-machines and pub/sub messaging/queuing. We want
>to attract more developers to the project, and we believe that the ASF’s
>open and meritocratic philosophy will help us with this. We note the
>success of other similar projects already part of the ASF, like Kafka.
>
>= Core Developers =
>DistributedLog is actively developed within Twitter. Most of the developers
>are from Twitter. Many of them are committers or PMC members of Apache

Re: [VOTE] Accept DistributedLog into the Apache Incubator

[Naresh Agarwal]

+1 (non-binding)

On Tue, Jun 21, 2016 at 11:26 AM, Jia Zhai <zhaiji...@gmail.com> wrote:

> +1
>
> From: Sijie Guo <si...@apache.org>
> > Date: Mon, Jun 20, 2016 at 10:11 PM
> > Subject: [VOTE] Accept DistributedLog into the Apache Incubator
> > To: general@incubator.apache.org
> >
> >
> > Hello All,
> >
> > Following the discussion thread, I would like to call a VOTE on accepting
> > DistributedLog into the Apache Incubator.
> >
> > [] +1 Accept DistributedLog into the Apache Incubator
> > [] +0 Abstain.
> > [] -1 Do not accept DistributedLog into the Apache Incubator because ...
> >
> > This vote will be open for at least 72 hours.
> >
> > The proposal follows, you can also access the wiki page:
> > https://wiki.apache.org/incubator/DistributedLogProposal
> >
> > Here is my +1.
> >
> > Thanks,
> > Sijie
> >
> > = Abstract =
> > DistributedLog is a high-performance replicated log service. It offers
> > durability, replication and strong consistency, which provides a
> > fundamental building block for building reliable distributed systems, e.g
> > replicated-state-machines, general pub/sub systems, distributed
> databases,
> > distributed queues and etc.
> >
> > See “Building Distributedlog - Twitter’s high performance replicated log
> > service” for details:
> >
> https://blog.twitter.com/2015/building-distributedlog-twitter-s-high-performance-replicated-log-service
> >
> > = Proposal =
> > We propose to contribute DistributedLog codebase and associated artifacts
> > (e.g. documentation, web-site content etc.) to the Apache Software
> > Foundation with the intent of forming a productive, meritocratic and open
> > community around DistributedLog’s continued development, according to the
> > ‘Apache Way’.
> >
> > = Background =
> > Engineers at Twitter began developing DistributedLog in early 2013.
> > DistributedLog is described in a Twitter engineering blog post and
> > presented at the Messaging Meetup in Sep 2015. It has been released as an
> > Apache-licensed open-source project on GitHub in May 2016.
> >
> > DistributedLog is a high-performance replicated log service, which
> > provides simple stream-oriented abstractions over log-segments and offers
> > durability, replication and strong consistency for building reliable
> > distributed systems. The features offered by DistributedLog includes:
> >
> >  * Simple high-level, stream oriented interface
> >  * Naming and metadata scheme for managing streams and other entities
> >  * Log data management policies, include data segmentation and data
> > retention
> >  * Fast write pipeline leveraging batching and compression
> >  * Fast read mechanism leveraging long-poll and read-ahead caching
> >  * Service tiers supporting writer fan-in and reader fan-out
> >  * Geo-replicated logs
> >
> > DistributedLog’s most important benefit is high-performance with a strong
> > durability guarantee, making it extremely appropriate for running
> different
> > workloads from distributed database journaling to real-time stream
> > computing. Its modern, layered architecture makes it easy to run the
> > service tiers in multi-tenant datacenter environments such as Apache
> Mesos
> > or cloud environments such as EC2.
> >
> > = Rationale =
> > DistributedLog is designed to provide core fundamental features like
> > high-performance, durability and strong consistency to anyone who is
> > building reliable distributed systems, in a simple and efficient way.
> >
> > We believe that the ASF is the right venue to foster an open-source
> > community around DistributedLog’s development. We expect that
> > DistributedLog will benefit from collaboration with related Apache
> > projects, and under the auspices of the ASF will attract talented
> > contributors who will push DistributedLog’s development forward at a
> faster
> > pace.
> >
> > We believe that the timing is right for DistributedLog’s development to
> > move to the ASF: DistributedLog has already run in production at Twitter
> > for 3 years and served various workloads including a distributed database
> > journal, reliable cross datacenter replication, search ingestion,
> > andgeneral pub/sub messaging. The project is stable. We are excited to
> see
> > where an ASF-based community can take DistributedLog.
> >
> > = Current Status =
> > DistributedLog is a stable project that has been used in production at
> > Twitter for 3 years.

Re: [VOTE] Accept DistributedLog into the Apache Incubator

[Jia Zhai]

+1

From: Sijie Guo <si...@apache.org>
> Date: Mon, Jun 20, 2016 at 10:11 PM
> Subject: [VOTE] Accept DistributedLog into the Apache Incubator
> To: general@incubator.apache.org
>
>
> Hello All,
>
> Following the discussion thread, I would like to call a VOTE on accepting
> DistributedLog into the Apache Incubator.
>
> [] +1 Accept DistributedLog into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept DistributedLog into the Apache Incubator because ...
>
> This vote will be open for at least 72 hours.
>
> The proposal follows, you can also access the wiki page:
> https://wiki.apache.org/incubator/DistributedLogProposal
>
> Here is my +1.
>
> Thanks,
> Sijie
>
> = Abstract =
> DistributedLog is a high-performance replicated log service. It offers
> durability, replication and strong consistency, which provides a
> fundamental building block for building reliable distributed systems, e.g
> replicated-state-machines, general pub/sub systems, distributed databases,
> distributed queues and etc.
>
> See “Building Distributedlog - Twitter’s high performance replicated log
> service” for details:
> https://blog.twitter.com/2015/building-distributedlog-twitter-s-high-performance-replicated-log-service
>
> = Proposal =
> We propose to contribute DistributedLog codebase and associated artifacts
> (e.g. documentation, web-site content etc.) to the Apache Software
> Foundation with the intent of forming a productive, meritocratic and open
> community around DistributedLog’s continued development, according to the
> ‘Apache Way’.
>
> = Background =
> Engineers at Twitter began developing DistributedLog in early 2013.
> DistributedLog is described in a Twitter engineering blog post and
> presented at the Messaging Meetup in Sep 2015. It has been released as an
> Apache-licensed open-source project on GitHub in May 2016.
>
> DistributedLog is a high-performance replicated log service, which
> provides simple stream-oriented abstractions over log-segments and offers
> durability, replication and strong consistency for building reliable
> distributed systems. The features offered by DistributedLog includes:
>
>  * Simple high-level, stream oriented interface
>  * Naming and metadata scheme for managing streams and other entities
>  * Log data management policies, include data segmentation and data
> retention
>  * Fast write pipeline leveraging batching and compression
>  * Fast read mechanism leveraging long-poll and read-ahead caching
>  * Service tiers supporting writer fan-in and reader fan-out
>  * Geo-replicated logs
>
> DistributedLog’s most important benefit is high-performance with a strong
> durability guarantee, making it extremely appropriate for running different
> workloads from distributed database journaling to real-time stream
> computing. Its modern, layered architecture makes it easy to run the
> service tiers in multi-tenant datacenter environments such as Apache Mesos
> or cloud environments such as EC2.
>
> = Rationale =
> DistributedLog is designed to provide core fundamental features like
> high-performance, durability and strong consistency to anyone who is
> building reliable distributed systems, in a simple and efficient way.
>
> We believe that the ASF is the right venue to foster an open-source
> community around DistributedLog’s development. We expect that
> DistributedLog will benefit from collaboration with related Apache
> projects, and under the auspices of the ASF will attract talented
> contributors who will push DistributedLog’s development forward at a faster
> pace.
>
> We believe that the timing is right for DistributedLog’s development to
> move to the ASF: DistributedLog has already run in production at Twitter
> for 3 years and served various workloads including a distributed database
> journal, reliable cross datacenter replication, search ingestion,
> andgeneral pub/sub messaging. The project is stable. We are excited to see
> where an ASF-based community can take DistributedLog.
>
> = Current Status =
> DistributedLog is a stable project that has been used in production at
> Twitter for 3 years. The source code is public at github.com/twitter,
> which will seed the Apache git repository.
>
> = Meritocracy =
> We understand the central importance of meritocracy to the Apache Way. We
> will work to establish a welcoming, fair and meritocratic community.
> Several companies have already expressed interest in this project, and we
> intend to invite additional developers to participate. We look forward to
> growing a rich user and developer community.
>
> = Community =
> There is a large need for a performant replicated log service for
> applications such as dist

[VOTE] Accept DistributedLog into the Apache Incubator

[Sijie Guo]

Hello All,

Following the discussion thread, I would like to call a VOTE on accepting
DistributedLog into the Apache Incubator.

[] +1 Accept DistributedLog into the Apache Incubator
[] +0 Abstain.
[] -1 Do not accept DistributedLog into the Apache Incubator because ...

This vote will be open for at least 72 hours.

The proposal follows, you can also access the wiki page:
https://wiki.apache.org/incubator/DistributedLogProposal

Here is my +1.

Thanks,
Sijie

= Abstract =
DistributedLog is a high-performance replicated log service. It offers
durability, replication and strong consistency, which provides a
fundamental building block for building reliable distributed systems, e.g
replicated-state-machines, general pub/sub systems, distributed databases,
distributed queues and etc.

See “Building Distributedlog - Twitter’s high performance replicated log
service” for details:
https://blog.twitter.com/2015/building-distributedlog-twitter-s-high-performance-replicated-log-service

= Proposal =
We propose to contribute DistributedLog codebase and associated artifacts
(e.g. documentation, web-site content etc.) to the Apache Software
Foundation with the intent of forming a productive, meritocratic and open
community around DistributedLog’s continued development, according to the
‘Apache Way’.

= Background =
Engineers at Twitter began developing DistributedLog in early 2013.
DistributedLog is described in a Twitter engineering blog post and
presented at the Messaging Meetup in Sep 2015. It has been released as an
Apache-licensed open-source project on GitHub in May 2016.

DistributedLog is a high-performance replicated log service, which provides
simple stream-oriented abstractions over log-segments and offers
durability, replication and strong consistency for building reliable
distributed systems. The features offered by DistributedLog includes:

 * Simple high-level, stream oriented interface
 * Naming and metadata scheme for managing streams and other entities
 * Log data management policies, include data segmentation and data
retention
 * Fast write pipeline leveraging batching and compression
 * Fast read mechanism leveraging long-poll and read-ahead caching
 * Service tiers supporting writer fan-in and reader fan-out
 * Geo-replicated logs

DistributedLog’s most important benefit is high-performance with a strong
durability guarantee, making it extremely appropriate for running different
workloads from distributed database journaling to real-time stream
computing. Its modern, layered architecture makes it easy to run the
service tiers in multi-tenant datacenter environments such as Apache Mesos
or cloud environments such as EC2.

= Rationale =
DistributedLog is designed to provide core fundamental features like
high-performance, durability and strong consistency to anyone who is
building reliable distributed systems, in a simple and efficient way.

We believe that the ASF is the right venue to foster an open-source
community around DistributedLog’s development. We expect that
DistributedLog will benefit from collaboration with related Apache
projects, and under the auspices of the ASF will attract talented
contributors who will push DistributedLog’s development forward at a faster
pace.

We believe that the timing is right for DistributedLog’s development to
move to the ASF: DistributedLog has already run in production at Twitter
for 3 years and served various workloads including a distributed database
journal, reliable cross datacenter replication, search ingestion,
andgeneral pub/sub messaging. The project is stable. We are excited to see
where an ASF-based community can take DistributedLog.

= Current Status =
DistributedLog is a stable project that has been used in production at
Twitter for 3 years. The source code is public at github.com/twitter, which
will seed the Apache git repository.

= Meritocracy =
We understand the central importance of meritocracy to the Apache Way. We
will work to establish a welcoming, fair and meritocratic community.
Several companies have already expressed interest in this project, and we
intend to invite additional developers to participate. We look forward to
growing a rich user and developer community.

= Community =
There is a large need for a performant replicated log service for
applications such as distributed databases, distributed transactional
systems, replicated-state-machines and pub/sub messaging/queuing. We want
to attract more developers to the project, and we believe that the ASF’s
open and meritocratic philosophy will help us with this. We note the
success of other similar projects already part of the ASF, like Kafka.

= Core Developers =
DistributedLog is actively developed within Twitter. Most of the developers
are from Twitter. Many of them are committers or PMC members of Apache
BookKeeper. Others aren’t currently affiliated with ASF so they will
require new ICLAs.

= Alignment =
DistributedLog is related to several other Apache projects:

 *