I understand that this information is useful - but I would advise against writing specific versions into the wiki. Because they would get outdated quickly. But instead we can link to where one can look up the versions, possibly direct links to the package search to make it easy like I did above.
However, I am not sure where the best place would be to add the information. Everybody can register in the wiki and write to it, it only takes a few seconds to set up an account. How about you try to add the information where you think it fits in?
i am getting ready to help this project with my knowledge and time ( and brought a nexus 5x waiting to arrive)
first i thought that all the packages will be outdated but it is pretty much uptodate .( ubports qt version i think is 5.5).
i will open an account in wiki and add some information there.here are some i want to improve .
add toolkit information as that is very important for the developer.
add some more tips to take most out of pmOS as portable computer lover.
add a tutorial to setup vnc .(i think it is important)
suggest some information for newcomers . what device to get, what DE to chose etc.
and some works in user space apps.
making a keyboard with qt .
i made some app for touch based apps .now working to add gestures in some apps.
i was thinking about the settings app for pmOS.but don't know much about kernel and low level things.
an app launcher with touch support.( working on progress) ... and many exciting things.
i have some more question .
what is the to-dos and future of os? any page related to this?
what pmOS devlopers think about convergence ?
what is the meaning of that "Put the battery out of your device when it is turned off. " in wiki page.i think there should be more information about that for normal users.
is pmOS is build( packages , kernel ) in my pc then make an image ?
will the armhf packages will work on aarch64 ?
MOST IMPORTANT , support for flatpack,snap and Appimage coming?
any gui front-end for package management?
what file system will be installed after flash ?? and what other filesystem is ablable for flashing ?
i will open an account in wiki and add some information there.
Awesome! Do not take this the wrong way, but please have a look at the English Punctuation Rules first (no space before full stops and question marks, one space after). It's important for the wiki, so we have consistent and well readable text over there.
here are some i want to improve .
The list sounds good.
making a keyboard with qt .
There's already qt5-qtvirtualkeyboard.
an app launcher with touch support.( working on progress) ... and many exciting things.
What would be the benefit of your app launcher vs. the existing ones? Just saying, existing UIs need any help they can get as well. It's easier to get anywhere when working together with existing communities instead of creating many small, but unfinished UIs. Consider Plasma Mobile, for example: https://www.plasma-mobile.org/findyourway/
what is the to-dos and future of os? any page related to this?
postmarketOS is a true Linux distribution, so in theory you should be able to connect your keyboard and a monitor, and then you turned your phone into a PC. (That is what convergence is about, right?) However, there are no drivers for connecting a monitor to phones that run on postmarketOS - AFAIK they all depend on proprietary Android userspace drivers.
what is the meaning of that "Put the battery out of your device when it is turned off. " in wiki page.i think there should be more information about that for normal users.
Which wiki page exactly?
is pmOS is build( packages , kernel ) in my pc then make an image ?
You build the rootfs image on your PC with binary packages from the postmarketOS binary repository. Missing packages get built locally. But usually the repo is up-to-date. Building packages locally is useful for development.
The kernel is built in a package, so it works the same.
will the armhf packages will work on aarch64 ?
Yes, but why not use all CPU instructions of aarch64 and have faster binaries?
MOST IMPORTANT , support for flatpack,snap and Appimage coming?
Nobody worked on this yet, and it's questionable how useful that would be. Even if we supported that, it would not be compatible with existing snaps/flatpacks etc, because the binaries in these are linked against the glibc (GNU libc), not against musl libc.
One can also argue, that these 3rd party packages open up the gates for low quality and possibly harmful and/or proprietary applications. You don't have a package maintainer in-between, which at least tries to make sure that there is nothing harmful in the applications and that they work properly on postmarketOS. I see this as an advantage of Linux distributions over App Shops. After all, we would not want to have apps that track us and show us advertisements all the time, right? See also: http://kmkeen.com/maintainers-matter/
It's important for the wiki, so we have consistent and well readable text over there.
don't worry, i wrote that in hurry.
There's already qt5-qtvirtualkeyboard.
but it is not an app, don't have proper UX.(am i sure? don't know). and it is based on qml. and qml is not fast as c++.
What would be the benefit of your app launcher vs. the existing ones?
i think you will like and understand the difference. i just need to fix some small issues.
i mean by convergence is in mobile screen apps in mobile view and touch friendly and when connect to big screen app will move to desktop view for apps.
i don't like the KDE. also postmarketOS for me is like a full desktop. i don't need the call,sms etc. i am into handheld device with linux, like this one. but it is expensive.
i want a desktop os with touch support in linux.not another android or iso knock off.you can cheack out some apps here. i don't want t hurt anyones love with android or plasma, just shear my view of os for productivity.
is pmOS is build( packages , kernel ) in my pc then make an image ?
i asked ,because i saw some issues related to gcc8.00 ,as my distro (arch) is always in uptodate version.
will the appimage run? as it is not related to glibc.
this going off topic. lets come to work.
add an page for future and to-dos of this project.
i will add the topic i asked here in the wiki page .like
"will the armhf packages will work on aarch64 ?"
"support for flatpack,snap and Appimage coming?"
"what file system will be installed after flash ??"
"add where to find the packaged apps."
"pmos is based on Alpine Edge,add also the change in future"
i want a desktop os with touch support in linux.not another android or iso knock off.you can cheack out some apps here. i don't want t hurt anyones love with android or plasma, just shear my view of os for productivity.
Well, if you like, then go ahead and try your desktop on postmarketOS. You can also run postmarketOS in QEMU if you don't want to do a bare-metal installation.
will the appimage run? as it is not related to glibc.
I don't have any experience with appimage, you can try it out. I'd highly recommend going with native packages though, it is easy to create Alpine/postmarketOS packages:
https://wiki.postmarketos.org/wiki/Create_a_package
Thanks for extending the wiki. Please don't add "not sure" listings in the FAQ, we want to answer questions there and not leave the reader with more uncertainty, right?
Also I found some entries hard to read and rewrote them (e.g. "Is postmarketOS build (packages ,kernel) in my system then make an image?" -> "Are all postmarketOS packages and the kernel built locally when creating an installation image?"). At least one entry had wrong wiki syntax and did not display the link right (The package build recipes (APKBUILDs) are in the [ https://gitlab.com/postmarketOS/pmaports/ pmaports] repository.). Stuff like that happens, but please pay a lot more attention to quality and have a look at the preview before submitting changes.
I would welcome this not only in the wiki, but also in posts in issues. It makes it a lot easier to communicate with one another.
@MYEUHD: thanks for your clean up!
add an page for future and to-dos of this project.
We want to put out a blog post about that after we have migrated our binary repository to sr.ht (see the vision issue I've mentioned earlier). This would also be the right place to discuss it, when you want to contribute ideas to that vision.
So it seems that all questions are answered now, closing this issue.