TeX good first issues

This is a community discussion thread for users to request new language translations for a project. Users are instructed to first search for their desired language and upvote existing requests, or create a new comment with their language if it's not already listed.

This GitHub issue outlines a comprehensive to-do list for the "2026 release" of a document, likely an orientation guide for new students. It includes tasks ranging from content updates and proofreading to technical Git operations and checking external information like opening hours and course details.

This issue proposes a discussion to design new Human-Robot Interaction (HRI) tasks for RoboCup that are more challenging and impactful for research. The goal is to move beyond simple dialogues and incorporate multi-modal interactions, social cues, and adaptive strategies, addressing current limitations in robot attentiveness and interaction fluidity.

This issue seeks to establish community norms regarding development workflows, specifically whether contributors should use forks or branches within the main repository. The goal is to discuss and decide on a preferred approach, then update documentation and educate new members accordingly.

This issue highlights a lack of user understanding regarding proper colcon workspace setup, specifically concerning the `colcon_defaults.yaml` file and colon mixins. The goal is to improve documentation or provide clearer guidance to address this common confusion.

This issue describes work towards a specific research goal (MAIS-O16) by implementing a proof checker and a cooperating "FairBot_k". The current progress involves a working proof checker, and the next steps are to implement the FairBot and determine a cooperation threshold. The complexity arises from the potential for large proof sizes with the current system.

The `run_demo.py` script duplicates significant functionality already present in `FewShotPrompter`. This leads to maintenance issues as changes need to be applied in two places. The proposed fix is to refactor `run_demo.py` to be a simple CLI wrapper that utilizes the existing `FewShotPrompter` class, eliminating the redundant code.

This issue reports a broken link within the Turing Way documentation. The link, intended to point to a Jupyter Book page, now leads to a nonexistent URL. This is a straightforward bug fix requiring the correction of a single hyperlink.

This issue proposes adding support for linking personal profiles on external academic platforms like ORCID, Google Scholar, and DBLP to user profiles on the DICE teams page. This would allow researchers to connect their profiles and make them more discoverable for others within and outside the team. The proposed solutions involve using RDF properties or `owl:sameAs` for data representation and icons for web page rendering.

The user is requesting documentation and concrete examples for a more advanced `launch.json` configuration. They want to launch specific subsets of modules within a project, a capability they previously achieved with the `cwd` parameter but is no longer supported in the current configuration language. The user is looking for ways to achieve this controlled launching from the top-level `launch.json`.

A notebook fails during CI builds because it attempts to read a CSV file from a raw GitHub URL, which is being rate-limited (HTTP 429). The CSV file is already vendored within the repository, so the fix involves changing the code to read the local file instead of fetching it over the network. A similar issue in a parallel notebook should also be addressed.

This issue involves replacing deprecated `tic`/`toc` timer functions with the `qe.Timer` context manager in the `kesten_processes.md` lecture. The change is straightforward as the existing code uses `tic`/`toc` pairs to time single code blocks and print the elapsed time, which directly maps to the functionality of `qe.Timer`.

Embedded videos on the "Online Collaboration Cafe" page are not displaying, showing a blank box instead of the video player. This could be due to a broken link or an incorrect embed directive. The expected behavior is for the video player to be visible and functional on the page.