Using Qri Call - 09/09/2019 === Attendees: (add your name!) * @rico * @b5 * @dustmop * @chriswhong * @ramfox **AGENDA** * Intros * News & Updates * Peer Corner: Issues, Ideas & Bugs * Discussion: How can Qri Help? **News & Updates:** - Sprint Q Review: https://github.com/orgs/qri-io/projects/8 - Sprint R Review: https://github.com/orgs/qri-io/projects/9 - Demo: Qri Desktop (CW) - Call for Volunteers: Test Driving Qri Desktop & Feedback on tutorial **Peer Corner: Issues, Ideas, bugs?** * Astro Update: * Jonathan Update: **Discussion / How can Qri help?** * X * X * X **Resources** * Project Template (https://github.com/qri-io/community/blob/master/using_qri/dataset_project_template.md) * Docs (https://qri.io/docs) * Tutorials & Videos (https://qri.io/docs/tutorials/) * Qri Discord Channel (https://discord.gg/ApGYqb) for Q&A and linking up with other qri peers and devs (asynch) * Qri Dev Calls (bi-weekly): “like live RFCs” We’ll be publishing notes from the calls onto the Qri Community github repo (https://github.com/qri-io/community) We want outputs of these conversations to take the form of actionable github issues. Download Qri, test drive it, and share your impressions (nothing is too big nor too small)& file issues on our github **Raw Meeting Notes** ISSUES: