> > However, maintaining an external repo is a risk. The Dubbo community > needs to keep a close eye on it and ensure that anything there is there > for a good reason and that the repo is not abused as a way to bypass the > ASF community. >
Good suggestion, we will keep close eye to make sure these projects run in the Apache way. In fact, we discuss these side projects here in @dev list from time to time, and expect the community to contribute not only dubbo rpc itself, but also any other area, as long as they are relevant to dubbo, and as long as they are valuable to the users. In short word, we want to keep core clean, but develop eco rich. Just as Mark said, we keep them in a separated place for the sound reasons, sometimes because they are too niche, sometimes because they are not mature, but we plan to move any of them in to incubate under ASF with no hesitate when we feel any of them is ready. Right now, all dubbo Apache committers are members of dubbo group. We do hope to run this group in the way of other Apache's project. Mark and Justin, I will invite you into dubbo group, pls. look into dubbo group closer and give us any advice if you see anything inappropriate. On Wed, Aug 29, 2018 at 8:52 PM Mark Thomas <ma...@apache.org> wrote: > On 29/08/18 09:55, Justin Mclean wrote: > > HI, > > > > Just a couple of questions below for people to ponder and I think it > worth having a discussion on list about this. I don’t think having this > external repo is a bad idea or against ASF policy but long term it could > harm the project. For instance only contributions to the Apache project can > be considered when voting committers or PMC members in. So contribution to > the eco system doesn't accrue merit in the project eyes. You may run into > licensing and other IP issues without ICLA to cover all contributions. > Projects in the eco system may not follow the release or other ASF > policies. I can see that several already don’t follow the ASF licensing > policy, which is OK as they are not ASF projects, but if you want to use > them with Dubbo that could cause issues. You see the sort of issues that > could occur here? > > > > What do other mentors think about this? > > I think it is something to keep an eye on. I'm simply not familiar > enough with the contents of the external repo to feel comfortable saying > whether I think the current split is correct or not. > > Generally, I would expect it to be in the best interests of the Dubbo > community to have as much as possible in a single place (here at the > ASF) but where there are good reasons that can't happen (licensing, too > niche) then an external repo managed by this community is a model that > has been used by other projects. > > However, maintaining an external repo is a risk. The Dubbo community > needs to keep a close eye on it and ensure that anything there is there > for a good reason and that the repo is not abused as a way to bypass the > ASF community. > > Mark >
