I think these are 2 things. 1. How to manage plugins? Because every one plugin could have a similar case, whether it is still working in current main branch and next release. 2. Which plugins should be maintained in the main repo(or monorepo)? In this context, we need to have a consensus about why Ambari doesn't fit the requirements.
The reasons listed in this proposal, seem too general. Sheng Wu 吴晟 Twitter, wusheng1108 Jiajie Zhong <[email protected]> 于2021年11月19日周五 下午2:45写道： > Hey guys, > > I am here to proposal we DolphinScheduler remove Apache Ambari plugin in > our main repo. > > I think we should keep our main repo as pure as possible, and Ambari plugin > is not our major features. > > For now Ambari plugin in our main repo, we have to verify the availability > when we create a new release. > And some users would create an issue about the plugin. All this things I > think is not the responsibilities of > DolphinScheduler, it more looks like the responsibilities of > DolphinScheduler, and should not blame > DolphinScheduler core itself. > > Maybe it is time to make it clear whose responsibility it is. > > If this proposal passes, we should: > 1. Create an issue and PR to remove code in `ambari_plugin` and other > related in main repo > 2. Remove related document in dev and 2.0 > > Best Wish > — Jiajie >
