Re: [PROPOSAL] Changing requirements for IPMC

2018-11-10 Thread Roman Shaposhnik
On Wed, Nov 7, 2018 at 1:28 AM Bertrand Delacretaz
 wrote:
>
> Hi,
>
> On Tue, Nov 6, 2018 at 9:20 AM Justin Mclean  wrote:
> > ...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
>
> And maybe we should make sure each podling has at least one
> experienced mentor, that is one who has successfully brought other
> podlings to graduation, or a long-time ASF Member.

I like both the original idea (after all I, myself, was one such case -- an IPMC
member before an ASF member) and this idea of a mentor-in-training
for podlings.

+1 to both!

Thanks,
Roman.

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



Re: [PROPOSAL] Changing requirements for IPMC

2018-11-10 Thread Willem Jiang
+1 to elected non-members to the IPMC.
In this way, We could leverage hands from the PPMC member who has some
experience podling process.
>From my experience I learned a lot from the whole podling process even
I mentored serval project before.

Regards,

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem
On Sun, Nov 11, 2018 at 5:48 AM Justin Mclean  wrote:
>
>
> Hi,
>
> > 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.
>
> This is part of the issue, but I think with a large IPMC and a very large 
> pool of potential people it's a lot harder to recognise people with merit 
> compared to other PMCs.
>
> Anyone that is brought up for discussion, unless they are well known to 
> several active IPMC members, doesn't tend to go anywhere. (e.g. see last 
> person I brought up for possible inclusion in the IPMC).
>
> Its also hard to recognise people who have merit from working in their 
> podling (or even several podlings) as an IPMC member needs to be active in 
> all of podlings to se that activity.
>
> And finally when we do recognise people, there's probably a greater chance 
> (compared to other PMCs) that they may not be interested in joining the IPMC 
> as it may be tangential to their interests.
>
> > (4) As merit is acquired we VOTE on private@incubator.
>
> This proposal including voting for new IPMC members in the usual way.
>
> Thanks,
> Justin
>
> -
> 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: [VOTE] Accept the brpc Project into the Apache Incubator.

2018-11-10 Thread Byung-Gon Chun
+1 (binding)


On Sun, Nov 11, 2018 at 6:29 AM Justin Mclean 
wrote:

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

-- 
Byung-Gon Chun


Re: [PROPOSAL] Changing requirements for IPMC

2018-11-10 Thread Justin Mclean


Hi,

> 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.

This is part of the issue, but I think with a large IPMC and a very large pool 
of potential people it's a lot harder to recognise people with merit compared 
to other PMCs.

Anyone that is brought up for discussion, unless they are well known to several 
active IPMC members, doesn't tend to go anywhere. (e.g. see last person I 
brought up for possible inclusion in the IPMC).

Its also hard to recognise people who have merit from working in their podling 
(or even several podlings) as an IPMC member needs to be active in all of 
podlings to se that activity.

And finally when we do recognise people, there's probably a greater chance 
(compared to other PMCs) that they may not be interested in joining the IPMC as 
it may be tangential to their interests.

> (4) As merit is acquired we VOTE on private@incubator.

This proposal including voting for new IPMC members in the usual way.

Thanks,
Justin

-
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.

2018-11-10 Thread Justin Mclean
Hi,

+1 (binding)

Thanks,
Justin

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



Re: [PROPOSAL] Changing requirements for IPMC

2018-11-10 Thread Justin Mclean
Hi,

Bertrand recommendation on having at least one ASF mentor or experienced mentor 
seems sensible to me.

Dave it is the case that some experienced IPMC mentor dropout. we currently 
need more mentors to replace missing ones than we do for new incubating 
projects, so initial most of these people are likely to help out on existing 
projects.

Re measurement “criteria", these are just some indicators not hard rules set in 
stone, but I think we need to give people something to go by otherwise we wont 
get anyone volunteering (as Myrle said). I would consider any PMC member who 
volunteered, but some may not have the right experience, (e.g. they were voting 
in due to code contributions, but have little experience with community 
building, policy or releases)

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



[RESULT] [VOTE] Ratis-thirdparty 0.1.0rc1

2018-11-10 Thread Josh Elser
This vote passes with 3 binding +1's (Justin, Jitendra, Josh) and 
nothing else.


Thanks, all.

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



[VOTE] Release Apache SkyWalking (incubating) version 6.0.0-alpha

2018-11-10 Thread ???? Sheng Wu
Hi All,
This is a call for vote to release Apache SkyWalking (Incubating) version 
6.0.0-alpha.


The Apache SkyWalking community has tested, voted and approved the proposed
release of Apache SkyWalking (Incubating) 6.0.0-alpha


We now kindly request the Incubator PMC members review and vote on this
incubator release.


SkyWalking: APM (application performance monitor) tool for distributed systems, 
especially designed for microservices, cloud native and container-based 
(Docker, Kubernetes, Mesos) architectures. 
Underlying technology is a distributed tracing system.



Vote Thread:
 * 
https://lists.apache.org/thread.html/649d6ca16404ed752fd80ea1b6fc2c9aeaae1c525032ae90e3529cd5@%3Cdev.skywalking.apache.org%3E


Release notes:




* https://github.com/apache/incubator-skywalking/blob/v6.0.0-alpha/CHANGES.md




Release Candidate:




* https://dist.apache.org/repos/dist/dev/incubator/skywalking/6.0.0-alpha/
* sha512 checksums
- 
6ef68b622c6c26db5143238f545ef569919757b70ec3c950305063da8ded8789c2bf2cc31e8edeaa90e18a3697786dff1ef287c03cd8ff5701e11a75b3b65899
 apache-skywalking-apm-incubating-6.0.0-alpha-src.tgz
- 
acfae5d3ef91ba7ffbb2ad7aaf58f92ea494c5c55593a2e2ad393140194cd9db7f5a5a0e57066160d10c3e556749186b4549768484a9d341d49a1af083e240ed
 apache-skywalking-apm-incubating-6.0.0-alpha.tar.gz
- 
7553603875fc7a77d8cb7ea0108edaea25fc8790a8b13388b2ea1d3730b5f81a3771cf39703bcb89ce75a0387ed6ad7b8ed1d1a54d943e4e48de6e6f124072c9
 apache-skywalking-apm-incubating-6.0.0-alpha.zip




Maven 2 staging repository:




* 
https://repository.apache.org/content/repositories/orgapacheskywalking-1025/org/apache/skywalking/




Release Tag :




* https://github.com/apache/incubator-skywalking/tree/v6.0.0-alpha




Release CommitID :




* 
https://github.com/apache/incubator-skywalking/tree/14009ce1172e8d70c5410029a096d3ae1a41c76d
* Git submodule
* skywalking-ui: 
https://github.com/apache/incubator-skywalking-ui/tree/26f2c3b7bd93aa71897e842d90d272ee4cb618dc
* apm-protocol/apm-network/src/main/proto: 
https://github.com/apache/incubator-skywalking-data-collect-protocol/tree/e7fc69462955c86d70f3f7f33712dfe33ecefbc6
* 
oap-server/server-query-plugin/query-graphql-plugin/src/main/resources/query-protocol
 
https://github.com/apache/incubator-skywalking-query-protocol/tree/c65a23bd6b9bba8d1df30d4de261624952df2b7b




Keys to verify the Release Candidate :




* https://dist.apache.org/repos/dist/release/incubator/skywalking/KEYS 
corresponding to wush...@apache.org




Guide to build the release from source :




* 
https://github.com/apache/incubator-skywalking/blob/v6.0.0-alpha/docs/en/guides/How-to-build.md
* `docs/en/guides/How-to-build.md` in source tar



Voting will start now (10th Nov. date) and will remain open for at least 72 
hours, Request IPMC to give their vote.
[ ] +1 Release this package.
[ ] +0 No opinion.
[ ] -1 Do not release this package because





--
Sheng Wu
Apache SkyWalking & Sharding-Sphere