├── README.md ├── index.html ├── media ├── pmk_logo-red.png └── pmk_logo-red_300w.png ├── pmk-styles.css ├── potluck-framework ├── README.md ├── facilitator.md ├── phonecall.md └── potluck.md ├── public-media-potluck-january-2018.html ├── public-media-potluck-january-2019.html └── public-media-potluck-june-2018.html /README.md: -------------------------------------------------------------------------------- 1 | ![Public Media Kitchen Logo](/media/pmk_logo-red.png) 2 | *** 3 | # The Public Media Kitchen Toolkit 4 | 5 | There is too much duplication of effort in public media product development. We can do a better job sharing practices and things we build for ourselves that could be useful to others. The Public Media Kitchen Toolkit is a collection of interesting things we're all working on. The intention is first to inform but over time move to direct collaboration. 6 | 7 | The Toolkit itself is the `index.html` file in this repo that lists summaries and links to the respective project. The rules for listing things: 8 | 9 | - If it is a link to software, the page linked to the project must clearly explain what the project is and how to use it. 10 | - If it is instead a process or methodology, the link should clearly explain how it works. 11 | - Even if the project is not readily extensible in it's current form, it should be a project open for collaboration. 12 | 13 | By participating in this project you agree to abide by the above terms. 14 | 15 | # Contribution Guidelines 16 | 17 | **The pull request needs a useful title. Pull requests with `Update index.html` as title will be closed without review.** 18 | 19 | Please ensure your pull request adheres to the following guidelines: 20 | 21 | - Review the list carefully before adding your project - there's a chance someone has already listed your project. 22 | - Additions should be added in alphabetical order within the relevant category. 23 | - Make an individual pull request for each project listing. 24 | - Use the following format: `

[Project Name]: [Subhead description no longer than 140 character]

` followed by `

[a paragraph less than 500 characters.]

` and a closing `
` tag. 25 | - Check your spelling and grammar. 26 | - The pull request and commit should have a useful title. 27 | - New categories or improvements to existing categorization are welcome, but must also be submitted with individual pull requests. 28 | -------------------------------------------------------------------------------- /index.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Public Media Kitchen Toolkit 6 | 7 | 8 |
9 |
10 | 11 | 12 |

There is too much duplication of effort in public media product development. We can do a better job sharing practices and things we build for ourselves that could be useful to others. The Public Media Kitchen Toolkit is a collection of interesting things we're all working on. The intention is first to inform but over time move to direct collaboration.

13 | Click here for information about the next Public Media Potluck - the Public Media Kitchen's in person meetup January 17-18th, 2019 in San Francisco, CA.

14 | 15 |

The Toolkit

16 |

Instructions for updating this list can be found in this GitHub project's readme file.

17 |
18 | 19 | 20 |
21 |
22 |

Streaming Media

23 | 24 |
25 |

StreamMachine: Next-generation streaming audio infrastructure for radio stations

26 |

StreamMachine is an open-source streaming audio server aimed at pushing innovation for radio stations that have spent too many years running old technology like Shoutcast and Icecast. The project has two goals: emulating the traditional streaming experience and building support for new features that push the radio listening experience forward. Currently StreamMachine supports traditional Shoutcast-style streaming and HTTP Live Streaming. SCPR has run StreamMachine in production since 2012.

27 |
28 | 29 |
30 |

RateIt App: A Rails engine for rating items.

31 |

Validates users using OAuth and the rated thing using injected plugins. Implementations of this ratings engine include the APM|MPR Alexa skill and the APM Radio app (coming to Public Media Kitchen February 2018)

This is a Knight funded project built by APM|MPR.

32 |
33 | 34 |
35 |

Top Music: A year-end list generated by your audiences' votes

36 |

This app provides a user interface for allowing the display of a large number of items that can be selected by an authenticated user. There is code for importing songs and fetching album artwork and works with OAuth for authentication.

This is a Knight funded project built by APM|MPR.

37 |
38 | 39 |
40 | 41 | 42 |
43 |
44 |

On-Demand Media

45 | 46 |
47 |

Resound: A suite of applications to help with the storage, management, and distribution of digital audio

48 |

The goal of the project is that it's plug-and-play with existing systems, and is easy to use for any user in any given organization. This is a Knight funded project built by SCPR in collaboration with NYPR, WHYY, and NPR-DS.

49 |
50 | 51 |
52 |

APM Go and Bragi API: A personal playlist app and supporting backend API.

53 |

The front end of this project is a React based player that allows an authenticated user to play and archive audio from a variety of participating websites. The back end of this project is an API that stores data about individual users, what audio files they have saved and whether they are in a new or archived state.

This is a Knight funded project built by APM|MPR.

54 |
55 | 56 | 57 |
58 | 59 | 60 |
61 |
62 |

Data Management

63 |
64 | 65 | 66 |
67 |
68 |

IoT (Internet of Things)

69 | 70 |
71 |

Alexa Skill for Music Stations: An example Alexa Skill for playing live streams and calling Composer API to identify song info

72 |

This is a simple skill that demonstrates live music streaming and interacting with the NPR Composer API, initially developed for WYEP

73 |
74 | 75 |
76 |

Alexa Skill Share

77 |

Developed by APM|MPR with funding from the Knight Foundation.
78 | The base code is here.

79 |

A small library to reduce boilerplate and enable sharing of state handlers and intents between skills. Easily compose intents to create a state handler, and compose state handlers to create an Alexa skill lambda handler. This library is currently up and running in a development version of the skill for The Current.

80 |
81 | 82 |
83 | 84 |
85 |
86 |

Content Management Systems

87 |
88 |

Slimdown A library for structured, markdown based pages

89 |

Slimdown is a simple gem to allow you to easily add static pages to your app via a folder full of Markdown files. There is also a PHP version available.

90 |
91 | 92 |
93 |

NPR's Interactive Template A comprehensive scaffolding for building interactive stories

94 |

The Interactive Template provides a complete toolkit for building rich multimedia pages, fed from Google Sheets, Docs, CSV, JSON, and Markdown. Includes a live development server with utilities for bundling and compiling JavaScript and CSS (from LESS). Pages are deployed to Amazon S3.

95 |
96 | 97 |
98 |

Dailygraphics Next A data visualization template from NPR Visuals

99 |

The Dailygraphics rig is used by NPR to create data visualizations for stories using D3, powered by Google Sheets and published to S3. It includes a number of templates for different types of graphics, all of which are responsive and embeddable using Pym.js.

100 |
101 | 102 |
103 | 104 | 105 |
106 |
107 |

Social Media & 3rd Party Platforms

108 | 109 |
110 |

Audiograms A library for generating shareable videos from audio clips

111 |

Unlike audio, video is a first-class citizen of social media. It's easy to embed, share, autoplay, or play in a feed, and the major services are likely to improve their video experiences further over time. WNYC's solution to this problem was this library. Given a piece of audio to share on social media, this can generate a video with that audio and some basic accompanying visuals: a waveform of the audio, a theme for the show it comes from, and a caption. For more backstory, read this post.

112 |
113 | 114 |
115 |

oEmbed Proxy Simple library to manage first party, embedly, and custom oembeds

116 |

At MPR/APM, producers want to include content from tons of third party systems. Many of these support oEmbeds, a spec for content embedding. To handle these, we built the oEmbed Proxy which is a single place to support first party oembeds (where the provider supports oembeds natively), Embed.ly oembeds (where they built support for a pile of additional content providers), and "Fauxembeds (where we build our own embed providers for sites which do not support it). The oEmbed Proxy is highly extensible and makes it easy to add additional oEmbed providers.

117 |
118 | 119 |
120 |

Lunchbox Utilities for creating social cards and embeds

121 |

Lunchbox is a combination of several tools used at NPR for creating social media cards: a watermarking tool, quote card generator, and fact list image creator.

122 |
123 |
124 | 125 | 126 |
127 |
128 |

Mobile Apps

129 |
130 |

WBUR Listen App

131 |

WBUR is unable to publicly open source the code for its mobile app. However, they are more than happy to share the code with anyone who works in public media. Just contact David Moore or Will Smith (available on the #public-media-kitchen Slack channel).

132 |
133 |
134 | 135 | 136 |
137 |
138 |

Design Systems

139 |
140 |

Hypothesis-Driven Design From NPR Visuals

141 |

A guide to creating immersive storytelling projects on editorial teams, from conception to publication.

142 |
143 |
144 | 145 | 146 |
147 |
148 |

Marketing Methodologies / Case Studies

149 |
150 | 151 |
152 |
153 |

Analysis

154 |
155 |
156 |
157 |

Live Blogs

158 | 159 |
160 |

Scribble Live: Commercial liveblog tool

161 |

Used by MPR News. Has generally been a no fuss hosted service though there have been some speed bumps getting https setup properly.

162 |
163 | 164 |
165 |

Sourcefabric Live Blog: Opensource live blog

166 |

Based on OSS Superdesk CMS.

167 |
168 | 169 |
170 |

Slack Live Blog Slack-based live blog

171 |

OSS project that uses Rails 4.2 and the slack-api gem to generate a live blog fed from a Slack channel. Does not appear to be actively maintained.

172 |
173 | 174 |
175 |

Live Coverage Forms For (and From) the Immediate Future: SRCCON 2017 session on live events coverage

176 |

A deck about—and some examples of—experiments around live event coverage. Most of the software listed was not opensource or commercially available at the time of the presentation.

177 |
178 |
179 |
180 | 181 | 182 | -------------------------------------------------------------------------------- /media/pmk_logo-red.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/PublicMediaKitchen/toolkit/6d57965a65c01dba41d8bce4b090e62ed461bda8/media/pmk_logo-red.png -------------------------------------------------------------------------------- /media/pmk_logo-red_300w.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/PublicMediaKitchen/toolkit/6d57965a65c01dba41d8bce4b090e62ed461bda8/media/pmk_logo-red_300w.png -------------------------------------------------------------------------------- /pmk-styles.css: -------------------------------------------------------------------------------- 1 | @import url('https://fonts.googleapis.com/css?family=Archivo+Narrow|Source+Serif+Pro|Space+Mono'); 2 | 3 | body { 4 | background-color: #F0F0F1; 5 | font-size: 1em; 6 | line-height: 1.4em; 7 | } 8 | 9 | h1, h2 { 10 | font-family: 'Archivo Narrow', sans-serif; 11 | color: #FF5142; 12 | padding-left: 15px; 13 | } 14 | 15 | hr { 16 | border: 0; 17 | height: 1px; 18 | background-image: linear-gradient(to right, rgba(0, 0, 0, 0), #292C45, rgba(0, 0, 0, 0)); 19 | } 20 | 21 | h3 { 22 | font-family: 'Space Mono', monospace; 23 | text-transform: uppercase; 24 | font-weight: 200; 25 | color: #292C45; 26 | padding-left: 15px; 27 | margin: 2em auto 0; 28 | line-height: 1.5em; 29 | } 30 | 31 | h4 { 32 | font-family: 'Space Mono', monospace; 33 | font-weight: 700; 34 | color: #292C45; 35 | font-size: .75em; 36 | padding-left: 15px; 37 | } 38 | 39 | p { 40 | font-family: 'Source Serif Pro', serif; 41 | color: #292C45; 42 | margin: 0em auto 0em; 43 | padding: 15px; 44 | } 45 | 46 | a { 47 | color: #4C7DE4; 48 | text-decoration: none; 49 | } 50 | 51 | .main { 52 | max-width: 1024px; 53 | margin: 0 auto; 54 | } 55 | 56 | a:visited { 57 | color: #20719F; 58 | } 59 | 60 | img.logo { 61 | display: block; 62 | margin: auto; 63 | } 64 | 65 | .intro { 66 | margin: 1em 5em 0; 67 | } 68 | 69 | .category { 70 | margin: 0 5em; 71 | } 72 | 73 | .listing { 74 | max-width: 900px; 75 | margin: 0 5em 3em; 76 | line-height: 1.2em; 77 | } 78 | 79 | .listing:last-child { 80 | margin: 0 5em 0; 81 | } -------------------------------------------------------------------------------- /potluck-framework/README.md: -------------------------------------------------------------------------------- 1 | # Public Media Potluck 2 | 3 | ## What is it? 4 | **potluck:** A semiannual conference or set of workshops where attendees come together for a few days to share, collaborate, and talk about products they've worked on or plan to work on. [more info](potluck.md) 5 | 6 | **potluck calls:** A biweekly phone call where attendees dial in to talk and listen about specific topics. [more info](phonecall.md) 7 | 8 | ## Who can attend 9 | Anyone who is working in a hands-on capacity on a product or software development team at a public media organization. This is for people on the ground who make the design mockups, create roadmaps, and write code. 10 | 11 | Potluck is designed as a conversation between product teams. To ensure that value, we have to protect it from commercial interests and sales pitches. There may be third parties interested in attending the calls or conference, but unless they are directly involved in public media, it's not recommended that they attend. 12 | 13 | ## Who can host 14 | Anyone can host, but our goal is to rotate the location so that attendees have a chance to visit across the US. 15 | 16 | Hosts are expected to: 17 | * [organize and facilitate](facilitator.md) all calls leading up to the potluck they're hosting. 18 | * organize communications around the calls 19 | * communicate any logistics about the potluck leading up to the potluck 20 | 21 | ## Session suggestions 22 | The following was collected from survey results after the January Potluck: 23 | * CMS: the design of, the stack, the api, etc. 24 | * Lightning talks: 25 | * whiteboard your stack 26 | * what makes up your team? 27 | * disaster recovery scenarios (ie: broadcast signal went down, what now?) 28 | * how to write maintainable one-off code 29 | * sharing actual code & patterns 30 | * demos of products 31 | * Mobile apps 32 | * Analytics on how new products or features are performing 33 | -------------------------------------------------------------------------------- /potluck-framework/facilitator.md: -------------------------------------------------------------------------------- 1 | # Facilitator Guide 2 | As a facilitator, it's your job to lead the discussions or workshops and ensure that the group is engagged. 3 | 4 | ## responsibilities 5 | * set the agenda and structure for the session 6 | * ensure that the discussion is inclusive everyone feels ready to participate 7 | * ensure that everyone who wants to talk gets a chance to talk. That includes reminding someone who has been speaking too long that some conversations can be conducted offline. 8 | * think of the outcome of the session: what do you want the attendees to leave with? 9 | 10 | ## tips 11 | * have a clock or watch handy to keep track of time 12 | * the facilitator should not be the note-taker 13 | * [how to do a break-out session](https://facilitation.aspirationtech.org/index.php?title=Facilitation:Break-Outs) -------------------------------------------------------------------------------- /potluck-framework/phonecall.md: -------------------------------------------------------------------------------- 1 | # Potluck Calls 2 | These biweekly calls serve as a way to keep the Public Media Kitchen community up to date with what everyone is working on, thinking about, or planning. They should occur at the same time every other week and tackle different agendas each time. Topics can be a more in-depth discussion about things that came up during the Potluck conference, or just things that come during the time between Potlucks. 3 | 4 | Be mindful of both West and East coast participants: schedule in a 9am-5pm slot for both zones. KPCC found that Tuesday 9am PST worked. 5 | 6 | The goal of the call is for discussion and not fussing with logistics, so ideally the calls are audio only and don't require video. If visuals are needed for context, send a link to the visuals beforehand to all the interested parties so that they can view them on their own screen. 7 | 8 | ## Hosting calls 9 | The hosting group for the upcoming potluck is expected to also host calls leading to the potluck. 10 | 11 | ## Instructions 12 | 13 | ### a week before the call 14 | * decide on a topic for the call 15 | * try your best to diversify the talks as much as possible -- keeping them open to devs, designers, PMs, etc. 16 | * recruit 1-3 leaders for the talk (#public-media-kitchen is your best bet) 17 | * send an email to everyone on the contact list (BCC please) with the call topic or agenda 18 | * post an @here message in the #public-media-kitchen slack channel in npr+friends 19 | * if there are specific people you want to lead a talk, send a separate email to them to confirm that they can do it 20 | 21 | ### a day before the call 22 | * send a reminder email to everyone on the contact list with any updates to the agenda (BCC please) 23 | * send a reminder email to anyone who will be leading a talk and make sure there are links on the etherpad to anything that requires context 24 | * message a @here reminder to the #public-media-kitchen slack channel 25 | 26 | ### the call 27 | KPCC uses [freeconference.com](https://freeconference.com). Whatever service you use, make sure to: 28 | * Turn off entry and exit chimes 29 | * Turn off name announce 30 | * Put it in QA mode or some other mode so that everyone except the host is muted by default but participants can unmute themselves. 31 | * Dial into the conference call five minutes beforehand to make sure all audio is set up 32 | * Remind participants of how to unmute (for example, *6) 33 | * Make sure the designated note-taker is ready on the etherpad 34 | * Make sure the facilitator can see the etherpad for any questions that come up 35 | * At the start of _every call_, be sure to *explicitly and clearly introduce* the PMK, the calls, the role of the calls, the topic, and each speaker (first and last name, org, title). 36 | * In other words, avoid _too much_ informality and any hints of exclusivity and/or clubbiness. 37 | * Before the first speaker, address any housekeeping concerns (e.g., upcoming potluck). Repeat those concerns at the very end of the call. 38 | 39 | ### after the call 40 | * have the note-taker revise or clean up the notes 41 | * update the Call Notes Archive (below) with a link to the notes 42 | 43 | 44 | ## Call Notes Archive: 45 | * [12/19/2017](https://etherpad.scprdev.org/p/PublicMediaPotluck_Call-121917): fundraising and potluck conference agenda 46 | * [02/13/2018](https://etherpad.scprdev.org/p/PublicMediaPotluck_Call-02132018): open source software 47 | * [02/27/2018](https://etherpad.scprdev.org/p/PublicMediaPotluck_Call-02272018): database architecture 48 | * [03/13/2018](https://etherpad.scprdev.org/p/PublicMediaPotluck_Call-03132018): js cage match (React, Vue, Angular) 49 | * [03/27/2018](https://etherpad.scprdev.org/p/PublicMediaPotluck_Call-03272018): js cage match 2 (Ember, isomorphic React) 50 | * [04/10/2018](https://etherpad.scprdev.org/p/PublicMediaPotluck_Call-04102018): mobile app development 51 | * [04/24/2018](https://etherpad.scprdev.org/p/PublicMediaPotluck_Call-04242018): css management 52 | * [05/08/2018](https://etherpad.scprdev.org/p/PublicMediaPotluck_Call-05082018): automated tests 53 | * [05/22/2018](https://etherpad.scprdev.org/p/PublicMediaPotluck_Call-05222018): data visualizations 54 | * [10/23/2018]: 55 | * [11/05/2018](https://etherpad.scprdev.org/p/pmk-call-2018-11-05): project management in public media organizations 56 | * [12/04/2018]: elections fun! 57 | * [05/14/2019](https://etherpad.scprdev.org/p/pmk_call_05-2019): KQED potluck feedback and CRMs 58 | * [06/11/2019](https://etherpad.scprdev.org/p/PMK-call_06-11-19): Public Radio Incubation Lab and core web technologies 59 | -------------------------------------------------------------------------------- /potluck-framework/potluck.md: -------------------------------------------------------------------------------- 1 | # Potluck Conference 2 | Based on survey results, we've found out that the following worked well for most attendees: 3 | * two day conference 4 | * Thursday and Friday worked out best for most attendees 5 | * 3 x 1.5 hour sessions per day 6 | * 30 minute breaks between sessions 7 | * reminders or tips on how to prep for the sessions beforehand 8 | * off-site dinner the first day of the potluck 9 | * on-site light breakfast, lunch, and coffee throughout the day 10 | * etherpad for "after hours" meetups or suggestions (last day dinner plans, board games during lunch, studio tours, etc.) 11 | 12 | 13 | For an example of how the day was structured, refer to the [January Potluck Schedule](https://publicmediakitchen.github.io/toolkit/public-media-potluck-january-2018.html) 14 | 15 | In picking a hosting city for Potluck Conferences, we should be mindful to pick from different parts of the US. For example, since there was already one on the West Coast, it's good to plan one on the East and then one in the Midwest. 16 | 17 | 18 | ## Instructions: 19 | ### at least 3 months before potluck 20 | * agree on dates for the potluck 21 | * agree on venue for the potluck 22 | * book the venue for the potluck if it needs to be booked far in advance 23 | 24 | ### at least 2 months before potluck 25 | * decide on a headliner session or overall topic 26 | * change the link and blurb on [Public Media Kitchen Toolkit](https://publicmediakitchen.github.io/toolkit/) to refer to the new potluck. Date, location, and a new page [like this](https://publicmediakitchen.github.io/toolkit/public-media-potluck-january-2018.html) 27 | * put as much logistical information as possible on the upcoming potluck page: 28 | * address/location 29 | * time and dates 30 | * headliner session or topic umbrella 31 | * lodging suggestions 32 | 33 | ### 3 weeks before the potluck 34 | * put the daily schedule onto the potluck page 35 | * put out last call for attendees to potluck 36 | * decide who will be the note-takers for each session 37 | * talk to any vendors and nail down food & coffee supply 38 | 39 | ### 1 week before the potluck 40 | * finalize attendee list 41 | * send an email confirming the potluck schedule & ask for dietary restrictions 42 | * send an email to anyone leading a session to confirm they have what they need 43 | * confirm off-site dinner menu if necessary 44 | 45 | ### two days before the potluck 46 | * send an email re-iterating any logistics around the location of the Potluck (parking and walking tips, how to get into the building) 47 | * confirm any dining arrangements with restaurants if necessary 48 | * confirm all the rest of the food & coffee supplies 49 | * confirm that the conference site is set up (screens, dongles, wifi, chairs, snacks, water) 50 | 51 | ### the potluck 52 | * act as the default facilitator for any sessions 53 | * communicate any logistics around dining 54 | 55 | ### after the potluck 56 | * compile all the notes and link to them from the potluck's schedule page 57 | * send out a survey about the success or results of the conference 58 | * collect survey results after 2 weeks 59 | * share an overview of the results in an email with the conference attendees 60 | 61 | ## Protips: 62 | * Put a breakfast slot in the schedule so that people planning to fly in day-of have a margin to work with. 63 | * During Day 1's opening, collect or write down high level goals of the conference. 64 | * It's easy to design hands-on coding sessions for developers, but product designers and product managers also would like hands-on sessions. -------------------------------------------------------------------------------- /public-media-potluck-january-2018.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Public Media Potluck - January 2018 6 | 7 | 8 |
9 |
10 | 11 | 12 | 13 |

Public Media Potluck - January 2018 Logistics

14 |

Build the next generation of Public Media together at the two day "Public Media Potluck". Share ideas, projects, and stories of success and failure with different public media product teams from around the country. Have a bigger impact by tackling issues facing public media organizations of all sizes and types of digital sophistication. This collective, coordinated effort will ensure you're solving problems that benefit more than just "our team", while also reaping the same efficiency benefits from other products and teams. The goal is to stop reinventing the wheel, at every program and station, to work together more, and to share technology.

If you'd like to contact the team organizing the Potluck, the best way to do that is via this form.

15 |
16 | 17 | 18 |
19 |
20 |

Where and When

21 | 22 |

January 25-26, 2018

23 |

The Crawford Family Forum at KPCC - Southern California Public Radio
474 S Raymond Ave
Pasadena, CA

24 | 25 |
26 | 27 | 28 |
29 |
30 |

Schedule

31 |

32 | informal events are on this etherpad 33 |

34 |

Thursday January 25, 2017

35 |

36 | 9:00 - 9:45
37 | Breakfast and Welcome 38 |

39 |

40 | 10:00 - 11:30
41 | Smart Speakers Skills Design
42 | notes 43 |
44 | Concentrating on Alexa, each organization should come prepared to answer these questions: 45 |

46 | 52 |

53 | 12:00 - 01:00
54 | Lunch 55 |

56 |

1:30 - 3:00
57 | Failures show and tell 58 |
59 | notes 60 |
61 | Let’s share war stories about things we did that maybe we shouldn’t have done. Or things that went horribly wrong. Each organization should come prepared to talk for 10 minutes about one of their failures. 62 |

63 |

3:30 - 5:00
64 | Tools, tips, and tricks breakout session
65 | Tips and tricks for developers
66 | Tips and tricks for design and product managers 67 |
68 | We’re going to divide into two groups: 1.) product designers and product managers, 2.) developers. Within these groups, each person should be prepared to talk about at least one tool and one tip or trick that they use on a daily basis.
69 |

70 |

5:00 - 5:15
71 | Closing Day 1 72 |

73 |

6:00 - 8:00
74 | Dinner
75 | Sponsored by Greater Public 76 |

77 |
78 |
79 |

Friday January 26, 2017

80 |

9:00 - 9:45
81 | Breakfast

82 |

10:00 - 11:30
83 | Let's overhaul the site!
84 | notes
85 | WHYY and KPCC both recently “completed” an overhaul of their website. Rebecca Smith, Katie Briggs, and Vijay Singh lead the discussion with how they approached their redesigns using a user first design process. This session will also touch upon CMS interface and data mapping, and establishing a product development process within our organizations. 86 |

87 |

12:00 - 01:00
88 | Lunch 89 |

90 |

1:30 - 3:00
91 | Smart Speakers Skills Build
92 | notes
93 | Building on learnings from our earlier session about smart speakers, we’re going to build a skill! Anyone who wants to give building a skill a shot should already have an AWS account set up, including the AWS cli tool. Make sure you install the requirements and complete the setup steps prior to this session. README 94 |

95 | Not Just Audio: How to visually jazz up your skill and promote smart speakers
96 | notes
97 | How do you promote smart speaker skills on a show or audio spot? What are some creative ways to get your skill picked up by users? How can your skill translate to the Amazon Echo Show or Echo Spot? What are some cool ideas that combine visuals with your audio-first skill? 98 |

99 |

3:30 - 5:00
100 | Show me the money!
101 | notes
102 | Most of us are from member-funded organizations. What are some processes that remove friction from the donation process? What are some hurdles to using apple pay for donations? Can people use the Alexa skill to donate? Come prepared to talk about your membership drive process and experiments you’ve tried or would like to try. 103 |

104 |

5:00 - 5:15
105 | Goodbye 106 |

107 |
108 | 109 | 110 |
111 |
112 |

Lodging

113 | 114 |

Hotels not far from the venue include:

115 |

GreenTree Pasadena Inn
Website: https://www.greentreepasadenainn.com/

116 |

The Westin Pasadena
Website: http://www.starwoodhotels.com/westin/property/overview/index.html?propertyID=1453&language=en_US

117 |

Sheraton Pasadena Hotel
Website: http://www.sheratonpasadena.com/

118 |

Courtyard Marriott
Website: http://www.marriott.com/hotels/travel/laxot-courtyard-los-angeles-pasadena-old-town/

119 | 120 |
121 | 122 | 123 |
124 |
125 |

Places of Interest

126 | 127 |

KPCC’s offices are in Pasadena, which is conveniently located if you want to check out the city or what the rest of LA has to offer.

128 |

Sticking to this side of town, Old Town Pasadena is a 15 minute walk from the station and has two great independent coffee shops and some decent restaurants.

129 |

A 10 minute Lyft ride away is the Huntington Botanical Gardens (huntington.org) which is a must visit if you want to take advantage of the good weather and have a few hours to kill.

130 |

If you’re willing to drive 20 minutes, you can get to the heart of the San Gabriel Valley, known for its vast array of Chinese restaurants. If you want to explore regional Chinese cuisine, this is where to do it.

131 |

A 30 minute train ride on the Gold line will bring you into downtown LA, straight into a historic train station as well as many walkable spots like Grand Central Market (food hall), Chinatown, and Olvera Street.

132 | 133 |
134 | 135 |
136 | 137 | 138 | -------------------------------------------------------------------------------- /public-media-potluck-january-2019.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Public Media Potluck - 2019 6 | 7 | 8 |
9 |
10 | 11 | 12 | 13 | 14 |

Public Media Potluck - 2019 - San Francisco

15 |

Build the next generation of Public Media together at the two day "Public Media Potluck". Share ideas, projects, and stories of success and failure with different public media product teams from around the country. Have a bigger impact by tackling issues facing public media organizations of all sizes and types of digital sophistication. This collective, coordinated effort will ensure you're solving problems that benefit more than just "our team", while also reaping the same efficiency benefits from other products and teams. The goal is to stop reinventing the wheel, at every program and station, to work together more, and to share technology.

16 |

We are in the process of formulating what topics to focus on for this meetup. Please use contact form below to give us suggestions!

17 |

If you'd like to contact the team organizing the Potluck, the best way to do that is via this form.

18 |
19 | 20 | 21 |
22 |
23 |

Where and When

24 |

25 | January 17-18, 2019 (Thursday-Friday) 26 |

27 |

Please RSVP by Friday, December 21 via the Evite

28 |

29 | Note: Monday, January 21 is Martin Luther King Jr holiday for those who may want to turn the trip into a long weekend in San Francisco. 30 |

31 |

32 | KQED
33 | 2601 Mariposa Street
34 | San Francisco, CA 94110 35 |

36 |

 

37 |
38 | 39 |
40 |
41 |

Cost and tickets

42 |

It's 100% free! But we still need you to RVSP by the deadline of Friday, December 21 here: http://evite.me/ETeBj55ndJ

43 |
44 | 45 |
46 |
47 |

Getting There

48 | 49 |

If you're flying in, both SFO and OAK are accessible to public transportation. Nearest BART Station to KQED is Mission 16th Street.

50 | 51 |

San Francisco Internation Airport (SFO)

52 | 55 | 56 |

Oakland Internation Airport (OAK)

57 | 60 | 61 |
62 | 63 |
64 |
65 |

Schedule (tentative):

66 |

Thursday January 17, 2019, 8:30 – 4pm program, group dinner out

67 |

68 | Analytics and Business Intelligence: The Path towards Data-Driven Newsrooms 69 |
A discussion of how to move beyond pageviews and spreadsheets, and into regularly-delivered metrics that keep your colleagues informed, and lead to newsroom success. 70 |

75 |

76 |

77 | Process! Process! Process! 78 |

86 |

87 | 88 |

Friday January 18, 2019, 8:30 – 4pm

89 |

90 | Smart speakers 91 |

97 |

98 |

99 | Earnest Collaboration
100 | What shared problems/challenges do we all have that we'd like collaboration on? Propose a topic, or join a topic in a breakout session here. 101 |

102 | 103 | 104 |
105 | 106 |
107 |
108 |

Lodging

109 |

Please note that KQED, 2601 Mariposa Street between Bryant and York Streets in San Francisco's Mission District, is located in a primarily residential neighborhood, and there are no hotels within close walking distance. Hotels downtown or South of Market (SOMA) are about 15-20 minutes by taxi or rideshare.

110 |

If you want to try to stay closer to KQED, we recommend trying AirBNB.

111 |

Downtown SF: Hotel Zetta, Kimpton Sir Francis Drake

112 |

There is one boutique hotel that is a little closer than downtown, the Parker Guest House. As of Dec 11 they still had rooms available, prices per night start at $199.

113 |

If you are entering addresses in GPS for streets in the Mission District or Downtown that are named with numbers (for example 17th Street), be sure you enter Street and not Avenue. You will end up in a very far away neighborhood if you accidentally use Avenue!

114 |
115 | 116 | 117 | 118 |
119 |
120 |

Places of Interest

121 |

Trip Advisor - Things to Do in San Francisco

122 |

Trip Advisor - Top Things to Do in the Mission District

123 |

FunCheap SF

124 |

Head to the 3rd Floor Lunchroom at KQED for a view of the new Salesforce Tower! (fog permitting) 125 |

This event conflicts with the Thursday evening dinner, but Thursday, Jan 17, 5-10pm is Free Museum & Gallery Crawl: Yerba Buena Third Thursdays | SoMa 126 | downtown.

127 |

Food

128 |

Light breakfast and box lunches will be provided at KQED on Thursday and Friday. Please let us know about any food allergies via the Evite, by the December 21 RSVP deadline.

129 |

Below are some local eateries:

130 |

Yelp's Top 10 Restaurants Close to KQED

131 |

Great nearby market with takeout Gus's Community Market 2111 Harrison St. at 17th Street (two-three blocks)

132 |

Safeway and some fast-food restaurants at Potrero Center, a two-block walk from KQED at 16th Street and Potrero
133 |

134 | 135 |
136 |

Drink

137 | 138 |

Closest Dive Bar to KQED: Mission Hill Saloon 491 Potrero Ave at Mariposa

139 | Some Other Favorite KQED Drinking Spots Within Walking Distance:
140 | The Homestead 2301 Folsom St at 19th Street
141 | Asiento 2730 21st St at Bryant Street
142 | Southern Pacific Brewing 620 Treat Ave off 20th Street
143 | Jay 'n Bee Club 2736 20th St at York St.
Il Pirata 2007 16th St between Potrero and Utah Streets
144 | Double Play Bar & Grill – Sports Bar 2401 16th St at Bryant
145 |

146 | 147 |
148 | 149 |
150 | 151 | 152 | -------------------------------------------------------------------------------- /public-media-potluck-june-2018.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Public Media Potluck - January 2018 6 | 7 | 8 |
9 |
10 | 11 | 12 | 13 |

Public Media Potluck - June 2018 - Boston

14 |

Build the next generation of Public Media together at the two day "Public Media Potluck". Share ideas, projects, and stories of success and failure with different public media product teams from around the country. Have a bigger impact by tackling issues facing public media organizations of all sizes and types of digital sophistication. This collective, coordinated effort will ensure you're solving problems that benefit more than just "our team", while also reaping the same efficiency benefits from other products and teams. The goal is to stop reinventing the wheel, at every program and station, to work together more, and to share technology.

15 |

This particular meetup will focus on the theme of content management and distribution: CMS, APIs, RSS, audio management, etc.

16 |

If you'd like to contact the team organizing the Potluck, the best way to do that is via this form.

17 |
18 | 19 | 20 |
21 |
22 |

Where and When

23 |

June 14-15, 2018

24 |

College of Communication - Boston University
Room 209
640 Commonwealth Ave
Boston, MA

25 |
26 | 27 |
28 |
29 |

Cost and tickets

30 |

It's 100% free! But we still need you to please register and get tickets.

31 |
32 | 33 |
34 |
35 |

Getting There

36 | 37 |

If you're flying in, book a flight to Boston's Logan Airport. (Landing in Portland, Hartford, or Providence is certainly possible, but not recommended.) Public transport from Logan to Kenmore Square exists but -- fair warning -- is less than ideal (shuttle to Blue Line, Blue Line to Green Line OR Silver Line to Red Line to Green Line). A cab is about $30.

38 |

Those traveling up the Acela Corridor will arrive at South Station. From there, you can take the Red Line to the Green line. If you're taking the train from the North Shore, New Hampshire or Maine, you'll arrive at North Station. There is a Green Line stop right in the station.

39 | 40 |
41 | 42 |
43 |
44 |

Schedule (subject to change!):

45 | 46 |

Thursday June 14, 2018

47 | 48 |

8:30-9:30 - Check-in, Breakfast and Welcome

49 | 50 |

9:45-10:45 - Whiteboard Your Stack

51 |

52 | Please bring a single image diagramming your stack. Let us know how it works and how well it works. Given the conference theme, try to focus on content distirubtion: CMS, APIs, RSS, etc. If that's not your cup of tea, please join us for... 53 |

54 | 55 |

9:45-10:45 - Whiteboard your Team & Process

56 |

57 | What's your team look like? Do you do Agile/Scrum? What are your regular meetings? What works well for your team? What are some issues? 58 |

59 | 60 |

11:00-12:00 - Audio pipeline

61 |

62 | How does your on-demand audio get from the soundboard to the listener's ears? What are you tips/technologies you can offer? What are your pain points? 63 |

64 | 65 |

12:00-1:00 - LUNCH

66 | 67 |

1:30-3:00 - PODCASTS

68 |

69 | Looking to jumpstart your podcast division? Hoping to broaden the reach of your podcasts? We'll bring in a few outside speakers to help answer these questions and follow with an open discussion of the topic. 70 |

71 | 72 |

3:30 - 5:00 - CMS

73 |

74 | What's lacking in your CMS? What do you like? What kind of community is behind it? Are you thinking about switching? 75 |

76 | 77 |

5:00-5:15 - Closing Day 1

78 |

6:00-8:00 - Reception @ WBUR

79 |

80 | Beer, wine, food - sponsored by Greater Public and WBUR 81 |

82 | 83 |
84 | 85 |

Friday June 15, 2018

86 |

8:30-9:30 - Breakfast

87 | 88 |

9:45-10:45 - ELECTIONS

89 |

90 | This fall's elections will likely be the most closely watched mid-terms in recent memory. What is your organization doing to prepare? What APIs are you using? What libraries? What code/ideas/tips can you share? 91 |

92 | 93 |

11:00 - 12:00 - It's a Disaster

94 |

95 | Tell us about your worst, latest and/or most interesting catastrophe. What happened and why? What have you done to prevent this from happening again? What are your pre-existing strategies to prevent disasters: monitoring, call schedule, paging, etc.? 96 |

97 | 98 |

12:00-1:00 - LUNCH

99 | 100 |

1:30-3:00 - LIGHTNING TALKS

101 |

102 | Bring your best 5 minutes and your best slides! Tell us about a new technology, vendor, technique, language or side-project that you like -- and that you think others in public media should know about. In particular, we'd love to hear about content management and distribution topics: CMS, APIs, audio tools, etc. 103 |

104 | 105 |

3:30-5:00 - Exploring Areas for Collaboration

106 |

107 | The rubber meets me the road. Let's agree upon areas and technologies on which we can collaborate, and start sketching out a plan forward! 108 |

109 | 110 |

5:00-5:15 - Goodbye

111 | 112 |
113 | 114 | 115 |
116 |
117 |

Lodging

118 | 119 |

Hotels not far from the venue include:

120 | 129 |

There are many other hotels and B&B's in the area as well as AirBnB, etc. The Red Sox are out of town that week, and college graduation season will be over, so you should have plenty of lodging options.

130 |
131 | 132 | 133 |
134 |
135 |

Places of Interest

136 | 148 | 149 |
150 |

Food

151 | 152 |

Kenmore/BU Area

153 | 173 | 174 |

Further Away (but worth the trip)

175 | 192 | 193 |

Food Trucks

194 |

Boston Food Truck Finder

195 | 196 |
197 |

Drink

198 | 199 | 214 | 215 |
216 | 217 |
218 | 219 | 220 | --------------------------------------------------------------------------------