Table of Contents

Time/Place

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

Agenda + Notes

  1. Plan for 2.2.5
    1. Steve will produce & upload patches in the next couple weeks
    2. Dan will send out EOL message on 2.2.x once this is done
    3. No formal 2.2.5 release is planned.
  2. Recent committer/dev list threads:
    1. Moving to a DVCS (git @ github, hg @ bitbucket)
      1. General agreement to try a small-scale experiments focusing on tools and integration
      2. Focus on mediashelf fedora client, which is currently hosted on github.
        1. Will see if commits to the client can be tracked in Jira and trigger a build in bamboo
        2. Eddie will create jira issues related to installing plugins 
        3. FCREPO-810 will serve as the guinea pig for this experiment, as it implies work that should take place in the client code
      3. Will re-convene after initial experience with tooling is gathered, determine if it is with pursuing with community at large
    2. CModel Discovery
      1. General consensus that the current behaviour of CMA at runtime service invocation is not ideal
        1. Disseminations work unexpectedly
        2. There may be problems in the future with alternate CMA impls, or incremented content model
      2. Current validation api methods should be able catch situations where objects have a 'hasModel' relationship to something that is not a CModel.
        1. This is run on a per-object basis.  No tool for validating entire set of objects in a repository
      3. It may be possible to implement a "quick fix" where the CMA will disallow arbitrary objects from fulfilling the role of CModel upon service invocation
        1. Implementing this quick fix will essentially hard code certain assumptions, so may need to be fixed or re-written with CMA evolves. It would not be unique in that aspect. 
      4. Action items:
        1. Send an e-mail to users list which summarizes this conversation
        2. Propose the quick fix - see if there is general agreement that this would not be "worse than doing nothing"
        3. Create or verify a Jira ticket for implementing a commandline tool for running repository-wide object validation.

Items deferred to next meeting:

  1. FeSL status
    1. revisit overall intention of FeSL, eventual replacement for existing XACML AuthZ?
    2. currently "experimental" - what would it take to make it "production-ready"?
    3. current outstanding FeSL issues - just for reference, probably need a Special Topics meeting to go through the deta
  2. Review other newly-submitted issues
#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels