Skip to content

Home

Jump to bottom
stranger edited this page Sep 19, 2019 · 18 revisions

*Note:* All dates below are in a DD/MM/YYYY format

What are we currently working on?

Everyone:

  • Familiarize yourself with the Source Code Management doc and the process for contributing code. You should be able to answer the question "which branch do you submit a pull request to?"

  • All pull requests will need 6 5 approving reviews before they will be merged

  • Familiarize yourself with the layout of GitHub Projects, Issues, Pull requests, and Wiki

  • (new: 07/09/2019) If you're new to GitHub, I highly recommend watching this video series on YouTube: Git and GitHub for Poets

  • (new: 07/09/2019) All tasks have been split up onto the Issues board in GitHub. Each Issue should include enough details to get you started. You are free to cherry-pick whatever you would like to work on. If you need help with something specific or need general advice, please reach out to any of the mentors on Discord. See the Projects tab on GitHub for a list of mentor usernames.

  • Once the project you wish to work on has a link to a mentor's development fork, you're free to clone that to your PC

Mentors:

  • Make sure your fork is even with the development branch of the main repo

  • Please edit your assigned project with a link to the development branch of your fork. It doesn't matter who's fork, just pick one and stick with it.

    THESE ARE STILL NEEDED:

    • Colony
    • Queen Progression
    • Forage
    • Species

  • You'll have to add your co-mentors as collaborators to your fork so they can approve PRs and whatnot if you're not available. From your fork, go to Settings > Collaborators > type in the GitHub username for each of your co-mentors and click Add Collaborator. Each person you invite must then accept.

  • Make sure you are a member in the Code Review team so that you can approve PRs. An administrator will have to add you.

Administrator:

  • More transparency, so anyone can see what is being worked on at any time (hence this wiki)
  • Weekly "State of the Game" updates to @everyone on Sundays
  • GitHub administrator will assign Code Review team to Reviewers section of PR

What are our next steps?

Everyone:

Mentors:

Administrator:

  • Continued GitHub and Discord organization
  • Continued game design and structure changes

What have we completed?

  • 12 coding teams with an average of 17 members each and 2-3 mentors on each, 230 total people
  • 12 team assignments
  • A web development team
  • A senior management team
  • A game design team
  • A skills test to determine who would make a good code reviewer, mentor, or manager
  • A source code management document
  • A first draft MVP structure
  • A first draft UML design
  • Travis-ci and Codecov integration for automated testing
  • Two huge architectural designs (see PR #69 and #71)
  • PR #71 merge into development branch
  • Change or remove existing team roles on discord to something else, currently TBD
  • Change team system to an open system on GitHub
  • Merge team assignment Google docs into each team's project or page on GitHub, give each mentor write access to original doc
  • Determine best course of action to break up big tasks into smaller tasks for individuals to work on
  • Decide what to do with all other PRs
  • Create a smaller "Code Review" team and reduce the number of necessary PR approvals
  • Shift project focus from Discord to GitHub, and align all Google docs/resources within GitHub resources
Clone this wiki locally