Topics mentioned:
* US Navy Risk matrix for incidents by severity and probability (from Marc) severity = loss of mission capability or mission-supporting assets down to minor delay, damage or inconvenience vs. probability of occurrences in broad categories from likely, probable, possible, unlikely.
* Zach's demo using Planet Nine smart contracts framed in a FedWiki platform, showing basics; a discussion of how to mark this out as a distinct point where we're using a "push" model with an external service.
* Crossing the Chasm as a context for making FedWiki more accessible in various contexts; work in progress for making the platform more ready to adapt to opportunities (CoffeeScript and jQuery modernization). Incidentally "Rename Page" and non-US-ASCII page title sand slugs discussed as examples of opportunities/barriers.
* Request from Marc for a chunk of time to record how to master use of a particular plug-in per week, a demonstration library as videos which we could review and revise; Marc will handle putting these up; timeboxed segment at the beginning of the second hour (for best attendance) but limited to this purpose to allow the Sunday calls to be more free-ranging.
* Ratio of positive to negative social strokes in building trust in a human social context; Eric's observation that DevOps frequent releases, XP promiscuous pairing, TDD and pairing together as examples of high frequency interactions allowing maintaining social trust.
* Techniques requiring experiential learning and high tolerance for failure and recovery, or learning experientially from an experienced practitioner who is also a good guide for learners (not distant in having high-expertise concepts).
* Communicating with leadership up the hierarchy, getting alignment by telling a story consistent with the org's priorities which stays coherent from details up to a brief practice + rationale statement. (Brian)