Infrastructure

This is on your pile at the moment
Cloph, shall we hand this over to Guilhem eventually or do you keep taking care of this?

overall I'd say "sure" - but atm there are some local changes/stuff that's not in the repo. So once that's taken care of/it was updated to current version I won't hold on to it re software updates.

Other tasks (adding/removing users (or roles, re CMS mail) won't require shell-access/can be done by any silvertripe user with admin privileges in the webbackend.

Fixing issues is kinda broad, so assume needs shell-access, so that's also something that others can chime in to.

Cloph will work with Guilhem on the next update, to share knowledge
Eventually I'd like Guilhem to handle that and reach out to Cloph in case of questions/problems specific to the CMS

When's the next update (and thus some training with Guilhem) due?

silverstripe 4 is a LTS version with secfixes til mid 2021 (and active support til summer 2019, and end of 2019 silverstripe 6 will be released that is another LTS one).

So plan is to update/adjust to silverstripe 4 and keep it at that for next two years. No special training required I think as it is php and the usual update bits (some functionality deprecated/replaced by new conventions). It is a larger change this time due to added namespacing and similar, but there are helper scripts to assist in the conversion.
Also file handling has changed (is now versioned as well)
So bottom line is that this needs some testing, especially in combination with the subsites feature we have enabled on the site.

Sounds like a good plan to me! If some changes are due with this anyways, we could try to get people onboard for some training and helping with Silverstripe as well.

old instance is now free of any "active" stuff - the conference site has been moved to the main website (that is at 3.x which is supported til mid-2021, so plan is to convert that to fully static and shut down the olddesign silverstripe instance.

redesign work/experiments (and the extensions one) are on the current 4.5 - so a little undecided whether it is worth updating the current site to 4.x or just wait for the redesign and then do the switchover.

If our current version is maintained for another year, sounds sensible
to wait for the migration to 4.x until a new design is ready indeed