Skip to main content
This document provides an introduction to project management and an overview of processes for the AlpaSim project.

​
Project Overview

​
Philosophy

AlpaSim is meant to be an open-source, best-effort research project. The processes for maintaining the project are designed to allow for rapid development and iteration while maintaining a reasonable level of quality.

​
Constraints

The project is maintained by a small team with limited time and resources. Therefore, the processes are designed to minimize overhead and maximize efficiency.

​
Leadership

Project Lead

Maximilian IglProgram Manager/PIC, Primary Researcher, and Owner

​
Security

PLC Security PIC

Michael Watson

​
Core Team

​
Technical Leadership

  • Michal Tyszkiewicz
  • Michael Watson
  • Sanja Fidler
  • Zan Gojcic
  • Boris Ivanovic
  • Marco Pavone

​
Project Management

  • Matt Cragun

​
Contributors by Area

​
Architecture and Infrastructure

  • Michal Tyszkiewicz
  • Maximilian Igl
  • Aaron Smith
  • Michal Tyszkiewicz
  • Michael Watson
  • Qi Wu (SLURM deployment)
  • Le Zhang (Data management)
  • Maximilian Igl
  • Aaron Smith
  • Ellie Tanimura
  • Michal Tyszkiewicz
  • Michael Watson
  • Maximilian Igl
  • Aaron Smith

​
Open Source and Quality

  • Guillermo Garcia Cobo
  • Maximilian Igl
  • Peter Karkus
  • Ellie Tanimura
  • Michael Watson
  • Guillermo Garcia Cobo
  • Peter Karkus
  • Ellie Tanimura

​
Data and Pipeline

  • Riccardo de Lutio
  • Janick Martinez
  • Le Zhang

​
Service Modules

  • Maximilian Igl
  • Peter Karkus
  • Michal Tyszkiewicz
  • Yulong Cao
  • Maximilian Igl
  • Michael Watson
  • Riccardo de Lutio
  • Maximilian Igl
  • Boris Ivanovic

​
Additional Acknowledgements

Additional contributions from:
  • Fabian Barajas
  • Kashyap Chitta
  • Ankit Gupta
  • Laura Leal-Taixe
  • Nicole Yang

​
Software Development Process

​
Branching Strategy

1

Main Branch

main - Primary branch, requires fast-forward merges only
2

Feature Branches

Created from main for new work
3

Branch Naming

Use descriptive names (e.g., dev/<username>/<feature-name>)

​
Rebasing

This repository requires fast-forward merges only to maintain a linear commit history. If your branch falls behind main, you must rebase.
Force pushes are expected and necessary when rebasing due to the linear history requirement.

​
Merge Request Process

Merge/Pull requests are required for all changes to the codebase. Templates are provided to ensure consistency and completeness.

​
Release Process

Versioning is automated by the CICD pipeline to ensure that versions remain uniquely identified. There is no plan to develop process for qualification/certification of releases at this time.
Updates will be rolled out continuously via the main branch.

​
Contact

For questions about project governance or to report issues, please:
  • Open an issue on the GitHub repository
  • Contact the project lead: Maximilian Igl
  • For security concerns, see the Security Policy

​
Next Steps

Contributing

Learn how to contribute to AlpaSim

Security

Report security vulnerabilities

Build docs developers (and LLMs) love

Get started for freeTalk to us