You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

Time/Place

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

Attendees 

Agenda

  1. Announcements
    1. Candidate Recommendation released!
    2. AWS Graph Store (Neptune)
    3. Oxford Common Filesystem Layout meeting... tomorrow, Friday, Dec 1st
  2. Needing volunteers
    1. New Fedora Clustering configuration
      1. Testing volunteers?
    2. Fedora workshop leader for Code4Lib 2018 in Washington, DC, February 13-16
      1. Esmé Cowles and Yinlin Chen
    3. Facilitator for Fedora user group meeting at 2018 Digital Initiatives Symposium in San Diego, April 24
      1. Danny Bernstein?
    4. Fedora exhibitor at Southern Miss IR Conference in Hattiesburg, MS, April 26-27
      1. ??
    5. Creating an auto-invite Fedora slack page?
      1. https://fedora-project.slack.com/
      2. Like: http://slack.samvera.org/
      3. Using: https://github.com/rauchg/slackin
  3. 4.7.5 release - Planning for January 2018
    1. Are there any missing bug fixes?
    2. Release manager?
  4. Discussion of Real Word Objects and Fedora
    1. Any objection to relaxing Single Subject Restriction?
  5. 5.0.0 release
    1. API Alignment
    2. Pairtrees?
    3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      1. Is tying Memento creation to modeshape a bad idea?
        https://github.com/whikloj/fcrepo4/blob/fcrepo-2617/fcrepo-kernel-modeshape/src/main/java/org/fcrepo/kernel/modeshape/services/VersionServiceImpl.java#L72
    4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  6. Beyond 5.0.0 - Areas of improvement
    1. Persistence?
    2. Journaling?
    3. Simple, synchronous query?
  7. Tickets requiring attention
    1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - waiting on feedback from Chris Colvard
    3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - ready to go? Danny Bernstein?
    4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - ready to go? Danny Bernstein?
  8. ...
  9. Tickets In-Review

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Ticket Summaries

  1. Please squash a bug!

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  2. Tickets resolved this week:

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  3. Tickets created this week:

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Minutes

  • No labels