Re: [VOTE]: Apache Weex-incubating Release 0.12.0-RC4

2017-05-17 Thread sospartan 
ok, I'll update my release script to bring every source code under root
directory.
Thanks for this tip.


On Thu, May 18, 2017 at 11:03 AM, John D. Ament 
wrote:

> On Wed, May 17, 2017 at 7:57 PM sospartan  wrote:
>
> > John,
> > Thanks for the review.
> > I don't understand the issue with "sub-directory". Is there any standard
> > directory structure for source release?
> >
>
>
> Typically the release contents are simply in the root directory.  There
> should not be a subdirectory where all the contents exist.
>
>
> >
> > John D. Ament 于2017年5月17日 周三下午11:41写道：
> >
> > > sospartan,
> > >
> > > Couple of things noticed:
> > >
> > > - Your email still points to your non-ASF hosted website.  Don't forget
> > to
> > > point to your ASF website.
> > > - The source release still contains a sub-directory.
> > > - Its still not clear to me how to create the binary.
> > > - Your package.json points still to old alibaba repos and not ASF repos
> > >
> > > I would like to see these 4 issues fixed for next release.
> > >
> > > LICENSE file looks good, minor typos (still need to fix the extra
> > comments)
> > > NOTICE file looks fine
> > > DISCLAIMER is present.
> > > No binaries that I can find.
> > >
> > > +1
> > >
> > > John
> > >
> > > On Mon, May 15, 2017 at 5:24 AM sospartan 
> wrote:
> > >
> > > > Hi IPMC,
> > > >
> > > > I'm calling a vote for Weex-incubating 0.12.0-RC4 release.
> > > > In this release, source tarball only include files necessary to build
> > > Weex
> > > > SDK.
> > > > All binaries were excluded.
> > > > A build README(README_RELEASE.md)  is in the tarball now.
> > > >
> > > > Thanks for peoples who were taking time to review our last RC (RC3).
> > I'm
> > > > Hoping
> > > > this RC is doing better.
> > > >
> > > > The PPMC vote for this release has passed:
> > > > https://lists.apache.org/thread.html/0e05de680b315e453fe8643ff297d5
> > > > ebfb9cdd30ea2c982e33854ff5@%3Cdev.weex.apache.org%3E
> > > >
> > > > The tag to be voted upon:
> > > > https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git
> > > > ;a=shortlog;h=refs/tags/0.12.0-rc4
> > > >
> > > > The commit hash:
> > > >
> > https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=commit;h=
> > > > e19ef8a4acc39cd8db2cf3be4f8369f6d7a0bb43
> > > > <
> > >
> > https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=commit;h=
> e19ef8a4acc39cd8db2cf3be4f8369f6d7a0bb43
> > > >
> > > >
> > > > The source tarball can be found at:
> > > >
> > > >
> > >
> > https://dist.apache.org/repos/dist/dev/incubator/weex/0.12.
> 0-incubating/RC4/
> > > >
> > > > The fingerprint of key to sign release artifacts:
> > > > 97B9 6598 A6A3 B63C 53BD  77E9 44C5 2286 22B9 7784
> > > >
> > > > Release artifacts are signed with the following key:
> > > > https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS
> > > >
> > > > Release note about this version:
> > > > https://issues.apache.org/jira/browse/WEEX-26
> > > >
> > > > This vote will remain open for at least 72 hours.
> > > > Please vote on releasing this RC.
> > > >
> > > > [ ] +1 approve
> > > > [ ] +0 no opinion
> > > > [ ] -1 disapprove (and reason why)
> > > >
> > > > --
> > > > Best Regards!
> > > > --
> > > >
> > > > sospartan
> > > > https://weex-project.io
> > > >
> > >
> > --
> > sospartan
> > Phone:13588488290
> > HangZhou
> >
>



-- 
sospartan
Phone:13588488290
HangZhou

Re: Questions on incubator releases

2017-05-17 Thread Justin Mclean 
Hi,

> Yes, though typically the staged maven repo is reviewed as a part of the
> release.

+1 best to review and vote on both at once

>> (q2) If the answer of q1 is yes, do we need to prepare different
>> LICENSE and NOTICE files for the binaries?  

IMO the answer is likely to be yes. In a lot of cases convenience binaries 
bundle other software and the license and notice need to reflect that.

However if binaries consist of only the complied source and contain no other 
3rd party jars then they would be identical.

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE]: Apache Weex-incubating Release 0.12.0-RC4

2017-05-17 Thread John D. Ament 
On Wed, May 17, 2017 at 7:57 PM sospartan  wrote:

> John,
> Thanks for the review.
> I don't understand the issue with "sub-directory". Is there any standard
> directory structure for source release?
>


Typically the release contents are simply in the root directory.  There
should not be a subdirectory where all the contents exist.


>
> John D. Ament 于2017年5月17日 周三下午11:41写道：
>
> > sospartan,
> >
> > Couple of things noticed:
> >
> > - Your email still points to your non-ASF hosted website.  Don't forget
> to
> > point to your ASF website.
> > - The source release still contains a sub-directory.
> > - Its still not clear to me how to create the binary.
> > - Your package.json points still to old alibaba repos and not ASF repos
> >
> > I would like to see these 4 issues fixed for next release.
> >
> > LICENSE file looks good, minor typos (still need to fix the extra
> comments)
> > NOTICE file looks fine
> > DISCLAIMER is present.
> > No binaries that I can find.
> >
> > +1
> >
> > John
> >
> > On Mon, May 15, 2017 at 5:24 AM sospartan  wrote:
> >
> > > Hi IPMC,
> > >
> > > I'm calling a vote for Weex-incubating 0.12.0-RC4 release.
> > > In this release, source tarball only include files necessary to build
> > Weex
> > > SDK.
> > > All binaries were excluded.
> > > A build README(README_RELEASE.md)  is in the tarball now.
> > >
> > > Thanks for peoples who were taking time to review our last RC (RC3).
> I'm
> > > Hoping
> > > this RC is doing better.
> > >
> > > The PPMC vote for this release has passed:
> > > https://lists.apache.org/thread.html/0e05de680b315e453fe8643ff297d5
> > > ebfb9cdd30ea2c982e33854ff5@%3Cdev.weex.apache.org%3E
> > >
> > > The tag to be voted upon:
> > > https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git
> > > ;a=shortlog;h=refs/tags/0.12.0-rc4
> > >
> > > The commit hash:
> > >
> https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=commit;h=
> > > e19ef8a4acc39cd8db2cf3be4f8369f6d7a0bb43
> > > <
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=commit;h=e19ef8a4acc39cd8db2cf3be4f8369f6d7a0bb43
> > >
> > >
> > > The source tarball can be found at:
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/weex/0.12.0-incubating/RC4/
> > >
> > > The fingerprint of key to sign release artifacts:
> > > 97B9 6598 A6A3 B63C 53BD  77E9 44C5 2286 22B9 7784
> > >
> > > Release artifacts are signed with the following key:
> > > https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS
> > >
> > > Release note about this version:
> > > https://issues.apache.org/jira/browse/WEEX-26
> > >
> > > This vote will remain open for at least 72 hours.
> > > Please vote on releasing this RC.
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove (and reason why)
> > >
> > > --
> > > Best Regards!
> > > --
> > >
> > > sospartan
> > > https://weex-project.io
> > >
> >
> --
> sospartan
> Phone:13588488290
> HangZhou
>

Re: Questions on incubator releases

2017-05-17 Thread John D. Ament 
On Wed, May 17, 2017 at 7:14 PM Tsz Wo Sze  wrote:

> Hi,
>
> The release VOTE has been passed in both the Podling dev list [1] and
> the Incubator's general list [2] for Apache Ratis.  I also have copied
> the RC to dist/release so that it is available at [3].
>
> My questions are:
> (q1) Our release is a source release, could we distribute binaries
> through other channels like the central Maven repository as described
> in [4]?
>
>
Yes, though typically the staged maven repo is reviewed as a part of the
release.  Something to do for next time, but assuming you've already been
setup go for it.


> (q2) If the answer of q1 is yes, do we need to prepare different
> LICENSE and NOTICE files for the binaries?  The jar files distributed
> over Maven are going to contain some third party binaries not included
> in the source release.
>
>
Is there anything different about your binaries?  The only reason they
would be different is if you've shaded in other libraries to your JARs
causing the original LICENSE/NOTICE to be invalid.  In most cases this is
not the case.


> Thank you in advance.
> Tsz-Wo
> ---
> [1]
> https://lists.apache.org/thread.html/eb0df0548299ae98e68c0067e43d9747a67e92a459cedbe55b56425d@%3Cdev.ratis.apache.org%3E
>
> [2]
> https://lists.apache.org/thread.html/ecb8ef1ce6c32995531cae1121a86522e34bfd6e64067b34dbb9dd8a@%3Cgeneral.incubator.apache.org%3E
>
> [3] http://www.apache.org/dist/incubator/ratis/0.1.0-alpha/
>
> [4] http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE]: Apache Weex-incubating Release 0.12.0-RC4

2017-05-17 Thread sospartan 
John,
Thanks for the review.
I don't understand the issue with "sub-directory". Is there any standard
directory structure for source release?

John D. Ament 于2017年5月17日 周三下午11:41写道：

> sospartan,
>
> Couple of things noticed:
>
> - Your email still points to your non-ASF hosted website.  Don't forget to
> point to your ASF website.
> - The source release still contains a sub-directory.
> - Its still not clear to me how to create the binary.
> - Your package.json points still to old alibaba repos and not ASF repos
>
> I would like to see these 4 issues fixed for next release.
>
> LICENSE file looks good, minor typos (still need to fix the extra comments)
> NOTICE file looks fine
> DISCLAIMER is present.
> No binaries that I can find.
>
> +1
>
> John
>
> On Mon, May 15, 2017 at 5:24 AM sospartan  wrote:
>
> > Hi IPMC,
> >
> > I'm calling a vote for Weex-incubating 0.12.0-RC4 release.
> > In this release, source tarball only include files necessary to build
> Weex
> > SDK.
> > All binaries were excluded.
> > A build README(README_RELEASE.md)  is in the tarball now.
> >
> > Thanks for peoples who were taking time to review our last RC (RC3). I'm
> > Hoping
> > this RC is doing better.
> >
> > The PPMC vote for this release has passed:
> > https://lists.apache.org/thread.html/0e05de680b315e453fe8643ff297d5
> > ebfb9cdd30ea2c982e33854ff5@%3Cdev.weex.apache.org%3E
> >
> > The tag to be voted upon:
> > https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git
> > ;a=shortlog;h=refs/tags/0.12.0-rc4
> >
> > The commit hash:
> > https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=commit;h=
> > e19ef8a4acc39cd8db2cf3be4f8369f6d7a0bb43
> > <
> https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=commit;h=e19ef8a4acc39cd8db2cf3be4f8369f6d7a0bb43
> >
> >
> > The source tarball can be found at:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/weex/0.12.0-incubating/RC4/
> >
> > The fingerprint of key to sign release artifacts:
> > 97B9 6598 A6A3 B63C 53BD  77E9 44C5 2286 22B9 7784
> >
> > Release artifacts are signed with the following key:
> > https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS
> >
> > Release note about this version:
> > https://issues.apache.org/jira/browse/WEEX-26
> >
> > This vote will remain open for at least 72 hours.
> > Please vote on releasing this RC.
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove (and reason why)
> >
> > --
> > Best Regards!
> > --
> >
> > sospartan
> > https://weex-project.io
> >
>
-- 
sospartan
Phone:13588488290
HangZhou

Questions on incubator releases

2017-05-17 Thread Tsz Wo Sze 
Hi,

The release VOTE has been passed in both the Podling dev list [1] and
the Incubator's general list [2] for Apache Ratis.  I also have copied
the RC to dist/release so that it is available at [3].

My questions are:
(q1) Our release is a source release, could we distribute binaries
through other channels like the central Maven repository as described
in [4]?

(q2) If the answer of q1 is yes, do we need to prepare different
LICENSE and NOTICE files for the binaries?  The jar files distributed
over Maven are going to contain some third party binaries not included
in the source release.

Thank you in advance.
Tsz-Wo
---
[1] 
https://lists.apache.org/thread.html/eb0df0548299ae98e68c0067e43d9747a67e92a459cedbe55b56425d@%3Cdev.ratis.apache.org%3E

[2] 
https://lists.apache.org/thread.html/ecb8ef1ce6c32995531cae1121a86522e34bfd6e64067b34dbb9dd8a@%3Cgeneral.incubator.apache.org%3E

[3] http://www.apache.org/dist/incubator/ratis/0.1.0-alpha/

[4] http://incubator.apache.org/incubation/Incubation_Policy.html#Releases

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Pulsar into the Apache Incubator

2017-05-17 Thread vintagewang 
+1(non-binding)

Pulsar is a powerful mq， I like it.



On Wed, May 17, 2017 at 2:44 PM, Julian Hyde  wrote:

> +1 (binding)
>
> > On May 17, 2017, at 1:58 PM, Jia Zhai  wrote:
> >
> > +1 (non-binding)
> >
> > On Thu, May 18, 2017 at 1:11 AM, P. Taylor Goetz 
> wrote:
> >
> >> +1 (binding)
> >>
> >> -Taylor
> >>
> >>> On May 16, 2017, at 10:39 PM, Bryan Call  wrote:
> >>>
> >>> Hi All,
> >>>
> >>> As the champion for Pulsar, I would like to start a VOTE to bring the
> >>> project in as Apache incubator podling.
> >>>
> >>> The ASF voting rules are described:
> >>>
> >>>   https://www.apache.org/foundation/voting.html
> >>>
> >>> A vote for accepting a new Apache Incubator podling is a majority vote
> >> for which
> >>> only Incubator PMC member votes are binding.
> >>>
> >>> This vote will run for at least 72 hours. Please VOTE as follows
> >>> [] +1 Accept Pulsar into the Apache Incubator
> >>> [] +0 Abstain.
> >>> [] -1 Do not accept Pulsar into the Apache Incubator because ...
> >>>
> >>> The proposal is listed below, but you can also access it on the wiki:
> >>>
> >>>   https://wiki.apache.org/incubator/PulsarProposal
> >>>
> >>> -Bryan
> >>>
> >>>
> >>> = Pulsar Proposal =
> >>>
> >>> == Abstract ==
> >>>
> >>> Pulsar is a highly scalable, low latency messaging platform running on
> >>> commodity hardware. It provides simple pub-sub semantics over topics,
> >>> guaranteed at-least-once delivery of messages, automatic cursor
> >> management for
> >>> subscribers, and cross-datacenter replication.
> >>>
> >>> == Proposal ==
> >>>
> >>> Pub-sub messaging is a very common design pattern that is increasingly
> >> found
> >>> in distributed systems powering Internet applications. These
> applications
> >>> provide real-time services, and need publish-latencies of 5ms on
> average
> >> and
> >>> no more than 15ms at the 99th percentile. At Internet scale, these
> >>> applications require a messaging system with ordering, strong
> >> durability, and
> >>> delivery guarantees. In order to handle the “five 9’s” durability
> >> requirements
> >>> of a production environment, the messages have to be committed on
> >> multiple
> >>> disks or nodes.
> >>>
> >>> Pulsar has been developed at Yahoo to address these specific
> >> requirements by
> >>> providing a hosted service supporting millions of topics for multiple
> >> tenants.
> >>> The current incarnation of Pulsar has been open-sourced under Apache
> >> license
> >>> in September 2016 and it is the direct evolution of systems that were
> >>> developed at Yahoo since 2011.
> >>>
> >>> We believe there is currently no other system that provides a
> >> multi-tenant
> >>> hosted messaging platform capable of supporting a huge number of topics
> >> while
> >>> maintaining strict guarantees for durability, ordering and low latency.
> >>> Current solutions would require to run multiple individual clusters
> with
> >>> additional operational work and capacity overhead.
> >>>
> >>> Since the open sourcing of Pulsar, the development has been done
> >> exclusively
> >>> on the public Github repository and two major releases were shipped
> >> (1.15 and
> >>> 1.16), along with multiple minor ones. Several other companies have
> >> expressed
> >>> interest in the project and its future direction.
> >>>
> >>> == Rationale ==
> >>>
> >>> Pulsar is a platform that is built on top of several other Apache
> >> projects. In
> >>> particular, Apache BookKeeper is used to store the data and Apache
> >> ZooKeeper
> >>> is used for coordination and metadata storage. Pulsar is also
> >> interoperable
> >>> out of the box with Apache Storm, to provide an easy to use stream
> >> processing
> >>> solution.
> >>>
> >>> We want to establish a community outside the scope of initial core
> >> developers
> >>> at Yahoo and we believe that the Apache Foundation is a great fit and
> >> long-
> >>> term home for Pulsar, as it provides an established process for
> >> community-
> >>> driven development and decision making by consensus. This is exactly
> the
> >> model
> >>> we want to adopt for future Pulsar development.
> >>>
> >>> == Initial Goals ==
> >>>
> >>> The initial goals will be to move the existing codebase to Apache and
> >>> integrate with the Apache development process. Furthermore, we plan for
> >>> incremental development, and releases along with the Apache guidelines.
> >>>
> >>> == Current Status ==
> >>>
> >>> Pulsar has been in service at large scale for more than 2 years at
> >> Yahoo. In
> >>> this time around 60 different applications were integrated with Pulsar.
> >> Other
> >>> companies are evaluating it as well and have been contributing code to
> >> the
> >>> project.
> >>>
> >>> === Meritocracy ===
> >>>
> >>> We value meritocracy and we understand that it is the basis to form an
> >> open
> >>> community that encourages multiple companies and individuals to
> >> contribute and
> >>> get

Re: Looking for additional mentor for Edgent with community growth ideas/focus

2017-05-17 Thread Martin Gainty 
my first impression when i first saw this 25 years ago when we stuffed network 
analytics into a MIB was that

as long as you have SNMP protocol stack and RIPv2 enabled gateway you could 
pass traffic info from Network device to NetworkDevice.

Cisco is probably the only company that picked up the ball on this concept with 
its own protocol IGMP

consequently I havent heard about network analytics as NA r disappeared into 
Cisco private domain

Given the fact that entire countries have gone dark because of what we called 
"network storm" now called Denial of Service does it not make sense to revive 
the concept of network-aware imps if for no other reason than to route traffic 
away from busy networks or networks burdened by DOS attack vectors.?


maybe this is pipe dream but if we can somehow config network devices to become 
self-aware and intelligently

route traffic away from heavily trafficked nodes and networks.. I could easily 
see these algorithms implemented by network intensive apps such as zookeeper 
and zookeeper under kafka


Salutations to all (including dogs)

WDYT?

Martin
__




From: Katherine Marsden 
Sent: Monday, May 15, 2017 3:31 PM
To: general@incubator.apache.org
Subject: Looking for additional mentor for Edgent with community growth 
ideas/focus

The Edgent community has just about all the pieces in place, great well
designed reliable software for analytics at the edge, great Apache Way
attitude and  understanding and open development from the committers and
ppmc members, successful releases and good documentation of the release
process, very welcoming to anyone who shows interest in joining the
community, no sticky legal or IP issues that I anticipate.

The only significant problem I see at this point is growing the size and
diversity of the user and development community.  Our last new committer
was a year ago and just saw only two new subscribers to the dev list in
our last reporting period.

I think it is a good time to bring on a new mentor for Edgent to help
kick start community growth.   Any interest?

At Apachecon this week there are a couple of talks about Edgent.  Please
attend if you are there and spread the word to anyone who might have
interest in either mentoring or getting involved in the Edgent community
or trying Edgent.  Please forward to anyone who might be interested.


Tuesday May 16 2:30 pm:
 * Video Analytics at the Edge: Fun with Apache Edgent, OpenCV and a
   Raspberry Pi - Dale LaBossiere and William Marshall, ppmc members and
   committers for Edgent.

Wednesday May 17: 12:15pm:
 * Having fun with Raspberry(s) and Apache Projects - Jean-Frederic
Clere.

Even if you can't come on as a mentor, I would most appreciate advice on
what the current mentors can do. I can imagine lots of applications, but
I don't have a lot of industry contacts now and will soon retire from my
day job and will have even fewer.  I will probably have some time to
yell, "Rah, Rah Edgent!" , but not sure my captive audience (my little
brown dog)  has real interest or contacts either.

Best

Kathey

About Edgent

Apache Edgent is a programming model and micro-kernel style runtime that
can be embedded in gateways and small footprint edge devices enabling
local, real-time, analytics on the continuous streams of data coming
from equipment, vehicles, systems, appliances, devices and sensors of
all kinds (for example, Raspberry Pis or smart phones). Working in
conjunction with centralized analytic systems, Apache Edgent provides
efficient and timely analytics across the whole IoT ecosystem: from the
center to the edge.


http://edgent.incubator.apache.org/
Apache Edgent
edgent.incubator.apache.org
Apache Edgent is a programming model and micro-kernel style runtime that can be 
embedded in gateways and small footprint edge devices enabling local, real-time 
...




-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Pulsar into the Apache Incubator

2017-05-17 Thread Julian Hyde 
+1 (binding)

> On May 17, 2017, at 1:58 PM, Jia Zhai  wrote:
> 
> +1 (non-binding)
> 
> On Thu, May 18, 2017 at 1:11 AM, P. Taylor Goetz  wrote:
> 
>> +1 (binding)
>> 
>> -Taylor
>> 
>>> On May 16, 2017, at 10:39 PM, Bryan Call  wrote:
>>> 
>>> Hi All,
>>> 
>>> As the champion for Pulsar, I would like to start a VOTE to bring the
>>> project in as Apache incubator podling.
>>> 
>>> The ASF voting rules are described:
>>> 
>>>   https://www.apache.org/foundation/voting.html
>>> 
>>> A vote for accepting a new Apache Incubator podling is a majority vote
>> for which
>>> only Incubator PMC member votes are binding.
>>> 
>>> This vote will run for at least 72 hours. Please VOTE as follows
>>> [] +1 Accept Pulsar into the Apache Incubator
>>> [] +0 Abstain.
>>> [] -1 Do not accept Pulsar into the Apache Incubator because ...
>>> 
>>> The proposal is listed below, but you can also access it on the wiki:
>>> 
>>>   https://wiki.apache.org/incubator/PulsarProposal
>>> 
>>> -Bryan
>>> 
>>> 
>>> = Pulsar Proposal =
>>> 
>>> == Abstract ==
>>> 
>>> Pulsar is a highly scalable, low latency messaging platform running on
>>> commodity hardware. It provides simple pub-sub semantics over topics,
>>> guaranteed at-least-once delivery of messages, automatic cursor
>> management for
>>> subscribers, and cross-datacenter replication.
>>> 
>>> == Proposal ==
>>> 
>>> Pub-sub messaging is a very common design pattern that is increasingly
>> found
>>> in distributed systems powering Internet applications. These applications
>>> provide real-time services, and need publish-latencies of 5ms on average
>> and
>>> no more than 15ms at the 99th percentile. At Internet scale, these
>>> applications require a messaging system with ordering, strong
>> durability, and
>>> delivery guarantees. In order to handle the “five 9’s” durability
>> requirements
>>> of a production environment, the messages have to be committed on
>> multiple
>>> disks or nodes.
>>> 
>>> Pulsar has been developed at Yahoo to address these specific
>> requirements by
>>> providing a hosted service supporting millions of topics for multiple
>> tenants.
>>> The current incarnation of Pulsar has been open-sourced under Apache
>> license
>>> in September 2016 and it is the direct evolution of systems that were
>>> developed at Yahoo since 2011.
>>> 
>>> We believe there is currently no other system that provides a
>> multi-tenant
>>> hosted messaging platform capable of supporting a huge number of topics
>> while
>>> maintaining strict guarantees for durability, ordering and low latency.
>>> Current solutions would require to run multiple individual clusters with
>>> additional operational work and capacity overhead.
>>> 
>>> Since the open sourcing of Pulsar, the development has been done
>> exclusively
>>> on the public Github repository and two major releases were shipped
>> (1.15 and
>>> 1.16), along with multiple minor ones. Several other companies have
>> expressed
>>> interest in the project and its future direction.
>>> 
>>> == Rationale ==
>>> 
>>> Pulsar is a platform that is built on top of several other Apache
>> projects. In
>>> particular, Apache BookKeeper is used to store the data and Apache
>> ZooKeeper
>>> is used for coordination and metadata storage. Pulsar is also
>> interoperable
>>> out of the box with Apache Storm, to provide an easy to use stream
>> processing
>>> solution.
>>> 
>>> We want to establish a community outside the scope of initial core
>> developers
>>> at Yahoo and we believe that the Apache Foundation is a great fit and
>> long-
>>> term home for Pulsar, as it provides an established process for
>> community-
>>> driven development and decision making by consensus. This is exactly the
>> model
>>> we want to adopt for future Pulsar development.
>>> 
>>> == Initial Goals ==
>>> 
>>> The initial goals will be to move the existing codebase to Apache and
>>> integrate with the Apache development process. Furthermore, we plan for
>>> incremental development, and releases along with the Apache guidelines.
>>> 
>>> == Current Status ==
>>> 
>>> Pulsar has been in service at large scale for more than 2 years at
>> Yahoo. In
>>> this time around 60 different applications were integrated with Pulsar.
>> Other
>>> companies are evaluating it as well and have been contributing code to
>> the
>>> project.
>>> 
>>> === Meritocracy ===
>>> 
>>> We value meritocracy and we understand that it is the basis to form an
>> open
>>> community that encourages multiple companies and individuals to
>> contribute and
>>> get invested in the project future. We will encourage and monitor
>>> participation and make sure to extend privileges and responsibilities to
>> all
>>> contributors.
>>> 
>>> === Community ===
>>> 
>>> We have validated, through the interest demonstrated by Pulsar users at
>> Yahoo,
>>> that a reliable hosted pub-sub messaging platform represent a very
>> important
>>> building

Re: [VOTE] Pulsar into the Apache Incubator

2017-05-17 Thread Jia Zhai 
+1 (non-binding)

On Thu, May 18, 2017 at 1:11 AM, P. Taylor Goetz  wrote:

> +1 (binding)
>
> -Taylor
>
> > On May 16, 2017, at 10:39 PM, Bryan Call  wrote:
> >
> > Hi All,
> >
> > As the champion for Pulsar, I would like to start a VOTE to bring the
> > project in as Apache incubator podling.
> >
> > The ASF voting rules are described:
> >
> >https://www.apache.org/foundation/voting.html
> >
> > A vote for accepting a new Apache Incubator podling is a majority vote
> for which
> > only Incubator PMC member votes are binding.
> >
> > This vote will run for at least 72 hours. Please VOTE as follows
> > [] +1 Accept Pulsar into the Apache Incubator
> > [] +0 Abstain.
> > [] -1 Do not accept Pulsar into the Apache Incubator because ...
> >
> > The proposal is listed below, but you can also access it on the wiki:
> >
> >https://wiki.apache.org/incubator/PulsarProposal
> >
> > -Bryan
> >
> >
> > = Pulsar Proposal =
> >
> > == Abstract ==
> >
> > Pulsar is a highly scalable, low latency messaging platform running on
> > commodity hardware. It provides simple pub-sub semantics over topics,
> > guaranteed at-least-once delivery of messages, automatic cursor
> management for
> > subscribers, and cross-datacenter replication.
> >
> > == Proposal ==
> >
> > Pub-sub messaging is a very common design pattern that is increasingly
> found
> > in distributed systems powering Internet applications. These applications
> > provide real-time services, and need publish-latencies of 5ms on average
> and
> > no more than 15ms at the 99th percentile. At Internet scale, these
> > applications require a messaging system with ordering, strong
> durability, and
> > delivery guarantees. In order to handle the “five 9’s” durability
> requirements
> > of a production environment, the messages have to be committed on
> multiple
> > disks or nodes.
> >
> > Pulsar has been developed at Yahoo to address these specific
> requirements by
> > providing a hosted service supporting millions of topics for multiple
> tenants.
> > The current incarnation of Pulsar has been open-sourced under Apache
> license
> > in September 2016 and it is the direct evolution of systems that were
> > developed at Yahoo since 2011.
> >
> > We believe there is currently no other system that provides a
> multi-tenant
> > hosted messaging platform capable of supporting a huge number of topics
> while
> > maintaining strict guarantees for durability, ordering and low latency.
> > Current solutions would require to run multiple individual clusters with
> > additional operational work and capacity overhead.
> >
> > Since the open sourcing of Pulsar, the development has been done
> exclusively
> > on the public Github repository and two major releases were shipped
> (1.15 and
> > 1.16), along with multiple minor ones. Several other companies have
> expressed
> > interest in the project and its future direction.
> >
> > == Rationale ==
> >
> > Pulsar is a platform that is built on top of several other Apache
> projects. In
> > particular, Apache BookKeeper is used to store the data and Apache
> ZooKeeper
> > is used for coordination and metadata storage. Pulsar is also
> interoperable
> > out of the box with Apache Storm, to provide an easy to use stream
> processing
> > solution.
> >
> > We want to establish a community outside the scope of initial core
> developers
> > at Yahoo and we believe that the Apache Foundation is a great fit and
> long-
> > term home for Pulsar, as it provides an established process for
> community-
> > driven development and decision making by consensus. This is exactly the
> model
> > we want to adopt for future Pulsar development.
> >
> > == Initial Goals ==
> >
> > The initial goals will be to move the existing codebase to Apache and
> > integrate with the Apache development process. Furthermore, we plan for
> > incremental development, and releases along with the Apache guidelines.
> >
> > == Current Status ==
> >
> > Pulsar has been in service at large scale for more than 2 years at
> Yahoo. In
> > this time around 60 different applications were integrated with Pulsar.
> Other
> > companies are evaluating it as well and have been contributing code to
> the
> > project.
> >
> > === Meritocracy ===
> >
> > We value meritocracy and we understand that it is the basis to form an
> open
> > community that encourages multiple companies and individuals to
> contribute and
> > get invested in the project future. We will encourage and monitor
> > participation and make sure to extend privileges and responsibilities to
> all
> > contributors.
> >
> > === Community ===
> >
> > We have validated, through the interest demonstrated by Pulsar users at
> Yahoo,
> > that a reliable hosted pub-sub messaging platform represent a very
> important
> > building block for web-scale distributed applications. We believe that
> many
> > companies can benefit by applying the same model and that bringing
> Pulsar to
> >

Re: [VOTE] Pulsar into the Apache Incubator

2017-05-17 Thread P. Taylor Goetz 
+1 (binding)

-Taylor

> On May 16, 2017, at 10:39 PM, Bryan Call  wrote:
> 
> Hi All,
> 
> As the champion for Pulsar, I would like to start a VOTE to bring the
> project in as Apache incubator podling.
> 
> The ASF voting rules are described:
> 
>https://www.apache.org/foundation/voting.html
> 
> A vote for accepting a new Apache Incubator podling is a majority vote for 
> which 
> only Incubator PMC member votes are binding.
> 
> This vote will run for at least 72 hours. Please VOTE as follows
> [] +1 Accept Pulsar into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept Pulsar into the Apache Incubator because ...
> 
> The proposal is listed below, but you can also access it on the wiki:
> 
>https://wiki.apache.org/incubator/PulsarProposal
> 
> -Bryan
> 
> 
> = Pulsar Proposal =
> 
> == Abstract ==
> 
> Pulsar is a highly scalable, low latency messaging platform running on
> commodity hardware. It provides simple pub-sub semantics over topics,
> guaranteed at-least-once delivery of messages, automatic cursor management for
> subscribers, and cross-datacenter replication.
> 
> == Proposal ==
> 
> Pub-sub messaging is a very common design pattern that is increasingly found
> in distributed systems powering Internet applications. These applications
> provide real-time services, and need publish-latencies of 5ms on average and
> no more than 15ms at the 99th percentile. At Internet scale, these
> applications require a messaging system with ordering, strong durability, and
> delivery guarantees. In order to handle the “five 9’s” durability requirements
> of a production environment, the messages have to be committed on multiple
> disks or nodes.
> 
> Pulsar has been developed at Yahoo to address these specific requirements by
> providing a hosted service supporting millions of topics for multiple tenants.
> The current incarnation of Pulsar has been open-sourced under Apache license
> in September 2016 and it is the direct evolution of systems that were
> developed at Yahoo since 2011.
> 
> We believe there is currently no other system that provides a multi-tenant
> hosted messaging platform capable of supporting a huge number of topics while
> maintaining strict guarantees for durability, ordering and low latency.
> Current solutions would require to run multiple individual clusters with
> additional operational work and capacity overhead.
> 
> Since the open sourcing of Pulsar, the development has been done exclusively
> on the public Github repository and two major releases were shipped (1.15 and
> 1.16), along with multiple minor ones. Several other companies have expressed
> interest in the project and its future direction.
> 
> == Rationale ==
> 
> Pulsar is a platform that is built on top of several other Apache projects. In
> particular, Apache BookKeeper is used to store the data and Apache ZooKeeper
> is used for coordination and metadata storage. Pulsar is also interoperable
> out of the box with Apache Storm, to provide an easy to use stream processing
> solution.
> 
> We want to establish a community outside the scope of initial core developers
> at Yahoo and we believe that the Apache Foundation is a great fit and long-
> term home for Pulsar, as it provides an established process for community-
> driven development and decision making by consensus. This is exactly the model
> we want to adopt for future Pulsar development.
> 
> == Initial Goals ==
> 
> The initial goals will be to move the existing codebase to Apache and
> integrate with the Apache development process. Furthermore, we plan for
> incremental development, and releases along with the Apache guidelines.
> 
> == Current Status ==
> 
> Pulsar has been in service at large scale for more than 2 years at Yahoo. In
> this time around 60 different applications were integrated with Pulsar. Other
> companies are evaluating it as well and have been contributing code to the
> project.
> 
> === Meritocracy ===
> 
> We value meritocracy and we understand that it is the basis to form an open
> community that encourages multiple companies and individuals to contribute and
> get invested in the project future. We will encourage and monitor
> participation and make sure to extend privileges and responsibilities to all
> contributors.
> 
> === Community ===
> 
> We have validated, through the interest demonstrated by Pulsar users at Yahoo,
> that a reliable hosted pub-sub messaging platform represent a very important
> building block for web-scale distributed applications. We believe that many
> companies can benefit by applying the same model and that bringing Pulsar to
> Apache will get the community to grow stronger.
> 
> === Core Developers ===
> 
> Pulsar has been initially developed at Yahoo and received significant
> contributions from Yahoo Japan. After having open-sourced the project there
> have been contribution from developers from several external companies.
> 
> === Alignment ===
> 
> Pulsar builds

Re: [VOTE] Pulsar into the Apache Incubator

2017-05-17 Thread Phil Sorber 
+1 (binding)

On Wed, May 17, 2017 at 8:21 AM Jim Jagielski  wrote:

> Make it so! +1! (binding)
>
> > On May 16, 2017, at 10:39 PM, Bryan Call  wrote:
> >
> > Hi All,
> >
> > As the champion for Pulsar, I would like to start a VOTE to bring the
> > project in as Apache incubator podling.
> >
> > The ASF voting rules are described:
> >
> >   https://www.apache.org/foundation/voting.html
> >
> > A vote for accepting a new Apache Incubator podling is a majority vote
> for which
> > only Incubator PMC member votes are binding.
> >
> > This vote will run for at least 72 hours. Please VOTE as follows
> > [] +1 Accept Pulsar into the Apache Incubator
> > [] +0 Abstain.
> > [] -1 Do not accept Pulsar into the Apache Incubator because ...
> >
> > The proposal is listed below, but you can also access it on the wiki:
> >
> >   https://wiki.apache.org/incubator/PulsarProposal
> >
> > -Bryan
> >
> >
> > = Pulsar Proposal =
> >
> > == Abstract ==
> >
> > Pulsar is a highly scalable, low latency messaging platform running on
> > commodity hardware. It provides simple pub-sub semantics over topics,
> > guaranteed at-least-once delivery of messages, automatic cursor
> management for
> > subscribers, and cross-datacenter replication.
> >
> > == Proposal ==
> >
> > Pub-sub messaging is a very common design pattern that is increasingly
> found
> > in distributed systems powering Internet applications. These applications
> > provide real-time services, and need publish-latencies of 5ms on average
> and
> > no more than 15ms at the 99th percentile. At Internet scale, these
> > applications require a messaging system with ordering, strong
> durability, and
> > delivery guarantees. In order to handle the “five 9’s” durability
> requirements
> > of a production environment, the messages have to be committed on
> multiple
> > disks or nodes.
> >
> > Pulsar has been developed at Yahoo to address these specific
> requirements by
> > providing a hosted service supporting millions of topics for multiple
> tenants.
> > The current incarnation of Pulsar has been open-sourced under Apache
> license
> > in September 2016 and it is the direct evolution of systems that were
> > developed at Yahoo since 2011.
> >
> > We believe there is currently no other system that provides a
> multi-tenant
> > hosted messaging platform capable of supporting a huge number of topics
> while
> > maintaining strict guarantees for durability, ordering and low latency.
> > Current solutions would require to run multiple individual clusters with
> > additional operational work and capacity overhead.
> >
> > Since the open sourcing of Pulsar, the development has been done
> exclusively
> > on the public Github repository and two major releases were shipped
> (1.15 and
> > 1.16), along with multiple minor ones. Several other companies have
> expressed
> > interest in the project and its future direction.
> >
> > == Rationale ==
> >
> > Pulsar is a platform that is built on top of several other Apache
> projects. In
> > particular, Apache BookKeeper is used to store the data and Apache
> ZooKeeper
> > is used for coordination and metadata storage. Pulsar is also
> interoperable
> > out of the box with Apache Storm, to provide an easy to use stream
> processing
> > solution.
> >
> > We want to establish a community outside the scope of initial core
> developers
> > at Yahoo and we believe that the Apache Foundation is a great fit and
> long-
> > term home for Pulsar, as it provides an established process for
> community-
> > driven development and decision making by consensus. This is exactly the
> model
> > we want to adopt for future Pulsar development.
> >
> > == Initial Goals ==
> >
> > The initial goals will be to move the existing codebase to Apache and
> > integrate with the Apache development process. Furthermore, we plan for
> > incremental development, and releases along with the Apache guidelines.
> >
> > == Current Status ==
> >
> > Pulsar has been in service at large scale for more than 2 years at
> Yahoo. In
> > this time around 60 different applications were integrated with Pulsar.
> Other
> > companies are evaluating it as well and have been contributing code to
> the
> > project.
> >
> > === Meritocracy ===
> >
> > We value meritocracy and we understand that it is the basis to form an
> open
> > community that encourages multiple companies and individuals to
> contribute and
> > get invested in the project future. We will encourage and monitor
> > participation and make sure to extend privileges and responsibilities to
> all
> > contributors.
> >
> > === Community ===
> >
> > We have validated, through the interest demonstrated by Pulsar users at
> Yahoo,
> > that a reliable hosted pub-sub messaging platform represent a very
> important
> > building block for web-scale distributed applications. We believe that
> many
> > companies can benefit by applying the same model and that bringing
> Pulsar to
> >

Re: [VOTE]: Apache Weex-incubating Release 0.12.0-RC4

2017-05-17 Thread John D. Ament 
sospartan,

Couple of things noticed:

- Your email still points to your non-ASF hosted website.  Don't forget to
point to your ASF website.
- The source release still contains a sub-directory.
- Its still not clear to me how to create the binary.
- Your package.json points still to old alibaba repos and not ASF repos

I would like to see these 4 issues fixed for next release.

LICENSE file looks good, minor typos (still need to fix the extra comments)
NOTICE file looks fine
DISCLAIMER is present.
No binaries that I can find.

+1

John

On Mon, May 15, 2017 at 5:24 AM sospartan  wrote:

> Hi IPMC,
>
> I'm calling a vote for Weex-incubating 0.12.0-RC4 release.
> In this release, source tarball only include files necessary to build Weex
> SDK.
> All binaries were excluded.
> A build README(README_RELEASE.md)  is in the tarball now.
>
> Thanks for peoples who were taking time to review our last RC (RC3). I'm
> Hoping
> this RC is doing better.
>
> The PPMC vote for this release has passed:
> https://lists.apache.org/thread.html/0e05de680b315e453fe8643ff297d5
> ebfb9cdd30ea2c982e33854ff5@%3Cdev.weex.apache.org%3E
>
> The tag to be voted upon:
> https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git
> ;a=shortlog;h=refs/tags/0.12.0-rc4
>
> The commit hash:
> https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=commit;h=
> e19ef8a4acc39cd8db2cf3be4f8369f6d7a0bb43
> 
>
> The source tarball can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/weex/0.12.0-incubating/RC4/
>
> The fingerprint of key to sign release artifacts:
> 97B9 6598 A6A3 B63C 53BD  77E9 44C5 2286 22B9 7784
>
> Release artifacts are signed with the following key:
> https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS
>
> Release note about this version:
> https://issues.apache.org/jira/browse/WEEX-26
>
> This vote will remain open for at least 72 hours.
> Please vote on releasing this RC.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> --
> Best Regards!
> --
>
> sospartan
> https://weex-project.io
>

Re: [VOTE] Pulsar into the Apache Incubator

2017-05-17 Thread Jim Jagielski 
Make it so! +1! (binding)

> On May 16, 2017, at 10:39 PM, Bryan Call  wrote:
> 
> Hi All,
> 
> As the champion for Pulsar, I would like to start a VOTE to bring the
> project in as Apache incubator podling.
> 
> The ASF voting rules are described:
> 
>   https://www.apache.org/foundation/voting.html
> 
> A vote for accepting a new Apache Incubator podling is a majority vote for 
> which 
> only Incubator PMC member votes are binding.
> 
> This vote will run for at least 72 hours. Please VOTE as follows
> [] +1 Accept Pulsar into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept Pulsar into the Apache Incubator because ...
> 
> The proposal is listed below, but you can also access it on the wiki:
> 
>   https://wiki.apache.org/incubator/PulsarProposal
> 
> -Bryan
> 
> 
> = Pulsar Proposal =
> 
> == Abstract ==
> 
> Pulsar is a highly scalable, low latency messaging platform running on
> commodity hardware. It provides simple pub-sub semantics over topics,
> guaranteed at-least-once delivery of messages, automatic cursor management for
> subscribers, and cross-datacenter replication.
> 
> == Proposal ==
> 
> Pub-sub messaging is a very common design pattern that is increasingly found
> in distributed systems powering Internet applications. These applications
> provide real-time services, and need publish-latencies of 5ms on average and
> no more than 15ms at the 99th percentile. At Internet scale, these
> applications require a messaging system with ordering, strong durability, and
> delivery guarantees. In order to handle the “five 9’s” durability requirements
> of a production environment, the messages have to be committed on multiple
> disks or nodes.
> 
> Pulsar has been developed at Yahoo to address these specific requirements by
> providing a hosted service supporting millions of topics for multiple tenants.
> The current incarnation of Pulsar has been open-sourced under Apache license
> in September 2016 and it is the direct evolution of systems that were
> developed at Yahoo since 2011.
> 
> We believe there is currently no other system that provides a multi-tenant
> hosted messaging platform capable of supporting a huge number of topics while
> maintaining strict guarantees for durability, ordering and low latency.
> Current solutions would require to run multiple individual clusters with
> additional operational work and capacity overhead.
> 
> Since the open sourcing of Pulsar, the development has been done exclusively
> on the public Github repository and two major releases were shipped (1.15 and
> 1.16), along with multiple minor ones. Several other companies have expressed
> interest in the project and its future direction.
> 
> == Rationale ==
> 
> Pulsar is a platform that is built on top of several other Apache projects. In
> particular, Apache BookKeeper is used to store the data and Apache ZooKeeper
> is used for coordination and metadata storage. Pulsar is also interoperable
> out of the box with Apache Storm, to provide an easy to use stream processing
> solution.
> 
> We want to establish a community outside the scope of initial core developers
> at Yahoo and we believe that the Apache Foundation is a great fit and long-
> term home for Pulsar, as it provides an established process for community-
> driven development and decision making by consensus. This is exactly the model
> we want to adopt for future Pulsar development.
> 
> == Initial Goals ==
> 
> The initial goals will be to move the existing codebase to Apache and
> integrate with the Apache development process. Furthermore, we plan for
> incremental development, and releases along with the Apache guidelines.
> 
> == Current Status ==
> 
> Pulsar has been in service at large scale for more than 2 years at Yahoo. In
> this time around 60 different applications were integrated with Pulsar. Other
> companies are evaluating it as well and have been contributing code to the
> project.
> 
> === Meritocracy ===
> 
> We value meritocracy and we understand that it is the basis to form an open
> community that encourages multiple companies and individuals to contribute and
> get invested in the project future. We will encourage and monitor
> participation and make sure to extend privileges and responsibilities to all
> contributors.
> 
> === Community ===
> 
> We have validated, through the interest demonstrated by Pulsar users at Yahoo,
> that a reliable hosted pub-sub messaging platform represent a very important
> building block for web-scale distributed applications. We believe that many
> companies can benefit by applying the same model and that bringing Pulsar to
> Apache will get the community to grow stronger.
> 
> === Core Developers ===
> 
> Pulsar has been initially developed at Yahoo and received significant
> contributions from Yahoo Japan. After having open-sourced the project there
> have been contribution from developers from several external companies.
> 
> === Alignment ===
> 
>

Re: [VOTE] Pulsar into the Apache Incubator

2017-05-17 Thread Jean-Baptiste Onofré 

+1 (binding)

Regards
JB

On 05/17/2017 04:39 AM, Bryan Call wrote:

Hi All,

As the champion for Pulsar, I would like to start a VOTE to bring the
project in as Apache incubator podling.

The ASF voting rules are described:

https://www.apache.org/foundation/voting.html

A vote for accepting a new Apache Incubator podling is a majority vote for which
only Incubator PMC member votes are binding.

This vote will run for at least 72 hours. Please VOTE as follows
[] +1 Accept Pulsar into the Apache Incubator
[] +0 Abstain.
[] -1 Do not accept Pulsar into the Apache Incubator because ...

The proposal is listed below, but you can also access it on the wiki:

https://wiki.apache.org/incubator/PulsarProposal

-Bryan


= Pulsar Proposal =

== Abstract ==

Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor management for
subscribers, and cross-datacenter replication.

== Proposal ==

Pub-sub messaging is a very common design pattern that is increasingly found
in distributed systems powering Internet applications. These applications
provide real-time services, and need publish-latencies of 5ms on average and
no more than 15ms at the 99th percentile. At Internet scale, these
applications require a messaging system with ordering, strong durability, and
delivery guarantees. In order to handle the “five 9’s” durability requirements
of a production environment, the messages have to be committed on multiple
disks or nodes.

Pulsar has been developed at Yahoo to address these specific requirements by
providing a hosted service supporting millions of topics for multiple tenants.
The current incarnation of Pulsar has been open-sourced under Apache license
in September 2016 and it is the direct evolution of systems that were
developed at Yahoo since 2011.

We believe there is currently no other system that provides a multi-tenant
hosted messaging platform capable of supporting a huge number of topics while
maintaining strict guarantees for durability, ordering and low latency.
Current solutions would require to run multiple individual clusters with
additional operational work and capacity overhead.

Since the open sourcing of Pulsar, the development has been done exclusively
on the public Github repository and two major releases were shipped (1.15 and
1.16), along with multiple minor ones. Several other companies have expressed
interest in the project and its future direction.

== Rationale ==

Pulsar is a platform that is built on top of several other Apache projects. In
particular, Apache BookKeeper is used to store the data and Apache ZooKeeper
is used for coordination and metadata storage. Pulsar is also interoperable
out of the box with Apache Storm, to provide an easy to use stream processing
solution.

We want to establish a community outside the scope of initial core developers
at Yahoo and we believe that the Apache Foundation is a great fit and long-
term home for Pulsar, as it provides an established process for community-
driven development and decision making by consensus. This is exactly the model
we want to adopt for future Pulsar development.

== Initial Goals ==

The initial goals will be to move the existing codebase to Apache and
integrate with the Apache development process. Furthermore, we plan for
incremental development, and releases along with the Apache guidelines.

== Current Status ==

Pulsar has been in service at large scale for more than 2 years at Yahoo. In
this time around 60 different applications were integrated with Pulsar. Other
companies are evaluating it as well and have been contributing code to the
project.

=== Meritocracy ===

We value meritocracy and we understand that it is the basis to form an open
community that encourages multiple companies and individuals to contribute and
get invested in the project future. We will encourage and monitor
participation and make sure to extend privileges and responsibilities to all
contributors.

=== Community ===

We have validated, through the interest demonstrated by Pulsar users at Yahoo,
that a reliable hosted pub-sub messaging platform represent a very important
building block for web-scale distributed applications. We believe that many
companies can benefit by applying the same model and that bringing Pulsar to
Apache will get the community to grow stronger.

=== Core Developers ===

Pulsar has been initially developed at Yahoo and received significant
contributions from Yahoo Japan. After having open-sourced the project there
have been contribution from developers from several external companies.

=== Alignment ===

Pulsar builds upon other Apache projects such as ZooKeeper and BookKeeper,
along with a number of other Apache libraries. We have already integrated with
Storm and we envision to integrate with multiple other systems in the
streaming and big data space.

==

Re: [VOTE] Pulsar into the Apache Incubator

2017-05-17 Thread Dave Fisher 
+1 (binding)

Regards,
Dave

Sent from my iPhone

> On May 16, 2017, at 10:39 PM, Bryan Call  wrote:
> 
> Hi All,
> 
> As the champion for Pulsar, I would like to start a VOTE to bring the
> project in as Apache incubator podling.
> 
> The ASF voting rules are described:
> 
>https://www.apache.org/foundation/voting.html
> 
> A vote for accepting a new Apache Incubator podling is a majority vote for 
> which 
> only Incubator PMC member votes are binding.
> 
> This vote will run for at least 72 hours. Please VOTE as follows
> [] +1 Accept Pulsar into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept Pulsar into the Apache Incubator because ...
> 
> The proposal is listed below, but you can also access it on the wiki:
> 
>https://wiki.apache.org/incubator/PulsarProposal
> 
> -Bryan
> 
> 
> = Pulsar Proposal =
> 
> == Abstract ==
> 
> Pulsar is a highly scalable, low latency messaging platform running on
> commodity hardware. It provides simple pub-sub semantics over topics,
> guaranteed at-least-once delivery of messages, automatic cursor management for
> subscribers, and cross-datacenter replication.
> 
> == Proposal ==
> 
> Pub-sub messaging is a very common design pattern that is increasingly found
> in distributed systems powering Internet applications. These


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Looking for additional mentors for weex-incubating

2017-05-17 Thread sospartan 
I'm very grateful to you for this.

I've make some changes to the source release and start new RC vote in
another thread:
https://lists.apache.org/thread.html/9e9308203feb3e9651644e7bef6578a50cf21a4a0513bd6175e1fb53@%3Cgeneral.incubator.apache.org%3E

I believe we can finally get there.
Thank you.


On Wed, May 17, 2017 at 5:44 PM, Raphael Bircher 
wrote:

> Hi sospartan
>
> Yea, I see, there are several issues. I will not act as an official
> mentor, but I subscribed the dev list, and we'll see what we can do.
>
> Regards Raphael
>
> Am .05.2017, 11:24 Uhr, schrieb sospartan :
>
> Weex has been incubating since 2016-11-30. Now we are working forward to
>> our first
>> apache release. Because our 4 mentors are mostly absent. Now we are
>> looking
>> for
>> additional mentors to join us.
>>
>> Anybody from IPMC interesting in weex is welcomed. Most (probably all) of
>> our
>> committers and contributors are new to ASF, we are still try to learn the
>> apache-way.
>> Especially, there are lots issues about our release according last RC
>> vote.
>> We need
>>  mentors to guide the community.
>>
>>
>
> --
> My introduction https://youtu.be/Ln4vly5sxYU
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
sospartan
Phone:13588488290
HangZhou

Re: Looking for additional mentors for weex-incubating

2017-05-17 Thread Raphael Bircher 

Hi sospartan

Yea, I see, there are several issues. I will not act as an official  
mentor, but I subscribed the dev list, and we'll see what we can do.


Regards Raphael

Am .05.2017, 11:24 Uhr, schrieb sospartan :


Weex has been incubating since 2016-11-30. Now we are working forward to
our first
apache release. Because our 4 mentors are mostly absent. Now we are  
looking

for
additional mentors to join us.

Anybody from IPMC interesting in weex is welcomed. Most (probably all) of
our
committers and contributors are new to ASF, we are still try to learn the
apache-way.
Especially, there are lots issues about our release according last RC  
vote.

We need
 mentors to guide the community.




--
My introduction https://youtu.be/Ln4vly5sxYU

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Looking for additional mentors for weex-incubating

2017-05-17 Thread sospartan 
Weex has been incubating since 2016-11-30. Now we are working forward to
our first
apache release. Because our 4 mentors are mostly absent. Now we are looking
for
additional mentors to join us.

Anybody from IPMC interesting in weex is welcomed. Most (probably all) of
our
committers and contributors are new to ASF, we are still try to learn the
apache-way.
Especially, there are lots issues about our release according last RC vote.
We need
 mentors to guide the community.

-- 
Best Regards!
--

sospartan

Weex is a framework for building Mobile cross-platform high performance UI.

Re: [VOTE]: Apache Weex-incubating Release 0.12.0-RC4

2017-05-17 Thread sospartan 
Could anyone from IPMC review this release?


On Mon, May 15, 2017 at 5:23 PM, sospartan  wrote:

> Hi IPMC,
>
> I'm calling a vote for Weex-incubating 0.12.0-RC4 release.
> In this release, source tarball only include files necessary to build Weex
> SDK.
> All binaries were excluded.
> A build README(README_RELEASE.md)  is in the tarball now.
>
> Thanks for peoples who were taking time to review our last RC (RC3). I'm
> Hoping
> this RC is doing better.
>
> The PPMC vote for this release has passed:
> https://lists.apache.org/thread.html/0e05de680b315e453f
> e8643ff297d5ebfb9cdd30ea2c982e33854ff5@%3Cdev.weex.apache.org%3E
>
> The tag to be voted upon:
> https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git
> ;a=shortlog;h=refs/tags/0.12.0-rc4
>
> The commit hash:
> https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git
> ;a=commit;h=e19ef8a4acc39cd8db2cf3be4f8369f6d7a0bb43
>
> The source tarball can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/weex/0.12.0
> -incubating/RC4/
>
> The fingerprint of key to sign release artifacts:
> 97B9 6598 A6A3 B63C 53BD  77E9 44C5 2286 22B9 7784
>
> Release artifacts are signed with the following key:
> https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS
>
> Release note about this version:
> https://issues.apache.org/jira/browse/WEEX-26
>
> This vote will remain open for at least 72 hours.
> Please vote on releasing this RC.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> --
> Best Regards!
> --
>
> sospartan
> https://weex-project.io
>



-- 
Best Regards!
--

sospartan
https://weex-project.io

Re: [VOTE] Pulsar into the Apache Incubator

2017-05-17 Thread Raphael Bircher 

+1 (binding)

Am .05.2017, 04:39 Uhr, schrieb Bryan Call :


Hi All,

As the champion for Pulsar, I would like to start a VOTE to bring the
project in as Apache incubator podling.

The ASF voting rules are described:

https://www.apache.org/foundation/voting.html

A vote for accepting a new Apache Incubator podling is a majority vote  
for which

only Incubator PMC member votes are binding.

This vote will run for at least 72 hours. Please VOTE as follows
[] +1 Accept Pulsar into the Apache Incubator
[] +0 Abstain.
[] -1 Do not accept Pulsar into the Apache Incubator because ...

The proposal is listed below, but you can also access it on the wiki:

https://wiki.apache.org/incubator/PulsarProposal

-Bryan


= Pulsar Proposal =

== Abstract ==

Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor  
management for

subscribers, and cross-datacenter replication.

== Proposal ==

Pub-sub messaging is a very common design pattern that is increasingly  
found

in distributed systems powering Internet applications. These applications
provide real-time services, and need publish-latencies of 5ms on average  
and

no more than 15ms at the 99th percentile. At Internet scale, these
applications require a messaging system with ordering, strong  
durability, and
delivery guarantees. In order to handle the “five 9’s” durability  
requirements
of a production environment, the messages have to be committed on  
multiple

disks or nodes.

Pulsar has been developed at Yahoo to address these specific  
requirements by
providing a hosted service supporting millions of topics for multiple  
tenants.
The current incarnation of Pulsar has been open-sourced under Apache  
license

in September 2016 and it is the direct evolution of systems that were
developed at Yahoo since 2011.

We believe there is currently no other system that provides a  
multi-tenant
hosted messaging platform capable of supporting a huge number of topics  
while

maintaining strict guarantees for durability, ordering and low latency.
Current solutions would require to run multiple individual clusters with
additional operational work and capacity overhead.

Since the open sourcing of Pulsar, the development has been done  
exclusively
on the public Github repository and two major releases were shipped  
(1.15 and
1.16), along with multiple minor ones. Several other companies have  
expressed

interest in the project and its future direction.

== Rationale ==

Pulsar is a platform that is built on top of several other Apache  
projects. In
particular, Apache BookKeeper is used to store the data and Apache  
ZooKeeper
is used for coordination and metadata storage. Pulsar is also  
interoperable
out of the box with Apache Storm, to provide an easy to use stream  
processing

solution.

We want to establish a community outside the scope of initial core  
developers
at Yahoo and we believe that the Apache Foundation is a great fit and  
long-
term home for Pulsar, as it provides an established process for  
community-
driven development and decision making by consensus. This is exactly the  
model

we want to adopt for future Pulsar development.

== Initial Goals ==

The initial goals will be to move the existing codebase to Apache and
integrate with the Apache development process. Furthermore, we plan for
incremental development, and releases along with the Apache guidelines.

== Current Status ==

Pulsar has been in service at large scale for more than 2 years at  
Yahoo. In
this time around 60 different applications were integrated with Pulsar.  
Other
companies are evaluating it as well and have been contributing code to  
the

project.

=== Meritocracy ===

We value meritocracy and we understand that it is the basis to form an  
open
community that encourages multiple companies and individuals to  
contribute and

get invested in the project future. We will encourage and monitor
participation and make sure to extend privileges and responsibilities to  
all

contributors.

=== Community ===

We have validated, through the interest demonstrated by Pulsar users at  
Yahoo,
that a reliable hosted pub-sub messaging platform represent a very  
important
building block for web-scale distributed applications. We believe that  
many
companies can benefit by applying the same model and that bringing  
Pulsar to

Apache will get the community to grow stronger.

=== Core Developers ===

Pulsar has been initially developed at Yahoo and received significant
contributions from Yahoo Japan. After having open-sourced the project  
there

have been contribution from developers from several external companies.

=== Alignment ===

Pulsar builds upon other Apache projects such as ZooKeeper and  
BookKeeper,
along with a number of other Apache libraries. We have already  
integrated with

Storm