Brendan O'Brien
Brendan O'Brien
We should pick a closed set of possible response codes that the qri JSON API will return, and map everything to those. Picking a set of codes requires us mapping...
we've run into this most recently in https://github.com/qri-io/qri/pull/1911, and have known about this issue for a while. We could clean up TODOs like this one: https://github.com/qri-io/qri/blob/d451f6f8a2b247958e80fdd14c79cfc0d4e6b1f2/base/save.go#L133-L135 Now that we have...
I'm proposing we add workflow create / remove operations to logbook, specifically to manage where datasets are scheduled. These `workflow` model operations would be _very_ sparse, consisting of: `identifier` (workflowID),...
We have plans for completion hooks that will work in qri cloud, but not locally. For example: we want a "send an email on successful update" hook, where qri.cloud will...
We have a number of places across where input parameters affect a listing result. While working on API refactoring (#1731) we've arrived at the following terms & fields for aggregation...
I'm concerned about the possibility of datasets resolving to different `InitIDs` if different codepaths use `CanonicalizeDatasetRef ` and/or `ResolveDatasetRef`. The easiest way to avoid any bugs that may arise here...
RFC0032 calls for modeling the `visibility` of a dataset based on logbook operations: > When a dataset has no visibility operations in it's log, it's visibility value is unknown. We...
I'd like to propose an extension interface aimed at improving the performance of time-to-not-found on a dataset alias that doesn't exist. Right now if I run `qri get some_user/random_gibberish_dataset_name`, all...
We had a user on discord ask if there was a roadmap anywhere for this project. Sadly, we don't have one yet. I'm a fan of a simple `ROADMAP.md` file...
#1882 adds context to the `Owner(ctx)` method. In an ideal world profile store implementations should be required to store the canonical "Owner" profile in memory, removing the need for any...