Askbot: Should the Sailfish OS id be included as part of the each user's profile information? [not relevant]

Not sure what you mean. Do you want it to update automatically each time we make a post, and what then when people use PCs to comment? Or should we update profiles manually, and won't this just postpone the problem to people having outdated info when they release updates?

I'm not against the idea, but I'm unsure how you want it implemented.

I am not sure if it is a problem at the moment, but I agree it should be adressed soon - as long as there is only one device running Jolla is available and updates run as smooth as they did for me in the past months, probably everyone has a Jolla and the most current Sailfish build. As another device gets released or ANdroid devices officially are enabled to run SailfishOS we need something like device and OS version.

@orjans - My original idea was to have SF id as field in the tjc user profile and show it to everyone as shown it picture of the question.

I guess it would be possible to make such information available via Jolla account, but then it would subject to privacy and how such information will be allowed to be used.

At first it could be just field in user profile and responsibility of maintaining it would per each user.

By having this kind of parameter in user profile would indicate the used SF version as it is requested by many comments of the posts.

Showing the version as it can be found in the Jolla account would not make sense. Let's say I report a problem on 1.0.2.5, later update to 1.0.3.8. Then 1.0.3.8 would be shown although the problem is on 1.0.2.5. Maybe the current version info from the profile could be copied into the question as it is raised. But I think having a field to manually mark the version related to the raised question / problem is enough.

I support the idea of a mandatory field for the Software-Version and maybe in future as well the Hardware-Version. It's just common sense. Otherwise discussions may totally meaningless as problems already been solved in a more recent SW release. Or problems are only related to a specific HW revision.