Scope of Activity Feed

[glemaitre]

Right now, we have an activity feed in skore.

I find out that I'm not sure of should be the scope of the activity feed.

I wanted to have a "live" tracker and was naively thinking that it was part of this activity feed. It is actually not the case since this tracker does not need to store anything inside the database. It is more a sort of callback on our tools and could be consolidated inside a new "view".

@adrinjalali mentioned that he is seeing the activity feed as an historical view that track item persisted during the execution of a specific run (related to the scope of the current open instantiation of the project).

I'm wondering if @GaelVaroquaux could provide his view on this to collect as well his input.

[adrinjalali]

To add to the context, I think there are two different things we care about here:

• live monitoring of a "run": this can be monitoring the "backend cluster" or even what's happening on the user's machine. An htop of a sort and a live view of what's finished already. This is a kind of callback based thing which we can configure, or let the user configure and have good defaults for it.
• a view of the past "runs": once we move to a run-based model, here the user would see different runs, which they can expand and see what's stored as a part of that run. In essence, once can think of a "run" as a "document" in an "index" if we talk ElasticSearch/nosql terms. Query-ing from that becomes a solved problem with defined APIs as well.

Those two views are both valid, but it makes sense to separate them from one another.