owned this note   changed 2 years ago  
Published Linked with GitHub matplotlib/ProjectManagement/meeting_notes/2020/07_2020.md

July 2020

hackmd-github-sync-badge

tags: 2020 dev call

Call co-ordinates: Mondays @ 15:00 Eastern daylight time (UTC -04:00) https://zoom.us/j/384435716

Previous notes: 2020 Meeting Agenda Archive: matplotlib/ProjectManagement

Needs discussion at some point

04 August 2020

Moved to August notes…

27 July 2020

Agenda

Follow ups

New Business:

PRs/Issues:

  • set_ticks() updates the limits https://github.com/matplotlib/matplotlib/issues/17136
    • Should it be possible to suppress that with a new parameter set_ticks(... , update_limits=False)
      • pro: There might be cases, in which you don't want to update
      • con: This increases the API footprint and can be worked around by setting the limits after set_ticks()

Notes

Governance stuff

  • @tacaswell tries to advocate for a progressive migration to a committee lead governance

Named roles

  • Release Manager
    • a role for a single release stream, may be short or longer if LTS
  • API Consistency Leader
    • Ensuring we don't add extra spellings of the same thing
    • Path forward for deprecations
  • Reference Documentation Leader
  • Narrative Documentation Leader
  • Secretary
    • Make sure meetings happen, that agenda is filled, and followed
  • Community Manager

Empty line to fix formatting; fix later…

  • @tacaswell generally wants to determine a specific level of commitment to the project, instead of asking too much of volunteers
  • Term limits of a year allow a specific cut-off

Current status:

  • Tabling change from project leader to community (committee) led for now
  • No-one has objected to list of named roles
  • No-one has objected to description of named roles
  • There may be some tweaks to the description of the named roles
  • Leave for another week

3.3.1 release

  • A few issues/PRs still open
  • May want someone to look at #18037
  • Release should be possible in a day or two

PyData global sprint

  • PyData is merging all their conferences into one online conference, Nov 11-15
  • Organize a ~20-hour sprint with a range of time zones?
  • Ask some European people to cover that range

MacMini

  • We have the Apple Silicon Development Kit available on our MacStadium system
  • Email @tacaswell for access if needed
  • do any of our mac devs know how to get x-forwarding out of a mac mini?

Governance issue 12 - Twitter Persona

  • Merge as is, as a description of what's currently going on?

PR/Issues

set_ticks() updates the limits

  • should be consistent behaviour, or use a flag, not context-dependent (i.e., depending on whether a limit were set explicitly)
  • general consensus to leave it as is

Partial handling of rcParams['axes.unicode_minus'] by formatters

  • defer to next week

20 July 2020

Agenda

Follow ups

  • finalize names / responsibilties of named roles. (Next week)

Small issue label cleanup:

  • replace default changes with API changes
  • remove not a blocker
  • enhancement vs new feature usage?

PRs:

Notes

MEP 22, 27,

  • lots of work sitting there, we should resolve it

MEP22

  • discussion https://github.com/matplotlib/matplotlib/issues/8712
  • most of work is merged, but not the default toolbar path.
  • goal is to make the tools in the toolbar reusable in other contexts
  • some design decisions need to be cleaned up
    • some ability to override specific backend tools
    • class spec vs string spec overwritability.
  • clip board included
  • Move to get into Matplotlib 3.4.
  • almost all groundwork has probably been done…
  • rcParam switching so little cost to making default.
  • ACTION: make new default

MEP27

  • trying to do the same thing to the rest of backends / GUI / canvas parts
  • unifying the different backends to make it easier to extend them all in a uniform way.
  • Should be deferred to after 3.4 / wishlist

label clean up

  • remove 'default changes' -> API changes is good enough
  • remove "not a blocker"
  • replace "enhancement" with "new feature"
    • new feature makes new API
    • performance enhancement & maintenance clean up code

Colors and defaults

PRs

  • #16457 was merged…

13 July 2020

Agenda

Notes

Season of Docs:

  • due 31 July
  • Google gets reccs from us, google gets back w/ how many projects we get

CZI round 3: grant for second year

  • Elliott and Hannah helping w/ writing
  • Discussion of metrics and progress for CZI

3.3

  • gtk fix
  • nan-PR
  • docs
  • Revert SVG inheritance diagrams to PNG due to link bug

docker

  • made dev-ops progress at the sprints, have a dev-ready container, can build docs

named roles

https://github.com/matplotlib/governance/pull/7/files

  • release manager(s) - Elliott?
  • narrative documentation manager
  • reference documentation manager - Bruno?
  • community manager - Hannah (if and only if nobody else volunteers)
    • developer relations - discourse/twitter question traffic control/etc
    • social media/communication
  • api consistency leader - Tim?
  • secretary
  • Action: Tom will write description and send out call for volunteers

6 July 2020

Agenda

Notes

GSOD

  • Apps due Thursday
  • A few proposals

How to contribute:

  • dev mailing list for features?
  • should go to github?
  • process for new feature to be discussed
  • Yes, just guide people to github

New constrained_layout

  • some discussion
  • would be good to get in soon so it can work in master over the next few months.

Spelling :type:

  • Issue:
  • color does this
  • issue with plain-text version of docs versus sphinx-directive
  • glossary module?
    • would need to teach
    • include a hint?
  • variable docstring interpolations mappings?
  • concerns about injecting too much ceremony / sphinx details into the docstrings
  • consensus that "glossary" approach seems like it's a good approach initiallly
    • since the important part is consolidating the docs themselves, we can discuss more about exact "spelling" once we have this
  • Jody: should we instead make sure that the individual class that uses these individual "concepts" gets a glossary?
  • The "glossary" appears to have grown into the idea that we should actually have dedicated Class's for these individual concepts, so that we can centralize not just the documentation (without the need for Sphinx roles), but also have the class own the validator and rcparam serializer.
  • For GSOD, I'll propose primarily the actual centralization of the documentation as a first step, then the "glossary" style with some comments about alternate approaches.
.. _supported linestyles

   asdf 
   dsa

Scipy Update

Select a repo