Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Team update - Mar 02, 2022 #85

Closed
trallard opened this issue Mar 2, 2022 · 3 comments
Closed

Team update - Mar 02, 2022 #85

trallard opened this issue Mar 2, 2022 · 3 comments
Labels
type: internal-pm Items related to how we manage the project internally

Comments

@trallard
Copy link
Member

trallard commented Mar 2, 2022

This is a @Quansight-Labs/czi-a11y-grant team sync 馃帀馃帀馃帀! This is a way for the Team Members to provide status reports on what they've been up to this week and request help and attention for things they are working on. This issue will be closed at the end of the day.

Copy and paste the template below, and answer questions as you wish!

Response Template
**Thanks I'd like to give 馃檶**
- So-and-so helped me out a lot with XXX...
- Thanks for Jo's work on the XXX repo...

**Updates from last week :heavy_check_mark:**
- I worked towards deliverable: <link-to-deliverable>
- I had a meeting with ABC

**Challenges I faced and things I'd like assistance with 馃檹**
- I had a hard time figuring out ...
- Could somebody take a look at ...

**My availability for next week**
- I'll be off on XXX day...
- I've got several meetings this week...

馃攳 Needs Triage:

The Needs Triage issues require an initial assessment and labeling.

馃幆 Project boards

Please make sure the boards reflect the current status of the project.

Jupyter a11y grant project

@trallard trallard added type: internal-pm Items related to how we manage the project internally type: team-update labels Mar 2, 2022
@isabela-pf
Copy link
Collaborator

Thanks I'd like to give 馃檶

  • Just a big thanks to the forces that be that I can work on accessibility at all.

Updates from last week 鉁旓笍

  • I've been spending more time lining things up for the Jupyter accessibility workshop, so I don't have too much to show.
  • Checked in about SPEC stuff with collaborator. I think I know what next steps are needed now.

Challenges I faced and things I'd like assistance with 馃檹

  • I can't think of anything at the time of typing this.

My availability for next week

  • I'll be here all week, just workshop scrambling.

@trallard trallard closed this as completed Mar 3, 2022
@gabalafou
Copy link
Contributor

Thanks I'd like to give 馃檶

Updates from last week 鉁旓笍

  • Adding checkboxes to file browser (plus fixing accessibility issues where it makes sense - for example, mousedown versus mouseup)
  • Note this means I have tabled working on jupyter/accessibility until I get a PR up for the file browser work

Challenges I faced and things I'd like assistance with 馃檹

  • Nothing at the moment. Just need a little more patience.

My availability for next week

  • Available all next week

@isabela-pf
Copy link
Collaborator

Notes:

  • Notebook units are called cells, comic book units are called cells. Tony demos using flexbox to format notebook cells like comic book pages.
  • Yes, %% HTML at the top of the notebook will make the notebook rewrite itself based on the cell contents when it's run. This can be useful for testing styling ideas, prototyping and being able to send demos to people that they can run themselves.

Isabela:

  • Trying to get workshop going
  • Where could people help?
    • Need agenda for the Workshop/auditing event. When people run similar events, what did they like or not about auditing there?
    • Need a list of projects we'd like to audit (may just be "use what you have" and we have a repo directory or maybe we need to set up binders)
    • When Isabela makes slides, please give them review to make sure they make sense
    • Share the announcement blog (and register if you can make it!) when it goes up

Gabriel:

  • Hooray for progress on the https://github.com/jupyterlab/retrolab/issues/260 work!
  • Trying to not split time more, but focus on having this specific thing working.
  • Needing to work with an area with less work around it, so need to work on tests for this project as well
  • No blockers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: internal-pm Items related to how we manage the project internally
Projects
None yet
Development

No branches or pull requests

3 participants