Jussi Kukkonen

I would prefer no module path and just using the class name (this is what we do for other things -- see e.g. how we refer to `TargetFile` and not...

I'll add the backlog tag with the hope that it leads to figuring out some better solution than the current worst-of-all-options (quite wordy in docstring, yet no linked docs on...

the `test_1_...` style is typically used to achieve a specific order for the tests to run in (you might want that because the tests are borken so they require state...

Hi, welcome, sorry to have kept you waiting: I'll assign, but there's no need to wait for that in future: if you just leave a note saying you're looking at...

another related thing is `case_name` that is set in the decorator now: it's quite useful but leads to multiple workarounds with both pylint and mypy correctly complaining about it. I...

Pasting in my notes on 1915: * The key & signer handling could probably be better (why does the generator function need to construct the signers?) but there's no need...

Unassigning for now: too busy to handle this right now

Documenting the experiments on target adding and removal in repository-editor: https://github.com/vmware-labs/repository-editor-for-tuf/blob/main/tufrepo/librepo/repo.py#L131: both need a delegation search to be ergonomic (user should not need to know the exact bin role name...

Note that this might be an impossible request: > Figure out how we stay up-to-date? So a plain hatchling version bump (and preferably checking that the build result did not...

Leaving a note for later: Defining an action of our own in this same repo should allow using the same code across different jobs: Maybe it's not hard to define...