Including such a file in Moore could be useful for assigning issues and MRs to relevant people, and to find out who should be contacted for questions on certain files. This might be particularly useful once many HLT lines are added.
Designs
Child items
0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items
0
Link issues together to show that they're related or that one is blocking others.
Learn more.
Agree, but if we are anyway cleaning up Rec and Phys and merging them, that seems an excellent moment to use this kind of file to really put together the code and assigned responsibilities. If I had known about this concept I might well have pushed for this in January already! Anyway can certainly start with Moore and then move onwards from there.
yeah that can be useful. We can't require approval from "owners" as this is a premium feature, but at least they come up like so in the merge request (rmatev/test-public!4 (closed)):
Agreed, but at least we can explain our understanding of the file in comments. Then we just need to decide what that understanding is. Perhaps something like
Files are assigned "owners" based on people's personal and professional investments. They do not "own" the code, as everyone is free to modify everything and to approve all changes of others, but are more likely to be interested in changes to those files.
As examples, an RTA work package coordinator may be interested in all HLT2 selections, a physics analysis working group convenor may be interested in selections relevant to their group, and the original author may be interested in a specific line in a particular file. All of these people would be marked here as "owners".