Create governance model and document it

[kpfleming]

This project is now independent, and as a result will need a documented governance process. This issue is the place to discuss that.

[jasongrout]

@SylvainCorlay @kaiayoung, is there currently a regular bqplot dev meeting videoconference?

[kaiayoung]

We could just make the existing one on Thursdays public?

[kaiayoung]

That had been the initial intention, but we also had previously discussed combining it with the ipywidgets' meetings.

[jasongrout]

We could just make the existing one on Thursdays public?

Let's ask if the other members of the transition team can make it. When is it?

[kaiayoung]

It was at 10a PST, but we can certainly move it around to sometime that works better for everyone!

[jasongrout]

PDT, right? (Or more conveniently, just PT?)

@bqplot/community-transition-leaders - does 10a PT on Thursdays work to have meetings to plan the transition?

[jasongrout]

(If it's not a good time for everyone, we'll send out a poll)

[ChakriCherukuri]

10am PT on Thursdays works for me

[jasongrout]

@bqplot/community-transition-leaders - from the only feedback above, let's try meeting in 10 minutes. If people can't make it, I'll send out a poll.

[jasongrout]

Notes from discussion in our meeting today:

Bqplot Governance discussion

• Model discussed:

  • Steering Committee with a small odd number of people (like 3 or 5)
  • Secretary on steering council responsible for decorum and process
  • "Semver" idea on which decisions can be taken by any committer, which require a SC member approval, which require a SC vote... Up to the judgement of the SC / committers to evaluate that.
    • Examples of what is breaking...
    • Visual change is breaking?
  • simpler than Matplotlib / Jupyter.
  • Who sets the strategic vision/roadmap?
  • has regular meetings

• Communication / transparency on SC decisions.

  • Anything that required a SC vote should typically require some communication.
  • set up team compass

• Institutional partners?

  • Employers of SC members
  • others?

• Sponsors?

  • Define better sponsors?

  • Should we make the listing of a sponsor a SC decision

    • Guidelines (money, since when)
    • Contributions by employees (how much, since when)

  • In the end, listing / removing a sponsor from the list discretionary to the SC.

• Composition of steering council?

  • Definite terms - 2 years, maybe with some initial members with 1-year terms
    • Makes it easier to commit for a specific time period
    • No term limits, so people can continue on the steering council
  • First SC nominated by the transition team, with advice from those currently involved
  • Every 2 years: reconduction / re evaluation of SC memberships / one or two people in a one year term?

• Distinguished contributors

  • Contributors who have done a lot for the project.
  • Former members of SC.

Bqplot Website / Logo / Visual Identity

Playful vs serious

Next meeting: before next Thursday

[SylvainCorlay]

Hello, another subject related to the move of bqplot to its own organization:

I think that it would make sense for the xplot project to move to the bqplot organization. xplot is a c++ backend to bqplot, which works in the C++ kernel.

Note: if we go with this,I was thinking of waiting for xplot to support the latest version of bqplot before moving with this. (currently, it targets bqplot@^0.4.3 (for the frontend package), which is bqplot 0.11.4).

[jasongrout]

@bqplot/community-transition-leaders - reminder of the bqplot meeting in about 1 hour 45 minutes.

[jasongrout]

Notes from meeting today:

Attendees: Sylvain, Jason, Itay, Kaia, Chakri

• bqplot 0.12.7 released

• bqplot 0.12.8 to be released in the next 24-28 hours to fix the dates issue.

• Move xplot to bqplot org

  • Vote: in favor 5 - 0 - 0.

• Make ipygg public and move to bqplot org

  • Vote: in favor 5 - 0 - 0.
  • All in favor of renaming to "bqscales".

• Steering council

  • 2 year terms
  • Having outside expectation of a term limit.
  • Regular meetings at least monthly

• Criteria for being on the steering council

  • Engagement:
    • participating in 3/4 of regular meetings
    • regular participation in discussions and offline votes with the SC mailing list

• Criteria for steering council candidates

  • To become eligible for being a Steering Council Member an individual must be a Project Contributor who has produced contributions that are substantial in quality and quantity, and sustained over at least one year.
  • Commitment to engage in the steering council over the term

• Electors

  • People who had a PR merged in the last year
  • Current board members
  • Participation in public meetings

• Distinguished Contributors: a recognition of past effort in the project

• Steering council decisions and responsibilities

  • Most day-to-day activities do not block on the steering council
  • Mediate significant conflict between community participants regarding the direction of the project
  • Code of conduct decisions
  • Releases
  • Approving or removing commit rights of people
  • Can delegate some of that power.

[jasongrout]

7 May 2020

Attendees: Sylvain, Jason, Kaia, Itay

Technical discussions

• bqplot 0.12.10 to be released anytime with all issues reported by Kaia.

• bqscales moved to bqplot organization.

  • open PRs to ipyvolume, ipyleaflet, ipydatagrid, bqplot to move to bqscales.
  • install bqplot labextension in ipydatagrid.
  • dependencies between JLab extensions

• 0.13
  -> boxed serialization supporting dates
  -> auto-layout
  -> bqscales
  -> minor schema changes (opacities PR)

Governance

• We will have a steering council of 3 or 5 people
• Transition team appoint the first steering council
• Steering council 2 year terms, monthly meetings at least

Ratification of discussion notes from last time about other governance items. We now move on to writing governance text for the next meeting (Sylvain volunteers to write text)

LOGO

• Serious <------------------||-------> Playful
• distiguishing factor: INTERACTIVITY
• COMPOSABILITY: lego for plotting: progressively building a plot
• Eye-Candy. TRANSITIONS and ANIMATIONS
• Fun / creativity. Bar chart with rainbow - was really nice looking to Itay.
• BOLD / vivid

[jasongrout]

14 May 2020

Attendees: Sylvain, Jason, Kaia, Chakri, Itay

Technical discussions

• bqplot: ragged arrays not supported in 0.12 so far. Pull request is in to support ragged arrays. Waiting on Maarten to review the PR before merging.

Governance

Governance drafted. Work-in-progress draft saved at https://github.com/bqplot/governance/blob/1bcef8a69a41024e732ac15bf4d043eb803bc9dc/governance.md

[jasongrout]

21 May 2020

Attendees: Sylvain, Chakri, itay, Kaia, Jason, Dhruv

Technical discussions

Theming: PR by Sylvain needs some iteration:

• make dark classic gridlines and axes dimmer

Many PRs merged in past week

Itay: regression: NAs in bars bqplot/bqplot#1151

Governance

Continued to iterate on the governance document, and will commit the draft to the governance repo.

[jasongrout]

We skipped meeting May 28.

During the 5 June 2020 meeting (Sylvain, Chakri, Itay, Kaia, Jason), we continued discussing the governance (18388a0) and started discussing the code of conduct.

[jasongrout]

Moving issue to the governance repo as a more appropriate place for these notes.

During the 11 Jun 2020 meeting, Kaia, Chakri, Sylvain, and I worked on the code of conduct enforcement manual.

[jasongrout]

During the 18 June 2020meeting, Kaia, Chakri, Sylvain, and Itay worked through the rest of the code of conduct enforcement.

@SylvainCorlay will be doing some work in the coming week to set up email lists, etc. The big item of business for next week is appointing a steering council and making plans for the NumFOCUS application.

[jasongrout]

It sounds like this can be closed, now that the transition team has completed its work and the new steering council is active.

Also, this repo's description in github still says "in-progress draft" - that can probably be changed to something more official.

[SylvainCorlay]

Good catch. Removing the "in-progress" and closing.