Based on a previous post, I have 8 students (3 engineering, 5 programmers) here working on our school planetarium Empty Epsilon Project.
Based on past experience (full missions taking many many hours to write), our strategic plan is to have tasks for individuals or small task groups to:
1) Document Empty Epsilon/LUA functions with explanations of execution and variables and include operational examples in the form of good script uses of this function.
2) Make new useful functions for the Utils script library.
The main goal is to make mission scripting more powerful (and faster) for everyone instead of spending time figuring things out via reverse engineering someone else's script.
Daid had mentioned that the Script_reference.html is created at compile time and that he might want to somehow include any documentation here instead of GitHub WIKI or some other reference guide...
I'm not sure how this would be accomplished but... we have scripts and functions collecting on our Google doc and stand ready to follow your instructions to make this knowledge available to everyone in the form you instruct us to.