Skip to content

OpenGrid Weekly Meeting Notes 2016 05 13

PriyaDoIT edited this page May 16, 2016 · 9 revisions

Weekly meeting

Materials

Agenda

1. Review of existing work

i. Review existing OpenGrid pull requests

  • None.

ii. Review 'Ready' and 'In Progress' OpenGrid issues

See the Kanban board at https://waffle.io/Chicago/opengrid

  • [Service layer API] Geo-location Filtering is still in progress - opengrid-svc-layer #3
  • Rod: the layer is complete; wrapping up unit testing; testing of mock lat and long data has shown that everything is fine, but need to update the test data to include location (mongodb)
  • Mobile: Add hyperlinks to show links to additional pages #178
    • @tomschenkjr fixed the issue, @nfspeedypur to deploy on opengrid.io
    • UTURN to provide Tom with access to S3 account.
  • [JSON service layer] Querying arrays #7
    • @himaniravella to fix
  • Mobile>Advanced Search does not open on First try #184
    • @nfspeedypur to fix
  • Mobile>Android>Advanced Search Appears and then disappears #188
    • @nfspeedypur to fix
  • Geolocation error on Chrome: "Only secure origins are allowed" #183
    • @nfspeedypur to fix
  • Create documentation for adding datasets to Plenar.io #174
    • Adam D. to send the instructions to windygrid.cityofchicago.org
  • chicago.opengrid.io/opengrid help link formatting is off #152
    • CLOSE and @tomschenkjr to open a new issues.
  • Describe how to configure new data sets for the application #166
    • @rladines will work on this after the completion of #190
  • Images in /docs/media slow down clone #145
    • @rladines to push to prod
  • Update Advanced Search to support service-side geoSpatial filtering #190
    • @rladines
  • Update OpenGrid Service API documentation with new geo-spatial filtering feature #191
    • @rladines

2. New Issues

None.

3. Update on AWS AMI Deployment

  • UTURN will work on version 2 of the AMI the week of 5/16

4. Review of recent and upcoming Plenario work

@willengler was not at meeting.

  • Now will work on quick fixes instead of big ticket items. For example, "or" vs "and" column filters; most common values in table for Filtered searches. Timeline: Throughout the summer. After the cut group testing results we can follow up with Will on items.

  • ETL work has been de-prioritized, but most work has been completed.

5. CUTGroup Planning

  • @smarziano and @reve0716 will review CUTGroup test results on 5/19.

6. Other items

  • Tom to present OG at Amazon Public Sector Summit in DC.
  • Release 1.1.0 by the end of May

Weekly meeting notes

Roadmap proposals

Scope and Planning

Clone this wiki locally