Find meaningful ways to contribute

This issue proposes the creation of a validating webhook for the Burrito project. The webhook will be responsible for validating resources before they are applied, specifically focusing on the `remediationStrategy` enum and complex interactions between various options.

This issue proposes that the public site should display blocks set to 'wide' or 'full width' similarly to how WordPress does. Currently, the site renders the saved markup but lacks the necessary layout classes and styling to achieve this visual effect, leading to content appearing uniform regardless of width settings. The solution involves adding WordPress's layout classes during block rendering and incorporating WordPress's root padding rules into site styles.

This issue identifies a bug where users cannot access message action buttons in specific overlay menus (Drafts, Scheduled messages, Message reminders) using keyboard navigation. The fix involves enabling Tab and Shift+Tab functionality for these buttons to improve accessibility.

This issue requests the implementation of a new Git provider for Bitbucket. It specifically mentions building upon the new structural changes introduced in a recent pull request, indicating a need to integrate with an existing framework.

This issue proposes adding a new configuration setting to the Burrito tool. This setting would prevent Burrito from executing 'apply' operations if the 'plan' output indicates that any resources are scheduled for destruction. The goal is to enhance safety and facilitate adoption on critical Terraform code by preventing accidental resource deletion.

The Cloud VM CLI incorrectly ignores trailing arguments or unknown flags for mutating verbs, potentially leading to unintended actions or incorrect machine operations. This issue affects multiple commands and requires stricter argument validation before executing RPCs.

This issue is a beginner-friendly task for Hacktoberfest, inviting contributors to add a new Japanese video game quote to a JSON file. No coding experience is required, and the contribution can be made directly through the browser in under a minute.

This issue aims to improve the discoverability of custom bot modules for users of zulip-botserver. The goal is to make it easier for less experienced Python users to set up bots successfully, likely through documentation improvements and adjustments to how bot modules are located.

This issue requests the creation of a comprehensive documentation section detailing the prerequisites for contract development. It aims to consolidate information scattered across various files, including specific toolchain versions and installation instructions, to streamline the onboarding process for new developers.

The "Close Other Tabs" feature in remote tmux mirror workspaces incorrectly leaves tmux windows alive after closing local tabs. This is because the menu/shortcut path uses a forced close that bypasses the logic responsible for communicating with tmux, unlike the context menu path which handles this correctly. The issue stems from how the `force: true` parameter skips the mirror routing mechanism.

This issue proposes adding CLI commands to control the visibility of the left sidebar in cmux. Currently, users must rely on macOS Accessibility features, which have security and fragility drawbacks. The proposed solution offers direct commands like `cmux left-sidebar show|hide|toggle` and `cmux left-sidebar state` for better scriptability and reliability.

This issue asks to investigate and remove an unused `vite.config.ts` file in a Next.js frontend project. The file might be a remnant of a past migration or intended for a tool like Storybook or Vitest, which needs to be confirmed. If it's truly unused, it should be deleted along with any redundant dependencies to improve project clarity.

The `ls --zero` command incorrectly terminates the last line with a newline character instead of a NUL character when used with column formatting options (`-C` or `-x`). This behavior deviates from GNU coreutils and the expected functionality of `--zero` which is to use NUL as a terminator for all output lines.

This issue requests the creation of a comprehensive runbook for upgrading and rolling back Soroban contracts. It needs to detail the step-by-step process, including wasm hash verification, state migration, and rollback procedures, with a dry-run walkthrough on testnet.

This issue requests the addition of Storybook stories for two key components, `DisputeWizard.tsx` and `MessageThread.tsx`. The goal is to create comprehensive stories that showcase various complex states of these components, using mocked data to avoid real network calls. This will improve the ability to demo and test these components independently.

This issue proposes adding a new `--no-color` (or `-nc`) command-line argument to the project. This argument should globally disable ANSI color styling for all command outputs, ensuring plain text output. This is a straightforward enhancement to improve accessibility and scriptability.

This issue proposes implementing a new `get_escrow_history` function to retrieve all state transitions for a job directly from the blockchain. This would enhance trustlessness by allowing on-chain verification of escrow history, rather than relying on an off-chain indexer. The implementation will involve modifying the escrow contract to log transitions and adding a new view function with comprehensive tests.

This issue proposes creating a public, read-only API to allow external tools to access a suite member's execution material. Currently, this functionality is internal to kmx, making it difficult for other tools to obtain this data without duplicating internal logic. The new API would provide a safe and typed way to load and retrieve this information from packaged suites.

The current docker-compose setup for development mode is broken because the production Dockerfiles are used, which lack necessary development dependencies and tools like nodemon and the Next.js CLI. This leads to services crash-looping. The issue requires either creating dedicated development Dockerfiles with dev dependencies or removing the development command overrides and relying on production commands.

This issue aims to improve the documentation for the sandbox Custom Resource Definition (CRD) by clarifying several non-obvious behaviors. It details how changes to replica counts, pod templates, and volume claim templates affect running pods and their associated resources, highlighting areas where current behavior might be surprising to users. The goal is to accurately record existing functionality and identify areas for future enhancement.

This issue proposes replacing custom logic for flattening and unflattening nested tensor structures in LLM Compressor and Compressed Tensors with the more robust `torch.utils._pytree` module. The goal is to improve code reliability and potentially simplify existing implementations by leveraging a standard library function.

This issue proposes adding a new function to the escrow system that allows clients to increase the locked budget of an active job. This will prevent the need to cancel and recreate escrows when job scopes expand, preserving historical data and milestone structure. The implementation involves changes in Rust smart contracts and a backend JavaScript endpoint.

This issue proposes moving the `ACCESSIBILITY_SUMMARY.md` file from the frontend root to the `docs/` directory, renaming it to `accessibility.md`. The goal is to make accessibility documentation more discoverable by updating its content, adding it to the main `docs/INDEX.md`, and ensuring it describes how to use the project's accessibility testing tools.

This issue involves localizing the custom 404 error page. The goal is to move all hardcoded English strings from the `404.tsx` page into translation keys within the `common.json` files for all supported locales. This ensures that users see the 404 page in their preferred language and that the existing i18n test suite passes.

This issue proposes refactoring three existing source generators from `ISourceGenerator` to `IIncrementalGenerator`. This migration is now feasible due to the removal of .NET 5 target framework dependencies, aiming to improve performance and incremental build capabilities.

The frontend's type-checking script is currently a placeholder that always passes, masking potential type errors in the TypeScript codebase. This issue requires re-enabling the actual `tsc --noEmit` command, fixing any existing type errors, and ensuring the CI pipeline correctly fails on new type errors.

This issue proposes expanding LeTrain's Linux installation options beyond Snap and portable zip files. The goal is to create native .deb and .rpm packages for common Linux distributions, as well as an AUR package for Arch Linux users. These packages will be generated automatically by the CI pipeline, providing users with more convenient and integrated installation methods.

This issue serves as a discussion and tracking point for requests and implementation of new "profiles." The list includes a wide variety of software, ranging from command-line tools and system utilities to desktop applications and games, indicating a broad scope for profile creation.

This enhancement request aims to enable keyboard-based panning of a canvas in view mode. Users should be able to move the canvas using arrow keys, including diagonal movement, with a slight deceleration effect similar to Miro.

This issue proposes adding a 1-click deploy option to Heroku, leveraging Docker deployment methods. The contributor notes that a similar feature has already been implemented in Rocket.Chat, suggesting a precedent and potential for reuse of existing patterns.