Re: Weex, Apache and outside code

Thanks for @Myrle, @Jan, @Dan, @Willem and everyone else who has make effort on this topic. Weex-Loader [1] and Weex-CLI [2] is a part of Apache Weex now. The problem is solved, finally. [1] https://github.com/apache/weex-loader [2] https://github.com/apache/weex-cli Best Regards, YorkShen 申远

Re: Weex, Apache and outside code

Going back through my mails, I realized I failed to answer one of your questions. My apologies. On Wed, Feb 20, 2019 at 9:24 AM 申远 wrote: > 1. If the corresponding code is owned by Alibaba, and someone represented > the company would sign the SGA, is there any necessary to have all the > contri

Re: Weex, Apache and outside code

>From my perspective, I'd like the idea of *geting the weex-toolkit donated and making the contributors Weex committers.* 1. If the corresponding code is owned by Alibaba, and someone represented the company would sign the SGA, is there any necessary to have all the contributors signed the SGA aga

Re: Weex, Apache and outside code

More information, here are the steps that will have to be completed for the IP clearance: http://incubator.apache.org/ip-clearance/ip-clearance-template.html I think finding out who currently *owns* the code is a good first step. My suspicion is that most of it is work-for-hire performed for Al

Re: Weex, Apache and outside code

Hi YorkShen, You may not need to contact all of the contributors. Some of the contributions may not pass the threshold of originality which is commonly applied in copyright law. For example: https://github.com/weexteam/weex-toolkit/commits?author=RiverCheng0825 This contributor only provided tw

Re: Weex, Apache and outside code

It took me some time to read things about IP Clearance , and I think https://github.com/weexteam/weex-toolkit is the only repo we should move. The following problems may prevent us from moving weex-toolkit to apache 1. According to informat

Re: Weex, Apache and outside code

Is weexteam/weex-toolkit really the only repo that should be included? If you go through this process, better make sure all the relevant stuff is included. If you plan to deprecate or remove things in the future, you can still do so. But for now _all_ the used code should be moved over to Apache.

Re: Weex, Apache and outside code

> > 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,

Re: Weex, Apache and outside code

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

Re: Weex, Apache and outside code

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 We

Re: Weex, Apache and outside code

Hi YorkShen, If you’re ready, I’ll file a Jira ticket with INFRA. Or would you like to do it? Best Regards, Myrle On Thu, Feb 14, 2019 at 3:48 AM 申远 wrote: > According to dependency in package.json > , I > don't think there is

Re: Weex, Apache and outside code

According to dependency in 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 J

Re: Weex, Apache and outside code

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 wrote: > > H

Re: Weex, Apache and outside code

> > I am not a committer for the apache/weex now, also I am not very familiar > with the apache process. I could start a committer's vote after we decide what to do next. Best Regards, YorkShen 申远 Dan 于2019年2月13日周三 上午11:41写道： > Hi Jan, > > > Definitely include INFRA in the move of the repos

Re: Weex, Apache and outside code

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 manuall

Re: Weex, Apache and outside code

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

Re: Weex, Apache and outside code

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: willemji

Re: Weex, Apache and outside code

Hey Dan, On Tue, Feb 12, 2019 at 4:46 AM Dan 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 c

Re: Weex, Apache and outside code

Hi, Myrle Sorry for the delay getting back to you. > 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 Ap

Re: Weex, Apache and outside code

Hi Dan, Some answers inline: On Fri, Feb 1, 2019 at 10:29 AM Dan wrote: > 2. The migration of the warehouse may cause some historical issues to > continue to track, the new repo will start from 0 (that's no bad, but a big > change). > Normally repo history can also be imported to an Apache rep

Re: Weex, Apache and outside code

Hey York Shen, I can understand why you're concerned, but nightly builds are a normal process for a lot of projects. A nightly build isn't a release, and getting user input can still be considered an "internal" process. We want to protect our users against a situation in which they thought they

Re: Weex, Apache and outside code

Good point re the subdomain, I didn't think about that. Best open an issue at https://issues.apache.org/jira/projects/INFRA/issues and ask if this is possible and how. Have a nice holiday you all! -J Am Fr., 1. Feb. 2019 um 14:40 Uhr schrieb York Shen : > > > Who goes ahead and does the first ve

Re: Weex, Apache and outside code

> Who goes ahead and does the first version as a PR? May be Dan could the job? BTW, as Chinese lunar year is coming, some of weex’s committers & contributor (include Dan and me) may take a vacation for one or two weeks. We may finish the document work when vacation is over. > Thanks for the exp

Re: Weex, Apache and outside code

> I totally agree with you. I think the first step is listing all the > corresponding toolchain and their relationship between weex in the document > clearly(e.g. xxx is official, and is third party plugin). Moving > weex-toolkit to Apache repos will be a huge according to my understanding,

Re: Weex, Apache and outside code

Hi, Jan. > that are _currently_ connected to Weex and list them on a page on the > documentation. Just a link to the repo and a short description what it > does ("weex-toolkit - A CLI for creating and managing Weex based > applications", "weex-pack - Scripts to run and build Weex apps for > differ

Re: Weex, Apache and outside code

Hi, awesome discussion I started here. Really like your responses. To add some context on the "unreleased code" discussion: For Apache Cordova we have official, voted releases, but all tooling can also be installed from git directly (`npm install -g cordova` vs. `npm install -g https://github.com

Re: Weex, Apache and outside code

Hi, all I suppose it's not just about the workload for Dan， it’s what do we think of the project. At first, Weex has no toolkits,  and thanks for Dan and other maintainer’s work, Weex has a good tool for starting guide,  and we link to it in our official site . Maybe there should be a more in

Re: Weex, Apache and outside code

Hi, Willem As the toolchain is not a necessary part of Weex framework and will not be published follow the Weex SDK, I thought the SNAPSHOT tag release cannot be worked on that issue. Thanks. Dan Willem Jiang 于2019年2月1日周五 下午5:34写道： > Here is instruction of distribution unrelease materials[1

Re: Weex, Apache and outside code

Here is instruction of distribution unrelease materials[1], as the SNAPSHOT means it's not official release, we just use it for the feedback the development. [1]https://www.apache.org/dev/release-distribution#unreleased Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Feb 1, 2019 at 4

Re: Weex, Apache and outside code

Hi Myrle, At present, I can think of the difficulties mainly in the following aspects: 1. I'm not very understanding of apache's workflow at present, and also I'm not a committer for Apache weex now, I should be voted to be a committer firstly. 2. The migration of the warehouse may cause some his

Re: Weex, Apache and outside code

According to my understanding and what Justin Mclean wrote https://lists.apache.org/thread.html/5c5a75f00d78211f75e10d17bfeb05bc7b0b4f9e8416fa602b0ebb54@%3Cgeneral.incubator.apache.org%3E

Re: Weex, Apache and outside code

Hello Dan, One answer inline below. On Fri, Feb 1, 2019 at 8:07 AM Dan wrote: > > About move weex-toolkit project into the Apache repo. > > For now, this is a little difficult and also inconvenient thing cause the > current 2.0 tools are in a state of rapid iteration, and I also hope to get > t

Re: Weex, Apache and outside code

A lot of Apache project has the SNAPSHOT release to get quick feedback from the community. It's OK if we don't announce the SNAPSHOT release as an office Apache release. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Feb 1, 2019 at 3:07 PM Dan wrote: > > Hey > > I'm the author of t

Re: Weex, Apache and outside code

Hey I'm the author of the weex-toolkit, also the main developer of the tools around weex, I need to explain the questions you mentioned above. > Is this redirection and inclusion of outside code intentional? Is this temporary or meant to be permanent? Early in the development and maintenance of t

Re: Weex, Apache and outside code

(Answering from my Apache address as my Gmail didn't receive your responses - I can only see them in the list archive. Strange.) Thanks York Shen and Willem Jiang for your answers. > As there are many Weex users coming from China and the GFW is a huge problem > for them, so we create several we

Re: Weex, Apache and outside code

Best Regards, York Shen 申远 > 在 2019年1月31日，21:12，Willem Jiang 写道： > > Apache is encourage to unify the community and current infrastructure > supports one project has multiple repositories. > If there is no license issue, we need to consider to move these > repositories into the umbrella of Ap

Re: Weex, Apache and outside code

Sorry for mis-sending previous e-mails. I will ask the authors of https://github.com/weexteam/xtoolkit and https://github.com/weexteam/weex-pack , not sure whether there is a license issue or they are happy to move

Re: Weex, Apache and outside code

Apache is encourage to unify the community and current infrastructure supports one project has multiple repositories. If there is no license issue, we need to consider to move these repositories into the umbrella of Apache Weex. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Thu, Jan 31, 2

Re: Weex, Apache and outside code

1. Repos Problem https://github.com/apache/incubator-weex-site is the repos for weex’s website as you mentioned. The repo for weex is https://github.com/apache/incubator-weex , from where weex community g

Weex, Apache and outside code

Hey, I recently spent some time looking into Weex (I am a PMC member of committer to Apache Cordova and was interested how you do things). But I quickly noticed, that although Weex being an Apache Incubator project, most of the code of Weex seems to come from an outside Github organization. This l