Contributing

The Fedora Robotics SIG welcomes contributions from anyone interested in bringing robotics software to Fedora. This page explains how to get started and where to help.

Getting Started

  1. Create a Fedora Account if one does not already exist.

  2. Sign the Fedora Project Contributor Agreement (FPCA) through the Fedora Account settings.

  3. Join the Robotics SIG Matrix channel to introduce yourself and find current work.

Ways to Contribute

RPM Packaging

The SIG maintains Fedora packages that robotics frameworks depend on. A Fedora Bugzilla ticket tracks blocker packaging issues.

Open packaging tasks in GitLab use the packaging label: packaging work items.

Image Building

The SIG builds and publishes container images for robotics workloads. Container-related tasks use the container label: container work items.

All image manifests live under the images sub-group in GitLab.

Demos and Showcases

Demo projects showing how to use ROS2 on Fedora live in the src sub-group. New demos, bug fixes, and documentation improvements to existing demos are all welcome.

Documentation

This documentation site is built with Antora from AsciiDoc source files. The source repository is fedora-docs on GitLab.

To preview changes locally:

git clone https://gitlab.com/fedora/sigs/robotics/fedora-docs.git
cd fedora-docs
./docsbuilder.sh -p

The preview is available at http://localhost:8080. Stop the preview with ./docsbuilder.sh -k.

The local preview requires Podman. Install it on Fedora with sudo dnf install podman.

Communication

The SIG uses the following channels:

  • Matrix is the primary communication channel.

  • Fedora Discussion hosts longer-form questions and discussions under the robotics-sig tag.

  • The SIG meets every other Thursday at 4PM UTC. Check the Fedora SIG calendar for dates.

  • Meeting notes are published in GitLab after each session.

Submitting Changes

All SIG repositories use GitLab for version control and code review.

  1. Fork the repository on GitLab.

  2. Create a branch for the change.

  3. Submit a merge request against the main branch.

  4. A SIG member reviews and merges the change.

Licensing

All documentation in this project is licensed under CC-BY-SA-4.0. Contributions to documentation are accepted under the same license.