diff --git a/potluck-framework/archive/etherpad/phonecall/PMK-call_06-11-19.html b/potluck-framework/archive/etherpad/phonecall/PMK-call_06-11-19.html
new file mode 100644
index 0000000..78bbfc1
--- /dev/null
+++ b/potluck-framework/archive/etherpad/phonecall/PMK-call_06-11-19.html
@@ -0,0 +1,143 @@
+
+
+
+PMK-call_06-11-19
+
+
+
+
+
+
+
+Public Media Kitchen Community Call | June 11, 2019
Every other Tuesday @ 12pm Eastern - 9am Pacific
*****CALL-IN NUMBER*****
712.775.7031
· *6 to unmute!
______________________________________
Welcome to the call!
ROLL CALL: Who are you? Where are you from? What do you do?
Alan Melson - KERA
Dina Nawas - NPR
Justin Bowers - KERA
Noah Cutter - VPR
Michael Chaplin - NPR
Katie Briggs, Senior Product Designer + Incubation Lab Member – NPR
Kathleen Fleischmann, Web Developer, NPR
Jonathan Butler, VPR & The Incubation Lab
Vijay Singh - SCPR
Liz Berg, Senior Product Manager - NYPR/WNYC
Matthew McClintock, Dev Ops, WBEZ
Renee Thompson, Digital Projects Manager, Capital Public Radio
Katy Kidwell, Front-end Developer, Capital Public Radio
Erin Ozmat, Sr. PM, NYPR/WNYC
David Moore, Developer, WBUR
Kim Thompson, Web Developer, MPR/APM
William Tam, Developer, WNET/Thirteen
Matt Aho, Web Developer, MPR/APM
Dan Newman, Director of Product Design, NPR
Andrea Edstrom, Senior Web Developer and Designer
Veronika Nagy, UX Designer, Capital Public Radio
Lauren Bracey Scheidt, NPR
Liz Danzico, NPR
Andrew Stevenson, Developer, MPR/APM
*****TODAY'S TOPICS*****
Public Radio Incubation Lab
Michael Chaplin (NPR) + Jonathan Butler (VPR)
- What the Incubation Lab has been up to
- Jonathan Butler:
- Blog: https://medium.com/public-radio-incubation-lab
- Vision: Strong public radio network that quickly adapts to new technologies and behaviors.
- NPR got generous funding for yearlong lab.
- Three four-month rotations. Each one has a different theme and team
- First rotation: Exploring ways to deepen engagement on npr.org and other platforms to drive value to stations
- Applications for next lab just went out on 6/10. Link on blog above.
- First group interviewing folks, doing research and surveys. Workshop on design thinking.
- Tons of ideas, big and small. Focus of lab is on ideas that could be driven into NPR's digital roadmap
- What will drive most value in short-term for the whole network?
- Big ideas: Capture more data about NPR's digital visitors, use that data to create informed/personalized calls to action, then drive greater conversion in registration/donations. (TL;DR: More leads, more data for local stations)
- Some work at national level; some work at station level.
- Michael Chaplin:
- Will be doing webinar soon to share findings, viz and prototypes (check PMK slack channel for later details)
- Focus around idea of deepening engagement
- Broken into two facets: Audience-facing and station-facing
- Audience product: How can we deepen user engagement on npr.org?
- Station product: How can we better provide leads to stations? (Some already using/activating NPR One leads, but we could make that process better and easier with more info)
- Building on idea of engagement pyramid we know (Grow > Know > Engage > Monetize/Activate)
- Research:
- Wide range of potential users on npr.org - flyby single-visit users, others who visit many times per day. Similar dynamic on station sites.
- We want to meet everyone at their engagement level.
- Group focus: Leverage user events we can track (data we already have access to) - clicks, time spent on site, frequency of use
- How can we alter experience for those different types of users?
- What can we ask these different cohorts of users to do?
- Example: First-time visitors to npr.org. We'd want to focus on getting them to return to site via high-impact calls to action. Read one more article; listen to one more audio story. Show them something different than what we'd show to other users. Right now we ask everyone to do everything
- Second cohort: 3-4 times weekly. Introduce them to local station. Prominent call to action for localization - streaming, clicks to local site. Next call to action is newsletter subscription.
- Last cohort: 10-15 times per month. Hard call to action to donate to local station.
- What would these look like, and what are technical hurdles/specs to making them happen?
- One tool: Optimizely.com. Looking at it as potential option for this experiential testing.
- Prototyping station lead engagement tool with access to leads, but more robust than current experience on stationconnect.org.
- Access to npr.org users in their market - who they are, what they're viewing, overall engagement level (which cohort they fall into)
- Provide emails - initially from NPR One, but perhaps ultimately from npr.org users as well.
- What types of content are these users viewing? (e.g. politics, international, arts/culture, etc.)
- Avenues for stations to engage with these leads. Many stations would like to do that engagement independently, but want guidance
- Provide resource stack for stations: Best practices, documentation, onboarding copy, KPIs to stations so they can take it on themselves
*****Questions/comments*****
- What is the thinking behind driving first time users to keep coming back to NPR.org vs. introducing them to local station right away, particularly given individual's perception that their local station is NPR?
- - Bigger picture: Idea is to build platform capable of learning more/more personalization; A/B test all of this to determine successes of different simple funnels.
- - Example: Going to nytimes.com for first time provides user experience focused on getting you to read more
- - Local user may go to npr.org for story and isn't even thinking about local station. We need to learn more via testing.
- - WNYC: A lot of users were using site to stream audio, and staying for long periods of time. NPR.org audience is coming from many different places to do many different things, and often leave quickly.
- - We want to do lots of testing to see what gets those flyby users to stick around.
- - This could look like a matrix of messages going to different users based on their behavior/frequency
- What advantages do you see for Optimize.ly vs Google Optimize?
- - One pro is that NPR already has relationship with Optimizely, but we're looking at all options. Need to know what level of service to expect from our vendor
- There is an in-development NPR/PBS (via CPB) 'public media login' system in the pipe. Do we see how this lead generation etc might integrate with that?
- - Digital Infrastructure Group SSO work - as NPR builds digital network and works that in, it would conceivably carry over to station sites as well
- - What can we do *right now* to get this going?
- - If we can build profile about user on multiple platforms (npr.org, pbs.org, station sites, apps), that will benefit everyone.
- - Every tech upgrade will help this process and continued growth.
Are you looking at/have you investigated engagement opportunities more 'offline'? in-person events etc.
- - That's something to look at and fold into our larger efforts to build more robust user profiles - and data to share w/stations
Core Website Technologies
Justin Bowers (KERA)
- KERA is beginning planning phase to consolidate a "constellation of sites" into a single larger site. Looking at all options, and wanting to see what others are using to help provide an optimal experience.
- What are you using?
- WBUR: Headless WordPress.
- Reporters like it - does pretty much what is needed.
- Actual website runs on node.js and React. May be over-engineered but gets us where we need to go
- Persistent player on every page.
- Connecting WP and frontend is an API built on Laravel (Rails/PHP)
- Built a Laravel tool to help people design page layouts (homepage, internal pages for podcasts, verticals, etc.)
- Preferable to giant monolithic WP/CMS page
- - WNYC: Just launched part of a redesign for Gothamist
- - Moved to new CMS - Wagtail
- - Hope to expand to other properties
- - KLRU: Using Node and Express
- - CMS: Contentful - APIaaS - templated content.
- - Can define content elements in granular fashion to build pages - each is type/attribute
- - Super customizable and easy to use on developer end
- - WNET: WordPress
- - WP Multi-Site.
- - Eventually moving to headless approach similar to WBUR
- - WP strength is admin - and vast user/dev base
- - MPR: React front end.
- - Tried to implement server-side rendering but ran into issues
- - Now using next.js build tool - working very well so far
- - GraphQL API backed by a good ol' CRUD Rails app and Elastic Search (GraphQL has been a hit with our devs)
- - I'm excited about Gatsby too, but ultimately we leaned toward Next.js to ensure that we can load a large volume of content quickly. Finally found the article that originally advised me to do that (https://blog.jakoblind.no/gatsby-vs-next/ ).
- - NPR: In case you missed NPR's "Future of Digital Publishing" webinar from last week, the recording is available on NPRStations.org at https://www.nprstations.org/policiesandin/memberadmi/stationcompact/digital.cfm. TL;DR: NPR is in the final stages of exploring a modern CMS that will replace both Core Publisher AND Seamus (NPR's homegrown CMS), with more details to come later this summer.
- What are you looking at for the future?
- KLRU: Very interested in next.js. Also looking at Gatsby static site builder.
- NPR: One of the platforms our devs have been impressed with is sanity.io. It would be great for a Gatsby site.
Online Pledge Forms + Call Center
Justin Bowers (KERA)
- Who do you use?
- What are the options?
*****Questions/comments*****
*****COMING UP*****
Next call – June 25th
Got an idea for a future topic for a call, or something we should consider tackling during a meetup? Let us know below, or fill out this form: https://goo.gl/forms/JTtFNbSduotdHGhj2
Potluck in Dallas (KERA), July 11-12
Public Media Developers Slack: https://pubmediadevs.slack.com/
- Contact Jess at jsnyder@weta.org if you need an invite
NPR Digital Day 2019, Sept. 11 in New Orleans (immediately preceding ONA19)
- Registration now available: http://digitalday2019.nprpresents.org
- Soliciting presenter recommendations and topic ideas through June 14th to DigitalDay@npr.org
- Audience will be digital journalist-heavy, but we'd love to have strong representation of public media technologists, too.
- Questions? Ask Dan Newman (dnewman@npr.org)
+
+
diff --git a/potluck-framework/archive/etherpad/phonecall/PublicMediaPotluck_Call-02132018.html b/potluck-framework/archive/etherpad/phonecall/PublicMediaPotluck_Call-02132018.html
new file mode 100644
index 0000000..4a89da9
--- /dev/null
+++ b/potluck-framework/archive/etherpad/phonecall/PublicMediaPotluck_Call-02132018.html
@@ -0,0 +1,143 @@
+
+
+
+PublicMediaPotluck_Call-02132018
+
+
+
+
+
+
+
+Public Media Potluck Community Call | February 13, 2018
Every other Tuesday @ 12pm Eastern - 9am Pacific
*****CALL-IN NUMBER*****
1-712-832-8328.
- Access code: 170 4041
- *6 to unmute!
______________________________________
Welcome to the call!
ROLL CALL: Who are you? Where are you from? What do you do?
- Louise Yang / KPCC / Lead Software Engineer
- Rebecca Smith / WHYY / Digital Product Manager
- Katie Briggs / NPR / Product Designer
- Liz Danzico / NPR / Creative Director
- Justin Bowers / KERA / Sr. Digital Developer/Designer
- Chris Lewis, WAMU
- Liz Berg, NYPR / Sr. Product Manager
- Dave Moore / Will Smith / Tiffany Campbell / John Davidow, WBUR
Jenna note: I will be in mostly listen mode, if that's ok. I commute at 9 a.m. You guys heard me talk briefly about the campaign funding scraper that our dev wrote and shared on KUOW's github. That's the only current open code we have, but aim to share more in the near future. We lean on the UW Co-Motion lab for guidance around licensing (we're lucky to have that IP/copyrights resource)
*****TODAY'S TOPICS*****
Open Source Software
- Do you practice it? Do you use it? Do you produce it? Why or why not?
- How do you practice it?
- What concerns does your org have about it?
- What license are you using?
- How do you sustain it?
Open Source Ember -- Brian (NYPR)
* Default to open-source
* Unless something is sensitive
* Publishing CMS (very old and tangled), so no value in open-sourcing
* Open-source Ember
* Point: It’s going to be downloaded to browser anyhow (Javascript app)
* Making repo private doesn’t protect code
* What is the argument to make it private?
* Client-side stuff is all open-source
* “We use a build system (CircleCI) to build front-end static stuff”
* Attack vectors (under review)
* Also _use_ peoples’ open-source stuff
* If reasonable, submit pull requests to help maintainers (contribute)
* Louise: From business side, non-developers feel “code is money”
* From a developer standpoint, developers are what cost money - not code, per se
* Hard to explain to business types
* Brian: They’ve had some success explaining it in community terms, non-profit mission, “free labor” due to fixes and improvements
* Benefit from patches and improvements
Past OS Project Learnings & Future Plans -- Louise (KPCC)
* KPCC Open-source Software
* What we have done, our plans, etc.
* Historically, our standard mode of operation is to keep everything in repo public.
* Code quality - “another set of eyes”
* No sensitive data/secrets
* Current
* 1. Outpost CMS (Ruby on Rails)
* Designed for newsroom w/radio station attached
* Audio management, news.
* Tied to our data model and structure, so it isn’t easy for other organizations to use.
* 2. AssetHost v1
* Image management project w/tie-in to Outpost
* More successful - decoupled with Outpost (uses plug-in).
* Still designed for our use
* Recently v2 came out
* Better decoupled
* Docker images
* Documentation and support aren’t great, so momentum was lost.
* 3. Stream Machine
* Some people use it, or pay a vendor to use it.
* Hosts digital version of broadcast stream.
* Not great documentation for provisioning or development
* 3rd-party companies provide provisioning and support
* Problem is that there is no good support plan for issues
* We host it in-house
* Bugs with stream rewinding, cut-outs, etc.
* ‘Stream Guys’ has run into the same problems, w/no idea of who would tackle the problem and fix it
* Upcoming: Resound
* Audio management for CMS
* Started with documentation for provisioning, architecture, end-user documentation
* From beginning we focused on easy deployment and provisioning
* Goal is other stations to be able to set it up themselves
* Other:
* iOS v4 app
* Won’t be open-source
* However, Jeff is refactoring so that components can be open-sourced
* Example: KPCC API Client framework
* Thinking of other possibilities
* License?
Peter (MPR) <-- Thanks (louise)
* They use MIT license for everything
* Fairly involved clearing w/legal department
* “One-size fits all” license
* Case by case basis
* They’ve not done a great job of open-sourcing things except that which is required.
* ie. Grant licensing requirement
Dave (WBUR)
* Faced with normal issues everyone is
* Not a lot of time to open-source
* But open-sourcing raises the bar for code quality
* Essayist: “Good enough for production, not good enough for GitHub”
* A lot of code is tied with WBUR things
* Thinking about separating out code, documenting “missing parts”
* One thing he has been fastidious about: Remembering, when selling open-source, that it’s more than putting code on GitHub
* Meet-ups
* Starting tickets
* Pull requests
* Documenting everything done behind-the-scenes
* “We’ve shown our code to people who want to see it”
* Private repo, but selectively opened to others
* iOS and Android apps
* No mobile developers
* Brian from NYPR has used some of their iOS code
* “Wary” of open-sourcing full code of iOS app
* Middle ground
* Probably not good enough for the zealots
* But helps others to not reinvent the wheel
* Brian: Defaulting to open-source encourages a change in mindset that prioritizes documentation, tests
* A stranger (on the Internet, on team, etc) can set it up
* Louise: Reiterating value of contributing, even if just to fix documentation
* Peter: Getting involved in a project early in lifecycle can help a lot even if not contributing code
* Even just issues, conversation, feedback
* Rails web pack integration
* Product fit their architecture better
* Submit feedback before architecture was set in stone
* Louise: Rails community is a good example of balancing
Future Potluck Plans -- John (WBUR)
* Excited to pick up baton from KPCC
* In terms of documentation and open-source
* Louise and her team have done a great job of creating a playbook
* Dave came back and felt that it was incredibly worthwhile
* “Our job is to not screw it up”
* Boston is a hotbed of public media
* Great place to represent the east coast
* Weather is nicer in June
* Date Thu/Fri (June 14/15)
* Will rely on Dave
* Will do their best to keep community growing
* Will Smith is working with Dave
Questions/comments
*****COMING UP*****
- Next call – Feb 27th
- Potluck attendees -- stay tuned for a wrap-up email at the end of this week
- Got an idea for a future topic for a call, or something we should consider tackling during a meetup? Let us know below, or fill out this form: https://goo.gl/forms/JTtFNbSduotdHGhj2
+
+
diff --git a/potluck-framework/archive/etherpad/phonecall/PublicMediaPotluck_Call-02272018.html b/potluck-framework/archive/etherpad/phonecall/PublicMediaPotluck_Call-02272018.html
new file mode 100644
index 0000000..a42e198
--- /dev/null
+++ b/potluck-framework/archive/etherpad/phonecall/PublicMediaPotluck_Call-02272018.html
@@ -0,0 +1,143 @@
+
+
+
+PublicMediaPotluck_Call-02272018
+
+
+
+
+
+
+
+Public Media Kitchen Community Call | February 27, 2018
Every other Tuesday @ 12pm Eastern - 9am Pacific
*****CALL-IN NUMBER*****
712-832-8330
- Access code: 595 4808
- *6 to unmute!
______________________________________
Welcome to the call!
ROLL CALL: Who are you? Where are you from? What do you do?
- WBUR
- KPCC
- NPR
- WNYC
- Capital Public Radio
- PRX
- Pro Publica
*****TODAY'S TOPICS*****
Joanne Garlow (NPR)
Slides -- https://docs.google.com/presentation/d/1wKFfbbAJsgClpiK-P4LTUG6CchCTftM_i4xLCZEOgWU/edit#slide=id.p
- Most NOR stuff on MySql in datacenter
- Native driver master/slave
- Oracle - recently changed pricing structure
- Percona backend
- 4 servers -- number ofslaves for each
- Not available from outside
- Even PHP can only read
- Relational database feeds doc database (newer) -- ElasticSearch in front of DB
- MySQL as doc database for older stuff (legacy search)
- What to do for larger scale stuff / HA (e.g, - stats for NPR One) -- My SQL not good for this
- Looked at Mongo, Cassandra, DynamoDB
- Liked Dynamo -- elastic; didn't need much search functionality
- Wanted in move-in-ready for production
- Dynamo -- good cost, good search
- DB's still really (comparatively speaking) small
- $1500 / month
- Don't have to clean data
- Dynamo streams feed post=process (using lambda)
- Analytics
- While public API needs to be fast with strong data recovery, we can use something liek Big Query for analytics
- Not in prod yet with Big Query, but lot of optimism
PRX -- we're doing similar stuff with lamdba / Bug Query
Will Smith (WBUR)
We use Amazon's Relational Database Service to host MySQL database instances for our production/staging environments.
Pros:
- Ease of maintenance
- Easily configurable backup systems
- Automatically partially addresses 3-2-1
- Quick setup for alerts
Cons:
- Timezone issues if you don't plan for UTC
- Higher latency than if you're hosting locally
- Some basic things harder in RDS: E.g. setting up slow query logging
Setup
3 RDS instances (Production, Stage and Legacy). Run nightly full backups offsite to private S3 bucket. Use RDS Snapshotting for daily snapshots for our production database.
We have CPU and connection monitoring set up on our production database which uses Amazon SNS to send text messages to dev team if our DB exceeds CPU thresholds across multiple polls (I think we have it running at 5 minute intervals and two failures prompts a SMS alert)
Considerations:
We have plans to set up read replicas for a few reasons:
- Better performance in read-heavy setups.
- Allow zero down time when running hourly snapshots
- Redundancy and failover
WBUR has a "headless" WordPress setup and our API and WordPress architectures are tied together which makes separating read/write operations more work than just setting up HyperDB WordPress plugin, but its still in our OPS backlog.
MySQL + EC2 and hosting locally:
In the past, I have seen a sizeable increase in performance running MySQL locally vs in RDS. We have considered keeping a local version of MySQL running in production for use in failover, but not having to worry about CPU and memory considerations for MySQL has allowed us to focus our EC2 setups for applications only.
How do we scale? Thrfow $$ at Amazon. Almost no problems in past 4-5 years (konck on wood).
WNYC (Sylvia) - pipeline streaming logs. S3, AWS redshift, looker (SQL-lioke language). luigi is veeeery slow -- https://looker.com/platform/ecosystem/amazon-web-services
Louise Yang (KPCC)
- wildfire tracker app
- comes with own replication (open source)
- postgres in RDS -- for ReSound
- CMS: Outpost
- MySQL / Percona cluster
- 3 nodes -- lots of HA, lots of maintenance
- 2 hour baks, daily full baks
- (?) from from percona to pricey read/write replicas
- Aurora (scalable ? ) PRX might experiment
- David (Pro Publica): hardware floor for Aurora quite high
*****COMING UP*****
- Next call – Feb 27th
- Potluck attendees -- stay tuned for a wrap-up email at the end of this week
- Got an idea for a future topic for a call, or something we should consider tackling during a meetup? Let us know below, or fill out this form: https://goo.gl/forms/JTtFNbSduotdHGhj2
+
+
diff --git a/potluck-framework/archive/etherpad/phonecall/PublicMediaPotluck_Call-03132018.html b/potluck-framework/archive/etherpad/phonecall/PublicMediaPotluck_Call-03132018.html
new file mode 100644
index 0000000..412941e
--- /dev/null
+++ b/potluck-framework/archive/etherpad/phonecall/PublicMediaPotluck_Call-03132018.html
@@ -0,0 +1,143 @@
+
+
+
+PublicMediaPotluck_Call-03132018
+
+
+
+
+
+
+
+Public Media KItchen Community Call | March 13, 2018
Every other Tuesday @ 12pm Eastern - 9am Pacific
*****CALL-IN NUMBER*****
712-832-8330
- Access code: 595 4808
- *6 to unmute!
______________________________________
Welcome to the call!
ROLL CALL: Who are you? Where are you from? What do you do?
- Jay from KPCC
- Louise from KPCC
- Sandi from PRX
- Ryan from PRX
- Bina, Noah, Jeff, Dan, Tommy, Phil, Jessica, Bunmi, Grant, Jason, and Nara from NPR
- Joanne from NPR
- Will, Daigo, Dave from WBUR
*****TODAY'S TOPICS*****
Useful links:
- React Next: https://github.com/zeit/next.js/
- React Create App: https://github.com/facebook/create-react-app
- React Native http://facebook.github.io/react-native/
- Vue.js: https://vuejs.org/
- Simple single-page Vue (and PHP) player: https://gist.github.com/CrookedNumber/c4f34da70813e95dd9e2ff58d8ace8a1
- TODO app (LOL, I know) using Vue single-file component: https://codesandbox.io/s/o29j95wx9
- Angular https://angular.io/
- Typescript https://www.typescriptlang.org/docs/home.html
- ngrx https://github.com/ngrx
- Protractor https://www.protractortest.org/#/
REACT (Jay, KPCC)
- Huge React fan
- React a library, technically -- not a framework
- Great for PWAa, dynamic charts
- Just makes a lot of sense
- View web app as a tree -- components inside components
- Good testing / predictability
- Natural way to test things, esp. if you use stateless components
- Basic lifecycle
- Transitions well into native apps -- see React Native
- Relative unopiniated
- Re-usable components
- Jay wants to use it more, next framework, universal (client- and server-side) apps
- Need to make sure it doesn't mess with SEO when using it on public-facing stuff
VUE (Dave, WBUR)
- We have a de-centralized CMS. Headless Wordpress, so we still needed a tool to arrang landing pages, and do other things.
- So we needed a js library for choosing stories from a list, creating/deleting new sections, dragging/dropping stories onto these sections. Basically -- just a of API calls and data manipulation, binding .
- We use React on the front end, but we went with Vue
- Didn't need state, not a SPA
- I liked the low barrier to entry, the two-way data binding (in at least 1.0), intuitive syntax.
- Easy to get started and start writing. User-friendly. Just pulled the framework in (remote min file) and started learning.
PROS
- Ease of use.
- Good community and docs
- Reminds one of React. Data bubbles down. Props / components. Etc.
- You're writing very simple js
- SINGLE FILE COMPONENTS!!! A html/mustache template; an object-like <script> (the brains); and the CSS (or Less, etc.)
- Re-usable code, not just components, but also patterns
- Constantly adding tools. VERY easy to add a quick form taht adds/edits data that gets shot out by our configuration API
- Integrates really well with Laravel
CONS
- A bunch of tricky, weird gotchas (though mostly in v1)
- Getting everything to work with single-file component-based system (Babel, webpack). And there are many ways to do this.
- Though Laravel and Mix help with this.
- Significant leap from v1 to v2 (though not like Angular). Conversion took a looong time. (v1 might have been a bit rushed).
ANGULAR (Nara, NPR)
- Angular v2
- Most NPR stuff uses React
- NPR One web app uses Angular
- Originally written in knockout + jQuery
- Re-wrote from scratch
- First considewred doing it in React (before create-a-react-app existed)
- React a library -- angualr is an all-in-one solution
- Dependency injection -- much better for unit tests
- NPR -- must write automated test for all we do
- unit tests + end-to-end tests
- Protractor -- wrapper around Selenium, like an "invisible robot"
- 100% unit test coverage
- With Angukar, routing and state management already taken care of
- Opinionated -- usually only one or two ways to do stuff
- Angular CLI -- like Ember CLI
- Angiular CLi abstracts away webpack
- E.g., -- to install webpack 4, just install latest version of CLI
PROS
- Typescript!
- Liking it better than plain old ES6
- testing (of course)
CONS
- steep learning curve
- dependency injection hard to learn
- big, meaty
- Needs updates frequently
- Need to stay on top of updates
- Can't walk away from it for a year
- NGRX
- Angular core team contributes to NGRX
- PRI uses NGRX
*****COMING UP*****
- Next call – March 27th
- Potluck attendees -- stay tuned for a wrap-up email at the end of this week
- Got an idea for a future topic for a call, or something we should consider tackling during a meetup? Let us know below, or fill out this form: https://goo.gl/forms/JTtFNbSduotdHGhj2
+
+
diff --git a/potluck-framework/archive/etherpad/phonecall/PublicMediaPotluck_Call-03272018.html b/potluck-framework/archive/etherpad/phonecall/PublicMediaPotluck_Call-03272018.html
new file mode 100644
index 0000000..daee5bd
--- /dev/null
+++ b/potluck-framework/archive/etherpad/phonecall/PublicMediaPotluck_Call-03272018.html
@@ -0,0 +1,143 @@
+
+
+
+PublicMediaPotluck_Call-03272018
+
+
+
+
+
+
+
+Public Media KItchen Community Call | March 27, 2018
Every other Tuesday @ 12pm Eastern - 9am Pacific
*****CALL-IN NUMBER*****
712-832-8330
- Access code: 595 4808
- *6 to unmute!
______________________________________
Welcome to the call!
ROLL CALL: Who are you? Where are you from? What do you do?
- Will, Daigo, Dave from WBUR
- Louise (KPCC), Jay (KPCC)
- Renee Thompson, Carlos Mitani Sigala (Capital Public Radio)
- Brian Whitton (WNYC)
- Jason Herring, Yenly Ma, Marc Obrien KQED
*****TODAY'S TOPICS*****
EMBER (Brian, WYNC)
Tons of APIs -- allow you to do conventional things.
3.5 years ago, NYC was experimenting with Backbone / Angular
Based on teh notion that URLs for browsers are special
URLs should always look teh same -- no matter where you came from
Like the extensibility
Biggest attendance edver for past Ember conference -- it's growing
Batteries included
Good "developer ergonomcis"
Opinionated [?]
Testing story is already told -- same for dependencies, asset handling, UI patterns, etc.
NYC uses it for "anythiong that is responsive" -- wync.org, qxr.org, goathmist, etc.
Audio recording app will be NYC's first fast-food (?) app. Link?
Pro-tio: Wappalyzer -- https://www.wappalyzer.com/
Choosing Ember vs React
- Routing, data
- Upgrading Ember -- pretty easy
"Stability without blocking/breaking"
Newer versions generally mean: getting rid of deprecated APIs w/o breaking stuff
New stuff
Excited about new testing stuff
using Web Assembly to take UI rendering library (?), trun it into machine code
(ISOMORPHIC) REACT (Will, WBUR)
First off, I am far from an expert. At WBUR we use a now-ancient framework which was built in late 2015 to early 2016, a very outdated version of Webpack (1.x), and various other pieces cobbled together from working "Todo MVCs" which seem to dominate the SPA tutorial market still. There are several boilerplate frameworks out there now with built-in SSR. There are also more opinionated platforms such as Next.js to take a lot of the complexity out of React development and SSR specifically. Finally, everything I am talking about is in the context of a *content* website, not some sort of CMS tool or other application.
Pros
- Checks the progressive enhancement box for all you purists out there
- In many cases, initial page loading is faster. "App gap".
- If the client doesn't support javascript, the site can still (mostly) work
- Facebook opengraph reads can't happen without it.
Cons
- complicates development environment
- can add a lot of boilerplate to your apps
- you now have to be very conscious about which code is running where (componentWillMount vs componentDidMount)
- complicates DOM manipulation as the server and client need to be in sync
WBUR Setup
Caveat: At WBUR, we are using a now-ancient framework cobbled together in mid-late 2015. So most of my experience is with this framework and I know a LOT has changed in the past 2.5 years.
We use Reactjs 15, Fluxible, Webpack. On the server we use Express server + pm2 for node minding.
Notes on client-side only rendering and Search bots:
- Google bot uses Chrome 41 for rendering. Chrome 41 doesn't support ES6.
- Most search engines WILL render js but they don't crawl the javascript links
- Javascript is very brittle compared to HTML5 (remember Quirks mode?). A simple syntax error can cause Google to not crawl and even de-index your page(s)
Resources:
*****COMING UP*****
- Next call – April 10th
- Got an idea for a future topic for a call, or something we should consider tackling during a meetup? Let us know below, or fill out this form: https://goo.gl/forms/JTtFNbSduotdHGhj2
+
+
diff --git a/potluck-framework/archive/etherpad/phonecall/PublicMediaPotluck_Call-04102018.html b/potluck-framework/archive/etherpad/phonecall/PublicMediaPotluck_Call-04102018.html
new file mode 100644
index 0000000..b565852
--- /dev/null
+++ b/potluck-framework/archive/etherpad/phonecall/PublicMediaPotluck_Call-04102018.html
@@ -0,0 +1,143 @@
+
+
+
+PublicMediaPotluck_Call-04102018
+
+
+
+
+
+
+
+Public Media KItchen Community Call | April 10, 2018
Every other Tuesday @ 12pm Eastern - 9am Pacific
*****CALL-IN NUMBER*****
712-832-8330
- Access code: 595 4808
- *6 to unmute!
______________________________________
Welcome to the call!
ROLL CALL: Who are you? Where are you from? What do you do?
- Will, Daigo, Dave from WBUR
- Bryan from WBEZ, Digital Plumber
- Benny Wong, Brian Lee, Lisa Buch from WNET
- Louise Yang from KPCC
- Jeff Campbell from KPCC
- Vijay from KPCC
- Mike Seifollahi, Michael Choe, Allen Baker, Jessica Chen, Paul Miles, Olubunmi Odumade, Nara Kasbergen, Grant Dickie, Jeff Sank, Ijeoma Ezeonyebuchi, Max Doumit, Adam Winters, Phil Shannon from NPR
- Renee Thompson from Capital Public Radio
- Tommy O’Keefe from NPR
- Joanne Garlow from NPR
*****TODAY'S TOPICS*****
MOBILE APP DEVELOPMENT
Brad Kammin (WYNC)
- Mobile dev at NYC
- Support 3 apps - RadioLab, QXR, NYC
- RadioLab was a PRX creation for 5+ years
- Rewrote PRX app from (?) Phone Gap / Cordova
- QRX on Phone Gap
- NYC app now Native
- Knocks vs. non-native (like Phone Gap): the lag time, 3rd-party integrations arrive sooner with Native
- Co-developed NYC app with Intrepid
- Android outsourced to Intrepid -- NYC took over maintennance
- Toolchain: X-code; Circle CI for CI
- Try to get 100% test coverage
- Apps talk to content API
- Google Analytics
- Facebook SDK
- New Relic for crash analytics -- have tried crashalytics and hockey app
- Only mobile dev "Pretty much all I do" -- except maybe some smart speaker stuff
- Several QA people on staff
- Partial allotment of QA person for app
- Release testing / smoke testing
Jeff Campbell (KPCC)
- iPhone and Ipad apps written in Obj-C
- Doing a rewrite (apps written in iPhone 5 days)
- Wasn't using flat design, auto-layouts, etc.
- No hardware contexts like 3-touch etc.
- Jeff learned Swift while re-writing app
- Swift moving rapidly -- but things have settled down
- Toward a universal app (iPhone and iPad) -- using size classes
- Advice: GO NATIVE!
- "Users can tell [the difference], even if they don't know why they can tell."
- "I like to avoid dependencies."
- "Best not to fight Apple."
- Don't want to wait when they are SDK changes.
- Maybe can use this with Home Pod.
- Car Play (poorly constructed)
- Part-time Andorid dev works on Android app
- LAist acquisition could mean more app development
- Full memeber of team: attends standup, planning, etc.
Michael Seifollahi (NPR)
Q: At what point do you stop and not turn into a podcasting app?
WBUR : We might have gone too far, now in middle ground between station app and true podcast app
NYC : check out discovery section in app -- heavy focus on offline listening (Analytics SDK can cache events and send batch when you have a signal).
Resources:
*****COMING UP*****
- Next call – April 24th
- Got an idea for a future topic for a call, or something we should consider tackling during a meetup? Let us know below, or fill out this form: https://goo.gl/forms/JTtFNbSduotdHGhj2
+
+
diff --git a/potluck-framework/archive/etherpad/phonecall/PublicMediaPotluck_Call-04242018.html b/potluck-framework/archive/etherpad/phonecall/PublicMediaPotluck_Call-04242018.html
new file mode 100644
index 0000000..51735bc
--- /dev/null
+++ b/potluck-framework/archive/etherpad/phonecall/PublicMediaPotluck_Call-04242018.html
@@ -0,0 +1,143 @@
+
+
+
+PublicMediaPotluck_Call-04242018
+
+
+
+
+
+
+
+Public Media Kitchen Community Call | April 24, 2018
Every other Tuesday @ 12pm Eastern - 9am Pacific
*****CALL-IN NUMBER*****
712-832-8330
- Access code: 595 4808
- *6 to unmute!
______________________________________
Welcome to the call!
ROLL CALL: Who are you? Where are you from? What do you do?
- Will, Daigo, Dave from WBUR
- Jay, Ben from KPCC
- Jenna, KUOW, director o' digital. I will be in listen mode (driving)
- Renee Thompson, Chris Hagan, Carlos Mitani Capital Public Radio
- Sandi Barr, PRX, Senior Software Engineer mostly front end
- NPR Digital Media: Paul Miles, Nara Kasbergen, Tommy O'Keefe, Phil Shannon, Jeff Sank, Dan Kottke, Todd Welstein, Libby Bawcombe, Michael Fussell
- Phil Zelnar, WAMU
- Andrea Edstrom, Minnesota Public Radio
- Brian Whitton, Michael Hearn from WNYC/NYPR
- Ryan Cavis, PRX
- Louise Yang KPCC
*****TODAY'S TOPICS*****
CSS
Todd Welstein (NPR)
Jay Arella (KPCC)
- SASS
- BEM
- CSS architecture mirrors our application architecture
SASS
- Pros:
- Simple things
- defining variables, great for breakpoints, font-families, interactivity
- scoping is pretty straightforward with nesting
- mixins
- we use a mixing to group css declarations for general layout positioning
- rails supports sass by default since 3.1
- Cons:
- nesting too deep can make things too specific and hard to re-use
- you sort of have to wait for compilation, and when you make a type with indents, it sort of breaks (although that’s also a pro)
BEM:
- Pros:
- easy to quickly find where a style is defined
- easy to understand what a style is doing with modifiers
- Cons:
- Sometimes the names end up being too verbose
- you still have to figure out names for each element, which can be a bit tricky
CSS architecture mirrors our application software
- We split up our application into reusable components called cells, so each cell has their own scope
- We split up our pages into layouts which contain those cells
- layout styles are mainly concerned with positioning, cell styles are mainly concerned with the content
- tried to move away from nesting
Daigo Fujiwara (WBUR)
- Mobile-first.
- Atomic web design
- SMACSS -- stae helper class, __ modifier
- SCSS -- don't have to worry about spacing
- Borrowed stuff from Zurb, but don't use it
- Instead, use homemade grid system (from Upstatement)
- Try to limit nesting, DOm is pretty flat
- CARD-based, show or hide
- Homemade simple pattern library
- No on-site designer
- Pattern library: can test; designer and developer can talk shop
- Pattern Lab http://patternlab.io/
- Frontend Style Guide http://styleguides.io/
- https://litmus.com/ for testing
Q: What browsers do you support?
A: NYC -- not IE11
BUR -- Flexbox, maybe some IE11, not IE9
NPR -- tiers. Tier 1: Support 100% Tier 2: IE11, might not be perfect
KPCC -- try to traget IE11, at least get something readable
Q: Testing for UI
A: WBUR -- litmus
NPR -- Automtaed. Selenium., Check for thinsg present at certain breakpoints. Comparing screenshots
back.js (?), automated screeshot testing
Ben TItcomb (KPCC)
* A Medium article I wrote on some of my CSS/Sass practices if you are interested in further reading: https://medium.com/kpcc-labs/patterns-for-writing-manageable-css-without-a-framework-109779743c41
Resources:
*****COMING UP*****
- Next call – May 8th
- Got an idea for a future topic for a call, or something we should consider tackling during a meetup? Let us know below, or fill out this form: https://goo.gl/forms/JTtFNbSduotdHGhj2
+
+
diff --git a/potluck-framework/archive/etherpad/phonecall/PublicMediaPotluck_Call-05082018.html b/potluck-framework/archive/etherpad/phonecall/PublicMediaPotluck_Call-05082018.html
new file mode 100644
index 0000000..12f623a
--- /dev/null
+++ b/potluck-framework/archive/etherpad/phonecall/PublicMediaPotluck_Call-05082018.html
@@ -0,0 +1,143 @@
+
+
+
+PublicMediaPotluck_Call-05082018
+
+
+
+
+
+
+
+Public Media Kitchen Community Call | May 8, 2018
Every other Tuesday @ 12pm Eastern - 9am Pacific
*****CALL-IN NUMBER*****
712-832-8330
- Access code: 595 4808
- *6 to unmute!
______________________________________
Welcome to the call!
ROLL CALL: Who are you? Where are you from? What do you do?
- Will, Daigo, Dave from WBUR
- Louise @KPCC
- Andrea Edstrom from MPR
- Jess Snyder, WETA
- Andrew Stevenson MPR
- Ryan Cavis PRX
- Matt Aho MPR / APM
- Renee Thompson, Capital Public Radio
- Eileen Noonan, web developer, MPR / APM
- Chris Lewis, WAMU
- Justin Steen, MPR/APM
- William Tam, WNET/Thirteen
- Andy Beger, MPR/APM
- Adam Winters, Grant Dickie, Max Doumit, "Boomie" - NPR
- Peter St.Jean MPR/APM
(question, why is the number outside of my calling plan? is this overseas? <-- I don't think so. It's a freeconference number: https://hello.freeconference.com/login It's because they use some weird telephone system loopholes to provide "free" service https://productforums.google.com/d/msg/voice/jkfZP6lz7I8/Odtux6moPAEJ
- Todd Whitley, WNET/THIRTEEN - Digital Fundraising
- Benny Wong, WNET/THIRTEEN
- Melissa Major, WNET/THIRTEEN - Product Manager
- Phil Zelnar, WAMU
- Christina Knight, WNET/THIRTEEN
- Richard Baniewicz, WHYY
- Joanne Garlow, NPR
*****TODAY'S TOPICS*****
AUTOMATED TESTS!
Adam WInters (NPR)
- Web testing
- PREVIOUSLY: Java driver -- Eclipse, Selenium
- RAINFOREST -- paid web app. $500 / month https://www.rainforestqa.com/
- Works for non-devs, tests in plain English, screenshots
- NOW: node.js nightwatch
- http://nightwatchjs.org/
- selenium / webpack
- mobile plug-in
- good community
- customizable
- easy to plug in
- test log-ins
- goes through Jenkins server
- kick off every day
- toward main goal of Continuous Integration
- Make sure they pass on staging environments
- MOBILE TEAM - Ostrepo for Android, Selenium for IOS
- Used to test UI, but can also test for visible/present elements
- Also, unit tests for CSS
- Q: Do you do optimization testing, like Google Optimize, fractional changes, user behavior?
- A: Not NPR but Will Tam (WNET?) has, pain to get it set up, trying first pass at it now. They are a wordpress shop, high hopes to test stuff liek language changes on donate buttons etc.
Ryan Cavis (PRX)
- PRX CI/CD system - http://cav.is/i/PRX_CI_CD.jpg
- CloudFormation stuff - https://github.com/PRX/Infrastructure
- Acceptance tests - https://github.com/PRX/meta.prx.org
- Open source almost everything
- Build on Travis CI -- all good
- Move toward microservices, away from Rails monolith
- test multiple APIs, pre-deployment
- "Longer a commit is in master and not deployed, the more dangerous it is."
- Deploy through AWS
- Run almost all stuff through Docker -- even Lambda
- pulled to master --> pushed to stage
- CODE BUILD -- acceptance tests
- Then makes a button in Slack --> allows you to ACCEPT/REJECT GIT diffs and then deploy
- No separate QA
- Devs are lazy -- so we automate
- push as many tests as possible to unit tests
- ACCEPTANCE TESTS -- happy path --> hit a bunch of microservice endpoints (URLs / PRX services)
- Trying to run Selenium in Docker
- Louise? How do you do hot fixes? Can do with no PR, still takes 5-10 minutes
- More likely -- we roll back rather than hot fix -- point back to previous Docker image78
https://facebook.github.io/jest/
RE automated tests -- do you do optimization testing, eg Optmizely/Google Optimize?
It would be great if you could share the test as a case study, sharing a visual and identifying key metrics, as well.
Questions for Ryan:
* do all developers have permission to merge into master?
- all PRX developers generally do. but PRs from others have to be merged by us.
Is that Slack notification/button open sourced?
- i think it's in our Infrastructure repo somewhere - i'll look for it!
okay, here is the function that generates githib-diff links (changesets), and creates a slack button https://github.com/PRX/Infrastructure/blob/d839978d5cc0d65ab888f2f89eabf77a55a4ba1a/cd/lambdas/pipeline-approval-notification-handler/lambda_function.py
and here is the function triggered after you click a "Deploy" or "Reject" button https://github.com/PRX/Infrastructure/blob/cb427c1283f4936ab003d4f7f7c6087851d5ea86/notifications/lambdas/ike-interactive-messages-callback-handler/index.js
note: we use SNS for a lot of of our AWS communication with slack
buttons look like this: http://cav.is/i/ubzus.jpg (with emojis disabled, the way they're meant to be!)
Peter St.Jean (APM)
- For the front end, something like react-testing-library is a great middle ground between unit tests and end-to-end ala Selenium
- https://github.com/kentcdodds/react-testing-library
- The core of this approach is in the generic dom-testing-library, which is framework agnostic
- https://github.com/kentcdodds/dom-testing-library
- Blog post describing the philosophy behind these libraries: https://blog.kentcdodds.com/introducing-the-react-testing-library-e3a274307e65
Resources:
*****COMING UP*****
- Next call – May 22
- Got an idea for a future topic for a call, or something we should consider tackling during a meetup? Let us know below, or fill out this form: https://goo.gl/forms/JTtFNbSduotdHGhj2
+
+
diff --git a/potluck-framework/archive/etherpad/phonecall/PublicMediaPotluck_Call-05222018.html b/potluck-framework/archive/etherpad/phonecall/PublicMediaPotluck_Call-05222018.html
new file mode 100644
index 0000000..a62f360
--- /dev/null
+++ b/potluck-framework/archive/etherpad/phonecall/PublicMediaPotluck_Call-05222018.html
@@ -0,0 +1,143 @@
+
+
+
+PublicMediaPotluck_Call-05222018
+
+
+
+
+
+
+
+Public Media Kitchen Community Call | May 22, 2018
Every other Tuesday @ 12pm Eastern - 9am Pacific
*****CALL-IN NUMBER*****
712-832-8330
- Access code: 595 4808
- *6 to unmute!
______________________________________
Welcome to the call!
ROLL CALL: Who are you? Where are you from? What do you do?
- Will Smith (developer), Daigo Fujiwara (developer) WBUR
- Wes Lindamood (Interaction Designer / NPR)
- Louise (developer @ KPCC)
- Renee Thompson (Capital Public Radio)
- Matt Aho (APM/MPR Web Developer)
- Andrea Edstrom (APM/MPR Web Developer)
- Andrew Stevenson (APM/MPR Software Developer)
- Geoff Hankerson (APM/MPR Web Development Lead)
- Jeff Sank (web dev - NPR HQ)
*****TODAY'S TOPICS*****
We’ll be talking about DATA VISUALIZATIONS/Web Interactive features
What has your org produced recently? What was process like (how many people worked on it, how long did it take; who came up with the idea)? What libraries/tools did you use? What are some cool new tools you’d like to use? What orgs — including those outside public media — inspire you? Etc.
We'll have Wes Lindamood (NPR) and Daigo Fujiwara (WBUR) kick things off. Then we’ll follow up with some Q&A.
Wes Lindamood (NPR)
Feel free to email me (wlindamood@npr.org) or send me a note in the npr+friends slack if you want to chat about statewide results embeds.
Publicly-available code
https://github.com/nprapps
https://github.com/nprapps/dailygraphics
I don't have recent work to share, but we’ve aggregated some of our favorite projects on our team website — http://blog.apps.npr.org
And write about our work and process at http://blog.apps.npr.org/blog/.
We also tweet about our work at https://twitter.com/nprviz.
Election 2016 Statewide Results https://www.npr.org/2016/11/08/501068629/ohio-2016-presidential-and-state-election-results
A wrapper for the AP v2 Elections API https://github.com/newsdev/elex
Daigo Fujiwara (WBUR)
Future of Work (bubble chart) http://www.wbur.org/bostonomix/2017/10/30/future-jobs-data-massachusetts
Boston Mayoral Results (map) http://www.wbur.org/news/2017/11/08/boston-mayor-results-map
Past election results http://www.wbur.org/news/2018/03/19/massachusetts-past-election-results
Climate Change series (bar graph) http://www.wbur.org/news/2017/08/23/massachusetts-temperature-precipitation
2016 Election results (map, table) http://www.wbur.org/politicker/2016/11/08/massachusetts-election-maps
tools
https://www.highcharts.com/products/highcharts/
https://gionkunz.github.io/chartist-js/
https://datatables.net/
https://d3js.org/
Geoff Hankerson (MPR)
*** REMINDER ***
Please register for June PotLuck in Boston
https://ti.to/public-media-kitchen-potluck/public-media-kitchen-potluck-june-2018-boston
See more info at https://publicmediakitchen.github.io/toolkit/public-media-potluck-june-2018.html
+
+
diff --git a/potluck-framework/archive/etherpad/phonecall/PublicMediaPotluck_Call-121917.html b/potluck-framework/archive/etherpad/phonecall/PublicMediaPotluck_Call-121917.html
new file mode 100644
index 0000000..5e3addf
--- /dev/null
+++ b/potluck-framework/archive/etherpad/phonecall/PublicMediaPotluck_Call-121917.html
@@ -0,0 +1,143 @@
+
+
+
+PublicMediaPotluck_Call-121917
+
+
+
+
+
+
+
+Public Media Potluck Community Call | December 19, 2017
Every other Tuesday @ 12pm Eastern - 9am Pacific
*****CALL-IN NUMBER*****
1-712-832-8328.
- Access code: 170 4041
- *6 to unmute!
______________________________________
Welcome to the call!
ROLL CALL: Who's here?
- Katie Briggs, @sisternebraska - KPCC
- Vijay Singh, @vjpsingh - KPCC
- Ben Titcomb, @ravenstine - KPCC
- Brendan Williams @brendanstl - St. Louis Public Radio
- Bryan Zera - WBEZ
- Rebecca Smith - WHYY
- Richard Baniewicz WHYY
- Andrew Kuklewicz - PRX
INTRODUCTIONS: Let's get to know you!
If you're new here, tell us who you are, where you're from, and why you've joined our call.
- Your name here / What do you do?
- Katie Briggs – I lead design at KPCC (until Dec. 29, then I'm off to join the design team at NPR!) I help lead Public Media Kitchen.
- Bryan Zera - Most things web / digital @ WBEZ
- Ben TItcomb - Web developer @ KPCC
- Brendan Williams - digital/web, email marketing, web marketing, digital fundraising implementation
- Rebecca Smith - Digital product manager
- Andrew Kuklewicz - PRX CTO, but I do get my hands dirty
*****TODAY*****
Fundraising – Digital Operations for Pledge Drives (Bryan Zera, WBEZ)
- Drives at WBEZ
- Digital tools
- Salesforce – CRM
- Extensive API
- Have Salesforce devs in-house
- Litle – Credit card processing
- ACD – Call center processing
- Custom tools
- Donation form
- Make alterations as thoughtfully as possible
- Flexible enough to make changes for unforseen future needs
- Custom Google sheet
- Keeps track of goals for drive
- Donation form launcher
- Stage changes to donation form
- E.g. Day 2 of drive has an iPad drawing, this tool allows for changes to be made ahead of time/lauched when appropriate
- Pledge timeline
- Pre-drive
- Membership + marketing teams come up with schedule for donation config launcher (3 weeks out)
- Setting goals for each day/daypart
- During the drive
- Be as flexible as possible (Does news preempt the drive? Have drive details changed? Config launcher needs to be managed/updated)
- Notes
- Pledge drive tools need to be as well-documented/easy to update as possible
- Drives at KPCC
- Digital tools
- Braintree – CC processing
- Call center service
- Custom tools
- Donation form is custom
- Built in custom form-builder, Mango
- Manages goal-setting, displays to folks who are pitching
- Pledge-free stream
- Heavy lift
- Getting the stream ready technically, prepping content, sharing code
- Existing or new members get access code to alternative, pitch-free stream
- Major perk for certain types of members
- Pushdowns on kpcc.org (top of the site)
- Best points of acquisition
- Coded/scheduled before the drive (prep begins 4-6wk out)
- Display ads (newsletters + across site)
- Retargeting
Questions/comments <- post questions/comments here, or *6 to unmute!
- What do you want to know about this?
- Where is the donation form configuration managed/launcher? CMS? Code? What does the interface look like?
- Launcher is a script that runs on donation form server
- Each change is a git branch
- Launcher makes changes based on git branch name
- Would like demo, please! rsmith@whyy.org
Fundraising – NPR Donation Portal – Design Process and Metrics (Kaytee Nesmith, NPR)
- Started as experimental donation push (included donation portal for Up First)
- First iteration for donation portal – Enter your email address + member station – create connection for listeners to podcast
- Newest iteration – applies to 25 podcasts, each gets own portal page/URL (e.g. donate.npr.org/sam for It's Been A Minute)
- Enter member station and email address on portal, then go off to your station's donation form
- Brought in geolocating to make member station connection easier for non-broadcast/NPR folks
- Reveal process: 1) Enter email, then 2) choose member station
- If email is already associated w/ member station, users don't have to choose
- Been promoted on podcasts + on Twitter
- Podcast host competition on Twitter
- Referrals to donation forms have increased exponentially from initial portal iteration
- I wish we knew ...
- I wish there would have been more research/usability testing/behavioral research
- Do a more formalized study before next iteration
- Folks coming to the portal that are new to NPR – what are they thinking? How can we better facilitate a connection between them and their member station?
Questions/comments
Fundraising – New Tech + Pledge Form Success Stories
- KPCC – One-touch donation through NPR One (Apple and Google Pay)
- Pain points
- Setting up secondary gateway
- Ironing out kinks internally around new process
- PRX – Radiotopia fundraiser + Radio Public
- Radio Public app ask (based on user behavior)
- Could then trace donations from Radio Public ask through completed donation
- I wish we knew ...
- Processing tool made attributions/tracing of transactions tougher than expected
- iOS bug interfered with some form interaction
- A better way to export/share data, repeat data gathering and analysis
Got a success story (or a status update)? Share it below!
- Question: Anyone have experience with PayPal set up/management/Integration. What do you wish you knew before you started that process.
- KPCC has experimented with PayPal in the past
- Setup is pretty straightforward (lots of good documentation)
- Issues came up in processing donations
- Non-custom tools provide different types of data/data we aren't ready to process
-
-
Potluck Meetup – Tentative Agenda (Vijay Singh, KPCC)
- JANUARY 25-26
- Foster as much collaboration as possible
- Developers + designers + product managers
- The headliner is going to be about smart speakers, and the process of designing and building skills.
- A session on User Research processes and collaboration
- Some sessions pitched
- Membership/pledge drives and technology
- Open source software and how public media dev teams can partake in that ecosystem
- Audience development and video
- Send some more ideas! https://goo.gl/forms/JTtFNbSduotdHGhj2
Questions/comments
*****COMING UP*****
- Next call – Jan. 9
- Public Media Potluck meetup – Jan. 25-26
- Got an idea for a future topic for a call, or something we should consider tackling during a meetup? Let us know below, or fill out this form: https://goo.gl/forms/JTtFNbSduotdHGhj2
+
+
diff --git a/potluck-framework/archive/etherpad/phonecall/pmk-call-2018-11-05.html b/potluck-framework/archive/etherpad/phonecall/pmk-call-2018-11-05.html
new file mode 100644
index 0000000..1b66186
--- /dev/null
+++ b/potluck-framework/archive/etherpad/phonecall/pmk-call-2018-11-05.html
@@ -0,0 +1,143 @@
+
+
+
+pmk-call-2018-11-05
+
+
+
+
+
+
+
+Public Media Potluck Community Call | November 5, 2018
Special Monday before Elections @ 1pm Eastern - 10am Pacific
*****CALL-IN NUMBER*****
1-712-832-8328.
- Access code: 170 4041
- *6 to unmute!
______________________________________
Welcome to the call!
ROLL CALL: Who are you? Where are you from? What do you do?
- Louise Yang / KPCC / Lead Software Engineer
- Renee Thompson, Capital Public Radio, Digital Projects Manager
- Vijay Singh Product Manager / Project Manager
- Carlos Mitani, Capital Public Radio, Web Developer
- Justin Bowers, KERA, Sr. Digital Designer/Developer
- Tim Olson, KQED, Chief Digital Officer
- Andrew Stevenson, MPR/APM, Software Developer
- Jason Phan, MPR/APM, Assoicate Web Developer
- Sarah Ziegenfuss, NPR, Senior Scrum Master/Project Manager
- Jason Herring, Dir of Digital Design and Development
- Danika Ragnhild, PRI/PRX, Software Engineer,
- Andrea Edstrom, Sr. Designer/Developer
- Cynthia Chiou, KUOW, Marketing Project Manager
- Jay Arella, KPCC, Web Developer
- Kate Hawkins, KQED, Product Manager
- Ki Sung, Senior Editor MindShift/KQED
*****TODAY'S TOPICS*****
Project Management in Public Media Organizations
- Does SCRUM work in a newsroom setting?
- How do you project manage within and across content teams?
- What works at your organization?
- What doesn't work at your organization?
*****Speakers******
Valentina Powers (digital ops lead @ WNYC)
- oversees project management, process, supports digital teams (engineers, product, dev ops, 25 fully staffed)
- scrum > 7 years
- works with conten -- lots of stakeholders :
- newsroom, gothamist
- wnyc studios (podcasts)
- music
- organization:
- team based on local audience (interdisciplinary) PM, devs, design, QA -- newsroom, wnyc, gothamist
- on demand wnyc studios, music, green space
- data/revenue team
- methods
- scrum
- kanban -- projects to push out quickly
- project manager is scrummaster, liason w/ content teams to coordinate editorial & marketing efforts
- checklists for necessary things:
- show launch -- show assets, descriptions, IP descriptions
- audio ops -- naming conventions
- marketing, sponsorship
- what works:
- tiger ? teams -- smaller x-functinoal teams
- need to know meetings every 2 weeks for content team
- updates on projects, show launches, pipeline updates
- digital team (couple of people) attend this meeting. distributes info back to their team
- shared calendar/tool w/ Airtable
- local scrum team has local meeting
- dashboard w/ goals every week, pacing, KPI's
- deck of updates from every section of the team (content, BD, membership)
- tactical/goal oriented
- clear roless & responsibilities
- who's the decision maker?
- sprints
- strict about digital process
- agile to newsroom intro
- trello board (what stories are happening at what stage, who's responsible)
- embedded external stakeholders in x-functional teams
- retrospectives
- org values
- what doesn't work
- too many people w/ too many levels of decision making
- solution: make teams small and more tactical
- no defined roles of who was making decisions
- too many directions from different stakeholders
- duplicated effort
- no clear process defined at beginning of meeting
- shared calendar across all teams
- Q: why break up the scrum teams the way that you did?
- A: broken up by product
- gives team more ownership w/ team charter and OKR's
- Q: any other quick tips w/ getting rest of org to understand how scrum/OKR's work?
- A: show and tell w/ different stakeholders introducing them to different teams
- describe OKR's and sprints
- local meeting -- looking at OKR's on a weekly meeting w/ rest of org.
- people understand the goals of everyone else
- Transparency:
- product demo, invite everyone in the org
- struggling w/ attendence now
- how to incentivize people to join
David Moore (developer @ WBUR)
- at WBUR > 3 years, before that at NPR
- no project/product manager or scrummaster b/c on a small team
- bare scrum
- 2 week sprints
- trello in 4-5 columns
- no points or burndown
- review & planning at the end of every sprint (90min meeting)
- no retro
- post mortem on big projects w/ interdisciplinary people (photographers, reporters, developers)
- standup
- Q: does scrum work in the newsroom?
- different coming from NPR
- A: works better than not having scrum
- provides process/procedure
- but still retain flexibility for news occuring mid-sprint
- sanctity of the sprint (is it really something that should/shouldn't wait 2-4 weeks?)
- before scrum:
- drive-by's -- reporters stop by and ask for data viz, puts it at the top of the queue
- socialize everyone to the idea that developers need time to work on something
- Q: how to project manage with and across content teams?
- data viz works more closely w/ newsroom
- content teams are not fully incorporated into the sprint
- boss will write a ticket or post it note
- note gets talked about during review/planning
- concepts of scrum have been dispersed to newsroom
- trello
- standups are open to anyone
- web editors join
- web editors go to planning and review if they have tickets they want to bring up in the next sprint
- critique: digital has a lack of transparency
- do a better job exposing epics board
- What works?
- lite-touch scrum
- not having too much structure, or strict rules
- adds more burden, no value added
- agree on consensus (rule) thru the team
- What doesn't?
- having scrum rules come from outside the team or from the top
- two project managers for 1 team
- **If it doesn't work for the team, don't do it**
- tried out points for 3 weeks, but waste of time
- Design your scrum rules "Cafeteria style" -- i.e., take only what you like/need
- Q: how has the org reacted to the change of doing scrum instead of drivebys?
- overall pretty well
- boss has buy in and socializes other managers to scrum
- still catching on, so far so good
- Q: people complain about lack of transparency, but they also don't want us to overshare. Any other tips?
- "changing hearts & minds one coworker at a time"
- pulling out the trello board when things come up
- epic board => dashboard might be easier for people to view?
- whiteboard of a roadmap for next 2 years
- idea: smaller whiteboard of 6 most current things digital team is working on
- if things are getting done, do we need transparency?
- Q: x-department stuff like w/ data viz, do you have to modify anything?
- still siloed, data viz still has to write tickets
- if other dept. person is tech savy, invite them to trello card, write cards in a user friendly manner so that person can see what's going on
- generally, things do not get modified
Vijay Singh (pro[duct|ject] @ KPCC)
- vanilla scrum: 2 week sprints, demo, planning
- has same issues Valentina & Dave have highlighted
- scrum started almost 4 years ago, org is generally accepting of it
- our team is more of a strategy team
- focus on long term efforts that pay off over time
- push to hand off project management of editorial projects to editorial teams
- scrum to the newsroom:
- started w/ digital editorial team (scpr.org | laist.com)
- went OK
- invited to product team's zenhub scrum board
- familiar w/ digital tools
- tried trello in the past
- hard for digital newsroom team to push back b/c sprint was already set
- 8 points a sprint
- 4 points for fires/daily news
- 4 points for long term projects
- success in getting to long term projects that used to be always on the backburner
- use zenhub as a scrum board
- PM can more easily say "no" to things, or make a case for early planning
- What didn't work:
- investigative team was interested in having more process b/c they work on longer term projects and understands the overall value of scrum
- fell apart b/c it didn't work w/ the team
- attempted to do it for 3-4 sprints
- too much overhead w/ points
- overly obsessed w/ the tooling
- extreme scrum-lite (kanban?): writes up tickets to capture effort
- too many cooks in the kitchen
- project coming from another department, harder to enforce who the product owner is
- What works:
- swap out whatever tool you want, but find a process that works
- task force for bigger projects (x-departmental projects)
- people get upset if they're not part of the task force
- easier for product team to enforce the product owner
- PM to enforce across teams:
- set up other teams as scrum to plan ahead of time and coordinate w/ other teams
- gets rest of org to have more of a project management mindset
Questions/comments?
- KUOW may have a couple people listening in (Jenna - digital dir, Cynthia - project manager). Looking forward to it
- Question for Valentina from Cynthia, KUOW, marketing project manager: You mentioned being clear about who the decision makers are, how do you handle this when certain tasks may live shared across editorial vs promotions/marketing? Thank you!
- no single solution, still struggling w/ this, not easy
- clarify understanding of who the product owner is and when to loop in marketing or editorial
- ie: podcast -- lines are clear, there's a template
- changes w/ every project
- dedicate 1 person on the content team to help coordinate and work w/ editorial to streamline
- Curious how points are used for smaller tickets that might only take an hour or two. Do you break them down to decimals?
- Vijay: yes! points are escalating: 0.5, 1, 2, 3, 5, 8, 13, 20
- Vijay: as a team, anything over 3 should be broken up
- Vijay: varies across teams
- Vijay: small tickets are 0.5 or 1
- Vijay: adjust scale to the smaller task
- Dave: rough fibonacci: 1, 2, 3, 5, 8, 13, 20 <-- 20 is an epic
- 1 - trivial
- push back about agonizing about how many points a ticket is
- Vijay: easier to use points to argue for fires and what tissues should be postponed in sprints
- Do you have consenus on how editorial can file tickets? Should reporters be filling out Jira tickets or filling out Google docs or sending notes via Slack? We are trying to balance speed vs. falling into the ticket hole.
- Vijay: depends on the level of the ask. Most requests should be filtered to a singular person in each department
- hard to prioritize if 2 people on a team of the same level ask for the same thing
- let people know to come to product manager first vs. going to someone on the team
- larger projects: google form to help people sketch out what they're asking for
- Valentina: try to streamline it, but there's 4 product managers, many project managers
- everyone files tickets thru Jira (for smaller asks)
- issue gets sent to the correct project/product manager
- intake helps streamline where the issues go
- protects sprints and devs to work on strategy instead of side-projects w/ little impact
- product managers have "opportunity accessment" (10 questions for an idea)
- what's the competitive landscape?
- what's the audience?
- what's success look like?
- yay/nay on going forward or not
- Dave: no dedicated product person
- if you have a trello account, add to a board of "incoming tickets"
- works pretty well. web producers point out bugs this way
- gets brought up during review/planning and puts into sprint columns
- worksk well b/c most people don't have access or know about it
- What recommendations do you have for managing expectations from editorial? (deadlines, ambitions, relevance to the audience)
- Vijay: google form to see what impact they're expecting
- gets them to understand the scope of things
- explicit of what's going to be delivered
- Valentina: when there's a request, circle back to the teams to see what the scope and goals of the request is
- goes back to request to explain what will be delivered, clarifying what can be achieved w/i the timeframe
- clear goals for the year (OKR's) -- everyone understands what those goals are
- Dave: similar process as above, explanations of constraints or why things are possible or not.
- cheap and easy alternatives
- For Valentina, quick question, What is the threshold for size of teams?
- we have limited resources, so scrum teams are pretty small
- 3-7 members on the team
- depends on the needs
- not set in stone
- some teams have shared resources (project management on 2 teams, QA, designers, etc.)
- make sure that allocation works
Thanks! This is super informative for me. I will follow up with you three!
-Agreed! Thank you. Valentina - if you're able to share samples of what your show launch checklists look like, I'd love to take a look as this has been a painpoint for our team with cross-departmental tasks. If not no worries, totally understand! - Cynthia, KUOW
*****COMING UP*****
- Got an idea for a future topic for a call, or something we should consider tackling during a meetup? Let us know below:
+
+
diff --git a/potluck-framework/archive/etherpad/phonecall/pmk_call_05-2019.html b/potluck-framework/archive/etherpad/phonecall/pmk_call_05-2019.html
new file mode 100644
index 0000000..bfd8e36
--- /dev/null
+++ b/potluck-framework/archive/etherpad/phonecall/pmk_call_05-2019.html
@@ -0,0 +1,143 @@
+
+
+
+pmk_call_05-2019
+
+
+
+
+
+
+
+Public Media Kitchen Community Call | May 14, 2019
Every other Tuesday @ 12pm Eastern - 9am Pacific
*****CALL-IN NUMBER*****
1-712.
- Access code: 170 4041
- *6 to unmute!
______________________________________
Welcome to the call!
ROLL CALL: Who are you? Where are you from? What do you do?
- Louise Yang / KPCC / Lead Software Engineer
- Vijay Singh / KPCC / Product Manager
- Luke Lam / KQED/ Technical Program Manager
- Alan Melson / KERA / VP-Digital
- Justin Bowers / KERA / Sr Digital Developer/Designer
- Jess Snyder / WETA / Sr Manager, Web Systems
- Matt Aho / MPR/APM / Web Developer
- Justin Steen / MPR/APM / Software Engineer
- Tim Olson, KQED, Chief Digital Officer
- Nikki Jones/NPR Digital Media/Agilist
- David Gorsline/NPR Digital Media/Software Engineer
- Jason Phan / MPR/APM / Associate Web Developer
- Tiffany Campbell, WBUR, Exec Editor, Digital
- Renee Thompson, Capital Public Radio, Digital Projects Manager
- Erin Ozmat / WNYC / Sr. Product Manager
- Liz Berg/WNYC, Sr. Product Manager
- Rachel Lieberman/WNYC, Support Analyst CRM
- Andrew Kuklewicz, PRX, CTO
- Ryan Cavis, PRX technical lead
- Richard Baniewicz, WHYY, director, online
- Dina Nawas/NPR Digital Media/Product Manager, CRM <-- Salesforce questions can be answered by her!
- Lauren Bracey Scheidt/NPR Digital Media/Director of Product
- Ryan Patecell/NPR Digital Media/Product Manager, Audience Engagement
- Frank J. Gómez, NPR Digital Media - Software Engineer
- Matthew Mcclintoc - WBEZ/Chicago Public Media - Operations Developer
- Dan Newman/NPR Digital Media/Director, Product Design
- Alex Diaz/NPR Digital Media/Scrum Master
- Cp Richardson/NPR Diigital Media/Scrum Master
- Dave Moore, Developer, WBUR
*****TODAY'S TOPICS*****
Survey Results
CRM's
- Vijay Singh (KPCC)
- We rely on APM for some services for our CRM. Workflow and organizational issues. We don't have anyone in house at KPCC to work on the CRM. Good: we don't have to think about anything related about the CRM. Terrible: we don't have resources to make SCPR/KPCC specific updates or changes. APM is supportive w/ getting changes done, but still some workflow issues b/c there's not much connective tissue between live events and websites.
- We're using Salesforce and Enterprise.
- Enterprise is customized heavily, so hard to migrate into Salesforce
- 1st priority: Core team at APM is updating better management of data to make sure all the data is flowing the right way.
- At KPCC: looking at other solutions other folks are using
- Salesforce Native is what we're using
- NGO Connect was acquired by Salesforce months ago. KQED is watching what happens on that.
- Justin & Alan (KERA)
- Team Approach since 2004 -- being sunsetted. Outdated.
- 3 membership programs (1 for each station: TV, 2 radio stations)
- Tessitura -- created for the Metro Opera in NY
- product support was fantastic, flexible
- Convened an internal core team w/ 12-13 stakeholder
- 18 month implementation process
- They had a PM who led the project
- Migrated completely off of Team Approach
- Using existing form for donation form and phone donations
- updated the mapping to work with Tessitura
- TNEW -- ticketing and web side of client app
- got up to speed quickly and prod env set up to feed into Tessitura
- flexible, allows for custom development
- thinking of converting it into a member portal
- self management/serve by members
- Well documented and clean API to go into their core system
- used for EFT conversions and credit card expiration
- All major gifts and givers are in Tessitura
- Quick examples of weird public media uses cases:
- Gifts functionality was around e-commerce model (ie: musem giftshop)
- Not set up for pledge drive scheduling, but KERA worked closely with Tessitura to adapt that
- Seasons vs. Fiscal Year campaign
- Important: Personalization -- Tessitura is focused on that
- T rolled out a BI suite
- integrated w/ emarketing client
- Andrew Kuklewicz PRX
Potluck in Big D(allas)
Will this be before or after PMDMC? (Or concurrent?) Would be good to know for travel booking...
Is there an agenda yet for the Potluck and a RSVP form?
- Not yet, but we will send out an email and slack message once we have it. If you have something you'd definitely want to talk to other stations about, let Louise (KPCC), Vijay (KPCC), Alan (KERA) or Justin (KERA) know
July 11-12
*****Questions/comments*****
- Are there big differences between your membership "types"? Does it easily support that sort of variety?
- Not huge differences, but T does support that amount of differences
- Spent a lot of time going over details of data structure
- Passport access was one difference (Video on Demand), KERA FM members
Question: why didn't you use Tessitura's shopping cart and are using ACD Direct?
- Decided Tessitura needed more time to evolve that product (w/ premiums management). ACD was already doing that.
- Still ongoing conversation for phase 2.
Any advanced / future features you're thinking about for the ticketing side?
- KERA: Using it in a limited way w/ car raffle in TNEW
- Using TNEW to power web forms for car raffle ticket
- Very flexible w/ how it's displayed -- a standard raffle ticket == a seat number
- Capped at 1500 tickets
- Some station events for music station
- thinking of using Tesitura for that and getting rid of ticket fee
Can anyone on Salesforce who works with an “implementation partner” comment on which partner they are working with and how you like working with them?
- Andrew PRX -- on phase 2 of moving over to Salesforce. Idealist Consulting They like them and good support.
Dina what is your contact information? (can I connect to you? tolson@kqed.org; Tim Olson, KQED)
dnawas@npr.org
*****COMING UP*****
- Next call – May 28th
- Got an idea for a future topic for a call, or something we should consider tackling during a meetup? Let us know below, or fill out this form: https://goo.gl/forms/JTtFNbSduotdHGhj2
+
+
diff --git a/potluck-framework/archive/etherpad/potluck/alexa-skills-potluck-2018.html b/potluck-framework/archive/etherpad/potluck/alexa-skills-potluck-2018.html
new file mode 100644
index 0000000..abe0a00
--- /dev/null
+++ b/potluck-framework/archive/etherpad/potluck/alexa-skills-potluck-2018.html
@@ -0,0 +1,143 @@
+
+
+
+alexa-skills-potluck-2018
+
+
+
+
+
+
+
+Bespoken Tools:
https://bespoken.io/bst/
http://docs.bespoken.io/en/latest/tutorials/tutorial_lambda_nodejs/
Virtual Alexa:
https://www.npmjs.com/package/virtual-alexa
+
+
diff --git a/potluck-framework/archive/etherpad/potluck/pmk-jan-2018-collaboration-topics.html b/potluck-framework/archive/etherpad/potluck/pmk-jan-2018-collaboration-topics.html
new file mode 100644
index 0000000..73e9231
--- /dev/null
+++ b/potluck-framework/archive/etherpad/potluck/pmk-jan-2018-collaboration-topics.html
@@ -0,0 +1,143 @@
+
+
+
+pmk-jan-2018-collaboration-topics
+
+
+
+
+
+
+
+Public Media Potluck San Francisco - January 17-18, 2019 (Thursday-Friday)
Session topics and session organizer point people
THURSDAY, JAN 17 SESSIONS
Topic: Simplified way to include Album Art on streaming services. (What API and strategies are useful)
- Joiners:
- - Laura Baumgartner (Colorado Public Radio)
Topic: Elections results scraper
- Joiners:
- - Justin Bowers (KERA)
FRIDAY, JAN 18 SESSIONS
Topic: Conversing on History (how to leverage archival content for conversational interfaces)
- Joiners:
- Erin Ozmat (NY Public Radio / WNYC)
- Justin Bowers (KERA)
Topic: Interactive Storytelling through Voice (what would a "choose your own adventure" story look like on Alexa?)
- Joiners:
- Erin Ozmat (NY Public Radio / WNYC) (one above or this one, depending on what folks might want to collab on more!)
- Louise Yang (KPCC)
- Ryan Cavis (PRX)
- Justin Bowers (KERA)
+
+
diff --git a/potluck-framework/archive/etherpad/potluck/potluck-2018-after-hours.html b/potluck-framework/archive/etherpad/potluck/potluck-2018-after-hours.html
new file mode 100644
index 0000000..7cdf000
--- /dev/null
+++ b/potluck-framework/archive/etherpad/potluck/potluck-2018-after-hours.html
@@ -0,0 +1,143 @@
+
+
+
+potluck-2018-after-hours
+
+
+
+
+
+
+
+Public Media Potluck After Hours | January 2018
Do you want to play board/card games after dinner or after the sessions on Friday?
Are you planning on staying in sunny LA into the weekend and would like to get together with folks?
Put your call out here, or sign up for things other people have proposed.
KPCC Studio Tour
Friday January 26th 12:45 - 1:20
Sign up here:
* Nara Kasbergen
*Jenna Montgomery
*Tommy O’Keefe
* Peter St.Jean
Friday January 26th dinner - Chinese food?
I live in a city with very little good Chinese food, so this is always one of my top priorities when in California, and a close friend gave me some good recs <20 mins away from KPCC
Add your name if interested:
*Louise Yang (YES! -- I always recommend Chinese food to visitors here) <-- Louise knows the real deal with Chinese food. - Ben
*Katie Briggs (YESSS! Can we set up a carpool to SGV?)
*Tommy O’Keefe
AM Run??
- Anyone interested in doing a morning run Thursday or Friday before 9am start? or could someone local LMK if the area is even a good/safe area? I'm staying at the Courtyward Marriot
- * Yes, it's quite safe and in a great area. You can head one block east toward Levitt Pavillion which is a park and do that loop. There are also exercise machines at that park that you are free to use. If you want a longer, more scenic run, trying going west on Colorado, over the bridge and then going north or south on Orange Grove. Beautiful historic houses. If you go north on Orange Grove, you'll pass the Gamble House, whose garage you may recognize from Back to the Future. But I won't be going on the run because I'm lazy in the morning.
- * I'm interested in doing a morning run Friday -- Peter St.Jean
- Peter - awesome. This thread originated from Rebecca Smith - let's coordinate something
Lunchtime Discussion: I'd love to chat with folks over lunch about Ember.js – Ben
- yeah i’m down to talk Ember - Brian
Chat with Arwen Nicks over what she thinks about how people will listen to podcasts over smart speakers and other uses for podcasters
Lunchtime Discussion idea: 1) Happy to do a "movie lunch," where I play the 25-min video recording from NPR's internal panel discussion with Shankar Vedantam on smart speakers (event from 1/24) or 2) I can review the findings from the Smart Speaker usability report we did in fall 2017. — Liz D
BEN from KPCC: Not an after-hours thing, but a link to a repo with the code I wrote to pump up the volume on our flash briefing. https://github.com/Ravenstine/get-it-up
EILEEN from MPR/APM: a little bootstrap library for Alexa skills that should also enable easy swapping and sharing of handlers and intents. https://github.com/APMG/skill-share
Create a basic streaming skill with 14 lines of code!
https://github.com/KUOW/campaign_finance
+
+
diff --git a/potluck-framework/archive/etherpad/potluck/potluck-2018-failure-show-and-tell.html b/potluck-framework/archive/etherpad/potluck/potluck-2018-failure-show-and-tell.html
new file mode 100644
index 0000000..7855021
--- /dev/null
+++ b/potluck-framework/archive/etherpad/potluck/potluck-2018-failure-show-and-tell.html
@@ -0,0 +1,143 @@
+
+
+
+potluck-2018-failure-show-and-tell
+
+
+
+
+
+
+
+KUOW
Our failures
- Election coverage
- Building a site that doesn't get a lot of traffic vs. articles that have an audience
- Unlocking gift
- UI failure, even after user testing
KQED
Our failure
- Machine learning collaboration leads to lack of trust, no progress, because people learn in different ways/have different interests
KPCC
Our failure
- Aesthetic unity release
- Site was too expensive
- Tried ruby + fragment caching, but keys that weren't specific enough led to components showing up in the wrong places
- Too much memory being used
- Oink points out the page types that are most expensive
- Discovered a bad pattern that was leading to pages being too bulky (got overeager with component-based model)
- After making improvements, memory usage is going down, transaction times have gone down
- What we've learned
- Before shipping, do load tests on production ahead of time + don't rely too much on local/staging results
- Question how to optimize a site (is caching the best option?)
- Helpful tools like Oink and New Relic are helpful to point out problem areas in optimization
PRX
Our failures
- Making PRX into a social network
- Bandito app
- Echonest APIs to suggest new music
- PRX beta version
- Exploring identity *while* rebuilding a site
- (What they actually should have done was create Radio Public)
- Dovetail (ad service)
- Network-wide ads are risky
- PMP
- We need to define a minimum viable organization/neutral ground
WNYC
Our failures
- Discover feature on the site
- 9 months of UI development
- .31% of monthly users use the feature
- 50% of all users go to the site for the live stream
MPR
Our failures
- Moving from Eloqua to Marketing Cloud
- Short integration period, lots of differences in features
- No support for double opt-in
- SOAP API + Ruby client
- Scramble to build a hack to make everything work
- Saved money for the org
- If you're picking a new vendor, test your most complicated use cases as early as possible
- Pressure your vendors
- Get a tech call
- Proof of concept
Marketplace
Our failures
- Site maps + taxonomy
- Wasted time on how to structure site maps
- Site maps doubled page views
- Should have been done a lot sooner
- There's lots of Marketplace content to digitize
- Learn how to document things better
- Working at a newsroom pace means things don't get documented
- Leads to repeat work
- How can we teach people how to do other people's jobs?
- WNYC suggestions:
- Writing tests helps figure out where the holes are; add to readme on Git so you're forced to explain what you're doing to other engineers
- Keep a record on Confluence
WHYY
Our failures
- WHYY quiz app
- Initial details
- To drive engagement/acquisition on news-only site
- Mobile-first
- Developed by external vendor
- No documentation
- Unused until a year ago
- Grant requirement leads to relaunch of app
- Questions about PA education funding
- Vendor wanted to relaunch on short timeline
- No basic strategy process
- Nobody asked if a quiz app was appropriate for this use case
- Sunset this year
WGBH
Our failures
- Bring Jazz 24/7 out from registration wall
WBUR
Our failures
- Site and app redesign
- 12-15 Wordpress site down to 1
- Outsource design to an agency
- Wordpress backend
- App issues
- Temporary API instead of actual API
- One bad decision led to a lot of other issues
WBEZ
Our failures
- Trying to create an interesting experience instead of considering what's being created by your station
- Create a radio experience that makes sense in a digital experience
WAMU
Our failures
- "Curb your enthusiasm"
- Going into projects with excessive enthusiasm
- Rebuilding WAMU.org – Excitement led to overestimation of what was possible
- Build in fall-backs, even when internal users say they don't need them
- Be realistic about content you're working with
- Don't cherrypick your content in comps
- Working with a vendor that overpromised
- If a feature feels to good to be true ...
NPR
Our failures
- Social media success dashboard
- Product owner given developers, developers wanted to build in Scala
- Nobody thought about long-term maintenance, and the tool breaks often
- Led to a fear of tech risks for 1+ year
- Seamus editor interface
- Lost lead developer, but no change in timeline
- Should have considered: What are the unknown unknowns?
- No considerations about tech challenges
- We need to be better about testing internal products
+
+
diff --git a/potluck-framework/archive/etherpad/potluck/potluck-2018-not-just-audio.html b/potluck-framework/archive/etherpad/potluck/potluck-2018-not-just-audio.html
new file mode 100644
index 0000000..911f910
--- /dev/null
+++ b/potluck-framework/archive/etherpad/potluck/potluck-2018-not-just-audio.html
@@ -0,0 +1,143 @@
+
+
+
+potluck-2018-not-just-audio
+
+
+
+
+
+
+
+**Not Just Audio: How to visually jazz up your skill and promote smart speakers**
NPR Smart Speaker Expo Panel
- NPR has been spending 2.5 years working on smart speaker skills and forging relationships with vendors
- Expo was way for all departments at NPR to play with smart speaker skills/products
- 11 million newscasts listens happen every month on smart speakers
- Adoption for smart speakers growing more quickly than adoption for smart phones
- Hurdles to getting Alexa to play nice with NPR
- How do we get people to see that NPR can deliver
Discussion
It's tempting to port existing content to smart speakers, but that's not the best strategy
- Figure out what's native to the platform
- Finding ways to adjust workflow and content
Why is there a conflict between smart speaker platform capabilities and what we can provide?
- Initially, platforms were assumed to be assistants, but can be used for longform listening
Editorial projects
- How can people pitch ideas for smart speaker content/skills?
- NPR Story Lab (open to the public!)
What happens when partners dislike something on our smart speaker content/skills?
What can member stations provide that NPR might not build?
- Anything that has to do with parts of day
How can NPR + stations + the network help each other build and promote skills?
- Member stations need to know how to measure success/user activity
- Try a Spark campaign in the smart speaker space
- Smart Speaker 101 Webinar on Wednesday
- NPR has broadcast spots promoing Alexa skill
- Smart campaign explains how to use different smart speakers
- KUOW has a social promo of a host interacting with an Echo
- Missing piece is search/discovery
- There's no such thing as usable search results
- The Current has a spot that demos the song request feature on The Current skill
- Promotions at the end of a skill experience/flash briefing
- e.g. Word of the Day skill promo at the end of NPR newscast
- Give users ideas on skills they're already using
- Installations in stations to raise awareness
Getting users familiar with your skill's features
- Neiman Foundation link from LIz goes here
- What can we do and what should we be doing when it comes to answering user prompts?
- Lists don't work
- Choose your own adventure
- Always give people a next step (John Keefe, Quartz Bot Lab)
- People just want one next step instead of "Here's all the things you can ask me"
- Linear content doesn't work (recipe skill example)
Complementary experiences with visual-enabled smart speakers
- Going beyond here's the best photo for this story
- How do visuals get passed?
- What happens there's not an obvious visual pairing?
- Similar process to 3-D Touch
- Not all devices accomodate 3-D Touch (not all speakers have visuals)
- Partially for super-users, partially as an upgrade to the experience (but lack of visuals doesn't affect the core experience)
- Progressive enhancement
Dynamically inserting ads on on-demand audio
- Can you target devices?
- Could set up different stream specifically for device
- KPCC + Ad Tech
- Can target sepearate platforms/third party apps
- Device-specific ads double tap-through rates
How might we serve people with a disability, elderly people, people in crisis, etc.?
How might we better serve our colleagues in newsrooms?
- Hearken's looking to collaborate on smart speaker skills
Building/measuring/learning
- NPR's experience
- What do we want a prototype to prove?
- What do we want to learn?
- Do we have the editorial latitude to change existing processes
- Is it a good user experience?
- If prototypes are approved, usabilty testing
- Technical build to follow usability testing
- NPR Training Team "Blueprint" goes here
- NPR skill flowchart goes here
- WGBH
- Starting to brainstorm around skills to find ideas, framework for testing
- KPCC
- Came up with lots of possibilities
- Found issues with tech
- Stepped back to prototyping process
- MPR
- NPR WWDTM Prototype
- Audio hyperlinked on PPT links
+
+
diff --git a/potluck-framework/archive/etherpad/potluck/potluck-2018-show-me-the-money.html b/potluck-framework/archive/etherpad/potluck/potluck-2018-show-me-the-money.html
new file mode 100644
index 0000000..23b31d4
--- /dev/null
+++ b/potluck-framework/archive/etherpad/potluck/potluck-2018-show-me-the-money.html
@@ -0,0 +1,143 @@
+
+
+
+potluck-2018-show-me-the-money
+
+
+
+
+
+
+
+**Show Me The Money**
WAMU – https://wamu.org/donate/
- Site redesign in 2017 – spent a lot of attention on donation form UX
- Campaigns have been more successful since redesign
- Membership department fairly hands-off (process was streamlined)
- Working to improve membership form by adding new features
- M&R helping on donate form with analytics/testing
- Recommendation: fewer fields = higher completion rate
- Minimum required info: Name, address
- Is it useful to ask donors if they are existing members
- Greenlighted for EFT
- Requests for upsells
- Once you've picked a donation amount, asking for more money
- Good approach: one-time donor in a certain range (~$50), give them the option to donate $5 monthly
- Dynamic laddering of donation levels
- Done through variable in URL
- Marketing support for membership team
- Build ad units to promote campaigns
- Lesson learned
- Have donation frequency before amount
- Have confirmation of amount before donation
- Use Google E-Commerce tracking (part of GA)
- Lightboxes get 5% clickthrough, but the conversion rate isn't worth it
WBUR – https://secure.wbur.org/WebModule/Donate.aspx?P=GENWEBHART&PAGETYPE=PLG&CHECK=LtaDIMe9SwvId2%2biAbOE2b1YhDw50SikSh2nq0qouhg%3d
- Allegiance creates forms (separate from the website)
- Not a lot of discussion between fundraising and digital team
- More interested in getting big promotional items on the site
- IT owns form maintenance
- Fundraising on their app
- Doesn't bring a lot of money ($1K/mo)
- Done through SMS
- Starting with $5/mo (tip jar philosophy)
WGBH – https://www.wgbh.org/support/makeagift_oct17_2.cfm
- Ads inserted dynamically into their stream
WHYY – https://support.whyy.org/join.php
- Forms are self-hosted
- Membership database is Team Approach
- During redesign, forms were only reskinned
- UX redesign to come later
- Discovery phase for new user flow happening now
- 1. Getting them to donate
- 2. Getting them in the form
- 3. What's the experience after the donation is made?
- Donation processing experience is labor-intensive
- Has a pledge-free stream
- Lots of people sign up, but hardly anyone uses the stream
KUOW – https://donate.kuow.org/donate/web
- New form
- Minimum number of fields
- Don't have to give address
- Demographics of audience – how many of them want to get mail?
- You can set up an account/manage it
- Fixing data management/entry
- Membership team tripled in the last year
- Keeping the form lean is consistently a struggle
- Donation function in Alexa TK
MPR/APM – https://mpr.org/donate
- Completely custom form
- Meets finance/development/membership needs
- Tough to find an acceprtable replacement
- Switch to Salesforce CRM
- Springboard is frontrunner for form replacement
- Recent work: hold on to recurring donations
- Credit card fraud has been an issue
- Make EFT default donation option
- Visa Account Updater (sends updated card info to recurring payments)
KPCC – https://kpcc.org/donate
- Uses same primary form as MPR/APM
- All digital assets done by product team
- Pushdown banner at top of page brings in a lot of donations
- App brings in donations
- New version of app includes Apple Pay, Google Pay
- KPCC Plus
- Pledge-free stream during drives (H/T to KQED)
- Expensive to run
- Part-time employee hired to run second pledge station
- Hard on membership to contact new/existing members
- Dev Ops has to export all current members
- Random tokens emailed to existing/new members
- Users not being able to access stream (user error)
- Usage is very low
- Exit intent modals display pledge messaging during drives (success hasn't been determined yet)
NPR
- Don't take money directly
- Might change with "Donate to NPR" Amazon skill (on hold for now)
- Donation portal – e.g. http://donate.npr.org/politics
- Drives fans of content to their local station's donation page
- Hosts of the shows had competition for year-end giving
- GA tracking how many people click donate button
- In-app donations in NPR One
- Three stations on pilot programs
- Setup is pain point
- Tech requirements
- Specific vendors
- How do we make this as frictionless as possible for small stations?
- No membership database at NPR
- Stations could upload CSV of members to keep members from hearing donation appeals on NPR One
- Build out membership list first? Or open NPR One donations to other stations first?
- Moving to SalesForce for CRM needs
WNYC – http://wnyc.org/donate
- Form is easy to use, business processes are a "rotten onion garbage fire"
- Django app
- CRM is managing payment processing (Netform)
- Working on pulling payment processing away from CRM
- Will that cover all use cases?
- Migrating all user tokens to a new processor
- Accepting non-digital donations
- POC with Stripe
- Lightboxes during campaigns
PRX
- Kickstarter to start Radiotopia
- Didn't do recurring donations
- Considered Patreon, GetChange
- CRM/payment processor uses Stripe, can process recurring donations
- Two campaigns
- Fall and pre- campaign
- Unlock rewards
- Integration with Radio Public
- Marketing tools to bring up donation buttons based on your Radiotopia subscriptions
- When Radiotopia is in campaign, the whole domain is taken over with fundraising
- Don't control/host show sites, but include Sumo on show sites to push donors to Radiotopia
- Moving more toward focus on Radiotopia as an entity, instead of shows
KQED – https://www.kqed.org/donate/gateway.jsp
- PledgeCart
- Membership is separate group that has to grant access
- Firewall between product+editorial and membership+users
- Lab
- Trying to monetize YouTube programming
- Tripled donations since last year (with no lightboxes)
Aubrey Bergauer, California Symphony on leveling up potential users to supporting donors: https://medium.com/@AubreyBergauer
+
+
diff --git a/potluck-framework/archive/etherpad/potluck/potluck-2018-site-overhaul.html b/potluck-framework/archive/etherpad/potluck/potluck-2018-site-overhaul.html
new file mode 100644
index 0000000..aa44a42
--- /dev/null
+++ b/potluck-framework/archive/etherpad/potluck/potluck-2018-site-overhaul.html
@@ -0,0 +1,143 @@
+
+
+
+potluck-2018-site-overhaul
+
+
+
+
+
+
+
+kpcc and whyy relaunched their sites
why would we ever want to overhaul the site??
- kpcc:
- * handed to us from stakeholders
- * started w/ the homepage even though it was least valuable, but stakeholders gonna stake
- * we wanted to tackle it in a strategic approach
- * wanted an overall unification of our brand across all digital products
- * started making the homepage a little more modern and shiny
- * thinking about our brand in the future
- * evolved from newspaper inspiried
- * radical change on the homepage drove the redesign of other pages
- * didn't ship a whole bunch of stuff around in interior pages
- * wanted to be inline w/ the vision of our digital future
- * took a good year to redesign the homepage b/c of stakeholder feedback
- * when unifying the rest of the site, just update aesthetics, but didn't reorganize information
- * moment where we wanted to introduce "prove things with data" to rest of organization
- * homepage was a very heavy lift for digital editorial teams
- * we wanted to be more honest w/ what we were creating on a daily basis
- * most traffic goes to articles, not homepage
- * beta period: managing the new homepage while still supporing the old homepage
- * we doubled the editorial team's workload for 2 months. Oops!
- * 2 months b/c we didn't see a significant enough change in retention in less than 2 months
- * in 1 month ,we were pleased, but other stakeholders were not. they wanted another month
- * learning curve for editorial on what type of content to put on the new homepage. editorial slowly understood how the page flowed, experimented w/ different content types
- * editorial team didn't have time to understand the new workflow till they were forced to in beta
- * Question: Did the new homepage improve page views, user views?
- * Product team: solve user's problems first, not business problems
- * explained user-first design process
- * had better user tests
- * more opportunities to iterate
- * better serve our mission
- * balance b/t stakeholder and user needs
- * empathy for business stakeholders vs. empathy for end users
- * navigating edge cases and desire to please everyone
- * some features are the cost of doing business
- * had to teach the rest of the org. how to think more strategically, get out of personal bias
- * idea of the news hound is WRONG
- * goals set around: return users three visits w/i the week, scroll depth
- * compared scroll rate on old vs. new homepage
- * increaed retention and visits by 5% in a week on new homepage
- * scroll depth increased 5-7x
- * how to get folks comfortable w/ a product development process
- * "Your opinion although interesting, is irrelevant."
- * When we say no, or ask why -- we're not trying to add extra work
- * Let's design a test to prove something out
- * remind people that we're on the same team
- * What we ended up with: scpr.org
- * different versions tweaked based on user testing
- * large "listen live" button still at the top
- * people are more comfortable scrolling
- * the cheese (dopamine hit at the end fo the homepage) ATARI method -- reward at the end
- * SoCal, What's Good?
- * regenerates new content each time about different places to visit
- * we hear direct user feedback about liking the cheese
- * builds a habit around particular product
- * article page
- * play button is more prominent at the top left, like our homepage, trains users that it's at the top left
- * previous site had a full banner at the top left, new page -- single stream of content
- * increase body copy size
- * brought everything into the same grid
- * compared people who listened to audio vs. reading
- * most articles, high read rate 75% average
- * on audio, less than 10%
- * Intended to ship it as an MVP and iterate
- * but haven't been able to return b/c of other projects
- * another ambitious idea: automate homepage
- * analyzing sentiment in an article, come up with score, curve, to order articles on the homepage
- whyy:
- * they had issues
- * sunset newsworks brand
- * whyy organizational site was out of date in terms of best practices (ux/ui)
- * wild west w/ what was on the homepage
- * wanted to merge onto one platform (wordpress + joomla??)
- * wanted to be mobile first
- * wanted a more modern look
- * wanted to give editorial team better tools to produce content
- * spent a lot of time on article template and cms
- * facebook shares are the new homepage
- * issues:
- - CMS interface
- - data mapping
- - migration headaches
- - builing toward automation/building toward a lighter workflow
- - site was slow, cms wasn't intuitive
- - old article type had no structured data
- - display on the site depended on taxonomy
- - everything in joomla was an article. No other content type.
- * data models
- * programs had segments, episodes
- * needed to understand workflow of producers and editors
- * all content had to be migrated to the new CMS
- * needed to gerry-rig the content types into different types for the migration
- * ie: which articles are actually segments, which ones are actually episodes
- * audio -- streamguys links
- * wanted to mirror an API in the CMS
- * that determines the fields
- * new: use advanced custom fields in wordpress
- * got pushback from content owners
- * wanted sharable pullquotes
- * the dream: stay in the story editor and be able to create other objects within it
- * worked w/ outside agency for design
- * spent time on what the information architecture in the end should be
- * spent 2-3 months on the UX of the CMS
- * needed to convert everything to https
- * worked w/ Blue Cadet design firm
- * focused on what they did best: make things visually interesting
- * Pantheon hosts wordpress for them
- * before, self-hosted everything
- * moved to Pantheon b/c of limited IT resources
- * ran weekly delta content during the migration period
- * can't ask content to do double entry for more than 2 weeks
- * had to maintain Newsworks and the new site for 2 weeks (editorial)
- * avoided asking users if they wanted feature when doing user-first research
- * wanted to understand what the pain points were for users
- * realization: some features were the cost of doing business
- * ie: crazy request from member services -- but their job is to solve every problem for every user
- * folded in tv proramming into the website
- * end users are not going to the website to view videos
- * but it was important to business stakeholders, so cost of doing business
- * fighting w/ membership to have our donate button be orange "because it pops"
- * wants to move it to the left b/c that's how people read NOPE!
- * compromise: they will get an orange heart inside the donate button
- * no luxury to push back b/c we see other teams in the hallway and we're all on the same side
- * Walk it back from the tactic to the actual problem or goal we're trying to solve
- * think: "is this a strategy, or am I coming w/ solutions first and applying tactics too soon?"
- * come to me w/ goals or problems, not the solution
- * goals, not solutions
- * What we ended up with
- * still had to serve a lot of stakeholders
- * new navigation focuses on distribution, not verticles
- * old site didn't hae a donate button, just a support link
- * live stream persistent player
- * focus scroll on things immediately consumable and changing
- * bring in relevancy to highlighting certain schedule elements
- * events because people didn't know how to find events on the old page
- * feed that pulls from event content type
- * topics as navigation
- * doesn't deter or detract
- * people don't actually use it
- * article
- * another type of article -- magazine/enterprise style
- * segments w/ podcasts, logo and subscribe to podcast links at the top
- * inline audio doesn't go into persistent player
- * persistent player:
- * stream does not start up after on demand audio stops
- * related content
- * mindful about the type of programs/content that gets pulled in
- * almost failure re: share CTA
- * instead of sharing, an impact CTA: "education your friends" or "Tell people about education problems" for sharing buttons
- * What publishes to fb?
- * YOAST plugin: manipulate metadata for social sharing
- * Question: Do you use the bottom spot for promos?
- * Yes
- * also have global notification banner for pledges and giving tuesday
- * Menu disapperas when scrolling down, but comes back up when scrolling up
Vijay asks: How have you pushed user-first thinking in your org?
PRX:
* send everyone through the matter program on design thinking
* so everyone has the same shorthand
Marketplace
WNYC
- * freelancer who runs user testing experiments
- * helpful for design iterations
- * stakeholders asking for a solution
- * product's job in product to figure out what the larger goals are
- * asking a lot of questions, learning processes, being patient
How do people get ahead of things that come up?
- * WNYC: quote caraousel
- * do other people want to use this? NOPE
- * death sex and money:
- * embed the quote carousel in an article
- * dev copied all the code and put it in an S3 bucket
- * new checklist provided to all shows re: embedding, digital extensions
- * invite whole org for demo days
- * provide ways for producers to generate things w/o product team
- * modules, toolkits, self service
- * build tools that multiple producers can use
- * KPCC:
- * get rest of org to understand how we work as an agile scrum team
- * unless it's a real fire, put it in the sprint
- * manage requests of your team
- * a form that collects pitches for the product team
- * what are you trying to do?
- * what user is it for?
- * what problem are you solving?
- * sending that link to people, or filling it out with them -- there's no way around this process
- * doing more upfront work to defend against last minute ask
- * bottom up: talking to people on the same level but on other teams about our process
- * biweekly meetings w/ major departments
- * NPR
- * expand design thinking outside of the digital media team
- * don't talk about design thinking by naming it
- * do the things and methodlogy, but don't call it that
- * don't evangelize design thinking
- * usability testing
- * invite everyone to watch testing
- WHYY
- * monthly backlog reviews w/ other departments
- * flag any editorial initiatives
Neilson has a good report on colors and best color for donate button
+
+
diff --git a/potluck-framework/archive/etherpad/potluck/potluck-2018-smart-speaker-skills-design.html b/potluck-framework/archive/etherpad/potluck/potluck-2018-smart-speaker-skills-design.html
new file mode 100644
index 0000000..5a72aea
--- /dev/null
+++ b/potluck-framework/archive/etherpad/potluck/potluck-2018-smart-speaker-skills-design.html
@@ -0,0 +1,143 @@
+
+
+
+potluck-2018-smart-speaker-skills-design
+
+
+
+
+
+
+
+***Smart Speaker Skills Roundup***
WBEZ
Skills they have
- Vocalo Radio music station
Wish they could
- Enable additional features (metadata, what’s next)
- BEZ skill (live stream, using API endpoint)
- Provide something that’s not a live stream
- Skip, pause, resume
Exploring
- Flash briefing
- Additional programming
- Reading headlines
- Google Home
WBUR
Skills they have
- Add WBUR to flash briefings
- “Play WBUR” on Google and Alexa
Limitations
- Making sure people can get to original BUR content as soon as possible
Wish they could
- Robust app that gives back WBUR content
- Had more time to look at metrics
- Figure out levels (audio is super quiet right now)
- A common issue is the audio levels are low
- KPCCBen wrote a skill to boost the audio levels of the news cast
WGBH
Skills they have
- WGBH skill “Alexa, play WGBH” (instead of TuneIn)
- Vendor: Dream Decks (sp?)
- Skill for specific daily show (plays when lives, plays most recent ep)
- Frontline (play most recent podcast ep)
- Flash briefing for local content
Exploring
- Kids skills (choose your own adventure)
WHYY
Exploring
- Trying not to duplicate existing skills (e.g. live stream)
- 30 year Fresh Air archive
- Working with Audioburst (searches sound clips)
- Have to build some kind of user-facing product using archive
- Making on-demand audio + podcasts available
- Children’s podcast choose your own adventure
Limitations
Marketplace
Skills they have
- Flash briefing for three shows
Exploring
- Basic skill
- Listen to latest show
- Tell me what I’m listening to
- Skills around content initiative/specific projects
- How to better discoverability of audio
APM/MPR
Skills they have
- Flash briefings
- Newsroom workflow has changed to accommodate for Alexa
- The Current
Exploring
- Text-to-speech for Alexa to read headlines/briefings
- Streaming (Stream Guyz vs. experiments in house)
- Mystery songs
- Classical music trivia/puzzles
- Podcasts as storytelling/audiobook (e.g. In the Dark)
- Kids podcasts (Brains On)
- Using smart speakers to dig into archive
- Elasticsearch + smart speakers
NPR
Skills they have
- Flash briefings
- NPR One skill
Exploring
- NPR One skill
- Rewriting from third-party initial code
- Improving the user experience
- Station streaming to replace TuneIn integration
- "Play WXYZ" or "Play NPR" launches local NPR stream instead of TuneIn
- If WXYZ has their own skill, it will point there instead
- Podcasting skill
- Access entire podcasting catalog
- On hold: Amazon is working on their own skill that pulls from a provided catalogue of content
- WWDTM quiz
- Ask NPR skill
- "Ask NPR to explain the debt ceiling" brings up an NPR story about the debt ceiling
- Visual newscast skill
- Echo Spot and Echo Show
- What does public radio's position look like when it comes to visuals? Do we want to compete in that space?
- Google Home
- Standalone "Actions" are possible, but audio possibilities are limited
- Universal taxonomy of utterances
- Can all platforms share one set of utterances?
- Time split between building skills *and* learning more about the process
WNYC
Skills they have
- Flash briefing
- Publish date needs to be in last seven days
- "Play WNYC" without iHeart/TuneIn
- Play stories based on topic
Exploring
- Login/auth
- Don't build it on top of Amazon Cognito
- Play specific program
Limitations
- Interaction pathways
- Taxonomy/utterances
PRX
Skills they have
- None, Radio Public is working more on consumer-facing products
Exploring
- Audio For Good hackfest
- Choose your own adventure skill
- Radio Public
- Working on skills, plus other products for other smart speakers
- Audio clip remix
- If a skill, what does it do?
- Thinking about marketing/membership messaging
- Kids Listen community (http://www.kidslisten.org/)
- Public radio podcast skill
KPCC
Skills they have
- Flash briefing
- Currently just the newscast
- Future improvements
Exploring
- Search for news by topic
- Unsure if that's something users want
- Master skill
- Play live stream
- Rewind the live stream
- Ask for events
- Was than an earthquake?
- News quiz
- Survey skill
- Interactive voter guide
Limitations
- Alexa is used passively
- Resources – content generation
KQED
Skills they have
Exploring
**Check out Mosiac**
KUOW
Skills they have
- Amazon's donation app (choose what org you want to donate to)
Exploring
- Flash briefing
- Listen skill
- Collaborating on future skills
- Ratings skill for podcast focus groups
- Super-listeners help vet podcast pitches
Limitations
WAMU
Skills they have
Exploring
- Flash briefings first
- Can stations fold their content into NPR's flash briefings/newscasts?
Discussion
- What's possible with donations + Alexa?
+
+
diff --git a/potluck-framework/archive/etherpad/potluck/potluck-2018-tips-and-tricks-design-product-mgmt.html b/potluck-framework/archive/etherpad/potluck/potluck-2018-tips-and-tricks-design-product-mgmt.html
new file mode 100644
index 0000000..9022e51
--- /dev/null
+++ b/potluck-framework/archive/etherpad/potluck/potluck-2018-tips-and-tricks-design-product-mgmt.html
@@ -0,0 +1,143 @@
+
+
+
+potluck-2018-tips-and-tricks-design-product-mgmt
+
+
+
+
+
+
+
+**Tips and Tricks: Non-Dev Edition**
- InVision's Craft plugin for real content in comps (Sketch or PSD)
- Minimum Viable Journal – keep a super basic log of conversations/activities throughout the day
- Richard Feynman's "Atomic Sentence"
- Check out McNally Jackson's Five Year Journal
- Make decisions driven by metrics
- Heatmaps on Hotjar
- Usertesting.com
- Write GA arrays to browser console
- Chrome extension called "Data Slayer"
- Zeplin: translates PSD/Sketch files into code
- Amazon's Device Farm for QA
- For idea pitches:
- Ask "WHY?"
- Ask non-product folks: "How do we measure it?"
- Ask "Who's going to maintain this after it launches?"
- Block out time to be out of meetings (and eat lunch)
- Listen for phrases like "X side," "us and them" "when we did that ..."
- Slowly builds divide between parties
- There are no sides, so point it out to people
- Put your work on the walls
- Make your thought processes visible
- Build trust, build visibility, build empathy
- Put your meeting notes in Confluence, and log your decisions
- Zenhub: Put your Git tickets through Agile
- No bad ideas in brainstorming
- Make your list of strategic goals managable – One per season? Per year?
- Giving people a prescriptive way to solve a problem
- e.g. Roll out an agile scrum process for another department
- Making communication more useful
- Getting people to start thinking the way we think
- Reduce your tracking tools to as few as possible
- e.g. Include OKR/goal tracking along your with your tickets
- Socialize your roadmap
+
+
diff --git a/potluck-framework/archive/etherpad/potluck/potluck-2018-tips-n-tricks.html b/potluck-framework/archive/etherpad/potluck/potluck-2018-tips-n-tricks.html
new file mode 100644
index 0000000..15d602d
--- /dev/null
+++ b/potluck-framework/archive/etherpad/potluck/potluck-2018-tips-n-tricks.html
@@ -0,0 +1,143 @@
+
+
+
+potluck-2018-tips-n-tricks
+
+
+
+
+
+
+
+Tips & Tricks
slate -- window management https://github.com/jigish/slate
ngrok -- opens a tunnel to your dev machine
pasteapp -- clipboard management
jq -- awk, but for json
MITM -- http proxy
Paintcode -- generates graphics assets for an app (iOS), can import from sketch https://www.paintcodeapp.com/
Codable -- encode/decode model objects for iOS dev
AWS lambda tricks:
- * override the logging
- * setup metrics on the log group
Chrome developer tool, wait() shows when the promise resolves
console.table(obj) -- show object in table format
zenhub -- track issues across repos
put gem management in docker-compose volumes
dinghy docker -- faster, friendlier docker for osx, web proxy, runs dns server inside
bisect in rspec -- gives you seed of how it randomized the tests. can rerun exact order of tests if you have seed
semantic-release -- version management & package publishing
commitizine -- tooling around git commits
bartender
https://foundation.zurb.com/emails/email-templates.html
document crisis, complex issues, prolongued bugs
thirty-thirty (app) -- create a flow of your day, time management
q-button on trello -- just filter for projects you're on
set accessibility hot key to zoom to quickly zoom in on screen
Hey taco -- give people thanks on slack
geekbot -- virtual standup in the same timezone
+
+
diff --git a/potluck-framework/archive/phonecall.md b/potluck-framework/archive/phonecall.md
new file mode 100644
index 0000000..4fd7ceb
--- /dev/null
+++ b/potluck-framework/archive/phonecall.md
@@ -0,0 +1,16 @@
+# Call Notes Archive
+
+* [12/19/2017](etherpad/phonecall/PublicMediaPotluck_Call-121917.html): fundraising and potluck conference agenda
+* [02/13/2018](etherpad/phonecall/PublicMediaPotluck_Call-02132018.html): open source software
+* [02/27/2018](etherpad/phonecall/PublicMediaPotluck_Call-02272018.html): database architecture
+* [03/13/2018](etherpad/phonecall/PublicMediaPotluck_Call-03132018.html): js cage match (React, Vue, Angular)
+* [03/27/2018](etherpad/phonecall/PublicMediaPotluck_Call-03272018.html): js cage match 2 (Ember, isomorphic React)
+* [04/10/2018](etherpad/phonecall/PublicMediaPotluck_Call-04102018.html): mobile app development
+* [04/24/2018](etherpad/phonecall/PublicMediaPotluck_Call-04242018.html): css management
+* [05/08/2018](etherpad/phonecall/PublicMediaPotluck_Call-05082018.html): automated tests
+* [05/22/2018](etherpad/phonecall/PublicMediaPotluck_Call-05222018.html): data visualizations
+* 10/23/2018:
+* [11/05/2018](etherpad/phonecall/pmk-call-2018-11-05.html): project management in public media organizations
+* 12/04/2018: elections fun\!
+* [05/14/2019](etherpad/phonecall/pmk_call_05-2019.html): KQED potluck feedback and CRMs
+* [06/11/2019](etherpad/phonecall/PMK-call_06-11-19.html): Public Radio Incubation Lab and core web technologies
diff --git a/potluck-framework/archive/potluck.md b/potluck-framework/archive/potluck.md
new file mode 100644
index 0000000..633896a
--- /dev/null
+++ b/potluck-framework/archive/potluck.md
@@ -0,0 +1,14 @@
+# Potluck Notes Archive
+
+## January 2018
+
+* [Session Topics](pmk-jan-2018-collaboration-topics.html)
+* [Smart Speaker Skills Design](potluck-2018-smart-speaker-skills-design.html)
+* [Failures Show and Tell](potluck-2018-failure-show-and-tell.html)
+* [Tips and Tricks for Developers](potluck-2018-tips-n-tricks.html)
+* [Tips and Tricks for Design and Product Managers](potluck-2018-tips-and-tricks-design-product-mgmt.html)
+* [Let's Overhaul the Site!](potluck-2018-site-overhaul.html)
+* [Smart Speakers Skills Build](alexa-skills-potluck-2018.html)
+* [Public Media Potluck After Hours](potluck-2018-after-hours.html)
+* [Not Just Audio: How to visually jazz up your skill and promote smart speakers](potluck-2018-not-just-audio.html)
+* [Show Me the Money!](potluck-2018-show-me-the-money.html)
diff --git a/potluck-framework/phonecall.md b/potluck-framework/phonecall.md
index ef243c0..80f8326 100644
--- a/potluck-framework/phonecall.md
+++ b/potluck-framework/phonecall.md
@@ -29,7 +29,7 @@ KPCC uses [freeconference.com](https://freeconference.com). Whatever service yo
* Turn off name announce
* Put it in QA mode or some other mode so that everyone except the host is muted by default but participants can unmute themselves.
* Dial into the conference call five minutes beforehand to make sure all audio is set up
-* Remind participants of how to unmute (for example, *6)
+* Remind participants of how to unmute (for example, \*6)
* Make sure the designated note-taker is ready on the etherpad
* Make sure the facilitator can see the etherpad for any questions that come up
* 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).
@@ -38,21 +38,4 @@ KPCC uses [freeconference.com](https://freeconference.com). Whatever service yo
### after the call
* have the note-taker revise or clean up the notes
-* update the Call Notes Archive (below) with a link to the notes
-
-
-## Call Notes Archive:
-* [12/19/2017](https://etherpad.scprdev.org/p/PublicMediaPotluck_Call-121917): fundraising and potluck conference agenda
-* [02/13/2018](https://etherpad.scprdev.org/p/PublicMediaPotluck_Call-02132018): open source software
-* [02/27/2018](https://etherpad.scprdev.org/p/PublicMediaPotluck_Call-02272018): database architecture
-* [03/13/2018](https://etherpad.scprdev.org/p/PublicMediaPotluck_Call-03132018): js cage match (React, Vue, Angular)
-* [03/27/2018](https://etherpad.scprdev.org/p/PublicMediaPotluck_Call-03272018): js cage match 2 (Ember, isomorphic React)
-* [04/10/2018](https://etherpad.scprdev.org/p/PublicMediaPotluck_Call-04102018): mobile app development
-* [04/24/2018](https://etherpad.scprdev.org/p/PublicMediaPotluck_Call-04242018): css management
-* [05/08/2018](https://etherpad.scprdev.org/p/PublicMediaPotluck_Call-05082018): automated tests
-* [05/22/2018](https://etherpad.scprdev.org/p/PublicMediaPotluck_Call-05222018): data visualizations
-* [10/23/2018]:
-* [11/05/2018](https://etherpad.scprdev.org/p/pmk-call-2018-11-05): project management in public media organizations
-* [12/04/2018]: elections fun!
-* [05/14/2019](https://etherpad.scprdev.org/p/pmk_call_05-2019): KQED potluck feedback and CRMs
-* [06/11/2019](https://etherpad.scprdev.org/p/PMK-call_06-11-19): Public Radio Incubation Lab and core web technologies
+* update the [Call Notes Archive](archive/phonecall.html) with a link to the notes
diff --git a/public-media-potluck-january-2018.html b/public-media-potluck-january-2018.html
index 23a797b..df17330 100644
--- a/public-media-potluck-january-2018.html
+++ b/public-media-potluck-january-2018.html
@@ -29,7 +29,7 @@ Where and When
Schedule
- informal events are on this etherpad
+ informal events are on this etherpad
Thursday January 25, 2017
@@ -39,7 +39,7 @@
Schedule
10:00 - 11:30
Smart Speakers Skills Design
- notes
+ notes
Concentrating on Alexa, each organization should come prepared to answer these questions:
@@ -56,14 +56,14 @@ Schedule
1:30 - 3:00
Failures show and tell
- notes
+ notes
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.
3:30 - 5:00
Tools, tips, and tricks breakout session
- Tips and tricks for developers
- Tips and tricks for design and product managers
+ Tips and tricks for developers
+ Tips and tricks for design and product managers
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.
@@ -81,7 +81,7 @@ Schedule
Breakfast
10:00 - 11:30
Let's overhaul the site!
- notes
+ notes
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.
12:00 - 01:00
@@ -89,16 +89,16 @@
Schedule
1:30 - 3:00
Smart Speakers Skills Build
- notes
+ notes
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
Not Just Audio: How to visually jazz up your skill and promote smart speakers
- notes
+ notes
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?
3:30 - 5:00
Show me the money!
- notes
+ notes
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.
5:00 - 5:15
