Ok, thanks for explaining. If it seems ok to keep placeholders there, it is also Ok from my perspective.
BTW, we're voting in the discussion thread. Should we cast votes in the vote thread, as well? сб, 8 июн. 2019 г. в 09:13, Sönke Liebau <[email protected] >: > Hi Justin, > > thanks for explaining! +1 from me (binding). > > Best regards, > Sönke > > Justin Mclean <[email protected]> schrieb am Sa., 8. Juni 2019, 02:07: > > > Hi, > > > > > 1. in NOTICE there is a sentence that mentions that this content was > > > originally developed by you. Is that legally required to be there? > > > > It’s required by ASF policy yes. The original copyright notices were > > replaces with ASF ones and in that case you need to add the copyright to > > NOTICE. [1] (also [2] where it mentions relocated copyrights) > > > > > 2. At the bottom of the License file, there is a section that this > > project > > > contains parts of the reveal.js framework which is licensed under the > MIT > > > license. Should that not be in the Notice file? > > > > License stuff goes in LICENSE not in NOTICE. [2] > > > > > In the docs I found the following two sentences, which have me confused > > :) > > > "LICENSE should contain the text of the ALv2 -- no more, no less." [2] > > > > That for the case where you have no 3rd party bundled item inside, unlike > > this release. > > > > > "The LICENSE file communicates the licensing of all content in an > Apache > > > product distribution. It always contains the text of the Apache > License, > > > and sometimes more." [3] > > > > Thats for the case where we have 3rd part dependancies, like this release > > does. > > > > Thanks, > > Justin > > > > 1. https://www.apache.org/legal/src-headers.html#headers > > 2. http://www.apache.org/dev/licensing-howto.html#mod-notice > > > > >
