Versions Compared

Old Version 17

changes.mady.by.user A. Soroka

Saved on

compared with

New Version 18

changes.mady.by.user Andrew Woods

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. OSGi:

    No Format
    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. Jira
        serverDuraSpace JIRA
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-1532
      2. Jira
        serverDuraSpace JIRA
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-1630

  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

    Expand
    1. Performance
      • Jira
        serverDuraSpace JIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-1609
    2. Single subject
      • Jira
        serverDuraSpace JIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-1474
      • Jira
        serverDuraSpace JIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-1540
      • Jira
        serverDuraSpace JIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-1447
      • Jira
        serverDuraSpace JIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-1411
    3. fcr:metadata as a container
      • Jira
        serverDuraSpace JIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-1590
    4. Point-like objects
      • Jira
        serverDuraSpace JIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-1470
    5. Camel RDF serializer
      • Jira
        serverDuraSpace JIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-1519
    6. Migration-utils
      • Wait for Mike
    7. Bugs
      • Expand
        • Jira
          serverDuraSpace JIRA
          columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
          maximumIssues20
          jqlQueryfilter=13122
          serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5

  7. Tickets resolved this week:

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13111
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5

  8. Tickets created this week:

    Expand
    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13029
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5

Minutes

...

  1. OSGi:
    1. The decision is made on the changing Fedora package

...

    1. names. Fedora users/clients should not be impacted on it. However, software built around Fedora will be impacted.  

...

  1. 4.3.0 Release planning
    1. Release 4.3.0 next week. Nick is the release manager. Andrew and Nick will meet on next Friday and proceed

...

    1. 4.3.0 release. People who want to do future Fedora release can contact Andrew.

...

  2. NonRdfSource properties
    1. After discussion, decide to internally store the properties presented as triples in fcr:metadata on the NonRDFSource being described (as opposed to on the fcr:metadata-backing resource). 
    2. [IRC discussion]
      1. ajs6f: I claim that this won't prevent us from doing whatever we want with fcr:metadata later (making it a container, making it have a special lifecycle, filling it with peanut butter and Valvoline and baking it for several hours in a turtle shell, whatever we want).
      2. escowles: i'm fine with storing the properties on the nonRDFsource -- that makes sense since they are about that

...

      1. resource and i'm actually fine with retrieving fcr:metadata and getting triples about the nonRDFsource -- I think it was barmintor who was most concerned with the repository URL and the subject URI being the same
      2. awoods: I think there is good reason for concern about a mismatch between the repository URL (binary/fcr:metadata) and the subject URI (binary)... but there does not appear to be a better solution at the moment.
      3. escowles: i agree -- too many operations required by the binary and its description for them to peacefully coexist at the same rest api URL

...

  1. F4 core, extras, and labs
    1. F4 core capabilities: Repository CRUD, Transactions, Versioning, Authorization, and Fixity.

...

    1.  
    2. Included in any given release: Fedora reference impl. 
      1. Could be accompanied by a compatibility matrix for non-core modules along the lines of: http://docs.sonarqube.org/display/PLUG/Plugin+Version+Matrix

...

    2. Decouple module versioning? 
      1. yes. seems everyone agrees with it. 
    3. Continue discuss 4.d in next week meeting.