Squashed commit of the following:
commit 70dfecb342
Author: Craig Oates <craig@craigoates.net>
Date: Mon May 24 19:24:16 2021 +0100
fix spelling.
commit 4a9ac06489
Author: Craig Oates <craig@craigoates.net>
Date: Mon May 24 19:22:32 2021 +0100
correct filtered_flicker_entries.csv link.
commit aefee00614
Author: Craig Oates <craig@craigoates.net>
Date: Mon May 24 19:19:31 2021 +0100
update photosensitive epiliespy assessment links.
commit e3e7461270
Author: Craig Oates <craig@craigoates.net>
Date: Fri May 21 19:15:17 2021 +0100
update photosensitive epilepsy assessment.
commit deb5549dc7
Author: Craig Oates <craig@craigoates.net>
Date: Mon May 17 19:10:01 2021 +0100
fix typo in epilespy assessment.
commit 20304e04dc
Author: Craig Oates <craig@craigoates.net>
Date: Mon May 17 19:05:22 2021 +0100
update photosensitive epiliespy risk assessment.
commit c856203e4f
Author: Craig Oates <craig@craigoates.net>
Date: Sun May 9 01:01:41 2021 +0100
add photosensitive epilepsy risk assement data and doc's.
commit ace5c1dc47
Author: Craig Oates <craig@craigoates.net>
Date: Sun Oct 25 03:32:13 2020 +0000
(#2) add initial content light-meter.md.
Most the content is taken from the ReadMe file from Light Meter's code
repository. Project overviews for Return to Ritherdon, Light Meter
and 'Artwork 1' are all here. The hardware requirements are, also,
included (part of issue #2) and preparation/maintenance instructions
for the software side of the project.
commit a1dfc95e86
Author: Craig Oates <craig@craigoates.net>
Date: Sat Oct 24 21:21:51 2020 +0100
add note to ReadMe about Eyes and Ears project.
This project is not essential and is not included in the diagrams
housed with the ReadMe file. This commit leaves a note next to the
link to the Eyes and Ears project highlighting this. The aim is to
reduce confusion about its inclusion.
commit 314a93755c
Author: Craig Oates <craig@craigoates.net>
Date: Sat Oct 24 21:17:15 2020 +0100
write ReadMe and add attachments.
This is a basic overview of the Return to Ritherdon project as a whole
and a breakdown of each project within this particular project
within Return to Ritherdon. (That makes no sense but it's the best I
can do right now.)
These are a collection of markdown files which will hold the
information for each project. The initial idea is to write and track
everything with markdown and git. When each document is ready to
'publish', they are exported as a .pdf file and stored in the
'Releases' section.
All work is done in the 'unstable' branch and moved to the 'stable'
branch when milestones are reached -- keeping all commit history. The
'master' branch is for creating 'snapshots' of the repository which
will not contain the full git history -- like 'stable' and 'unstable'
does. That's the plan at least.
Craig Oates