Hi Nick, Thank you for understanding the pull-request driven workflow. We, this Apache incubator project, need management on operation at github/apache/incubator-milagro because it is in the critical path of the pull-request driven workflow. That is the reason why I am offering the effort for the management as a participant of the project.
We appreciate if you are happy to take a part in the management too. I do not think you are a man-in-the-middle because you have a role that connects this project with the Apache eco-system. Let's go forward together. Regards, Go Yamamoto -----Original Message----- From: Nick Kew [mailto:n...@apache.org] Sent: Tuesday, April 10, 2018 11:55 PM To: dev@milagro.incubator.apache.org Subject: Re: [VOTE] Retire Milagro On Tue, 10 Apr 2018 16:30:25 +0900 "Go Yamamoto" <yamamoto...@lab.ntt.co.jp> wrote: > Hi Nick, > > I agree the infrastructure problem you have pointed out My problem is that I'm man-in-the-middle here. I have an incomplete understanding of what you're looking for, including your first paragraph. > We NTT request to allow for contributors to work at their own fork > repository. All the changes on the code happens at local fork > repositories owned by each contributor, however, the changes at local > fork will be pull-requested to the official repo, and the operation > team at the official repo will review the pull-request and merge it to > the official. Yes, that's normal. Though as much as possible of that forked work should take place in public repos, too: that's what git is good at! I'd expect most local private forks to have a lifetime of just a few days - while the developer works through an issue - before either becoming public or abandoned. > If this workflow is OK for everybody here, NTT would like to take the > effort of operational tasks and managements on the official repo at > least until we reach the first release. How is that bringing the work to Apache? -- Nick Kew
