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

Compare with Current View Page History

« Previous Version 8 Next »

Time/Place

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

Attendees 

Agenda

  1. Fedora 4.7.1 release status
  2. Maven GroupId for API-related code
  3. Spec effort: how to trigger fixity checks
    1. Esmé Cowles : via Want-Digest
    2. empty-body POST to a fixity container
    3. just screaming "FIXITY" at your repo
  4. Import/Export sprint update
  5. New public Fedora calendar (iCal)
  6. Defining/Documenting the Fedora API with http://swagger.io/
  7. Comments for participant in last week's Fedora Camp?
  8. ...
  9. Status of "in-flight" tickets

    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

  1.   Feodra 4.7.1 release
    • Bethany Seeger kindly volunteered to do the release, and will have a RC later today
  2. Unknown User (acoburn) pointed out fcrepo-vocabulary that represents various RDF vocabularies in Java.  It will be an alternative to our current flawed string-concatenation method.
    • Unknown User (acoburn) wishes to use it soon, but it will have to have a maven release, and to do so, he's suggesting we change the group name from org.fcrepo to org.fcrepo.api (and has issued a PR)
    • A. Soroka has a mild preference for "org.fcrepo" because people more commonly put API stuff there.
    • Unknown User (acoburn) agrees, but would like to avoid reusing/re-purposing existing artifact names and allow for separate version numbers for API stuff
    • Andrew Woods suggested an alternative of instead of changing group names now, just find new artifact names for other stuff later.
      • The approach going forward will be to change implementation-specific group ids.
      • The PR will be closed (not merged) and a release will be made

 

 

  • No labels