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 <[email protected]> 写道： > > 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 <[email protected]> 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 [email protected], 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 <[email protected]> 于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 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 <[email protected]> wrote: >>>> Sorry for mis-sending previous e-mails. >>>> >>>> I will ask the authors of https://github.com/weexteam/xtoolkit < >>> https://github.com/weexteam/xtoolkit> and >>> https://github.com/weexteam/weex-pack < >>> 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 <[email protected]> 写道： >>>>> >>>>> >>>>> >>>>> Best Regards, >>>>> York Shen >>>>> >>>>> 申远 >>>>> >>>>>> 在 2019年1月31日，21:12，Willem Jiang <[email protected] <mailto: >>> [email protected]>> 写道： >>>>>> >>>>>> 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 <[email protected] >>> <mailto:[email protected]>> wrote: >>>>>>> >>>>>>> 1. Repos Problem >>>>>>> https://github.com/apache/incubator-weex-site < >>> https://github.com/apache/incubator-weex-site> < >>> https://github.com/apache/incubator-weex-site < >>> 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 < >>> https://github.com/apache/incubator-weex> < >>> https://github.com/apache/incubator-weex < >>> 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 < >>> https://github.com/apache/incubator-weex-site> < >>> https://github.com/apache/incubator-weex-site < >>> 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 <[email protected] <mailto: >>> [email protected]>> 写道： >>>>>>>> >>>>>>>> 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> >>>>>>>> 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 >>>>>>> >>>>> >>>> >>>> >>>
