|
| 1 | +# 2025-10-02 |
| 2 | + |
| 3 | +## Sprint 2025-10-02 Retrospective (2025-10-28) |
| 4 | + |
| 5 | +| Chair | Timekeeper | Note Taker | |
| 6 | +|-------|------------|------------| |
| 7 | +| JH | TW | KB | |
| 8 | + |
| 9 | +## Items from previous Retrospective |
| 10 | +### Review of First Line Support |
| 11 | + - FA talked to DI about `JIRA` it will do what we want, but cost is a query |
| 12 | + - The other solution available was not going to do what we need. |
| 13 | + |
| 14 | +### Developer Manual - protection of master branch |
| 15 | + - Trial in progress |
| 16 | + |
| 17 | +### Documentation on wiki instrument-information--hotfixes |
| 18 | + |
| 19 | +### Wiki instrument information pages are significantly out of date |
| 20 | + - Warning included |
| 21 | + |
| 22 | +### Weird permissions on stage-deleted |
| 23 | + - Issue bumped until CMS is available to discuss. |
| 24 | + |
| 25 | +### Galil-old branch |
| 26 | + - FA has created a ticket to create a repo check on galil-old. |
| 27 | + |
| 28 | +## Items from this retrospective: |
| 29 | +### Disk space |
| 30 | +- Many examples in thread, none of which are database truncation. |
| 31 | +- Caution for network going down is in place, but not enough space necessarily for the data coming in should the network go down. |
| 32 | +- Return again when CMS is in the room. |
| 33 | + |
| 34 | +### Support for non-`NDH`/`NDX` |
| 35 | +- Evidence that at one point NDCs were our responsibility, but that was not widely known about. |
| 36 | +- Existing remote viewing/control (`Daxtens`) also getting out of support. |
| 37 | +- See [Instrument Machine Standards](https://stfc365.sharepoint.com/:w:/r/sites/ISISExperimentControls/_layouts/15/Doc.aspx?sourcedoc=%7B6CC20F26-86D9-4F1B-8BEA-0E96B69E5A32%7D&file=Instrument%20Machine%20standards.doc&action=default&mobileredirect=true) for the existing evidence |
| 38 | +- *Action*: FA to make sure the expected policy for support and machine names is written down and agreed by CMS, the rest of the group and DI, and then it is communicated to all stakeholders. |
| 39 | + |
| 40 | +### 1926 Build server |
| 41 | +- Instruments are on LTS which is on a 10 year contract, ESU can be a purchased update. |
| 42 | +- Both are security updates not quality updates. |
| 43 | +- Discussion moved into the fact that keeping a test server on the same architecture was useful. |
| 44 | +- Return again when CMS relating to update deploys. |
| 45 | +- FA suggested getting an extra machine for the time being, which was agreed. |
| 46 | + |
| 47 | +### First Line |
| 48 | +- Being discussed in many places, no firm decision to be found here today. |
| 49 | + |
| 50 | +### Server Common |
| 51 | +- JH had a different thought, rename server_common to IBEX_helpers, two dependencies group members, for those which need EPICS call ins, and one which doesn't. |
| 52 | + |
| 53 | +### PR Templates |
| 54 | +- Some bits of the PR templates relate to repo specific reminders, but acceptance criteria are used sporadically, should the acceptance criteria be removed from the templates? |
| 55 | +- Consensus was `Yes` |
| 56 | + |
| 57 | +### Location of Emulators |
| 58 | +- JH raised the three different locations that the device emulators can exist in - within LEWiS, in the IOC support modules themselves, or in a separate directory again. |
| 59 | +- Suggestion is to move them to within LEWiS itself, to make it easier to highlight that success from the team, and present it at various conferences. |
| 60 | +- Only potential downside is that we don't always emulate the values that we don't interact with. |
| 61 | +- If not tied to the EPICS aspects, then they become more obviously useful to other control system users. |
| 62 | +- Some IOCs and similar will use multiple devices, and having the emulators in LEWiS would potentially make that clearer. |
| 63 | +- Tests are very individual, but emulators less so. |
| 64 | +- Being able to package the emulators with the framework provides a more modern python interface. |
| 65 | +- FA mentioned the possibility of packaging the emulators separate so that you don't have to install all the emulators as well. |
| 66 | +- Discussion highlighted that we will need to make sure that the versioning and so on is clear. |
| 67 | +- *Action*: JH to schedule a technical discussion for this. |
| 68 | + |
| 69 | +### Sysadmin docs location |
| 70 | +- Delay until CMS is in the room. |
| 71 | + |
| 72 | +### Work Experience Student |
| 73 | +- FA Happy for it to be done. |
| 74 | +- No one in the room wanted to take the supervisor job on. |
| 75 | +- *Action*: Check in with those that are not present. |
| 76 | + |
| 77 | +### Organisational Diagram |
| 78 | +- Not currently appropriate given the structure of the team. |
| 79 | + |
| 80 | +### Contact Cards |
| 81 | +- Make the email bigger, and update the information. |
| 82 | +- Provide a QR code that links to the user manual. |
| 83 | +- *Action*: KB to try and find the existing template. |
| 84 | +- *Action*: Someone update the cards and find a suitable landing page. |
| 85 | + |
| 86 | +## Mad/Sad/Glad |
| 87 | +- Got through cycle |
| 88 | +- Glad that SECI is now done with |
| 89 | +- Removal of the SECI related items should continue, e.g. SECI2IBEX, the re-organisation of the `mini-insts` etc. may be needed, needs a think and discuss for some aspects |
| 90 | +- Sad that LC is moving on to a new role |
0 commit comments