Now that the Trusted Committer Videos are out there we need to publish the written articles as well. We'd like each article to occupy its own page in the Learning Path.

We should produce a video based on the Conclusion section of the Contributor outline.

The video should teach the same points as the Conclusion Article.

We're talking about this video. We like the latter title better.

"Update" means:

• The title in the O'Reilly UI.
• The introductory slide.

We should produce a video based on the Becoming an InnerSource Contributor section of the Contributor outline.

The video should teach the same points as the Becoming an InnerSource Contributor Article.

We discussed if we would want to move the Patterns repo (currently at https://github.com/paypal/InnerSourcePatterns/ ) to our InnerSourceCommons org here. It looks like a "Go", thus we should update the links to the repo where ever it is used, e.g. here.

This ticket is to keep track of that.

We should produce a written article based on the Becoming an InnerSource Contributor section of the Contributor outline.

The article should teach the same points as the Becoming an InnerSource Contributor Video.

The README has some pretty clear roles to fill and the project board tracks completion of those roles, but there isn't a 1:1 mapping between the two. We should adjust one, the other, or both so that they are in sync.

We should produce a video based on The Contributor in InnerSource section of the Contributor outline.

The video should teach the same points as The Contributor in InnerSource Article.

Multiple people have identified various opportunities to continue the learning path experience on various channels with more advanced topics (this repo, Slack, other repos, calls, ...).

This issue is to collect those references or ideas and to be able to use them later on to create said more advanced material.

Source and first idea:
https://github.com/InnerSourceCommons/InnerSourceLearningPath/pull/59/files/3dc60f7166de253aad59acf18f358ef9839ac98c#r267404860

Consistent with other sections of the learning path, we should create an outline.md document for Product Owner. It can be based on the existing videos and transcripts and should encompass the breadth (but not depth) of what we want to say about each segment in the Product Owner section of the learning path.

After the outline is complete we should open up individual tickets representing the full-written articles for each video.

We should produce a written article based on The Contributor in InnerSource section of the Contributor outline.

The article should teach the same points as The Contributor in InnerSource Video.

We should produce a video based on the Mechanics of Contributing section of the Contributor outline.

The video should teach the same points as the Mechanics of Contributing Article.

DESCRIPTION

Currently the videos that we're producing are exclusively hosted in the O'Reilly Safari learning platform. We're so glad that the content is there! However, not all members of the InnerSource Commons have access to them.

We want O'Reilly to release the videos to the InnerSource Commons so that they can be hosted at a location where all members can see them.

In order to do so, PayPal needs to sign an updated contract consistent with the above-stated intent. The purpose of this card is to track that work happening.

ACCEPTANCE CRITERIA

There is a signed contract for the Learning Path that allows for release of the produced videos to the InnerSource Commons.

#22

Here are some additional thoughts on this first introductory article:

Overall, I think this is a great start - it's thorough and covers the topic in an appropriate level of detail.

Some potential issues I found were:

• Should this be an article in the 1st person (who is I or we?)

• On Line 214, a statement was made about InnerSource being done during working hours, vs. 'after hours' contributions for Open Source. That may be the case in some companies, but there are a lot of companies where InnerSource and Open Source contributions happen during working hours. The vast majority of open source software is built by engineers working on company time to achieve business goals. I think we should consider removing or rewording that section.

• There are a couple of descriptions of 'Newbies' or 'Newbie tasks', which I think sound a bit demotivating to those who may be 'newbies'. Let's brainstorm a new name for those community members.

• There is a lot of focus on TCs being community managers, as well as deep technical experts. In some communities, you may be able to consider separating the roles so that a dedicated community manager can take on some of those. This could be especially important if a TC has a deep technical passion, for example, but has a hard time interacting or promoting the project within an internal organization.

In our last LP call on 2019/2/14 (see Google Docs) we heard from O'Reilly that they support hyperlinks to other LP parts or outside web pages in their LP format. (Yay! 👍 )
Once we know how to annotate them inside the documents we need to go through or textual resources and actually add all the hyperlinks we want. Let's use this ticket to track that.

Before filming O'Rielly needs us to fill out this Video Proposal. We'll do this by first making a PR to this markdown version of the document. Once that is approved and merged we can copy the text there into the GDoc that O'Reilly will see.

The following audio portions need to be re-recorded:

Video 02_primer:

• The entire audio should be re-recorded (about ~18 sec).
• Instead of saying: "This is the fifth video, in a five video series about inner source. Please watch the other videos first."
• It should be saying something like: "This is the last of the four video sections (or series? or segments?) about inner source. Please watch the other video segments first."

Video 07_contact:

• The audio from 00:00:11:07 should be re-recorded. I suggest to re-record everything until 00:00:26:10 where there is a natural pause anyway.
• Instead of saying: "You should also watch the other four videos if you haven't yet ..."
• It should be saying something like: "You should also watch the other three video sections (or segments?) if you haven't yet ..."

As mentioned in PR #38 and discussed on Slack we need to decide which spelling to use - either 'InnerSource' or 'inner source'.
After deciding on that we'll need to clean up the articles respectively.

Let's use this ticket to coordinate / bundle all related matters, i.e. close this

• once the decision is made AND
• all files are cleaned up accordingly.

We have the raw content of what we'd like to go in the Contributor section. Now we need to refine and polish that brain dump into a set of individual segments, each with a descriptive title and also a clear outline of what is in the section. These titles/outlines should be descriptive and complete enough for us to fill out the shoot playbook, video proposal, and also to start drafting the written articles.

A potential contributor asked what is the license for the videos, articles, and workbook. We don't have one right now, but should.

We should produce a written article based on The Contributor Ethos section of the Contributor outline.

The article should teach the same points as The Contributor Ethos Video.

We should produce a video based on the Benefits of Contribution section of the Contributor outline.

The video should teach the same points as the Benefits of Contribution Article.

We should produce a written article based on the Benefits of Contribution section of the Contributor outline.

The article should teach the same points as the Benefits of Contribution Video.

Before filming O'Reilly needs us to fill out this shoot playbook.
This author kit has an instructional video on the shoot playbook.

We should produce a video based on The Contributor Ethos section of the Contributor outline.

The video should teach the same points as The Contributor Ethos Article.

Context

The learning path will have a workbook companion report.
Videos are broken into small segments. Before viewers go on to the next segment, the workbook gives them an opportunity to ask themselves multiple choice questions to make sure they got the videos’ takeaway.

Action point

Create questions (in the Google doc) for the Contributor Segment.
See #103 for details.

There can be as few or as many questions as make sense to cover the key points of content.

We discussed the filming of the contributor videos in Berlin. To gauge the suitability of the local resources for the purpose a small clip will be created and discussed with O'Reilly.

Context

The learning path will have a workbook companion report. 🎆
Videos are broken into small segments. Before viewers go on to the next segment, the workbook gives them an opportunity to ask themselves multiple choice questions to make sure they got the videos’ takeaway.

Required action

This will be a set of multiple choice questions dealing with the key take-aways per segment. We need someone to be responsible to collect and deliver them to O'Reilly per segment. O'Reilly can help to provide the wrong answers, we need to provide the questions and the right answers.

@clobner probably is interested in this ticket. Does Andy have a GitHub handle?

Ticket purpose

This ticket is supposed to find the people, let's handle the actual collection in separate tickets then.

We should produce a written article based on the Mechanics of Contributing section of the Contributor outline.

The article should teach the same points as the Mechanics of Contributing Video.

At some point we'll want to promote the existence of the learning path so that people use it. This issue tracks coming up with a community-agreed marketing plan for the learning path.

The plan should describe what we will do and also when in the creation cycle of the learning path that we should do it.

Rationale

O'Reilly Production happens in Atlas. Atlas conceptually is a large GitLab instance with attached document production capabilities. We want to enable push of our upstream changes to the O'Reilly system to enable faster and easier collaboration for everyone while ensuring they do not break anything at O'Reilly.
Thus we need to sync our repo on changes and check PR's to not break the O'Reilly process - in other words: We need CI.

Action points

• Figure out Atlas build process
  • build configuration files, jobs (separation of articles)
  • API usage to trigger artifact builds, possibly provide artifacts?
• Figure out possibly needed changes to format to enable good looking results for PDF and EPUB.
• Figure out credential storage, appropriate CI system, possibly acquire needed non-personal accounts
• Setup jobs on testing copy and validate with O'Reilly that nothing breaks
  • PR tests
  • Continuous sync/push of master to O'Reilly
• Write about the approach s.t. it can possibly be useful for others.

Possible additional use

• Trigger builds to GitBook or similar for our own use / site rendering
  • possibly also relevant for video integration (#46, #66)
• Possibly partially also useful for the patterns repo.

This card tracks the work to create a written article to teach the universal, underlying principles of effective inner source.

The article should be PR'd to https://github.com/InnerSourceCommons/InnerSourceLearningPath/blob/master/introduction/principles.md

As the community progresses and grows we'd like to be able to share the meeting roles between active members. One role that's not sharable right now Scheduler because the repeating calendar invite is sent from Russ's calendar, which only he can access.

We should come up with some kind of calendar/invite solution that allows any interested community member to (potentially) act as Scheduler.

Per the schedule we'd need an outline for the content of the Contributor section of the learning path.

The outline should include a listing of the segments of the learning path as well as the major points of each segment.

Once this outline is finished we can simultaneously start producing both the written and video portions of the segments.

Context

The learning path will have a workbook companion report.
Videos are broken into small segments. Before viewers go on to the next segment, the workbook gives them an opportunity to ask themselves multiple choice questions to make sure they got the videos’ takeaway.

Action point

Review and propose changes (in the Google doc) for the Introduction Segment Questions.
See #103 for details.

Context

The learning path will have a workbook companion report.
Videos are broken into small segments. Before viewers go on to the next segment, the workbook gives them an opportunity to ask themselves multiple choice questions to make sure they got the videos’ takeaway.

Action point

Review and propose changes (in the Google doc) for the Product Owner Segment Questions.
See #103 for details.

It's fun to work together on the learning path, but we also want the work to come to an end and to finish it together! A natural target for finishing would be the upcoming ISC Spring Summit in Ireland. Let's put down a rough schedule of what we'd need to do to finish all expected videos and articles and have them published on innersourcecommons.org and O'Reilly Safari at that point.

Context

The learning path will have a workbook companion report.
Videos are broken into small segments. Before viewers go on to the next segment, the workbook gives them an opportunity to ask themselves multiple choice questions to make sure they got the videos’ takeaway.

Action point

Review and propose changes (in the Google doc) for the Trusted Committer Segment Questions.
See #103 for details.

following the "join the slack" call to action at OSCON

https://isc-inviter.herokuapp.com/ is what's linked to on the docs (somewhere) and when I try login in it gives an error about not being a paid version.

We should produce a written article based on the Conclusion section of the Contributor outline.

The article should teach the same points as the Conclusion Video.