Time/Place

This meeting is a hybrid teleconference and slack chat. Anyone is welcome to join...here's the info:

Attendees

Agenda

  1. Upcoming Sprints
    1. Please sign up
    2. Sprint 1: Release 5.0
      1. Optimally we start Sprint 1 with a release candidate
      2. Mostly complete documentation
      3. Wrap up the compatibility test kit
    3. Sprint 2: (if 5.0 is release) Ecosystem Tools
      1. Camel Toolbox
      2. Java Client
      3. Import/Export
    4. What is the best way to prepare as a team?
      1. Proposal:  mini sprint for external content and minor spec alignment issues that are coming out of the CTS development.
      2. Alternative to a mini sprint:  form group willing to commit to doing (1?2?3?) of the following small things each week:
        1. work a minor bug
        2. review a documentation page
        3. write a new CTS test (lots of opportunities)
        4. fix an existing CTS test (lots of opportunities here as well)
  2. Getting to 5.0 Release Candidate
    1. 5.x Documentation Effort matrix
    2. In progress tickets
    3. Remaining external content (low-hanging: ie volunteers?, mini-sprint?) issues:


    4. All API Alignment Issues


  3. Closing Fixity conversation:  
    1. UMD + NLM design collaboration
    2. Andrew's suggestion of a "pluggable module"
      1. (What is a pluggable module in fedora today? Does that notion exist independently of API-X?)
  4. <Add your agenda item here>

Ticket Summaries

  1. Please squash a bug!


  2. Tickets resolved this week:


  3. Tickets created this week:


Minutes