We need to better understand the workflow around asking for new features

[philiph-slac]

Are we to use issues? That doesn't seem to have been the case so far. I thought we did a pull request but I'm told that's not the usual style or my question is badly posed. I think TID uses JIRA for this not a git native procedure.

At the moment I want to add the idea of handling the saturation setting in LinearityPlotsParallelSlice - it should turn off when we're in AHL or AML and on otherwise. But the script doesn't entirely obviously know what gain configuration as it stands. This could be extracted from the data config or a command line specification (which would be a bit of a pain to do every time).

[nstelter-slac]

Hi,

I'm in favor of using issues.

The benefit is it keeps everything easy to find on this one GitHub page, its integrated into the repo (can nicely link to parts of the code base, etc), and can also link an issue to a code patch. Issues can be auto-closed when the related patch is merged in.

So I'd say feel free to open up more issues with anything that needs to be done/added.