{"id":19402296,"url":"https://github.com/robertdebock/docker-scoring","last_synced_at":"2026-04-09T16:49:02.696Z","repository":{"id":90625982,"uuid":"81249710","full_name":"robertdebock/docker-scoring","owner":"robertdebock","description":"An application to analyse knowledge spread on technologies in a team.","archived":false,"fork":false,"pushed_at":"2017-03-30T14:24:49.000Z","size":9,"stargazers_count":1,"open_issues_count":0,"forks_count":0,"subscribers_count":3,"default_branch":"master","last_synced_at":"2025-02-16T10:28:52.361Z","etag":null,"topics":["analysis","awk","bash","bc","cut","docker","grep","sed","team","wc"],"latest_commit_sha":null,"homepage":null,"language":"Shell","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/robertdebock.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2017-02-07T20:15:04.000Z","updated_at":"2021-06-02T11:52:12.000Z","dependencies_parsed_at":"2023-07-16T02:00:42.337Z","dependency_job_id":null,"html_url":"https://github.com/robertdebock/docker-scoring","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/robertdebock%2Fdocker-scoring","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/robertdebock%2Fdocker-scoring/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/robertdebock%2Fdocker-scoring/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/robertdebock%2Fdocker-scoring/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/robertdebock","download_url":"https://codeload.github.com/robertdebock/docker-scoring/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":240576486,"owners_count":19823293,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["analysis","awk","bash","bc","cut","docker","grep","sed","team","wc"],"created_at":"2024-11-10T11:22:56.357Z","updated_at":"2025-10-29T13:39:05.908Z","avatar_url":"https://github.com/robertdebock.png","language":"Shell","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Scoring\nAn application to analyse knowledge spread on technologies in a team.\n\nImaging you want to understand strong and developmental areas within a group\nof people. This tool can be used to analyse a teams knowlegde.\n\n## INPUT\nFill details in the file \"input.txt\". Every line start with a technologie,\nand appends a score per person. Higher is better. For example like this:\n\n    Docker 1 3 5\n    Vim    3 2 1\n    HTML   5 4 5\n\nThis means:\n- There are three people in the team, because there are 3 columns.\n- There are three technologies being analysed, because there are 3 lines.\n- Knowledge on Docker is varying from low (1) to higher (5).\n- Knowlege on HTML is pretty high.\n\n### LIMITATIONS ON INPUT\nPlease make sure:\n- Every line starts with a \"technology\".\n- There are at least two lines.\n- Every technology is followed by two or more scores, separated by a\n  (white)space.\n- A technology is one word.\n- A score is one number, without periods or commas.\n\nMore samples make a more interesting result, I would suggest listing seven or\nmore technologies, and four or more scores/people.\n\n## ANALYSE\nYou can hook up a commit to CI, travis.yml has been provided.\nYou can also manually run the scripts. Using Docker is the most logical:\n     \n    docker tag $(docker build . -q) scoring\n    docker run scoring\n\n## OUTPUT\nAn example output can look like this:\n\n    # Analysis of technology knowledge.\n\n    Our team can clearly work with Git.\n    We all feel insecure about Python.\n    We are most similarly knowledgable on Puppet.\n    Our expertise level differs most for Packer.\n    The team may miss some knowledge about Packer.\n    Not everybody in the team has knowledge on Packer.\n\n## PRESENTING\nThe output is displayed in MarkDown format, you can use reveal-md to\npresent the output, or simply \"cat\" it. It's quite readable.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Frobertdebock%2Fdocker-scoring","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Frobertdebock%2Fdocker-scoring","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Frobertdebock%2Fdocker-scoring/lists"}