Ich würde gere mitmachen

[mschnell1]

...I'd like to contribute ...

I am experienced in doing embedded software since 40 Years.

I am used to use git

Mostly I did C and some C++, but since a year I am exclusively on Rust, which is not easy to learn, but beats C++ in all aspects.

I also did some Linux projects. I do have a Raspberry Pi for testing (or I would buy another one).

In the moment I started a project on Pico 2. Same supposedly would be very well suited for EOS, if you don't want to engage a standard OS. (It only costs 5 €.)

How to get together ?

==============================================================================

Ich habe 40 Jahre Erfahrung als embedded Programmierer.

Ich mit git umgehen.

Ich habe meist in C und ab und zu in C++ programmiert, seit einem Jahr aber komplett auf Rust umgestellt, das nicht ganz leicht zu lernen ist, dann aber C++ in allen Bereichen schlägt.

Ich habe auch schon mit Linux gearbeitet. habe auch einen RasPi zum Testen (oder würde noch einen anschaffen)

Momentan bereite ich ein Projekt mit einem Pico 2 vor. Der wäre vermutlich sehr gut geeignet für EOS, wenn man kein reguläres Betriebssystem bemühen will. (koste nur 5Euro oder so.)

Wie kommen wir zusammen ?

(Wäre English her besser ?)

[Lasall]

Awesome! You can get started with the setup at https://github.com/Akkudoktor-EOS/EOS/blob/main/CONTRIBUTING.md#setup-development-environment . Currently development is done in the branch feature/config-overhaul with some architectural redesign compared to the main branch. #275 would be a small issue to get started. Otherwise a lot of documentation is required (maybe not so easy to get started), the release plan can be seen in the wiki: https://github.com/Akkudoktor-EOS/EOS/wiki/Roadmap-and-Vision#milestone-010

In the wiki there is also some (currently very limited and incomplete) information how to setup the system with the feature branch https://github.com/Akkudoktor-EOS/EOS/wiki/First-Steps-(Branch-feature-config%E2%80%90overhaul). The best documentation is actually the code (sphynx api generation: make docs) and the swagger documentation (make run-dev then go to /docs endpoint).

Please ask any questions or make PRs to help with anything (documentation, etc.).

[mschnell1]

Asking questions here ?
Creating new topics ?

I normally use VSCode to do development (C++ and Rust)

I normally do documentation in ASCIIDoc, so it can be easily edited and previewed in VSCode and distributed in PDF and HTML.

What are the desired targets to have the software run on ? IMHO it would be nice to have it runnable at least on PC and Linux (using the appropriate OS API) and on PICO 2. Here AFAIK, FreeRTOS is possible (with C++), but for threads I just used Rust embassy and the async/await pattern.

Regarding "embedded" use of the software, IMHO it should be "headless" and a user interface for monitoring and configuration should be available via a built-in Web server, so that you just need to access it via TCP-IP using a web browser.

(Exactly this is what I am researching right now in the Rust world, where the GUI issue is not really "standard" right now.)

[Lasall]

However you see fit. Maybe small things relating to your setup here and general/bigger ideas as a new discussion. Bugs you notice as issue.

[mschnell1]

OK. I git-cloned the project and see that it is nicely opened in VSCode.
I also see that it's Python, which I did some small projects in, but do not like that much (for it's lacking safety / error immunity). OTOH with Python there are many stable open source libraries you can make use of....

Is there a description of the structure of the project to get started with ?

[Lasall]

The most description of structure you can get is the build the documentation: make docs and then access it at build/docs/html/index.html . There you can navigate in the left pane to EOS API to get a class overview.

[mschnell1]

when I am in VScode bash (on Windows) I don't have a command "make". (I used that installation for Rust development, that does not use make.)
Very obviously I need to take care of some prerequisites....
(I did not yet find anything regarding using VSCode in Windows for working on EOS)

I could install Code in a virtual machine running Linux. Is that recommended ?

[mschnell1]

In Linux I was able to git clone EOS and then do make docs.

Then I was able to install the prerequisites in in Windows to be accessible in VSCode.

[mschnell1]

I also can start the server using the instruction in the documentation,but I don't get a connection @ http://0.0.0.0:8503 or @ http://127.0.0.1:8503
In Linux I can start the server and do get a web page @ http://0.0.0.0:8503 .

[NormannK]

try localhost:8503

[mschnell1]

Yep that works !
Thanks !!!
So I understand that make is not necessary with Python.

[mschnell1]

So theoretically I could do tome testing etc ...

[NormannK]

yes you don't need make to tests with python and VSCode. So far my attempts to get make running in VSCode were unsuccessful i also use a linux dist for that.
but regarding that localhost you could make your first issue.