siggame / colisee Goto Github PK

Rendering of the table on http://siggame.io/colisee is messed up.
Its probably something to do with the spacing of the Markdown table.

Core Responsibilities:

• Ingest file with team name
• Build docker image from archive
• Push built docker image
• Report status of submission
• Update status of submission on db

Core Responsibilities

• Establish and maintain relations between entities siggame/colisee-db#18

simplifies networking and also can help with security

Core Responsibilities

• Ingest game from db
• Pull docker image for each team
• Run docker image for each team
• Report status of a game
• Update the progress of a game on the db

Things that should be outlined in this section

• Prefer branching over forking
• Master branch is the development branch
• Stable branch is curated by repo owners.
• Code should be developed in typescript
• Add tests for major normal and robustness testing
• Generally prefer 4 space indenting.
• Prefer lambdas
• Prefer automatic type deduction except where value is possibly undefined/null
• Use strictest null checks

• Create intitial generic API

• Create local FS API implementation

• Create Google Storage API implementation

• Add project scaffolding

• Update README to initial specifications

Core Responsibilities:

• Ingest list of teams
• Create tournament schedule for given teams
• Create new games as tournament progresses
• Report status of tournament

Add a column in the services table that contains a badge showing the number of issues in that repo

Use the following as a template:

[![Open Issues](https://img.shields.io/github/issues-raw/siggame/colisee-builder.svg?style=flat-square)](http://github.com/siggame/colisee-builder)

Requirements that a README should have

• title - siggame/thing
• badges - Travis Build, DockerHub Pulls, dependencies
• table of contents
• description (should contain link to primary developer)
• Getting Started
• API

When downloading the build logs from the server, it appears that they are not downloading in the gzip format although they still have the .gz extension. Even when viewing it though, there still appears to be a problem with the files.

Here is an example where I renamed the file to a .txt file for convenience and then opened it up in a text editor to show the issues

• Use each component for CS5400 Spring 2018

Core Responsibilities

• Ingest teams from db
• Create game from teams

• Backlog
• Blocked
• Ready
• In Progress
• Completed

Ignore:

.vagrant/
.vscode/
.idea/
.env

*.log

node_modules/
docs/
dist/
npm-debug.log

src//.js
src/.js
test//.js
test/.js