Meetings 2017 03 06

Jump to bottom Edit New page

Ricardo Garcia Silva edited this page Apr 6, 2017 · 2 revisions

Date/Time

Monday 06 March 2017 1400h UTC

Location

https://gitter.im/geopython/pycsw

Agenda (Draft)

Review of action items
pyfes status/update
repository plugins (ElasticSearch)
OAI/SRU support
Python 3 based packages
Google Summer of Code 2017 via OSGeo

2017 ideas

Attendees

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

Notes

1. Review of action items from last meeting

A: Experiment with the codecov service (@ricardogsilva) - No progress -> pushed to next meeting (Action A)
B: Prepare materials for guiding @tomkralidis' work on pyfes during OSGE code sprint week (@ricardogsilva) - DONE - See https://github.com/geopython/pyfes/wiki/Architecture-sketches
C: Prepare a summary on the status of packaging pycsw with python3 (@kalxas) There isn't currently any ongoing work towards packaging pycsw for python3. However @kalxas has experience packaging other projects, so the effort to package pycsw should not be too big, when the need to package it for python3 comes. OSGEO-Live is not on Python3 yet and will probably remain until upstream changes to Python3.
D: Open up a space on pycsw's wiki for GSOC discussion (@tomkralidis) - DONE - See https://github.com/geopython/pycsw/wiki/OSGeo-GSoC

1.1 Dropping support for Python2.6

Maintaining support for Python 2.6 is troublesome, as this version is no longer easily available on dev's machines
Furthermore, there doesn't seem to be active pycsw deployments on that are still on Python 2.6
As such, we'll push for dropping support for Python 2.6
@tomkralidis will take care of notifying pycsw-devel mailing-list and will also perform changes to the codebase (Action B)

2. pyfes status/update

@ricardogsilva has made some small progress. However, things are still in an initial stage. Support for Expression and some Operator types is shaping up. See https://github.com/geopython/pyfes
@ricardogsilva will try to pick up a faster pace of development, so the project should start to become useful in the short term. Focus will be on supporting filters that use the XML format first. CQL will come later
@ricardogsilva added CI and some unit tests too

3. repository plugins (ElasticSearch/Solr/QGIS/etc)

@tomkralidis is seeing significant interest in the implementation of additional pycsw backends, but at this point there isn't much progress to be reported. pyfes seems like it will be an enabler for this work

4. OAI/SRU support

No update from the situation reported previously
See issue#494 for some more context on the work to be done

5. Python3 based packages

Packaging pycsw for Python3 has not started yet
@tomkralidis will file a ticket (Action C) and assign to @kalxas, who will work on it eventually. No timeline has been discussed yet.

6. Google Summer of Code 2017 via OSGEO

We are waiting to see if there are some candidates to work on pycsw related projects during GSOC
If pycsw project(s) get selected we'll need mentors and co-mentors
@ricardogsilva volunteered to co-mentor

Decisions

Lets drop Python 2.6 support, as long as there are no objections from pycsw-devel mailing list

Actions

A: @ricardogsilva will experiment with codecov and we'll discuss it next meeting
B: @tomkralidis will notify pycsw-devel and will proceed to remove Python2.6 support
C: @tomkralidis will open a ticket and assign to @kalxas for packaging pycsw with python3

Next meeting

Next meeting should happen in about 4 weeks - probably on 10th March

https://pycsw.org