rademark of ASF and
> using weex in domain domain name also violate the legal right of ASF.*
>
> Best Regards,
> YorkShen
>
> 申远
>
>
> Jan Piotrowski 于2019年12月4日周三 上午4:29写道：
>
> > I already sent somthing similar in the other thread, so repeating:
> > If t
I already sent somthing similar in the other thread, so repeating:
If the editor code is not part of Apache Weex, it should live on its own
domain.
Keep the weex.io domain around so old links continue to work, but redirect
the main domain to the Apache Weex site and the editor subdomain to the new
Thanks - sounds good to me.
Am Do., 17. Okt. 2019 um 14:43 Uhr schrieb 申远 :
>
> I am personally in favour of the donation for following reasons:
>
>- It's a pity that there is no UI library for Weex
>- Weex UI is a confusion name and may violate the brand of ASF as ASF
>hold the
Nice progress.
Let me know when website and all public communication and content is
on par for what you think should be fine for graduation, and I will
spend the time to go through all of it and see if I can find any
confusing parts.
-J
Am Fr., 27. Sept. 2019 um 13:40 Uhr schrieb shihan zheng
:
I like Ionic's take on this:
https://ionicframework.com/blog/making-sense-of-apples-tos/
Am Mi., 18. Sept. 2019 um 16:23 Uhr schrieb York Shen :
>
> Hi, there.
>
> I noticed Apple announced new policy [1] on HTML5 Apps weeks ago. Through
> which Apple makes it position very clear:
>
> "Apps may
shall also be 'org.apache.weex'.
> The weex_sdk_legacy will be built with the plugin therefore its package name
> shall be ‘com.taobao.weex'.
> Users can choose whichever the above connivence library they’d like.
>
>
> > 在 2019年9月18日，02:56，Jan Piotrowski 写道：
> >
> > Sounds g
[1] "When overriding a method, the signatures (name and argument types) have
> to be the same after type erasure." Ref
> https://docs.oracle.com/javase/specs/jls/se7/html/jls-8.html#jls-8.4.2
> <https://docs.oracle.com/javase/specs/jls/se7/html/jls-8.html#jls-8.4.2> for
&g
+1
Am Mi., 11. Sept. 2019 um 10:37 Uhr schrieb York Shen :
>
> Hi, community
>
> The community of weex-loader [1], some of whose contributors are also
> committers of Apache Weex recently proposed to make their code donated to ASF
> with Incubator-Weex as receiving PPMC.
>
> "weex-loader is a
Releases to npm, maven, bintray etc. are what is called "convenience"
in ASF land, similar to the "Convenience Binaries" that are produced.
The official release is the _source code_ that will he hosted on an
_ASF server_, everything else is just to make life easier (which is
super important of
+1!
Am Mi., 4. Sept. 2019 um 09:15 Uhr schrieb York Shen :
>
> Hi, all
>
> The community of CLI-for-Apache-Weex [1], which is known as weex-cli or
> weex-toolkit recently proposed to make their code donated to ASF with
> Incubator-Weex as receiving PPMC.
>
> "CLI-for-Apache-Weex is dedicated to
Awesome, that is really quite an achievement!
So, who is going to translate it into English? ;)
J
Am Do., 29. Aug. 2019 um 09:37 Uhr schrieb York Shen :
>
> Hi, community
>
> I am happy to share some information with you guys. I just found a book [1]
> introducing Weex written in Chinese while
:
>
> Well, it’s actually my mis-spelling.
>
> As I didn’t find a way to change the email address and the Sauce Lab team had
> promoted the account to 5 VMs before I found my mistake, I have no way but
> live with it.
>
>
> > 在 2019年8月29日，14:44，Jan Piotrowski 写道：
&
Off list:
The login emails seems to have a typo at
https://svn.apache.org/repos/private/pmc/incubator/weex/SauceLab - is
this intentional?
J
Am Do., 29. Aug. 2019 um 05:01 Uhr schrieb York Shen :
>
> Hi, community
>
> The Open Source account of Sauce Lab is enabled, one can access the
>
t like the idea of donating, they can
> remain their status without any problem. Actually, weex_playground have a
> dependency for those tools, it would be great if they are part of ASF. Of
> course, that depends on the choice of owners of those tools.
>
> > 在 2019年8月23日，15:11，Jan Piot
Note from me as a private person, not an Apache Incubator mentor:
I really don't understand why and how the names of "Useful, but not
essential" are "violating the IP of ASF". I really dislike this
position.
"Apache Weex Android Devtools" would be problematic, but "Android
Devtools for Apache
Sounds good - SauceLabs are good people.
J
Am Di., 20. Aug. 2019 um 09:54 Uhr schrieb York Shen :
>
> Hi, community.
>
> I’d like to run Weex test case with emulator on SauceLab [1] as they provide
> stable and fast emulator than TravisCI. When I am applying the open source
> account of
Unfortunately there is no way to fix your second point when working in
the apache/* repositories as far as I know.
This is the account of Apache Software Foundation, which is shared
between all projects.
If you fork the repo and work in your own namespace, you can use your
own Travis account and
rly in next week.
> >
> > Best Regards,
> > York Shen
> >
> > 申远
> >
> >> 在 2019年7月16日，16:44，Jan Piotrowski >> <mailto:piotrow...@gmail.com>> 写道：
> >>
> >> Awesome, that was quick - thanks Katherine and RenminWang!
>
As far as I am aware ASF rules only apply to code included in the
releases - what you do to build or test your code is not really
relevant to these requirements.
But obviously you should follow the licences of the code itself, which
seems fine in this case.
Of course if you want to keep that in
Issues definitely are like weeds - there are always more.
Some unstructured thoughts:
- Add a feature request template
- Add a support template that moves questions and debugging stuff to
Stack Overflow (if you have many of those)
- Add some more space to type into the bug report template,
Awesome, that was quick - thanks Katherine and RenminWang!
I will try to check out and play with
https://github.com/apache/incubator-weex-playground soon.
A note: Now that playground is separate,
https://github.com/apache/incubator-weex#use-weex could use some
cleanup to make clear what
These emails should probably not go to this email address, but
comm...@weex.incubator.apache.org or similar. Was probably not
configured when creating the playground repository, and the default is
the dev list if I remember correctly.
Not sure if this can be done in self service or an INFRA issue
;
> > Thanks, I will change it to
> >
> > Copyright 2019 Apache Incubator-Weex
> >
> > Best Regards,
> > York Shen
> >
> > 申远
> >
> >> 在 2019年7月11日，16:09，Jan Piotrowski >> <mailto:piotrow...@gmail.com>> 写道：
>
rstanding, I don't think it's a good idea that we list these
> > dependencies
> > in LICENSE file.
> >
> > [1] https://github.com/apache/incubator-weex-playground
> > [2]
> > https://github.com/apache/incubator-weex/blob/master/android/playground/app/build.gr
>From my understanding
http://www.apache.org/legal/release-policy.html#licensing-documentation
doesn't apply at all if there are no releases (archive, vote process,
publishing) planned for this repository. (Which of course does not
mean that you _can't_ create these files as a service for
ies of the community). The end
result then can be the basis for formal milestones that are used by
developers to select their work.
Of course this can get a _lot_ more fancy and process based - but with
cost of additional effort.
J
Am Do., 4. Juli 2019 um 11:32 Uhr schrieb Jan Piotrowski :
&
Thanks for bringing this up Renmin Wang.
It is important to note here, that Github Milestones are just a tool
to document and organize an organizational process. If the Apache Weex
contributors are not actually planning in milestones, it doesn't make
too much sense to use Github Milestones.
So
Awesome!
I volunteer to test the app(s) when the move has been made to ensure
everything works and will also gladly review any README etc. Just
reply when the move is in a state that should be looked at.
J
Am Do., 4. Juli 2019 um 10:08 Uhr schrieb 王仁敏 :
>
> and I would like to do the separating
oject. It *is* important that you
> > communicate to your users how you intend to handle situations like this
> > though. People find it easier to accept things when they are not surprised.
> >
> > So, the first question is: what do you think is right for your project?
>
As a new user, I would probably be confused to find a
`com.taobao.xxx/com.alibaba.xxx` package name in an Apache Software
Foundation project.
As a a developer, I have no idea how to rename a Java package in a
backwards compatible way though. Proxy classes maybe that just import
and "redirect" to
> Cordova does too, so Jan may be able to answer.
Apache Cordova fortunately only _uses_ it via APIs that are offered by the
OS, and does not _include_ it (or any of its code) - so this problem never
came up.
-J
Am Di., 11. Juni 2019 um 18:32 Uhr schrieb Myrle Krantz :
> On Tue, Jun 11, 2019
That sounds like a good plan YorkShen.
For me, with a user hat on,
https://weex.apache.org/guide/develop/create-a-new-app.html is
definitely the first place I will go to test Weex. So I will be told
to use `weex-toolkit`. The preview rendered by `npm start` will tell
me to use
n users that
> > "weex playground is developer by third party and may contain vulnerable".
> > Anyway, not a perfect solution, but acceptable for me.
> >
> > [1] https://issues.apache.org/jira/browse/INFRA-18494
> > [2] https://github.com/fastlane/fastlane
could and would mark thing "Stuff that some third party provides for
> > > Apache Weex", but for "Stuff for Weex the Apache Weex team also
> > provides",
> > > this is really confusing concept.
> > >
> > > Best Regards,
> > > YorkShen
oid Playground.
>
> I could and would mark thing "Stuff that some third party provides for
> Apache Weex", but for "Stuff for Weex the Apache Weex team also provides",
> this is really confusing concept.
>
> Best Regards,
> YorkShen
>
> 申远
>
>
>
t need write code snippet
>online [2], and scan the QR code, then they get what they write.
>
> [1] https://github.com/googlesamples
> [2] http://dotwe.org/vue
>
> Best Regards,
> YorkShen
>
> 申远
>
>
> Jan Piotrowski 于2019年5月24日周五 下午8:14写道：
>
> > A
A compiled Android or iOS native app is actually an interesting case.
Is this actually part of the release, or is just the source code of
the app?
How tightly coupled are weex and the playground app anyway? Right now
the playground app seems to live in a `playground` subfolder of `ios`
and
I was under the impression that nothing happened yet after we talked
about this the last time. Or was there some cleanup that I missed?
Because then I would re-review the situation and point out the
remaining problems again.
-J
Am Mo., 13. Mai 2019 um 09:39 Uhr schrieb 申远 :
>
> Hi, community
>
>
> Weex needs a place that is only visible to PPMCs to store private key for NPM
> and Bintray distribution channel.
Apache Cordova is using a private SVN hosted by Apache for that and
similar use cases.
> BTW: Though Apache Cordova release process is pretty complicated, I think
> Weex can
ge
> https://github.com/apache/incubator-weex#weex
> <https://github.com/apache/incubator-weex#weex> ?
>
> Best Regards,
> York Shen
>
> 申远
>
> > 在 2019年4月23日，19:21，Jan Piotrowski 写道：
> >
> > I would guess the .tgz includes the RELEASENOTES.md that i
ChangeLog/ReleaseNote pages for Cordova’s Source Distribution?
>
> Best Regards,
> York Shen
>
> 申远
>
> > 在 2019年4月23日，18:00，Jan Piotrowski 写道：
> >
> > What part of the release policy are you specifically referring to?
> >
> > The main distr
What part of the release policy are you specifically referring to?
The main distribution mechanism for Apache Cordova is npm, which
command is mentioned in the "Get started" [1] part of the homepage and
installations instructions [2] of the documentation. Using the source
code is just a fallback,
Anecdotally deprecation is often a problem as many users misunderstand
it as "we removed this" or "this is broken", instead of what it
actually means. So they will be unhappy, although you didn't change
anything than to put a label "this will not be developed further in
its current form" on it.
tion may be
> unacceptable and need corrected. So, I am really in a dilemma.
>
> > 在 2019年3月6日，23:11，Jan Piotrowski 写道：
> >
> > I assume Myrle's response was not focused on this one extension, but
> > on the general topic we discussed over multiple emails.
> >
> >
; > on the apache github account.
> >
> > The Weex PMC needs to have control of all the weex code or else you won't
> > be able to graduate. And generating more code in these off-list projects
> > pushes your project *away* from graduation, not towards it.
> >
>
Welcome He Ling!
Am Mi., 6. März 2019 um 03:41 Uhr schrieb 申远 :
>
> The Podling Project Management Committee (PPMC) for Apache Weex has invited
> He Ling to become a committer and we are pleased to announce that he has
> accepted.
>
> He Ling is a great iOS Developer and works with weex project
not under my or
> > other PPMC's control.
> >
> > Actually, I think Dan may have the admin privilege of weex.io.
> >
> > What do you think, Dan?
> >
> > Best Regards,
> > YorkShen
> >
> > 申远
> >
> >
> > Jan Piotrowski 于2019年3
in them in the page as they are now.
>
> When I finished my work, maybe you could review my PR?
>
>
> Best Regards,
> YorkShen
>
> 申远
>
>
> Jan Piotrowski 于2019年3月1日周五 下午6:10写道：
>
> > Ok, then it's pretty simple:
> >
> > Those tools should have
ctually, there
> > is an entry[1] for EMAS in Chinese document. Besides that, there is no
> > difference between http://weex.apache.org and http://emas.weex.io/ .
> >
> > And Weex projcet always declared that http://weex.apache.org or
> > http://weex.io are the official homep
ways declared that http://weex.apache.org or
> http://weex.io are the official homepage.
>
> [1] http://emas.weex.io/zh/community/biz-emas.html
>
> Best Regards,
> YorkShen
>
> 申远
>
>
> Jan Piotrowski 于2019年2月28日周四 下午10:08写道：
>
> > I don't understand.
>
is a list for weex tool. Except
> for Playground App, others are developed by third party developers. As such
> tools are useful and we cannot move all of them to Apache repos, we just
> list it in the page.
>
> [1] https://weex.apache.org/tools/playground.html
>
&
> Such tools are useful and attractive for users of Weex, and we need a place
to list such tools in Weex eco system, ...
Sorry, did I miss part of the thread here? What "development tools and
others" are you talking about?
> As weex users are Android/iOS/JavaScript developers, they often choose
; while weex only use incubator-weex-site [2]
>
> [1] http://emas.weex.io/
> [2] https://github.com/apache/incubator-weex-site/
>
> Best Regards,
> YorkShen
>
> 申远
>
>
> Jan Piotrowski 于2019年2月28日周四 上午5:37写道：
>
> > Nice!
> >
> > Just found http:
; > >
> > > > > Anyway, I have updated the content of https://weex.apache.org/,
> > which
> > > is
> > > > > the same as https://weex.io now. *As there is a
> > > > > privilege issue, https://weex-project.io/ <https://weex-project.io/>
>
traffic to websites on relaunches.
> > (https://www.google.com/search?client=firefox-b-d=site%3Aweex.apache.org
> > - 217 pages that show mostly a 404 right now)
> >
> > I am do it now, will be fixed today.
> >
> > > Have you already created a Google Search Console
Hm, what kind of code is the user missing at that link? (Google
Translate unfortunately didn't help)
If there was something on the old site that can now not be par of it
any more, it should at least be moved somewhere else (subdomain of
weex.io for example?) and the old URL redirected.
Being
improve
> it later.
>
> Maybe some of the content can be built from a data file on the
> incubator-weex-site <https://github.com/apache/incubator-weex-site> repo.
>
> Thanks,
> Dan
>
> Jan Piotrowski 于2019年2月25日周一 下午6:11写道：
>
> > Yeah, the homepage is unfortunately miss
ntribute-code-or-document
>
> Best Regards,
> YorkShen
>
> 申远
>
>
> Jan Piotrowski 于2019年2月25日周一 下午5:46写道：
>
> > Nice.
> >
> > Which is the repository and branch to send PRs with typo fixes etc to?
> >
> > Am Mo., 25. Feb. 2019 um 10:18
ch
> >> is
> >> > the same as https://weex.io now. *As there is a
> >> > privilege issue, https://weex-project.io/ <https://weex-project.io/>
> >> is not
> >> > updated yet.*
> >> >
> >> > Later, I will redirect https
After further thinking about it I think I agree with Myrle:
If you can answer a Chinese issue in Chinese, just do so.
If you want, you can translate both question and answer to English
manually or automatically as well.
I don't read any Chinese, so I would definitely have to translate to
English
There also seems to be a related documentation PR at
https://github.com/apache/incubator-weex-site/pull/308
-J
Am Do., 21. Feb. 2019 um 09:41 Uhr schrieb 申远 :
>
> It would be better if you could share your feature with more detail here,
> like document so that everyone can understand what is
Ha, good that you got some practice in then - you will probably also need
SVN to publish the releases to be voted on ;)
(Using TortoiseSVN for me was a really nostalgic moment. So many years
working with that software - all forgotten now)
-J
Am Do., 21. Feb. 2019 um 07:31 Uhr schrieb 申远 :
> I
Difficult situation.
Apache projects definitely use English as the default language, but
with an existing userbase that is used to create issue in Chinese,
this would be negative to enforce.
I saw some people using Google Translate to translate the question,
then repost the question in English
ometimes one may give up a better engineer solution due to law issue.
> From user points, we need to give a brief explanation of the latency
> problem.
>
> Best Regards,
> YorkShen
>
> 申远
>
>
> Jan Piotrowski 于2019年2月20日周三 上午2:24写道：
>
> > Uh, the _domain name_
they'll at least
> look at it.
>
> Feel free to add any details you have.
>
> Best Regards,
> Myrle
>
> On Tue, Feb 19, 2019 at 7:18 AM Dan wrote:
>
> > Thanks, Jan, I will take a look at this.
> >
> > Jan Piotrowski 于2019年2月18日周一 下午6:15写道：
> >
&
>
> BTW, do you know the detail about how to do the user-track bellow the
> apache way, I know the Cordova has telemetry.cordova.io to record it, and
> we also want to record the user's behavior in the weex-toolkit to help us
> better improve the tool experience.
>
> Thanks,
> D
Besides what the rules say (which I don't really know):
An apache.org domain has an incredible effect on credibility and
trust. Apache is a really strong brand with developers, and especially
new projects like Weex can benefit from that.
(The project will be called "Apache Weex" anyway)
Apache
ols`? 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
&
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
main called https://weex.io
> <https://weex.io/> .
>
> If there is a way to deploy website to draft.weex.apache.org
> <http://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 写道：
> >
&g
https://weex.io <https://weex.io/> when all the job are done. You may think
> https://weex.io <https://weex.io/> is in beta stage and will be the weex’s
> website. We would like to publish https://weex.io <https://weex.io/> on Weex
> conf 2019. Ref this <http://
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
>>>
> >>> 2. All website you listed is coming
> >>> https://github.com/apache/incubator-weex-site
> >>> <https://github.com/apache/incubator-weex-site>
> >>> <https://github.com/apache/incubator-weex-site
> >>> &l
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
74 matches
Mail list logo
