March 2018 Developer Congress Meeting Agenda


Note: please consider attending and separately registering for LDCX on the preceding Monday through Wednesday.


  • Focused face to face time for Samvera developer community
  • Knowledge sharing, new developer on-boarding, & paring time
  • Community code exchange
  • Move community development goals forward

Dev Congress Rough Schedule

Thursday AM

8:30 am to 9 am: Coffee and introductions

9:00 am to 9:30 am: Start of Conference 

Fast Introductions

One Minute Curated Session Pitches (sign up here)

Plenary Topics (10 minutes max per topic, if further discussion is needed a group can be spun off)

9:30 AM to 11:10 AM: Group Work or breakout to

Component Maintenance discussion in Partners Meeting

11:10 am to 11:30: Groups report on morning work

Thursday PM

1:00 pm to 4:45 pm: Continuation of Group Topics

4:45 am to 5:00: Groups report on morning work

Friday AM

8:30 am to 9 am: Coffee

9:00 am to 9:30 am: Road map (sorta). Where would we like to go?

  • Road Map (more of a wishlist):
    • Blacklight 7 - requires bootstrap 4 - we should use it!
    • Valkyrie Hyrax
      • Data mapper pattern instead of Active Redord
      • Advantage: you can run tests w/ fedora objects just in memory
      • Advantage: you can swap out fedora for other persistence stores
    • Hyrax decoupled feature specs
    • Hyrax UI / API separation
    • Extract Plugins
    • Actor Stack refactor → DRY Transactions
    • Solrizer is going away
      • It's functionality has been incorporated into AF See issue AF #1303
      • Can that really happen? 
      • cam156 is the product owner and will move this forward one way or another
    • Hyrax Accessibility (A11y) - bess will talk to Mark Bussey about next steps
      • Explore the impact of Bootstrap 4
    • Hyrax Analytics - 
    • Documentation
      • Migration of fully populated repositories and documentation of the process
      • Component maintenance will involve documentation review and production
      • Frustrations with current documentation site:
        • Empty pages (remove them and replace them with TODO tickets)
        • Review wiki and replace with pointers to site
        • Review website and replace with pointers to site
        • Add a header to the samvera wiki with a reminder that techncial documentation belongs in the site
        • Bess will talk to Justin about how to remove and replace it with a pointer to the new location of that info

9:30 am to 10:00 am: Repitch and reconvene groups

10:00 am to 11:10 am: Group Work

11:10 am to 11:30: Groups report on morning work

Thursday PM

1:00 pm to 4:45 pm: Continuation of Group Topics

4:45 am to 5:00: Groups report on morning work

Potential Topics (Add your ideas here)

Development Ideas (Add your ideas here)

  1. Extract Sipity from Hyrax to an engine or microservice. ~1.5 days (justin)
  2. Bug fixes for v2.1.0 release (Lynette Rayle)
  3. Core components working group - prioritize work, populate backlogs, kick off work for phase 2 of the WG (bess)
  4. Optimization of nested collection indexing.  (LaRita Robinson) minimally address issue: which may require changes in ActiveFedora (help wanted)
  5. Explore dry-transaction ( as a potential replacement for the actor stack (time box to 1 day) (tamsin woo)
  6. How do we onboard new developers to the community?  What could be covered quickly - e.g. in 4 days or so at Samvera Camp?  What things need more time and mentoring from others in the community? (Mark Bussey)
  7. If you were going to attend an Advanced Samvera Camp, what topics would you like to see covered? (bessMark Bussey)
  8. Sorting tables. The final frontier.

Development Ideas, Prioritized (for later use, pls do not edit)

Well Defined
Achievable by Friday