# Hackathon Elevator Pitches ###### tags: `contributor summit` ## Format for new entries Copy this section: ``` ## Project or Group Name Short paragraph describing who you are and what you will be working on during the hackathon. A list of things you would like to work on during the hackathon: - General Idea #1 - Specific Issue #1 - etc. ``` ## Ansible Community Team Hi! We're the Ansible Community Team and we'll be around throughout the entire hackathon ([our planned schedule](https://cryptpad.fr/sheet/#/2/sheet/edit/YB1Z2ZiIVZOC59teLR72wfia/)). We'll mostly be working on making sure things are working for everyone else. ## `community.network` Collection Hi, I'm [Deric](https://github.com/dericcrago), I'm one of the maintainers of the [`community.network` collection](https://github.com/ansible-collections/community.network). We'll be around throughout the entire hackathon ([`community.network` schedule](https://cryptpad.fr/sheet/#/2/sheet/edit/+rLidUMvsByHjVxCXYnaipdd/)). List of things we'll be working on (in order): - Fixing [CI sanity errors](https://dev.azure.com/ansible/community.network/_build?definitionId=32&_a=summary) - Reviewing [PRs](https://github.com/ansible-collections/community.network/pulls) - Triaging [Issues](https://github.com/ansible-collections/community.network/issues) ## antsibull Who: Toshio (abadger1999) What: https://github.com/ansible-community/antsibull I'll be working on the tool which is used to build the ansible package from ansible-core and the collections during this hackfest. The tool also generates the plugin docs for docs.ansible.com. Easy things that will get worked on: * changing ansible-base references to ansible-core (edits to comments, docstrings, and renames of variable names). * Fixing the plugin template to remove hardcoded "module", substituting $plugin_type instead. * Add a file with collection versions to the ansible tarball: https://github.com/ansible-community/antsibull/issues/156 Harder things that will be worked on if someone is interested in getting started during the hackathon but doing continuing work after: * Adding plugin attributes to the generated documentation. (PR mostly done, mockups and templates to implement them needed) * Account for different version numbers for ansible-core and ansible in the ansible package build. ## Basic collection code improvements **Who:** Andrei Klychkov GitHub: Andersson007 IRC/Matrix: andersson007_ *"Hi there! I'm a maintainer of several Ansible collections. Me or other developers will be happy to help you with fixing these very simple issues during the hackathon. See [our planned schedule](https://cryptpad.fr/sheet/#/2/sheet/edit/YB1Z2ZiIVZOC59teLR72wfia/)."* **What:** **(DONE by Honiix on Matrix)** https://github.com/ansible-collections/community.proxysql/issues/68 **Why:** This is a basic refactoring easyfix issue that would be good for first-time contributors. This does NOT require any knowledge of ProxySQL. **Essense:** Moving a function from each module to a library, then load it from there instead of using the same copy everywhere. PR https://github.com/ansible-collections/community.proxysql/pull/78 **What:** https://github.com/ansible-collections/community.general/issues/3353 **Why:** Misc doc examples formatting easyfixes. Does NOT require any technology-specific knowledge. **Important:** this can be done with separate PRs to let at least **four** folks train their skills. So please pick up one file to fix and let us know which one.l **What [NOT VACANT, SOLVED]:** **Why:** These are doc examples formatting easyfixes. Does NOT require any technology-specific knowledge. **Important:** this can be done with separate PRs to let **two** folks train their skills. So please pick up one file to fix and let us know which one. File 1 https://github.com/ansible-collections/community.general/pull/3479 File 2 https://github.com/ansible-collections/community.general/pull/3485 ## ara Who: dmsimard What: - https://github.com/ansible-community/ara - https://github.com/ansible-community/ara-collection Demo: https://demo.recordsansible.org/ Would you like to try ara in order to have simple reporting for your Ansible playbooks ? The author as well as contributors to the project will be around to help, answer questions and identify gaps in the getting started documentation. ## Stats Feedback Discussions Who: Greg (gwmngilfen:ansible.im) Working with maintainers and contributor on figuring out what stats make sense to track. How do you (a user) decide what projects look alive and well maintained? How do you (the maintainer) know if you're on top of your repo? What else is useful when working in Open Source? ## Docs Who: samccann & ariordan Where: #ansible-docs **What:** https://github.com/ansible/ansible/issues/75663 **Why:** These are doc examples formatting easyfixes. Does NOT require any technology-specific knowledge. Others: https://github.com/ansible/ansible/labels/hackathon ## Matrix Docs, Tooling & Usage Who: Greg (gwmngilfen:ansible.im) Where: Matrix, room TBA Matrix is our new shiny in the Ansible Community. I'll be available for: - If something isn't working for you - get help with anything Matrix related - Fixing the many doc pages where IRC is mentioned - Good practice with the PR process and fixing docs - Writing Matrix bots - Hacking on other cool things we could do Join and discuss all your Matrix thoughts! ## Outreach (Meetups, events, Bullhorn) Who: Carol (@cybette:ansible.im) If you'd like to find out how you can help with Ansible Community outreach with meetups and newsletters, feel free to ping me and let's chat! ## Ansible Network Team Hello! We're the Ansible Network team and we'll be around during the hackathon ([our planned schedule](https://cryptpad.fr/sheet/#/2/sheet/view/UdUeX1uhoST66bnFvLP2lVg8bt4o6cs2DdpeEUL5DMk/)) to discuss all things Network Automation. We'll be available to: - Discuss issues or feature ideas that you may have. - Talk about developing Resource Modules with `cli_rm_builder` and `RMEngineBase`. - Fixing CI sanity issues.