Gooey should be able to respond to a privileged user and create what's needed for a new module

[Cervator]

Would exercise a minimal implementation of several integrations and functionality. This could probably be used roughly the same on IRC as well as Slack.

Gooey: Create module x for y

• x = name of the module, also used for Jenkins job name, GitHub team name, etc
• y = name of user (ideally same on IRC and Slack, or otherwise only added on one side)

Available to moderators/admins. Next stage after this would include granting the user role rights to run commands related to that module specifically - #13

• Create a new module repo x under http://github.com/Terasology
• Create a new module team x under http://github.com/Terasology and add y to it
• Create a new Jenkins job (or otherwise prepare Jenkins) to build the new module

Expected result: module repo, team, and job created. Module now exists but does not yet have release management enabled (only snapshot builds) . Likely not yet available via meta server, launcher, or listed in docs. No IRC/Slack roles yet.

Outstanding: Should a newly created repo be filled with the template files so the user can simply fetch it or should it start blank assuming the user did gradlew createModuleX locally first? Support both cases? "Create and fill module x" vs. "Create empty module x" ?

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/36714297-gooey-should-be-able-to-respond-to-a-privileged-user-and-create-what-s-needed-for-a-new-module?utm_campaign=plugin&utm_content=tracker%2F983091&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F983091&utm_medium=issues&utm_source=github).