Add JLab accessibility meeting minutes

[isabela-pf]

As discussed in #16, I'd like to start storing meeting minutes for accessibility work throughout the Jupyter ecosystem here to create a centralized resource. This PR adds the minutes originally posted in jupyterlab/team-compass #98 as a starting point.

As these meetings are ongoing, I'm planning to submit future PRs in a group like this as well, but I'm open to what a good cadence might be. I've based the organization on other minutes repo's I've encountered, but I'm open to feedback if there's better practices for this I'm unaware of.

Thanks in advance for reviewing this PR!

[goanpeca]

If we are already using hackmd, and split each meeting into a separate file, we could automate this process entirely. :)

[isabela-pf]

@goanpeca if having a PR automatically opened every two weeks seems like a good amount of time, I can do that. We are currently using hackmd, just not separate files. That would be an easy enough change, though!

[jasongrout]

Thanks!

Two suggestions:

1. If the files have a .md extension, github will render them nicely as markdown
2. Having each week as a separate file means that it is hard to scan through or search minutes to find when a specific topic was talked about (it's the difference between scrolling quickly or finding in a single page, compared to opening up single files one by one and searching or scanning). I find myself often trying to refer to discussions that I know happened, but can't quite remember when they happened, so being able to easily scan through many days is something I found useful.

Finally, I think @isabela-pf should have maintainer access to this repo.

[willingc]

@jasongrout The hackmd workflow that @isabela-pf is something that we've used for nteract for several years. It's worked really well and Isabella has been a key person in the past year doing that.

Yes, we should definitely give @isabela-pf maintainer access.

[willingc]

@jasongrout I'm going to merge as is so the content is easier to consume in the short term. Going forward the team can always shuffle content later.

[jasongrout]

@jasongrout I'm going to merge as is so the content is easier to consume in the short term. Going forward the team can always shuffle content later.

+1. Sorry, I should have said they were suggestions, not blockers to merge. Thanks again @isabela-pf for all your organization work here!

[isabela-pf]

Thank you all for your support in making this work happen! Also thanks @jasongrout for catching that I somehow missed marking the files are markdown every single time; I'll update that with the next notes PR.