Added charter (#5)

* Added charter

Author: AlexEne

README.md

@@ -1,2 +1,23 @@
-# wg
-Coordination repository of the Game Development Working Group 
+
+# Rust game development working group
+
+The game development working group's main purpose is to make Rust a first-class option for game developers.
+
+## What are we doing?
+
+At the very high level we have two main tasks:
+
+* To improve the experience of people using rust for game development. 
+We want game developers to have a representation in the Rust project.
+We are a bridge between them and the Rust dev team.
+
+* Share knowledge and make game engine development more accessible for people that are not engine developers. We know it can be an intimidating and scary field when you're just starting out.
+
+## How can you help
+
+Let us know where the gaps currently are. If there are problems in the tooling, documentation crate ecosystem, or even the language, we would like to know about it.
+
+If you have an idea, proposal or issue where you think the rust language or ecosystem needs to improve in order to make it a better option for game development open an issue on this repository. It will be discussed and triaged here.
+
+You can also look for issues tagged with `good first issue` or `help wanted` in this organization.
+

docs/charter.md

@@ -0,0 +1,24 @@
+# Rust game development working group
+
+The game development working group's main purpose is to make Rust a first-class option for game developers.
+
+## What are we doing?
+
+At the very high level we have two main tasks:
+
+* To improve the experience of people using rust for game development. 
+We want game developers to have a representation in the Rust project.
+We are a bridge between them and the Rust dev team.
+
+* Share knowledge and make game engine development more accessible for people that are not engine developers. We know it can be an intimidating and scary field when you're just starting out.
+
+## Goals
+
+* Gather a list of all the main gaps that separate us from the ideal state described in the introduction. Could be tooling gaps, a language feature gap, a library feature (eg. custom allocators). After this is gathered, we can start working on the biggest issues in that list. There are a few initial candidates but we encourage you to tell us where you are having issues so we can help. It may involve helping out with a low-level library.
+
+* Write guides to make game development in Rust more accessible for everyone.
+
+## What we are not doing
+
+* We will not build games or a game engine as this working group. However, we can create low-level tooling or libraries that are aimed at the healthy growth of the ecosystem and is not meant to be opinionated or favor an engine over another.
+* We will not be curators for "approved" game development libraries. Our purpose is to help such engines to exist, not to promote one library over another.