(Accesibility council) Vote to fold accessibility meeting into frontends weekly meeting

[ohrely]

Discussed in #148 and jupyterlab/frontends-team-compass#252. Frontends council vote at jupyterlab/frontends-team-compass#254.

Proposal

Merge accessibility meetings into frontends meetings:

• Rebrand the existing weekly Wednesday Jupyter Frontends meeting to a Jupyter Frontends and Accessibility meeting.
• Remove the existing alternating Thursdays accessibility meeting from the Jupyter Community Calendar.
• Advertise that accessibility topics are welcome in all of the combined meetings but members of the accessibility subproject will make a particular effort to attend the first meeting of each calendar month.

Per the Jupyter decision-making guide, "After the proposal is seconded by another member of the council, members have seven days to vote."

Votes

• @trallard
  • Yes
  • No
  • Abstain
• @ajbozarth
  • Yes
  • No
  • Abstain
• @fcollonval
  • Yes
  • No
  • Abstain
• @marthacryan
  • Yes
  • No
  • Abstain
• @afshin
  • Yes
  • No
  • Abstain
• @ohrely
  • Yes
  • No
  • Abstain
• @gabalafou
  • Yes
  • No
  • Abstain
• @krassowski
  • Yes
  • No
  • Abstain
• @isabela-pf
  • Yes
  • No
  • Abstain

[ohrely]

I don't have permission to add a "vote" label to this, would appreciate if someone could!

[fcollonval]

I can't vote due to missing rights. But my vote is for yes

[afshin]

I think you should have permission now, @fcollonval!

[krassowski]

I do not have a permission to vote. I think I would vote "yes" with a caveat that having a quarterly or half a year dedicated accessibility-only meeting could be a good addition to this proposal.

[trallard]

Agree, been too busy to sit down and write thoughts.
But I would like to continue to find opportunities or create space to discuss accessibility within Jupyter as a whole (vs solely in the context of Jupyter frontend).

[ohrely]

I do not have a permission to vote.

Voted "yes" for you, hope that's okay @krassowski. I think @trallard and @afshin have the power to add you to the accessibility team for future votes.

But I would like to continue to find opportunities or create space to discuss accessibility within Jupyter as a whole (vs solely in the context of Jupyter frontend).

My understanding/expectation while pushing for this meeting merge has been that all Jupyter accessibility topics, frontends-related or not, will be fair game at the Wednesday calls (esp. during the 1st meeting of the month). If the amount of meeting time dedicated to frontends-unrelated accessibility topics becomes a burden, we can reassess the wisdom of merging the two meetings.

I think I would vote "yes" with a caveat that having a quarterly or half a year dedicated accessibility-only meeting could be a good addition to this proposal.

I like the idea of an occasional "Jupyter Accessibility Summit" to discuss topics that don't tend to come up in weekly calls (big direction decisions, council membership maintenance, etc.)

[trallard]

I am +1 on having a summit/separate call whatever it is.

I am very unlikely to make it to the frontends call as I have hard scheduling conflicts at the time/day these take place so having other alternatives to discuss meta accessibility topics would be good for me and potentially others.

[ohrely]

Closing this issue to mark vote completion as we are at 100% voted. Final tally: 8 yes, 1 no.