Re: [VOTE] Heron Release 0.20.0-incubating Candidate 5

[Fu Maosong]

Sorry Justin,

Previously I read
`
PMC members have formally binding votes, but in general community members
are encouraged to vote, even if their votes are only advisory.
`

I learned now. Thanks!

Justin Mclean  于2018年11月8日周四 下午7:15写道：

> Hi,
>
> > On 9 Nov 2018, at 11:07 am, Fu Maosong  wrote:
> >
> > +1 (binding)
>
> Thanks, for voting but Just a reminder that only IPMC votes are binding.
>
> Thanks,
> Justin
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-- 
With my best Regards
--
Fu Maosong
Twitter Inc.
Mobile: +001-415-244-7520

Re: [PROPOSAL] Changing requirements for IPMC

[Dave Fisher]

Hi -

Sent from my iPhone

> On Nov 8, 2018, at 3:43 AM, Myrle Krantz  wrote:
> 
>> On Wed, Nov 7, 2018 at 7:10 PM Dave Fisher  wrote:
>> 
>> Hi -
>> 
 ...I propose this:
 
 If someone has done several of the following:
 - has been involved in an incubating project from start to finish
 - has been a release manager
 - has assembled LICENSE and NOTICE files
 - has reviewed and voted on releases
 - has proposed or accepted committers/PPMC members
 
 Then they can ask the IPMC to join to IPMC by sending an email to
>> private@ listing what they have been involved in...
>>> 
>>> I like that, +1
>> 
>> I think that those items are hard to measure and are oriented to release
>> policy only.
>> 
>> I would propose a simpler requirement.
>> 
>> - Any PMC member of any TLP including ComDev. We then do formal NOTICE to
>> the Board and if there is a concern address it.
>> 
> 
> You're right that some (not all) of the items are hard to measure.  I think
> your counter-proposal would just push work to the Board (who simply won't
> do it),

Well the IPMC and not the Board. I admit I was pushing an extreme position as a 
device for focus.

> and may result in podlings getting stuck with inactive mentors, and
> limbo'ed releases.  Perhaps it's possible to cut the original list down to
> things that are measurable, and change the approach from one of enforcement
> to one of enlistment:
> 
> * Is willing and able to review and vote on releases for the podling.
> * Is willing and able to coach the podling in proposing and accepting
> committers/PPMC members.
> 
> The real goal here, I think, is not to specify criteria that the IPMC or
> the board can apply.  The real goal is two-fold: a.) to give a potential
> mentor the information necessary to determine if they can do the job.  And
> b.) to create an instrument of commitment.  The mentor commits to involve
> themselves in specific ways in the podling's incubation.

Yes, and commitment is the key. The IPMC can fix this if we take some examples.

(1) We have elected non-members to the IPMC. I was one. We should be more 
active in identifying merit.
(2) We take Justin’s and/or your list of criteria.
(3) We discuss potential IPMC candidates on private using the Beam model 
discussed dev@community. Specifically we start threads on private@incubator to 
track candidates as soon as an IPMC identifies a podling member getting the 
Apache Way.
(4) As merit is acquired we VOTE on private@incubator.

This approach follows the Apache Way. It makes the IPMC more closely operate 
like all other PMCs that are under the Board.

Regards,
Dave


> 
> Best Regards,
> Myrle


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

Re: [VOTE] Ratis-thirdparty 0.1.0rc1

[Justin Mclean]

Hi,

+1 (binding)

I checked:
- incubating in name
- signature and hashes fine, but you may want to check the file extensions as 
policy changed a little while back to what was allowed
- LICENSE and NOTICE good
- no binary files
- no source files, but poms have ASF headers
- can compile from “source"

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

Re: [VOTE] Sharding-Sphere incubation proposal

[Benjamin Hindman]

+1

On Thu, Nov 8, 2018 at 12:18 PM Gilbert Song  wrote:

> +1 (non-binding).
>
> - Gilbert
>
> On 2018/11/07 17:44:21, Raja Sundaram Ganesan  wrote:
> > +1 (Non Binding)
> >
> >
> >
> > On Wed 7 Nov, 2018, 11:02 vintagewang  >
> > > +1 (non-binding)
> > >
> > > XIAORUI Wang
> > >
> > > zhangli...@apache.org 于2018年11月7日 周三09:30写道：
> > >
> > > > +1 (non-binding)
> > > >
> > > > Thanks,
> > > > John(Zhang Liang) from Sharding-Sphere
> > > >
> > > > Bruno Mahé  于2018年11月7日周三 上午1:37写道：
> > > >
> > > > > +1 (non-binding)
> > > > >
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Bruno
> > > > >
> > > > > On 11/5/18 10:41 PM, Roman Shaposhnik wrote:
> > > > > > Hi!
> > > > > >
> > > > > > on behalf of Sharding-Sphere community, I'd like to call
> > > > > > a VOTE to accept it into the Apache Incubator. The full
> > > > > > proposal is available on the wiki:
> > > > > >  https://wiki.apache.org/incubator/ShardingSphereProposal
> > > > > > and it is also attached below for your convenience.
> > > > > >
> > > > > > Please cast your vote:
> > > > > >
> > > > > >[ ] +1, bring Sharding-Sphere into Incubator
> > > > > >[ ] +0, I don't care either way,
> > > > > >[ ] -1, do not bring Sharding-Sphere into Incubator,
> because...
> > > > > >
> > > > > > The vote will open at least for 72 hours.
> > > > > >
> > > > > > Thanks,
> > > > > > Roman.
> > > > > >
> > > > > > = Abstract =
> > > > > > Sharding-Sphere is an ecosystem of transparent distributed
> database
> > > > > > middleware, focusing on data sharding, distributed transaction
> and
> > > > > > database orchestration. It provides maximum compatibility for
> > > > > > applications through Sharding-JDBC (a driver to implement JDBC)
> or
> > > > > > Sharding-Proxy (a proxy to implement database protocol).
> > > > > >
> > > > > > = Proposal =
> > > > > > With a large number of end users, Sharding-Sphere has a fairly
> huge
> > > > > > community in China. It is also widely adopted by many
> > > > > > [[http://shardingsphere.io/community/en/company/|companies and
> > > > > > organizations]] as a solution to process their massive amounts of
> > > > > > data.
> > > > > >
> > > > > > We believe that bringing Sharding-Sphere into Apache Software
> > > > > > Foundation could advance development of a stronger and more
> diverse
> > > > > > open source community.
> > > > > >
> > > > > > Dangdang submits this proposal to donate Sharding-Sphere's source
> > > > > > codes and all related documentations to Apache Software
> Foundation.
> > > > > > The codes are already under Apache License Version 2.0.
> > > > > >
> > > > > >* Code base:
> https://github.com/sharding-sphere/sharding-sphere
> > > > > >
> > > > > >* Web site: http://shardingsphere.io/
> > > > > >
> > > > > >* Documentations: http://shardingsphere.io/document/current/
> > > > > >
> > > > > >* Community: http://shardingsphere.io/community/
> > > > > >
> > > > > > = Background =
> > > > > >
> > > > > > Relational database hardly supports such huge amounts of data any
> > > more
> > > > > > which has increased rapidly in recent years, but for reason of
> > > > > > technique maturity, developers and DBAs still want to use it to
> > > > > > persist core data.
> > > > > >
> > > > > > Sharding-Sphere was open sourced on Github in 2016. At the very
> > > > > > beginning, Sharding-Sphere is just a JDBC driver for data
> sharding
> > > > > > (name as Sharding-JDBC) at Dangdang internal framework; now it
> offers
> > > > > > data sharding, distributed transaction and database
> orchestration.
> > > > > > Besides JDBC, proxy to implement MySQL database protocol is also
> > > > > > supported at present. Furthermore, our roadmap includes Proxy for
> > > > > > PostgreSQL protocol, Sidecar model, data repica and elastic data
> > > > > > scalability function as well.
> > > > > >
> > > > > > Due to the extension of project, we provide proxy model and
> sidecar
> > > > > > model in addition to JDBC model. Therefore, we rename it to
> > > > > > Sharding-Sphere by
> > > > > > [[
> https://github.com/sharding-sphere/sharding-sphere/issues/788|a
> > > > > > public vote]], which refers to a sharding ecosphere with
> > > > > > Sharding-JDBC, Sharding-Proxy and Sharding Sidecar as its three
> > > > > > sub-projects.
> > > > > >
> > > > > > Sharding-JDBC has won the
> > > > > > [[http://www.oschina.net/project/top_cn_2016|TOP 20 most popular
> > > open
> > > > > > source projects in China 2016]].
> > > > > >
> > > > > > = Rationale =
> > > > > >
> > > > > > Relational database still plays a very important role on current
> > > > > > application system. The maturity of products and surrounding
> > > > > > ecosystem, the friendliness of its data query and developers' and
> > > > > > DBAs' mastery of it, cannot be completely replaced with other
> types
> > > of
> > > > > > database in the near future. However, current relational database
> > > > > > cannot support cloud native very well and it is not friendly to
> 

Re: [VOTE] Ratis-thirdparty 0.1.0rc1

[Justin Mclean]

Hi,

> And on that note: those 72hours elapses today. Any IPMC votes would be 
> greatly appreciated!

Your mentors are IPMC member and can vote on this release, given it basically 
contains nothing I’m not sure why they haven’t.

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

Re: [VOTE] Apache Toree 0.3.0-incubating (RC1)

[Justin Mclean]

Hi,

+1 (binding)

I checked:
- incubating in name (although I notice the pip package doesn’t - is this a 
limitation?)
- signatures and hashes all good
- DISCLAIMER exists
- LICENSE and NOTICE file
- all source files have ASF headers
- No binary files in release
- Can compile from source

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

Re: [VOTE] Heron Release 0.20.0-incubating Candidate 5

[Justin Mclean]

Hi,

> On 9 Nov 2018, at 11:07 am, Fu Maosong  wrote:
> 
> +1 (binding)

Thanks, for voting but Just a reminder that only IPMC votes are binding.

Thanks,
Justin



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

Re: [VOTE] Heron Release 0.20.0-incubating Candidate 5

[Justin Mclean]

Hi,

> This vote has been open for 8 days. If you have some time, please provide
> any feedback to help us improve.

I suggest you contact your mentors (you have 4) and ask them to vote as they 
are IPMC members.

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

Re: November 2018 Incubator report timeline

[Justin Mclean]

Hi,

>Tue November 13 -- Mentor signoff due by end of day

There a few podlings that still don’t have sign off and only a few days to go 
(Tuesday) until that is due, the report will be submitted on next Wednesday. 
Podlings without sign-off will need to report agin next month.

Thanks,
Justin



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

Re: [NEW MENTORS REQUIRED] Apache SensSoft

[Atri Sharma]

I am willing to help.

On Fri, 9 Nov 2018 at 3:36 AM, lewis john mcgibbney 
wrote:

> Hi Folks,
> We are looking for new motivated mentors for the Apache SensSoft
> (Incubating) project [0] look at that kick ass Website :)
> In a nutshell SensSoft is a generalized user behavioral logging platform
> for web pages and thin-client applications.
> The podling was accepted into the Apache Incubator on 2016-07-13 so has
> been maturing and has made one release during that timeframe.
> We have been struggling somewhat with active mentorship which has
> attributed to the podling struggling with the final push through to
> graduation.
> Interestingly the SensSoft community is also going through the process of a
> PODLINGNAMESEARCH meaning that we will no longer be SensSoft but something
> else. This is an excellent time for a mentor or two to come aboard and help
> us drive onwards to TLP status.
> Please let us know at d...@senssoft.apache.org if you are interested,
> Lewis
>
> [0] http://senssoft.apache.org/
>
> --
> http://home.apache.org/~lewismc/
> http://people.apache.org/keys/committer/lewismc
>
-- 
Regards,

Atri
Apache Concerted

[jira] [Updated] (INCUBATOR-225) Missing Link on Incubator Website

[Wei Chen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wei Chen updated INCUBATOR-225:
---
Priority: Minor  (was: Major)

> Missing Link on Incubator Website
> -
>
> Key: INCUBATOR-225
> URL: https://issues.apache.org/jira/browse/INCUBATOR-225
> Project: Incubator
>  Issue Type: Bug
>  Components: site
>Reporter: Wei Chen
>Priority: Minor
>
> On page: http://incubator.apache.org/projects/ 
> On the left-hand side: 
> in **General** 
> [Incubation Guides|http://incubator.apache.org/guides/index.html] 
> in **Status** 
> [Incubator History|http://incubator.apache.org/history] 
> These 2 pages are missing.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Created] (INCUBATOR-225) Missing Link on Incubator Website

[Wei Chen (JIRA)]

Wei Chen created INCUBATOR-225:
--

 Summary: Missing Link on Incubator Website
 Key: INCUBATOR-225
 URL: https://issues.apache.org/jira/browse/INCUBATOR-225
 Project: Incubator
  Issue Type: Bug
  Components: site
Reporter: Wei Chen


On page: http://incubator.apache.org/projects/ 
On the left-hand side: 

in **General** 
[Incubation Guides|http://incubator.apache.org/guides/index.html] 

in **Status** 
[Incubator History|http://incubator.apache.org/history] 

These 2 pages are missing.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Re: [VOTE] Accept the brpc Project into the Apache Incubator.

[Willem Jiang]

+1(binding)

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Nov 9, 2018 at 3:28 AM Dave Fisher  wrote:
>
> Hi -
>
> This is a VOTE to accept the brpc Project into the Apache Incubator.
>
> It will last for at least 72 hours and will pass if at least 3 +1 IPMC Votes 
> and more IPMC Votes are +1 than -1.
>
> [ ] +1, accept the brpc proposal.
> [ ] -1, reject the brpc proposal
>
> Regards,
> Dave
>
> = 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 were adopted and online at late 2014. The framework was 
> rapidly iterated at 2015-2017, and thousands kinds of services and almost all 
> core services adopted it. And in 2017, we opensourced it as "brpc" and hope 
> to get more adoptions and contributions from outside. At the time of 
> opensourcing, there're more than 1 million instances inside Baidu using 
> baidu-rpc (not counting clients).
>
>
> === Rationale ===
>
> brpc has been approved inside baidu, since many high performance core 
> services are using it.
> And since its open source, it has been adopted by several other companies, 
> including Iqiyi, Didi, Sougou, BiliBili etc.
>
>
> === Current Status ===
>
> brpc has been an open source project on GitHub (https://github.com/brpc/brpc 
> ) since 2017.
>
> Currently it has more than 7.3k stars, 1.6k forks, and is one of the most 
> popular repositories in topic of rpc category in GitHub rpc catelogy.
> It has been widely used in Baidu, with 1,000,000+ instances and thousands 
> kinds of services.
> Besides, many other companies have already used it also, such as Iqiyi, Didi, 
> Sougou, BiliBili etc.
>
>
> === Meritocracy ===
>
> brpc was originally created by Ge Jun and Chen zhangyi inside baidu from 2014.
> Since its opensource in 2017, it has already followed meritocracy principles.
> It accepts multiple contributions from other companies.
> And now, the core developers are from several different companies.
>
> We will follow Apache way to encourage more developers to contribute in this 
> project.
> We know that only active and committed developers from a diverse set of 
> backgrounds
> can make brpc a successful project.
>
>
> === Community ===
>
> brpc has been building an active community since its open source. Currently,
> the community includes over 31 contributors.
> The core developers of brpc are listed below.
>
> === Core Developers ===
>
>   * Ge Jun(https://github.com/jamesge  
> jge...@gmail.com )
>   * Chen Zhangyi(https://github.com/chenzhangyi 
>  frozen@gmail.com 
> )
>   * Jiang Rujie(https://github.com/old-bear  
> jrjb...@gmail.com )
>   * Zhu Jiashun(http://github.com/zyearn  
> zhujiashun2...@gmail.com )
>   * Wang Yao(https://github.com/ipconfigme  
> ipconfi...@gmail.com )
>
> === Alignment ===
>
> brpc is useful for building reliable and high-performance applications.
> Since ASF has many famous performance-related and rpc-related projects,
> we believe that ASF is a perfect choice to help brpc project to attract
> more developers and users as well as having more cooperation with existing 
> projects.
>
> === Known Risks ===
>  Orphaned products 
>
> Since our core developers are from different companies and many companies are 
> using it,
> the risk of the project being abandoned is minimal.
> For example, Baidu is extensively using it in their production environment
> and many large corporations including Iqiyi, Didi, Sougou, BiliBili use it in 
> their production applications.
>
>  Inexperience with Open Source 
>
> brpc has been an active open source project for more than one year.
> During that time, the project has attracted 30+ contributors and gained a lot 
> of attention.
> The core developers are all active users and followers of open source.
>
>  Homogenous Developers 
>
> brpc was created inside Baidu, but after brpc was open sourced, it received a 
> lot of bug fixes and enhancements from other developers not working at 

Re: [VOTE] Heron Release 0.20.0-incubating Candidate 5

[Fu Maosong]

+1 (binding)

Neng Lu  于2018年11月8日周四 下午3:43写道：

> Hi All,
>
> This vote has been open for 8 days. If you have some time, please provide
> any feedback to help us improve.
> Thank you very much!
>
> On Wed, Oct 31, 2018 at 10:31 AM Neng Lu  wrote:
>
> > Hi All,
> >
> > This is the 5th release candidate for Apache Heron, version
> > 0.20.0-incubating. Thanks everyone for providing various feedback for the
> > previous release candidates at the @dev mailing list voting process. This
> > release candidate passed the project's dev voting process so we are
> > bringing it to a broader voting process.
> >
> > It is the starting point of Heron and contains heron's main features,
> such
> > as core streaming
> > processing, stateful processing, streamlet API, API server, eco support,
> > etc.
> >
> > The full list of changes and fixes are available:
> >
> >
> https://github.com/apache/incubator-heron/compare/0.17.8...release/v-0.20.0-incubating
> >
> > *** Please download, test and vote on this release. This vote will stay
> > open
> > for at least 72 hours ***
> >
> > Source files:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.0-incubating-candidate-5/
> >
> > SHA-512 checksums:
> >
> >
> 27890ab30fc3e69b627f47d58d178d1a7dffa9dbe4ebbb5a5aa77caaac882fdc2b6f98b3b76210020db0fa3fd86e294cba214f86072e449837e1b7615cd6124a
> > incubator-heron-v-0.20.0-incubating-candidate-5.tar.gz
> >
> > The tag to be voted upon:
> > v0.20.0-incubating-candidate-5 (45043bb6dcef1e8089c0834f17f8be0cc3f451d3)
> >
> >
> https://github.com/apache/incubator-heron/releases/tag/v-0.20.0-incubating-candidate-5
> >
> > Please download the source package, and follow the compiling guide(
> >
> https://apache.github.io/incubator-heron/docs/developers/compiling/compiling/
> )
> > to build and run the Heron locally.
> >
> > --
> > Best Regards,
> > Neng
> >
>
>
> --
> Best Regards,
> Neng
>


-- 
With my best Regards
--
Fu Maosong
Twitter Inc.
Mobile: +001-415-244-7520

Re: [VOTE] Heron Release 0.20.0-incubating Candidate 5

[Neng Lu]

Hi All,

This vote has been open for 8 days. If you have some time, please provide
any feedback to help us improve.
Thank you very much!

On Wed, Oct 31, 2018 at 10:31 AM Neng Lu  wrote:

> Hi All,
>
> This is the 5th release candidate for Apache Heron, version
> 0.20.0-incubating. Thanks everyone for providing various feedback for the
> previous release candidates at the @dev mailing list voting process. This
> release candidate passed the project's dev voting process so we are
> bringing it to a broader voting process.
>
> It is the starting point of Heron and contains heron's main features, such
> as core streaming
> processing, stateful processing, streamlet API, API server, eco support,
> etc.
>
> The full list of changes and fixes are available:
>
> https://github.com/apache/incubator-heron/compare/0.17.8...release/v-0.20.0-incubating
>
> *** Please download, test and vote on this release. This vote will stay
> open
> for at least 72 hours ***
>
> Source files:
>
> https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.0-incubating-candidate-5/
>
> SHA-512 checksums:
>
> 27890ab30fc3e69b627f47d58d178d1a7dffa9dbe4ebbb5a5aa77caaac882fdc2b6f98b3b76210020db0fa3fd86e294cba214f86072e449837e1b7615cd6124a
> incubator-heron-v-0.20.0-incubating-candidate-5.tar.gz
>
> The tag to be voted upon:
> v0.20.0-incubating-candidate-5 (45043bb6dcef1e8089c0834f17f8be0cc3f451d3)
>
> https://github.com/apache/incubator-heron/releases/tag/v-0.20.0-incubating-candidate-5
>
> Please download the source package, and follow the compiling guide(
> https://apache.github.io/incubator-heron/docs/developers/compiling/compiling/)
> to build and run the Heron locally.
>
> --
> Best Regards,
> Neng
>


-- 
Best Regards,
Neng

[VOTE] Apache Toree 0.3.0-incubating (RC1)

[Luciano Resende]

Please vote to approve the release of Apache Toree 0.3.0-incubating (RC1).

The podling dev vote thread:
https://www.mail-archive.com/dev@toree.incubator.apache.org/msg01914.html

And the result:
https://www.mail-archive.com/dev@toree.incubator.apache.org/msg01927.html

Tag: v0.3.0-incubating-rc1 (3ff5df33cc459ea214e542a4798fd9ba6e0a2ef8)

https://github.com/apache/incubator-toree/tree/v0.3.0-incubating-rc1

All distribution packages, including signatures, digests, etc. can be found at:

https://dist.apache.org/repos/dist/dev/incubator/toree/0.3.0-incubating-rc1/

Staging artifacts can be found at:

https://repository.apache.org/content/repositories/orgapachetoree-1014

The vote is open for at least 72 hours and passes if a majority of at
least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache Toree 0.3.0-incubating
[ ] -1 Do not release this package because ...

--
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

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

[NEW MENTORS REQUIRED] Apache SensSoft

[lewis john mcgibbney]

Hi Folks,
We are looking for new motivated mentors for the Apache SensSoft
(Incubating) project [0] look at that kick ass Website :)
In a nutshell SensSoft is a generalized user behavioral logging platform
for web pages and thin-client applications.
The podling was accepted into the Apache Incubator on 2016-07-13 so has
been maturing and has made one release during that timeframe.
We have been struggling somewhat with active mentorship which has
attributed to the podling struggling with the final push through to
graduation.
Interestingly the SensSoft community is also going through the process of a
PODLINGNAMESEARCH meaning that we will no longer be SensSoft but something
else. This is an excellent time for a mentor or two to come aboard and help
us drive onwards to TLP status.
Please let us know at d...@senssoft.apache.org if you are interested,
Lewis

[0] http://senssoft.apache.org/

-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

Re: [Vote] call a vote for IoTDB incubation proposal

[Yang Bo]

+1 non-binding

On Thu, Nov 8, 2018 at 4:25 AM Justin Mclean  wrote:

> +1 (binding)
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-- 
Best Regards,
Yang.

Re: How to review so-called "binary releases"?

[Carlos Santana]

The Jim we are in strongly agreement then :-)

Willem
Yes I think that’s the word “DISCLAIMER”, was the concept and idea I was 
describing. 

I think it depends on the binary (ie npm tgz, jar, docker image, dll, 
executable) and location (website, sftp, maven, npm registry, nuget, etc) on 
where to put this. Up to each community what’s the best was to make user 
downloading aware that this DISCLAIMER exist. 

- Carlos Santana
@csantanapr

> On Nov 7, 2018, at 8:10 PM, Willem Jiang  wrote:
> 
> DISCLAIMER

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

Re: [Vote] call a vote for IoTDB incubation proposal

[Willem Jiang]

+1. (binding)


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, Nov 7, 2018 at 3:47 PM hxd  wrote:
>
> Hi,
> Sorry for the previous mail with bad format.
> I'd like to call a VOTE to accept IoTDB project, a database for managing 
> large amounts of time series data  from IoT sensors in industrial 
> applications, into the Apache Incubator.
> The full proposal is available on the wiki: 
> https://wiki.apache.org/incubator/IoTDBProposal
> and it is also attached below for your convenience.
>
> Please cast your vote:
>
>   [ ] +1, bring IoTDB into Incubator
>   [ ] +0, I don't care either way,
>   [ ] -1, do not bring IoTDB into Incubator, because...
>
> The vote will open at least for 72 hours.
>
> Thanks,
> Xiangdong Huang.
>
> = IoTDB Proposal  =
> v0.1.1
>
>
> == Abstract ==
> IoTDB is a data store for managing large amounts of time series data such as 
> timestamped data from IoT sensors in industrial applications.
>
> == Proposal ==
> IoTDB is a database for managing large amount of time series data with 
> columnar storage, data encoding, pre-computation, and index techniques. It 
> has SQL-like interface to write millions of data points per second per node 
> and is optimized to get query results in few seconds over trillions of data 
> points. It can also be easily integrated with Apache Hadoop MapReduce and 
> Apache Spark for analytics.
>
> == Background ==
>
> A new class of data management system requirements is becoming increasingly 
> important with the rise of the Internet of Things. There are some database 
> systems and technologies aimed at time series data management.  For example, 
> Gorilla and InfluxDB which are mainly built for data centers and monitoring 
> application metrics. Other systems, for example, OpenTSDB and KairosDB, are 
> built on Apache HBase and Apache Cassandra, respectively.
>
> However, many applications for time series data management have more 
> requirements especially in industrial applications as follows:
>
>  * Supporting time series data which has high data frequency. For example, a 
> turbine engine may generate 1000 points per second (i.e., 1000Hz), while each 
> CPU only reports 1 data points per 5 seconds in a data center monitoring 
> application.
>
>  * Supporting scanning data multi-resolutionally. For example, aggregation 
> operation is important for time series data.
>
>  * Supporting special queries for time series, such as pattern matching, time 
> series segmentation, time-frequency transformation and frequency query.
>
>  * Supporting a large number of monitoring targets (i.e. time series). An 
> excavator may report more than 1000 time series, for example, revolving speed 
> of the motor-engine, the speed of the excavator, the accelerated speed, the 
> temperature of the water tank and so on, while a CPU or an application 
> monitor has much fewer time series.
>
>  * Optimization for out-of-order data points. In the industrial sector, it is 
> common that equipment sends data using the UDP protocol rather than the TCP 
> protocol. Sometimes, the network connect is unstable and parts of the data 
> will be buffered for later sending.
>
>  * Supporting long-term storage. Historical data is precious for equipment 
> manufacturers. Therefore, removing or unloading historical data is highly 
> desired for most industrial applications. The database system must not only 
> support fast retrieval of historical data, but also should guarantee that the 
> historical data does not impact the processing speed for “hot” or current 
> data.
>
>  * Supporting online transaction processing (OLTP) as well as complex 
> analytics. It is obvious that supporting analyzing from the data files using 
> Apache Spark/Apache Hadoop MapReduce directly is better than transforming 
> data files to another file format for Big Data analytics.
>
>  * Flexible deployment either on premise or in the cloud.  IoTDB is as simple 
> and can be deployed on a Raspberry Pi handling hundreds of time series. 
> Meanwhile, the system can be also deployed in the cloud so that it supports 
> tens of millions ingestions per second, OLTP queries in milliseconds, and 
> analytics using Apache Spark/Apache Hadoop MapReduce.
>
>  * * (1) If users deploy IoTDB on a device, such as a Raspberry Pi, a wind 
> turbine, or a meteorological station, the deployment of the chosen database 
> is designed to be simple. A device may have hundreds of time series (but less 
> than a thousand time series) and the database needs to handle them.
>  * * (2) When deploying IoTDB in a data center, the computational resources 
> (i.e., the hardware configuration of servers) is not a problem when compared 
> to a Raspberry Pi. In this deployment, IoTDB can use more computation 
> resources, and has the ability to handle more time seires (e.g., millions of 
> time series).
>
> Based on these requirements, we developed IoTDB, a new data store system for 
> managing time series data.
>
> IoTDB started as a 

Re: [VOTE] Accept the brpc Project into the Apache Incubator.

[Kevin A. McGrail]

+1 (Binding) though I vote we call it Apache Burp or Apache Hiccup ;-)

On 11/8/2018 2:43 PM, Matt Sicker wrote:
> +1 (binding)
>
> On Thu, 8 Nov 2018 at 13:30, Julian Hyde  wrote:
>
>> +1 (binding)
>>
>>> On Nov 8, 2018, at 11:29 AM, Dave Fisher  wrote:
>>>
>>> +1 (binding)
>>>
>>> Regards,
>>> Dave
>>>
 On Nov 8, 2018, at 11:25 AM, Dave Fisher  wrote:

 Hi -

 This is a VOTE to accept the brpc Project into the Apache Incubator.

 It will last for at least 72 hours and will pass if at least 3 +1 IPMC
>> Votes and more IPMC Votes are +1 than -1.
 [ ] +1, accept the brpc proposal.
 [ ] -1, reject the brpc proposal

 Regards,
 Dave

 = 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 were adopted and online at late 2014. The
>> framework was rapidly iterated at 2015-2017, and thousands kinds of
>> services and almost all core services adopted it. And in 2017, we
>> opensourced it as "brpc" and hope to get more adoptions and contributions
>> from outside. At the time of opensourcing, there're more than 1 million
>> instances inside Baidu using baidu-rpc (not counting clients).

 === Rationale ===

 brpc has been approved inside baidu, since many high performance core
>> services are using it.
 And since its open source, it has been adopted by several other
>> companies, including Iqiyi, Didi, Sougou, BiliBili etc.

 === Current Status ===

 brpc has been an open source project on GitHub (
>> https://github.com/brpc/brpc ) since 2017.
 Currently it has more than 7.3k stars, 1.6k forks, and is one of the
>> most popular repositories in topic of rpc category in GitHub rpc catelogy.
 It has been widely used in Baidu, with 1,000,000+ instances and
>> thousands kinds of services.
 Besides, many other companies have already used it also, such as Iqiyi,
>> Didi, Sougou, BiliBili etc.

 === Meritocracy ===

 brpc was originally created by Ge Jun and Chen zhangyi inside baidu
>> from 2014.
 Since its opensource in 2017, it has already followed meritocracy
>> principles.
 It accepts multiple contributions from other companies.
 And now, the core developers are from several different companies.

 We will follow Apache way to encourage more developers to contribute in
>> this project.
 We know that only active and committed developers from a diverse set of
>> backgrounds
 can make brpc a successful project.


 === Community ===

 brpc has been building an active community since its open source.
>> Currently,
 the community includes over 31 contributors.
 The core developers of brpc are listed below.

 === Core Developers ===

 * Ge Jun(https://github.com/jamesge 
>> jge...@gmail.com )
 * Chen Zhangyi(https://github.com/chenzhangyi <
>> https://github.com/chenzhangyi> frozen@gmail.com > frozen@gmail.com>)
 * Jiang Rujie(https://github.com/old-bear 
>> jrjb...@gmail.com )
 * Zhu Jiashun(http://github.com/zyearn 
>> zhujiashun2...@gmail.com )
 * Wang Yao(https://github.com/ipconfigme 
>> ipconfi...@gmail.com )
 === Alignment ===

 brpc is useful for building reliable and high-performance applications.
 Since ASF has many famous performance-related and rpc-related projects,
 we believe that ASF is a perfect choice to help brpc project to attract
 more developers and users as well as having more cooperation with
>> existing projects.
 === Known Risks ===
  Orphaned products 

 Since our core developers are from different companies and many
>> companies are using it,
 the risk of the project being abandoned is minimal.
 For example, Baidu is extensively using it in their production
>> environment
 and many large corporations including Iqiyi, Didi, Sougou, BiliBili use
>> it in their production applications.
  Inexperience with Open 

Re: licenses and copyrights of dependencies

[Justin Mclean]

Hi,

> @Justin I understand the need for this to be transitive but what if the 
> artifact has contracting licenses, e.g. as mentioned BSD-c2 vs BSD-c3? I 
> assume it is not our problem to figure this out but just put whatever is in 
> there in our LICENSE file?=

I would probably put both in the LICENSE file, but would need to look at the 
actual code to work out what to do.

Thanks,
Justin

Re: [VOTE] Sharding-Sphere incubation proposal

[Dave Fisher]

+1 (binding)

Sent from my iPhone

> On Nov 5, 2018, at 10:41 PM, Roman Shaposhnik  wrote:
> 
> Hi!
> 
> on behalf of Sharding-Sphere community, I'd like to call
> a VOTE to accept it into the Apache Incubator. The full
> proposal is available on the wiki:
>https://wiki.apache.org/incubator/ShardingSphereProposal
> and it is also attached below for your convenience.
> 
> Please cast your vote:
> 
>  [ ] +1, bring Sharding-Sphere into Incubator
>  [ ] +0, I don't care either way,
>  [ ] -1, do not bring Sharding-Sphere into Incubator, because...
> 
> The vote will open at least for 72 hours.
> 
> Thanks,
> Roman.
> 
> = Abstract =
> Sharding-Sphere is an ecosystem of transparent distributed database
> middleware, focusing on data sharding, distributed transaction and
> database orchestration. It provides maximum compatibility for
> applications through Sharding-JDBC (a driver to implement JDBC) or
> Sharding-Proxy (a proxy to implement database protocol).
> 
> = Proposal =
> With a large number of end users, Sharding-Sphere has a fairly huge
> community in China. It is also widely adopted by many
> [[http://shardingsphere.io/community/en/company/|companies and
> organizations]] as a solution to process their massive amounts of
> data.
> 
> We believe that bringing Sharding-Sphere into Apache Software
> Foundation could advance development of a stronger and more diverse
> open source community.
> 
> Dangdang submits this proposal to donate Sharding-Sphere's source
> codes and all related documentations to Apache Software Foundation.
> The codes are already under Apache License Version 2.0.
> 
>  * Code base: https://github.com/sharding-sphere/sharding-sphere
> 
>  * Web site: http://shardingsphere.io/
> 
>  * Documentations: http://shardingsphere.io/document/current/
> 
>  * Community: http://shardingsphere.io/community/
> 
> = Background =
> 
> Relational database hardly supports such huge amounts of data any more
> which has increased rapidly in recent years, but for reason of
> technique maturity, developers and DBAs still want to use it to
> persist core data.
> 
> Sharding-Sphere was open sourced on Github in 2016. At the very
> beginning, Sharding-Sphere is just a JDBC driver for data sharding
> (name as Sharding-JDBC) at Dangdang internal framework; now it offers
> data sharding, distributed transaction and database orchestration.
> Besides JDBC, proxy to implement MySQL database protocol is also
> supported at present. Furthermore, our roadmap includes Proxy for
> PostgreSQL protocol, Sidecar model, data repica and elastic data
> scalability function as well.
> 
> Due to the extension of project, we provide proxy model and sidecar
> model in addition to JDBC model. Therefore, we rename it to
> Sharding-Sphere by
> [[https://github.com/sharding-sphere/sharding-sphere/issues/788|a
> public vote]], which refers to a sharding ecosphere with
> Sharding-JDBC, Sharding-Proxy and Sharding Sidecar as its three
> sub-projects.
> 
> Sharding-JDBC has won the
> [[http://www.oschina.net/project/top_cn_2016|TOP 20 most popular open
> source projects in China 2016]].
> 
> = Rationale =
> 
> Relational database still plays a very important role on current
> application system. The maturity of products and surrounding
> ecosystem, the friendliness of its data query and developers' and
> DBAs' mastery of it, cannot be completely replaced with other types of
> database in the near future. However, current relational database
> cannot support cloud native very well and it is not friendly to
> distributed system.
> 
> It is the ultimate goal of Sharding-Sphere, which manages the
> databases scattering around the system, to make user use distributed
> databases as simply as using a single one.
> 
> Without extra cost, Sharding-JDBC directly connects database with Java
> application to get the best performance.
> 
> Sharding-Proxy is deployed as a stateless server and supports MySQL
> protocol at present. In the paper
> [[https://db.cs.cmu.edu/papers/2016/pavlo-newsql-sigmodrec2016.pdf|What’s
> Really New with NewSQL?]], three types of NewSQL are introduced, among
> which Sharding-Proxy is a Transparent Sharding Middleware.
> 
> Sharding-Sidecar can be understood as a data panel in Service Mesh.
> The interaction between the application and the database provides a
> mesh layer. The concept of Database Mesh is similar to Service Mesh,
> and it focuses on how to connect data access applications to the
> database. Database Mesh will set up a huge grid system between
> applications and databases. Applications and databases need be placed
> in the grid system. They are all objects managed by the meshing layer.
> 
> = Current Status =
> == Meritocracy ==
> Sharding-Sphere was incubated at Dangdang in 2015 and open sourced on
> GitHub in 2016. In 2017, Jingdong recognized its value and determined
> to sponsor this project. Sharding-Sphere has contributors and users
> from many companies; we have set up the PMC Team and 

Re: [VOTE] Sharding-Sphere incubation proposal

[Gilbert Song]

+1 (non-binding).

- Gilbert

On 2018/11/07 17:44:21, Raja Sundaram Ganesan  wrote: 
> +1 (Non Binding)
> 
> 
> 
> On Wed 7 Nov, 2018, 11:02 vintagewang  
> > +1 (non-binding)
> >
> > XIAORUI Wang
> >
> > zhangli...@apache.org 于2018年11月7日 周三09:30写道：
> >
> > > +1 (non-binding)
> > >
> > > Thanks,
> > > John(Zhang Liang) from Sharding-Sphere
> > >
> > > Bruno Mahé  于2018年11月7日周三 上午1:37写道：
> > >
> > > > +1 (non-binding)
> > > >
> > > >
> > > > Thanks,
> > > >
> > > > Bruno
> > > >
> > > > On 11/5/18 10:41 PM, Roman Shaposhnik wrote:
> > > > > Hi!
> > > > >
> > > > > on behalf of Sharding-Sphere community, I'd like to call
> > > > > a VOTE to accept it into the Apache Incubator. The full
> > > > > proposal is available on the wiki:
> > > > >  https://wiki.apache.org/incubator/ShardingSphereProposal
> > > > > and it is also attached below for your convenience.
> > > > >
> > > > > Please cast your vote:
> > > > >
> > > > >[ ] +1, bring Sharding-Sphere into Incubator
> > > > >[ ] +0, I don't care either way,
> > > > >[ ] -1, do not bring Sharding-Sphere into Incubator, because...
> > > > >
> > > > > The vote will open at least for 72 hours.
> > > > >
> > > > > Thanks,
> > > > > Roman.
> > > > >
> > > > > = Abstract =
> > > > > Sharding-Sphere is an ecosystem of transparent distributed database
> > > > > middleware, focusing on data sharding, distributed transaction and
> > > > > database orchestration. It provides maximum compatibility for
> > > > > applications through Sharding-JDBC (a driver to implement JDBC) or
> > > > > Sharding-Proxy (a proxy to implement database protocol).
> > > > >
> > > > > = Proposal =
> > > > > With a large number of end users, Sharding-Sphere has a fairly huge
> > > > > community in China. It is also widely adopted by many
> > > > > [[http://shardingsphere.io/community/en/company/|companies and
> > > > > organizations]] as a solution to process their massive amounts of
> > > > > data.
> > > > >
> > > > > We believe that bringing Sharding-Sphere into Apache Software
> > > > > Foundation could advance development of a stronger and more diverse
> > > > > open source community.
> > > > >
> > > > > Dangdang submits this proposal to donate Sharding-Sphere's source
> > > > > codes and all related documentations to Apache Software Foundation.
> > > > > The codes are already under Apache License Version 2.0.
> > > > >
> > > > >* Code base: https://github.com/sharding-sphere/sharding-sphere
> > > > >
> > > > >* Web site: http://shardingsphere.io/
> > > > >
> > > > >* Documentations: http://shardingsphere.io/document/current/
> > > > >
> > > > >* Community: http://shardingsphere.io/community/
> > > > >
> > > > > = Background =
> > > > >
> > > > > Relational database hardly supports such huge amounts of data any
> > more
> > > > > which has increased rapidly in recent years, but for reason of
> > > > > technique maturity, developers and DBAs still want to use it to
> > > > > persist core data.
> > > > >
> > > > > Sharding-Sphere was open sourced on Github in 2016. At the very
> > > > > beginning, Sharding-Sphere is just a JDBC driver for data sharding
> > > > > (name as Sharding-JDBC) at Dangdang internal framework; now it offers
> > > > > data sharding, distributed transaction and database orchestration.
> > > > > Besides JDBC, proxy to implement MySQL database protocol is also
> > > > > supported at present. Furthermore, our roadmap includes Proxy for
> > > > > PostgreSQL protocol, Sidecar model, data repica and elastic data
> > > > > scalability function as well.
> > > > >
> > > > > Due to the extension of project, we provide proxy model and sidecar
> > > > > model in addition to JDBC model. Therefore, we rename it to
> > > > > Sharding-Sphere by
> > > > > [[https://github.com/sharding-sphere/sharding-sphere/issues/788|a
> > > > > public vote]], which refers to a sharding ecosphere with
> > > > > Sharding-JDBC, Sharding-Proxy and Sharding Sidecar as its three
> > > > > sub-projects.
> > > > >
> > > > > Sharding-JDBC has won the
> > > > > [[http://www.oschina.net/project/top_cn_2016|TOP 20 most popular
> > open
> > > > > source projects in China 2016]].
> > > > >
> > > > > = Rationale =
> > > > >
> > > > > Relational database still plays a very important role on current
> > > > > application system. The maturity of products and surrounding
> > > > > ecosystem, the friendliness of its data query and developers' and
> > > > > DBAs' mastery of it, cannot be completely replaced with other types
> > of
> > > > > database in the near future. However, current relational database
> > > > > cannot support cloud native very well and it is not friendly to
> > > > > distributed system.
> > > > >
> > > > > It is the ultimate goal of Sharding-Sphere, which manages the
> > > > > databases scattering around the system, to make user use distributed
> > > > > databases as simply as using a single one.
> > > > >
> > > > > Without extra cost, Sharding-JDBC directly connects 

Re: [VOTE] Accept the brpc Project into the Apache Incubator.

[Matt Sicker]

+1 (binding)

On Thu, 8 Nov 2018 at 13:30, Julian Hyde  wrote:

> +1 (binding)
>
> > On Nov 8, 2018, at 11:29 AM, Dave Fisher  wrote:
> >
> > +1 (binding)
> >
> > Regards,
> > Dave
> >
> >> On Nov 8, 2018, at 11:25 AM, Dave Fisher  wrote:
> >>
> >> Hi -
> >>
> >> This is a VOTE to accept the brpc Project into the Apache Incubator.
> >>
> >> It will last for at least 72 hours and will pass if at least 3 +1 IPMC
> Votes and more IPMC Votes are +1 than -1.
> >>
> >> [ ] +1, accept the brpc proposal.
> >> [ ] -1, reject the brpc proposal
> >>
> >> Regards,
> >> Dave
> >>
> >> = 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 were adopted and online at late 2014. The
> framework was rapidly iterated at 2015-2017, and thousands kinds of
> services and almost all core services adopted it. And in 2017, we
> opensourced it as "brpc" and hope to get more adoptions and contributions
> from outside. At the time of opensourcing, there're more than 1 million
> instances inside Baidu using baidu-rpc (not counting clients).
> >>
> >>
> >> === Rationale ===
> >>
> >> brpc has been approved inside baidu, since many high performance core
> services are using it.
> >> And since its open source, it has been adopted by several other
> companies, including Iqiyi, Didi, Sougou, BiliBili etc.
> >>
> >>
> >> === Current Status ===
> >>
> >> brpc has been an open source project on GitHub (
> https://github.com/brpc/brpc ) since 2017.
> >>
> >> Currently it has more than 7.3k stars, 1.6k forks, and is one of the
> most popular repositories in topic of rpc category in GitHub rpc catelogy.
> >> It has been widely used in Baidu, with 1,000,000+ instances and
> thousands kinds of services.
> >> Besides, many other companies have already used it also, such as Iqiyi,
> Didi, Sougou, BiliBili etc.
> >>
> >>
> >> === Meritocracy ===
> >>
> >> brpc was originally created by Ge Jun and Chen zhangyi inside baidu
> from 2014.
> >> Since its opensource in 2017, it has already followed meritocracy
> principles.
> >> It accepts multiple contributions from other companies.
> >> And now, the core developers are from several different companies.
> >>
> >> We will follow Apache way to encourage more developers to contribute in
> this project.
> >> We know that only active and committed developers from a diverse set of
> backgrounds
> >> can make brpc a successful project.
> >>
> >>
> >> === Community ===
> >>
> >> brpc has been building an active community since its open source.
> Currently,
> >> the community includes over 31 contributors.
> >> The core developers of brpc are listed below.
> >>
> >> === Core Developers ===
> >>
> >> * Ge Jun(https://github.com/jamesge 
> jge...@gmail.com )
> >> * Chen Zhangyi(https://github.com/chenzhangyi <
> https://github.com/chenzhangyi> frozen@gmail.com  frozen@gmail.com>)
> >> * Jiang Rujie(https://github.com/old-bear 
> jrjb...@gmail.com )
> >> * Zhu Jiashun(http://github.com/zyearn 
> zhujiashun2...@gmail.com )
> >> * Wang Yao(https://github.com/ipconfigme 
> ipconfi...@gmail.com )
> >>
> >> === Alignment ===
> >>
> >> brpc is useful for building reliable and high-performance applications.
> >> Since ASF has many famous performance-related and rpc-related projects,
> >> we believe that ASF is a perfect choice to help brpc project to attract
> >> more developers and users as well as having more cooperation with
> existing projects.
> >>
> >> === Known Risks ===
> >>  Orphaned products 
> >>
> >> Since our core developers are from different companies and many
> companies are using it,
> >> the risk of the project being abandoned is minimal.
> >> For example, Baidu is extensively using it in their production
> environment
> >> and many large corporations including Iqiyi, Didi, Sougou, BiliBili use
> it in their production applications.
> >>
> >>  Inexperience with Open Source 
> >>
> >> brpc has been an active open source project for more than one year.
> >> During that 

Re: [VOTE] Accept the brpc Project into the Apache Incubator.

[Julian Hyde]

+1 (binding)

> On Nov 8, 2018, at 11:29 AM, Dave Fisher  wrote:
> 
> +1 (binding)
> 
> Regards,
> Dave
> 
>> On Nov 8, 2018, at 11:25 AM, Dave Fisher  wrote:
>> 
>> Hi -
>> 
>> This is a VOTE to accept the brpc Project into the Apache Incubator.
>> 
>> It will last for at least 72 hours and will pass if at least 3 +1 IPMC Votes 
>> and more IPMC Votes are +1 than -1.
>> 
>> [ ] +1, accept the brpc proposal.
>> [ ] -1, reject the brpc proposal
>> 
>> Regards,
>> Dave
>> 
>> = 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 were adopted and online at late 2014. The framework was 
>> rapidly iterated at 2015-2017, and thousands kinds of services and almost 
>> all core services adopted it. And in 2017, we opensourced it as "brpc" and 
>> hope to get more adoptions and contributions from outside. At the time of 
>> opensourcing, there're more than 1 million instances inside Baidu using 
>> baidu-rpc (not counting clients).
>> 
>> 
>> === Rationale ===
>> 
>> brpc has been approved inside baidu, since many high performance core 
>> services are using it.
>> And since its open source, it has been adopted by several other companies, 
>> including Iqiyi, Didi, Sougou, BiliBili etc.
>> 
>> 
>> === Current Status ===
>> 
>> brpc has been an open source project on GitHub (https://github.com/brpc/brpc 
>> ) since 2017.
>> 
>> Currently it has more than 7.3k stars, 1.6k forks, and is one of the most 
>> popular repositories in topic of rpc category in GitHub rpc catelogy.
>> It has been widely used in Baidu, with 1,000,000+ instances and thousands 
>> kinds of services.
>> Besides, many other companies have already used it also, such as Iqiyi, 
>> Didi, Sougou, BiliBili etc.
>> 
>> 
>> === Meritocracy ===
>> 
>> brpc was originally created by Ge Jun and Chen zhangyi inside baidu from 
>> 2014.
>> Since its opensource in 2017, it has already followed meritocracy principles.
>> It accepts multiple contributions from other companies.
>> And now, the core developers are from several different companies.
>> 
>> We will follow Apache way to encourage more developers to contribute in this 
>> project.
>> We know that only active and committed developers from a diverse set of 
>> backgrounds
>> can make brpc a successful project.
>> 
>> 
>> === Community ===
>> 
>> brpc has been building an active community since its open source. Currently,
>> the community includes over 31 contributors.
>> The core developers of brpc are listed below.
>> 
>> === Core Developers ===
>> 
>> * Ge Jun(https://github.com/jamesge  
>> jge...@gmail.com )
>> * Chen Zhangyi(https://github.com/chenzhangyi 
>>  frozen@gmail.com 
>> )
>> * Jiang Rujie(https://github.com/old-bear  
>> jrjb...@gmail.com )
>> * Zhu Jiashun(http://github.com/zyearn  
>> zhujiashun2...@gmail.com )
>> * Wang Yao(https://github.com/ipconfigme  
>> ipconfi...@gmail.com )
>> 
>> === Alignment ===
>> 
>> brpc is useful for building reliable and high-performance applications.
>> Since ASF has many famous performance-related and rpc-related projects,
>> we believe that ASF is a perfect choice to help brpc project to attract
>> more developers and users as well as having more cooperation with existing 
>> projects.
>> 
>> === Known Risks ===
>>  Orphaned products 
>> 
>> Since our core developers are from different companies and many companies 
>> are using it,
>> the risk of the project being abandoned is minimal.
>> For example, Baidu is extensively using it in their production environment
>> and many large corporations including Iqiyi, Didi, Sougou, BiliBili use it 
>> in their production applications.
>> 
>>  Inexperience with Open Source 
>> 
>> brpc has been an active open source project for more than one year.
>> During that time, the project has attracted 30+ contributors and gained a 
>> lot of attention.
>> The core developers are all active users and followers of open source.

Re: [VOTE] Accept the brpc Project into the Apache Incubator.

[Dave Fisher]

+1 (binding)

Regards,
Dave

> On Nov 8, 2018, at 11:25 AM, Dave Fisher  wrote:
> 
> Hi -
> 
> This is a VOTE to accept the brpc Project into the Apache Incubator.
> 
> It will last for at least 72 hours and will pass if at least 3 +1 IPMC Votes 
> and more IPMC Votes are +1 than -1.
> 
> [ ] +1, accept the brpc proposal.
> [ ] -1, reject the brpc proposal
> 
> Regards,
> Dave
> 
> = 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 were adopted and online at late 2014. The framework was 
> rapidly iterated at 2015-2017, and thousands kinds of services and almost all 
> core services adopted it. And in 2017, we opensourced it as "brpc" and hope 
> to get more adoptions and contributions from outside. At the time of 
> opensourcing, there're more than 1 million instances inside Baidu using 
> baidu-rpc (not counting clients).
> 
> 
> === Rationale ===
> 
> brpc has been approved inside baidu, since many high performance core 
> services are using it.
> And since its open source, it has been adopted by several other companies, 
> including Iqiyi, Didi, Sougou, BiliBili etc.
> 
> 
> === Current Status ===
> 
> brpc has been an open source project on GitHub (https://github.com/brpc/brpc 
> ) since 2017.
> 
> Currently it has more than 7.3k stars, 1.6k forks, and is one of the most 
> popular repositories in topic of rpc category in GitHub rpc catelogy.
> It has been widely used in Baidu, with 1,000,000+ instances and thousands 
> kinds of services.
> Besides, many other companies have already used it also, such as Iqiyi, Didi, 
> Sougou, BiliBili etc.
> 
> 
> === Meritocracy ===
> 
> brpc was originally created by Ge Jun and Chen zhangyi inside baidu from 2014.
> Since its opensource in 2017, it has already followed meritocracy principles.
> It accepts multiple contributions from other companies.
> And now, the core developers are from several different companies.
> 
> We will follow Apache way to encourage more developers to contribute in this 
> project.
> We know that only active and committed developers from a diverse set of 
> backgrounds
> can make brpc a successful project.
> 
> 
> === Community ===
> 
> brpc has been building an active community since its open source. Currently,
> the community includes over 31 contributors.
> The core developers of brpc are listed below.
> 
> === Core Developers ===
> 
>  * Ge Jun(https://github.com/jamesge  
> jge...@gmail.com )
>  * Chen Zhangyi(https://github.com/chenzhangyi 
>  frozen@gmail.com 
> )
>  * Jiang Rujie(https://github.com/old-bear  
> jrjb...@gmail.com )
>  * Zhu Jiashun(http://github.com/zyearn  
> zhujiashun2...@gmail.com )
>  * Wang Yao(https://github.com/ipconfigme  
> ipconfi...@gmail.com )
> 
> === Alignment ===
> 
> brpc is useful for building reliable and high-performance applications.
> Since ASF has many famous performance-related and rpc-related projects,
> we believe that ASF is a perfect choice to help brpc project to attract
> more developers and users as well as having more cooperation with existing 
> projects.
> 
> === Known Risks ===
>  Orphaned products 
> 
> Since our core developers are from different companies and many companies are 
> using it,
> the risk of the project being abandoned is minimal.
> For example, Baidu is extensively using it in their production environment
> and many large corporations including Iqiyi, Didi, Sougou, BiliBili use it in 
> their production applications.
> 
>  Inexperience with Open Source 
> 
> brpc has been an active open source project for more than one year.
> During that time, the project has attracted 30+ contributors and gained a lot 
> of attention.
> The core developers are all active users and followers of open source.
> 
>  Homogenous Developers 
> 
> brpc was created inside Baidu, but after brpc was open sourced, it received a 
> lot of bug fixes and enhancements from other developers not working at Baidu.

[VOTE] Accept the brpc Project into the Apache Incubator.

[Dave Fisher]

Hi -

This is a VOTE to accept the brpc Project into the Apache Incubator.

It will last for at least 72 hours and will pass if at least 3 +1 IPMC Votes 
and more IPMC Votes are +1 than -1.

[ ] +1, accept the brpc proposal.
[ ] -1, reject the brpc proposal

Regards,
Dave

= 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 were 
adopted and online at late 2014. The framework was rapidly iterated at 
2015-2017, and thousands kinds of services and almost all core services adopted 
it. And in 2017, we opensourced it as "brpc" and hope to get more adoptions and 
contributions from outside. At the time of opensourcing, there're more than 1 
million instances inside Baidu using baidu-rpc (not counting clients).


=== Rationale ===

brpc has been approved inside baidu, since many high performance core services 
are using it.
And since its open source, it has been adopted by several other companies, 
including Iqiyi, Didi, Sougou, BiliBili etc.


=== Current Status ===

brpc has been an open source project on GitHub (https://github.com/brpc/brpc 
) since 2017.

Currently it has more than 7.3k stars, 1.6k forks, and is one of the most 
popular repositories in topic of rpc category in GitHub rpc catelogy.
It has been widely used in Baidu, with 1,000,000+ instances and thousands kinds 
of services.
Besides, many other companies have already used it also, such as Iqiyi, Didi, 
Sougou, BiliBili etc.


=== Meritocracy ===

brpc was originally created by Ge Jun and Chen zhangyi inside baidu from 2014.
Since its opensource in 2017, it has already followed meritocracy principles.
It accepts multiple contributions from other companies.
And now, the core developers are from several different companies.

We will follow Apache way to encourage more developers to contribute in this 
project.
We know that only active and committed developers from a diverse set of 
backgrounds
can make brpc a successful project.


=== Community ===

brpc has been building an active community since its open source. Currently,
the community includes over 31 contributors.
The core developers of brpc are listed below.

=== Core Developers ===

  * Ge Jun(https://github.com/jamesge  
jge...@gmail.com )
  * Chen Zhangyi(https://github.com/chenzhangyi 
 frozen@gmail.com 
)
  * Jiang Rujie(https://github.com/old-bear  
jrjb...@gmail.com )
  * Zhu Jiashun(http://github.com/zyearn  
zhujiashun2...@gmail.com )
  * Wang Yao(https://github.com/ipconfigme  
ipconfi...@gmail.com )

=== Alignment ===

brpc is useful for building reliable and high-performance applications.
Since ASF has many famous performance-related and rpc-related projects,
we believe that ASF is a perfect choice to help brpc project to attract
more developers and users as well as having more cooperation with existing 
projects.

=== Known Risks ===
 Orphaned products 

Since our core developers are from different companies and many companies are 
using it,
the risk of the project being abandoned is minimal.
For example, Baidu is extensively using it in their production environment
and many large corporations including Iqiyi, Didi, Sougou, BiliBili use it in 
their production applications.

 Inexperience with Open Source 

brpc has been an active open source project for more than one year.
During that time, the project has attracted 30+ contributors and gained a lot 
of attention.
The core developers are all active users and followers of open source.

 Homogenous Developers 

brpc was created inside Baidu, but after brpc was open sourced, it received a 
lot of bug fixes and enhancements from other developers not working at Baidu.
And the core developers now are from different companies now.

=== Reliance on Salaried Developers ===

Baidu invested in brpc as a general rpc framework used in company widely.
The core developers have been dedicated to this project for about four years.
And after its open source, developers around the world have involved in.

[CANCEL][VOTE] Accept burp into the Apache Incubator

[Dave Fisher]

Cancelling due to incorrect subject.

> On Nov 8, 2018, at 11:06 AM, Dave Fisher  wrote:
> 
> Hi -
> 
> This is a VOTE to accept the brpc Project into the Apache Incubator.
> 
> It will last for at least 72 hours and will pass if at least 3 +1 IPMC Votes 
> and more IPMC Votes are +1 than -1.
> 
> [ ] +1, accept the brpc proposal.
> [ ] -1, reject the brpc proposal
> 
> Regards,
> Dave
> 
> = 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 were adopted and online at late 2014. The framework was 
> rapidly iterated at 2015-2017, and thousands kinds of services and almost all 
> core services adopted it. And in 2017, we opensourced it as "brpc" and hope 
> to get more adoptions and contributions from outside. At the time of 
> opensourcing, there're more than 1 million instances inside Baidu using 
> baidu-rpc (not counting clients).
> 
> 
> === Rationale ===
> 
> brpc has been approved inside baidu, since many high performance core 
> services are using it.
> And since its open source, it has been adopted by several other companies, 
> including Iqiyi, Didi, Sougou, BiliBili etc.
> 
> 
> === Current Status ===
> 
> brpc has been an open source project on GitHub (https://github.com/brpc/brpc) 
> since 2017.
> 
> Currently it has more than 7.3k stars, 1.6k forks, and is one of the most 
> popular repositories in topic of rpc category in GitHub rpc catelogy.
> It has been widely used in Baidu, with 1,000,000+ instances and thousands 
> kinds of services.
> Besides, many other companies have already used it also, such as Iqiyi, Didi, 
> Sougou, BiliBili etc.
> 
> 
> === Meritocracy ===
> 
> brpc was originally created by Ge Jun and Chen zhangyi inside baidu from 2014.
> Since its opensource in 2017, it has already followed meritocracy principles.
> It accepts multiple contributions from other companies.
> And now, the core developers are from several different companies.
> 
> We will follow Apache way to encourage more developers to contribute in this 
> project.
> We know that only active and committed developers from a diverse set of 
> backgrounds
> can make brpc a successful project.
> 
> 
> === Community ===
> 
> brpc has been building an active community since its open source. Currently,
> the community includes over 31 contributors.
> The core developers of brpc are listed below.
> 
> === Core Developers ===
> 
>   * Ge Jun(https://github.com/jamesge jge...@gmail.com)
>   * Chen Zhangyi(https://github.com/chenzhangyi frozen@gmail.com)
>   * Jiang Rujie(https://github.com/old-bear jrjb...@gmail.com)
>   * Zhu Jiashun(http://github.com/zyearn zhujiashun2...@gmail.com)
>   * Wang Yao(https://github.com/ipconfigme ipconfi...@gmail.com)
> 
> === Alignment ===
> 
> brpc is useful for building reliable and high-performance applications.
> Since ASF has many famous performance-related and rpc-related projects,
> we believe that ASF is a perfect choice to help brpc project to attract
> more developers and users as well as having more cooperation with existing 
> projects.
> 
> === Known Risks ===
>  Orphaned products 
> 
> Since our core developers are from different companies and many companies are 
> using it,
> the risk of the project being abandoned is minimal.
> For example, Baidu is extensively using it in their production environment
> and many large corporations including Iqiyi, Didi, Sougou, BiliBili use it in 
> their production applications.
> 
>  Inexperience with Open Source 
> 
> brpc has been an active open source project for more than one year.
> During that time, the project has attracted 30+ contributors and gained a lot 
> of attention.
> The core developers are all active users and followers of open source.
> 
>  Homogenous Developers 
> 
> brpc was created inside Baidu, but after brpc was open sourced, it received a 
> lot of bug fixes and enhancements from other developers not working at Baidu.
> And the core developers now are from different companies now.
> 
> === Reliance on Salaried Developers ===
> 
> Baidu invested in brpc as a general rpc framework used in company widely.
> The core developers have been dedicated to this project for about four years.
> And after its open source, developers around the world have 

RE: [VOTE] Accept burp into the Apache Incubator

[Dave Birdsall]

I think autocorrect messed with the subject line of this call-to-vote.

-Original Message-
From: Dave Fisher  
Sent: Thursday, November 8, 2018 11:06 AM
To: general@incubator.apache.org
Subject: [VOTE] Accept burp into the Apache Incubator

External

Hi -

This is a VOTE to accept the brpc Project into the Apache Incubator.

It will last for at least 72 hours and will pass if at least 3 +1 IPMC Votes 
and more IPMC Votes are +1 than -1.

[ ] +1, accept the brpc proposal.
[ ] -1, reject the brpc proposal

Regards,
Dave

= 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 were 
adopted and online at late 2014. The framework was rapidly iterated at 
2015-2017, and thousands kinds of services and almost all core services adopted 
it. And in 2017, we opensourced it as "brpc" and hope to get more adoptions and 
contributions from outside. At the time of opensourcing, there're more than 1 
million instances inside Baidu using baidu-rpc (not counting clients).


=== Rationale ===

brpc has been approved inside baidu, since many high performance core services 
are using it.
And since its open source, it has been adopted by several other companies, 
including Iqiyi, Didi, Sougou, BiliBili etc.


=== Current Status ===

brpc has been an open source project on GitHub (https://github.com/brpc/brpc) 
since 2017.

Currently it has more than 7.3k stars, 1.6k forks, and is one of the most 
popular repositories in topic of rpc category in GitHub rpc catelogy.
It has been widely used in Baidu, with 1,000,000+ instances and thousands kinds 
of services.
Besides, many other companies have already used it also, such as Iqiyi, Didi, 
Sougou, BiliBili etc.


=== Meritocracy ===

brpc was originally created by Ge Jun and Chen zhangyi inside baidu from 2014.
Since its opensource in 2017, it has already followed meritocracy principles.
It accepts multiple contributions from other companies.
And now, the core developers are from several different companies.

We will follow Apache way to encourage more developers to contribute in this 
project.
We know that only active and committed developers from a diverse set of 
backgrounds can make brpc a successful project.


=== Community ===

brpc has been building an active community since its open source. Currently, 
the community includes over 31 contributors.
The core developers of brpc are listed below.

=== Core Developers ===

   * Ge Jun(https://github.com/jamesge jge...@gmail.com)
   * Chen Zhangyi(https://github.com/chenzhangyi frozen@gmail.com)
   * Jiang Rujie(https://github.com/old-bear jrjb...@gmail.com)
   * Zhu Jiashun(http://github.com/zyearn zhujiashun2...@gmail.com)
   * Wang Yao(https://github.com/ipconfigme ipconfi...@gmail.com)

=== Alignment ===

brpc is useful for building reliable and high-performance applications.
Since ASF has many famous performance-related and rpc-related projects, we 
believe that ASF is a perfect choice to help brpc project to attract more 
developers and users as well as having more cooperation with existing projects.

=== Known Risks ===
 Orphaned products 

Since our core developers are from different companies and many companies are 
using it, the risk of the project being abandoned is minimal.
For example, Baidu is extensively using it in their production environment and 
many large corporations including Iqiyi, Didi, Sougou, BiliBili use it in their 
production applications.

 Inexperience with Open Source 

brpc has been an active open source project for more than one year.
During that time, the project has attracted 30+ contributors and gained a lot 
of attention.
The core developers are all active users and followers of open source.

 Homogenous Developers 

brpc was created inside Baidu, but after brpc was open sourced, it received a 
lot of bug fixes and enhancements from other developers not working at Baidu.
And the core developers now are from different companies now.

=== Reliance on Salaried Developers ===

Baidu invested in brpc as a general rpc framework used in company widely.
The core developers have been dedicated to this project for about four years.
And after its open source, developers around the world have involved in.
Besides, we want more developers and researchers to contribute to the 

Re: [VOTE] Accept burp into the Apache Incubator

[Dave Fisher]

Darn acid reflux!

Thanks Julian

> On Nov 8, 2018, at 11:17 AM, Julian Hyde  wrote:
> 
> Dave,
> 
> You’ll want to cancel this vote. The subject line is an unfortunate victim of 
> auto-correct.
> 
> Julian
> 
> 
>> On Nov 8, 2018, at 11:06 AM, Dave Fisher  wrote:
>> 
>> Hi -
>> 
>> This is a VOTE to accept the brpc Project into the Apache Incubator.
>> 
>> It will last for at least 72 hours and will pass if at least 3 +1 IPMC Votes 
>> and more IPMC Votes are +1 than -1.
>> 
>> [ ] +1, accept the brpc proposal.
>> [ ] -1, reject the brpc proposal
>> 
>> Regards,
>> Dave
>> 
>> = 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 were adopted and online at late 2014. The framework was 
>> rapidly iterated at 2015-2017, and thousands kinds of services and almost 
>> all core services adopted it. And in 2017, we opensourced it as "brpc" and 
>> hope to get more adoptions and contributions from outside. At the time of 
>> opensourcing, there're more than 1 million instances inside Baidu using 
>> baidu-rpc (not counting clients).
>> 
>> 
>> === Rationale ===
>> 
>> brpc has been approved inside baidu, since many high performance core 
>> services are using it.
>> And since its open source, it has been adopted by several other companies, 
>> including Iqiyi, Didi, Sougou, BiliBili etc.
>> 
>> 
>> === Current Status ===
>> 
>> brpc has been an open source project on GitHub 
>> (https://github.com/brpc/brpc) since 2017.
>> 
>> Currently it has more than 7.3k stars, 1.6k forks, and is one of the most 
>> popular repositories in topic of rpc category in GitHub rpc catelogy.
>> It has been widely used in Baidu, with 1,000,000+ instances and thousands 
>> kinds of services.
>> Besides, many other companies have already used it also, such as Iqiyi, 
>> Didi, Sougou, BiliBili etc.
>> 
>> 
>> === Meritocracy ===
>> 
>> brpc was originally created by Ge Jun and Chen zhangyi inside baidu from 
>> 2014.
>> Since its opensource in 2017, it has already followed meritocracy principles.
>> It accepts multiple contributions from other companies.
>> And now, the core developers are from several different companies.
>> 
>> We will follow Apache way to encourage more developers to contribute in this 
>> project.
>> We know that only active and committed developers from a diverse set of 
>> backgrounds
>> can make brpc a successful project.
>> 
>> 
>> === Community ===
>> 
>> brpc has been building an active community since its open source. Currently,
>> the community includes over 31 contributors.
>> The core developers of brpc are listed below.
>> 
>> === Core Developers ===
>> 
>>  * Ge Jun(https://github.com/jamesge jge...@gmail.com)
>>  * Chen Zhangyi(https://github.com/chenzhangyi frozen@gmail.com)
>>  * Jiang Rujie(https://github.com/old-bear jrjb...@gmail.com)
>>  * Zhu Jiashun(http://github.com/zyearn zhujiashun2...@gmail.com)
>>  * Wang Yao(https://github.com/ipconfigme ipconfi...@gmail.com)
>> 
>> === Alignment ===
>> 
>> brpc is useful for building reliable and high-performance applications.
>> Since ASF has many famous performance-related and rpc-related projects,
>> we believe that ASF is a perfect choice to help brpc project to attract
>> more developers and users as well as having more cooperation with existing 
>> projects.
>> 
>> === Known Risks ===
>>  Orphaned products 
>> 
>> Since our core developers are from different companies and many companies 
>> are using it,
>> the risk of the project being abandoned is minimal.
>> For example, Baidu is extensively using it in their production environment
>> and many large corporations including Iqiyi, Didi, Sougou, BiliBili use it 
>> in their production applications.
>> 
>>  Inexperience with Open Source 
>> 
>> brpc has been an active open source project for more than one year.
>> During that time, the project has attracted 30+ contributors and gained a 
>> lot of attention.
>> The core developers are all active users and followers of open source.
>> 
>>  Homogenous Developers 
>> 
>> brpc was created inside Baidu, but after brpc was open sourced, it received 
>> a lot of bug fixes and enhancements from other developers not working at 
>> Baidu.
>> And the core developers now 

Re: [VOTE] Accept burp into the Apache Incubator

[Julian Hyde]

Dave,

You’ll want to cancel this vote. The subject line is an unfortunate victim of 
auto-correct.

Julian


> On Nov 8, 2018, at 11:06 AM, Dave Fisher  wrote:
> 
> Hi -
> 
> This is a VOTE to accept the brpc Project into the Apache Incubator.
> 
> It will last for at least 72 hours and will pass if at least 3 +1 IPMC Votes 
> and more IPMC Votes are +1 than -1.
> 
> [ ] +1, accept the brpc proposal.
> [ ] -1, reject the brpc proposal
> 
> Regards,
> Dave
> 
> = 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 were adopted and online at late 2014. The framework was 
> rapidly iterated at 2015-2017, and thousands kinds of services and almost all 
> core services adopted it. And in 2017, we opensourced it as "brpc" and hope 
> to get more adoptions and contributions from outside. At the time of 
> opensourcing, there're more than 1 million instances inside Baidu using 
> baidu-rpc (not counting clients).
> 
> 
> === Rationale ===
> 
> brpc has been approved inside baidu, since many high performance core 
> services are using it.
> And since its open source, it has been adopted by several other companies, 
> including Iqiyi, Didi, Sougou, BiliBili etc.
> 
> 
> === Current Status ===
> 
> brpc has been an open source project on GitHub (https://github.com/brpc/brpc) 
> since 2017.
> 
> Currently it has more than 7.3k stars, 1.6k forks, and is one of the most 
> popular repositories in topic of rpc category in GitHub rpc catelogy.
> It has been widely used in Baidu, with 1,000,000+ instances and thousands 
> kinds of services.
> Besides, many other companies have already used it also, such as Iqiyi, Didi, 
> Sougou, BiliBili etc.
> 
> 
> === Meritocracy ===
> 
> brpc was originally created by Ge Jun and Chen zhangyi inside baidu from 2014.
> Since its opensource in 2017, it has already followed meritocracy principles.
> It accepts multiple contributions from other companies.
> And now, the core developers are from several different companies.
> 
> We will follow Apache way to encourage more developers to contribute in this 
> project.
> We know that only active and committed developers from a diverse set of 
> backgrounds
> can make brpc a successful project.
> 
> 
> === Community ===
> 
> brpc has been building an active community since its open source. Currently,
> the community includes over 31 contributors.
> The core developers of brpc are listed below.
> 
> === Core Developers ===
> 
>   * Ge Jun(https://github.com/jamesge jge...@gmail.com)
>   * Chen Zhangyi(https://github.com/chenzhangyi frozen@gmail.com)
>   * Jiang Rujie(https://github.com/old-bear jrjb...@gmail.com)
>   * Zhu Jiashun(http://github.com/zyearn zhujiashun2...@gmail.com)
>   * Wang Yao(https://github.com/ipconfigme ipconfi...@gmail.com)
> 
> === Alignment ===
> 
> brpc is useful for building reliable and high-performance applications.
> Since ASF has many famous performance-related and rpc-related projects,
> we believe that ASF is a perfect choice to help brpc project to attract
> more developers and users as well as having more cooperation with existing 
> projects.
> 
> === Known Risks ===
>  Orphaned products 
> 
> Since our core developers are from different companies and many companies are 
> using it,
> the risk of the project being abandoned is minimal.
> For example, Baidu is extensively using it in their production environment
> and many large corporations including Iqiyi, Didi, Sougou, BiliBili use it in 
> their production applications.
> 
>  Inexperience with Open Source 
> 
> brpc has been an active open source project for more than one year.
> During that time, the project has attracted 30+ contributors and gained a lot 
> of attention.
> The core developers are all active users and followers of open source.
> 
>  Homogenous Developers 
> 
> brpc was created inside Baidu, but after brpc was open sourced, it received a 
> lot of bug fixes and enhancements from other developers not working at Baidu.
> And the core developers now are from different companies now.
> 
> === Reliance on Salaried Developers ===
> 
> Baidu invested in brpc as a general rpc framework used in company widely.
> The core developers have been dedicated to this project for about four 

Re: [VOTE] Accept burp into the Apache Incubator

[Dave Fisher]

+1 (binding)

> On Nov 8, 2018, at 11:06 AM, Dave Fisher  wrote:
> 
> Hi -
> 
> This is a VOTE to accept the brpc Project into the Apache Incubator.
> 
> It will last for at least 72 hours and will pass if at least 3 +1 IPMC Votes 
> and more IPMC Votes are +1 than -1.
> 
> [ ] +1, accept the brpc proposal.
> [ ] -1, reject the brpc proposal
> 
> Regards,
> Dave
> 
> = 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 were adopted and online at late 2014. The framework was 
> rapidly iterated at 2015-2017, and thousands kinds of services and almost all 
> core services adopted it. And in 2017, we opensourced it as "brpc" and hope 
> to get more adoptions and contributions from outside. At the time of 
> opensourcing, there're more than 1 million instances inside Baidu using 
> baidu-rpc (not counting clients).
> 
> 
> === Rationale ===
> 
> brpc has been approved inside baidu, since many high performance core 
> services are using it.
> And since its open source, it has been adopted by several other companies, 
> including Iqiyi, Didi, Sougou, BiliBili etc.
> 
> 
> === Current Status ===
> 
> brpc has been an open source project on GitHub (https://github.com/brpc/brpc) 
> since 2017.
> 
> Currently it has more than 7.3k stars, 1.6k forks, and is one of the most 
> popular repositories in topic of rpc category in GitHub rpc catelogy.
> It has been widely used in Baidu, with 1,000,000+ instances and thousands 
> kinds of services.
> Besides, many other companies have already used it also, such as Iqiyi, Didi, 
> Sougou, BiliBili etc.
> 
> 
> === Meritocracy ===
> 
> brpc was originally created by Ge Jun and Chen zhangyi inside baidu from 2014.
> Since its opensource in 2017, it has already followed meritocracy principles.
> It accepts multiple contributions from other companies.
> And now, the core developers are from several different companies.
> 
> We will follow Apache way to encourage more developers to contribute in this 
> project.
> We know that only active and committed developers from a diverse set of 
> backgrounds
> can make brpc a successful project.
> 
> 
> === Community ===
> 
> brpc has been building an active community since its open source. Currently,
> the community includes over 31 contributors.
> The core developers of brpc are listed below.
> 
> === Core Developers ===
> 
>   * Ge Jun(https://github.com/jamesge jge...@gmail.com)
>   * Chen Zhangyi(https://github.com/chenzhangyi frozen@gmail.com)
>   * Jiang Rujie(https://github.com/old-bear jrjb...@gmail.com)
>   * Zhu Jiashun(http://github.com/zyearn zhujiashun2...@gmail.com)
>   * Wang Yao(https://github.com/ipconfigme ipconfi...@gmail.com)
> 
> === Alignment ===
> 
> brpc is useful for building reliable and high-performance applications.
> Since ASF has many famous performance-related and rpc-related projects,
> we believe that ASF is a perfect choice to help brpc project to attract
> more developers and users as well as having more cooperation with existing 
> projects.
> 
> === Known Risks ===
>  Orphaned products 
> 
> Since our core developers are from different companies and many companies are 
> using it,
> the risk of the project being abandoned is minimal.
> For example, Baidu is extensively using it in their production environment
> and many large corporations including Iqiyi, Didi, Sougou, BiliBili use it in 
> their production applications.
> 
>  Inexperience with Open Source 
> 
> brpc has been an active open source project for more than one year.
> During that time, the project has attracted 30+ contributors and gained a lot 
> of attention.
> The core developers are all active users and followers of open source.
> 
>  Homogenous Developers 
> 
> brpc was created inside Baidu, but after brpc was open sourced, it received a 
> lot of bug fixes and enhancements from other developers not working at Baidu.
> And the core developers now are from different companies now.
> 
> === Reliance on Salaried Developers ===
> 
> Baidu invested in brpc as a general rpc framework used in company widely.
> The core developers have been dedicated to this project for about four years.
> And after its open source, developers around the world have involved in.
> Besides, we 

[VOTE] Accept burp into the Apache Incubator

[Dave Fisher]

Hi -

This is a VOTE to accept the brpc Project into the Apache Incubator.

It will last for at least 72 hours and will pass if at least 3 +1 IPMC Votes 
and more IPMC Votes are +1 than -1.

[ ] +1, accept the brpc proposal.
[ ] -1, reject the brpc proposal

Regards,
Dave

= 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 were 
adopted and online at late 2014. The framework was rapidly iterated at 
2015-2017, and thousands kinds of services and almost all core services adopted 
it. And in 2017, we opensourced it as "brpc" and hope to get more adoptions and 
contributions from outside. At the time of opensourcing, there're more than 1 
million instances inside Baidu using baidu-rpc (not counting clients).


=== Rationale ===

brpc has been approved inside baidu, since many high performance core services 
are using it.
And since its open source, it has been adopted by several other companies, 
including Iqiyi, Didi, Sougou, BiliBili etc.


=== Current Status ===

brpc has been an open source project on GitHub (https://github.com/brpc/brpc) 
since 2017.

Currently it has more than 7.3k stars, 1.6k forks, and is one of the most 
popular repositories in topic of rpc category in GitHub rpc catelogy.
It has been widely used in Baidu, with 1,000,000+ instances and thousands kinds 
of services.
Besides, many other companies have already used it also, such as Iqiyi, Didi, 
Sougou, BiliBili etc.


=== Meritocracy ===

brpc was originally created by Ge Jun and Chen zhangyi inside baidu from 2014.
Since its opensource in 2017, it has already followed meritocracy principles.
It accepts multiple contributions from other companies.
And now, the core developers are from several different companies.

We will follow Apache way to encourage more developers to contribute in this 
project.
We know that only active and committed developers from a diverse set of 
backgrounds
can make brpc a successful project.


=== Community ===

brpc has been building an active community since its open source. Currently,
the community includes over 31 contributors.
The core developers of brpc are listed below.

=== Core Developers ===

   * Ge Jun(https://github.com/jamesge jge...@gmail.com)
   * Chen Zhangyi(https://github.com/chenzhangyi frozen@gmail.com)
   * Jiang Rujie(https://github.com/old-bear jrjb...@gmail.com)
   * Zhu Jiashun(http://github.com/zyearn zhujiashun2...@gmail.com)
   * Wang Yao(https://github.com/ipconfigme ipconfi...@gmail.com)

=== Alignment ===

brpc is useful for building reliable and high-performance applications.
Since ASF has many famous performance-related and rpc-related projects,
we believe that ASF is a perfect choice to help brpc project to attract
more developers and users as well as having more cooperation with existing 
projects.

=== Known Risks ===
 Orphaned products 

Since our core developers are from different companies and many companies are 
using it,
the risk of the project being abandoned is minimal.
For example, Baidu is extensively using it in their production environment
and many large corporations including Iqiyi, Didi, Sougou, BiliBili use it in 
their production applications.

 Inexperience with Open Source 

brpc has been an active open source project for more than one year.
During that time, the project has attracted 30+ contributors and gained a lot 
of attention.
The core developers are all active users and followers of open source.

 Homogenous Developers 

brpc was created inside Baidu, but after brpc was open sourced, it received a 
lot of bug fixes and enhancements from other developers not working at Baidu.
And the core developers now are from different companies now.

=== Reliance on Salaried Developers ===

Baidu invested in brpc as a general rpc framework used in company widely.
The core developers have been dedicated to this project for about four years.
And after its open source, developers around the world have involved in.
Besides, we want more developers and researchers to contribute to the project.

=== Relationships with Other Apache Products ===


=== A Excessive Fascination with the Apache Brand ===

The mission of brpc is to help developers build reliable and high-performance 
services quickly and easily.
It has been widely used in production 

Re: [DISCUSS] bprc proposal

[Dave Fisher]

Sent from my iPhone

> On Nov 7, 2018, at 11:10 PM, Justin Mclean  wrote:
> 
> Hi,
> 
>> brpc also includes third party code in the source tree.
>> 
>> * https://github.com/brpc/brpc/tree/master/src/butil/third_party (BSD, MIT, 
>> MPL, and Public Domain)
> 
> Being category B the MPL code may be an issue as it probably can’t be 
> included in a source release. [1]

True and that will be part of Incubation to replace the prtime module.

> 
> Thanks,
> Justin
> 
> 1. 
> https://www.apache.org/legal/resolved.html#what-can-we-maybe-include-in-an-asf-project-category-b
> -
> 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: Voting in new IPMC members

[Dmitriy Pavlov]

Hi,

I also think any negative votes -1 are veto for committer and PMC.
Assigning roles in a community is a very sensitive subject so allowing veto
seems natural for me, but playing democracy is dangerous. We still have for
example -0.9 vote that means not a veto but disagreement.

Sincerely,
Dmitry Pavlov

ср, 7 нояб. 2018 г., 12:31 Bertrand Delacretaz :

> On Tue, Nov 6, 2018 at 12:34 PM  wrote:
> > ...For instance [1] which states:
> > "For committership, that is typical. Most PMCs allow a veto for adding
> new members to the PMC.” ...
>
> Interesting, I missed that indeed, I'll start a discussion on our
> members@ list to see what people think.
>
> Thanks for being persistent in arguing ;-)
>
> -Bertrand
>
> > 1.
> https://lists.apache.org/thread.html/406150947529308214f1ab80b42ed670a71df0537c1a860c1da2f82f@1380817899@%3Cgeneral.incubator.apache.org%3E
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: licenses and copyrights of dependencies

[Jonas Pfefferle]

@Alex @Julian ok, I understand the convenience argument.
@Vincent thanks for the input, the licenses in an extra folder is certainly 
an option to consider.


@Justin I understand the need for this to be transitive but what if the 
artifact has contracting licenses, e.g. as mentioned BSD-c2 vs BSD-c3? I 
assume it is not our problem to figure this out but just put whatever is in 
there in our LICENSE file?


Thanks,
Jonas

 On Wed, 7 Nov 2018 20:51:44 +
 "Vincent S Hou"  wrote:
I used to use and also see some other projects use the following 
structure to maintain the third-party license:
Create a folder licenses under root to hold the licenses of the 
dependencies, like lib1.txt with the content of lib1 license, and 
lib2.txt with the license content of lib2.


In your LICENSE file under root, you can use statement like "This 
project/module has a binary dependency on lib1, with its license 
available in licenses/lib1.txt...". As long as you have correct 
description about the relationship with the third-party library. It 
should be fine.


Again, for source code release, it is OK without saying the 
relationship and pointing to the licenses, because users only grab 
your source code with the correct apache license 2.0. You do not ship 
the libraries you depend on in your artifacts, but you can tell the 
users they can download them from somewhere to run your project. 
After they download it, it is their responsibility to get the correct 
dependencies, build and run your project. To me, no matter what they 
do, how they use and build, are technically out of your scope, 
because it is not under the brand of apache. Even if they run into 
legal issues, it will be their problems. 

But for binary release, you need to say the artifact you ship 
depends on these these libraries with the licenses, since the 
artifact is built based on them, and is made available under the 
brand of apache.


This is actually my understanding about shipping the code and 
binaries.


Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, 
IBM Cloud


Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, 
United States


-Julian Hyde  wrote: -
To: general@incubator.apache.org
From: Julian Hyde 
Date: 11/07/2018 12:43PM
Subject: Re: licenses and copyrights of dependencies

What Alex is saying makes sense. Whether you like it or not, you are 
creating a derived work (or something - I am not a lawyer), and that 
needs its own L



On Nov 7, 2018, at 9:03 AM, Alex Harui  
wrote:


IIRC, we use the food allergy analogy for these situations.  AIUI, 
the goal is for the top-level LICENSE to make it convenient for 
someone to see what the ingredients are, because some folks are 
"allergic" to certain licenses.  I think you can still use "pointers" 
instead of copying full texts of licenses, but having people open jar 
files to read the licenses seems to defeat the "convenience" of 
reading the ingredients.  If your packaging can extract a LICENSE 
from each jar you could point to those files.


My 2 cents,
-Alex

On 11/7/18, 8:07 AM, "Jonas Pfefferle" > wrote:


   Hi Vincent,


   At least right now we have the source code part covered since we 
do not ship 
   any third party code/jars etc. with it. However, as you pointed 
it is a 
   concern for the binary release. We just want this to be easy to 
manage. At 
   the moment we have 80+ jars that we ship as dependencies in the 
binary 
   release. As pointed out before all of them have the license at 
least 
   mentioned in the pom or have a license file in META-INF. Best 
case scenario 
   we could just list all jars in the LICENSE file and refer to 
their license 
   in the jar instead of copying everything. This makes it much 
easier to 
   add/remove dependencies or change versions...

   Does this make sense?

   Thanks,
   Jonas

 On Wed, 7 Nov 2018 15:56:45 +
 "Vincent S Hou"  wrote:

Hi Jonas,

I totally understand your situation right now, because I have just 
gone through the release process for my project Apache OpenWhisk as 
well.


Regarding whether you should add the copyright, to me, it depends on 
the source code release or the binary release.
If you only care about the source code release, you can only focus 
on the "SOURCE CODE". For example, if one or some of your SOURCE 
CODE 
come from another library with a certain copyright, you should add 
it 
into your LICENSE file. If your code depends on jar or any other 
packages shipped by other parties, you do not need to add their 
copyright into your LICENSE, because your source code release do not 
and should not include any jar or packages. You can document 
somewhere that these jars or packages are dependencies to run your 
code.


If you come to binary release, and all the dependencies play a role 
in order to compile your source 

Re: [DISCUSS] bprc proposal

[Justin Mclean]

Hi,

> brpc also includes third party code in the source tree.
> 
> * https://github.com/brpc/brpc/tree/master/src/butil/third_party (BSD, MIT, 
> MPL, and Public Domain)

Being category B the MPL code may be an issue as it probably can’t be included 
in a source release. [1]

Thanks,
Justin

1. 
https://www.apache.org/legal/resolved.html#what-can-we-maybe-include-in-an-asf-project-category-b
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Ratis-thirdparty 0.1.0rc1

[Josh Elser]

Looks like I forgot to include duration in my initial message. Of 
course, this will run for at least the customary 72hours.


And on that note: those 72hours elapses today. Any IPMC votes would be 
greatly appreciated!


- Josh

On 11/5/18 2:09 PM, Josh Elser wrote:

IPMC,

Please vote on the following release candidate to become Apache Ratis
Thirdparty 0.1.0.

You may find the PPMC VOTE thread at 
https://lists.apache.org/thread.html/000d9c6f69b6ddcda5391134df8666c7df83193dd01b97218579069c@%3Cdev.ratis.apache.org%3E, 
with the RESULT at 
https://lists.apache.org/thread.html/d287f08e6535e1bfa3876ec8921d85aa7a269a65cda3fd6308c5008b@%3Cdev.ratis.apache.org%3E 



I'm including my IPMC-binding vote. +1

---

The Apache Ratis Thirdparty project is a collection of all thirdparty
dependencies that Apache Ratis uses, repackaged for optimal use by
Ratis. As such, there is very little net-new source code in this project.

The source release is present at
https://dist.apache.org/repos/dist/dev/incubator/ratis/thirdparty/0.1.0-rc1/ 



SHA512 checksum is on the source tarball: 2B11B643 836E367E C47D0F64 
7750E1AB DE2C3FDE ECF2C825 5F8292FA D4CF2DB4 04BEB4B6

  12173754 4C6ACEEE B8534964 C6A4B690 EA9656E2 CAFDB317 FAAB46BA

This source release was created from the Git commit SHA1:
896f7b3453e155df96b8ef62b85aa0b92c37d886. For your convenience, there
is also a GPG-signed tag with the name "ratis-thirdparty-0.1.0rc1" that
also points at this commit.

This source release was signed with my key: 4677D66C. This is present
in the KEYS file (dist/dev and dist/release).

The corresponding "binaries" for this release are staged at
https://repository.apache.org/content/repositories/orgapacheratis-1008/ and
will be promoted pending successful PPMC and IPMC votes. You can
update your local ~/.m2/settings.xml to add this as a repository to
test the build of ratis.git if you choose (appears to work fine for me).

This vote will be open for at least 72hours (until 2018/11/08 19:00:00
GMT).

- Josh


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

Re: UNICEF Open Source project- Apache Foundation

[Kevin A. McGrail]

Hi Ariam, I got your voicemail again  Feel free to ping me back at
703.798.0171 and we can coordinate a face to face meeting.  Regards,
KAM
--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Wed, Oct 31, 2018 at 12:57 PM Kevin A. McGrail 
wrote:

> Thanks Ariam, got your v/m.  Feel free to call me back at 703 798 0171.
> --
> Kevin A. McGrail
> VP Fundraising, Apache Software Foundation
> Chair Emeritus Apache SpamAssassin Project
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
>
> On Tue, Oct 30, 2018 at 11:44 AM Ariam Mogos  wrote:
>
>> Sure, sounds good Kevin. You can reach me at 917.974.5997.
>>
>>
>>
>> *From: *"Kevin A. McGrail" 
>> *Date: *Monday, October 29, 2018 at 6:27 PM
>> *To: *"da...@davebanesaccess.org" 
>> *Cc: *Ariam Mogos , "general@incubator.apache.org" <
>> general@incubator.apache.org>, Aditi Poddar , "
>> e...@ecs.soton.ac.uk" 
>> *Subject: *Re: UNICEF Open Source project- Apache Foundation
>>
>>
>>
>> Thanks David for the introduction.  Ariam, I am located in Fairfax so a
>> meeting in DC is more than possible.
>>
>>
>>
>> Can I give you a call to coordinate?  If so, what's a good number to
>> reach you?
>>
>> --
>>
>> Kevin A. McGrail
>>
>> VP Fundraising, Apache Software Foundation
>>
>> Chair Emeritus Apache SpamAssassin Project
>>
>> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>>
>>
>>
>>
>>
>> On Mon, Oct 29, 2018 at 4:57 PM  wrote:
>>
>> Just to quickly introduce EA and myself – we work together in a not for
>> profit at globalsymbols.com
>>
>>
>>
>> We are very much committed to both open licence and working in the open,
>> and have a special interest in seeking to ensure that AAC reaches those
>> communities that have been most under served in this field
>>
>>
>>
>> One of our first projects was in the Middle East where we collaborated to
>> develop Tawasol, the Arabic open symbol set, designed to reflect both
>> language and culture within the Middle East and especially the gulf. To do
>> that we created a system that democratised symbol design, allowing a range
>> of stakeholder to determine the design and selection of symbols to
>> represent concepts.
>>
>>
>>
>> Very much hope to continue discussions together about collaboration
>> around the paper Ariam has distributed
>>
>>
>>
>> Best regards
>>
>>
>>
>> David
>>
>>
>>
>> *From:* Kevin A. McGrail 
>> *Sent:* 29 October 2018 20:49
>> *To:* Ariam Mogos ; general@incubator.apache.org
>> *Cc:* Aditi Poddar ; da...@davebanesaccess.org; EA
>> Draffan 
>> *Subject:* Re: UNICEF Open Source project- Apache Foundation
>>
>>
>>
>> Thanks Ariam,
>>
>> I have a child with Autism so this is very interesting to me and I also
>> helped found the largest support group in the Washington DC area.  I have
>> done grants for curriculum to teach children with autism to swim with
>> Autism Speaks and I can talk intelligently about AT/PECS.  We also just had
>> our keynote from Cliff Schmidt at Amplio which has some crossover.  Anyway,
>> enough about me, I'd like to setup a call, nothing long and talk about our
>> incubator and how we work/what we do.
>>
>> Regards,
>> KAM
>>
>>
>> On 10/29/2018 3:53 PM, Ariam Mogos wrote:
>>
>> Thanks so much Kellen, Dave and Kevin!
>>
>> (copying Aditi from our partnerships team)
>>
>> (copying David Banes and EA Draffan, two of our advisors on AAC)
>>
>>
>>
>> Yes we’d be interested in collaborating with Apache and learning more
>> about the incubator program.
>>
>>
>>
>> We’re very excited to share about this project. I’ve created a google doc
>> with some information here:
>>
>>
>>
>>
>> https://docs.google.com/document/d/1fMY5_YgqqE5VfqNCDwQ0HQe8ozkz1v7kpjQpimVsjuI/edit
>>
>>
>>
>> Please feel free to leave any comments, questions, recommendations in the
>> document.
>>
>>
>>
>> Cheers,
>> Ariam
>>
>>
>>
>> *From: *"Kevin A. McGrail"  
>> *Date: *Sunday, October 28, 2018 at 4:51 PM
>> *To: *"general@incubator.apache.org" 
>>  
>> *Cc: *Ariam Mogos  
>> *Subject: *Re: UNICEF Open Source project- Apache Foundation
>>
>>
>>
>> In addition to the list responses, I'm happy to chat especially with my
>> VP Fundraising duties. Love UNICEF and love what you do especially around
>> Halloween.  Happy to jump on a call and give you some guidance!
>>
>>
>>
>> Regards,
>>
>> KAM
>>
>> --
>>
>> Kevin A. McGrail
>>
>> VP Fundraising, Apache Software Foundation
>>
>> Chair Emeritus Apache SpamAssassin Project
>>
>> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>>
>>
>>
>>
>>
>> On Sun, Oct 28, 2018 at 1:39 AM Dave Fisher 
>> wrote:
>>
>> Exactly as Kellen describes!
>>
>> If for whatever reason you require an offline discussion to start then
>> I’m sure someone here may be willing to “champion” your proposal.
>>
>> Regards,
>> Dave
>>
>> Sent from my iPhone
>>
>> > On Oct 27, 2018, at 9:43 PM, kellen sunderland <
>> kellen.sunderl...@gmail.com> wrote:
>> >
>> > Hello Ariam, reading 

Re: [PROPOSAL] Changing requirements for IPMC

[Myrle Krantz]

On Wed, Nov 7, 2018 at 7:10 PM Dave Fisher  wrote:

> Hi -
>
> >> ...I propose this:
> >>
> >> If someone has done several of the following:
> >> - has been involved in an incubating project from start to finish
> >> - has been a release manager
> >> - has assembled LICENSE and NOTICE files
> >> - has reviewed and voted on releases
> >> - has proposed or accepted committers/PPMC members
> >>
> >> Then they can ask the IPMC to join to IPMC by sending an email to
> private@ listing what they have been involved in...
> >
> > I like that, +1
>
> I think that those items are hard to measure and are oriented to release
> policy only.
>
> I would propose a simpler requirement.
>
> - Any PMC member of any TLP including ComDev. We then do formal NOTICE to
> the Board and if there is a concern address it.
>

You're right that some (not all) of the items are hard to measure.  I think
your counter-proposal would just push work to the Board (who simply won't
do it), and may result in podlings getting stuck with inactive mentors, and
limbo'ed releases.  Perhaps it's possible to cut the original list down to
things that are measurable, and change the approach from one of enforcement
to one of enlistment:

* Is willing and able to review and vote on releases for the podling.
* Is willing and able to coach the podling in proposing and accepting
committers/PPMC members.

The real goal here, I think, is not to specify criteria that the IPMC or
the board can apply.  The real goal is two-fold: a.) to give a potential
mentor the information necessary to determine if they can do the job.  And
b.) to create an instrument of commitment.  The mentor commits to involve
themselves in specific ways in the podling's incubation.

Best Regards,
Myrle