Skip to content

fhstp/ergo4all

Repository files navigation

ergo4all

Funded within the Projektfonds Arbeit 4.0 Programme Project partners
The logo of the AK Lower Austria The logo of the TU Vienna The logo of the UAS St. Pölten

The main repository for the Ergo4All project.

Checkout the projects Changelog to see what's new.

Project structure

This is a monorepo/workspace project with the following parts.

Name Description
ergo4all The main Ergo4All app
pose_tester A testing app for pose detection and scoring
common Common dart logic
common_ui Common ui logic
custom_locale Logic for managing a custom locale setting
pose_detect Logic to extract poses from images
pose_vis UI logic for visualizing poses

License

This repository uses dual licensing.

Software (code)

All source code in this repository is licensed under the MIT License with Commons Clause. This means the software is free to use, modify, and distribute for non-commercial purposes. However, you may not sell the software or provide it as part of a commercial service or paid support offering.

See LICENSE_SOFTWARE for details.

Content and Media

All non-code assets (i.e., texts, images, branding, logos, and other) are licensed under the Creative Commons Attribution–NonCommercial–NoDerivatives 4.0 International (CC BY-NC-ND 4.0) license. You may share these assets with attribution, but you may not modify or use them commercially.

See LICENSE_CONTENT for details.

CC BY-ND 4.0 cc-by-nd-shield

If you are interested in alternative licenses, please contact the project team.

Develop

To get started developing, install Flutter, preferably using fvm. Then clone the repo and run fvm use inside the project directory to setup the correct flutter sdk.

It is recommended to use VSCode with the recommended extensions.

Commit conventions

This project uses conventional commits, specifically the Angular style. It is used by semantic-release for automated releases.

We use the following commit types:

type description release
feat A new feature. A user can now do something they could not before. Also use this when dropping a feature, but in that case include the BREAKING text. minor or major if breaking
fix A bug fix. Something that was broken is now not. patch
refactor Internal change to code logic which has no effect on users none
style A purely stylistic / formatting change to code none
docs A change to some documentation item, such as readme or dart doc none
deps Made a change to installed dependencies, such as updating none
misc A change which fits into none of the above categories none

We also use scopes matching the name of the affected app or package. If a change affects multiple scopes, then omit it.

Contributors

AlinaGodun Alina Godun ML and Visualization Development
anasoftwareanddataengineer Ana Vesic UX conceptualisation, initial data visualisation concepts
kaiseran99 Andreas Kaiser App development
RiinaXoXo Carina Stoiber UI/UX
ukarfs David Kostolani AI model architecture and development roadmap
comradevanti Ramon Brullo App development
SantiagoCalvo Santiago Calvo App development
ThiccWitch Vivian Seidl UI/UX and Visualizations