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 https://weex.apache.org/tools/playground.html.

So for the toolkit we definitely need a solution, as this will
effectively be understood as "being" Weex by users (When people talk
about Apache Cordova, they often actually mean the CLI `cordova` - for
`weex` this comes from the toolkit).
The playground app needs to come from Apache Weex as well, and be
released as a normal Apache Weex project - but we already talked about
that elsewhere and this is in progress if  I understood correctly. (It
then of course should also not be listed under "Third Party Tools" on
the website any more).

A bit confusing might be https://weex.apache.org/tools/dotwe.html
which is linked as "Online Playground", which indicates to belong to
the Playground app, but is actually a third party thing hosted on
editor.weex.io (which of course it not ok as domain). What you get
clicking the link also actually looks different than the preview
screenshot, which looks a lot more like http://dotwe.org/vue/ - which
itself is not linked at all in "Third Party Tools".

If I as a user can follow the "Create a new app" instructions without
needing to use third party tools or encountering confusing links and
discrepancies, a good part of the problems might be solved already.

-J

PS: Small bug report: https://weex.apache.org/tools/ide.html shows
Chinese disclaimer.

Am Do., 6. Juni 2019 um 12:08 Uhr schrieb 申远 <[email protected]>:
>
> Hi, community
>
> I spent some time this week to figure out what are essential parts to run
> Apache Weex and what are not. Those essential part should go into Apahce
> Weex's umbrella, while others could change their name to avoid violation of
> ASF's trademark and copyright. What's more, the document itself should be
> clear enough about what exactly users download or install when they use
> Weex and where it come from. Here are progresses and issues still need
> solved.
>
> Documentation
> The following issues are solved, all of the are marked as Un-Apache or
> deleted:
>
>    - https://weex.apache.org/tools/ide.html
>    - https://weex.apache.org/tools/extension.html
>    - https://weex.apache.org/tools/toolkit.html
>    - https://weex.apache.org/404.html
>    - https://github.com/weex-plugins
>    - https://github.com/weexteam/ (Some of the repos may still have
>    problems, see later discussion about Github Repo)
>
> BTW: After some negotiation, I am a administor of the last two Github team.
> And I will guide those repos to make sure all of them are not violation of
> ASF's policies.
>
> The following issues doesn't need solved, as they are clear about whether
> they are part of Apache or not.
>
>    - https://weex.apache.org/tools/playground.html
>    - https://github.com/weexext
>    - https://github.com/weex-cli
>
> Currently, there are two essential tools listed in the documents and none
> of them are under ASF:
>
>    - weex-toolkit [1]
>    - vue-loader [2]
>
> Weex-toolkit is a collection of useful tools, maybe we could find a
> replacement for it and rewrite the corresponding document. As for
> vue-loader, I don't think users can build Weex without it. Correct me if I
> am wrong, as I am not that familiar with front-side-engineering.
>
> Github repositories
> The following github repositories may lead confusion, as it's hard for
> developers to understand whether they are part of Apache Weex or not. As
> Weex document clearly said vue-loader as essential part [2], I am not sure
> which of the following repoes are vue-loader and their relationships.
>
>    - https://github.com/weexteam/weex-vue-render
>    - https://github.com/weexteam/weex-vue-loader
>    - https://github.com/weexteam/weex-vue-precompiler
>    - https://github.com/weexteam/weex-builder
>    - https://github.com/weexteam/weex-loader
>
> Host Name
> The following host name is clear about they are not part of Apache Weex, I
> don't think we need pay more attention:
>
>    - http://dotwe.org/vue/
>
> The following host name may need more eyes, as they may lead confusion:
>
>    - http://editor.weex.io/
>
> [1] https://weex.apache.org/guide/develop/create-a-new-app.html
> [2] https://weex.apache.org/guide/use-vue-in-weex.html
>
> Best Regards,
> YorkShen
>
> 申远

Reply via email to