> > 1. What repositories should be imported? (=> List of repositories)
https://github.com/weexteam/weex-toolkit 2. Who contributed to theses repositories? Who are active and relevant > contributors? (Individuals and companies) (=> List of names) > 25 individuals, maybe two or three are active, detail: https://github.com/weexteam/weex-toolkit/graphs/contributors 3. Are all names from that list joining as contributors / PMC members? (=> > Yes/No) No, most of them are not. 5. If no: SGA It Seems like a SGA is needed, though it is almost impossible to contact all of the 25 contributors. What confuses me is repository we talked about is under *MIT license* by individual developers , Is IP clearness is still necessary here? Best Regards, YorkShen 申远 Jan Piotrowski <[email protected]> 于2019年2月14日周四 下午5:38写道： > I read through the links you provided Willem, and extracted the following > questions that have to be answered: > > 1. What repositories should be imported? (=> List of repositories) > 2. Who contributed to theses repositories? Who are active and relevant > contributors? (Individuals and companies) (=> List of names) > 3. Are all names from that list joining as contributors / PMC members? (=> > Yes/No) > 4. If yes: ICLA for all have to be available > 5. If no: SGA > 6. Is [email protected] ok with the ICLAs and SGAs on hand? > > I assume that the existing weex Apache codebase went through the same > process, so this shouldn't actually be too hard if only the same people > worked on the additional repositories that should be moved. > > When the questions above are answered, it should be pretty easy for one of > the mentors to start the code acceptance process, correct? > > J > > Am Do., 14. Feb. 2019 um 08:03 Uhr schrieb Willem Jiang < > [email protected]>: > > > We need to do the IP Clearance[1] first. To be honest, it's my first > > time to go through this process. > > We could take the others project path[2] as an example. > > > > [1]https://incubator.apache.org/guides/ip_clearance.html > > [2]http://incubator.apache.org/ip-clearance/ > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Thu, Feb 14, 2019 at 10:48 AM 申远 <[email protected]> wrote: > > > > > > According to dependency in package.json > > > <https://github.com/weexteam/weex-toolkit/blob/master/package.json>, I > > > don't think there is a IP issue. Maybe Dan could do a double check. > > > > > > BTW, what's the standard procedure if we want to move a repo to Apache > > > project ? > > > > > > Best Regards, > > > YorkShen > > > > > > 申远 > > > > > > > > > Willem Jiang <[email protected]> 于2019年2月13日周三 下午2:35写道： > > > > > > > If we want to move the repo, we need to address the SGA problem > first. > > > > It has nothing to do with the committer right yet, we just need to > > > > make sure the IP issue is resolved before moving forward. > > > > > > > > Willem Jiang > > > > > > > > Twitter: willemjiang > > > > Weibo: 姜宁willem > > > > > > > > On Wed, Feb 13, 2019 at 11:41 AM Dan <[email protected]> wrote: > > > > > > > > > > Hi Jan, > > > > > > > > > > > Definitely include INFRA in the move of the repositories, they > can > > > > > probably > > > > > make it a normal move/transfer of a GitHub repository between two > > orgs, > > > > so > > > > > not only the stars, but also issues, PRs etc are moved and the old > > URLs > > > > are > > > > > automatically forwarded. The only thing one has to do manually, is > to > > > > > update the user/repository name if you use it in the code somewhere > > - but > > > > > probably also not _right now_, but whenever you have the time to do > > so - > > > > as > > > > > all the links, repository clones etc. should be forwarded. > > > > > > > > > > Did you mean to transfer the `weexteam/weex-toolkit` project to the > > link > > > > > like `apache/incubator-weex-tools`? This seems to be a relatively > > > > low-cost > > > > > method at present. I only need someone to help me check the > > > > specifications > > > > > of the project. > > > > > > > > > > By the way, after that, there will be three git repo on the > > > > > `apache/weex` team, like `apache/incubator-weex`, > `apache/incubator- > > > > > weex-site` and `apache/incubator-weex-tools`, I don't know that's > > ok or > > > > > not, just tell the situation. > > > > > > > > > > I am not a committer for the apache/weex now, also I am not very > > familiar > > > > > with the apache process. > > > > > > > > > > Maybe someone can list what we need to do next? > > > > > > > > > > Thanks, > > > > > Dan > > > > > > > > > > Jan Piotrowski <[email protected]> 于2019年2月12日周二 下午9:20写道： > > > > > > > > > > > If I may give some input here as well: > > > > > > Definitely include INFRA in the move of the repositories, they > can > > > > probably > > > > > > make it a normal move/transfer of a GitHub repository between two > > > > orgs, so > > > > > > not only the stars, but also issues, PRs etc are moved and the > old > > > > URLs are > > > > > > automatically forwarded. The only thing one has to do manually, > is > > to > > > > > > update the user/repository name if you use it in the code > > somewhere - > > > > but > > > > > > probably also not _right now_, but whenever you have the time to > > do so > > > > - as > > > > > > all the links, repository clones etc. should be forwarded. > > > > > > > > > > > > -J > > > > > > > > > > > > Am Di., 12. Feb. 2019 um 13:43 Uhr schrieb Willem Jiang < > > > > > > [email protected]>: > > > > > > > > > > > > > I don't aware the git repository transfer issue, if it related > > to the > > > > > > > snapshot release, I think we can work out a solution for it. > > > > > > > If it relates to SGA things, I think we need to dig more detail > > about > > > > > > that. > > > > > > > Anyway, I'd happy to help you to do the code transfer work. > > > > > > > > > > > > > > Willem Jiang > > > > > > > > > > > > > > Twitter: willemjiang > > > > > > > Weibo: 姜宁willem > > > > > > > > > > > > > > On Tue, Feb 12, 2019 at 5:33 PM Myrle Krantz <[email protected] > > > > > > wrote: > > > > > > > > > > > > > > > > Hey Dan, > > > > > > > > > > > > > > > > On Tue, Feb 12, 2019 at 4:46 AM Dan <[email protected]> > > wrote: > > > > > > > > > > > > > > > > > Hi, Myrle > > > > > > > > > > > > > > > > > > Sorry for the delay getting back to you. > > > > > > > > > > > > > > > > > > > > > > > > > No problem. I hope you enjoyed Chinese New Year! > > > > > > > > > > > > > > > > > Normally repo history can also be imported to an Apache > > > > repository. > > > > > > Is > > > > > > > > > that what you mean by warehouse? > > > > > > > > > > > > > > > > > > The `warehouse` is caused by incorrect translation, it > should > > > > means > > > > > > git > > > > > > > > > repo, don't mind. I know there has a way to import history > > into > > > > > > Apache > > > > > > > > > repo, but based on the experience of the last weex repo > > > > migration, > > > > > > some > > > > > > > > > developers will be very uncomfortable with this change, and > > may > > > > even > > > > > > > feel > > > > > > > > > that this is an unstable performance. At the same time, > some > > > > > > developers > > > > > > > > > will still feedback new project issues in the old project. > We > > > > need to > > > > > > > > > conduct reasonable and effective guidance, I think this is > > not a > > > > > > matter > > > > > > > > > that can be decided immediately, I will initiate a vote on > > this > > > > > > matter. > > > > > > > > > > > > > > > > > > > > > > > > > I'm sorry to hear that things didn't go smoothly in the first > > > > transfer. > > > > > > > I > > > > > > > > don't know the details, since I wasn't mentoring then. > > > > > > > > > > > > > > > > As I understand it, Infra can also do a repository move, > which > > > > would > > > > > > > bring > > > > > > > > over all the stars, etc. Would you like me to ask? > > > > > > > > > > > > > > > > Best Regards, > > > > > > > > Myrle > > > > > > > > > > > > > > > > > > > >
