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

Compare with Current View Page History

« Previous Version 9 Next »

Time/Place

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

  • Time: 11:00am Eastern Daylight Time US (UTC-4)
  • U.S.A/Canada toll free: 866-740-1260, participant code: 2257295
  • International toll free:  http://www.readytalk.com/intl 
    • Use the above link and input 2257295 and the country you are calling from to get your country's toll-free dial-in number
    • Once on the call, enter participant code 2257295
  • IRC:

Attendees 

Agenda

  1. OSGi:

    fcrepo-kernel -> fcrepo-kernel-api
    fcrepo-kernel-impl -> fcrepo-kernel-modeshape

    Standard practice with OSGi bundles is that any package with "impl" or "internal" is not exported.

  2. 4.3.0 Release planning

    1. Outstanding items? 
      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.
  3. NonRdfSource properties - where should they live?

  4. F4 core, extras, and labs (mailing list thread)

    1. What are the "core" Fedora capabilities/projects?
    2. Which projects are always included in any given release?
    3. Should we decouple the version number schemes of optional projects from core releases?
      1. A. Soroka: Yes, there is no advantage to locking them.
    4. Should optional projects share the same "org.fcrepo" package namespace?
      1. A. Soroka: Only if the responsibility for them is the same as the responsibilities for core (that is, owned by the same people and accompanied by the same promises)
    5. What are the criteria for graduating from (1c)? - Practices from Islandora? Hydra?
    6. What is the policy for deprecating a project from (1a) or (1b)?
    7. What should the name of a third GitHub organization be, if such an organization is needed?
      1. fcrepo-extras
      2. fcrepo-ext
      3. fcrepo-flaky
      4. fcrepo-chum-bucket
  5. ...

  6. Current Priorities

    1. Performance
      • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    2. Single subject
      • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    3. fcr:metadata as a container
      • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    4. Point-like objects
      • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    5. Camel RDF serializer
      • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    6. Migration-utils
      • Wait for Mike
    7. Bugs
        • 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.

  7. 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.

  8. 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