Remove retrospective notes

doc/Overview.md

@@ -34,8 +34,8 @@ overview/Links-and-Resources
 ## Documentation & Processes
 
 - [How to edit this documentation](Editing-the-Wiki)
-- [Notes from Retrospectives](processes/Retrospective-Notes): Notes from Sprint Retrospective meetings are recorded here.
 - [Decision Log](processes/Decision-Log): A place to write down decisions made.
 - [Documentation](processes/dev_processes/Project-Documentation): Documentation of the project and processes _(including why we have 3 wikis)_
 - [Data Protection](processes/admin/Data-Protection): Data Protection & GDPR as it applies to IBEX.
 - [Links & Resources](overview/Links-and-Resources): Useful external links & documentation.
+- Notes from Retrospectives are now located under `General > Group Meetings` in teams (including old retrospective notes)

doc/client/coding/PV-Switching.md

@@ -28,7 +28,7 @@ This extension point is setup in `uk.ac.stfc.isis.ibex.instrument/META-INF/MANIF
 This sets up the name of the extension point and the schema. 
 The schema is in `/uk.ac.stfc.isis.ibex.instrument/schema/uk.ac.stfc.isis.ibex.instrument.info.exsd`
 (click Schema on previous page).
-This defines the methods that should be fulfilled by the plugin that want to sign up to this extension.
+This defines the methods that a plugin must implement to use this extension point.
 
 In this case there are three methods:
 - `preSetInstrument` - this will be called before the instrument is switched. This is useful for closing resources 

doc/processes/meetings/Meeting-Roles-and-Rotas.md

@@ -23,10 +23,10 @@ It was decided that we would set up a rota for the various roles in IBEX meeting
 - Keep an eye on the end time of the meeting - give everyone a five minute warning
 - If the meeting is scheduled for more than an hour to indicate the halfway time to make sure we take a break
 
-### Note taker in Retrospective:
+### Note taker in Retrospective/Group Meeting:
 
 - Keep notes of the discussed points
-- Add them to the wiki with a link on the [main retrospective notes page](../Retrospective-Notes)
+- Add them to the meeting notes folder under `General > Group Meetings` in teams
 
 ### Note taker in Planning:
 

doc/processes/meetings/Sprint-Review-and-Retro.md

@@ -13,7 +13,7 @@
 
 1. Go through each person's slide and get them to demo and mention tickets they have done
 1. Discuss any issues and goodness in the code
-1. Review the [retrospective notes](../Retrospective-Notes) from the previous meeting, which will be found at the top of the page. The items to discuss will be located under 'Items from this retrospective:' and 'Other comments (Mad/Glad/Sad)'
+1. Review the notes from the previous meeting, which will be found at the top of the page. The items to discuss will be located under 'Items from this retrospective:' and 'Other comments (Mad/Glad/Sad)'
 
 1. Open up Teams > IBEX Developers > retrospective and discuss any items below the relevant post:
 

doc/processes/meetings/Technical-Debt-Stand-down.md

@@ -45,7 +45,6 @@ Try to make sure all tickets by the end of the day are in a good state.
 - `dbchecker` vs `dbunitchecker` vs `dbchanges`
 - Python 3 Compatibility
 - User manual updates e.g. https://github.com/ISISComputingGroup/IBEX/issues/2763 and https://github.com/ISISComputingGroup/IBEX/issues/3814
-- Update the specific device IOC pages see [here](../retrospective-notes/Retrospective-Notes-2020.05.28)
 - Tidy up code, remove unneeded parts
     - Discuss what to do with pv sets
 - Fix epics unit tests (https://github.com/ISISComputingGroup/IBEX/issues/5539)