Re: [DISCUSS] Import Maintainer Mechanism for Apache RocketMQ

Agreed, this is my point actually. The flatter the project structure, the easier it is for anyone to step up. This has been proven for years at the ASF. Installing hierarchy will only slow things down. Bruce On Wed, Apr 26, 2017 at 4:24 PM, Justin Mclean wrote: > Hi,

Re: [DISCUSS] Import Maintainer Mechanism for Apache RocketMQ

Hi, > So we want to import the maintainer mechanism for Apache RocketMQ to > promote the development of community efficiently, but I am not sure whether > it's ok for a incubator project, please mentors let me know If there are > any problems. I think it was probably introduced on those projects

Re: [DISCUSS] Import Maintainer Mechanism for Apache RocketMQ

Hi yukon, I haven't heard of this concept at the ASF before, so I guess it's something that only a few projects are using. It seems kinda heavy-handed, but maybe this is just my perspective in not having worked on the RocketMQ code base. Is the RocketMQ code base currently divided up with certain

Re: [DISCUSS] Import Maintainer Mechanism for Apache RocketMQ

+1 I remembered storm pmc member xinwang has raised the similar problem. IMO, we can learn from Apache other project’s best practice. Maintainer’s introduction is a good choise for RocketMQ's Issue, codebase and other community affairs. Consider this is a good start, We could polish this