{"id":15157043,"url":"https://github.com/puppetlabs/may-the-source-be-with-you","last_synced_at":"2026-01-18T06:53:00.130Z","repository":{"id":160932513,"uuid":"635718962","full_name":"puppetlabs/May-The-Source-Be-With-You","owner":"puppetlabs","description":"💻 “May the Source Be With You” is a virtual hackathon focused on improvements to our developer tooling ecosystem. May 4th, 2023","archived":false,"fork":false,"pushed_at":"2023-12-05T22:47:31.000Z","size":116,"stargazers_count":0,"open_issues_count":0,"forks_count":1,"subscribers_count":6,"default_branch":"main","last_synced_at":"2025-02-09T11:15:30.450Z","etag":null,"topics":["hackathon","maythesourcebewithyou"],"latest_commit_sha":null,"homepage":"","language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"cc-by-sa-4.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/puppetlabs.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":"CODEOWNERS","security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2023-05-03T10:03:11.000Z","updated_at":"2023-05-03T16:16:13.000Z","dependencies_parsed_at":null,"dependency_job_id":"888523d2-ff8a-4ca0-bee0-52f6ef697001","html_url":"https://github.com/puppetlabs/May-The-Source-Be-With-You","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/puppetlabs%2FMay-The-Source-Be-With-You","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/puppetlabs%2FMay-The-Source-Be-With-You/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/puppetlabs%2FMay-The-Source-Be-With-You/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/puppetlabs%2FMay-The-Source-Be-With-You/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/puppetlabs","download_url":"https://codeload.github.com/puppetlabs/May-The-Source-Be-With-You/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":247093956,"owners_count":20882507,"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":["hackathon","maythesourcebewithyou"],"created_at":"2024-09-26T20:00:21.322Z","updated_at":"2026-01-18T06:53:00.092Z","avatar_url":"https://github.com/puppetlabs.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"![banner](images/puppet-may-the-source-be-with-you-2023.jpg)\n\n# May The Source Be With You - Hackathon 2023\n\nWelcome to our first annual _May the Source Be With You_ virtual hackathon focused on improvements to our developer tooling ecosystem.\n\nDo you have a pet peeve about the PDK, rspec-puppet, puppet-lint, the Puppet VSCode extension, or any other tool you use when building Puppet code? Join forces with us to help defeat these pain points during our live event.\n\n* May 4th, 2023\n* PDT: 10 am - 6 pm \n* CEST: 10 am - 6 pm \n\n----\n\nTable of Contents\n-----------------\n\n- [Agenda](#agenda)\n- [Before starting](#before-starting)\n- [Tools and resources](#tools-and-resources)\n- [List of challenges](#list-of-challenges)\n- [Submitting your contribution](#submitting-your-contribution)\n\n### Agenda\n\nThe following timelines are subject to the CEST and PDT time zones:\n\n- 10 AM - Welcome and introduction to the hackathon – Zoom session\n    - Sharing links and this repository\n    - Explaining the dynamics\n- 12 PM - Office hours on Slack (`#hackathons` channel) – 45 min\n    - This is a good opportunity to connect with some of our Puppet engineers, whether you have questions regarding one of the challenges or if you are stuck in setting up a project, let us know how we can help you here :)\n-  6 PM - Closing - Zoom session\n    - Participants recognition and final words\n\n### Before starting\n\n- [Sign up for the hackathon](https://docs.google.com/forms/d/e/1FAIpQLSc0jDa0SIFJjmBh9q2SoH55hIixFXbCWyedvGib5eUiRXyZbg/viewform) In case you haven't done that before\n    - 🦤 A little birdie says that you might even get a bit of exclusive swag for participating, too! \n- Make sure you are logged in the [Puppet Community Slack](https://slack.puppet.com/)\n- Join the [`#hackathons`](https://puppetcommunity.slack.com/archives/C055MT5TA2K/p1683127438265399) channel\n    - Most of the communication will be asynchronous, make sure you are in that channel so you don't miss anything!\n- Have some coffee ☕ and cookies 🍪 handy \n\n### Tools and resources\n\n- [Zoom](https://support.zoom.us/hc/en-us/articles/4415294177549-Downloading-the-Zoom-desktop-client-and-mobile-app). The hackathon kick-off and closing will happen via Zoom, make sure to check the `#hackathons` channel for more up to date information.\n- [Slack](https://slack.com/download)\n\n### List of challenges\n\n- Developer tooling ecosystem\n    - [Puppet PDK](https://github.com/puppetlabs/pdk)\n        - Open issues: https://github.com/puppetlabs/pdk/issues\n    - [Puppet Rspec](https://github.com/puppetlabs/rspec-puppet)\n        - RSpec tests for your Puppet manifests \u0026 modules\n        - Open issues: https://github.com/puppetlabs/rspec-puppet/issues\n    - [Puppet Litmus](https://github.com/puppetlabs/puppet_litmus)\n        - Litmus is a command line tool that allows you to run acceptance tests against Puppet modules\n        - Open issues https://github.com/puppetlabs/puppet_litmus/issues\n    - [Puppet VS Code extension](https://github.com/puppetlabs/puppet-vscode)\n        - Open issues https://github.com/puppetlabs/puppet-vscode/issues\n    - [Provision](https://github.com/puppetlabs/provision)\n        - When provisioning to GCP fails, make `provision::provision_service provisioner` retry on 500 error responses, there should be a MAX RETRY set though (3). So, the CI doesn’t fail due to provisioning failures.\n        - Previous attempts: https://github.com/puppetlabs/provision/pull/194\n    - [Puppet Code Validator](https://validate.puppet.com/)\n        - Open issues: https://github.com/puppetlabs/puppet-validator/issues\n    - [Puppet Spec Helper](https://github.com/puppetlabs/puppetlabs_spec_helper)\n        - Open issues: https://github.com/puppetlabs/puppetlabs_spec_helper/issues\n    - [PE Status Check](https://github.com/puppetlabs/puppetlabs-pe_status_check)\n        - lookup indicator_exclusions from hiera pe_status check\n        - Related issue on Github: https://github.com/puppetlabs/puppetlabs-pe_status_check/issues/127\n    - Rubocop offenses\n        - Help us to fix Rubocop offenses from our tooling and modules.\n        - This is a good way to get to know a new project, by making small changes to reduce the number of Rubocop offenses in a project.\n        - This is just one example about a [rubocop TO DO file from the PDK project](https://github.com/puppetlabs/pdk/blob/main/.rubocop_todo.yml)\n        - The best approach to fix these would be to:\n            - find repos with a `.rubocop_todo.yml`\n            - Look at the rules that have been excluded\n            - Comment one out\n            - Run bundle exec rubocop\n            - Commit your changes :)\n        - Here is the general search on all our public Github repos that use a `.rubocop_todo.yml` file that has active filters: https://github.com/search?q=org%3Apuppetlabs+path%3A.rubocop_todo.yml+%2F%5E.*%5C%2F.*%3A%24%2F\u0026type=code\n    - [Forge Ruby Gem](https://github.com/puppetlabs/forge-ruby)\n        - Issue: This library (gem) currently does no response caching of its own, instead opting to re-issue every request each time.\n- General help needed\n    - [Puppet's repositories labeled as `hacktoberfest`](https://github.com/search?q=topic%3Ahacktoberfest+org%3Apuppetlabs+fork%3Atrue\u0026type=repositories)\n- Greenfield solutions\n    - Build a module’s legacy facts scanner, it should receive an optional parameter (replace=true) to replace automatically the legacy facts for current facts\n- Bring your own challenge\n    - Maybe you have a bug that has been bothering you for some time now, or you want to improve a feature that your work depends on. Work on something that motivates you 😊\n    - You are not familiar with Puppet's Dev tooling ecosystem but you still want to contribute in a module? Please feel free to do that 🙌\n\n### Submitting your contribution\n\nAfter creating a Pull Request (PR) on the Github repositories, make sure to add the label `MayTheSourceBeWithYou` to it.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fpuppetlabs%2Fmay-the-source-be-with-you","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fpuppetlabs%2Fmay-the-source-be-with-you","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fpuppetlabs%2Fmay-the-source-be-with-you/lists"}