Hi Craig, I think it will be both to be honest - at least that would be my vision :)
We'd have a few "courses" defined that are distributed as-is, for example Kafka, Elasticsearch, HBase, Hadoop (picked as examples because we have decks for those that we want to donate). But, all the content will also be available as source, along with the tools and means to create new and more specific courses from this material. These would then not necessarily be distributed in a compiled form as I expect these to be fairly specific to for example a training request. Best regards, Sönke On Sat, Mar 16, 2019 at 9:07 PM Craig Russell <[email protected]> wrote: > Hi Sönke, > > > On Mar 16, 2019, at 12:30 PM, Sönke Liebau > > <[email protected]> > wrote: > > > > One sentence from your mail made me think a little. You said "Apache > policy > > is "no binaries in releases" which is commonly understood to mean that > > releases contain the sources to build the release and not the result of > > compiling" - would this, for us, mean that we cannot distribute HTML > slides > > as releases but have to ship Asciidoc material and the means to create > > slides from those? > > If the sources are in asciidoc, which get compiled into pptx, I'd say the > pptx is then binary that can be distributed as convenience binary, similar > to other projects distributing Docker files, java binaries, etc. > > If we compose the presentations with other training artifacts, is there a > need to "compile" the presentations into pptx? Or can these be done by the > consumer? I don't know the answer. It depends on how we thing these are > going to be consumed. > > Craig > > > > Best regards, > > Sönke > > Craig L Russell > Secretary, Apache Software Foundation > [email protected] <mailto:[email protected]> http://db.apache.org/jdo < > http://db.apache.org/jdo> > -- Sönke Liebau Partner Tel. +49 179 7940878 OpenCore GmbH & Co. KG - Thomas-Mann-Straße 8 - 22880 Wedel - Germany
