Add planning/automated-tasks.md

planning/automated-tasks.md

@@ -0,0 +1,9 @@
+# Automated tasks
+
+Gitea has [action runners](https://docs.gitea.com/usage/actions/overview#runners) which are essentially a drop in replacement for [Github Actions](https://github.com/features/actions).
+
+These actions are typically specified as a script that will use a base image, install all the tools needed for the task at hand and then execute that task. This breaks [DRY](https://en.wikipedia.org/wiki/Don%27t_repeat_yourself) but in execution space rather than code space.
+
+To address this [`gitea.efforting.tech`](https://gitea.efforting.tech/) will be using a system where you have image declarations and task declarations. Multiple tasks could be using the same image, and the image will be reused. This should make tasks execute faster, invoke less network traffic and be [greener](https://en.wikipedia.org/wiki/Green_computing).
+
+One thing not yet addressed is building for other platforms, like if you want to make sure your project can compile on windows or mac. But if we address this, this would probably be handled by additional VPS since it might be a bit too resource intensive to run multiple [QEMU](https://www.qemu.org/) sub systems for this purpose. But we will burn that bridge once we get to it.