Find meaningful ways to contribute

This issue requests native speaker reviews for the Spanish, French, Italian, and Russian interfaces. The current translations were machine-generated and lack human linguistic validation, despite checks against style guides and glossaries. Native speakers are needed to ensure accuracy, appropriate tone, and correct handling of language-specific nuances like plurals and address forms.

This issue proposes adding a `project.reference_repos` configuration to allow agents to read from external repositories for assessment purposes without needing them to be authorized. It also introduces an optional opt-in for limited write access (issues/PRs) to these reference repositories, with strict limitations to prevent unauthorized modifications.

This issue involves updating documentation across several files to accurately describe the `project.reference_repos` configuration. The documentation needs to cover its various forms, default behavior, write permissions, and rendering implications. This is a documentation-focused task that is part of a larger effort and is currently blocked by another issue.

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 to display "reference repositories" in the dashboard's repository list. These reference repositories will be visually distinguished with specific chips and will not show ACMM evaluations or work item counts, indicating a read-only or limited functionality status.

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.

This issue proposes adding a new section to the scanner's kick message to display read-only reference repositories. It aims to clarify how findings related to these reference repositories are handled, ensuring they are considered in scope for analysis and their deliverables are associated with the authorized repository.

This issue is a "good first issue" that invites contributors to add a new offline developer tool to the Dev Utilities Sandbox. The tool should be client-side, provide value to developers, and integrate with the existing UI. Examples of potential tools are provided, but contributors are encouraged to suggest their own.

This issue proposes implementing read-only access for 'reference repos' within the GitHub proxy. Public GET requests and clones will be allowed, but all write operations will be denied with a specific 403 error indicating the repo is a read-only reference. It also outlines opt-in write permissions for specific actions like opening issues or PRs on the hive's own items.

This issue proposes adding a new configuration field, `ProjectConfig.ReferenceRepos`, to manage referenced repositories within a project. It will support both simple owner/name strings and more complex objects allowing write permissions for issues and pull requests. The implementation includes validation, a new accessor for retrieving repository tiers, and comprehensive testing.

This feature request aims to improve face management by allowing manual review and assignment of faces even when automated face recognition is disabled. It also proposes scoping the unnamed and suggested faces queues to match selected categories in the sidebar, providing more context-aware filtering.

A test case for a kernel rig is failing because a previously refused operation (a fillet) is now successfully built by Solidcore. The issue requires updating the test to grade the successful build based on its analytic volume and geometric properties, rather than expecting a refusal. The test should be adjusted to reflect the new successful behavior and removed from the known failing list.

This issue proposes renaming database tables and fields to improve clarity and simplify naming conventions. Specifically, `sponsor_partner` will become `affiliate`, `project_sponsor_partner_xref` will be renamed to `affiliation`, and the `is_sponsor` field will be changed to `type` to better represent the relationship.

The developers are seeking testers to verify the compatibility of 'hyperbutler' with a running Docker Desktop instance on Windows 11. They need users to perform specific commands and observe the behavior of both applications, particularly concerning Docker contexts, port publishing, and WSL 2 integration.

This issue requests community members to test a new Linux port of the Claude Desktop application. Testers need to build the application from a specific branch, install it, and then perform basic functionality tests like adding and switching between multiple accounts, and testing the 'Start at login' feature. Feedback on their Linux distribution, desktop environment, and any encountered issues is required.

Pull-only hosted spokes without a startup probe crash-loop when the forge is unreachable because synchronous GHE calls during startup exceed probe timeouts. The fix involves adding a startup probe to these spokes and improving the status dot legend.

This feature request aims to allow users to define and manage review perspectives for a "hive" directly from a GitHub file, similar to how other configurations like `definition_source` are handled. This would enable maintainers to update perspectives through standard PRs while still leveraging upstream changes to the `reviewer-queue.md` protocol.

The GitHub Actions CI pipeline is failing because the MySQL service cannot be started. The error message "sudo: '/etc/init.d/mysql': command not found" indicates that the script to start MySQL is missing or not accessible in the CI environment. This prevents the tests from running successfully.

This issue is a beginner-friendly task to add a new Japanese cultural etiquette tip to a JSON file. It requires no coding and can be completed in under a minute by forking the repository, editing the file directly in the browser, and submitting a pull request.

This issue proposes adding a new command-line interface (CLI) option to F3D that allows users to generate an animated camera orbit. This feature would be useful for scenes that lack pre-defined cameras or animations, providing a default orbiting behavior to visualize the scene.

This issue requests the addition of a project gallery to the website, mirroring the functionality and design of the example provided by the moviepy project. The goal is to showcase projects in a visually appealing and organized manner.

This issue serves as a central hub for advisory findings from Hive agents, particularly at lower ACMM levels where agents analyze code without creating direct issues or PRs. A governor agent periodically posts digest comments summarizing these advisory findings. This issue is intended to be a living document and should not be closed.

This issue requests the creation of user-facing documentation for an existing managed identity SQL Server example. The goal is to explain how to use the example, including necessary permissions and placeholders, without requiring local credential storage. It also aims to add service-free checks and cross-link the example within the existing documentation.

This issue proposes exploring the use of a USSE microkernel on the SGX535 GPU, similar to how the vendor stack operates. The author has developed an open-source microkernel for the SGX545 that handles GPU-specific tasks without host intervention, and is inquiring if a similar approach has been considered for the SGX535, noting potential hardware differences.

This issue proposes implementing anomaly detection and alerting for Bitcoin P2P metrics currently displayed in Grafana dashboards. The goal is to move beyond raw data visualization by identifying unusual patterns, such as sudden drops in inbound connections or spikes in address messages, and triggering alerts based on statistical methods like Z-scores.

The 'zizmor' CI check is failing simultaneously on 10 open pull requests in the projectbluefin/server repository. This widespread failure suggests a shared root cause, likely related to the base branch, a workflow configuration, a pinned GitHub Action, or the runner image, rather than individual code changes. The issue is being tracked centrally to address the underlying problem efficiently.

The user wants to replace the current `java.awt.Robot` class for bot controls with more efficient APIs like `PostMessage` (on Windows) or equivalent for Linux. This change aims to allow users to continue using their devices while the bot is active, improving usability. The project targets Windows (7+) and Linux (Ubuntu).

The `pods.prune` API endpoint in Podman is not respecting the provided filters, leading to the deletion of all eligible pods in the store instead of only those matching the filter. This affects users who expect scoped deletion based on labels, as demonstrated by the `podman-py` library.

The Podman API's `networks.list` endpoint incorrectly ignores name and ID filters when they are provided as part of a `filters` dictionary. Instead, it sends an unfiltered request and returns all networks. This behavior is due to the client library overwriting these filter keys with `None` when separate `names` and `ids` arguments are not present.