Time/Place

• Time: 11:30am Eastern Daylight Time US (UTC-4)
• Call-in: DuraSpace conference line
  • 209-647-1600,   117433#

Attendees

• Julie Allinson 
• Chris Awre (second half)
• Robert Cartolano
• Stefano Cossu
• Tom Cramer
• Steve DiDomenico
• Jon Dunn
• Declan Fleming
• Michael Friscia
• Michael J. Giarlo (regrets)
• Michael Gonzales
• Ladd Hanson
• Wolfram Horstmann
• Neil Jefferies
• Susan Lafferty
• Mark Leggott
• Jonathan Markow
• Steve Marks
• Tom Murphy
• Matthias Razum
• Glen Robson 
• Robin Lindley Ruggaber 
• Dan Santamaria
• Tim Shearer
• Thorny Staples
• Jim Tuttle
• David Wilcox
• Andrew Woods
• Patrick Yott

Agenda

Previous Actions

• David Wilcox will pull together a list of current green fields and upgration by the next leaders call
• Declan Fleming and David Wilcox will compile a list of vendors and information to support outreach
•  Stefano Cossu will work on a review of the website
• Tom Cramer will contact Cliff Lynch to request a room for the Data Mandate discussion pre-CNI
• Susan Lafferty will write up the Australian steps toward making funded research data visible and harvestable
• Michael J. Giarlo will look into F4 performance issues and, if appropriate, engage Hydra and Fedora communities about corroborating/troubleshooting/resolving them

Minutes

1. Review of raising developer contributions.
   1. The governance model that equates $ with dev time as more fungible is on the right track 
   2. How do we quantify and track contributions? Honor system? Peer pressure about showing up on code sprints (or not) has worked OK in the past
   3. But we can't really differentiate between .2 and .3 FTE. 
      1. Ad hoc contributions are also useful, and seem to be growing
      2. Overall Andrew is happy with current trajectory
   4. and how do we push people off/down if they don't meet commitments? 
      1. should "credit" for FTEs allocated be applied to the next year?
         1. or would this be too much delayed gratification?
   5. bottom line is we're hurting for developers
      1. how do we establish the norm of getting more contributors on from more sites? 
      2. how do we provide onramps for new developers to come up to speed?
         1. more modular architecture helps–work on just a piece, not a whole monolith
         2. make clear that new developers are welcome through invitation and communication
         3. Andrew sometimes sends tickets triaged by level of expertise required–entry tix for expert tix
   6. Fedora Camp. Get a colocated Fedora Dev Camp; structured curriculum focused on enhancing code, bringing new devs on. 
      1. AGREEMENT: Lets pilot this in late 2015 or early 2016. Start stateside. See if it works out then go international.
   7. BugFix-a-Thon. Schedule a 20-dev, distributed effort to squash a ton of bugs, and bring a bunch of new devs on line.
      1. AGREEMENT: Worth investigating. David & Andrew will investigate to see how this could be framed, timed. 
   8. Hold joint code-sprints with Hydra & Islandora. Good idea. 
2. Current Fedora 4 implementations
   1. How do we keep this list up to date? How do we make the most of it? 
   2. Notes:
      1. Virginia Tech in soft launch.  
      2. Royal Library of Denmark likely in prod or near prod by now.
   3. Need it for mktg, to show degree of traction. Want a mix of regions, sizes, types, greenfield/upgrations.
   4. "An Ambassadors list"
   5. Start a list / table in Confluence with updated case studies
      1. look at mining the panels from CNI and other meetings on Fedora 4 demos
      2. David to curate this content
3. Stefano's initial review of website
   1. David & Stefano forming an elite subcommittee to refresh content on the Website. 
      1. Indicate interest in joining to David & Stefano. 
      2. Patrick Yott is committed (in pencil); have a lot of Drupal talent in house.
   2. Duration = 6 months if we use current Drupal theme. 
   3. also looking at improving the Fedora registry
   4. Send any additional comments on content
4. Steering Elections update.
   1. Votes are still open; voting for 3 new Steering members; each institution only gives one vote.
5. Upgration Support / Next Sprint
   1. do another round of upgration pilots. 
   2. Glen sez that moving from F3 to F4 requires a paradigm shift in mentality. Need a map of concepts from F3 to F4. 
      1. starter doc is already on the wiki. (Link?)
      2. maybe also look at the web UI; what is a PID in F4? (Andrew says it becomes a DC identifier)
      3. see Glen's note to Fedora-Leaders. 
      4. what next? 
         1. do an ad hoc phone call with Fedora Tech and Fedora Community
         2. make it a Webinar?
         3. this needs more discussion; David, Andrew & Jonathan will discuss, frame and reflect back out to Leaders. 

Actions

• Lets pilot a Hackathon for Fedora Developers in late 2015 or early 2016

• David Wilcox & Andrew Woods to investigate how a Bug-Fix-a-Thon could be framed, timed (20 devs for 1 week bug fix party). 
• David Wilcox to begin capturing, curating content for an "ambassadors" list of F4 implementations. Start a list / table in Confluence with updated case studies
• David Wilcox & Stefano Cossu to form an elite subcommittee to refresh content on the Website over next 6 months
• Patrick Yott to confirm participation on elite subcommittee by end of this week
  
• All: send any additional comments on website content in to Leaders or the Elite Subcommittee
• All: Steering election is still open; voting for 3 new Steering members; each institution only gives one vote. Votes open another 1-2 weeks. 
• Jonathan Markow, David Wilcox, Andrew Woods to discuss the F3 -> F4 mental mapping / upgration support issues raised by Glen in email to leaders, reflect back to Leaders