Find meaningful ways to contribute

This issue is a beginner-friendly request to add a new color theme called "Calligraphy Ink" to the KanaDojo project. It requires no coding and can be completed in under a minute by directly editing a JSON file in the browser.

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 GitHub issue announces a challenge to rigorously test the mathematical reasoning capabilities of the Spark-X2.5 language models. Participants are required to download the models, conduct evaluations on math benchmarks or specific problem types, and publish their reproducible results on Hugging Face Discussions. Submissions are open from September 7th to September 13th, 2026, with judging and awards following.

After upgrading Apache Airflow to version 3.2.0 on Python 3.12, users are unable to access the login screen due to a `TypeError` when creating cookies. This error, "cannot use a string pattern on a bytes-like object," originates from the FAB provider's session saving mechanism.

This issue is an onboarding task for new contributors to the Rustchain project. Participants are asked to star the repository, explore its documentation or code, and then file a bug report for any issues they find, such as broken links, confusing messages, or actual bugs. Successful submissions will be rewarded with 1 RTC.

This issue requires adding missing docstrings to magic methods within the Bio library, specifically in the Bio/SeqIO/_index.py and Bio/Geo/Record.py files. The goal is to improve code documentation by adhering to established docstring styles for special methods and subsequently removing the D105 rule from the flake8 configuration.

This issue asks to implement a command within `src/plugins/firstIssueRecap.ts` that generates a brief recap of a contributor's first merged issue, intended for social media sharing. The task involves understanding the TODO's intent, implementing the functionality, removing the TODO comment, and ensuring the code passes checks.

This issue requests adding test coverage to the `src/dailyIssueBacklog.ts` file. The goal is to ensure the main exported functionality is tested without relying on live network or GitHub API calls, and that the tests pass `npm run check`.

This issue asks to implement a command in `src/plugins/exportStats.ts` that exports a contributor's statistics (PRs, issues, labels touched) as a JSON file. The goal is to find the existing TODO, implement the described functionality, remove the TODO comment, and ensure the code passes `npm run check`.

This issue proposes creating a new Markdown guide to help beginners understand and resolve 'Updates were rejected' Git push errors. The guide should explain the cause of the error in simple terms, offer a safe recovery command like `git pull --rebase origin main`, and warn against using destructive reset commands without understanding them. The guide will be linked from the README.

This issue requests the creation of a document outlining the project's commit message convention, including prefixes like `docs:`, `fix:`, and `feat:`. The goal is to provide clear examples pulled from the git log and link this guide from the `CONTRIBUTING.md` file.

This issue proposes adding a new animated accordion component to the repository. The component should feature smooth transitions for expanding/collapsing content and a rotating chevron icon. This is intended to enhance the user experience for displaying structured content or FAQs.

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 adding a new command-line interface (CLI) tool called `openmed i18n check`. This tool will allow language-pack contributors to perform an offline validation of locale packs, ensuring metadata, registry wiring, synthetic fixtures, span integrity, and evidence references are correct. The goal is to provide deterministic output for easy integration into CI/CD pipelines.

This issue proposes generating deterministic, reusable metadata-only fixtures for private learning tests. These fixtures will simulate heterogeneous clients and round outcomes without requiring actual site simulations, ensuring byte-identical outputs for identical seeds and excluding sensitive data.

This issue aims to create a language pack readiness matrix that provides maintainers with a clear, deterministic view of the status of various language packs. The matrix will be rendered in both JSON and Markdown formats, utilizing existing data and ensuring comprehensive test coverage.

This issue aims to develop a tool to compare language coverage manifests between different releases without requiring model loading or clinical fixtures. The goal is to identify regressions and improvements in language capabilities by analyzing manifest differences across various linguistic attributes, ensuring stable golden outputs and focused unit tests.

This issue requires the implementation of a system to validate the license and lineage of synthetic clinical datasets. It involves defining strict manifests for dependencies like generators, templates, and models, and failing the process if any dependencies have restricted, incompatible, or unknown lineage. The scope includes defining these manifests and handling various problematic dependency scenarios, with tests focusing on offline unit tests using synthetic fixtures.

This issue proposes to add preflight checks for secure aggregation rounds to ensure that quorum, recovery threshold, and dropout tolerance parameters are internally consistent before enrollment begins. The goal is to fail federated rounds early if these parameters are invalid, preventing potential issues later in the process.

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 aims to create aggregate summaries of privacy budget consumption for differential privacy training rounds and model families. The summaries should not reveal individual site identifiers, employing techniques like small-cell suppression and deterministic bucketing to protect privacy while providing high-level insights.

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 aims to establish a robust and machine-readable contract for differential privacy budget policies. It involves defining strict, versioned policy types with bounded numeric fields and closed enums, while rejecting ambiguous or unsafe configurations. The goal is to ensure predictable and secure handling of privacy budgets in private learning rounds.

This issue proposes adding synthetic, malformed PDF and DICOM header fixtures to a preflight testing suite. The goal is to create reusable, deterministic test cases that simulate various header corruption scenarios for document and medical image files, aiding in the validation of preflight checks without using real sensitive data.

This issue requires the creation of a compatibility matrix that shows which local multimodal providers can handle specific validated modality profiles. The output should be a deterministic JSON and Markdown representation, detailing provider IDs, capability versions, profile IDs, and compatibility outcomes without including sensitive information like model paths or endpoints.

This issue requires the development of a feature to aggregate audio format statistics (channel, sample rate, bit depth, duration buckets, format) without storing any sensitive content like filenames, transcripts, or samples. The goal is to provide summarized counts for deployment planning, with specific requirements for handling edge cases and ensuring data privacy through small-cell suppression.

This issue aims to define and validate a content-free contract for frame-sampling manifests in clinical video. The goal is to ensure reproducible frame selection and coverage by establishing strict rules for manifest properties and testing various edge cases.

This issue requires developing a system to estimate the memory needed for multimodal data batches on edge runtimes before decoding. The estimate will be derived from asset manifest metadata and used to determine if a batch can be accepted, split, or rejected based on device budgets. The scope includes handling various data types and edge cases, ensuring platform-independent arithmetic and thorough unit testing.

This issue proposes to enhance DICOM processing by pre-checking transfer syntaxes before attempting pixel decoding. The goal is to identify unsupported or potentially problematic syntaxes early, allowing for a more robust and efficient pipeline by categorizing outcomes like native, optional-decoder, review, or unsupported with clear reasons.

This issue aims to detect conflicts between declared image geometry transforms and embedded orientation metadata (EXIF/TIFF). The goal is to identify and flag these discrepancies to prevent silent errors in region provenance after image transformations, without requiring pixel decoding.