Hi Justin, apologies, I completely missed your first mail, it was only the reminder that for some reason popped up on my feed.
Just to be sure I understand your intention, this is actual content, that you'd like to donate to training and which we can use as a training exercise for how we'd organize things in the repository? If true, keep reading, if false, disregard the rest of this mail :) I am a bit torn as to how to organize something like that, to be honest, so far we mostly spoke about things that would live in the repository as "source code" - reveal.js presentations more specifically. That being said, I think that it would be a good idea to consider the possibility of other content types like webinars, podcasts, or labs for that matter, which have already been touched upon. What I do not think we should do is have audio or video content in the repo, it will become monstrously large very fast if we do that. But what we should definitely have in the repository is a reference to this content along with metadata etc. to make it searchable in our "content list" (for lack of a better word). So what I could imagine is having a metadata file about this content in the repo, which states where the actual files are, what they contain, maybe how to recreate the final product etc. and then have the binaries on shared storage somewhere, Dropbox, disk. As for where to host the video, I think reaching out to vimeo and enquiring whether they'd be willing to help out might be a good idea. I have no idea what providers exist in that space, youtube would be the obvious one, vimeo is known, but beyond that... Hope that helps, even if it probably asked more questions than answered :) Best regards, Sönke On Thu, Mar 28, 2019 at 5:44 AM Justin Mclean <[email protected]> wrote: > Hi, > > Anyone have any suggestions? > > Thanks, > Justin > > On Fri, 22 Mar 2019, 13:49 Justin Mclean, <[email protected]> > wrote: > > > Hi, > > > > I have a worked example of applying [1] to a fake Apache project here > [2]. > > > > I made a short video of it here [3]. The title screen and content was > also > > made by me. It also have english closed captions. > > > > There are no IP issues all code was written my me and a couple of small > > PRs covered by ALv2. > > > > So asset wise I have: > > 1. Code in GitHub > > 2. Video title image (photoshop) > > 3. Raw video and sound > > 4. edited sound > > 5. Screen-flow file used to produce the final video. > > 6. Final video > > 7. Caption file (including timing) for English > > > > Would we want all of that? For instance it might be nice to have the > > captions translated into other languages. I’ve involved with a couple of > > podlings that might be able to help with that for Chinese. > > > > Just think how to put this all together under > > https://github.com/apache/training. > > > > Perhaps under /incubator/license-howto? > > > > /license-howto > > |- wombat > > | - code (code from GitHub) > > |- assets (video, caption files etc) > > |- LICENSE > > |- NOTICE > > |- README > > > > That also ask where should we host the video? At some point my vimeo > > account may not exist. Do we ask the board for an apache acocunt there or > > do we ask vimeo nicely if they would provide a free account or do we > place > > it elsewhere? > > > > I had intended to make other worked examples but like a lot of things > > never got around to it. > > > > I went with this first and it may also help in making LICENSE files for > > stuff we add. > > > > Thanks, > > Justin > > > > 1. http://www.apache.org/dev/licensing-howto.html > > 2. https://github.com/justinmclean/ApacheWombat > > 3. https://vimeo.com/171210141 > -- Sönke Liebau Partner Tel. +49 179 7940878 OpenCore GmbH & Co. KG - Thomas-Mann-Straße 8 - 22880 Wedel - Germany
