Thanks folks. Here are my notes from the meeting...
- Shapefile export; pdf export; & regionalization are now complete on
gmu.azavea.com - Mike & Micah to QA.
- After QA will be tagged and rolled in AMI
- Videos -- Abby to post videos to the "publicmapping" youtube channel, unless Robert has a better channel name
- Branding -- Home page branding appears to be agreeable to all
- Micah to draft license text for attribution to preserve branding
- Abby to review inner page branding
-- Use of logo for upper right corner? (Maybe not, if color schemes clash)
-- Link from upper right corner "DistrictBuilder" to main page of app
-- Add (minimal?) footer to internal pages
- Data tools
- David to circulate gdoc with (short) main use/cases overall design
- David to investigate (non-customizable) default sld generation so that subjects can be immediately usable one added
- I8n/L10n
- Kenny/Andrew to circulate gdoc spec addressing use questions/implementation questions
- use questions:
- how does admin provide additional set of text strings for a new locale
- how is default l10n's indicated in config?
- how does user select from available l10n's
- implementation questions
- where does other text exist that is currently in single language (e.g. config file descriptive text for scores, subjects; reporting engine labels (?); SLD labels ).
- besides printing text strings, what other presentation is affected by locale (e.g. number formatting; date formatting; sort order for alphanumeric sort keys) -- what needs to be refactored to be locale-aware?
- for each of these, what mechanism is used to add additional locale text/indicate user locale for presentation (e.g. add alternative descriptions with lang attribute to config.xml; send user locale as a param to reporting engine?)