Table of Contents
|
Time/Place
This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join...here's the info:
- Time: 11 am Eastern Daylight Time US (GMT-4)
- Voice
- Via Skype+: Dial from anywhere: \+9900827047086940 (callto://+9900827047086940)
- Via Phone+: US Number: +1 (201) 793-9022, Room #7086940
- IRC:
Agenda + Notes
- Plan for 2.2.5
- Steve will produce & upload patches in the next couple weeks
- Dan will send out EOL message on 2.2.x once this is done
- No formal 2.2.5 release is planned.
- Recent committer/dev list threads:
- Moving to a DVCS (git @ github, hg @ bitbucket)
- General agreement to try a small-scale experiments focusing on tools and integration
- Focus on mediashelf fedora client, which is currently hosted on github.
- Will see if commits to the client can be tracked in Jira and trigger a build in bamboo
- Eddie will create jira issues related to installing plugins
- FCREPO-810 will serve as the guinea pig for this experiment, as it implies work that should take place in the client code
- Will re-convene after initial experience with tooling is gathered, determine if it is with pursuing with community at large
- CModel Discovery
- General consensus that the current behaviour of CMA at runtime service invocation is not ideal
- Disseminations work unexpectedly
- There may be problems in the future with alternate CMA impls, or incremented content model
- Current validation api methods should be able catch situations where objects have a 'hasModel' relationship to something that is not a CModel.
- This is run on a per-object basis. No tool for validating entire set of objects in a repository
- 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
- 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.
- Action items:
- Send an e-mail to users list which summarizes this conversation
- Propose the quick fix - see if there is general agreement that this would not be "worse than doing nothing"
- Create or verify a Jira ticket for implementing a commandline tool for running repository-wide object validation.
Items deferred to next meeting:
- FeSL status
- revisit overall intention of FeSL, eventual replacement for existing XACML AuthZ?
- currently "experimental" - what would it take to make it "production-ready"?
- current outstanding FeSL issues - just for reference, probably need a Special Topics meeting to go through the deta
- Review other newly-submitted issues
|
#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))