3: Move issues into a folder of their own

CONTRIBUTING.md

@@ -6,4 +6,8 @@
 
 ## What can I work on?
 
-Check out the [issues file](./Issues.md) to understand what work needs to be done, and to find the official issue tracker for the project
+Check out the [open issues file](./issues/open.md) to understand what work needs to be done.
+
+## Why is there an issue tracker in the codebase and in our SCM solution?
+
+Github does provide nice linking to issues for PRs and for the community to add issues to the project without having code access. The issues markdown files in the repo should be represented in Github as well, but are usually of higher priority and more immediately available to be worked on.

issues/closed.md

@@ -0,0 +1,5 @@
+# Open Issues
+
+Move [in-progress](./in-progress.md) issues to this file when completed
+
+- [Closed issues search](https://github.com/ExoKomodo/openwomb/issues?q=is%3Aissue+is%3Aclosed)

Issues.md → issues/in-progress.md

@@ -1,26 +1,14 @@
-# Issues
+# In-Progress Issues
 
-## Important Links
+Once completed, move the issue into [closed](./closed.md), and also close it within the [Official Issue Tracker](https://github.com/exokomodo/openwomb/issues)
 
-- [Official Issue Tracker](https://github.com/exokomodo/openwomb/issues)
+## Render textures/sprites
 
-### Why?
+### [Issue Link](https://github.com/ExoKomodo/openwomb/issues/3)
 
-Sick of not having issues co-local to the codebase, and this allows for more freeform planning and discussion, before dumping it into a PR or official issue. Also allows for platform-agnostic issue handling if we ever move off of Github.
+### Branch - [3_sprites](https://github.com/exokomodo/openwomb/tree/3_sprites)
 
-## Open
-
-To check all open issues on Github, [go here](https://github.com/ExoKomodo/openwomb/issues?q=is%3Aopen+is%3Aissue)
-
-## In-Progress
-
-### Render textures/sprites
-
-#### [Issue Link](https://github.com/ExoKomodo/openwomb/issues/3)
-
-#### Branch - [3_sprites](https://github.com/exokomodo/openwomb/tree/3_sprites)
-
-#### Overview
+### Overview
 
 There are 2 different ways to render images with SDL:
 
@@ -29,17 +17,13 @@ There are 2 different ways to render images with SDL:
 
 This issue is to only implement the OpenGL way, as it provides a general-purpose use case, since rendering to a quad is all that is "needed" for dealing with images and textures in graphics.
 
-#### Instructions
+### Instructions
 
 1. Read the [OpenGL tutorial for rendering textures to a quad](https://learnopengl.com/Getting-started/Textures). Now prepare for implementation.
 1. Will require some changes to the [Primitives.ShadedObject.From function](./src/Womb/Graphics/Primitives.fs)
 1. Will require some changes to the [Primitives.ShadedObject.UseMvpShader function](./src/Womb/Graphics/Primitives.fs)
 1. Will require some changes to the [example shaders in the Playground example](./examples/Playground/Resources/Shaders/)
 
-#### Acceptance Criteria
+### Acceptance Criteria
 
 Be able to render an image to a shaded quad. To demonstrate this, modify the [Playground example](./examples/Playground) to render the [hello_world.bmp](./examples/Playground/Resources/Textures/hello_world.bmp). For proper completeness, demonstrate how we can color the texture in the shader as well.
-
-## Closed
-
-To check all closed issues on Github, [go here](https://github.com/ExoKomodo/openwomb/issues?q=is%3Aissue+is%3Aclosed)

issues/open.md

@@ -0,0 +1,3 @@
+# Open Issues
+
+- [Open issues search](https://github.com/ExoKomodo/openwomb/issues?q=is%3Aissue+is%3Aopen+no%3Aassignee)