Find meaningful ways to contribute

This issue involves adding a new compliance check for relay audit coverage. It requires modifying Go code to define the check, mapping it to existing compliance standards, updating documentation, and creating a changelog entry. The work is dependent on another "hub-emitter" child issue.

A test in the `PerformanceCounterCategory_GetCounters` test suite is failing on an ARM64 Windows build. The error indicates that a required performance counter category, 'PerformanceCounterCategory_GetCounters_Category', does not exist, suggesting a potential race condition or setup issue during test execution.

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. The governor will periodically post summaries of these advisory findings. It's crucial not to close this issue as it's intended to be a continuously updated document.

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 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 requires updating the Zulip terminal client to use the new 'direct' message type for sending direct/private messages to Zulip servers supporting API feature level 17. This change aligns with the API's preferred method for direct messages and typing notifications, ensuring compatibility with newer server versions.

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 automating the process of pulling match logs after a competition match concludes. The goal is to save the latest log to the drive station and, if a USB drive is connected, to that drive as well, ensuring space is available. If immediate post-match pulling isn't feasible, a fallback mechanism for ASAP log retrieval to USB is required.

This issue requests the addition of a public DNS resolver from an underrepresented geographical region (Africa, South America, Middle East, or Oceania) to the project's existing list. The goal is to expand coverage beyond current regions like the US and EU by adding a single, well-documented, publicly intended resolver per new region.

This issue proposes adding a missing major website to one of the project's curated connectivity import lists. The process involves identifying a suitable site, adding its details to a JavaScript file, and ensuring the favicon is correctly downloaded and committed. The contributor should first propose the site in a comment for review.

This issue requests community contributions to expand country-specific connectivity lists. Contributors are asked to identify relevant local and global services for their country, provide an ID and flag emoji, and submit their findings as a pull request. The goal is to create more comprehensive and locally relevant internet connectivity data.

This issue invites community members to translate the project's README file into languages not already supported. Contributors should first comment with the desired language to avoid duplication, then create a new translated file based on the English version, following specific formatting guidelines.

This issue is a call for community contributions to translate the MyIP application into new languages. The developers have simplified the translation process, requiring only a few commands and minimal code changes, making it accessible even for those unfamiliar with Vue. They encourage partial translations and offer existing localized data for specific languages to enhance the translation effort.

This issue introduces an opt-in feature for relays to upload audit attestations, allowing contributors to share specific levels of audit data (lifecycle, commands, or reasoning). The relay will attach these attestations to task completion/failure frames, and the hub will record them, potentially storing command details separately for higher sharing levels. This feature is part of a larger initiative and is currently blocked by other related tasks.

This issue proposes to integrate the 'hive-code-defect' triggers from the fleet report system into the existing self-report tracker. Currently, fleet reports lack rich context like hive names, owners, and diagnostic details, making them less actionable compared to self-reports. The goal is to consolidate these triggers to improve the quality and actionability of automated reports.

This issue aims to re-enable the site's internal search functionality. It involves creating a new `/search/` page using an existing component, filtering search results to only published articles by title, and restoring the search entry point in the header. User-facing text will be translated to Chinese, and the search query parameter `?q=` will be supported.

This issue proposes a new feature to automatically enable a user's personal projects upon login. The goal is to enhance user experience by making their projects readily accessible as soon as they authenticate.

This issue involves adding a new filter to the audit API to allow filtering by contributor login. It also includes UI updates for an audit log filter chip and a "Your assignments" card on the Contributor Operations tab. The work is dependent on a previous issue related to relay actions.

This issue aims to improve the handling of `acmm-shortfall` reports by preventing them from creating new standalone issues when an existing open self-report for the same component and version already exists. Instead, the `acmm-shortfall` information will be rolled up into a comment on the existing self-report. If no open self-report is found, the `acmm-shortfall` will be filed as a standalone issue with additional identifying information.

This issue proposes adding support for IP subnet and range patterns (e.g., 192.168.x.*) to the site data exception list. Currently, only exact IPs or hostname wildcards are supported, making it difficult for users to whitelist entire local networks while still benefiting from the clear-on-exit feature for public sites.

This issue aims to refactor the fleet reporting system by removing the 'hive-code-defect' synthesis and ensuring all fleet reports are enriched with identity, ownership, and diagnostic information. It also addresses a bug where relayed reports could have zero labels, ensuring a fallback mechanism is in place.

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 aims to enhance the fleet reporting system by introducing self-reporting classes for agent stalls, crash loops, and CI poll nudges. These new classes will provide more detailed information in reports, replacing the current generic "hive-code defect" issues. The implementation involves adding new entries to the fleet report system, observing them at specific counter hook sites, and including comprehensive diagnostics and recovery mechanisms.

The KiCad exporter fails to place components on a 127-component board, even with ample free space and various configuration attempts. The issue appears to stem from the placer's greedy first-fit algorithm, which lacks backtracking and struggles with moderately filled boards.

This issue requests the addition of unit tests for the `MarshalBinary` interface implementations in the Go SDK's command types. The goal is to ensure that the binary serialization and deserialization of commands are correct and compatible with the Iggy server's expected format. This will improve data integrity and protocol reliability.

This GitHub issue is a request for a content review of Chapter 6.1, "Embeddings and RAG Fundamentals," which is part of a larger work on Mastering Agentic AI Systems. Reviewers are asked to assess technical accuracy, currency of tools, clarity, and relevance to specific certification exams, with a focus on Retrieval-Augmented Generation (RAG).

This feature request aims to implement comprehensive audit logging for the ClankeR contributor relay. Currently, the relay lacks end-to-end accountability for actions involving short-lived GitHub tokens and task leases, making it difficult for operators to track contributor activity and for the system to meet compliance requirements.

This issue requests documentation for a new pre-chat form feature in the widget. The documentation should cover its configuration options, behavior, and integration with the existing chat system. It also requires updating the `WidgetConfig` reference and ensuring the documentation site builds successfully.

The protobuf compiler (protoc) for C++ generates code where enum values, specifically `SEVERITY_ERROR`, conflict with globally defined macros or variables from system headers like `winerror.h`. This conflict leads to build errors in C++ projects on Windows.

This issue proposes migrating from Karma to Vitest for Angular testing. The goal is to enable running Angular services within Vitest's spec files, either by initializing an Angular testing module for Vitest or by following a provided migration guide.