Using Qri Call - 09/23/2019
===

Attendees: (add your name!)
* @rico
* @b5
* @chriswhong
* @ramfox
* YOU

**AGENDA**
* Intros
* News & Updates
* Peer Corner: Issues, Ideas & Bugs
* Discussion: How can Qri Help?

**News & Updates:**

- Sprint R Review: https://github.com/orgs/qri-io/projects/9
- Sprint S Review: https://github.com/orgs/qri-io/projects/10
- Discussion: Qri.cloud "Replicate" idea
- Beta testing Qri

**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:
* What is the evolution of the Qri registry?
* Decided to guide our technical work along use cases. If you're browsing datasets, move that to Qri Cloud (see all public datasets), If you're editing, use Qri Desktop.
* What is Qri's POV on how Qri Desktop interacts with Qri Cloud?

* Linking vs. Pinning Data
* Pinning: i'll keep a copy (IPFS)
* Linking: here's a version on my computer that works like a git repo (staging in git)
* Will browsing & editing combine in the future?
* Likely to follow compelling use cases. KN: Seems weird to have to do two tasks from two 'locations.'

* Rob: Re: Download button. If part of what makes Qri is its distributed nature, downloading is antithetical to that.

* Important to figure out how to present the notion of "rehosting"
* This also leads to the quesion of what the right way to run qri locally is doing. I assume that as a naive user I'm running qri connect, which is running an IPFS daemon, and while it's running people might be getting data from me
* Should it be running while I close qri? Is there a way to manage that, say, with a menu bar item?
* What's the right way to manage that?
* There are some different sorts of things you could be doing with Data on Qri that aren't exposed in the right way in UI. For example: I've got some data, can I see how I'm re-sharing it?
* I've been using the phrase "follow" to talk about tailing & pinning dataset versions
* This adds new complicated questions when interacting with the filesystem
* Because there's the whole d.web nature it, is there a situation that's important, like sharing or re-hosting a dataset that I'm not necessarily working on. Is there something in my database, but not something that's checked out on my local filesystem.

Chris W: I'm wondering if just getting the cloning is worth it, do we need to go full-tilt p2p to get value, or can we just use the clone functionality first.

Rob:
* I def don't think kill the download button outright
* Maybe you could use a modal instead of a PDF. PDF strikes me as kinda weird.
* I'm not interested in Qri for versioning. There are other ways I can do that. The primary concern is that it's distributed. We got interested in Qri purely because it's distributed. The thing we at EDGI
* It should be straightforward to have a system where what gets published publically can be replicated easily.
* We need a technical system that alleviates the requirements for data publishers to not have to either do a lot of work or not make a mistake
* If that were the only thing, I wouldn't be using Qri. The fact that it's distributed encourages people to participate
* I'm very interested in this notion of following or tracking
* I was trying to find some time to sit down & think through the notion of following
* If I'm looking at someone else's dataset, an important part of those things is for me to know if something has been updated and download it if I want
* should it be dropbox style or git style? Am I actively collaborating
* I'm not sure what qri cloud aims to be and what qri aims to be, but this connects to the problem of having qri being able to aggregate & connect data. Decentralized version of airtable.
* I start with the basic things that are in Qri, and without getting ahead of myself, I want the foundations of my distributed filemaker or airtable, with versioning and everything else :)

Kevin:
*