Time | Item | Presenter | Notes |
|---|
5 mins | Intro | | |
30 mins | Work Plan | Trevor Thornton | https://docs.google.com/document/d/1f0PocP9XKjhbuh2s8B2CMTlmM70Vv0msPw6xl9xKRr4/edit?usp=sharing Mark’s priority is to ensure that the Github pages site generated from the tech-docs repo can serve as the single source of documentation so that building the documentation can be fully decoupled from the application build process. This has been added to the Work Plan doc Trevor suggests that the other work of the sub team should focus on maintaining the current documentation repo, identifying areas of potential improvement (organization, documentation gaps, etc.), and encouraging members of the community to contribute to the documentation.
|
15 mins | API Docs Working Group | Dave Mayo (Unlicensed)
Trevor Thornton | https://docs.google.com/spreadsheets/d/1VTt6CJNIRkOkXZhtbHMedUQay16QiE1QhI2rWEPCXB8/edit?usp=sharing Mark agreed to sit in on the API Docs meetings as he is able, and suggested that Lora might do the same as she’s been working closely with the API. The idea is for one or both of them to be available as a resource for anyone with technical questions, but there’s no expectation that they should spend time on the implementation. Rachel will ask Don Mennerich at NYU if he’d like to work on the API documentation project. That would be a good thing to have happen.
|
10 mins | Other topics (if there are any) | | Why Trevor’s Zoom crashes so much |
