17 November 2022

Minutes of a Regular Meeting of the Board of Directors of NumFOCUS. All votes are reported in the form “(Y/N/A)” (in favor-Y‚ opposed-N‚ abstentions-A; e.g. “4-1-2” means “4 in favor, 1 opposed, and 2 abstentions”).

November 17, 2022

Attending: Logan Kilpatrick, Larry Gray, Sylvain Corlay, James Powell

Executive Director: Leah Silen

Not attending: Rosie Pongracz, Katrina Riehl, Stéfan van der Walt

Executive Director's Report:

No Quorum so we will not be voting

Discussion Items:

  1. Get a system online to capture service requests from the projects

    (ticket system) so we have stats on usage and turn around / feedback from projects on individual services

    a. Today, we have a freshdesk setup which we use for internal > tracking (not project related)

    i.  Events, emails, etc are all ticketed in freshdesk
    ii. help at umfocus.org is the
        > main project point of contact email right now
    -   Goal: Have this online by the end of Q1 of 2023
    -   Acknowledge this will add a bit of overhead for the NF staff
        > and projects. There will be a learning curve but this
        > should help better operationalize NF.
    -   The dashboard needs to include a pull-down with projects
        > names and an option to choose the type of request or need
  2. See what stats we can collect on payment turnaround times (what is

    the common bottleneck, how do we get to sub 2 days on all payments).

    a. Does Open Collective collect these stats? Can we work with them > to create a system to do so?

    b. We should set a goal once this is in place for how quickly we > turn around these payments. Otherwise, we have no idea where > we are in providing this core service to projects.

  3. Ensure all services / initiatives have clear goals going into 2023.

    If we don't have a goal and metrics, then we should evaluate whether we provide that service or not.

    a. This includes PyData (and lots of sub components of PyData), > small grants, staff happiness, project happiness (NPS), etc.

    b. Note: Since some initiatives might not have a clear path to > collect metrics right now, we may need to have our initial > goal be the setup of metric tracking.

    c. Once we have metrics in place around usage, time taken to > provide that service, etc, we should conduct a services review > and talk about what we provide and if we should continue doing > so (or how to make it leaner).