Meetings 2017 10 16

Date/Time

Monday 16 October 2017 1200h UTC

Location

https://gitter.im/geopython/pycsw

Agenda (Draft)

Review of action items
pyfes status/update
Python 3 based packages
Docker integration
codecov integration
testing and diffs
release planning (2.2.0, 2.0.3)
roadmap (2.4.0)

Attendees

@kalxas - Angelos Tzotsos
@ricardogsilva - Ricardo Garcia Silva
@tomkralidis - Tom Kralidis

Notes

Review of action items
- codecov integration - DONE - @ricardogsilva has integrated codecov into our travis CI script.
  - Detailed coverage information is available at pycsw's codecov page.
  - Codecov also chimes in on all new PRs with information on how test coverage will be affected by the PR.
  - Coverage is currently at 56%. We are aiming to reach at least 80% before making this information more visible by adding a coverage badge to the README - DECISION D1.
  - @ricardogsilva is working on refactoring metadata parsing code and adding unit tests. A WIP PR will be created and @tomkralidis will review - ACTION A1
pyfes status/update - Nothing to report since last meeting. @ricardogsilva did not work on pyfes in the meanwhile. We'll revisit next meeting
Python3 based packages - @kalxas will take care of Python3 packaging during the upcoming 2.2.0 release preparation
docker integration - @ricardogsilva submitted PR #534 which adds some docker related stuff to pycsw. In addition to the Dockerfile, the PR also includes a docker compose/stack file in order to demo using pycsw with a postgis container. @kalxas will review the PR - ACTION A2. When merged to master, @ricardogsilva will add docker hub integration and write documentation on how to use the docker image; Later on, @ricardogsilva hopes to also add a stack file for mysql. This should ease development and testing against different repositories
codecov integration - Already covered above
testing and diffs - Since moving to pytest as testing framework, failed tests no longer default to showing diff outputs between actual and expected result. The change was made in favor of supporting XML canonicalization as a default comparison, since it is more robust than textual diffs for XML documents. However, since diffing is still a useful feature to have when working on the code, we've decided to bring back the diff output, as an optional flag that could be turned on during test runs. @ricardogsilva will implement this change - ACTION A3. This will boost @tomkralidis' current work in fixing some blocker issues for next release
release planning - next release will be 2.2.0
- blockers: #543, #544 - @tomkralidis is working on them and needs the testing diffs (@ricardogsilva) back in order to be more efficient
- it would also be good to update our dependencies, especially libxml2, which has recently released v2.9.5. @kalxas will investigate if the new version works OK
- after releasing 2.2.0, we'll still support v1.10 and v2.0 mainly due to there being some significant deployments using these older versions
roadmap for 2.4.0
- @tomkralidis will create a github milestone for version 2.4.0 - ACTION A4
- initial timeframe is to get 2.4.0 out by next summer (2018)
- some tasks that would be nice to have:
  - fully abstracted backend mechanism, including filter handling
  - new backends for ES/SOLR
  - improved test coverage, including functional tests for postgres and mysql
- @kalxas proposed trying to get some additional funding in order to commit more seriously to newer features and release timeline
extra
- @kalxas reported on the 2017 OSGeo AGM, which was held at FOSS4G Boston. Paolo Corti attended on behalf of the pycsw PSC and a two minute report was presented to OSGeo board
- According to @kalxas, pycsw has a 2000 USD budget still available for spending until the end of 2017. We need to decide how to best spend the available funds. Some options raised during the meeting:
  - sponsoring dev trips for participating in code sprints;
  - outreach materials;
  - updating pycsw's logo;
  - funding devs for implementation of specific features;
- We'll think about this and revisit on next meeting - ACTION A5

Decisions

D1: Lets bring code coverage up to 80% before adding a coverage badge to the README

Actions

A1: @ricardogsilva will open an issue and a WIP PR with the on-going work to refactor metadata parsing code
A2: @kalxas will review the docker PR - DONE - PR accepted and merged
A3: @ricardogsilva will open an issue and a PR for bringing back the diff outputs in the tests
A4: @tomkralidis will create 2.4.0 milestone on GitHub and will organize open issues accordingly - DONE - milestone created
A5: @all will think about ways to spend the remaining 2k on pycsw's budget for 2017