PySAL Agenda - July 5, 2019

Chair: Serge

Agenda

1. meta 2.1

   • release planning
   • overview of meta-build tooling

2. subpackage version vs. meta version

   • develop a method to catch changes in the api.rst files from each subpackage between versions when doing a new meta release
   • causing doc rendering issues
   • example from spaghetti
   • release draft release example
   • two steps after the github release of a subpackage
     • update the tag pointing to the github release
     • udpate the metapackage api page

3. Infrastructure specialists (pushed from last month)

   • We spend way too much time rediscovering what others have learned
   • Should we appoint a lead specialists for infrastructure? For example, on things like:
     • travis
     • readthedocs
     • sphinx
     • pypi
     • conda
     • other?
   • In other words, one person is the go-to for guidance on each area.
   • Currently, we have informal structure. Current members are already the defacto expert. We need to decide whether to formalize these roles.
   • Vote on formal decision
   • Communal document is the decision
     • link to document

4. NumFocus

   • PySAL now a NumFocus Affiliated project!
     • Funding possibilities
   • Process
     • Steering Council
     • Proposal
       • include "PySAL Enhancement Proposals" in PySAL Wiki
       • submission month before deadline April, July, November

5. Milestones

   • to "connect" releases to bugs that we'd like to be addressed

     

6. esda / pip failures

   • .rst vs .md

7. decision for region

   • end-of-life release / announcement?
   • need the maxp bug formally filed

Previous Meeting

Next Meeting