Share Feedback
Your feedback helps us make LabID better for everyone. Whether you have ideas for improvements, questions about functionality, or suggestions for new features, we want to hear from you.
Contribute ideas & discuss features
To suggest ideas or discuss features, contact us on Slack or by email.
Join us on Slack
Chat with the community and maintainers in real-time.
Send us an email
Reach out directly to the development team.
Project Structure
LabID is organized as a collection of repositories with separated concerns. The main components are:
labid-server
The backend API and core business logic.
labid-ui
The web-based user interface.
labid-cli
The command-line interface.
labid-lib
Shared libraries and utilities.
labid-user-docs
User documentation.
Report Bugs
To report bugs, please create an issue on the relevant LabID GitLab repository. For a UI bug, please create an issue on the UI repository, and for a backend bug, please create an issue on the backend repository. If unsure, go ahead and choose either - we will be able to triage appropriately.
Please include as much detail as possible in your bug report, including steps to reproduce the issue, expected behaviour, relevant screenshots or error messages, and environment details. This will help us address the issue more efficiently.
Contribute Code
We welcome code contributions from the community. If you're planning to work on a new feature or significant change, we encourage you to discuss it with the community first. This helps ensure your contribution aligns with the project's direction and avoids duplicated effort. For smaller contributions, such as fixing documentation typos, you can go ahead and submit a pull request directly.
What makes it to the codebase?
As with many other open source projects, code contributions are reviewed by the core team before being merged into the codebase.
Long-term Collaborations & Funding
If you have funding and are interested in moving the project forward, or if you would like to establish a long-term collaboration with the development team, please contact us by email or Slack.