{"id":19030650,"url":"https://github.com/hackclub/slacker","last_synced_at":"2025-04-23T16:06:22.267Z","repository":{"id":199984885,"uuid":"703588899","full_name":"hackclub/slacker","owner":"hackclub","description":"Slacker is an attempt to organize and systematize our developer/customer support use cases into something that is easy to manage and measure, and also is welcoming of newcomers wanting to help participate on projects.","archived":false,"fork":false,"pushed_at":"2024-09-10T01:55:40.000Z","size":808,"stargazers_count":17,"open_issues_count":8,"forks_count":18,"subscribers_count":3,"default_branch":"main","last_synced_at":"2025-04-23T16:06:15.469Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"","language":"TypeScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/hackclub.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":"CONTRIBUTING.md","funding":null,"license":null,"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":"2023-10-11T14:20:45.000Z","updated_at":"2025-04-04T04:13:23.000Z","dependencies_parsed_at":"2023-10-26T23:23:27.540Z","dependency_job_id":"14f5e389-785e-4f9e-b7e0-20ae418edcc1","html_url":"https://github.com/hackclub/slacker","commit_stats":null,"previous_names":["hackclub/slacker"],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/hackclub%2Fslacker","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/hackclub%2Fslacker/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/hackclub%2Fslacker/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/hackclub%2Fslacker/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/hackclub","download_url":"https://codeload.github.com/hackclub/slacker/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":250468273,"owners_count":21435452,"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":[],"created_at":"2024-11-08T21:18:59.167Z","updated_at":"2025-04-23T16:06:22.247Z","avatar_url":"https://github.com/hackclub.png","language":"TypeScript","funding_links":[],"categories":[],"sub_categories":[],"readme":"# What is Slacker?\nAt Hack Club, we have a lot of different projects that need ownership over the long-term.  Each project might encompass many git repositories and Slack channels that need various different levels of support.  Slacker is an attempt to organize and systematize our developer/customer support use cases into something that is easy to manage and measure, and also is welcoming of newcomers wanting to help participate on projects.\n\n# Project scope\n* Its primary purpose is to match incoming work with correct project maintainers\n* It is Github and Slack aware, which are both avenues through which work is submitted to us in practice @ HC\n* It is a system designed such that we do not drop balls (ignore and fail to triage incoming work), and will measure this directly via a time-series document trail written to ElasticSearch\n* Also aims to invite people to join teams and gain responsibilities, advertising them via Slack and web interfaces\n* Will (semi or fully) automate work where possible\n\n# How do I use it?\nCurrently, the main interface to Slacker is via issuing slack bot commands.  A good first step to to run ```/slacker help``` to generally see its capabilities - but generally, one takes the following process:\n1. Assign yourself to a project via a project in the [config directory](https://github.com/hackclub/slacker/tree/main/config).\n  \u003cbr\u003e**_NOTE:_** _You must be entered into the [maintainers config](https://github.com/hackclub/slacker/blob/main/maintainers.yaml) to be assigned to a project._\n\n2. Run ```/slacker whatsup```, which shows all of the projects you're currently assigned to.\n  \u003cimg width=\"512px\" src=\"https://cloud-leau67md4-hack-club-bot.vercel.app/0screenshot_2023-11-13_at_11.03.36_am.png\"\u003e\n\n\n3. Run ```/slacker gimme``` to self-assign the next work item.  After you investigate the AI, you can click 'Resolve' to signify the issue has been triaged successfully, 'Close - Irrelevant' to mark the issue as not needing action, or 'Snooze', where you can specify a time in the future to remind maintainers to triage this issue.\n\n  \u003cimg width=\"512px\" src=\"https://cloud-o3tl16zau-hack-club-bot.vercel.app/0screenshot_2023-11-13_at_2.35.43_pm.png\"\u003e\n\n4. If you need to regain context on your current work, run ```/slacker me```.  This will display all work items that are currently assigned to you.\n\n# Can it support my project?\nIn all likelihood, yes.  Just add yourself and your project members to the global [maintainers configuration file](https://github.com/hackclub/slacker/blob/main/maintainers.yaml), and add a new project config [here](https://github.com/hackclub/slacker/tree/main/config).  Here is an example from the Sprig project - it is fairly self-explanatory...\n```\nname: Sprig\ndescription: Teens make games and get a Sprig\nmaintainers: [leo, lucas, kognise, max, graham, josias, shawn]\nchannels:\n  - name: sprig\n    id: C02UN35M7LG\n    sla:\n      responseTime: 1h\n  - name: sprig-platform\n    id: C04S1A8NT44\n    sla:\n      responseTime: 24h\n  - name: sprig-device-requests\n    id: C063DFZ532M\n    sla:\n      responseTime: 24h\nrepos:\n  - uri: https://github.com/hackclub/sprig\n    sla:\n      responseTime: 1h\n  - uri: https://github.com/hackclub/spade\n    sla:\n      responseTime: 24h\n```\n\n# Backend architecture\n\u003cimg width=\"768px\" src=\"https://cloud-5qrh6ctqm-hack-club-bot.vercel.app/0screenshot_2023-11-13_at_9.37.43_am.png\"\u003e\n\n# How can I learn more?\nFeel free to visit the [#hq-engineering](https://hackclub.slack.com/archives/C05SVRTCDGV) Hack Club Slack channel and ask away!\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fhackclub%2Fslacker","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fhackclub%2Fslacker","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fhackclub%2Fslacker/lists"}