>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 potential users - they are not just useless process but actually useful and contain important information for the user.)
Which of course raises another question: What kind of repository will weex playground be? You mentioned "only for demo purpose", I also know that it will probably be published on Apache App Store accounts and be used by developers to play with weex. But will it make sense for users of weex to use the source code of the app for something, as a base for a project for example? -J Am Mi., 10. Juli 2019 um 11:09 Uhr schrieb 申远 <shenyua...@gmail.com>: > > Hi, community. > > As you might already knew, we are separating playground from weex_sdk [1]. > As playground is only for demo purpose and never released in Apache Way, I > am a little concerned about the LICENSE issue around playground. > > There are many runtime/download dependencies(image library, network > library, json library, etc..) in weex playground [2] as any other Apps do. > Do we need to list them in LICENSE file? Or are they separately downloaded > dependencies[3] and we can ignore them in LICENSE file? > > LICENSE and NOTICE MUST NOT provide unnecessary information about materials > > which are not bundled in the package, such as separately downloaded > > dependencies. > > > These dependencies would not be bundled in source release nor binary > convenience library of Weex Playground. > > [1] > https://lists.apache.org/thread.html/020895785263a3f5ee4dfa6c56167c01699227d9512f19f6635ef563@%3Cdev.weex.apache.org%3E > [2] > https://github.com/apache/incubator-weex/blob/master/android/playground/app/build.gradle#L104-L127 > [3] http://www.apache.org/legal/release-policy.html#licensing-documentation > > Best Regards, > YorkShen > > 申远
