On Fri, Jun 3, 2022 at 7:52 PM 吴治国 <[email protected]> wrote: > > Of course. > > Hi everyone, > > Here are the details I share with Kengo, Brahma and Michiel: > > Let me explain why we want to restart Ambari's community and the current > status of re-incubation. > > Since Ambari still has large demands, the retirement makes lots of companies > looking for a replacement. > My team also needs to manage some new bigdata components that Ambari doesn't > provide, But the only choice is to redevelop a fork version of it, And we > have the idea to upload it to github, start a new community. > But compare to maintain the Ambari's original community, start a new one > based on fork version has some disadvantages. > First, we can no longer use the name "Ambari", which will make it difficult > for original users to find it. It can also lead to insufficient attraction of > new developers. > Next, that name change also causes inconvenience for end users and other > projects leveraging Ambari, e.g., Bigtop. They have to change their > operational procedures, scripts, users guide, and so on. > Lastly, we have to rebuild the development infrastructure and workflows etc., > but it's time-consuming and meaningless because Ambari has already done it. > So we hope we can help restart Ambari's community again. > > And if Ambari can be successfully re-incubated, I think there should be > in-depth collaboration with bigtop community in the future. > > Currently, the proposal has a draft version, and we now have 1 champion, 2 > mentors, and some initial committers(Sorry I cannot share the details here).
Honestly, I think we can do it in a much simpler way if we manage to find at least 3 ASF Members who are willing to oversee the initial PMC and make sure that the community actually re-coalesces. Between myself (I'm definitely interested) and perhaps Cos (CCed) would only need one more ASF member to try a direct route. Anybody else interested in helping? Thanks, Roman.
