PySAL agenda, 3 August 2018

1. Summer of Code
   • what to merge where?
     • splot/25
     • documentation
     • esda varnames (blocks other esda pulls) /23
   • final documentation & demos
   • plan to include plots as classmethods?
     • accepted
     • Already done with giddy
       • unittests and doctests are removed from giddy by WK
     • esda is next
   • dual testing
     • how to set up: ljwolf.org/post/testingmatrix
     • examples
       • spreg https://github.com/pysal/spreg/blob/master/.travis.yml
       • giddy https://github.com/pysal/giddy/blob/master/.travis.yml
2. Finishing the release candidate
   • API finalization for libpysal
     • to api.py or not api.py accepted, no api.py
     • del module? should we use? rejected
       • [@ljwolf] while I did merge this, I did not anticipate side effects like:
         1. breaking a large amount of code in pointpats
         2. segfault on ipython console because of jedi completion cache misses
     • should we keep using pysal in the docstrings? or be consistent for libpysal? RESOLVED: use libpysal always, and from libpysal import weights pattern.
   • developer contract
   • timeline/deadline for in/out decisions for pysal 2.0 (suitable for GDS'18?)
     • remaining in/out decisions
       • region & friends (spenc, skaterpy, spcluster?) rejected, too heavy deps
         • spanel from GeoDaCenter accepted, integrated into spreg
         • spaghettiaccepted
     • website
       • migrating.pysal.org not redirecting
         • https://github.com/pysal/pysal.site/issues/10
         • RESOLVED: ljw will make release of pysal 1.14.4post2 directing users to pysal.org/about
           • Some links in the release note for PySAL2.0rc1 are empty such as alpha shapes
3. future directions

• build tools
  • move to building from pypi?
  • build from git release tags && add git tags to contract
  • simplify/lift the grep-fu using fstrings/ 'string {} {variables}'.format()
  • dedicated discussion for September meeting.
• submodule procedure
  • https://github.com/pysal/submodule_template
  • RESOLVED: needs updates & attention
  • new module rules in submodule contract
  • testing
  • RESOLVED: version of python must be out for 6 months to test in metapackage

4. Documentation
   • subpackages
     • example online: https://giddy.readthedocs.io/en/v1.2.0/
     • RESOLVED: [@weikang9009] will post instructions on how to do this
   • metapackage uses a single best notebook from subpackage
     • [@knaaptime] table of contents for each submodule?
5. Code of conduct
   • RESOLVED: revise the scipy code of conduct for local contacts, but use its
6. Instructions on working with pysal.org to add your names to team
   https://github.com/pysal/pysal.github.io/issues/51

next meeting