I think we can transfer the repos to ASF first. As it is possible to use the disclaimer when making a release in ASF, the transfer should not effect the old release schedule. And we can make a new branch to do the clean up work(which may mess the repo up when it is not fully done), and then merge it back to the development branch. So before the first nasty clean up works done, we could still make releases based on the old code base which has the old license, etc.
And I think there is no technical problem for transferring the code base, the infra team will help? Just mirror the code from bitbucket to ASF gitbox, and then mirror it to GitHub, then we could start to use GitHub. And we could even just clone the code to local, and then push it to the ASF gitbox, no problem. The problem maybe the stuff on BitBucket other than code, for example, the issues and PRs? I do not think it is easy to transfer these things... Are they important to the project Greg? Thanks. Justin Mclean <justinmcl...@me.com.invalid> 于2019年11月29日周五 下午12:28写道： > Hi, > > > It is our intention to use the Apache GitHub. > > Just be aware that you can use git as well and modify the ASF mirror and > the changes will go to GitHub and vice versa. People don’t have to use > GitHub if they don’t want to. > > > I do have some question about the transition. NuttX is a very active > project with a large user base. We have to both (1) modify the code base > to conform to licensing and other requirements, but also (2) continue to > support the community with quality releases. > > I would suggest moving over repos quickly and continuing to make releases > at the ASF with the work in progress disclaimer. Alternatively you could > not transfer right away and continue to make a couple of non ASF releases > while things are put in order in your current bitbucket repos. Up to the > project to decide. > > > I imagine that it will take a month or two to get the GitHub > repositories ready for prime time. > > The physical transfer shouldn’t take that long, fixing up all the headers > and licenses may take longer but that’s OK when using the work in progress > disclaimer, you can makes incubating ASF release that don’t fully comply > with ASF policy when including that disclaimer. > > > with changes pulled into the Apache Github until such time that support > can transition seamlessly to GitHub. > > Im not sure how easy that’s going to be, generally infra have made a > single transfer and I’m not aware of any projects that tried this approach. > It would require some discussion with infra to see what’s possible here. > > Thanks, > Justin > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
