@jezek as doniks said, compiling the app and perhaps fixing a bug would be a good start to get to know the code a little bit. (Now step 3 a little more detailed.) Then if you're sure you want to maintain it, you may state that here: https://github.com/ubports/messaging-app/issues/1 :) Then you'll likely get the permissions to commit on branches of the messaging-app repository and manage the issues. The work flow then would be roughly: Assign the bug, lets assume to yourself, develop your fix on a branch of the official messaging repository, eventually create a beta release on github (s.t. qa team has something to work with), make a pull request. Once thats all done someone will publish the new release in the openstore. Beside that you'll moderate the discussion on the issues on github...
@elastic don't worry, but I don't know how to get involved into the "community management", I was just browsing through the app repos and collecting the "needs maintainer" issues :-)
@Einstein212 Yes I know how that feels :) I was also completely new to qml, when I was starting hacking around in the calendar... And it still feels like: "Uuuhmmm I don't really know what I'm doing..." ;-) And it also took me some reasonably amount of time to at least understand whats going on a little bit.
@markalexa at the ubports gettogether in Munich @TimSueberkrueb held a presentation on that topic: https://github.com/timsueberkrueb/ubports-gettogether/blob/master/timsueberkrueb/pyotherside/presentation.md
Actually this is quite doable. Not as a native application however (though that itself IS possible using the Discord SDK, considering that there is a wonderful third-party UWP Discord application for Windows), but using the webapp-container with the user-agent string of the latest Chrome or Chromium release, will cause the webapp to request permission for Microphone and allow VOIP calling under Ubuntu Touch. It will not however, allow PTT (as PTT requires a native application).
Just tried out linking the Ubuntu Signal app (https://signal.org/blog/standalone-signal-desktop/) with Ubuntu Touch Signal app - works like a charm!
Thanks a lot, Aaron for taking over maintenance of and adding new features to the Signal app!
Only hiccup so far: During my first tests messages I wrote on the desktop did not all make it over to the mobile app.
@hudson when creating a new project, which framework did you choose?
Also, you can try the solution that error message suggested (use the --force-missing-framework option too) but the relevant point is you have to know for which framework you are developing ;)
I‘ll start with a Ubuntu touch client for Asteroid OS in the next weeks. I‘ve wrote with FlorentRevest the Initiator and developer of Asteroid OS. He provides a repository with a platform independent C++ Qt library for writing Asteroid clients https://github.com/AsteroidOS/libasteroid. There is also an cli example. Currently he is working on a sailfish os client https://github.com/AsteroidOS/starfish. He is paying attention to be compatible as much as possible with Ubuntu touch. I’ll create a fork of the sailfish client. I should be able to use 90 % of this code. The major part would be the rewrite of the qml code for Ubuntu touch.
Also note it works a little differently now in the updated script. It will create an $HOME/UBports directory on the host which it will mount as the $HOME in the container. It also symlinks any ssh keys you might have on the host and copies over the .gitconfig. This way it keeps the container home seperate from host but can easily be accessed on the host. If you want to change the directory used for the container you can do