+1

在 2019/12/13 上午11:38,“Bear Jiang”<[email protected]> 写入:

    +1
    
    On Thu, Dec 12, 2019 at 11:51 AM Zhangyi Chen <[email protected]> wrote:
    
    > +1
    >
    > On Thu, Dec 12, 2019 at 11:17 AM James Ge <[email protected]> wrote:
    >
    > > +1
    > >
    > > On Thu, Dec 12, 2019 at 11:12 AM JiashunZhu <[email protected]>
    > > wrote:
    > >
    > > > +1.
    > > >
    > > > tan zhongyi <[email protected]> 于2019年12月11日周三 下午11:26写道:
    > > >
    > > > > Hi, guys,
    > > > >
    > > > > Let us vote to accept Helei as committer.
    > > > > Please reply +1 if you agree,
    > > > > Reply -1 if you disagree, together with your reason.
    > > > > Thanks
    > > > >
    > > > >
    > > > > Below is his application:
    > > > >
    > > > > "Hello, I'm he Lei from iqiyi advertising department. I'm mainly
    > > > > responsible for the infrastructure of advertising engine. My home
    > page
    > > of
    > > > > GitHub is https://github.com/tousakarin. My team introduced brpc in
    > > > 2017,
    > > > > and adopted brpc for most of the background services of advertising
    > > > engine.
    > > > > We maintain our own branch within iqiyi, and regularly synchronize
    > code
    > > > > with the community, and also push some features and bug fix to the
    > > > > community. During this period, I pushed features such as consumer
    > name
    > > > > service, automatic current limiting, single node fusing, multi
    > > connection
    > > > > mode and some bug fix to the community. The automatic current
    > limiting
    > > > and
    > > > > single node fusing functions are mainly developed by me and have 
been
    > > > > merged to the master branch.
    > > > >
    > > > > Next, I hope to further participate in the development and promotion
    > of
    > > > > brpc, including but not limited to 1. Participate in the discussion
    > of
    > > > > distribution / technical route. 2. Bug fix and provide features. 3.
    > The
    > > > > promotion of brpc"
    > > > >
    > > > >
    > > > >
    > > >
    > > > --
    > > > Jiashun Zhu
    > > >
    > >
    >
    

Reply via email to