In $WORK we refer to them as “training slides” and “reference” – as in “check the reference documentation on the internal web” and “no, there is no point in only getting the slides, they have to be explained by a trainer anyway”.
So, yes, they serve different purpose.
Going to web-based training means producing something in-between.
From: openchain-bounces@... [mailto:openchain-bounces@...] On Behalf Of Catharina Maracke
Sent: Monday, June 06, 2016 8:46 AM
To: Jilayne Lovejoy <Jilayne.Lovejoy@...>
Subject: Re: [OpenChain] Curriculum next steps
The more I read through the documents and the more I think about it, the more I like to idea of having two different formats as suggested by Jilayne and I am wondering whether we should adopt this approach for the OpenChain Curriculum
I would really like to have a short, clean, and easy to read text file, which can be translated and distributed without much further explanation and which would provide a sophisticated overview for people, who like to read something
by themselves - most likely in addition to the presentation? I don’t think such a text file can or should replace the (probably) more detailed set of slides we are about to develop, but having two different formats sounds quite useful and elaborate.
> On May 28, 2016, at 12:56 AM, Jilayne Lovejoy <Jilayne.Lovejoy@...> wrote:
> Hi Shane and curriculum team,
> I am attaching additional materials contributed by ARM. These are
> general training slides from 2 1-hour recorded sessions and a text
> document version of the slides used for general education about open
> source software. They have been stripped of any corporate material
> and are formatted quite plainly (not many pictures, mostly text). They
> cover most of the topics listed in OpenChain requirement 1.2
> I tried to upload them directly, but need a login, hence attaching
> them here.
> The slides are in PowerPoint format, but the text file is open
> document (as I thought all would need to be in open format, before I
> read this email ;) Happy to convert that to a different format if need be.
> Why two formats? I found that 1) a video recording (or just slides)
> is not as easy to refer back to later, whereas posted text on a
> website with a linkable table of contents provides a quick and easy
> sustainable resource; and 2) some engineers seem to prefer reading
> than listening or watching. Having explained that, format is
> something the curriculum team may want to think about - slides need a
> presenter, whereas reading materials do not. Of course, reading is not
> as trackable as attendance to a presentation - food for thought!
> On 5/23/16, 8:22 PM, "openchain-bounces@... on
> behalf of Shane Martin Coughlan"
> <openchain-bounces@... on behalf of
> shane@...> wrote:
>> Hi Dave
>> Thanks for confirming!
>> The list of people who have explicitly stepped forward to participate
>> in building out the curriculum so far is:
>> Dave Marr
>> Jilayne Lovejoy
>> Kate Stewart
>> Ramesh Jain
>> Shane Coughlan
>> Tom Arcidiacono
>> If anyone else is interested in contributing just message me or step
>> into our calls and drafting at any point.
>> All, the donated slides from Dave (Qualcomm) and Ibrahim (Samsung)
>> have been uploaded to OneDrive and can be edited by anyone without
>> any log-in via this URL:
>> There are three files:
>> (1) Dave’s slides
>> (2) Ibrahim’s slide
>> (3) A placeholder document for the OpenChain Curriculum Core Open
>> Source Compliance slides
>> As per our last call, the Curriculum Work Team aims to:
>> (A) Review (1) and (2) to remove any corporate branding or extra
>> (B) Combine them into (3)
>> (C) Before working on reducing the slide count to result in a
>> presentation that takes less than an hour.
>> We are going to aim to get the first rough cut ready in time for our
>> next call in the third week of June. The end result should support
>> the goals outlined here:
>> In particular, we want to help support Section 1.2, the 'Mandatory
>> FOSS training’ requirements. Ideally our slides would help people get
>> started in this area.
>> The process is simple. Just open the link, click a file, and select
>> “Edit in Browser” to get started. I am personally going to get
>> started on (A) later this week and would appreciate help to trim any
>> remaining corporate branding or slides which are unnecessary.
>> Of course we are still accepting submissions of additional material
>> so just reach out if you want to donate under CC-0.
>> NOTE #1: Why OneDrive and PowerPoint Online? The original slides were
>> in PowerPoint format. A search for online systems with easy import
>> and collaborative editing of these documents resulted in a shortlist
>> of Google Slides or PowerPoint Online. PowerPoint Online appears to
>> work in China while Google services are more challenging to access.
>> If anyone strongly wants us to use another system I am happy to discuss that too.
>> NOTE #2: Why a public link that anyone can access? Because we want to
>> encourage everyone to step in and lend a hand. Our goal, as per the
>> minutes from the last call, is to make a simple, clear set of slides
>> to support Open Source compliance in the context of OpenChain, and to
>> help “on-board” people into both compliance best practice and
>> deployment of OpenChain.
>>> On May 22, 2016, at 7:00 AM, Marr, David <dmarr@...> wrote:
>>> Shane please add me as a member of the curriculum work team.
>>> -----Original Message-----
>>> [mailto:openchain-bounces@...] On Behalf Of
>>> Shane Martin Coughlan
>>> Sent: Thursday, May 19, 2016 10:51 PM
>>> Subject: [OpenChain] Curriculum next steps
>>> Dear OpenChain project members
>>> Thank you to everyone who contributed to our last call and to many
>>> others who expressed interest in contributing to our curriculum work
>>> The specific proposals to launch the work team were:
>>> (1) We provide high level process management slides that can be
>>> adopted and expanded by any company seeking to undertake Open Source
>>> (2) We will create the first iteration of these slides in a three
>>> (3 call) window, with most of the actual work happening offline;
>>> (3) We re-use existing material that is available (or can be made
>>> available) under a CC-0 license;
>>> (4) We keep things simple to make adoption, translation and
>>> understand as straightforward as possible.
>>> These proposals were accepted by the curriculum work team members
>>> What this means for the team is:
>>> (1) An initial version of the slides going online for editing next
>>> (2) The team working on the slides for the next month to prepare the
>>> first draft;
>>> (3) Review of the slides will take place on our second call to
>>> assess status and where we need to focus energy;
>>> (4) The subsequent month will apply focus to these points before
>>> resulting in our first deliverable for consideration in the third call.
>>> I will send an email next week with details of how we will
>>> collaborate online.
>>> OpenChain mailing list
>> OpenChain mailing list
> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other
person, use it for any purpose, or store or copy the information in any medium. Thank you.
> OpenChain mailing list
OpenChain mailing list