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:
- Join the #fcrepo chat room via Freenode Web IRC (enter a unique nick)
- Or point your IRC client to #fcrepo on irc.freenode.net
Attendees
- A. Soroka
- David Wilcox
- James R. Griffin III
- Aaron Birkland
- Unknown User (daniel-dgi)
- Andrew Woods
- Yinlin Chen
- Jared Whiklo
- Doron Shalvi
- Kevin S. Clarke
- Nick Ruest
Agenda
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.
4.3.0 Release planning
- Outstanding items?
- Outstanding items?
NonRdfSource properties - where should they live?
F4 core, extras, and labs (mailing list thread)
- What are the "core" Fedora capabilities/projects?
- Which projects are always included in any given release?
- Should we decouple the version number schemes of optional projects from core releases?
- A. Soroka: Yes, there is no advantage to locking them.
- Should optional projects share the same "org.fcrepo" package namespace?
- 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)
- What are the criteria for graduating from (1c)? - Practices from Islandora? Hydra?
- What is the policy for deprecating a project from (1a) or (1b)?
- What should the name of a third GitHub organization be, if such an organization is needed?
- fcrepo-extras
- fcrepo-ext
- fcrepo-flaky
- fcrepo-chum-bucket
...
Current Priorities
Tickets resolved this week:
Tickets created this week:
Minutes
1. The decision is made on the changing Fedora package name. Fedora users/clients should not be impacted on it. However, software built around Fedora will be impacted.
2. Release 4.3.0 next week. Nick is the release manager. Andrew and Nick will meet on next Friday and proceed 4.3.0 release. Review current sprint JIRA tickets and decided which tickets to be included in the 4.3.0 release. People who want to do future Fedora release can contact Andrew.
3. After discussion, decide to store the properties presented as triples in fcr:metadata on the NonRDFSource being described (as opposed to on the fcr:metadata-backing resource).
[IRC discussion]
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.
escowles: i'm fine with storing the properties on the nonRDFsource -- that makes sense since they are about that resource 12:29
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
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.
escowles: i agree -- too many operations required by the binary and its description for them to peacefully coexist at the same rest api URL
4. a. Repository CRUD: LDP, Transactions, Versioning, Authorization, and Fixity. https://wiki.duraspace.org/display/FF/F4+GitHub+Organizations
b. ref impl. Could have something like http://docs.sonarqube.org/display/PLUG/Plugin+Version+Matrix
c. yes. seems everyone agrees with it.
Continue discuss 4.d in next week meeting.
