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

申远


Myrle Krantz  于2019年3月9日周六 下午6:54写道：

> 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
> > contributors signed the SGA again?
> >
>
> I believe that would be sufficient, but you should ask the legal
> committee.  (See below.)
>
> 2. From my point of view, there will be lots of copyright  / trademark
> > issues around, as none of the PPMC member is lawyer, Is there anyone from
> > Apache we can consult about the law issue?
> >
>
> There is!  This is one of the services ASF provides for its projects.  You
> can email legal-disc...@apache.org or, if it's something that needs to be
> kept private legal-inter...@apache.org.  You may prefer to submit a JIRA
> ticket (https://issues.apache.org/jira/projects/LEGAL)  You can get more
> information here: https://www.apache.org/legal/
>
>
> > 3. weex-toolkit is already an open source project under MIT license,
> would
> > it violate any copyright  / trademark rules/laws if we fork the original
> > weex-toolkit and push it to Apache repos.
> >
>
> I believe it would be allowed, because the MIT license is a category A
> license.  But I suggest you ask someone with more legal know-how (see
> above).  It may not accomplish your purposes unless you convince the
> developers there to start doing their work here.  If they were to continue
> working over there, it would be problematic because the Weex PMC wouldn't
> be able to participate in decisions about who commits or what they commit.
>
> Best Regards,
> Myrle
>

Re: Weex, Apache and outside code

[Myrle Krantz]

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
> contributors signed the SGA again?
>

I believe that would be sufficient, but you should ask the legal
committee.  (See below.)

2. From my point of view, there will be lots of copyright  / trademark
> issues around, as none of the PPMC member is lawyer, Is there anyone from
> Apache we can consult about the law issue?
>

There is!  This is one of the services ASF provides for its projects.  You
can email legal-disc...@apache.org or, if it's something that needs to be
kept private legal-inter...@apache.org.  You may prefer to submit a JIRA
ticket (https://issues.apache.org/jira/projects/LEGAL)  You can get more
information here: https://www.apache.org/legal/


> 3. weex-toolkit is already an open source project under MIT license, would
> it violate any copyright  / trademark rules/laws if we fork the original
> weex-toolkit and push it to Apache repos.
>

I believe it would be allowed, because the MIT license is a category A
license.  But I suggest you ask someone with more legal know-how (see
above).  It may not accomplish your purposes unless you convince the
developers there to start doing their work here.  If they were to continue
working over there, it would be problematic because the Weex PMC wouldn't
be able to participate in decisions about who commits or what they commit.

Best Regards,
Myrle

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 again?

2. From my point of view, there will be lots of copyright  / trademark
issues around, as none of the PPMC member is lawyer, Is there anyone from
Apache we can consult about the law issue?

3. weex-toolkit is already an open source project under MIT license, would
it violate any copyright  / trademark rules/laws if we fork the original
weex-toolkit and push it to Apache repos.

Best Regards,
YorkShen

申远


Myrle Krantz  于2019年2月19日周二 下午7:40写道：

> 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 Alibaba.  That
> would mean Alibaba owns the code.  Please use your contacts inside that
> company to find out.
>
> Best Regards,
> Myrle
>
>
> On Tue, Feb 19, 2019 at 12:30 PM Myrle Krantz  wrote:
>
> > 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 two commits and both were minor wording
> > changes.  My initial guess looking at the contributors list is that
> you'll
> > need to contact roughly half of the contributors.  If you're lucky, some
> of
> > them are already part of the Weex project.
> >
> > That's the copyright law side of things.  On the trademark law side of
> > things you have a different problem.  As far as I know, the weex name
> > belongs to Apache.  Naming an account weexteam, and a project
> weex-toolkit
> > violates that trademark.  It implies that a thing is Apache Weex which is
> > clearly not, since
> > * the license of the code isn't Apache,
> > * the code doesn't belong to Apache,
> > * the contributors aren't discussing their changes on the Apache mailing
> > lists, and
> > * the Apache Weex PMC can't decide who is allowed to contribute to the
> > code.
> >
> > I'm guessing that you want most of that code to actually be part of the
> > Apache Weex project.  If you can get it donated, that will be a much
> nicer
> > way to resolve the problem.  But if you can't get it resolved that way,
> the
> > names of the things that aren't Weex will have to be changed so that they
> > aren't misleading.  In short you have two options:
> >
> > * Get the code donated and make the contributors Weex committers, or
> > * Change the names in the code so that it doesn't call itself Weex.
> >
> > I believe getting the code donated would be better for the community.
> But
> > it's up to you.  Either way, I'll help you navigate Apache in the steps
> > involved.
> >
> > You have time to do this, so you can do it repository by repository if
> you
> > need to.  But you'll have to get it done before Weex can graduate.
> >
> > Best Regards,
> > Myrle
> >
> > On Mon, Feb 18, 2019 at 8:29 AM 申远  wrote:
> >
> >> 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 informations on github
> >>,
> there
> >>are 25 contributors, it is almost impossible to notify all them to
> >> sign the
> >>SGA.
> >>2. weex-toolkit is owned not by Alibaba Group
> >> but a custom weexteam
> >> organization among which many
> developers
> >>are employees of Alibaba Group. As I am not an IP lawyer, I don't
> know
> >>whether there is a potential IP issues or how to solve this issue.
> >>
> >> Best Regards,
> >> YorkShen
> >>
> >> 申远
> >>
> >>
> >> Jan Piotrowski  于2019年2月15日周五 下午7:44写道：
> >>
> >> > 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.
> >> >
> >> > For the details on SGA/MIT etc the mentors will have to help. Usually
> >> > there are practical and simple solutions to these things.
> >> >
> >> > J
> >> >
> >> > Am Fr., 15. Feb. 2019 um 05:16 Uhr schrieb 申远 :
> >> > >
> >> > > >
> >> > > > 1. What repositories should be 

Re: Weex, Apache and outside code

[Myrle Krantz]

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 Alibaba.  That
would mean Alibaba owns the code.  Please use your contacts inside that
company to find out.

Best Regards,
Myrle


On Tue, Feb 19, 2019 at 12:30 PM Myrle Krantz  wrote:

> 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 two commits and both were minor wording
> changes.  My initial guess looking at the contributors list is that you'll
> need to contact roughly half of the contributors.  If you're lucky, some of
> them are already part of the Weex project.
>
> That's the copyright law side of things.  On the trademark law side of
> things you have a different problem.  As far as I know, the weex name
> belongs to Apache.  Naming an account weexteam, and a project weex-toolkit
> violates that trademark.  It implies that a thing is Apache Weex which is
> clearly not, since
> * the license of the code isn't Apache,
> * the code doesn't belong to Apache,
> * the contributors aren't discussing their changes on the Apache mailing
> lists, and
> * the Apache Weex PMC can't decide who is allowed to contribute to the
> code.
>
> I'm guessing that you want most of that code to actually be part of the
> Apache Weex project.  If you can get it donated, that will be a much nicer
> way to resolve the problem.  But if you can't get it resolved that way, the
> names of the things that aren't Weex will have to be changed so that they
> aren't misleading.  In short you have two options:
>
> * Get the code donated and make the contributors Weex committers, or
> * Change the names in the code so that it doesn't call itself Weex.
>
> I believe getting the code donated would be better for the community.  But
> it's up to you.  Either way, I'll help you navigate Apache in the steps
> involved.
>
> You have time to do this, so you can do it repository by repository if you
> need to.  But you'll have to get it done before Weex can graduate.
>
> Best Regards,
> Myrle
>
> On Mon, Feb 18, 2019 at 8:29 AM 申远  wrote:
>
>> 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 informations on github
>>, there
>>are 25 contributors, it is almost impossible to notify all them to
>> sign the
>>SGA.
>>2. weex-toolkit is owned not by Alibaba Group
>> but a custom weexteam
>> organization among which many developers
>>are employees of Alibaba Group. As I am not an IP lawyer, I don't know
>>whether there is a potential IP issues or how to solve this issue.
>>
>> Best Regards,
>> YorkShen
>>
>> 申远
>>
>>
>> Jan Piotrowski  于2019年2月15日周五 下午7:44写道：
>>
>> > 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.
>> >
>> > For the details on SGA/MIT etc the mentors will have to help. Usually
>> > there are practical and simple solutions to these things.
>> >
>> > J
>> >
>> > Am Fr., 15. Feb. 2019 um 05:16 Uhr schrieb 申远 :
>> > >
>> > > >
>> > > > 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 

Re: Weex, Apache and outside code

[Myrle Krantz]

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 two commits and both were minor wording
changes.  My initial guess looking at the contributors list is that you'll
need to contact roughly half of the contributors.  If you're lucky, some of
them are already part of the Weex project.

That's the copyright law side of things.  On the trademark law side of
things you have a different problem.  As far as I know, the weex name
belongs to Apache.  Naming an account weexteam, and a project weex-toolkit
violates that trademark.  It implies that a thing is Apache Weex which is
clearly not, since
* the license of the code isn't Apache,
* the code doesn't belong to Apache,
* the contributors aren't discussing their changes on the Apache mailing
lists, and
* the Apache Weex PMC can't decide who is allowed to contribute to the code.

I'm guessing that you want most of that code to actually be part of the
Apache Weex project.  If you can get it donated, that will be a much nicer
way to resolve the problem.  But if you can't get it resolved that way, the
names of the things that aren't Weex will have to be changed so that they
aren't misleading.  In short you have two options:

* Get the code donated and make the contributors Weex committers, or
* Change the names in the code so that it doesn't call itself Weex.

I believe getting the code donated would be better for the community.  But
it's up to you.  Either way, I'll help you navigate Apache in the steps
involved.

You have time to do this, so you can do it repository by repository if you
need to.  But you'll have to get it done before Weex can graduate.

Best Regards,
Myrle

On Mon, Feb 18, 2019 at 8:29 AM 申远  wrote:

> 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 informations on github
>, there
>are 25 contributors, it is almost impossible to notify all them to sign
> the
>SGA.
>2. weex-toolkit is owned not by Alibaba Group
> but a custom weexteam
> organization among which many developers
>are employees of Alibaba Group. As I am not an IP lawyer, I don't know
>whether there is a potential IP issues or how to solve this issue.
>
> Best Regards,
> YorkShen
>
> 申远
>
>
> Jan Piotrowski  于2019年2月15日周五 下午7:44写道：
>
> > 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.
> >
> > For the details on SGA/MIT etc the mentors will have to help. Usually
> > there are practical and simple solutions to these things.
> >
> > J
> >
> > Am Fr., 15. Feb. 2019 um 05:16 Uhr schrieb 申远 :
> > >
> > > >
> > > > 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  于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 gene...@incubator.apache.org ok with the ICLAs and 

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 informations on github
   , there
   are 25 contributors, it is almost impossible to notify all them to sign the
   SGA.
   2. weex-toolkit is owned not by Alibaba Group
    but a custom weexteam
    organization among which many developers
   are employees of Alibaba Group. As I am not an IP lawyer, I don't know
   whether there is a potential IP issues or how to solve this issue.

Best Regards,
YorkShen

申远


Jan Piotrowski  于2019年2月15日周五 下午7:44写道：

> 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.
>
> For the details on SGA/MIT etc the mentors will have to help. Usually
> there are practical and simple solutions to these things.
>
> J
>
> Am Fr., 15. Feb. 2019 um 05:16 Uhr schrieb 申远 :
> >
> > >
> > > 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  于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 gene...@incubator.apache.org 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 <
> > > willem.ji...@gmail.com>:
> > >
> > > > 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 申远  wrote:
> > > > >
> > > > > 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 Jiang  于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 
> wrote:
> > > > > > >
> > > > > > > Hi Jan,
> > > > > > >
> > > > > > > > Definitely include INFRA in the move of the repositories,
> they
> > > can
> > > > > > > probably
> > > > > > > make it a normal move/transfer of a GitHub 

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, 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  于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 gene...@incubator.apache.org 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 <
> willem.ji...@gmail.com>:
>
> > 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 申远  wrote:
> > >
> > > 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 Jiang  于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  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  于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 

Re: Weex, Apache and outside code

[Jan Piotrowski]

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 gene...@incubator.apache.org 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 <
willem.ji...@gmail.com>:

> 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 申远  wrote:
> >
> > 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 Jiang  于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  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  于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 <
> > > > > willem.ji...@gmail.com>:
> > > > >
> > > > > > 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 
> > > wrote:
> > > > > > >
> > > > > > > Hey Dan,
> > > > > > >
> > > > > > > On Tue, Feb 12, 2019 at 4:46 AM Dan 
> wrote:
> > 

Re: Weex, Apache and outside code

[Willem Jiang]

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 申远  wrote:
>
> 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 Jiang  于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  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  于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 <
> > > > willem.ji...@gmail.com>:
> > > >
> > > > > 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 
> > wrote:
> > > > > >
> > > > > > 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 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 

Re: Weex, Apache and outside code

[Myrle Krantz]

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 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  于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  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  于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 <
> > > > willem.ji...@gmail.com>:
> > > >
> > > > > 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 
> > wrote:
> > > > > >
> > > > > > 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 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 

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 Jiang  于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  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  于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 <
> > > willem.ji...@gmail.com>:
> > >
> > > > 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 
> wrote:
> > > > >
> > > > > 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 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
> > > >
> > >
>

Re: Weex, Apache and outside code

[Willem Jiang]

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:
>
> 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  于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 <
> > willem.ji...@gmail.com>:
> >
> > > 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  wrote:
> > > >
> > > > 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 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
> > >
> >

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 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  于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 <
> > willem.ji...@gmail.com>:
> >
> > > 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  wrote:
> > > >
> > > > 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 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
> > >
> >
>

Re: Weex, Apache and outside code

[Dan]

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  于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 <
> willem.ji...@gmail.com>:
>
> > 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  wrote:
> > >
> > > 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 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
> >
>

Re: Weex, Apache and outside code

[Jan Piotrowski]

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 <
willem.ji...@gmail.com>:

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

Re: Weex, Apache and outside code

[Willem Jiang]

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

Re: Weex, Apache and outside code

[Myrle Krantz]

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

Re: Weex, Apache and outside code

[Dan]

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

> Which kinds of adjustments do you need to make for an Apache project?
Generally, as long as the code is legally licenseable with the ApacheV2
license, Apache doesn't set technical requirements.  The Weex project may
have technical requirements, but I haven't heard anyone espress any here.

That's ok, I can handle these.

Thanks.
Dan

Myrle Krantz  于2019年2月5日周二 上午12:04写道：

> 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 repository.  Is
> that what you mean by warehouse?
>
>
> > 3. I need to re-adjust my code and follow the apache approach, which also
> > has a certain cost for me, and now I was the only one who works on the
> > weex toolchain.
> >
>
> Which kinds of adjustments do you need to make for an Apache project?
> Generally, as long as the code is legally licenseable with the ApacheV2
> license, Apache doesn't set technical requirements.  The Weex project may
> have technical requirements, but I haven't heard anyone espress any here.
>
>
> > I look forward to more comments and discussions to get this matter going.
> >
>
> Thank you for being so open to considering this!
>
> Best Regards,
> Myrle
>

Re: Weex, Apache and outside code

[Myrle Krantz]

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 repository.  Is
that what you mean by warehouse?


> 3. I need to re-adjust my code and follow the apache approach, which also
> has a certain cost for me, and now I was the only one who works on the
> weex toolchain.
>

Which kinds of adjustments do you need to make for an Apache project?
Generally, as long as the code is legally licenseable with the ApacheV2
license, Apache doesn't set technical requirements.  The Weex project may
have technical requirements, but I haven't heard anyone espress any here.


> I look forward to more comments and discussions to get this matter going.
>

Thank you for being so open to considering this!

Best Regards,
Myrle

Re: Weex, Apache and outside code

[Myrle Krantz]

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 had Apache licensed code, but are sued
for intellectual property theft.  As long as your testers are just trying
out your nightly build that shouldn't be a danger, right?

Best Regards,
Myrle

On Fri, Feb 1, 2019 at 9:44 AM York Shen  wrote:

> According to my understanding and what Justin Mclean wrote
> https://lists.apache.org/thread.html/5c5a75f00d78211f75e10d17bfeb05bc7b0b4f9e8416fa602b0ebb54@%3Cgeneral.incubator.apache.org%3E
> <
> https://lists.apache.org/thread.html/5c5a75f00d78211f75e10d17bfeb05bc7b0b4f9e8416fa602b0ebb54@%3Cgeneral.incubator.apache.org%3E>
> , any format of unofficial release is forbidden, all release must be voted
> before we publish it.
>
> Correct me if I am wrong.
>
>
> Best Regards,
> York Shen
>
> 申远
>
> > 在 2019年2月1日，16:27，Willem Jiang  写道：
> >
> > 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 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 this project, the project
> was
> >> designed to support package integration of multiple command line tools,
> and
> >> to manage mappings between them through xtoolkit module, the idea is
> good,
> >> but too many projects are scattered into the various git repo, such as
> >> weex-debugger, weex-pack and so on.
> >>
> >> On the weex-toolkit@2.0,  I'm split each function module into separate
> >> parts, and manage multiple separate releases in the repository via
> Lerna,
> >> after that you can find all the module you want in the weex-toolkit repo
> >> (currently in the alpha process), you can enjoy it follow the document
> >> here: https://weex.io/tools/toolkit.html, it also supports the
> thrid-part
> >> extensions, the document will be further supplemented
> >>
> >>> 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
> >> the user's usage from the tool, this may not be allowed by apache, I
> prefer
> >> to develop these tools as a third-party developer, it should be ok to
> >> remind users in the documentation that it's not part of Apache Weex.
> >>
> >>> why the module called toolkit but not cli?
> >>
> >> This is the name defined by the previous module creator. I personally
> think
> >> it might be better to call it weex-cli. Maybe I will consider renaming
> the
> >> module soon.
> >>
> >> Thanks
> >> Dan
> >>
> >> Jan Piotrowski  于2019年2月1日周五 上午3:13写道：
> >>
> >>> (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 website for users from China to
> have
> >>> the right access. You can choose whatever you want, as the three
> websites
> >>> are all the same.
> >>>
> >>> Thanks for that explanation.
> >>>
> >>> In my opinion (and maybe Apache guidelines?) there should only be _one_
> >>> domain per Apache project, so you know you can trust the content of
> that
> >>> domain. You (the team) should probably decide which one of the two
> >>> apache.org domains you should use (and can use per incubation rules!),
> >>> and redirect the other one. Otherwise both Google and users can be
> >>> confused.
> >>> For the non-Apache mirrors for Chinese users you could maybe add a
> banner
> >>> that this is a mirror of *.apache.org for Chinese users and link to it
> >>> from somewhere _on_ the site so it is discoverable? Additionally maybe
> >>> no-index the domain, so Google doesn't list them? Then it is all
> >>> transparent and there is no confusion.
> >>>
>  The repo for weex is https://github.com/apache/incubator-weex, from
> >>> where weex community generates apache release.
>  All the other repos is not officially belong to weex, though some of
> are
> >>> useful tools for debug, development purpose. They are just useful
> tools,
> >>> one can using weex framework without these tools with no problem. I
> will
> >>> consider these tools as useful plugins, and 

Re: Weex, Apache and outside code

[Jan Piotrowski]

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 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 explanation of the domain. Confusing.
> > draft.weex.apache.org  would work and 
> > communicate much better.
> Actually, I couldn’t find a way to deploy to draft.weex.apache.org 
> . It seems like Gitpubsub will deploy the 
> asf-site branch of incubator-weex-site 
>  to weex.apache.org 
>  automatically. In order to have more fine control 
> when deploying, we use another domain called https://weex.io 
>  .
>
> If there is a way to deploy website to draft.weex.apache.org 
>  , I’d really like to learn. Any help or 
> advise on the domain issue?
>
>
> > 在 2019年2月1日，19:55，Jan Piotrowski  写道：
> >
> >> 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, maybe we should talk this later in another thread after we 
> >> finished the document work first.
> >
> > Awesome. Who goes ahead and does the first version as a PR? I am happy
> > to jump in when something is up and give feedback on how to improve
> > the list - but you are probably _much_ faster in collecting the
> > relevant repos and giving them a bit of context.
> >
> >> weex.io is based on ...
> >
> > Thanks for the explanation of the domain. Confusing.
> > draft.weex.apache.org would work and communicate much better.
> >
> > You should check with Apache Incubator first if weex.io as a domain
> > will work. Cordova is officially cordova.apache.org although we have
> > cordova.io as a short domain. This might be required for Apache
> > projects - and actually makes sense from a branding perspective!
> >
> > -J
> >
> >
> > Am Fr., 1. Feb. 2019 um 12:19 Uhr schrieb York Shen :
> >>
> >> 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
> >>> different platforms (used by weex-toolkit)" etc). That would give a
> >>> first overview and help to decide which should be migrated when.
> >>
> >> 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, maybe we should talk this later in another thread after we 
> >> finished the document work first.
> >>
> >>
> >>> PS: What is https://weex.io/  based on?
> >> https://weex.io  is based on the draft branch of 
> >> https://github.com/apache/incubator-weex-site 
> >>  , other website like 
> >> http://weex.incubator.apache.org  and 
> >> https://weex-project.io  are based on the master 
> >> branch. We are trying to rewrite weex's website and host it on 
> >> https://weex.io  . Other URL will be redirect to 
> >> https://weex.io  when all the job are done. You may 
> >> think https://weex.io  is in beta stage and will be the 
> >> weex’s website. We would like to publish https://weex.io 
> >>  on Weex conf 2019. Ref this 
> >>  to have a deeper view 
> >> of weex conf 2018.
> >>
> >> Best Regards,
> >> York Shen
> >>
> >> 申远
> >>
> >>> 在 2019年2月1日，18:30，Jan Piotrowski  写道：
> >>>
> >>> 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/apache/cordova-cli` or even `git clone
> >>> https://github.com/apache/cordova-cli` with `npm link`). We also have
> >>> a cronjob that 

Re: Weex, Apache and outside code

[York Shen]

> 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 explanation of the domain. Confusing.
> draft.weex.apache.org  would work and 
> communicate much better.
Actually, I couldn’t find a way to deploy to draft.weex.apache.org 
. It seems like Gitpubsub will deploy the 
asf-site branch of incubator-weex-site 
 to weex.apache.org 
 automatically. In order to have more fine control 
when deploying, we use another domain called https://weex.io  
.

If there is a way to deploy website to draft.weex.apache.org 
 , I’d really like to learn. Any help or advise 
on the domain issue?


> 在 2019年2月1日，19:55，Jan Piotrowski  写道：
> 
>> 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, 
>> maybe we should talk this later in another thread after we finished the 
>> document work first.
> 
> Awesome. Who goes ahead and does the first version as a PR? I am happy
> to jump in when something is up and give feedback on how to improve
> the list - but you are probably _much_ faster in collecting the
> relevant repos and giving them a bit of context.
> 
>> weex.io is based on ...
> 
> Thanks for the explanation of the domain. Confusing.
> draft.weex.apache.org would work and communicate much better.
> 
> You should check with Apache Incubator first if weex.io as a domain
> will work. Cordova is officially cordova.apache.org although we have
> cordova.io as a short domain. This might be required for Apache
> projects - and actually makes sense from a branding perspective!
> 
> -J
> 
> 
> Am Fr., 1. Feb. 2019 um 12:19 Uhr schrieb York Shen :
>> 
>> 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
>>> different platforms (used by weex-toolkit)" etc). That would give a
>>> first overview and help to decide which should be migrated when.
>> 
>> 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, 
>> maybe we should talk this later in another thread after we finished the 
>> document work first.
>> 
>> 
>>> PS: What is https://weex.io/  based on?
>> https://weex.io  is based on the draft branch of 
>> https://github.com/apache/incubator-weex-site 
>>  , other website like 
>> http://weex.incubator.apache.org  and 
>> https://weex-project.io  are based on the master 
>> branch. We are trying to rewrite weex's website and host it on 
>> https://weex.io  . Other URL will be redirect to 
>> https://weex.io  when all the job are done. You may think 
>> https://weex.io  is in beta stage and will be the weex’s 
>> website. We would like to publish https://weex.io  on Weex 
>> conf 2019. Ref this  to 
>> have a deeper view of weex conf 2018.
>> 
>> Best Regards,
>> York Shen
>> 
>> 申远
>> 
>>> 在 2019年2月1日，18:30，Jan Piotrowski  写道：
>>> 
>>> 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/apache/cordova-cli` or even `git clone
>>> https://github.com/apache/cordova-cli` with `npm link`). We also have
>>> a cronjob that creates nightly builds and pushes them to npm, so those
>>> can be tested. That way normal users do use the normal, stable, voted
>>> Apache releases - and maintainers and more active users can still use
>>> the newest stuff. For Apache it is only important that only the
>>> official releases are marketed to users, because only those have the
>>> "seal of approval" from the PMC by voting.
>>> 
>>> Maybe a freat first step would be to 

Re: Weex, Apache and outside code

[Jan Piotrowski]

> 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, 
> maybe we should talk this later in another thread after we finished the 
> document work first.

Awesome. Who goes ahead and does the first version as a PR? I am happy
to jump in when something is up and give feedback on how to improve
the list - but you are probably _much_ faster in collecting the
relevant repos and giving them a bit of context.

> weex.io is based on ...

Thanks for the explanation of the domain. Confusing.
draft.weex.apache.org would work and communicate much better.

You should check with Apache Incubator first if weex.io as a domain
will work. Cordova is officially cordova.apache.org although we have
cordova.io as a short domain. This might be required for Apache
projects - and actually makes sense from a branding perspective!

-J


Am Fr., 1. Feb. 2019 um 12:19 Uhr schrieb York Shen :
>
> 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
> > different platforms (used by weex-toolkit)" etc). That would give a
> > first overview and help to decide which should be migrated when.
>
> 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, 
> maybe we should talk this later in another thread after we finished the 
> document work first.
>
>
> > PS: What is https://weex.io/  based on?
> https://weex.io  is based on the draft branch of 
> https://github.com/apache/incubator-weex-site 
>  , other website like 
> http://weex.incubator.apache.org  and 
> https://weex-project.io  are based on the master 
> branch. We are trying to rewrite weex's website and host it on 
> https://weex.io  . Other URL will be redirect to 
> https://weex.io  when all the job are done. You may think 
> https://weex.io  is in beta stage and will be the weex’s 
> website. We would like to publish https://weex.io  on Weex 
> conf 2019. Ref this  to 
> have a deeper view of weex conf 2018.
>
> Best Regards,
> York Shen
>
> 申远
>
> > 在 2019年2月1日，18:30，Jan Piotrowski  写道：
> >
> > 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/apache/cordova-cli` or even `git clone
> > https://github.com/apache/cordova-cli` with `npm link`). We also have
> > a cronjob that creates nightly builds and pushes them to npm, so those
> > can be tested. That way normal users do use the normal, stable, voted
> > Apache releases - and maintainers and more active users can still use
> > the newest stuff. For Apache it is only important that only the
> > official releases are marketed to users, because only those have the
> > "seal of approval" from the PMC by voting.
> >
> > Maybe a freat first step would be to identify all the repositories
> > 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
> > different platforms (used by weex-toolkit)" etc). That would give a
> > first overview and help to decide which should be migrated when.
> >
> > Thanks to Dan for explaining a bit about _why_ stuff is how it is. As
> > usual, it can be summarized as "it just grew that way" and that is
> > perfectly fine. One of the benefits of being an Apache project is that
> > the rules force a bit of clarity here and make you clean up, so users
> > don't send emails like the one I did. I am happy you are all moving
> > forward here instead of just blocking. I think this could be really
> > great for the Weex project.
> >
> > Best,
> > Jan
> >
> > PS: What is https://weex.io/ based on?
> >
> >
> > Am Fr., 1. Feb. 2019 um 11:13 Uhr schrieb Adam Feng :
> >>
> >> Hi, all
> >>
> >> I suppose it's not just about the workload for 

Re: Weex, Apache and outside code

[York Shen]

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
> different platforms (used by weex-toolkit)" etc). That would give a
> first overview and help to decide which should be migrated when.

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, 
maybe we should talk this later in another thread after we finished the 
document work first.


> PS: What is https://weex.io/  based on?
https://weex.io  is based on the draft branch of 
https://github.com/apache/incubator-weex-site 
 , other website like 
http://weex.incubator.apache.org  and 
https://weex-project.io  are based on the master 
branch. We are trying to rewrite weex's website and host it on https://weex.io 
 . Other URL will be redirect to https://weex.io 
 when all the job are done. You may think https://weex.io 
 is in beta stage and will be the weex’s website. We would 
like to publish https://weex.io  on Weex conf 2019. Ref this 
 to have a deeper view of 
weex conf 2018.

Best Regards,
York Shen

申远

> 在 2019年2月1日，18:30，Jan Piotrowski  写道：
> 
> 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/apache/cordova-cli` or even `git clone
> https://github.com/apache/cordova-cli` with `npm link`). We also have
> a cronjob that creates nightly builds and pushes them to npm, so those
> can be tested. That way normal users do use the normal, stable, voted
> Apache releases - and maintainers and more active users can still use
> the newest stuff. For Apache it is only important that only the
> official releases are marketed to users, because only those have the
> "seal of approval" from the PMC by voting.
> 
> Maybe a freat first step would be to identify all the repositories
> 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
> different platforms (used by weex-toolkit)" etc). That would give a
> first overview and help to decide which should be migrated when.
> 
> Thanks to Dan for explaining a bit about _why_ stuff is how it is. As
> usual, it can be summarized as "it just grew that way" and that is
> perfectly fine. One of the benefits of being an Apache project is that
> the rules force a bit of clarity here and make you clean up, so users
> don't send emails like the one I did. I am happy you are all moving
> forward here instead of just blocking. I think this could be really
> great for the Weex project.
> 
> Best,
> Jan
> 
> PS: What is https://weex.io/ based on?
> 
> 
> Am Fr., 1. Feb. 2019 um 11:13 Uhr schrieb Adam Feng :
>> 
>> 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-depth discussion about whether toolkit 
>> should be a part of Apache Weex， in my opinion,  it should be but is not 
>> yet,  at present Weex focus on “framework” and focus on how to be integrated 
>> into mobile environment ,  which is used without toolkit,  toolkit is a 
>> pluses but not a requirement.
>> 
>> Dan is a strong developer and develop toolkit almost by himself,  but we 
>> need more discussions and interactions between Weex repo and toolkit repo,  
>> not only just a link and a part of document. I’m looking forward to the 
>> “official” toolkit.
>> 
>> Other opinions are really important,  maybe I’m too “cleanliness”.
>> 
>> 
>> 
>> Thanks.
>> Adam Feng
>> 在 2019年2月1日 +0800 PM5:29，Dan ，写道：
>>> 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 

Re: Weex, Apache and outside code

[Jan Piotrowski]

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/apache/cordova-cli` or even `git clone
https://github.com/apache/cordova-cli` with `npm link`). We also have
a cronjob that creates nightly builds and pushes them to npm, so those
can be tested. That way normal users do use the normal, stable, voted
Apache releases - and maintainers and more active users can still use
the newest stuff. For Apache it is only important that only the
official releases are marketed to users, because only those have the
"seal of approval" from the PMC by voting.

Maybe a freat first step would be to identify all the repositories
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
different platforms (used by weex-toolkit)" etc). That would give a
first overview and help to decide which should be migrated when.

Thanks to Dan for explaining a bit about _why_ stuff is how it is. As
usual, it can be summarized as "it just grew that way" and that is
perfectly fine. One of the benefits of being an Apache project is that
the rules force a bit of clarity here and make you clean up, so users
don't send emails like the one I did. I am happy you are all moving
forward here instead of just blocking. I think this could be really
great for the Weex project.

Best,
Jan

PS: What is https://weex.io/ based on?


Am Fr., 1. Feb. 2019 um 11:13 Uhr schrieb Adam Feng :
>
> 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-depth discussion about whether toolkit should 
> be a part of Apache Weex， in my opinion,  it should be but is not yet,  at 
> present Weex focus on “framework” and focus on how to be integrated into 
> mobile environment ,  which is used without toolkit,  toolkit is a pluses but 
> not a requirement.
>
> Dan is a strong developer and develop toolkit almost by himself,  but we need 
> more discussions and interactions between Weex repo and toolkit repo,  not 
> only just a link and a part of document. I’m looking forward to the 
> “official” toolkit.
>
>  Other opinions are really important,  maybe I’m too “cleanliness”.
>
>
>
> Thanks.
> Adam Feng
> 在 2019年2月1日 +0800 PM5:29，Dan ，写道：
> > 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 historical issues to
> > continue to track, the new repo will start from 0 (that's no bad, but a big
> > change).
> > 3. I need to re-adjust my code and follow the apache approach, which also
> > has a certain cost for me, and now I was the only one who works on the
> > weex toolchain.
> >
> > Maybe this issue can be resolved, but I'm not sure how much time I need to
> > complete this thing.
> >
> > I look forward to more comments and discussions to get this matter going.
> >
> > Thanks.
> > Dan
> >
> > Myrle Krantz  于2019年2月1日周五 下午4:32写道：
> >
> > > 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
> > > > the user's usage from the tool, this may not be allowed by apache, I
> > > > prefer
> > > > to develop these tools as a third-party developer, it should be ok to
> > > > remind users in the documentation that it's not part of Apache
> > >
> > >
> > > This is a common misconception. Code does not have to be complete to be
> > > developed at Apache. Rapid prototyping and user feedback are important
> > > parts of all software development whether at Apache or elsewhere. For an
> > > example of a project currently doing this in incubation see PLC4X.
> > >
> > > Can you explain in more detail what makes development within an Apache
> > > GitHub repository difficult for you? Perhaps it’s an issue that can be
> > > resolved?
> > >
> > > It’s important that the Weex PPMC resolves this. A project which is split
> > > in this way cannot be effectively governed by the Weex PMC. The governance
> > > imbalance 

Re: Weex, Apache and outside code

[Adam Feng]

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-depth discussion about whether toolkit should 
be a part of Apache Weex， in my opinion,  it should be but is not yet,  at 
present Weex focus on “framework” and focus on how to be integrated into mobile 
environment ,  which is used without toolkit,  toolkit is a pluses but not a 
requirement.

Dan is a strong developer and develop toolkit almost by himself,  but we need 
more discussions and interactions between Weex repo and toolkit repo,  not only 
just a link and a part of document. I’m looking forward to the “official” 
toolkit.

 Other opinions are really important,  maybe I’m too “cleanliness”.



Thanks.
Adam Feng
在 2019年2月1日 +0800 PM5:29，Dan ，写道：
> 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 historical issues to
> continue to track, the new repo will start from 0 (that's no bad, but a big
> change).
> 3. I need to re-adjust my code and follow the apache approach, which also
> has a certain cost for me, and now I was the only one who works on the
> weex toolchain.
>
> Maybe this issue can be resolved, but I'm not sure how much time I need to
> complete this thing.
>
> I look forward to more comments and discussions to get this matter going.
>
> Thanks.
> Dan
>
> Myrle Krantz  于2019年2月1日周五 下午4:32写道：
>
> > 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
> > > the user's usage from the tool, this may not be allowed by apache, I
> > > prefer
> > > to develop these tools as a third-party developer, it should be ok to
> > > remind users in the documentation that it's not part of Apache
> >
> >
> > This is a common misconception. Code does not have to be complete to be
> > developed at Apache. Rapid prototyping and user feedback are important
> > parts of all software development whether at Apache or elsewhere. For an
> > example of a project currently doing this in incubation see PLC4X.
> >
> > Can you explain in more detail what makes development within an Apache
> > GitHub repository difficult for you? Perhaps it’s an issue that can be
> > resolved?
> >
> > It’s important that the Weex PPMC resolves this. A project which is split
> > in this way cannot be effectively governed by the Weex PMC. The governance
> > imbalance can cause distortions in the code architecture. More important:
> > it can damage the community.
> >
> > Best Regards,
> > Myrle
> >
> > (I speak from experience: I made exactly this mistake when I first became
> > involved with Apache.)
> >

Re: Weex, Apache and outside code

[Dan]

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],  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:44 PM York Shen  wrote:
> >
> > According to my understanding and what Justin Mclean wrote
> https://lists.apache.org/thread.html/5c5a75f00d78211f75e10d17bfeb05bc7b0b4f9e8416fa602b0ebb54@%3Cgeneral.incubator.apache.org%3E
> <
> https://lists.apache.org/thread.html/5c5a75f00d78211f75e10d17bfeb05bc7b0b4f9e8416fa602b0ebb54@%3Cgeneral.incubator.apache.org%3E>
> , any format of unofficial release is forbidden, all release must be voted
> before we publish it.
> >
> > Correct me if I am wrong.
> >
> >
> > Best Regards,
> > York Shen
> >
> > 申远
> >
> > > 在 2019年2月1日，16:27，Willem Jiang  写道：
> > >
> > > 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 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 this project, the project
> was
> > >> designed to support package integration of multiple command line
> tools, and
> > >> to manage mappings between them through xtoolkit module, the idea is
> good,
> > >> but too many projects are scattered into the various git repo, such as
> > >> weex-debugger, weex-pack and so on.
> > >>
> > >> On the weex-toolkit@2.0,  I'm split each function module into
> separate
> > >> parts, and manage multiple separate releases in the repository via
> Lerna,
> > >> after that you can find all the module you want in the weex-toolkit
> repo
> > >> (currently in the alpha process), you can enjoy it follow the document
> > >> here: https://weex.io/tools/toolkit.html, it also supports the
> thrid-part
> > >> extensions, the document will be further supplemented
> > >>
> > >>> 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
> > >> the user's usage from the tool, this may not be allowed by apache, I
> prefer
> > >> to develop these tools as a third-party developer, it should be ok to
> > >> remind users in the documentation that it's not part of Apache Weex.
> > >>
> > >>> why the module called toolkit but not cli?
> > >>
> > >> This is the name defined by the previous module creator. I personally
> think
> > >> it might be better to call it weex-cli. Maybe I will consider
> renaming the
> > >> module soon.
> > >>
> > >> Thanks
> > >> Dan
> > >>
> > >> Jan Piotrowski  于2019年2月1日周五 上午3:13写道：
> > >>
> > >>> (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 website for users from China
> to have
> > >>> the right access. You can choose whatever you want, as the three
> websites
> > >>> are all the same.
> > >>>
> > >>> Thanks for that explanation.
> > >>>
> > >>> In my opinion (and maybe Apache guidelines?) there should only be
> _one_
> > >>> domain per Apache project, so you know you can trust the content of
> that
> > >>> domain. You (the team) should probably decide which one of the two
> > >>> apache.org domains you should use (and can use per incubation
> rules!),
> > >>> and redirect the other one. Otherwise both Google and users can be
> > >>> confused.
> > >>> For the non-Apache mirrors for Chinese users you could maybe add a
> banner
> > >>> that this is a mirror of *.apache.org for Chinese users and link to
> it
> > >>> from somewhere _on_ the site so it is discoverable? Additionally
> maybe
> > >>> no-index the domain, so Google doesn't list them? Then it is all
> > >>> transparent and there is no confusion.
> > >>>
> >  The repo for weex is https://github.com/apache/incubator-weex, from
> > >>> where weex community generates apache release.
> >  All the other repos is not officially belong to 

Re: Weex, Apache and outside code

[Willem Jiang]

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:44 PM York Shen  wrote:
>
> According to my understanding and what Justin Mclean wrote 
> https://lists.apache.org/thread.html/5c5a75f00d78211f75e10d17bfeb05bc7b0b4f9e8416fa602b0ebb54@%3Cgeneral.incubator.apache.org%3E
>  
> 
>  , any format of unofficial release is forbidden, all release must be voted 
> before we publish it.
>
> Correct me if I am wrong.
>
>
> Best Regards,
> York Shen
>
> 申远
>
> > 在 2019年2月1日，16:27，Willem Jiang  写道：
> >
> > 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 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 this project, the project was
> >> designed to support package integration of multiple command line tools, and
> >> to manage mappings between them through xtoolkit module, the idea is good,
> >> but too many projects are scattered into the various git repo, such as
> >> weex-debugger, weex-pack and so on.
> >>
> >> On the weex-toolkit@2.0,  I'm split each function module into separate
> >> parts, and manage multiple separate releases in the repository via Lerna,
> >> after that you can find all the module you want in the weex-toolkit repo
> >> (currently in the alpha process), you can enjoy it follow the document
> >> here: https://weex.io/tools/toolkit.html, it also supports the thrid-part
> >> extensions, the document will be further supplemented
> >>
> >>> 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
> >> the user's usage from the tool, this may not be allowed by apache, I prefer
> >> to develop these tools as a third-party developer, it should be ok to
> >> remind users in the documentation that it's not part of Apache Weex.
> >>
> >>> why the module called toolkit but not cli?
> >>
> >> This is the name defined by the previous module creator. I personally think
> >> it might be better to call it weex-cli. Maybe I will consider renaming the
> >> module soon.
> >>
> >> Thanks
> >> Dan
> >>
> >> Jan Piotrowski  于2019年2月1日周五 上午3:13写道：
> >>
> >>> (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 website for users from China to 
> >>> have
> >>> the right access. You can choose whatever you want, as the three websites
> >>> are all the same.
> >>>
> >>> Thanks for that explanation.
> >>>
> >>> In my opinion (and maybe Apache guidelines?) there should only be _one_
> >>> domain per Apache project, so you know you can trust the content of that
> >>> domain. You (the team) should probably decide which one of the two
> >>> apache.org domains you should use (and can use per incubation rules!),
> >>> and redirect the other one. Otherwise both Google and users can be
> >>> confused.
> >>> For the non-Apache mirrors for Chinese users you could maybe add a banner
> >>> that this is a mirror of *.apache.org for Chinese users and link to it
> >>> from somewhere _on_ the site so it is discoverable? Additionally maybe
> >>> no-index the domain, so Google doesn't list them? Then it is all
> >>> transparent and there is no confusion.
> >>>
>  The repo for weex is https://github.com/apache/incubator-weex, from
> >>> where weex community generates apache release.
>  All the other repos is not officially belong to weex, though some of are
> >>> useful tools for debug, development purpose. They are just useful tools,
> >>> one can using weex framework without these tools with no problem. I will
> >>> consider these tools as useful plugins, and there are perhaps tens of such
> >>> plugins, so they are not under Apache repositories.
>  I will ask the authors of  https://github.com/weexteam/xtoolkit and
> >>> https://github.com/weexteam/weex-pack, not sure whether there is a
> 

Re: Weex, Apache and outside code

[Dan]

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 historical issues to
continue to track, the new repo will start from 0 (that's no bad, but a big
change).
3. I need to re-adjust my code and follow the apache approach, which also
has a certain cost for me, and now I was the only one who works on the
weex toolchain.

Maybe this issue can be resolved, but I'm not sure how much time I need to
complete this thing.

I look forward to more comments and discussions to get this matter going.

Thanks.
Dan

Myrle Krantz  于2019年2月1日周五 下午4:32写道：

> 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
>> the user's usage from the tool, this may not be allowed by apache, I
>> prefer
>> to develop these tools as a third-party developer, it should be ok to
>> remind users in the documentation that it's not part of Apache
>
>
> This is a common misconception. Code does not have to be complete to be
> developed at Apache.  Rapid prototyping and user feedback are important
> parts of all software development whether at Apache or elsewhere. For an
> example of a project currently doing this in incubation see PLC4X.
>
> Can you explain in more detail what makes development within an Apache
> GitHub repository difficult for you? Perhaps it’s an issue that can be
> resolved?
>
> It’s important that the Weex PPMC resolves this. A project which is split
> in this way cannot be effectively governed by the Weex PMC.  The governance
> imbalance can cause distortions in the code architecture. More important:
> it can damage the community.
>
> Best Regards,
> Myrle
>
> (I speak from experience: I made exactly this mistake when I first became
> involved with Apache.)
>

Re: Weex, Apache and outside code

[York Shen]

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

 , any format of unofficial release is forbidden, all release must be voted 
before we publish it.

Correct me if I am wrong.


Best Regards,
York Shen

申远

> 在 2019年2月1日，16:27，Willem Jiang  写道：
> 
> 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 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 this project, the project was
>> designed to support package integration of multiple command line tools, and
>> to manage mappings between them through xtoolkit module, the idea is good,
>> but too many projects are scattered into the various git repo, such as
>> weex-debugger, weex-pack and so on.
>> 
>> On the weex-toolkit@2.0,  I'm split each function module into separate
>> parts, and manage multiple separate releases in the repository via Lerna,
>> after that you can find all the module you want in the weex-toolkit repo
>> (currently in the alpha process), you can enjoy it follow the document
>> here: https://weex.io/tools/toolkit.html, it also supports the thrid-part
>> extensions, the document will be further supplemented
>> 
>>> 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
>> the user's usage from the tool, this may not be allowed by apache, I prefer
>> to develop these tools as a third-party developer, it should be ok to
>> remind users in the documentation that it's not part of Apache Weex.
>> 
>>> why the module called toolkit but not cli?
>> 
>> This is the name defined by the previous module creator. I personally think
>> it might be better to call it weex-cli. Maybe I will consider renaming the
>> module soon.
>> 
>> Thanks
>> Dan
>> 
>> Jan Piotrowski  于2019年2月1日周五 上午3:13写道：
>> 
>>> (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 website for users from China to have
>>> the right access. You can choose whatever you want, as the three websites
>>> are all the same.
>>> 
>>> Thanks for that explanation.
>>> 
>>> In my opinion (and maybe Apache guidelines?) there should only be _one_
>>> domain per Apache project, so you know you can trust the content of that
>>> domain. You (the team) should probably decide which one of the two
>>> apache.org domains you should use (and can use per incubation rules!),
>>> and redirect the other one. Otherwise both Google and users can be
>>> confused.
>>> For the non-Apache mirrors for Chinese users you could maybe add a banner
>>> that this is a mirror of *.apache.org for Chinese users and link to it
>>> from somewhere _on_ the site so it is discoverable? Additionally maybe
>>> no-index the domain, so Google doesn't list them? Then it is all
>>> transparent and there is no confusion.
>>> 
 The repo for weex is https://github.com/apache/incubator-weex, from
>>> where weex community generates apache release.
 All the other repos is not officially belong to weex, though some of are
>>> useful tools for debug, development purpose. They are just useful tools,
>>> one can using weex framework without these tools with no problem. I will
>>> consider these tools as useful plugins, and there are perhaps tens of such
>>> plugins, so they are not under Apache repositories.
 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 into Apache Weex  umbrella
>>> officially.
>>> 
>>> The documentation and guides made them sound very much a part of Weex - so
>>> if in any way possible you should move _all_ the tools, plugins,
>>> playground, and other pieces that are used in the documentation and
>>> examples to Apache repositories (PMC members and committers can create
>>> additional repositories at https://gitbox.apache.org/setup/newrepo.html).
>>> 
>>> If you can't transfer any of the code 

Re: Weex, Apache and outside code

[Myrle Krantz]

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
> the user's usage from the tool, this may not be allowed by apache, I prefer
> to develop these tools as a third-party developer, it should be ok to
> remind users in the documentation that it's not part of Apache


This is a common misconception. Code does not have to be complete to be
developed at Apache.  Rapid prototyping and user feedback are important
parts of all software development whether at Apache or elsewhere. For an
example of a project currently doing this in incubation see PLC4X.

Can you explain in more detail what makes development within an Apache
GitHub repository difficult for you? Perhaps it’s an issue that can be
resolved?

It’s important that the Weex PPMC resolves this. A project which is split
in this way cannot be effectively governed by the Weex PMC.  The governance
imbalance can cause distortions in the code architecture. More important:
it can damage the community.

Best Regards,
Myrle

(I speak from experience: I made exactly this mistake when I first became
involved with Apache.)

Re: Weex, Apache and outside code

[Willem Jiang]

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 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 this project, the project was
> designed to support package integration of multiple command line tools, and
> to manage mappings between them through xtoolkit module, the idea is good,
> but too many projects are scattered into the various git repo, such as
> weex-debugger, weex-pack and so on.
>
> On the weex-toolkit@2.0,  I'm split each function module into separate
> parts, and manage multiple separate releases in the repository via Lerna,
> after that you can find all the module you want in the weex-toolkit repo
> (currently in the alpha process), you can enjoy it follow the document
> here: https://weex.io/tools/toolkit.html, it also supports the thrid-part
> extensions, the document will be further supplemented
>
> > 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
> the user's usage from the tool, this may not be allowed by apache, I prefer
> to develop these tools as a third-party developer, it should be ok to
> remind users in the documentation that it's not part of Apache Weex.
>
> > why the module called toolkit but not cli?
>
> This is the name defined by the previous module creator. I personally think
> it might be better to call it weex-cli. Maybe I will consider renaming the
> module soon.
>
> Thanks
> Dan
>
> Jan Piotrowski  于2019年2月1日周五 上午3:13写道：
>
> > (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 website for users from China to have
> > the right access. You can choose whatever you want, as the three websites
> > are all the same.
> >
> > Thanks for that explanation.
> >
> > In my opinion (and maybe Apache guidelines?) there should only be _one_
> > domain per Apache project, so you know you can trust the content of that
> > domain. You (the team) should probably decide which one of the two
> > apache.org domains you should use (and can use per incubation rules!),
> > and redirect the other one. Otherwise both Google and users can be
> > confused.
> > For the non-Apache mirrors for Chinese users you could maybe add a banner
> > that this is a mirror of *.apache.org for Chinese users and link to it
> > from somewhere _on_ the site so it is discoverable? Additionally maybe
> > no-index the domain, so Google doesn't list them? Then it is all
> > transparent and there is no confusion.
> >
> > > The repo for weex is https://github.com/apache/incubator-weex, from
> > where weex community generates apache release.
> > > All the other repos is not officially belong to weex, though some of are
> > useful tools for debug, development purpose. They are just useful tools,
> > one can using weex framework without these tools with no problem. I will
> > consider these tools as useful plugins, and there are perhaps tens of such
> > plugins, so they are not under Apache repositories.
> > > 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 into Apache Weex  umbrella
> > officially.
> >
> > The documentation and guides made them sound very much a part of Weex - so
> > if in any way possible you should move _all_ the tools, plugins,
> > playground, and other pieces that are used in the documentation and
> > examples to Apache repositories (PMC members and committers can create
> > additional repositories at https://gitbox.apache.org/setup/newrepo.html).
> >
> > If you can't transfer any of the code for licence reasons, it should be
> > clearly documented in the documentation when you advise users to use it
> > that this is not part of Apache Weex, but a user space plugin or project.
> >
> > From a user standpoint, if I use an Apache project I want to know that I
> > can trust all the project code. With parts of the source code being
> > downloaded (especially if not via npm!) from some other repository,
> > installed and executed, I can't do that. (Additionally there have to be
> > release processes with votes etc. that make sure that what gets published
> > on npm actually matches 

Re: Weex, Apache and outside code

[Dan]

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 this project, the project was
designed to support package integration of multiple command line tools, and
to manage mappings between them through xtoolkit module, the idea is good,
but too many projects are scattered into the various git repo, such as
weex-debugger, weex-pack and so on.

On the weex-toolkit@2.0,  I'm split each function module into separate
parts, and manage multiple separate releases in the repository via Lerna,
after that you can find all the module you want in the weex-toolkit repo
(currently in the alpha process), you can enjoy it follow the document
here: https://weex.io/tools/toolkit.html, it also supports the thrid-part
extensions, the document will be further supplemented

> 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
the user's usage from the tool, this may not be allowed by apache, I prefer
to develop these tools as a third-party developer, it should be ok to
remind users in the documentation that it's not part of Apache Weex.

> why the module called toolkit but not cli?

This is the name defined by the previous module creator. I personally think
it might be better to call it weex-cli. Maybe I will consider renaming the
module soon.

Thanks
Dan

Jan Piotrowski  于2019年2月1日周五 上午3:13写道：

> (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 website for users from China to have
> the right access. You can choose whatever you want, as the three websites
> are all the same.
>
> Thanks for that explanation.
>
> In my opinion (and maybe Apache guidelines?) there should only be _one_
> domain per Apache project, so you know you can trust the content of that
> domain. You (the team) should probably decide which one of the two
> apache.org domains you should use (and can use per incubation rules!),
> and redirect the other one. Otherwise both Google and users can be
> confused.
> For the non-Apache mirrors for Chinese users you could maybe add a banner
> that this is a mirror of *.apache.org for Chinese users and link to it
> from somewhere _on_ the site so it is discoverable? Additionally maybe
> no-index the domain, so Google doesn't list them? Then it is all
> transparent and there is no confusion.
>
> > The repo for weex is https://github.com/apache/incubator-weex, from
> where weex community generates apache release.
> > All the other repos is not officially belong to weex, though some of are
> useful tools for debug, development purpose. They are just useful tools,
> one can using weex framework without these tools with no problem. I will
> consider these tools as useful plugins, and there are perhaps tens of such
> plugins, so they are not under Apache repositories.
> > 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 into Apache Weex  umbrella
> officially.
>
> The documentation and guides made them sound very much a part of Weex - so
> if in any way possible you should move _all_ the tools, plugins,
> playground, and other pieces that are used in the documentation and
> examples to Apache repositories (PMC members and committers can create
> additional repositories at https://gitbox.apache.org/setup/newrepo.html).
>
> If you can't transfer any of the code for licence reasons, it should be
> clearly documented in the documentation when you advise users to use it
> that this is not part of Apache Weex, but a user space plugin or project.
>
> From a user standpoint, if I use an Apache project I want to know that I
> can trust all the project code. With parts of the source code being
> downloaded (especially if not via npm!) from some other repository,
> installed and executed, I can't do that. (Additionally there have to be
> release processes with votes etc. that make sure that what gets published
> on npm actually matches what is in the repository!) Otherwise the Apache
> repository is just a front for untrusted code that belongs to the project,
> but doesn't follow the Apache ways.
>
> If you move all the repositories to Apache, it will be much easier to
> clean everything up and make sure there is no duplication of documentation,
> the guides and also the software only uses tools that belong to Apache Weex.
>
> This maybe all sounds a bit harsh now, and 

Re: Weex, Apache and outside code

[Jan Piotrowski]

(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 website for users from China to have the right 
> access. You can choose whatever you want, as the three websites are all the 
> same.

Thanks for that explanation. 

In my opinion (and maybe Apache guidelines?) there should only be _one_ domain 
per Apache project, so you know you can trust the content of that domain. You 
(the team) should probably decide which one of the two apache.org domains you 
should use (and can use per incubation rules!), and redirect the other one. 
Otherwise both Google and users can be confused. 
For the non-Apache mirrors for Chinese users you could maybe add a banner that 
this is a mirror of *.apache.org for Chinese users and link to it from 
somewhere _on_ the site so it is discoverable? Additionally maybe no-index the 
domain, so Google doesn't list them? Then it is all transparent and there is no 
confusion.

> The repo for weex is https://github.com/apache/incubator-weex, from where 
> weex community generates apache release.
> All the other repos is not officially belong to weex, though some of are 
> useful tools for debug, development purpose. They are just useful tools, one 
> can using weex framework without these tools with no problem. I will consider 
> these tools as useful plugins, and there are perhaps tens of such plugins, so 
> they are not under Apache repositories.
> 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 into Apache Weex  umbrella officially.

The documentation and guides made them sound very much a part of Weex - so if 
in any way possible you should move _all_ the tools, plugins, playground, and 
other pieces that are used in the documentation and examples to Apache 
repositories (PMC members and committers can create additional repositories at 
https://gitbox.apache.org/setup/newrepo.html).

If you can't transfer any of the code for licence reasons, it should be clearly 
documented in the documentation when you advise users to use it that this is 
not part of Apache Weex, but a user space plugin or project.

>From a user standpoint, if I use an Apache project I want to know that I can 
>trust all the project code. With parts of the source code being downloaded 
>(especially if not via npm!) from some other repository, installed and 
>executed, I can't do that. (Additionally there have to be release processes 
>with votes etc. that make sure that what gets published on npm actually 
>matches what is in the repository!) Otherwise the Apache repository is just a 
>front for untrusted code that belongs to the project, but doesn't follow the 
>Apache ways.

If you move all the repositories to Apache, it will be much easier to clean 
everything up and make sure there is no duplication of documentation, the 
guides and also the software only uses tools that belong to Apache Weex.

This maybe all sounds a bit harsh now, and this was definitely not my goal. I 
was excited to play around with Weex, but it was a real pain to understand what 
was going on.

Best,
Jan



On 2019/01/31 13:25:57, York Shen  wrote: 
> 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 into 
> Apache Weex  umbrella officially.
> 
> Best Regards,
> York Shen
> 
> 申远
> 
> > 在 2019年1月31日，21:22，York Shen  写道：
> > 
> > 
> > 
> > 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 Apache Weex.
> >> 
> >> Willem Jiang
> >> 
> >> Twitter: willemjiang
> >> Weibo: 姜宁willem
> >> 
> >> On Thu, Jan 31, 2019 at 8:59 PM York Shen  >> > wrote:
> >>> 
> >>> 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 

Re: Weex, Apache and outside code

[York Shen]

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 Apache Weex.
> 
> Willem Jiang
> 
> Twitter: willemjiang
> Weibo: 姜宁willem
> 
> On Thu, Jan 31, 2019 at 8:59 PM York Shen  wrote:
>> 
>> 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 
>> generates apache release.
>> All the other repos is not officially belong to weex, though some of are 
>> useful tools for debug, development purpose. They are just useful tools, one 
>> can using weex framework without these tools with no problem. I will 
>> consider these tools as useful plugins, and there are perhaps tens of such 
>> plugins, so they are not under Apache repositories.
>> 
>> 
>> 2. All website you listed is coming 
>> https://github.com/apache/incubator-weex-site 
>>  . As there are many Weex 
>> users coming from China and the GFW is a huge problem for them, so we create 
>> several website for users from China to have the right access. You can 
>> choose whatever you want, as the three websites are all the same.
>> 
>> 3. Feel free to ask anything about weex, I am glad to answer these questions.
>> 
>> Best Regards,
>> York Shen
>> 
>> 申远
>> 
>>> 在 2019年1月31日，20:31，Jan Piotrowski  写道：
>>> 
>>> 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
>>> left me a bit confused what is going on, and where what code is coming from
>>> and what it is used for.
>>> 
>>> There are only 2 Apache (Incubator) repositories for Weex:
>>> https://github.com/apache/incubator-weex
>>> https://github.com/apache/incubator-weex-site
>>> 
>>> The main repository https://github.com/apache/incubator-weex quickly links
>>> me to https://github.com/weexteam/weex-toolkit which seems to be a CLI
>>> (toolkit = CLI?) to create and build Weex based apps. Its npm dependencies
>>> are pretty light, but it seems to download many more code via
>>> https://github.com/weexteam/xtoolkit anyway and cache it with some custom
>>> mechanism, like e.g. https://github.com/weexteam/weex-pack that seems to
>>> contain the code to create, run, build native apps.
>>> 
>>> Is this redirection and inclusion of outside code intentional?
>>> Is this temporary or meant to be permanent?
>>> 
>>> There are also many more repositories at https://github.com/weexteam that I
>>> have no idea what they are used for.
>>> 
>>> (That being said, the guide at http://weex.apache.org/guide/ is really good
>>> and gives a very clear picture what steps need to be taken to developer a
>>> Weex app - it just all breaks down if you look behind the curtain and try
>>> to understand where all the code comes from and what is going on a level
>>> deeper.)
>>> 
>>> The website also seems to be available under several domains:
>>> http://weex.incubator.apache.org
>>> https://weex.apache.org
>>> https://weex-project.io
>>> Do these all host the same content from
>>> https://github.com/apache/incubator-weex-site? Or are those different
>>> things?
>>> 
>>> Best,
>>> Jan
>> 

Re: Weex, Apache and outside code

[York Shen]

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 into Apache 
Weex  umbrella officially.

Best Regards,
York Shen

申远

> 在 2019年1月31日，21:22，York Shen  写道：
> 
> 
> 
> 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 Apache Weex.
>> 
>> Willem Jiang
>> 
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>> 
>> On Thu, Jan 31, 2019 at 8:59 PM York Shen > > wrote:
>>> 
>>> 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 
>>> generates apache release.
>>> All the other repos is not officially belong to weex, though some of are 
>>> useful tools for debug, development purpose. They are just useful tools, 
>>> one can using weex framework without these tools with no problem. I will 
>>> consider these tools as useful plugins, and there are perhaps tens of such 
>>> plugins, so they are not under Apache repositories.
>>> 
>>> 
>>> 2. All website you listed is coming 
>>> https://github.com/apache/incubator-weex-site 
>>>  
>>> >> > . As there are many Weex 
>>> users coming from China and the GFW is a huge problem for them, so we 
>>> create several website for users from China to have the right access. You 
>>> can choose whatever you want, as the three websites are all the same.
>>> 
>>> 3. Feel free to ask anything about weex, I am glad to answer these 
>>> questions.
>>> 
>>> Best Regards,
>>> York Shen
>>> 
>>> 申远
>>> 
 在 2019年1月31日，20:31，Jan Piotrowski >>> > 写道：
 
 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
 left me a bit confused what is going on, and where what code is coming from
 and what it is used for.
 
 There are only 2 Apache (Incubator) repositories for Weex:
 https://github.com/apache/incubator-weex 
 
 https://github.com/apache/incubator-weex-site
 
 The main repository https://github.com/apache/incubator-weex quickly links
 me to https://github.com/weexteam/weex-toolkit which seems to be a CLI
 (toolkit = CLI?) to create and build Weex based apps. Its npm dependencies
 are pretty light, but it seems to download many more code via
 https://github.com/weexteam/xtoolkit anyway and cache it with some custom
 mechanism, like e.g. https://github.com/weexteam/weex-pack that seems to
 contain the code to create, run, build native apps.
 
 Is this redirection and inclusion of outside code intentional?
 Is this temporary or meant to be permanent?
 
 There are also many more repositories at https://github.com/weexteam that I
 have no idea what they are used for.
 
 (That being said, the guide at http://weex.apache.org/guide/ is really good
 and gives a very clear picture what steps need to be taken to developer a
 Weex app - it just all breaks down if you look behind the curtain and try
 to understand where all the code comes from and what is going on a level
 deeper.)
 
 The website also seems to be available under several domains:
 http://weex.incubator.apache.org
 https://weex.apache.org
 https://weex-project.io
 Do these all host the same content from
 https://github.com/apache/incubator-weex-site? Or are those different
 things?
 
 Best,
 Jan
>>> 
> 

Re: Weex, Apache and outside code

[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 Apache Weex.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Thu, Jan 31, 2019 at 8:59 PM York Shen  wrote:
>
> 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 
> generates apache release.
> All the other repos is not officially belong to weex, though some of are 
> useful tools for debug, development purpose. They are just useful tools, one 
> can using weex framework without these tools with no problem. I will consider 
> these tools as useful plugins, and there are perhaps tens of such plugins, so 
> they are not under Apache repositories.
>
>
> 2. All website you listed is coming 
> https://github.com/apache/incubator-weex-site 
>  . As there are many Weex 
> users coming from China and the GFW is a huge problem for them, so we create 
> several website for users from China to have the right access. You can choose 
> whatever you want, as the three websites are all the same.
>
> 3. Feel free to ask anything about weex, I am glad to answer these questions.
>
> Best Regards,
> York Shen
>
> 申远
>
> > 在 2019年1月31日，20:31，Jan Piotrowski  写道：
> >
> > 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
> > left me a bit confused what is going on, and where what code is coming from
> > and what it is used for.
> >
> > There are only 2 Apache (Incubator) repositories for Weex:
> > https://github.com/apache/incubator-weex
> > https://github.com/apache/incubator-weex-site
> >
> > The main repository https://github.com/apache/incubator-weex quickly links
> > me to https://github.com/weexteam/weex-toolkit which seems to be a CLI
> > (toolkit = CLI?) to create and build Weex based apps. Its npm dependencies
> > are pretty light, but it seems to download many more code via
> > https://github.com/weexteam/xtoolkit anyway and cache it with some custom
> > mechanism, like e.g. https://github.com/weexteam/weex-pack that seems to
> > contain the code to create, run, build native apps.
> >
> > Is this redirection and inclusion of outside code intentional?
> > Is this temporary or meant to be permanent?
> >
> > There are also many more repositories at https://github.com/weexteam that I
> > have no idea what they are used for.
> >
> > (That being said, the guide at http://weex.apache.org/guide/ is really good
> > and gives a very clear picture what steps need to be taken to developer a
> > Weex app - it just all breaks down if you look behind the curtain and try
> > to understand where all the code comes from and what is going on a level
> > deeper.)
> >
> > The website also seems to be available under several domains:
> > http://weex.incubator.apache.org
> > https://weex.apache.org
> > https://weex-project.io
> > Do these all host the same content from
> > https://github.com/apache/incubator-weex-site? Or are those different
> > things?
> >
> > Best,
> > Jan
>

Re: Weex, Apache and outside code

[York Shen]

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 generates 
apache release.
All the other repos is not officially belong to weex, though some of are useful 
tools for debug, development purpose. They are just useful tools, one can using 
weex framework without these tools with no problem. I will consider these tools 
as useful plugins, and there are perhaps tens of such plugins, so they are not 
under Apache repositories.


2. All website you listed is coming 
https://github.com/apache/incubator-weex-site 
 . As there are many Weex users 
coming from China and the GFW is a huge problem for them, so we create several 
website for users from China to have the right access. You can choose whatever 
you want, as the three websites are all the same.

3. Feel free to ask anything about weex, I am glad to answer these questions.

Best Regards,
York Shen

申远

> 在 2019年1月31日，20:31，Jan Piotrowski  写道：
> 
> 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
> left me a bit confused what is going on, and where what code is coming from
> and what it is used for.
> 
> There are only 2 Apache (Incubator) repositories for Weex:
> https://github.com/apache/incubator-weex
> https://github.com/apache/incubator-weex-site
> 
> The main repository https://github.com/apache/incubator-weex quickly links
> me to https://github.com/weexteam/weex-toolkit which seems to be a CLI
> (toolkit = CLI?) to create and build Weex based apps. Its npm dependencies
> are pretty light, but it seems to download many more code via
> https://github.com/weexteam/xtoolkit anyway and cache it with some custom
> mechanism, like e.g. https://github.com/weexteam/weex-pack that seems to
> contain the code to create, run, build native apps.
> 
> Is this redirection and inclusion of outside code intentional?
> Is this temporary or meant to be permanent?
> 
> There are also many more repositories at https://github.com/weexteam that I
> have no idea what they are used for.
> 
> (That being said, the guide at http://weex.apache.org/guide/ is really good
> and gives a very clear picture what steps need to be taken to developer a
> Weex app - it just all breaks down if you look behind the curtain and try
> to understand where all the code comes from and what is going on a level
> deeper.)
> 
> The website also seems to be available under several domains:
> http://weex.incubator.apache.org
> https://weex.apache.org
> https://weex-project.io
> Do these all host the same content from
> https://github.com/apache/incubator-weex-site? Or are those different
> things?
> 
> Best,
> Jan

Weex, Apache and outside code

[Jan Piotrowski]

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
left me a bit confused what is going on, and where what code is coming from
and what it is used for.

There are only 2 Apache (Incubator) repositories for Weex:
https://github.com/apache/incubator-weex
https://github.com/apache/incubator-weex-site

The main repository https://github.com/apache/incubator-weex quickly links
me to https://github.com/weexteam/weex-toolkit which seems to be a CLI
(toolkit = CLI?) to create and build Weex based apps. Its npm dependencies
are pretty light, but it seems to download many more code via
https://github.com/weexteam/xtoolkit anyway and cache it with some custom
mechanism, like e.g. https://github.com/weexteam/weex-pack that seems to
contain the code to create, run, build native apps.

Is this redirection and inclusion of outside code intentional?
Is this temporary or meant to be permanent?

There are also many more repositories at https://github.com/weexteam that I
have no idea what they are used for.

(That being said, the guide at http://weex.apache.org/guide/ is really good
and gives a very clear picture what steps need to be taken to developer a
Weex app - it just all breaks down if you look behind the curtain and try
to understand where all the code comes from and what is going on a level
deeper.)

The website also seems to be available under several domains:
http://weex.incubator.apache.org
https://weex.apache.org
https://weex-project.io
Do these all host the same content from
https://github.com/apache/incubator-weex-site? Or are those different
things?

Best,
Jan