PySAL Agenda, 7 September, 2018

Pre-meeting agenda items

1. tooling/build for releases
   • MOVED: talk about this next month.
2. CoC adaptation
   • MOVED: adopt the SciPy code of conduct. Vote to adopt deferred to next month.
3. governance structure
   • standard development meetings should be held once a month, and are open to the public.
   • Specific requests for action (R4A) should be proposed, seconded, and voted on in standard development meetings. The exact text of the R4A should be written down for future evaluation. Specific topics that must be proposed as an R4A include:
     • API changes
       • in libpysal
       • any subpackage upon which more than three down-stream project packages depend
       • However, maintainers should not be expected to maintain changes with which they do not consent.
     • changes to the submodule contract
     • changes to maintainership or development group membership.
       • New members to the development group may be added by simple majority vote during a standard development meeting.
       • If a pressing need arises, new members to the development organization can be provisionally added at any time, but must be approved by simple majority vote at the next standard development meeting.
   • Threads in the dev group should serve the function of mailing list-style discussions.
     • New releases of subpackages MUST post their new releases to the thread in the dev group on github and link to their changelogs
     • All R4As should be recorded in the development group on github.

Items added during meeting

1. New releases required for packages?
   • splot: tests are green, but notebooks need review.
     • legendgram integration slated for future?
     • desire to make a roadmap for the package, outlining future directions.
   • spaghetti: no action, @jGaboardi absent
   • region: talked about integrating @jGaboardi's new work, but unsure.

Items deferred or added for next meeting:

1. recorded on the next meeting page

previous meeting
next meeting