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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Team update - Jul 27, 2022 #149

Closed
trallard opened this issue Jul 27, 2022 · 5 comments
Closed

Team update - Jul 27, 2022 #149

trallard opened this issue Jul 27, 2022 · 5 comments
Labels
type: internal-pm Items related to how we manage the project internally type: team-update

Comments

@trallard
Copy link
Member

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 foo...

**Updates from last week :heavy_check_mark:**
- I worked towards deliverable: <link-to-deliverable>

**Challenges I faced and things I'd like assistance with 🙏**
- I had a hard time figuring out ...

**My availability for next week**
- I'll be off on foo day...

**Important items for discussion 💬**
- I have a question about goal <link-to-goal>
- Can @foo give a comment on issue #NN ?
- I opened #NN for discussion, please chime in
- I need to discuss foo

🔍 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 Jul 27, 2022
@steff456
Copy link

Thanks I'd like to give 🙌

  • Everyone for giving me queues in how to start!

Updates from last week ✔️

Challenges I faced and things I'd like assistance with 🙏

  • I had a hard time figuring out actual tasks to start working on 😅

My availability for next week

  • I'll be here!

Important items for discussion 💬

@isabela-pf
Copy link
Contributor

Thanks I'd like to give 🙌

  • @steff456's energy is lovely! I appreciate her drive to tackle a task.
  • @gabalafou has been working to coordinate us all, and I appreciate the effort!
  • I've heard positive feedback about @tonyfast's onboarding of our team members, so I want to give kudos there!

Updates from last week ✔️

  • Rendered notebook user testing - Round 1 #146. STScI User testing outreach begins. We have the go ahead, so we're getting people scheduled, writing recording consent forms, scheduling a test run, and generally getting things finalized for the first round of tests.
  • Curate JupyterLab themes #133. Theme status. Still nothing much to report. I just barely got to start experimenting with some of the non-color changes, but I can't decide if it's better to try and iterate via the inspector even though my CSS knowledge is pretty basic and I may be slow.
  • I've been really slow.

Challenges I faced and things I'd like assistance with 🙏

My availability for next week

  • I'll be out of office on July 29.

Important items for discussion 💬

  • I think I don't have anything now. I hope this meeting helps be iron out everyone's current work in relation to each other.

@gabalafou
Copy link
Contributor

gabalafou commented Jul 28, 2022

Thanks I'd like to give 🙌

  • Thanks to @isabela-pf for always showing up, asking good questions, leading calls in the Jupyter community. I'm not sure I could do it.
  • Thanks to @steff456 for being flexible in scheduling calls and bringing good energy :)

Updates from last week ✔️

  • Spent time pairing with Stephannie.
  • Spent time reviewing and understanding Isabela's work curating/scoping theme extension work.

Challenges I faced and things I'd like assistance with 🙏

  • I cannot adequately review/respond to Isabela's theme work on my own. I think this is a whole-team thing.

My availability for next week

  • Here

Important items for discussion 💬

  • Review my priorities with team. I have a lot more time to work on the grant. This is for the next few weeks:
    • testing: the testing tasks I want to finish up, unifying my/Tania's work with Tony's
    • theme extension: wherever I can be helpful
    • implementing accessibility fixes (with accompanying tests) directly in JupyterLab (or Lumino) - for example, removing tab traps
    • continue to help onboarding Stephannie and Kulsoom
    • for later: pydata-sphinx-theme pa11y work
  • Isabela's accessible theme curation/scoping
  • Tania, please repeat: what does a good github/workflow look like in your mind for jupyter-a11y-testing? compared against the workflow we have now:
name: a11y tests

on: [workflow_dispatch, push, pull_request]

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2 
        name: Fetch all history for all tags and branches
        with:
          fetch-depth: 0
      - name: Set up Python
        uses: actions/setup-python@v3
        with:
          python-version: 3.9
      - uses: conda-incubator/setup-miniconda@v2
        with:
          auto-activate-base: true
          activate-environment: ""
      - name: install development dependencies
        run: python -m pip install -e .
      - name: list jupyter build tasks
        run: python -m jupyter_accessibility -i jupyterlab -- list
          
      - name: establish the runtime systems for the builds
        run: python -m jupyter_accessibility -i jupyterlab -- env
      - name: setup the development content for building
        run: python -m jupyter_accessibility -i jupyterlab -- setup
      - name: setup the testing environments
        run: python -m jupyter_accessibility -i jupyterlab -- test_setup
      - name: run tests against the build
        run: python -m jupyter_accessibility -i jupyterlab -- test
      - name: upload testing results
        uses: actions/upload-artifact@v3
        with:
          name: a11y-test-results
          path: |
            jupyter-ally-build/jupyter-axe/test-results/*.html
            jupyter-ally-build/jupyter-axe/test-results/**/*.html
            jupyter-ally-build/jupyter-axe/test-results/*.json
            jupyter-ally-build/jupyter-axe/test-results/**/*.json

@isabela-pf
Copy link
Contributor

isabela-pf commented Jul 28, 2022

Notes! (I will be editing and adding as I go.)

  • Stephannie:
    • still looking for clarity around the tasks she can jump in on. Most of the confusion is around what the testing tasks includes.
    • Has made the decision to further split up the theming review work and start going.
    • There are scoping questions. ie. how does/does code mirror reflow as a part of this, or even is this even an extension-possible change? We need to discuss this for many points, but will postpone until Monday meeting in favor of updates.
    • Is this too big a scope still?
    • What's the timeline for this now?
  • Isabela
    • Theming work going slow, and it seems like we really need to agree on things because I keep having the same conversation on loop with different people.
    • STScI stuff is moving. Give the issues a look if you have time.
    • Excited we'll be talking theme stuff on Monday!
  • Gabriel
    • Jumping back in with more time, what are first priorities.
    • Of the list above. Also mention of onboarding as another first priority. Does documentation fit, or not yet?
    • Will work on these tasks in sequence, not all at once.
  • Tony
  • Kulsoom
    • Has been reading WCAG, but it's all abstract! It's hard to wrap your head around
    • Has been familiarizing herself with types of disabilities
    • ARIA, reviewing other accessibility primer things
    • Getting all-around familiarized! 🎉
  • Not person-dependent
    • There is expectation that the checklist will take a whole hour to talk about; there's a lot of questions people have.
    • Isabela needs to clarify the theming workflow. It sounds like people aren't understanding what the checklist does, how it has been used, specific tests tied to the checklist, and how the checklist moves to implementation.

@gabalafou
Copy link
Contributor

Possible discussions for Monday:

  • Stephannie is a little unclear about the priorities of the grant. Question: where do we want JupyterLab to be at the end of the grant?
  • What timeline are we currently working in?
  • Team review for:

Gabriel to review STSci related issues in GitHub for missing context.

@trallard trallard closed this as completed Aug 1, 2022
Repository owner moved this from Todo 📬 to Done 💪🏾 in Jupyter a11y CZI grant 🚀 Aug 1, 2022
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 type: team-update
Projects
Status: Done 💪🏾
Development

No branches or pull requests

4 participants