Meeting Notes: May 6 2022

[MarsBarLee]

Meeting Notes: May 6, 2022

Follow-up on last week's to-dos

• Mars, Isabela to talk with Swast and review Best Practices for Accessible Real-Time Collaboration - Draft

Discussion topics and Resources

Exams over! Woo!

Last week's timesheet

• Need to edit and resubmit as PTO

  Extended internship by 3 weeks

• New end date: May 21 2022, 3 Saturdays from now

New Timeline

April 21: Previous meeting April 21-April 30: Exams May 6: This meeting May 8: Swast to release new draft May 9-13: Mentors, Tania to review. Swast to write a blog post May 13: All reviews submitted May 14-18: Swast to re-write, edit based on feedback May 18-20: Buffer, conversion from Notion to Markdown, write alt-text May 20: Final Submission May 21: End of internship

Slack channel to end May 21st, Saturday at

• 9AM (Isabela)
• 12:00 PM (Mars)
• 9:30PM (Swast)

Additional time would give more time

• Swast to write report (3-4 days)
• Mentors, Tania to review report
  • Tania will need some additional turn-around time, so account for that as well
• Swast to re-write report, based on feedback (3-4 days)
• Swast to write a blog post?
  • Can be written in the review period, while waiting for mentors and Tania to review
  • List of previous Quansight Internship 2021 blog posts
  • Lower stress, not reviewed like the report. Can be fun, free form
  • Some people may review blog post: Isabela, Mars, Ralf

Updates to the report

• Recommendation section

  • General? Or for specific audience eg Recommendations for designers vs Recommendations for developers
  • Write Recommendations list, see how many are specific vs general, go from there
  • Using audit as proof in Recommendation of what to do, not to do.
  • 'These recommendations are based on the audits and research conducted. Click on the link to see the source'
  • Formatting
  • Being very direct, brief summary, bullet point style
  • Linking vs not linking to audit.
  • Linking can be sufficient. Similar to a citation or WCAG recommendations.
  • Don't need to explain fully after each bullet point

• Represent data at tables

  • Example, template from previous meeting

• Alt-text for diagrams

  • Will get help writing alt-text for more complex images soon

• Previous discussion about removing, adding sections based on Mega Outline

  • https://github.com/isabela-pf/internship/blob/main/weekly-updates/report-outline-collaboration.md
  • Can link out
  • Can remove section- remove Recommendations? Or change
  • Does Next Steps seems feasible? Can be a bullet list
  • User Stories- diagrams, while cool, take time. Could make a bullet point version.
  • Remove 'Summary of Audit' section, since already discussed elsewhere

What are you planning to work on next?

Do you have any questions for someone on the team? Do you need any help from someone on the team?

Scheduling next meeting

• Will anyone be out of office in the next week? Any other scheduling conflicts?

Other

• Time for any learning/larger discussion (time permitting)
• Anything else?

[isabela-pf]

Questions

• For Recommendations section, should the audience be listed? And if so, to who?
  • We said there's no drawback to listing audience.
  • Start writing things and see if there's enough it would help to split the points by audience. If there's enough, they could be split.
• Formatting for recommendations. Any thoughts?
  • Short sentences usually are good.
  • Recommendations don't need to justify themselves, you can just say the thing and link it. So no need for complex intros.
• How can we pull the work together (ie. link the audit in the recommendations) to show why these recommendations are being made?
  • Have an opening line that says "these are based on this research; links per point refer to the specific work used to explain that point."
  • Mars says it could be treated it roughly like a citation.