Rough notes from Developer Meeting sessions on Wednesday, 2012-02-08
| Table of Contents |
|---|
Implementations, methods, tools (13:15-14:30)
...
- Multiple language
- Guide user behavior
Automatic start/end date generation based on more simple input; e.g. 20th century, generate earliest and last dates
Quarter, half, middle, end, decade, period, century, based on requests from staff at the museum, more or less copied from existing system
Boundary checking for dates
Requires:
- Extensions
- Date library for date arithmetic
- Use case for replacing widget or customizing widget
Integrations we're waiting to do
AD
DAM
Exhibition management
Public web browsing
Export to Regin
Condition database
Literature references - downloads of references to items in the collection from the National Library, pulling them in automatically
ConservationSpace
...
gitFlow, abstraction with making merging and branches a little nicer
git start branch
git finish branch
workflow shortcuts, makes what is hard to remember easier https://github.com/nvie/gitflow
Introduction: http://jeffkreeftmeijer.com/2010/why-arent-you-using-git-flow/
Strategies for extensions (15:25-17:00)
The following notes for this session are sparse - randomly selective
What support GitHub provides for community contributions
tagging or naming conventions
Nate: Would likely coalesce around a "good enough" schema, use it thereafter
(Jesse mentioned that phrase)
Patrick:
Business-to-business transfer of loans
Possibility of pluggable export tools, like reports and batch processes
Templates might consist only of language translations of message bundles
Templates for ETL tools - at least as an example; even a bunch of Perl scripts
Local development in the UI layer with record.html
Missing from the mini-build
Ubuntu
has done a good job of distinguishing between:
- this is core
- this is community
- this is the wild west
Django
everything's in the contrib directory
when you check it out, you get all that
A big question / assumption is that you can get your data back out, not just a database dump
Hosting providers can potentially do a better job of backing up, resting restores, etc.
Generating from app layer config might help simplify community contributions