Lovely guys, I think I must stand up and make clear about this Hackathon. As I have pointed out in our proposal discussion stage. Since RocketMQ opened its source in Github, over 100+(According to incomplete statistics) companies outside Alibaba Group have adopted or made secondary development in their production environment. So that’s the Hackathon goal. We hope more guys around the word can join us, creating a new ecosystem projects or make a secondary development based on RocketMQ. Also, I believed under the guidance of the Apache’s code of conduct and Apache way[2][3](collaborative software development,commercial-friendly standard license,consistently high quality software,respectful, honest, technical-based interaction,faithful implementation of standards,security as a mandatory feature).Apache RocketMQ community will become more healthy, more active, more mature :-)
As for master role. IMO, this is a service role for every project, similar to SCRUM’s master. we consider it as a product manager, product architect, product organizer. As we know, the first Hackathon has bring some guys, they are all active in RocketMQ community and familiar with apache way and apache code of conduct. Why ? We must thanks the backend mentors in the first Hackathon. As well, wei zhou and dongforever are willing to be the second Hackathon’s mentors, they will help those active contributors to be familiar with Apache. But, may be, we have made a mistake for Hackathon’s rewards, committers are voted within PPMC. So, we must remove this item :-) [1] https://www.apache.org/foundation/policies/conduct <https://www.apache.org/foundation/policies/conduct> [2]https://www.apache.org/foundation/how-it-works.html <https://www.apache.org/foundation/how-it-works.html> [3] https://community.apache.org/apache-way/apache-project-maturity-model.html <https://community.apache.org/apache-way/apache-project-maturity-model.html> > 在 2017年4月2日，21:08，Luke Han <[email protected]> 写道： > > Would like you guys to go through The Apache Way and Committer Guide first: > > https://www.apache.org/dev/new-committers-guide.html > > There's policy and standard for such role, such rights and others, as an > incubator project, the most important thing is try to follow The Apache Way. > > Thanks. > > > Best Regards! > --------------------- > > Luke Han > > On Sun, Apr 2, 2017 at 12:33 PM, wei zhou <[email protected]> wrote: > >> +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 >> >>
