Yuvi

also, I definitely don't expect that `display` call to work in retrolab!

@ericvd-ucb yeah, that's a great point. I think maybe they ask students to manually save before submitting? @chrispyles @fperez do either of you know if you manually instruct users to...

Ah, ok! @chrispyles would you consider this kinda functionality allowing you to save the notebook from python a blocker for retrolab adoption?

@balajialg Thank you for making some changes! I'm still struggling to understand the 'what is the problem we are trying to solve here?' question I framed in https://github.com/berkeley-dsep-infra/datahub/pull/3384#discussion_r876753925. And I'm...

@balajialg @felder how about we automate running the archiver so it runs every week, and then for people with >100GB, we archive on 3 months of inactivity? That should help...

As for deletion, I'd say we can do something like 'your files will be deleted 18 months after they are archived' or something of that sorts, and enforce that consistently...

So if the goal is to save more expensive on-disk storage, I propose that we run the archiver continuously (I'll have to redesign it slightly but doable), and if your...

Thanks for the response, @balajialg. I agree these are all important problems to solve. I personally don't think we should be writing actual policy that treats users differently based on...

How would you determine who are GSIs / TAs? I think that is a fundamental problem that I want to keep out of scope of this policy to begin with,...

@balajialg ah, that is very nice! I do think the purpose of that group is a bit different, and probably more tuned to *manual* communications. I've specified the scope to...