Makefile good first issues

This issue proposes the implementation of a comprehensive testing infrastructure for the repository, including unit, integration, and end-to-end tests. The goal is to achieve reliable test execution in CI and locally, with specific guidelines for each test tier, including mocking strategies, required dependencies, and desired code coverage.

This issue addresses problems with initial Bluetooth controller pairing in EmuELEC versions 4.7 and above. It provides troubleshooting steps including checking controller compatibility, forgetting the device, and running specific SSH commands to enable debugging for further analysis if the initial steps fail.

This issue proposes to freeze two specific documentation repositories on Launchpad (SRU docs and TB governance docs) to prevent further content updates. Additionally, the Launchpad projects themselves should be marked as deprecated and linked to a new, presumably existing, documentation set.

This issue proposes integrating Meshery's Nighthawk performance testing capabilities with AI assistants. The goal is to enable AI agents to initiate, monitor, and retrieve results from performance tests using natural language commands. This involves implementing several new tools within the MCP framework to manage the entire performance testing workflow.

This issue reports that a specific security requirement (FCS_CKM_EXT.7/LOCKED), which is linked to another requirement (FDP_DAR_EXT.2), does not currently list any Post-Quantum Cryptography (PQC) algorithms as supported. The goal is to ensure PQC algorithms are included in the relevant security specifications.

This issue proposes enabling writeable pflash and internal flashing for QEMU boards. Currently, firmware updates involve rebuilding QEMU, and injecting keys is done through separate build statements. The goal is to allow direct modification of the flash, potentially by patching QEMU and flashrom, and leveraging existing but niche QEMU features for unified firmware and variable storage.

The user is requesting support for Forgejo, a self-hosted Git service, as the current GitHub Action is not correctly making the built ISO artifact accessible in their CI environment. They are experiencing issues where the build appears successful but the output is not found by subsequent steps like `tree` or `upload-artifact`.

This issue proposes automating the creation of issues in SIG repositories to notify them of specification changes. The goal is to improve communication and ensure SIGs are aware of updates, potentially by leveraging automated changelog generation. Maintainers are being consulted to gauge desirability and address concerns about potential spam.

This issue requests a clear definition for 'traces' as a signal type within the OpenTelemetry specification. The goal is to add this definition to the existing glossary to ensure consistent understanding of OpenTelemetry signals.

This issue proposes adding a 7-day cooldown period to Dependabot's dependency updates. This is to mitigate supply chain attack risks by providing a window to identify malicious releases before they are automatically rolled out. The solution involves updating the repository's Dependabot configuration to mirror a similar change already implemented in the `beeware/.github` repository.

The issue discusses the desire to accept cryptocurrency donations for the project, but the maintainer is concerned about the legal, accounting, and conversion burdens. Potential solutions explored include switching fiscal hosts to Open Collective Europe, which has specific requirements, or directly providing wallet addresses, which shifts the burden to the maintainer.

This issue proposes the implementation of several new tools within Meshery's MCP (Meshery Control Plane) to enable AI assistants to query and retrieve information about infrastructure components and models. These tools will allow AI agents to search, browse, and get detailed definitions of available infrastructure building blocks, such as Kubernetes Deployments or Istio components.

This issue proposes the implementation of several tools within Meshery's AI assistant to manage Kubernetes cluster connections. These tools will enable AI agents to list, connect, disconnect, and query the health and resources of Kubernetes clusters through natural language commands, enhancing Meshery's integration capabilities.

The Kicksecure ISO fails to boot in live-amnesic USER session mode on the novacustom-v540tu hardware, causing an auto-reboot before the desktop appears. This issue is specific to the USER session, as the SYSMAINT session boots successfully on the same hardware. The problem does not occur on other tested hardware like the x230 and novacustom-nv4x_adl.

This issue reports a bug in the `smartdns` OpenWrt package (version 46.1) where it incorrectly appends CIDR notation to the LAN IP address when configuring DHCP options. This leads to invalid DNS entries for clients. The fix involves updating `smartdns` to upstream version 47.1, which resolves this by removing the CIDR notation and utilizing `uci batch` for configuration.

The watchcat package in OpenWrt 25.12.0-rc5 is failing to acknowledge ping responses when the traffic traverses a mesh network. This issue, which did not exist in previous versions, prevents watchcat from correctly detecting network connectivity, leading to false reboot triggers.

This issue requests the conversion of an existing Ubuntu community governance chart, currently in an image format on their website, into Mermaid syntax. The goal is to make the chart searchable and easier to maintain within the documentation.

The user wants to make resource attributes accessible to a logging library SDK to enrich legacy application logs. Currently, resource attributes are part of the SDK, not the API, forcing applications to depend on the SDK for this functionality. This issue proposes moving resource attributes to the API to allow logging libraries to access them without a direct SDK dependency.

This issue proposes the implementation of a comprehensive CI/CD pipeline for the `meshery-mcp-server` repository. It includes setting up automated builds, tests, linting, and multi-platform binary/Docker image releases using GoReleaser. Additionally, it calls for dependency management with Dependabot and security scanning with CodeQL and Gosec.

This issue proposes adding a recommended maximum backoff time to the OTLP specification for handling transient errors. Currently, the spec mandates exponential backoff with jitter but doesn't specify a limit, leading to potential inconsistencies across different implementations. The enhancement aims to provide clearer guidance for SIGs.

The user is experiencing a "no sound playing" bug with the Deezer desktop application on Fedora 44. They have confirmed audio is working with other applications and tried different audio outputs, but the Deezer app produces no sound. The issue might be related to Wayland/Hyprland or a specific incompatibility with Vulkan.

This issue requests comprehensive documentation for the meshery-mcp-server, including a user guide, configuration reference, and AI client integration examples. The goal is to enable new users to set up and integrate the server quickly. The implementation plan involves overhauling the README and creating new markdown files for installation, configuration, tool references, specific integrations, and development guidelines.

This issue proposes the implementation of new MCP tools to enable AI assistants to manage Meshery environments and workspaces. The tools will allow users to list, create, and switch between these entities using natural language prompts, with specific requirements for input/output formats and error handling.

This issue proposes the implementation of several "MCP Tools" within Meshery to enable AI assistants to manage infrastructure designs and patterns. These tools will allow AI agents to perform operations like listing, creating, deploying, undeploying, and deleting designs through natural language commands. The implementation will involve creating specific Go functions with JSON schema validation, structured output, and error handling.

This issue proposes exposing live infrastructure topology data from Meshery as MCP resources. This will allow AI assistants to access real-time cluster information for analysis and troubleshooting without direct tool calls. The implementation involves defining specific MCP resource URIs and ensuring they return JSON-serialized topology data with subscription support.

This issue proposes the implementation of guided workflow templates (MCP prompts) for AI assistants interacting with Meshery. These templates will provide structured guidance for common Meshery operations like deploying applications, debugging clusters, and reviewing designs, improving consistency and reducing verbosity in AI interactions.

This issue proposes the implementation of an MCP (Model Context Protocol) server within Meshery to enable AI assistants to connect and interact with Meshery's capabilities. The implementation will involve adding an MCP Go SDK dependency, creating a new server entry point, and supporting both stdio and SSE/HTTP transports, along with graceful shutdown, structured logging, and server capability advertisement.