From a54c3f975aa6ee8661f45b4cfb46a2a427d20e87 Mon Sep 17 00:00:00 2001 From: FlightControl Date: Sun, 22 Jan 2017 14:55:28 +0100 Subject: [PATCH] doc --- docs/README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/README.md b/docs/README.md index 603fde6f5..79fd6c1d5 100644 --- a/docs/README.md +++ b/docs/README.md @@ -22,8 +22,10 @@ local SpawnGroup = SpawnObject:Spawn() -- Here we use the :Spawn() method of the ## 1.1) MOOSE framework goal The goal of MOOSE is to allow mission designers to enhance their scripting with mission orchestration objects, which can be instantiated from defined classes within the framework. This will allow to write mission scripts with minimal code embedded. Of course, the richness of the framework will determine the richness of the misson scenarios. -The MOOSE is a service that is produced while being consumed ... , it will evolve further as more classes are developed for the framework, and as more users are using it. -MOOSE is meant to be a one-man show, it is meant to evolve within a growing community around the framework. +The MOOSE is a service that is produced while being consumed ... , it will evolve further as more classes are developed for the framework, and as more users are using it. + +MOOSE is NOT meant to be a one-man show, it is meant to evolve within a growing community around the framework. + Within the community, key users will start supporting, documenting, explaining and even creating new classes for the framework. It is the ambition to grow this framework as a de-facto standard for mission designers to use.