Date
Call-in Information
Attendees
Indicating note-taker
Agenda
- Reviewing / merging
- authorization update for self editors - updates?
- Back-porting to 1.11.1?
- authorization update for self editors - updates?
- Branch pruning policy announcement
- Sprint planning: i18n
- Triple store recommendation - moving forward
- Volunteer for the one-character change?
- Decoupled triplestore:
- Architectural diagrams - discuss at a future date
Notes
1.11.1 release
- Once https://github.com/vivo-project/Vitro/pull/106 has been merged, we should cherry-pick the commit into the 1.11-maint branch and release 1.11.1
Branching Policy
- Is there significance to the feature branches? - not really
- The VIVO 1.6 release was significant
- Would it make sense to propose removing non-maint branches before the 1.6 release?
- Dec 14, 2013
- That would mean pruning below row 34 of the "Vitro" tab in the branches spreadsheet
- We can then take an incremental approach to branch removal from 2014 to the present
- ACTION: Andrew to send out proposal to vivo-tech with the above suggestion
i18n
- Consolidate languages?
- Agreement that consolidation is helpful
- Can we standardize updates to labels with i18n properties?
- Focus
- language aware editing
- Not: label ordering
Triplestores
- Defining relevant tests
- Reads
- Pages: large number of associated triples (Australia)
- SPARQL Query API
- Writes
- SPARQL Update API
- Reindex
- Inference
- Reads
- Mike has test data generator?
- Let's finish documenting tests/procedures for "Triple store performance test procedures" by end of next week!
Actions
- Andrew to send out branch-pruning proposal to vivo-tech
Previous Actions
- Huda Khan to review:
- Brian Lowe to review:
- Ralph O'Flinn to review: