Re: [RESTART] [VOTE] Graduate Apache Beam

[Von Gosling]

+1

> 在 2016年12月6日，07:30，Davor Bonaci  写道：
> 
> Hi everyone,
> Please vote on the draft resolution proposed by the Apache Beam PPMC below,
> which establishes Apache Beam as a new top-level project at the Apache
> Software Foundation, as follows:
> 
> [ ] +1, Graduate Apache Beam from the Incubator.
> [ ] +0, Don't care.
> [ ] -1, Don't graduate Apache Beam from the Incubator because...
> 
> Please note that this is a restarted vote, per John's request, to clarify
> the alternatives. The old voting thread is archived [1].
> 
> Before voting, please see the full text of the draft resolution below and
> the corresponding discussion thread [2], and vote only after you feel ready
> to do so. The vote will be open for at least 72 hours. This is a procedural
> vote [3]; it is adopted by a simple majority of qualified votes (with no
> minimum).
> 
> If approved by the Apache Incubator, the proposed resolution will be
> submitted to the Board of Directors for their consideration.
> 
> Thank you!
> 
> Davor
> 
> [1]
> https://lists.apache.org/thread.html/a8e9cecfe93f0e464cc7c1774d2761ca14326df1101b7670ca8b1dc3@%3Cgeneral.incubator.apache.org%3E
> [2]
> https://lists.apache.org/thread.html/b9c1071b35558846836814575ada3cdca61c72dc1e672ab994a9c936@%3Cgeneral.incubator.apache.org%3E
> [3] http://apache.org/foundation/voting.html
> 
> The full-text of the draft resolution proposed by the Apache Beam PPMC:
> 
>X. Establish the Apache Beam Project
> 
>   WHEREAS, the Board of Directors deems it to be in the best
>   interests of the Foundation and consistent with the
>   Foundation's purpose to establish a Project Management
>   Committee charged with the creation and maintenance of
>   open-source software, for distribution at no charge to
>   the public, related to a unified programming model for both
>   batch and streaming data processing, enabling efficient
>   execution across diverse distributed execution engines
>   and providing extensibility points for connecting to different
>   technologies and user communities.
> 
>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>   Committee (PMC), to be known as the "Apache Beam Project",
>   be and hereby is established pursuant to Bylaws of the
>   Foundation; and be it further
> 
>   RESOLVED, that the Apache Beam Project be and hereby is
>   responsible for the creation and maintenance of software
>   related to a unified programming model for both batch and
>   streaming data processing, enabling efficient execution across
>   diverse distributed execution engines and providing extensibility
>   points for connecting to different technologies and user
>   communities; and be it further
> 
>   RESOLVED, that the office of "Vice President, Apache Beam" be
>   and hereby is created, the person holding such office to
>   serve at the direction of the Board of Directors as the chair
>   of the Apache Beam Project, and to have primary responsibility
>   for management of the projects within the scope of
>   responsibility of the Apache Beam Project; and be it further
> 
>   RESOLVED, that the persons listed immediately below be and
>   hereby are appointed to serve as the initial members of the
>   Apache Beam Project:
> 
> * Tyler Akidau 
> * Davor Bonaci 
> * Robert Bradshaw 
> * Ben Chambers 
> * Luke Cwik 
> * Stephan Ewen 
> * Dan Halperin 
> * Kenneth Knowles 
> * Aljoscha Krettek 
> * Maximilian Michels 
> * Jean-Baptiste Onofré 
> * Frances Perry 
> * Amit Sela 
> * Josh Wills 
> 
>   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Davor Bonaci
>   be appointed to the office of Vice President, Apache Beam, to
>   serve in accordance with and subject to the direction of the
>   Board of Directors and the Bylaws of the Foundation until
>   death, resignation, retirement, removal or disqualification,
>   or until a successor is appointed; and be it further
> 
>   RESOLVED, that the initial Apache Beam PMC be and hereby is
>   tasked with the creation of a set of bylaws intended to
>   encourage open development and increased participation in the
>   Apache Beam Project; and be it further
> 
>   RESOLVED, that the Apache Beam Project be and hereby
>   is tasked with the migration and rationalization of the Apache
>   Incubator Beam podling; and be it further
> 
>   RESOLVED, that all responsibilities pertaining to the Apache
>   Incubator Beam podling encumbered upon the Apache Incubator
>   Project are hereafter discharged.


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

Re: [VOTE]: Release Apache RocketMQ 4.0.0(incubating) (RC3)

[Von Gosling]

I also want to know the correct distribution about NOTICE and LICENSE. also 
including the LICENSE and LICENSE-BIN(why we must list the 2 different license 
files when in source and bundle. it seems to different in many apache projects 
.we are confused when refering these projects )

IMO, if have some clear guide for this problem. may be a good help for our 
incubator project :-)


> 在 2017年2月17日，08:27，John D. Ament  写道：
> 
> On Thu, Feb 16, 2017 at 12:32 PM Bruce Snyder 
> wrote:
> 
>> +1 (binding)
>> 
>> No showstopper issues found, only minor issues that will be ironed out in
>> subsequent releases (e.g., README needs some cleanup, need consistency in
>> artifact naming).
>> 
> 
> Do you have a full list of those issues?  Here's problems I see
> (non-exhaustive):
> 
> - README points to "rocketmq community" as a github page
> - LICENSE/NOTICE are not consistent for the bin files. (there should be
> more apache licensed stuff in the bin than actually present)
>  - fastjson (missing NOTICE)
>  - commons-cli (missing NOTICE)
>  - NOTICE points to non-existent file LICENSE..txt
> - LICENSE-BIN mentions "ASL2"
> 
> Assuming this is your list, I'm OK with a +1.
> 
> John
> 
> 
> 
>> 
>> Bruce
>> 
>> On Wed, Feb 15, 2017 at 10:46 PM, yukon  wrote:
>> 
>>> Hello Incubator PMC,
>>> 
>>> The Apache RocketMQ community has voted and approved the proposal to
>>> release Apache RocketMQ 4.0.0 (incubating). We now kindly request the
>> IPMC
>>> review and vote on this incubator release.
>>> 
>>> [VOTE] Thread:
>>> https://lists.apache.org/thread.html/349e3268cf5ae7ec65d1cd584362c7
>>> 6bd11f86afb935b2bfb8ee6b6b@%3Cdev.rocketmq.apache.org%3E
>>> 
>>> [RESULT][VOTE] Thread:
>>> https://lists.apache.org/thread.html/6487e8afc7a71cbdf9848d1270997e
>>> c55ffe6cb9e7a2ddfce2bedb35@%3Cdev.rocketmq.apache.org%3E
>>> 
>>> The RC3 artifacts:
>>> https://dist.apache.org/repos/dist/dev/incubator/rocketmq/4.
>>> 0.0-incubating-rc3/
>>> 
>>> Git tag for the release:
>>> https://github.com/apache/incubator-rocketmq/tree/
>>> rocketmq-4.0.0-incubating
>>> 
>>> Hash for the release tag:
>>> dddc3daa2cbec4c7240d6525d2ce198826d29967
>>> 
>>> Release Notes:
>>> http://rocketmq.incubator.apache.org/release_notes/release-notes-4.0.0-
>>> incubating/
>>> 
>>> The artifacts have been signed with Key : E9BDDB0E, which can be found in
>>> the keys file:
>>> https://dist.apache.org/repos/dist/dev/incubator/rocketmq/KEYS
>>> 
>>> The maven release artifacts:
>>> 
>> https://repository.apache.org/content/repositories/orgapacherocketmq-1003
>>> 
>>> The vote will be open for at least 72 hours or until necessary number of
>>> votes are reached.
>>> 
>>> Please vote accordingly:
>>> 
>>> [ ] +1 approve
>>> [ ] +0 no opinion
>>> [ ] -1 disapprove with the reason
>>> 
>>> Here is my +1
>>> 
>>> Thanks,
>>> The Apache RocketMQ Team
>>> 
>> 
>> 
>> 
>> --
>> perl -e 'print
>> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E> 
>> ActiveMQ in Action: http://bit.ly/2je6cQ
>> Blog: http://bsnyder.org/ 
>> Twitter: http://twitter.com/brucesnyder
>> 


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

Re: [VOTE]: Release Apache RocketMQ 4.0.0(incubating) (RC3)

[Von Gosling]

> IMO it best to follow current documentation than copy what other projects may 
> of done.

Agreed. That’s why i hope some clear official documentation to be polished, 
rather than scatter in every apache project  :-)

BTW, in order to help our guys, we also arrange 2 articles in website about 
apache PR best practice[1] and distribution process[2] following our mentor 
justin guidance endeavor in many apache projects. and continue to polish these 
guidance. I hope we can offer help or feedback If official documentations need 
to be polished in these points.   

[1] http://rocketmq.incubator.apache.org/docs/pull-request/ 

[2] http://rocketmq.incubator.apache.org/docs/release-manual 


> 在 2017年2月17日，14:47，Justin Mclean  写道：
> 
> Hi,
> 
>> I also want to know the correct distribution about NOTICE and LICENSE. also 
>> including the LICENSE and LICENSE-BIN(why we must list the 2 different 
>> license files when in source and bundle)..
> 
> As explained on the dev list you need different NOTICE and LICENSE files 
> because their contents are different.
> 
>> it seems to different in many apache projects .we are confused when refering 
>> these projects )
> 
> There's not always consistency among projects and there are often multiple 
> ways of dealing with the some issue. In a few cases policy or best practice 
> has changed over time and the project has not kept up to date. IMO it best to 
> follow current documentation than copy what other projects may of done.
> 
>> IMO, if have some clear guide for this problem. may be a good help for our 
>> incubator project :-)
> 
> The best guidance that I know of can be find here [1] and in the legal how 
> to. [2] 
> 
> This example I made some time ago may also help. [3][4]
> 
> Thanks,
> Justin
> 
> 1. http://www.apache.org/dev/licensing-howto.html
> 2. https://www.apache.org/legal/resolved
> 3. https://github.com/justinmclean/ApacheWombat
> 4. https://vimeo.com/iotsydney/apachewombat
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

Re: [VOTE] Heron to enter Apache Incubator

[Von Gosling]

Hi,

I will give +1(Non-binding), but,

I have the similar question about so many streaming framework in the apache, 
how to develop community for themselves. 




Best Regards,
Von Gosling



> 在 2017年6月23日，08:51，Edward Capriolo  写道：
> 
> I believe heron and storm should be merged back together. I do not see the
> value of storm and a storm fork in the asf.
> 
> On Thursday, June 22, 2017, Bill Graham  <mailto:billgra...@gmail.com>> wrote:
> 
>> Thanks Taylor for relaying these sentiments, especially the part about the
>> Heron website which is indeed poorly worded (I suspect this could have been
>> the result of internal docs being open-sourced). I've opened this pull
>> request to update the language regarding Storm:
>> 
>> https://github.com/twitter/heron/pull/1979
>> 
>> On Thu, Jun 22, 2017 at 12:21 PM, P. Taylor Goetz > > wrote:
>> 
>>> The Apache Storm PMC had a discussion regarding the Heron proposal. In
>> the
>>> spirit of openness I wanted to bring some of the sentiments expressed in
>>> that discussion back to this list. Please note that I am paraphrasing
>> from
>>> that discussion and attempting to relay opinions of the collective PMC,
>> not
>>> necessarily that of any individual.
>>> 
>>> * There is a general disappointment that the Heron community chose not to
>>> engage with the Storm community and instead chose a separate path.
>>> * A majority of the PMC supports Heron’s incubation, though some felt it
>>> would result in unnecessary duplication of effort.
>>> * A majority of the PMC supports the two projects working closely
>>> together. A number of PMC members suggested the two projects merge in
>> some
>>> way.
>>> * Many PMC members took issue some of the marketing language on the Heron
>>> website, particularly Heron being billed as “the direct successor to
>> Apache
>>> Storm” and the prominent “Upgrade from Storm” links.  The main concern
>> here
>>> was such phrasing has somewhat of a hostile tone and undermines the
>> desire
>>> for better collaboration, as well as confusing users.
>>> 
>>> One of my goals as a proposed mentor for Heron and a Storm PMC member is
>>> to address some of these concerns and encourage collaboration. As I
>>> mentioned to the Storm PMC on that thread, if there are ongoing concerns
>>> from either the Storm PMC or the Heron PPMC about me acting as a mentor,
>> I
>>> would be willing to step down.
>>> 
>>> +1 (binding)
>>> 
>>> -Taylor
>>> 
>>>> On Jun 16, 2017, at 4:41 PM, Bill Graham > > wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> Based on the discussion on the incubator mailing list[1] I would like
>> to
>>>> call a vote to add Heron to the Apache Incubator.
>>>> 
>>>> The full proposal is available below, and is also available on the
>> Apache
>>>> Incubator wiki at:
>>>>   https://wiki.apache.org/incubator/HeronProposal
>>>> 
>>>> Please vote:
>>>> [ ] +1, bring Heron into Incubator
>>>> [ ] -1, do not bring Heron into Incubator, because...
>>>> 
>>>> The vote will open for 7 days until Friday June 23 at 14:00 PT.
>>>> 
>>>> Thank you
>>>> 
>>>> 1 -
>>>> https://lists.apache.org/thread.html/fb91f527ef479bb5df45bf2c9d93b7
>>> 786c3fa6cdbfeba3128599df79@%3Cgeneral.incubator.apache.org%3E
>>>> 
>>>> 
>>>> 
>>>> = Heron Proposal =
>>>> 
>>>> = Abstract =
>>>> Heron is a real-time, distributed, fault-tolerant stream processing
>>> engine
>>>> initially developed by Twitter.
>>>> 
>>>> = Proposal =
>>>> 
>>>> Heron is a real-time stream processing engine built for high
>> performance,
>>>> ease of manageability, performance predictability and developer
>>>> productivity[1]. We wish to develop a community around Heron to
>> increase
>>>> contributions and see Heron thrive in an open forum.
>>>> 
>>>> = Background =
>>>> 
>>>> Heron provides the ability for developers to compose directed acyclic
>>>> graphs (DAGs) of real-time query execution logic (i.e. a topology) and
>>>> submit the topology to execute on a pluggable job scheduling system
>>> (e.g.,
>>>> Apache Aurora, YARN, Marathon, etc). Users can em

Re: Seeking interested parties for a messaging components podling

[Von Gosling]

Hi,


I am not sure your mention is Apache RocketMQ. In RocketMQ, jms integration is 
just a adaptor, while not fully support JMS 1.1 and JMS 2.0 specification. 

IMO, that’s a good idea. if we messaging engines can collaborate to some common 
components, such as benchmark, common api specification, wire protocol bridge 
and so on. 

Indeed, we have drafted some api specification(OpenMessaging) about messaging 
and streaming fields[1], welcome any idea about it :-) 


[1] https://openmessaging.github.io/ <https://openmessaging.github.io/>

Best Regards,
Von Gosling


> 在 2017年6月24日，05:25，Michael André Pearce  写道：
> 
> Hi,
> 
> As already been discussing in the Artemis mailing lists have some areas we 
> would like to contribute/commit in particular already looking at:
> 
> JMSObject Custom serdes wrapper (with and avro serdes as initial provided)
> Generic JMS Client side persistence 
> 
> 
> Cheers
> Mike
> 
> 
> 
> On 2017-06-22 04:39 (+0100), Atri Sharma wrote: 
>> I would love to contribute.> 
>> 
>> On Jun 22, 2017 8:05 AM, "John D. Ament" wrote:> 
>> 
>>> All,> 
>>>> 
>>> There's an ongoing discussion on the ActiveMQ dev list [1] to spin up a> 
>>> project focused on core, reusable messaging components. The feeling is> 
>>> that this is outside the realm of ActiveMQ for various reasons and could 
>>> be> 
>>> leveraged by various messaging platforms, potentially even building out> 
>>> some reusability and core protocol support along the ways.> 
>>>> 
>>> Knowing that we have some messaging experience within the incubator, I> 
>>> wanted to prod around a bit to see if there was anyone else interested in 
>>> a> 
>>> project like this.> 
>>>> 
>>> John> 
>>>> 
>>> PS - when I say interested parties, it could be> 
>>> champions/mentors/contributors or heck even possible TLP sponsors.> 
>>>> 
>>> [1]:> 
>>> https://lists.apache.org/thread.html/ff3ffb0408d299724caadbfb6e3c37> 
>>> 3e74d5d16def9af0c1a8fd8db9@%3Cdev.activemq.apache.org%3E> 
>>>> 
>> 
> 
> 
> Sent from my iPad
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org 
> <mailto:general-unsubscr...@incubator.apache.org>
> For additional commands, e-mail: general-h...@incubator.apache.org 
> <mailto:general-h...@incubator.apache.org>

Re: Seeking interested parties for a messaging components podling

[Von Gosling]

Hi john,

I am very interested in participate in such a podling personally. as for 
RocketMQ community, imo, we will start a thread to discussion this idea :-)

Best Regards,
Von Gosling


> 在 2017年6月24日，22:17，John D. Ament  写道：
> 
> Hi Von Gosling,
> 
> So I just want to check, is this an indication that there may be interest
> from the RocketMQ community to participate in such a podling?
> 
> John
> 
> On Fri, Jun 23, 2017 at 9:35 PM Von Gosling  wrote:
> 
>> 
>> Hi,
>> 
>> 
>> I am not sure your mention is Apache RocketMQ. In RocketMQ, jms
>> integration is just a adaptor, while not fully support JMS 1.1 and JMS 2.0
>> specification.
>> 
>> IMO, that’s a good idea. if we messaging engines can collaborate to some
>> common components, such as benchmark, common api specification, wire
>> protocol bridge and so on.
>> 
>> Indeed, we have drafted some api specification(OpenMessaging) about
>> messaging and streaming fields[1], welcome any idea about it :-)
>> 
>> 
>> [1] https://openmessaging.github.io/ <https://openmessaging.github.io/>
>> 
>> Best Regards,
>> Von Gosling
>> 
>> 
>>> 在 2017年6月24日，05:25，Michael André Pearce 
>> 写道：
>>> 
>>> Hi,
>>> 
>>> As already been discussing in the Artemis mailing lists have some areas
>> we would like to contribute/commit in particular already looking at:
>>> 
>>> JMSObject Custom serdes wrapper (with and avro serdes as initial
>> provided)
>>> Generic JMS Client side persistence
>>> 
>>> 
>>> Cheers
>>> Mike
>>> 
>>> 
>>> 
>>> On 2017-06-22 04:39 (+0100), Atri Sharma wrote:
>>>> I would love to contribute.>
>>>> 
>>>> On Jun 22, 2017 8:05 AM, "John D. Ament" wrote:>
>>>> 
>>>>> All,>
>>>>>> 
>>>>> There's an ongoing discussion on the ActiveMQ dev list [1] to spin up
>> a>
>>>>> project focused on core, reusable messaging components. The feeling is>
>>>>> that this is outside the realm of ActiveMQ for various reasons and
>> could be>
>>>>> leveraged by various messaging platforms, potentially even building
>> out>
>>>>> some reusability and core protocol support along the ways.>
>>>>>> 
>>>>> Knowing that we have some messaging experience within the incubator, I>
>>>>> wanted to prod around a bit to see if there was anyone else interested
>> in a>
>>>>> project like this.>
>>>>>> 
>>>>> John>
>>>>>> 
>>>>> PS - when I say interested parties, it could be>
>>>>> champions/mentors/contributors or heck even possible TLP sponsors.>
>>>>>> 
>>>>> [1]:>
>>>>> https://lists.apache.org/thread.html/ff3ffb0408d299724caadbfb6e3c37>
>>>>> 3e74d5d16def9af0c1a8fd8db9@%3Cdev.activemq.apache.org%3E>
>>>>>> 
>>>> 
>>> 
>>> 
>>> Sent from my iPad
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> <mailto:general-unsubscr...@incubator.apache.org>
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>> <mailto:general-h...@incubator.apache.org>
>> 


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

Re: [VOTE] Graduate Apache DistributedLog as a subproject of Apache BookKeeper

[Von Gosling]

+1

Best Regards,
Von Gosling


> 在 2017年6月29日，13:42，Sijie Guo  写道：
> 
> +1
> 
> On Wed, Jun 28, 2017 at 8:25 AM, John D. Ament 
> wrote:
> 
>> I have no idea why this is copying both public and private lists.
>> 
>> I'm +1 to graduate.
>> 
>> On Wed, Jun 28, 2017 at 8:06 AM Flavio Junqueira  wrote:
>> 
>>> The Apache DistributedLog community has voted to graduate the project and
>>> make it a subproject of Apache BookKeeper. The Apache BookKeeper PMC has
>>> also voted to accept DistributedLog as a subproject. The links to the
>> vote
>>> threads are the following:
>>> 
>>> DistributedLog PPMC vote:
>>> 
>>> https://mail-search.apache.org/members/private-arch/
>> distributedlog-private/201706.mbox/%3cCAO2yDyY3nzjtb934g-
>> aryujswzjetktpupf_la0jkhf263f...@mail.gmail.com%3e
>>> <
>>> https://mail-search.apache.org/members/private-arch/
>> distributedlog-private/201706.mbox/%3cCAO2yDyY3nzjtb934g-
>> aryujswzjetktpupf_la0jkhf263f...@mail.gmail.com%3e
>>>> 
>>> 
>>> https://mail-search.apache.org/members/private-arch/
>> distributedlog-private/201706.mbox/%3cCAO2yDybfqt72xGtrvR-9eUYycHJvpCo5=
>> ts87rzhpsm096r...@mail.gmail.com%3e
>>> <
>>> https://mail-search.apache.org/members/private-arch/
>> distributedlog-private/201706.mbox/%3cCAO2yDybfqt72xGtrvR-9eUYycHJvpCo5=
>> ts87rzhpsm096r...@mail.gmail.com%3e
>>>> 
>>> 
>>> DistributedLog Community vote:
>>> 
>>> http://mail-archives.apache.org/mod_mbox/incubator-
>> distributedlog-dev/201706.mbox/%3cCAO2yDyZzinfGhjXqmVEHxDaULKw
>> dt9v2nkqeyuzxe0i4tzg...@mail.gmail.com%3e
>>> <
>>> http://mail-archives.apache.org/mod_mbox/incubator-
>> distributedlog-dev/201706.mbox/%3cCAO2yDyZzinfGhjXqmVEHxDaULKw
>> dt9v2nkqeyuzxe0i4tzg...@mail.gmail.com%3e
>>>> 
>>> 
>>> http://mail-archives.apache.org/mod_mbox/incubator-
>> distributedlog-dev/201706.mbox/%3cCAO2yDya-=0cBfUM0SsL5kuf9HJ1G=pL7Z_=7Ps+
>> TQgqwJs=c...@mail.gmail.com%3e
>>> <
>>> http://mail-archives.apache.org/mod_mbox/incubator-
>> distributedlog-dev/201706.mbox/%3cCAO2yDya-=0cBfUM0SsL5kuf9HJ1G=pL7Z_=7Ps+
>> TQgqwJs=c...@mail.gmail.com%3e
>>>> 
>>> 
>>> BookKeeper PMC vote:
>>> 
>>> https://mail-search.apache.org/members/private-arch/
>> bookkeeper-private/201706.mbox/%3cCAO2yDyacdXuXh==iw1OqrRiuGoxHprP_
>> htnofojot5rxmv6...@mail.gmail.com%3e
>>> <
>>> https://mail-search.apache.org/members/private-arch/
>> bookkeeper-private/201706.mbox/%3cCAO2yDyacdXuXh==iw1OqrRiuGoxHprP_
>> htnofojot5rxmv6...@mail.gmail.com%3e
>>>> 
>>> 
>>> https://mail-search.apache.org/members/private-arch/
>> bookkeeper-private/201706.mbox/%3cCAO2yDyYzV_7vVNg6Efyp3TPjddoYRyQx4rXvqP=
>> W=c09qk2...@mail.gmail.com%3e
>>> <
>>> https://mail-search.apache.org/members/private-arch/
>> bookkeeper-private/201706.mbox/%3cCAO2yDyYzV_7vVNg6Efyp3TPjddoYRyQx4rXvqP=
>> W=c09qk2...@mail.gmail.com%3e
>>>> 
>>> 
>>> This message is to start an IPMC vote. Please vote on the following:
>>> 
>>> [ ] +1 Graduate Apache DistributedLog from the Incubator.
>>> [ ] +0 No opinion
>>> [ ] -1 Don't graduate Apache DistributedLog from the Incubator (please
>>> provide
>>> the reason)
>>> 
>>> This VOTE will be opened for the next 72 hours.
>>> 
>>> -Flavio
>> 


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

Re: Seeking interested parties for a messaging components podling

[Von Gosling]

Hi,

RocketMQ community have discussed the common messaging components endeavor[1], 
we are glad to join this podling  :-)

As for OpenMessaging spec, we have launched this spec. project under Linux 
foundation(May be CNCF later), If guys have interest about it, welcome join and 
discuss at gitter[2].



Best Regards,
Von Gosling




[1] https://lists.apache.org/list.html?general@incubator.apache.org 
<https://lists.apache.org/list.html?general@incubator.apache.org>
[2] https://gitter.im/openmessaging/public 
<https://gitter.im/openmessaging/public>





> 在 2017年6月28日，22:30，Clebert Suconic  写道：
> 
> With the number of message brokers out there (call it message
> solution, server.. whatever you want to call it).. This new project
> could represent a nice opportunity..  it was a simple idea that's
> starting to grow I think
> 
> 
> 
> @Von Gosling: would you be able to bring OpenMessaging as part of this?
> 
> 
> 
> On Wed, Jun 28, 2017 at 10:20 AM, John D. Ament  wrote:
>> You've been added.
>> 
>> On Wed, Jun 28, 2017 at 8:06 AM Michael André Pearce <
>> michael.andre.pea...@me.com> wrote:
>> 
>>> @John,
>>> 
>>> I have created username: MichaelAndrePearce (so original)
>>> 
>>> Could I be enabled to edit the wiki
>>> 
>>> Cheers
>>> Mike
>>> 
>>> Sent from my iPhone
>>> 
>>>> On 26 Jun 2017, at 21:47, Clebert Suconic 
>>> wrote:
>>>> 
>>>> @John: do I need special auth to change the WIKI you created? I can't
>>>> figure out how to make a change.
>>>> 
>>>>> On Mon, Jun 26, 2017 at 6:16 AM, John D. Ament 
>>> wrote:
>>>>> All,
>>>>> 
>>>>> I've dropped in the proposal template to
>>>>> https://wiki.apache.org/incubator/MessagingComponentsProposal - we can
>>>>> rename it later if we come up with a better name.  I'd encourage those
>>>>> interested in the project to start to form out this proposal so we can
>>>>> start to shape the who, the why and the what.  If you need access to the
>>>>> incubator wiki, first register then email on here asking to gain access.
>>>>> Include your username.
>>>>> 
>>>>> John
>>>>> 
>>>>>> On Sun, Jun 25, 2017 at 9:17 PM Von Gosling 
>>> wrote:
>>>>>> 
>>>>>> Hi john,
>>>>>> 
>>>>>> I am very interested in participate in such a podling personally. as
>>> for
>>>>>> RocketMQ community, imo, we will start a thread to discussion this
>>> idea :-)
>>>>>> 
>>>>>> Best Regards,
>>>>>> Von Gosling
>>>>>> 
>>>>>> 
>>>>>>> 在 2017年6月24日，22:17，John D. Ament  写道：
>>>>>>> 
>>>>>>> Hi Von Gosling,
>>>>>>> 
>>>>>>> So I just want to check, is this an indication that there may be
>>> interest
>>>>>>> from the RocketMQ community to participate in such a podling?
>>>>>>> 
>>>>>>> John
>>>>>>> 
>>>>>>> On Fri, Jun 23, 2017 at 9:35 PM Von Gosling 
>>>>>> wrote:
>>>>>>> 
>>>>>>>> 
>>>>>>>> Hi,
>>>>>>>> 
>>>>>>>> 
>>>>>>>> I am not sure your mention is Apache RocketMQ. In RocketMQ, jms
>>>>>>>> integration is just a adaptor, while not fully support JMS 1.1 and
>>> JMS
>>>>>> 2.0
>>>>>>>> specification.
>>>>>>>> 
>>>>>>>> IMO, that’s a good idea. if we messaging engines can collaborate to
>>> some
>>>>>>>> common components, such as benchmark, common api specification, wire
>>>>>>>> protocol bridge and so on.
>>>>>>>> 
>>>>>>>> Indeed, we have drafted some api specification(OpenMessaging) about
>>>>>>>> messaging and streaming fields[1], welcome any idea about it :-)
>>>>>>>> 
>>>>>>>> 
>>>>>>>> [1] https://openmessaging.github.io/ <
>>> https://openmessaging.github.io/>
>>>>>>>> 
>>>>>>>> Best Regards,
>>>>>

Re: Urgent: Regarding Java package name change to org.apache.*

[Von Gosling]

> Or to put it a different way: during your eventual graduation this
> question will be
> asked and you better have a really, really good explanation if you're
> still using
> something other than o.a.


In fact, Apache RocketMQ Community has ever struggle with this issue. Consider 
more than 100 subsidiary corporations and 1000+ applications using rocketmq 3.x 
version(before incubator, not naming org.apache.*), we are not planning to 
change the package originally until some new version changed dramatically. On 
the other hand, we resort to maven shade to workaround for backwards 
incompatibility. So, I are very pleased to introduce this way for guys, if we 
hope to avoid the cost of downstream migrations and backwards incompatibility 
:-)



Best Regards
Von Gosling




> 在 2017年8月3日，08:54，Roman Shaposhnik  写道：
> 
> On Wed, Aug 2, 2017 at 5:40 PM, Abhishek Tiwari  <mailto:a...@apache.org>> wrote:
>> Hi all,
>> 
>> In regards to the recently incubated project - Gobblin, we were wondering
>> about the policy around renaming Java package names to org.apache.* Is it a
>> mandatory requirement or good to have?
>> 
>> The reason to ask this is that while we see many projects have migrated to
>> use org.apache.* package name for their Java source files, the Kafka
>> project uses kafka.* for Scala sources and org.apache.kafka.* for Java
>> sources.
>> 
>> Please let us know as soon as possible, because we are in process of
>> renaming the  packages but if not mandatory we would want to keep gobblin.*
>> package name and avoid the cost of downstream migrations and backwards
>> incompatibility.
> 
> You don't have to do it right away, but it is a requirement unless you
> have a really,
> really, really good reason of why you can't do that.
> 
> Or to put it a different way: during your eventual graduation this
> question will be
> asked and you better have a really, really good explanation if you're
> still using
> something other than o.a.
> 
> Thanks,
> Roman.
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org 
> <mailto:general-unsubscr...@incubator.apache.org>
> For additional commands, e-mail: general-h...@incubator.apache.org 
> <mailto:general-h...@incubator.apache.org>

[VOTE] Graduate Apache RocketMQ from podling to TLP

[Von Gosling]

Hello IPMC,

The recent DISCUSS thread in PPMC and VOTE thread in Community on the topic of 
Apache RocketMQ graduation have been opened for at least 72 hours, and I 
believe all questions have been answered and issues addressed at this point.

With the discussion having settled down, I would now like to call for a 
recommendation VOTE to present the ASF board with the following resolution to 
graduate from incubation and establish Apache RocketMQ as a top-level project 
(TLP).

RocketMQ PPMC DISCUSS thread:
https://lists.apache.org/thread.html/9a11743e18cf15c1c7ecbd6be7d2041453d5838a4ed2d1b8457f5dbc@%3Cprivate.rocketmq.apache.org%3E
 
<https://lists.apache.org/thread.html/9a11743e18cf15c1c7ecbd6be7d2041453d5838a4ed2d1b8457f5dbc@%3Cprivate.rocketmq.apache.org%3E>
 

RocketMQ Community VOTE thread:
https://lists.apache.org/thread.html/6fabcac0aeb8f649ee5e8ba2ab0c867a01d3e836c9adbd9072dc738e@%3Cdev.rocketmq.apache.org%3E
 
<https://lists.apache.org/thread.html/6fabcac0aeb8f649ee5e8ba2ab0c867a01d3e836c9adbd9072dc738e@%3Cdev.rocketmq.apache.org%3E>
 

RocketMQ Community VOTE RESULT thread:
https://lists.apache.org/thread.html/40cca6b958bdf0f9ec698ef35e54187fe884600c1fed4f98a79c1c2c@%3Cdev.rocketmq.apache.org%3E
 
<https://lists.apache.org/thread.html/40cca6b958bdf0f9ec698ef35e54187fe884600c1fed4f98a79c1c2c@%3Cdev.rocketmq.apache.org%3E>
 


Apache RocketMQ entered incubation in November 2016. Since then there have been 
two releases and four committers and one pmc candidate member have been added 
to the project. For each release, source and binary artifacts have been made 
available. Based on the completed maturity evaluation we believe that the 
project is ready to graduate from the incubator. More checklist info about 
graduation, please refer to  
https://cwiki.apache.org/confluence/display/ROCKETMQ/Graduation+Checklist 
<https://cwiki.apache.org/confluence/display/ROCKETMQ/Graduation+Checklist> 


Please vote on whether to recommend the following graduation resolution to the 
ASF Board.

[  ]  +1, In favor of recommending the following graduation resolution to the 
ASF Board to establish Apache RocketMQ as a TLP
[  ]  +0, Neither opposed to, nor in favor of, recommending the following 
graduation resolution to the Board
[  ]  -1, Opposed to recommending the following graduation resolution to the 
Board(provide details)

This VOTE will be open for at least 72 hours. Here is my vote +1. Thanks to all 
Mentors and Apache RocketMQ Project members for their support and contributions 
again.

The full text of the resolution is below. If approved by the Apache Incubator 
PMC members, the proposed resolution will be submitted to the Board of 
Directors for their consideration.

Establish the Apache RocketMQ Project
WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to establish
a Project Management Committee charged with the creation and maintenance
of open-source software, for distribution at no charge to the public,
related to a fast, low latency, reliable, scalable, distributed, easy to
use message-oriented middleware, especially for processing large amounts
of streaming data.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache RocketMQ Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache RocketMQ Project be and hereby is responsible
for the creation and maintenance of software related to a fast, low
latency, reliable, scalable, distributed, easy to use message-oriented
middleware, especially for processing large amounts of streaming data;
and be it further
RESOLVED, that the office of "Vice President, Apache RocketMQ" be and
hereby is created, the person holding such office to serve at the
direction of the Board of Directors as the chair of the Apache RocketMQ
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache RocketMQ
Project; and be it further
RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache RocketMQ
Project:
* Bsnyder 
* Jmclean 
* Jim 
* Ningjiang 
* Von Gosling  
* Xiaorui Wang 
* Xinyu Zhou 
* Zhanhui Li 
* Jixiang Jin 
* Dongeforever 

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Xiaorui Wang be appointed to
the office of Vice President, Apache RocketMQ, to serve in accordance
with and subject to the direction of the Board of Directors and the
Bylaws of the Foundation until death, resignation, retirement, removal
or disqualification, or until a successor is appointed; and be it
further
RESOLVED, that the initial Apache RocketMQ PMC be and hereby is tasked
with the creation of a set of bylaws intended to encourage open
development and increased participation in the Apache RocketMQ Project;
and be it further

Re: [VOTE] Graduate Apache RocketMQ from podling to TLP

[Von Gosling]

Hi John,

Thanks for your suggestion, we have looked through the graduation process 
carefully and made a discussion in PPMC email list sufficiently. From our guide 
picture[1] depict, I haven't seen the IPMC discuss process. But in the next 
paragraph, I noticed the description :

The resolution should be proposed on the general incubator list before a VOTE 
is started to allow feedback. Once a consensus has been reached, a VOTE should 
be started on the same general incubator list by a member of the PPMC proposing 
that the IPMC recommends the resolution to the Board.

I’m totally confused. If the discussion in IPMC is necessary, I am willing to 
cancel this email and call for discussion in IPMC list :-)

[1] 
https://incubator.apache.org/guides/graduation.html#ipmc-top-level-recommendation
 
<https://incubator.apache.org/guides/graduation.html#ipmc-top-level-recommendation>


Best Regards,
Von Gosling


> 在 2017年8月23日，11:34，John D. Ament  写道：
> 
> Hi Von Gosling,
> 
> A few concerns pop up on my side when looking at this.
> 
> - You're mixing public and private mailing lists in this email.
> - You may want to review [1] - we do call out the need to forward to the
> incubator that the vote.  This is usually to start discussions.
> Specifically we do ask in [2] that the charter be sent before a vote to
> help us discuss it before the vote.
> 
> I'd like you to consider these things and perhaps start a discussion
> thread.  We're more than 3 weeks ahead of the board meeting so plenty of
> time to iron things out.  You can see examples of what this looks like at
> [3] and [4].
> 
> [1]:
> https://incubator.apache.org/guides/graduation.html#the_graduation_process 
> <https://incubator.apache.org/guides/graduation.html#the_graduation_process>
> [2]:
> https://incubator.apache.org/guides/graduation.html#the_recommendation_vote 
> <https://incubator.apache.org/guides/graduation.html#the_recommendation_vote>
> [3]:
> https://lists.apache.org/thread.html/214424f03d6f7b47f3abc1e3da772627390a07960daa8b95365380bc@%3Cgeneral.incubator.apache.org%3E
>  
> <https://lists.apache.org/thread.html/214424f03d6f7b47f3abc1e3da772627390a07960daa8b95365380bc@%3Cgeneral.incubator.apache.org%3E>
> [4]:
> https://lists.apache.org/thread.html/f4050631cf7f561b8ce648ac04d9b3c86a6972b2f5e3a84e4d6139a1@%3Cgeneral.incubator.apache.org%3E
>  
> <https://lists.apache.org/thread.html/f4050631cf7f561b8ce648ac04d9b3c86a6972b2f5e3a84e4d6139a1@%3Cgeneral.incubator.apache.org%3E>
> 
> 
> On Tue, Aug 22, 2017 at 11:08 PM Von Gosling  <mailto:fengji...@gmail.com>> wrote:
> 
>> Hello IPMC,
>> 
>> The recent DISCUSS thread in PPMC and VOTE thread in Community on the
>> topic of Apache RocketMQ graduation have been opened for at least 72 hours,
>> and I believe all questions have been answered and issues addressed at this
>> point.
>> 
>> With the discussion having settled down, I would now like to call for a
>> recommendation VOTE to present the ASF board with the following resolution
>> to graduate from incubation and establish Apache RocketMQ as a top-level
>> project (TLP).
>> 
>> RocketMQ PPMC DISCUSS thread:
>> 
>> https://lists.apache.org/thread.html/9a11743e18cf15c1c7ecbd6be7d2041453d5838a4ed2d1b8457f5dbc@%3Cprivate.rocketmq.apache.org%3E
>> <
>> https://lists.apache.org/thread.html/9a11743e18cf15c1c7ecbd6be7d2041453d5838a4ed2d1b8457f5dbc@%3Cprivate.rocketmq.apache.org%3E
>>  
>> <https://lists.apache.org/thread.html/9a11743e18cf15c1c7ecbd6be7d2041453d5838a4ed2d1b8457f5dbc@%3Cprivate.rocketmq.apache.org%3E>
>>> 
>> 
>> RocketMQ Community VOTE thread:
>> 
>> https://lists.apache.org/thread.html/6fabcac0aeb8f649ee5e8ba2ab0c867a01d3e836c9adbd9072dc738e@%3Cdev.rocketmq.apache.org%3E
>>  
>> <https://lists.apache.org/thread.html/6fabcac0aeb8f649ee5e8ba2ab0c867a01d3e836c9adbd9072dc738e@%3Cdev.rocketmq.apache.org%3E>
>> <
>> https://lists.apache.org/thread.html/6fabcac0aeb8f649ee5e8ba2ab0c867a01d3e836c9adbd9072dc738e@%3Cdev.rocketmq.apache.org%3E
>>  
>> <https://lists.apache.org/thread.html/6fabcac0aeb8f649ee5e8ba2ab0c867a01d3e836c9adbd9072dc738e@%3Cdev.rocketmq.apache.org%3E>
>>> 
>> 
>> RocketMQ Community VOTE RESULT thread:
>> 
>> https://lists.apache.org/thread.html/40cca6b958bdf0f9ec698ef35e54187fe884600c1fed4f98a79c1c2c@%3Cdev.rocketmq.apache.org%3E
>>  
>> <https://lists.apache.org/thread.html/40cca6b958bdf0f9ec698ef35e54187fe884600c1fed4f98a79c1c2c@%3Cdev.rocketmq.apache.org%3E>
>> <
>> https://lists.apache.org/thread.html/40cca6b958bdf0f9ec698ef35e54187fe884600c1fed4f98a79c1c2c@%3Cdev.rocketmq.apache.org%3E

[CANCEL] [VOTE] Graduate Apache RocketMQ from podling to TLP

[Von Gosling]

Hi,

If no any thoughts, I  would like to cancel the vote and call for discuss later 
:-)


Best Regards,
Von Gosling


> 在 2017年8月23日，11:53，Von Gosling  写道：
> 
> Hi John,
> 
> Thanks for your suggestion, we have looked through the graduation process 
> carefully and made a discussion in PPMC email list sufficiently. From our 
> guide picture[1] depict, I haven't seen the IPMC discuss process. But in the 
> next paragraph, I noticed the description :
> 
> The resolution should be proposed on the general incubator list before a VOTE 
> is started to allow feedback. Once a consensus has been reached, a VOTE 
> should be started on the same general incubator list by a member of the PPMC 
> proposing that the IPMC recommends the resolution to the Board.
> 
> I’m totally confused. If the discussion in IPMC is necessary, I am willing to 
> cancel this email and call for discussion in IPMC list :-)
> 
> [1] 
> https://incubator.apache.org/guides/graduation.html#ipmc-top-level-recommendation
>  
> <https://incubator.apache.org/guides/graduation.html#ipmc-top-level-recommendation>
> 
> 
> Best Regards,
> Von Gosling
> 
> 
>> 在 2017年8月23日，11:34，John D. Ament > <mailto:johndam...@apache.org>> 写道：
>> 
>> Hi Von Gosling,
>> 
>> A few concerns pop up on my side when looking at this.
>> 
>> - You're mixing public and private mailing lists in this email.
>> - You may want to review [1] - we do call out the need to forward to the
>> incubator that the vote.  This is usually to start discussions.
>> Specifically we do ask in [2] that the charter be sent before a vote to
>> help us discuss it before the vote.
>> 
>> I'd like you to consider these things and perhaps start a discussion
>> thread.  We're more than 3 weeks ahead of the board meeting so plenty of
>> time to iron things out.  You can see examples of what this looks like at
>> [3] and [4].
>> 
>> [1]:
>> https://incubator.apache.org/guides/graduation.html#the_graduation_process 
>> <https://incubator.apache.org/guides/graduation.html#the_graduation_process>
>> [2]:
>> https://incubator.apache.org/guides/graduation.html#the_recommendation_vote 
>> <https://incubator.apache.org/guides/graduation.html#the_recommendation_vote>
>> [3]:
>> https://lists.apache.org/thread.html/214424f03d6f7b47f3abc1e3da772627390a07960daa8b95365380bc@%3Cgeneral.incubator.apache.org%3E
>>  
>> <https://lists.apache.org/thread.html/214424f03d6f7b47f3abc1e3da772627390a07960daa8b95365380bc@%3Cgeneral.incubator.apache.org%3E>
>> [4]:
>> https://lists.apache.org/thread.html/f4050631cf7f561b8ce648ac04d9b3c86a6972b2f5e3a84e4d6139a1@%3Cgeneral.incubator.apache.org%3E
>>  
>> <https://lists.apache.org/thread.html/f4050631cf7f561b8ce648ac04d9b3c86a6972b2f5e3a84e4d6139a1@%3Cgeneral.incubator.apache.org%3E>
>> 
>> 
>> On Tue, Aug 22, 2017 at 11:08 PM Von Gosling > <mailto:fengji...@gmail.com>> wrote:
>> 
>>> Hello IPMC,
>>> 
>>> The recent DISCUSS thread in PPMC and VOTE thread in Community on the
>>> topic of Apache RocketMQ graduation have been opened for at least 72 hours,
>>> and I believe all questions have been answered and issues addressed at this
>>> point.
>>> 
>>> With the discussion having settled down, I would now like to call for a
>>> recommendation VOTE to present the ASF board with the following resolution
>>> to graduate from incubation and establish Apache RocketMQ as a top-level
>>> project (TLP).
>>> 
>>> RocketMQ PPMC DISCUSS thread:
>>> 
>>> https://lists.apache.org/thread.html/9a11743e18cf15c1c7ecbd6be7d2041453d5838a4ed2d1b8457f5dbc@%3Cprivate.rocketmq.apache.org%3E
>>>  
>>> <https://lists.apache.org/thread.html/9a11743e18cf15c1c7ecbd6be7d2041453d5838a4ed2d1b8457f5dbc@%3Cprivate.rocketmq.apache.org%3E>
>>> <
>>> https://lists.apache.org/thread.html/9a11743e18cf15c1c7ecbd6be7d2041453d5838a4ed2d1b8457f5dbc@%3Cprivate.rocketmq.apache.org%3E
>>>  
>>> <https://lists.apache.org/thread.html/9a11743e18cf15c1c7ecbd6be7d2041453d5838a4ed2d1b8457f5dbc@%3Cprivate.rocketmq.apache.org%3E>
>>>> 
>>> 
>>> RocketMQ Community VOTE thread:
>>> 
>>> https://lists.apache.org/thread.html/6fabcac0aeb8f649ee5e8ba2ab0c867a01d3e836c9adbd9072dc738e@%3Cdev.rocketmq.apache.org%3E
>>>  
>>> <https://lists.apache.org/thread.html/6fabcac0aeb8f649ee5e8ba2ab0c867a01d3e836c9adbd9072dc738e@%3Cdev.rocketmq.apache.org%3E>
>>> <
>>> https://lists.apache.org

[DISCUSS] Graduate Apache RocketMQ from podling to TLP

[Von Gosling]

Greetings Incubator,

The RocketMQ podling has decided to pursue graduation to a TLP. The discuss 
thread[1] and The result of the RocketMQ vote in RocketMQ community is at 
[2][3]. Our podling status page has recently been updated and can be found 
here[4]. More graduation statement, including Maturity Evaluation, please refer 
to [5].

Below, you can view the proposed TLP resolution which we'd like to present to 
the board with the support of the IPMC, after sufficient discussion here and 
subsequent IPMC vote.

[1] 
https://lists.apache.org/thread.html/9a11743e18cf15c1c7ecbd6be7d2041453d5838a4ed2d1b8457f5dbc@%3Cprivate.rocketmq.apache.org%3E
 
[2] 
https://lists.apache.org/thread.html/6fabcac0aeb8f649ee5e8ba2ab0c867a01d3e836c9adbd9072dc738e@%3Cdev.rocketmq.apache.org%3E
[3] 
https://lists.apache.org/thread.html/40cca6b958bdf0f9ec698ef35e54187fe884600c1fed4f98a79c1c2c@%3Cdev.rocketmq.apache.org%3E
[4] http://incubator.apache.org/projects/rocketmq.html
[5] https://cwiki.apache.org/confluence/display/ROCKETMQ/Graduation+Checklist



**
Establish the Apache RocketMQ Project

WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to establish
a Project Management Committee charged with the creation and maintenance
of open-source software, for distribution at no charge to the public,
related to a fast, low latency, reliable, scalable, distributed, easy to
use message-oriented middleware, especially for processing large amounts
of streaming data.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache RocketMQ Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache RocketMQ Project be and hereby is responsible
for the creation and maintenance of software related to a fast, low
latency, reliable, scalable, distributed, easy to use message-oriented
middleware, especially for processing large amounts of streaming data;
and be it further
RESOLVED, that the office of "Vice President, Apache RocketMQ" be and
hereby is created, the person holding such office to serve at the
direction of the Board of Directors as the chair of the Apache RocketMQ
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache RocketMQ
Project; and be it further
RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache RocketMQ
Project:

* Bsnyder 
* Jmclean 
* Jim 
* Ningjiang 
* Von Gosling  
* Xiaorui Wang 
* Xinyu Zhou 
* Zhanhui Li 
* Jixiang Jin 
* Dongeforever 

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Xiaorui Wang be appointed to
the office of Vice President, Apache RocketMQ, to serve in accordance
with and subject to the direction of the Board of Directors and the
Bylaws of the Foundation until death, resignation, retirement, removal
or disqualification, or until a successor is appointed; and be it
further
RESOLVED, that the initial Apache RocketMQ PMC be and hereby is tasked
with the creation of a set of bylaws intended to encourage open
development and increased participation in the Apache RocketMQ Project;
and be it further
RESOLVED, that the Apache RocketMQ Project be and hereby is tasked with
the migration and rationalization of the Apache Incubator RocketMQ
podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache Incubator
RocketMQ podling encumbered upon the Apache Incubator PMC are hereafter
discharged.

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

Re: [VOTE] Graduate Apache RocketMQ from podling to TLP

[Von Gosling]

Hi,

Thanks Jim suggestion. I will complement here before the next formal vote :-).

Best Regards,
Von Gosling


> 在 2017年8月23日，19:15，Jim Jagielski  写道：
> 
> Another thing that the IPMC will likely have issues with is
> the list format of the initial members... The format should
> be
> 
>  * Full Name 
> 
> eg:
> 
>  * Bruce Snyder 
> 
> 
>> On Aug 22, 2017, at 11:34 PM, John D. Ament  wrote:
>> 
>> Hi Von Gosling,
>> 
>> A few concerns pop up on my side when looking at this.
>> 
>> - You're mixing public and private mailing lists in this email.
>> - You may want to review [1] - we do call out the need to forward to the 
>> incubator that the vote.  This is usually to start discussions.  
>> Specifically we do ask in [2] that the charter be sent before a vote to help 
>> us discuss it before the vote.
>> 
>> I'd like you to consider these things and perhaps start a discussion thread. 
>>  We're more than 3 weeks ahead of the board meeting so plenty of time to 
>> iron things out.  You can see examples of what this looks like at [3] and 
>> [4].
>> 
>> [1]: 
>> https://incubator.apache.org/guides/graduation.html#the_graduation_process
>> [2]: 
>> https://incubator.apache.org/guides/graduation.html#the_recommendation_vote
>> [3]: 
>> https://lists.apache.org/thread.html/214424f03d6f7b47f3abc1e3da772627390a07960daa8b95365380bc@%3Cgeneral.incubator.apache.org%3E
>> [4]: 
>> https://lists.apache.org/thread.html/f4050631cf7f561b8ce648ac04d9b3c86a6972b2f5e3a84e4d6139a1@%3Cgeneral.incubator.apache.org%3E
>> 
>> 
>> On Tue, Aug 22, 2017 at 11:08 PM Von Gosling  wrote:
>> Hello IPMC,
>> 
>> The recent DISCUSS thread in PPMC and VOTE thread in Community on the topic 
>> of Apache RocketMQ graduation have been opened for at least 72 hours, and I 
>> believe all questions have been answered and issues addressed at this point.
>> 
>> With the discussion having settled down, I would now like to call for a 
>> recommendation VOTE to present the ASF board with the following resolution 
>> to graduate from incubation and establish Apache RocketMQ as a top-level 
>> project (TLP).
>> 
>> RocketMQ PPMC DISCUSS thread:
>> https://lists.apache.org/thread.html/9a11743e18cf15c1c7ecbd6be7d2041453d5838a4ed2d1b8457f5dbc@%3Cprivate.rocketmq.apache.org%3E
>>  
>> <https://lists.apache.org/thread.html/9a11743e18cf15c1c7ecbd6be7d2041453d5838a4ed2d1b8457f5dbc@%3Cprivate.rocketmq.apache.org%3E>
>> 
>> RocketMQ Community VOTE thread:
>> https://lists.apache.org/thread.html/6fabcac0aeb8f649ee5e8ba2ab0c867a01d3e836c9adbd9072dc738e@%3Cdev.rocketmq.apache.org%3E
>>  
>> <https://lists.apache.org/thread.html/6fabcac0aeb8f649ee5e8ba2ab0c867a01d3e836c9adbd9072dc738e@%3Cdev.rocketmq.apache.org%3E>
>> 
>> RocketMQ Community VOTE RESULT thread:
>> https://lists.apache.org/thread.html/40cca6b958bdf0f9ec698ef35e54187fe884600c1fed4f98a79c1c2c@%3Cdev.rocketmq.apache.org%3E
>>  
>> <https://lists.apache.org/thread.html/40cca6b958bdf0f9ec698ef35e54187fe884600c1fed4f98a79c1c2c@%3Cdev.rocketmq.apache.org%3E>
>> 
>> 
>> Apache RocketMQ entered incubation in November 2016. Since then there have 
>> been two releases and four committers and one pmc candidate member have been 
>> added to the project. For each release, source and binary artifacts have 
>> been made available. Based on the completed maturity evaluation we believe 
>> that the project is ready to graduate from the incubator. More checklist 
>> info about graduation, please refer to  
>> https://cwiki.apache.org/confluence/display/ROCKETMQ/Graduation+Checklist 
>> <https://cwiki.apache.org/confluence/display/ROCKETMQ/Graduation+Checklist>
>> 
>> 
>> Please vote on whether to recommend the following graduation resolution to 
>> the ASF Board.
>> 
>> [  ]  +1, In favor of recommending the following graduation resolution to 
>> the ASF Board to establish Apache RocketMQ as a TLP
>> [  ]  +0, Neither opposed to, nor in favor of, recommending the following 
>> graduation resolution to the Board
>> [  ]  -1, Opposed to recommending the following graduation resolution to the 
>> Board(provide details)
>> 
>> This VOTE will be open for at least 72 hours. Here is my vote +1. Thanks to 
>> all Mentors and Apache RocketMQ Project members for their support and 
>> contributions again.
>> 
>> The full text of the resolution is below. If approved by the Apache 
>> Incubator PMC members, the proposed resolution will be submitted to the 
>> Board of D

Re: [DISCUSS] Graduate Apache RocketMQ from podling to TLP

[Von Gosling]

Hi,

Of course, we have listed our committer and PMC make-up in evaluation list[1] 
:-）


[1] https://cwiki.apache.org/confluence/display/ROCKETMQ/Maturity+Evaluation 
<https://cwiki.apache.org/confluence/display/ROCKETMQ/Maturity+Evaluation>

Best Regards,
Von Gosling


> 在 2017年8月24日，18:55，John D. Ament  写道：
> 
> Hi,
> 
> Would you be able to talk about committer and PMC diversity a bit?  When
> RocketMQ came to the incubator, most of the developers were from Alibaba.
> Please compare to [1] and let us know the affiliations of the prospective
> PMC members.
> 
> [1]: https://wiki.apache.org/incubator/RocketMQProposal
> 
> On Thu, Aug 24, 2017 at 2:24 AM yukon  wrote:
> 
>> Hi,
>> 
>> We have updated the latest incubation status report to RocketMQ podling
>> status page[1], also updated the resolution[2] according to
>> Jim's suggestion.
>> 
>> Can we pick this thread up, sincerely hope IPMC can give some opinions to
>> RocketMQ community.
>> 
>> [1] http://incubator.apache.org/projects/rocketmq.html
>> [2]
>> https://cwiki.apache.org/confluence/display/ROCKETMQ/Graduation+Checklist
>> 
>> Regards,
>> yukon
>> 
>> On Wed, Aug 23, 2017 at 4:14 PM, Von Gosling 
>> wrote:
>> 
>>> Greetings Incubator,
>>> 
>>> The RocketMQ podling has decided to pursue graduation to a TLP. The
>>> discuss thread[1] and The result of the RocketMQ vote in RocketMQ
>> community
>>> is at [2][3]. Our podling status page has recently been updated and can
>> be
>>> found here[4]. More graduation statement, including Maturity Evaluation,
>>> please refer to [5].
>>> 
>>> Below, you can view the proposed TLP resolution which we'd like to
>> present
>>> to the board with the support of the IPMC, after sufficient discussion
>> here
>>> and subsequent IPMC vote.
>>> 
>>> [1] https://lists.apache.org/thread.html/9a11743e18cf15c1c7ecbd6be7d204
>>> 1453d5838a4ed2d1b8457f5dbc@%3Cprivate.rocketmq.apache.org%3E
>>> [2] https://lists.apache.org/thread.html/6fabcac0aeb8f649ee5e8ba2ab0c86
>>> 7a01d3e836c9adbd9072dc738e@%3Cdev.rocketmq.apache.org%3E
>>> [3] https://lists.apache.org/thread.html/40cca6b958bdf0f9ec698ef35e5418
>>> 7fe884600c1fed4f98a79c1c2c@%3Cdev.rocketmq.apache.org%3E
>>> [4] http://incubator.apache.org/projects/rocketmq.html
>>> [5] https://cwiki.apache.org/confluence/display/ROCKETMQ/
>>> Graduation+Checklist
>>> 
>>> 
>>> 
>>> **
>>> Establish the Apache RocketMQ Project
>>> 
>>> WHEREAS, the Board of Directors deems it to be in the best interests of
>>> the Foundation and consistent with the Foundation's purpose to establish
>>> a Project Management Committee charged with the creation and maintenance
>>> of open-source software, for distribution at no charge to the public,
>>> related to a fast, low latency, reliable, scalable, distributed, easy to
>>> use message-oriented middleware, especially for processing large amounts
>>> of streaming data.
>>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>>> (PMC), to be known as the "Apache RocketMQ Project", be and hereby is
>>> established pursuant to Bylaws of the Foundation; and be it further
>>> RESOLVED, that the Apache RocketMQ Project be and hereby is responsible
>>> for the creation and maintenance of software related to a fast, low
>>> latency, reliable, scalable, distributed, easy to use message-oriented
>>> middleware, especially for processing large amounts of streaming data;
>>> and be it further
>>> RESOLVED, that the office of "Vice President, Apache RocketMQ" be and
>>> hereby is created, the person holding such office to serve at the
>>> direction of the Board of Directors as the chair of the Apache RocketMQ
>>> Project, and to have primary responsibility for management of the
>>> projects within the scope of responsibility of the Apache RocketMQ
>>> Project; and be it further
>>> RESOLVED, that the persons listed immediately below be and hereby are
>>> appointed to serve as the initial members of the Apache RocketMQ
>>> Project:
>>> 
>>> * Bsnyder 
>>> * Jmclean 
>>> * Jim 
>>> * Ningjiang 
>>> * Von Gosling 
>>> * Xiaorui Wang 
>>> * Xinyu Zhou 
>>> * Zhanhui Li 
>>> * Jixiang Jin 
>>> * Dongeforever 
>>> 
>>> NOW, THEREFORE, BE IT FURTHER RESOLVED, t

Re: [DISCUSS] Graduate Apache RocketMQ from podling to TLP

[Von Gosling]

Hi John,


Thanks for you explanation for AMM, I would like to complement an individual -> 
company mapping in our ME[1]. As for security aspect, not just for assessment, 
we would like to establish private channel in the website later :-)


[1] https://cwiki.apache.org/confluence/display/ROCKETMQ/Maturity+Evaluation 
<https://cwiki.apache.org/confluence/display/ROCKETMQ/Maturity+Evaluation>

Best Regards,
Von Gosling



> 在 2017年8月24日，19:06，John D. Ament  写道：
> 
> Also please understand that the Apache Maturity Model is something that
> helps the com dev team evaluate TLPs against.  Its relevance to a
> graduating podling is extremely small.
> 
> Also, if you want to discuss the AMM a bit, you have a bug in the security
> assessment that some other projects have hit as well.  The question should
> be "The project provides a well-documented, secure and private channel to
> report security issues, along with a documented way of responding to them.
> "  Thanks especially to Dave Fisher for finding this recently.
> 
> John
> 
> [1]:
> https://community.apache.org/apache-way/apache-project-maturity-model.html
> 
> On Thu, Aug 24, 2017 at 7:02 AM John D. Ament  wrote:
> 
>> Hi,
>> 
>> Could be that you have listed companies people work at.  However, I'm
>> looking for more of an individual -> company mapping.
>> 
>> John
>> 
>> 
>> On Thu, Aug 24, 2017 at 7:00 AM Von Gosling  wrote:
>> 
>>> Hi,
>>> 
>>> Of course, we have listed our committer and PMC make-up in evaluation
>>> list[1] :-）
>>> 
>>> 
>>> [1]
>>> https://cwiki.apache.org/confluence/display/ROCKETMQ/Maturity+Evaluation
>>> <https://cwiki.apache.org/confluence/display/ROCKETMQ/Maturity+Evaluation
>>>> 
>>> 
>>> Best Regards,
>>> Von Gosling
>>> 
>>> 
>>>> 在 2017年8月24日，18:55，John D. Ament  写道：
>>>> 
>>>> Hi,
>>>> 
>>>> Would you be able to talk about committer and PMC diversity a bit?  When
>>>> RocketMQ came to the incubator, most of the developers were from
>>> Alibaba.
>>>> Please compare to [1] and let us know the affiliations of the
>>> prospective
>>>> PMC members.
>>>> 
>>>> [1]: https://wiki.apache.org/incubator/RocketMQProposal
>>>> 
>>>> On Thu, Aug 24, 2017 at 2:24 AM yukon  wrote:
>>>> 
>>>>> Hi,
>>>>> 
>>>>> We have updated the latest incubation status report to RocketMQ podling
>>>>> status page[1], also updated the resolution[2] according to
>>>>> Jim's suggestion.
>>>>> 
>>>>> Can we pick this thread up, sincerely hope IPMC can give some opinions
>>> to
>>>>> RocketMQ community.
>>>>> 
>>>>> [1] http://incubator.apache.org/projects/rocketmq.html
>>>>> [2]
>>>>> 
>>> https://cwiki.apache.org/confluence/display/ROCKETMQ/Graduation+Checklist
>>>>> 
>>>>> Regards,
>>>>> yukon
>>>>> 
>>>>> On Wed, Aug 23, 2017 at 4:14 PM, Von Gosling 
>>>>> wrote:
>>>>> 
>>>>>> Greetings Incubator,
>>>>>> 
>>>>>> The RocketMQ podling has decided to pursue graduation to a TLP. The
>>>>>> discuss thread[1] and The result of the RocketMQ vote in RocketMQ
>>>>> community
>>>>>> is at [2][3]. Our podling status page has recently been updated and
>>> can
>>>>> be
>>>>>> found here[4]. More graduation statement, including Maturity
>>> Evaluation,
>>>>>> please refer to [5].
>>>>>> 
>>>>>> Below, you can view the proposed TLP resolution which we'd like to
>>>>> present
>>>>>> to the board with the support of the IPMC, after sufficient discussion
>>>>> here
>>>>>> and subsequent IPMC vote.
>>>>>> 
>>>>>> [1]
>>> https://lists.apache.org/thread.html/9a11743e18cf15c1c7ecbd6be7d204
>>>>>> 1453d5838a4ed2d1b8457f5dbc@%3Cprivate.rocketmq.apache.org%3E
>>>>>> [2]
>>> https://lists.apache.org/thread.html/6fabcac0aeb8f649ee5e8ba2ab0c86
>>>>>> 7a01d3e836c9adbd9072dc738e@%3Cdev.rocketmq.apache.org%3E
>>>>>> [3]
>>> https://lists.apache.org/thread.html/40cca6b958bdf0f9ec698ef35e5418
>>>>>> 7fe8846

[VOTE] Graduate Apache RocketMQ from podling to TLP

[Von Gosling]

Hello IPMC,

The recent DISCUSS thread in PPMC, IPMC and VOTE thread in Community on the 
topic of Apache RocketMQ graduation have been opened for at least 72 hours, and 
I believe all questions have been answered and issues addressed at this point.

With the discussion having settled down, I would now like to call for a 
recommendation VOTE to present the ASF board with the following resolution to 
graduate from incubation and establish Apache RocketMQ as a top-level project 
(TLP).

RocketMQ PPMC DISCUSS thread:
https://lists.apache.org/thread.html/9a11743e18cf15c1c7ecbd6be7d2041453d5838a4ed2d1b8457f5dbc@%3Cprivate.rocketmq.apache.org%3E
 
<https://lists.apache.org/thread.html/9a11743e18cf15c1c7ecbd6be7d2041453d5838a4ed2d1b8457f5dbc@%3Cprivate.rocketmq.apache.org%3E>
 

RocketMQ IPMC DISCUSS thread:
https://lists.apache.org/thread.html/2b84fa29cb3e7ce54a683a72e97f304b19321521b37435909c097e64@%3Cgeneral.incubator.apache.org%3E
https://lists.apache.org/thread.html/81a7710c71ed4d79e940fb0c5fcb0620b31e87297520fd7ceedf0cf2@%3Cgeneral.incubator.apache.org%3E
 
<https://lists.apache.org/thread.html/81a7710c71ed4d79e940fb0c5fcb0620b31e87297520fd7ceedf0cf2@%3Cgeneral.incubator.apache.org%3E>

RocketMQ Community VOTE thread:
https://lists.apache.org/thread.html/6fabcac0aeb8f649ee5e8ba2ab0c867a01d3e836c9adbd9072dc738e@%3Cdev.rocketmq.apache.org%3E
 
<https://lists.apache.org/thread.html/6fabcac0aeb8f649ee5e8ba2ab0c867a01d3e836c9adbd9072dc738e@%3Cdev.rocketmq.apache.org%3E>
 

RocketMQ Community VOTE RESULT thread:
https://lists.apache.org/thread.html/40cca6b958bdf0f9ec698ef35e54187fe884600c1fed4f98a79c1c2c@%3Cdev.rocketmq.apache.org%3E
 
<https://lists.apache.org/thread.html/40cca6b958bdf0f9ec698ef35e54187fe884600c1fed4f98a79c1c2c@%3Cdev.rocketmq.apache.org%3E>
 


Apache RocketMQ entered incubation in November 2016. Since then there have been 
two releases and four committers and one PMC candidate member have been added 
to the project. For each release, source and binary artifacts have been made 
available. Based on the completed maturity evaluation we believe that the 
project is ready to graduate from the incubator. More checklist info about 
graduation, please refer to  
https://cwiki.apache.org/confluence/display/ROCKETMQ/Graduation+Checklist 
<https://cwiki.apache.org/confluence/display/ROCKETMQ/Graduation+Checklist> 


Please vote on whether to recommend the following graduation resolution to the 
ASF Board.

[  ]  +1, In favor of recommending the following graduation resolution to the 
ASF Board to establish Apache RocketMQ as a TLP
[  ]  +0, Neither opposed to, nor in favor of, recommending the following 
graduation resolution to the Board
[  ]  -1, Opposed to recommending the following graduation resolution to the 
Board(provide details)

This VOTE will be open for at least 72 hours. Here is my vote +1. Thanks to all 
Mentors and Apache RocketMQ Project members for their support and contributions 
again.

The full text of the resolution is below. If approved by the Apache Incubator 
PMC members, the proposed resolution will be submitted to the Board of 
Directors for their consideration.

Establish the Apache RocketMQ Project
WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to establish
a Project Management Committee charged with the creation and maintenance
of open-source software, for distribution at no charge to the public,
related to a fast, low latency, reliable, scalable, distributed, easy to
use message-oriented middleware, especially for processing large amounts
of streaming data.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache RocketMQ Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache RocketMQ Project be and hereby is responsible
for the creation and maintenance of software related to a fast, low
latency, reliable, scalable, distributed, easy to use message-oriented
middleware, especially for processing large amounts of streaming data;
and be it further
RESOLVED, that the office of "Vice President, Apache RocketMQ" be and
hereby is created, the person holding such office to serve at the
direction of the Board of Directors as the chair of the Apache RocketMQ
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache RocketMQ
Project; and be it further
RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache RocketMQ
Project:

* Bruce Snyder 
* Justin Mclean 
* Jim Jagielski 
* Willem Ning Jiang 
* Von Gosling  
* Xiaorui Wang 
* Xinyu Zhou 
* Zhanhui Li 
* Jixiang Jin 
* Zhendong Liu 


NOW, THEREFORE, BE IT FURTHER RESOLVED, that Xiaorui Wang be appointed to
the office of Vice President, Apache R

[RESULT][VOTE] Graduate Apache RocketMQ from podling to TLP

[Von Gosling]

Hello IPMC,

As 72 hours have elapsed, the voting period has concluded, and the vote passes.

4 +1 (binding) votes: 
* John D Ament
* Bruce Snyder
* Willem Jiang
* Justin Mclean

11 +1 (non-binding) votes:
* Von Gosling
* Xin Wang
* Huxing Zhang
* Kevin Ratnasekera
* lollipop
* liuxue
* John Fang
* Dia Lin
* yukon
* dongeforever
* William Guo   


Many thanks to everyone who voted for your support.  

Best Regards,
Von Gosling


> 在 2017年8月30日，10:13，Von Gosling  写道：
> 
> Hello IPMC,
> 
> The recent DISCUSS thread in PPMC, IPMC and VOTE thread in Community on the 
> topic of Apache RocketMQ graduation have been opened for at least 72 hours, 
> and I believe all questions have been answered and issues addressed at this 
> point.
> 
> With the discussion having settled down, I would now like to call for a 
> recommendation VOTE to present the ASF board with the following resolution to 
> graduate from incubation and establish Apache RocketMQ as a top-level project 
> (TLP).
> 
> RocketMQ PPMC DISCUSS thread:
> https://lists.apache.org/thread.html/9a11743e18cf15c1c7ecbd6be7d2041453d5838a4ed2d1b8457f5dbc@%3Cprivate.rocketmq.apache.org%3E
>  
> <https://lists.apache.org/thread.html/9a11743e18cf15c1c7ecbd6be7d2041453d5838a4ed2d1b8457f5dbc@%3Cprivate.rocketmq.apache.org%3E>
>  
> 
> RocketMQ IPMC DISCUSS thread:
> https://lists.apache.org/thread.html/2b84fa29cb3e7ce54a683a72e97f304b19321521b37435909c097e64@%3Cgeneral.incubator.apache.org%3E
>  
> <https://lists.apache.org/thread.html/2b84fa29cb3e7ce54a683a72e97f304b19321521b37435909c097e64@%3Cgeneral.incubator.apache.org%3E>
> https://lists.apache.org/thread.html/81a7710c71ed4d79e940fb0c5fcb0620b31e87297520fd7ceedf0cf2@%3Cgeneral.incubator.apache.org%3E
>  
> <https://lists.apache.org/thread.html/81a7710c71ed4d79e940fb0c5fcb0620b31e87297520fd7ceedf0cf2@%3Cgeneral.incubator.apache.org%3E>
> 
> RocketMQ Community VOTE thread:
> https://lists.apache.org/thread.html/6fabcac0aeb8f649ee5e8ba2ab0c867a01d3e836c9adbd9072dc738e@%3Cdev.rocketmq.apache.org%3E
>  
> <https://lists.apache.org/thread.html/6fabcac0aeb8f649ee5e8ba2ab0c867a01d3e836c9adbd9072dc738e@%3Cdev.rocketmq.apache.org%3E>
>  
> 
> RocketMQ Community VOTE RESULT thread:
> https://lists.apache.org/thread.html/40cca6b958bdf0f9ec698ef35e54187fe884600c1fed4f98a79c1c2c@%3Cdev.rocketmq.apache.org%3E
>  
> <https://lists.apache.org/thread.html/40cca6b958bdf0f9ec698ef35e54187fe884600c1fed4f98a79c1c2c@%3Cdev.rocketmq.apache.org%3E>
>  
> 
> 
> Apache RocketMQ entered incubation in November 2016. Since then there have 
> been two releases and four committers and one PMC candidate member have been 
> added to the project. For each release, source and binary artifacts have been 
> made available. Based on the completed maturity evaluation we believe that 
> the project is ready to graduate from the incubator. More checklist info 
> about graduation, please refer to  
> https://cwiki.apache.org/confluence/display/ROCKETMQ/Graduation+Checklist 
> <https://cwiki.apache.org/confluence/display/ROCKETMQ/Graduation+Checklist> 
> 
> 
> Please vote on whether to recommend the following graduation resolution to 
> the ASF Board.
> 
> [  ]  +1, In favor of recommending the following graduation resolution to the 
> ASF Board to establish Apache RocketMQ as a TLP
> [  ]  +0, Neither opposed to, nor in favor of, recommending the following 
> graduation resolution to the Board
> [  ]  -1, Opposed to recommending the following graduation resolution to the 
> Board(provide details)
> 
> This VOTE will be open for at least 72 hours. Here is my vote +1. Thanks to 
> all Mentors and Apache RocketMQ Project members for their support and 
> contributions again.
> 
> The full text of the resolution is below. If approved by the Apache Incubator 
> PMC members, the proposed resolution will be submitted to the Board of 
> Directors for their consideration.
> 
> Establish the Apache RocketMQ Project
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to a fast, low latency, reliable, scalable, distributed, easy to
> use message-oriented middleware, especially for processing large amounts
> of streaming data.
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache RocketMQ Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
> RESOLVED, that the Apache RocketMQ Project be and hereby is responsible
> for the 

Re: Crail project looking for mentors

[Von Gosling]

Hi Crail Guys,

I am Apache RocketMQ PMC member. Although I have learned I can't be a formal 
mentor(Not ASF member), I am wiling to stick around with you guys - informal 
mentor. Not only I am interested in crail storage platform, But RocketMQ has 
graduated from podling -  I have learned some experience from Incubator. Hoping 
to help any way I can :-)



Best Regards,
Von Gosling

> 在 2017年10月19日，07:58，John D. Ament  写道：
> 
> On Wed, Oct 18, 2017 at 3:37 PM Clebert Suconic 
> wrote:
> 
>> Let me be an informal mentor? I will help any way I can...
>> 
> 
> Being an informal mentor can sometimes be the path to becoming an IPMC
> member, and later a mentor for other projects.
> 
> 
>> 
>> 
>> If you need a formal member for completing the application.. let me know.
>> 
>> 
>> there was also Gary Wang interested in...
>> 
>> On Wed, Oct 18, 2017 at 3:15 PM, Abhishek Tiwari  wrote:
>>> Not being on IPMC shouldn't block you as far as I know. Someone can be
>>> voted in to IPMC if they are willing to put in the effort to be the
>> mentor?
>> 
> 
> Per the Incubator's policies, only IPMC members can be mentors to new
> podlings.  We have an "open door" policy that allows all foundation members
> to join the IPMC in a compulsory fashion.  Otherwise, just like any other
> PMC, we are merit based.  We see people who participate in projects and are
> clearly making a difference, use that to identify new PMC members.
> 
> 
>>> 
>>> On Wed, Oct 18, 2017 at 11:42 AM, Clebert Suconic <
>> clebert.suco...@gmail.com
>>>> wrote:
>>> 
>>>> I just learned I can't be a mentor.. as I'm not on the IPMC...
>>>> 
>>>> but I will stick around with you guys :) let me know when it's the
>>>> right time to have technical discussions.. I have got a few things I
>>>> would change ... but in a way it wouldn't break what you have now.
>>>> 
>>>> On Wed, Oct 18, 2017 at 1:13 PM, Gang(Gary) Wang 
>> wrote:
>>>>> I'm a PPMC at Mnemonic project,  we got interested in this project
>>>> because
>>>>> our project is working on Ceph memory service for our Durable object
>>>> model
>>>>> (DOM) and Durable computing model (DCM). Crail could be a promising
>> and
>>>>> more efficient solution for us to take fully advantage of the RDMA
>>>>> capabilities for durable object exchange across nodes in a cluster.
>> I'm
>>>>> looking forward to integrating Crail soon...
>>>>> 
>>>>> 
>>>>> 
>>>>> On Tue, Oct 17, 2017 at 9:18 PM, patrick stuedi 
>>>> wrote:
>>>>> 
>>>>>> Efficient asynchronous I/O is one key aspect in Crail, because we're
>>>>>> directly leveraging the asynchronous hardware interfaces of NVMe,
>>>>>> RDMA, etc and export them at the distributed systems level. If you
>>>>>> have experience with libaio and similar interfaces then that's
>>>>>> definitely related.. Crail is a distributed storage system designed
>>>>>> for high-performance storage and networking hardware, tailored to
>>>>>> support data processing in new data center deployments. If you're
>>>>>> interested in becoming a mentor please let us know...
>>>>>> 
>>>>>> On Wed, Oct 18, 2017 at 5:44 AM, Clebert Suconic
>>>>>>  wrote:
>>>>>>> I have written a libaio wrapper in java.  For artemis and high
>>>>>> performance
>>>>>>> sync IOs.
>>>>>>> 
>>>>>>> 
>>>>>>> Would that work be related sim any form ?
>>>>>>> 
>>>>>>> On Tue, Oct 17, 2017 at 11:37 PM Luciano Resende <
>>>> luckbr1...@gmail.com>
>>>>>>> wrote:
>>>>>>> 
>>>>>>>> On Fri, Oct 13, 2017 at 5:58 PM, patrick stuedi <
>> pstu...@gmail.com>
>>>>>> wrote:
>>>>>>>> 
>>>>>>>>> Hi all,
>>>>>>>>> 
>>>>>>>>> The Crail project (www.crail.io) is looking for additional
>> mentors
>>>>>>>>> helping with the Apache incubator process. A draft of the Crail
>>>>>>>>> incubator proposal is available here:
>>>>>>>>> 
&

Re: [DISCUSS] Storage-class memory ecosystem program

[Von Gosling]

I'm happy to represent Apache RocketMQ on this  storage collaboration effort. 
This is a very key in low latency messaging.

Best Regards,
Von Gosling



> 在 2017年10月20日，02:55，Gang(Gary) Wang  写道：
> 
> Hi all,
> 
> We can expect more and more projects will take the huge potential
> advantages of storage-class memory for data processing and analytics
> because silicon companies are able to produce high capacity non-volatile
> memory on a large scale, this hardware technology will fundamentally change
> the way to construct high performance applications similar to what happened
> when replacing tape with disk technology since the 1980s. so if possible, I
> advocate establishing an Apache working group to enhance the collaboration
> and synergies mentioned by Patrick Stuedi for storage-class memory
> technology-oriented projects.
> 
> Best.
> Gary.


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

Re: [VOTE] Resolution to graduate Apache Impala to TLP

[Von Gosling]

+1

Best Regards,
Von Gosling

> 在 2017年11月9日，12:25，Jim Apple  写道：
> 
> The graduation of Impala to a TLP has been discussed[0] on dev@impala,
> voted on[1] on dev@impala, and discussed[2] on general@incubator. All
> threads were open 72 hours or more, and all seem to have quiesced.
> 
> This is a call for a VOTE to graduate Impala to a TLP. The draft resolution
> is below. Please select from:
> 
> [ ] +1: Graduate Impala to a TLP
> [ ] +-0: Neither graduate nor do not graduate Impala to a TLP
> [ ] -1: Do NOT graduate Impala to a TLP, because ...
> 
> 
> 
> [0]: <
> https://lists.apache.org/thread.html/2f5db4788aff9b0557354b9106c0328a29c1f90c1a74a228163949d2@%3Cdev.impala.apache.org%3E
>> 
> 
> [1]: <
> https://lists.apache.org/thread.html/a5a7c6895b3e019347d6e4e4cf49d67d094d31b8f2c7b4d59200f3e4@%3Cdev.impala.apache.org%3E
>> 
> 
> [2]: <
> https://lists.apache.org/thread.html/6b8598408f76a472532923c5a7fc510470b21671677ba3486568c57e@%3Cgeneral.incubator.apache.org%3E
>> 
> 
> 
> 
> Establish the Apache Impala Project
> 
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to a high-performance distributed SQL engine.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Impala Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
> 
> RESOLVED, that the Apache Impala Project be and hereby is responsible
> for the creation and maintenance of software related to a
> high-performance distributed SQL engine; and be it further
> 
> RESOLVED, that the office of "Vice President, Apache Impala" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache Impala
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Impala
> Project; and be it further
> 
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache Impala Project:
> 
> * Alex Behm 
> * Bharath Vissapragada 
> * Brock Noland 
> * Carl Steinbach 
> * Casey Ching 
> * Daniel Hecht 
> * Dimitris Tsirogiannis 
> * Henry Robinson 
> * Ishaan Joshi 
> * Jim Apple 
> * John Russell 
> * Juan Yu 
> * Lars Volker 
> * Lenni Kuff 
> * Marcel Kornacker 
> * Martin Grund 
> * Matthew Jacobs 
> * Michael Brown 
> * Michael Ho 
> * Sailesh Mukil 
> * Skye Wanderman-Milne 
> * Taras Bobrovytsky 
> * Tim Armstrong 
> * Todd Lipcon 
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jim Apple be appointed to
> the office of Vice President, Apache Impala, to serve in accordance with
> and subject to the direction of the Board of Directors and the Bylaws of
> the Foundation until death, resignation, retirement, removal or
> disqualification, or until a successor is appointed; and be it further
> 
> RESOLVED, that the initial Apache Impala PMC be and hereby is tasked
> with the creation of a set of bylaws intended to encourage open
> development and increased participation in the Apache Impala Project;
> and be it further
> 
> RESOLVED, that the Apache Impala Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Impala
> podling; and be it further
> 
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Impala podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.


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

Re: [VOTE] Accept Druid into the Apache Incubator

[Von Gosling]

+1 (non-binding)

Best Regards,
Von Gosling

> 在 2018年2月23日，03:03，Julian Hyde  写道：
> 
> Hi all,
> 
> After some discussion on the Druid proposal[1], I'd like to
> start a vote on accepting Druid into the Apache Incubator,
> per the ASF policy[2] and voting rules[3].
> 
> A vote for accepting a new Apache Incubator podling is a
> majority vote for which only Incubator PMC member votes are
> binding. Votes from other people are also welcome as an
> indication of people's enthusiasm (or lack thereof).
> 
> Please do not use this VOTE thread for discussions.  If
> needed, start a new thread instead.
> 
> This vote will run for at least 72 hours. Please VOTE as
> follows:
> [ ] +1 Accept Druid into the Apache Incubator
> [ ] +0 Abstain
> [ ] -1 Do not accept Druid into the Apache Incubator
>because ...
> 
> The proposal is listed below, but you can also access it on
> the wiki[4].
> 
> Julian
> 
> [1] 
> https://lists.apache.org/thread.html/b95f90a30b6e8587e9b108f368b07c1b3e23e25ca592448d9c9f81e2@%3Cgeneral.incubator.apache.org%3E
> 
> [2] 
> https://incubator.apache.org/policy/incubation.html#approval_of_proposal_by_sponsor
> 
> [3] http://www.apache.org/foundation/voting.html
> 
> [4] https://wiki.apache.org/incubator/DruidProposal
> 
> 
> 
> 
> 
> = Druid Proposal =
> 
> == Abstract ==
> 
> Druid is a high-performance, column-oriented, distributed
> data store.
> 
> == Proposal ==
> 
> Druid is an open source data store designed for real-time
> exploratory analytics on large data sets. Druid's key
> features are a column-oriented storage layout, a distributed
> shared-nothing architecture, and ability to generate and
> leverage indexing and caching structures. Druid is typically
> deployed in clusters of tens to hundreds of nodes, and has
> the ability to load data from Apache Kafka and Apache
> Hadoop, among other data sources. Druid offers two query
> languages: a SQL dialect (powered by Apache Calcite) and a
> JSON-over-HTTP API.
> 
> Druid was originally developed to power a slice-and-dice
> analytical UI built on top of large event streams. The
> original use case for Druid targeted ingest rates of
> millions of records/sec, retention of over a year of data,
> and query latencies of sub-second to a few seconds. Many
> people can benefit from such capability, and many already
> have (see http://druid.io/druid-powered.html). In addition,
> new use cases have emerged since Druid's original
> development, such as OLAP acceleration of data warehouse
> tables and more highly concurrent applications operating
> with relatively narrower queries.
> 
> == Background ==
> 
> Druid is a data store designed for fast analytics. It would
> typically be used in lieu of more general purpose query
> systems like Hadoop MapReduce or Spark when query latency is
> of the utmost importance. Druid is often used as a data
> store for powering GUI analytical applications.
> 
> The buzzwordy description of Druid is a high-performance,
> column-oriented, distributed data store. What we mean by
> this is:
> 
> * "high performance": Druid aims to provide low query
>  latency and high ingest rates possible.
> * "column-oriented": Druid stores data in a column-oriented
>  format, like most other systems designed for analytics. It
>  can also store indexes along with the columns.
> * "distributed": Druid is deployed in clusters, typically of
>  tens to hundreds of nodes.
> * "data store": Druid loads your data and stores a copy of
>  it on the cluster's local disks (and may cache it in
>  memory). It doesn't query your data from some other
>  storage system.
> 
> == Rationale ==
> 
> Druid is a mature, active project with a large number of
> production installations, dozens of contributors to each
> release, and multiple vendors offering professional
> support. Given Druid's strong community, its close
> integration with many other Apache projects (such as Kafka,
> Hadoop, and Calcite), and its pre-existing Apache-inspired
> governance structure, we feel that Apache is the best home
> for the project on a long-term basis.
> 
> == Current Status ==
> 
> === Meritocracy ===
> 
> Since Druid was first open sourced the original developers
> have solicited contributions from others, including through
> our blog, the project mailing lists, and through accepting
> GitHub pull requests. We have an Apache-inspired governance
> structure with a PMC and committers, and our committer ranks
> include a good number of people from outside the original
> development team.
> 
> === Community ===
&g

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

[Von Gosling]

Hi,

Dubbo teams are making every endeavor to prepare the first formal release under 
the apache way, I also help teams to sweep away the binary and source liences 
problems :-) 


Best Regards,
Von Gosling

> 在 2018年5月10日，16:31，Huxing Zhang  写道：
> 
> Hi,
> 
> On Thu, May 10, 2018 at 3:59 PM, Willem Jiang  <mailto:willem.ji...@gmail.com>> wrote:
>> Is there any plan for going through the vote process of Binary file?
> 
> Yes, binaries will also go through the vote process.
> 
>> Normally there are lots of work on the License files of Binary durning the
>> first release.
>> Maybe we should need to vote the binary file as well.
>> 
>> 
>> Willem Jiang
>> 
>> Blog: http://willemjiang.blogspot.com (English)
>>  http://jnn.iteye.com  (Chinese)
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>> 
>> On Wed, May 9, 2018 at 4:34 PM, Huxing Zhang  wrote:
>> 
>>> On Wed, May 9, 2018 at 3:35 PM, Bertrand Delacretaz
>>>  wrote:
>>>> On Wed, May 9, 2018 at 3:44 AM, Huxing Zhang  wrote:
>>>>> ...The maven artifact is the most significant for most of the Dubbo
>>>>> users, so we want to include a maven artifact in the release
>>>> 
>>>> Binaries are NOT part of Apache Releases, as mentioned earlier in this
>>> thread.
>>> 
>>> Yes, we fully understood that.
>>> 
>>> Here what I mean "release" does not mean an Apache release, it is
>>> actually a "hybrid" release, which includes:
>>> 
>>> * source (following Apache release policy)
>>> * binary (it is optional but still following Apache release policy)
>>> * Maven artifacts under third-party coordinates (Non Apache release)
>>> 
>>>> 
>>>> Dubbo mentors, I think we need a clear description of how these
>>>> "hybrid" releases are done, to avoid any misunderstandings.
>>>> 
>>>> Justin mentioned in this thread that that's been discussed on your dev
>>>> list, so you probably just need to summarize that and include the URL
>>>> in your next Incubator report.
>>>> 
>>>> -Bertrand
>>> 
>>> --
>>> Best Regards！
>>> Huxing
>>> 
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>>> 
> 
> -- 
> Best Regards！
> Huxing

Re: [ANN] Please welcome Justin Mclean as the new Incubator PMC chair!

[Von Gosling]

Hi,

Thanks John D. Ament excellent effort for the Apache Incubator Projects, 
especially for your guide on our eastern apache projects :-)   

And welcome Justin, our incubator project mentor, very glad to have you as 
Incubator PMC chair.


Best Regards,
Von Gosling

> 在 2018年6月4日，18:12，Bertrand Delacretaz  写道：
> 
> John D. Ament 

Re: [DISCUSS] IP Clearance

[Von Gosling]

I agree the IPMC only should care about podling. But another question, Is it 
necessary to guarantee the IP clearance when in TLP, some new TLPs  maybe not 
realize the importance of this question :-)

> 在 2018年6月5日，03:30，Jim Jagielski  写道：
> 
> I can see the IPMC being responsible for IP clearance for new incoming 
> podlings and current podlings.
> 
> For code being donated directly to a current TLP, they should be able to do 
> all that is required to ensure correct clearance and provenance.
> 
> In other words, unless the code is for a podling, the IPMC shouldn't be 
> involved, IMHO.
> 
>> On Jun 4, 2018, at 1:46 PM, Dave Fisher  wrote:
>> 
>> Hi -
>> 
>> I think that the IP Clearance process has become very much a bureaucratic 
>> process where the IPMC is contributing little of value. Very seldom is there 
>> any feedback provided.
>> 
>> (1) It is separate from the SGA process for new podlings, but it is similar 
>> in that the Secretary will record the SGA and/or CCLA.
>> (2) The documentation is confusing about whether or not podlings need to 
>> follow it or not.
>> (3) Top Level Projects are supposed to understand how to clear IP as that is 
>> a major part of the incubation process. If there are any questions the 
>> legal-discuss mailing list and JIRA are available.
>> (4) The Incubator is already stretched to provide Mentoring to all of our 
>> Podlings and IP Clearance seems to be off topic and not really scalable.
>> (5) Once a TLP graduates from the Incubator it seems regressive to have to 
>> go back unless there is a Community around the grant to be Incubated. That 
>> would lead to a Podling Proposal and not IP Clearance.
>> 
>> I think that the IPMC should recommend to the Board that this recording 
>> process be fully moved to the Secretary.
>> 
>> Regards,
>> Dave
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


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

Re: [DISCUSS] IP Clearance

[Von Gosling]

clear ~~~

For Podlings, vote in IPMC and document it in the exist center place.
For TLPs, vote in its PMC and document in the exist center place.

> 在 2018年6月5日，16:53，Bertrand Delacretaz  写道：
> 
> clearance

Re: [VOTE] Accept Zipkin into the Apache Incubator

[Von Gosling]

+1, wish a stable host place for Zipkin :-) 


Best Regards,
Von Gosling

> 在 2018年8月27日，11:14，Mick Semb Wever  写道：
> 
> After a brief discussion¹ I would like to call a VOTE to accept Zipkin into 
> the Apache Incubator. 
> The full proposal is available on the wiki² and is pasted below in text form 
> as well.
> 
> This vote will run at least 72 hours. Please VOTE as follows:
> 
> [ ] +1 Accept Zipkin into the Apache Incubator
> [ ] +0 No opinion
> [ ] -1 Do not accept Zipkin into the Apache Incubator because…
> 
> regards,
> Mick
> 
> [1] 
> https://lists.apache.org/thread.html/54798a5059db1d5716ed9910a15c92945509a25ec3b7ccb6b1215c53@%3Cgeneral.incubator.apache.org%3E
> [2] https://wiki.apache.org/incubator/ZipkinProposal
> 
> 
> 
> = Abstract =
> Zipkin is a distributed tracing system. It helps gather timing data needed to 
> troubleshoot latency problems in microservice architectures. It manages both 
> the collection and lookup of this data. Zipkin’s design is based on the 
> Google Dapper paper.
> 
> = Proposal =
> Zipkin provides a defined data model and payload type for distributed trace 
> data collection. It also provides an UI and http api for querying the data. 
> Its server implements this api and includes abstractions for storage and 
> transport of trace payloads. The combination of these parts avoid lock-in to 
> a specific tracing backend. For example, Zipkin includes integration with 
> different open source storage mechanisms like Apache Cassandra and 
> Elasticsearch. It also includes bridges to convert collected data and forward 
> it to service offerings such as Amazon X-Ray and Google Stackdriver. 
> Ecosystem offering extend this portability further.
> 
> While primarily focused on the system, Zipkin also includes tracing libraries 
> which applications use to report timing information. Zipkin's core 
> organization includes tracer libraries written in Java, Javascript, Go, PHP 
> and Ruby. These libraries use the formats mentioned above to report data, as 
> well "B3" which is a header format needed to send trace identifiers along 
> with production requests. Many Zipkin libraries can also send data directly 
> to other services such as Amazon X-Ray and Google Stackdriver, skipping any 
> Zipkin infrastructure. There are also more Zipkin tracing libraries outside 
> the core organization than inside it. This is due to the "OpenZipkin" culture 
> of promoting ecosystem work.
> 
> = Background =
> Zipkin began in 2012 at Twitter during a time they were investigating 
> performance problems underlying the "fail whale" seen by users. The name 
> Zipkin is from the Turkish word for harpoon: the harpoon that will kill the 
> failures! Incidentally, Zipkin was not the first tracing system, it had roots 
> in a former system at Twitter named BigBrotherBird. It is due to 
> BigBrotherBird that the de-facto tracing headers we still use today include 
> the prefix "X-B3".
> 
> In 2015, a community of users noticed the project was not healthy in so far 
> as it hadn't progressed and often didn't accept pull requests, and the 
> Cassandra backend was stuck on an unmaintained library. For example, the 
> Apache Incubator H-Trace project started in some ways as a reaction to the 
> inability to customize the code. The root cause of this was Twitter moving to 
> internal storage (Manhattan) and also the project not being managed as a 
> product. By mid 2015, the community regrouped as OpenZipkin and the codebase 
> moved from Twitter to an org also named OpenZipkin. This led to fast progress 
> on concerns including initially a server rewrite and Docker based deployment.
> 
> In 2018, the second version of the data model completed, and along the way, 
> many new libraries became standard, including javascript, golang and PHP. The 
> community is dramatically larger than 2015, and Zipkin remains the most 
> popular tracing system despite heavy competition.
> 
> = Rationale =
> Zipkin is a de-facto distributed tracing system, which is more important as 
> architectures become more fine grained due to popularity of microservice or 
> even serverless architectures. Applications transition to use more complex 
> communication including asynchronous code and service mesh, increasing the 
> need for tools that visualize the behavior of requests as they map across an 
> architecture.
> 
> Zipkin's server is focused only on distributed tracing. It is meant to be 
> used alongside existing logging and metrics systems. Generally, the community 
> optimizes brown field concerns such as interop over breaking changes such as 
> experimental features. The combination of code and community make Zi

Re: [VOTE] Graduate Apache Pulsar (incubating) as a TLP

[Von Gosling]

+1, very glad to see the pulsar to embrace the openmessaging spec in the coming 
soon


Best Regards,
Von Gosling

> 在 2018年9月14日，10:57，Dave Fisher  写道：
> 
> Hi -
> 
>> On Sep 13, 2018, at 7:04 PM, Willem Jiang > <mailto:willem.ji...@gmail.com>> wrote:
>> 
>> I think this line is generated from the template to explain the
>> purpose of the project.
>> It's no harmful to keep it there I guess.
> 
> It is an expanded version of the original text as seen on 
> http://incubator.apache.org/projects/pulsar.html 
> <http://incubator.apache.org/projects/pulsar.html>
> 
> 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.
> 
> Vs.
> 
>>>> a highly
>>>> scalable, low latency messaging platform running on commodity hardware.
>>>> It provides simple pub-sub and queue semantics over topics, lightweight
>>>> compute framework, automatic cursor management for subscribers, and
>>>> cross-datacenter replication; 
> 
> Modification is “lightweight compute framework” replaces "guaranteed 
> at-least-once delivery of messages"
> 
>>> 
> 
>> 
>> Willem Jiang
>> 
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>> 
>> On Thu, Sep 13, 2018 at 4:49 AM sebb > <mailto:seb...@gmail.com>> wrote:
>>> 
>>> On 12 September 2018 at 16:40, Dave Fisher >> <mailto:dave2w...@comcast.net>> wrote:
>>>> Hi -
>>>> 
>>>> The Apache Pulsar project is ready to graduate as a TLP. They entered
>>>> Incubation on June 1, 2017, have had many releases and have grown the
>>>> community.
>>>> 
>>>> Vote:
>>>> [ ] +1 - Recommend Graduation of Apache Pulsar as a TLP
>>>> [ ] -1 - Do not recommend graduation of Apache Pulsar because ….
>>>> 
>>>> At the mentors request they did a maturity model analysis [1] and wrote
>>>> contribution guidelines. [2]
>>>> 
>>>> The Graduation Proposal was written and discussed on the dev list. [3] At
>>>> the mentor's recommendation the By-Laws Clause was removed.
>>>> 
>>>> The new prospective PMC is set and the VOTE thread in the podling is here
>>>> [4] with these results. [5]
>>>> 
>>>> Regards,
>>>> Dave
>>>> 
>>>> [1]
>>>> https://github.com/apache/incubator-pulsar/wiki/Apache-Maturity-Model-Assessment-for-Pulsar
>>>>  
>>>> <https://github.com/apache/incubator-pulsar/wiki/Apache-Maturity-Model-Assessment-for-Pulsar>
>>>> [2] http://pulsar.incubator.apache.org/en/contributing/
>>>> [3]
>>>> https://lists.apache.org/thread.html/b0914461f57253237e4a3c9151342f6d4fa37359dfc98a07adf9f36f@%3Cdev.pulsar.apache.org%3E
>>>> [4]
>>>> https://lists.apache.org/thread.html/93198abe36564a9e11a2a1bfe3ea8f35998444dbafea830f8b39df7b@%3Cdev.pulsar.apache.org%3E
>>>> [5]
>>>> https://lists.apache.org/thread.html/64841a07ba3dee2271f4098f9142afd41acffae1736275592aab4c83@%3Cdev.pulsar.apache.org%3E
>>>> 
>>>> 
>>>> 
>>>> 
>>>> Establish the Apache Pulsar Project
>>>> 
>>>> WHEREAS, the Board of Directors deems it to be in the best interests of
>>>> the Foundation and consistent with the Foundation's purpose to establish
>>>> a Project Management Committee charged with the creation and maintenance
>>>> of open-source software, for distribution at no charge to the public,
>>>> related to a highly scalable, low latency messaging platform running on
>>>> commodity hardware. It provides simple pub-sub and queue semantics over
>>>> topics, lightweight compute framework, automatic cursor management for
>>>> subscribers, and cross-datacenter replication.
>>> 
>>> Such detail as provided in the last sentence is unusual for graduation
>>> resolutions.
>>> I think the last sentence should be dropped from the resolution; it's
>>> not necessary.
>>> 
>>>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>>>> (PMC), to be known as the "Apache Pulsar Project", be and hereby is
>>>> established pursuant to Bylaws of the Foundation; a

Re: We want to contribute brpc to ASF, looking for champion and mentor ,please help

[Von Gosling]

Hi,

I am excited to see a new rpc framework grow and flourish in apache 
comprehensive culture, rpc is so important infrastructure as messaging. Also, I 
am glad to help brpc community to learn and incubate smoothly under the Apache 
Way. After a look through about brpc , I  have one question that what’s the 
plan for our brpc future? I noticed that your mention brpc is an c++ rpc 
framework. AFAIK, sole language-lock rpc framework will not go far away in 
nowadays, especially facing the challenge of the new cloud computing paradigm, 
such as serverless and so on.


Best Regards,
Von Gosling

> 2. brpc is alternative for C++ rpc fcramework，implementations for other
> languages are not competitive enough (comparing to gRPC) to be
> opensourced.  Besides the basic RPC function, brpc(C++) provides
> additional features than gRPC:
>   - Clients and servers can talk in multiple protocols: baidu internal
> protocol, http, thrift, http2(communicable with gRPC, the PR is under
> reviewing) and tens of other protocols.
>   - Proved better performance in different scenarios, by eliminating
> locks on hotpaths and using goroutine-like concurrency(bthread) with cache
> friendly data structures
>   - More useful debugging utilities to help C++ programers build solid
> online services.
>   - Various access patterns such as one-to-one, one-to-many(fan out),
> streaming, which simplify implementation of complex distributed services.




> 在 2018年9月14日，16:19，Tan,Zhongyi  写道：
> 
> Hi， JB，
> Below are our answers to your questions，
> Please check，
> Thanks.
> 
> 1. brpc doesn't depend on any other Apache projects. brpc currently
> depends on the following external project:
>   - leveldb
>   - openssl
>   - protobuf
>   - gperftools (optional)
>   - glog (optional)
>   - gtest
> 
> 2. brpc is alternative for C++ rpc fcramework，implementations for other
> languages are not competitive enough (comparing to gRPC) to be
> opensourced.  Besides the basic RPC function, brpc(C++) provides
> additional features than gRPC:
>   - Clients and servers can talk in multiple protocols: baidu internal
> protocol, http, thrift, http2(communicable with gRPC, the PR is under
> reviewing) and tens of other protocols.
>   - Proved better performance in different scenarios, by eliminating
> locks on hotpaths and using goroutine-like concurrency(bthread) with cache
> friendly data structures
>   - More useful debugging utilities to help C++ programers build solid
> online services.
>   - Various access patterns such as one-to-one, one-to-many(fan out),
> streaming, which simplify implementation of complex distributed services.
> 
> 
> 
> 在 2018/9/13 下午3:00， "Jean-Baptiste Onofré"  写入:
> 
>> Hi,
>> 
>> It's an interesting project. I have two questions:
>> 
>> 1. do you have some interactions/dependencies with other Apache
>> projects, especially CXF for instance ?
>> 2. what's the comparison between brpc and gRPC ? An alternative ?
>> Different features ?
>> 
>> I might be interested by mentoring the project, I would like to
>> understand exactly the target/purposes.
>> 
>> Thanks !
>> Regards
>> JB
>> 
>> On 13/09/2018 08:20, Tan,Zhongyi wrote:
>>> Hi, guys,
>>> 
>>> brpc is one open source RPC framework that is very popular in baidu and
>>> china.
>>> We want to contribute it to ASF to make it more successful.
>>> And we are looking for champion and mentor for this project,
>>> if anyone would like to volunteer, we will be very appreciated.
>>> 
>>> Thanks.
>>> 
>>> 
>>> Here is the draft for brpc proposal.
>>> 
>>> 
>>> # brpc Proposal
>>> 
>>> ## Abstract
>>> 
>>> brpc is an industrial-grade RPC framework for building reliable and
>>> high-performance services.
>>> 
>>> ## Proposal
>>> 
>>> We propose to contribute the brpc codebase and associated
>>> artifacts(e.g. documentation etc.) to the Apache Software Foundation,
>>> and aim to  build a wider open community around it in the 'Apache Way'.
>>> 
>>> 
>>> ## Background
>>> 
>>> The RPC framework used in Baidu before 2014 was developed at 2008 and
>>> limited in protocols and performance, and there were also serveral
>>> implementations focused on their own scenarios from Baidu's different
>>> BU. As an infrastructural team in Baidu, we tried to build a new
>>> framework to unify all RPC scenarios inside. The framework was named
>>> "baidu-rpc" internally the early versions