Change Log
Last updated
Last updated
that specifies that the Operations Manual follows Semantic Versioning v.2.0.0 from now on
Note to that clarifies its adherence to Keep a Changelog v1.0.0
Latest hosted version is now available at
Use British English spelling 'programme' for the Competition Programme
Rename 'Core Team' to Competition Programme Committee
Rewrite the old 'Core Team' page to 'Competition Programme Team' and rewrite the majority of its contents to describe the new structure
Paragraph referencing code of conduct for volunteers
Paragraph explicitly restricting volunteers meeting or contact young people
Change Log page to document modifications between releases.
Shift dates of Core Team convening and disbanding one month earlier in the year (now convene in June and disband in May). This is to better align with the school year.
The whole Operations Manual has been completely rewritten and bears little resemblance to Version 2, therefore it would not be sensible to try and enumerate all of the changes. Version 3 effectively represents a completely new direction for the Operations Manual and should be viewed as a completely new work.
Instructions in the section to ensure that the Trustees have approved the release of a new Operations Manual, the decision to release is recorded, the Change Log is updated with the modifications made and the new version number and date of release is entered into the Change Log.
Clarification to that it is only young people who are participating in Student Robotics activities that volunteers must not meet outside of the supervised environment.
Examples of who 'those who participate in our community' are in section of Code of Conduct.
Instructions to in Code of Conduct detailing what information to include in a report, how the report is handled and how corner cases, such as the person being accused being one of the people who normally deals with reports, are dealt with.
Clarification to number 6 that only Trustees have direct access to volunteer dataset and that the Core Team will have to work with the Trustees to make use of it.
Clarification to number 5 to remove ambiguity around what the '£1000' is referring to.
Only store geographical region, instead of full postal address, in .
Soften 'expected' to 'will ideally' in Core Team section.
Make Core Team number 2 more all-encompassing.
Expect Core Team to run a Competition Program, rather than an explicit annual robotics competition, in number 4.
Pre-selection of 10 people to invite to the meeting to form the Core Team in the section.
Sentence explaining why more than eight people are invited to the meeting to form the Core Team in the section.
Explicit list of volunteer details recorded from number 6. (This information is already defined on the page).
Reference to not giving refunds to paid events from section of Code of Conduct. We don't run paid events, so it isn't relevant.
Make release procedure in section into a numbered list.
Make points under number 8 (be self-organising) into a numbered list.
Expand 'SR' into 'Student Robotics' in .
Reference Trustees' email address in a more readable manner in and .