+1, Personally very much agree with the views of Justin, Thank you for
professional guidance, as you help us to join the Apache community. Every one
of us to join the open source community are volunteers, the essence of the open
source community is to share our knowledge of open source, where only help and
help
> On 2017年4月2日, at 10:58, Justin Mclean <[email protected]> wrote:
>
> Hi,
>
>> As I known, the 'master' here mainly means one of the github project member
>> roles, others are 'guest' 'reporter' 'develop'. The one who was elected as
>> 'master' will be granted master privileges to the project, here is the 'Big
>> Data' project. Then the 'master' could be easily manage the code repo.
>
> First off, just in case this is unclear, this is how commitership works. The
> vote for new committers must take place on the private list and only PMC
> votes are binding. Only committers to Apache RocketMQ are given access to the
> Apache git repos.
>
> As I understand it this is for some external GitHub repos(?)
>
> It's a little confusing as:
> - We have a vote occurring on an Apache list for something that is not part
> of an Apache project
> - It’s unclear who votes are binding (it should only be PPMC members)
> - This seems to have just sprung up out of nowhere, although I may of missed
> the discussion? I really would of like to have seen this discussed on list by
> the PPMC and others before calling for votes.
>
> I think it would of been better to just ask for volunteers to help out
> (preferably committers) and give any who asked the access privileges to those
> external repos or to have simply given everyone equal access.
>
> In general votes other that for releases or new committer and PMC member
> should be rare and only used once the issue has been discussed and consensus
> has been reached.
>
> Thanks,
> Justin
