Tome of Knowledge: Beastmaster

Just a placeholder for now; this tome will include instructions and lessons learned by and for the Beastmaster.

In the unlikely event that a project is approved the Beastmaster should:

1. Convey their congratulations to the project owners in an appropriately sarcastic manner.

2. Make Project Owners aware of the aspects of projects, including:

• 2.1. Set up a GitHub Repo with a suitably amusing name at org level and Pin it with Apache 2.0 license*

• 2.2. Set up subdomain ie (myhillariouslynamedproject.biffud.com)

• 2.4. Establish appropriate email addresses if required and set up forwarding.

• 2.3. Set up appropriately named Slack channel and make people aware of its existence.

• 2.2. Meating Meating with the Beastmaster to establish:

  • 2.2.1 resources required
  • 2.2.2 frequency of project updates
  • 2.2.3 project best practice (set up a Kanban style Project View on GitHub with milestones etc)

3. Hand off to the Secretary of Code

*If you wish to use a different licence this can be discussed and potentially approved at a plotting session.