Where can i highlight spelling errors on app pages on the OpenStore website?

Opolork

@Moem I see, thanks.

Opolork

Hi. I created a gitlab.com account but am not sure about the setting up of an SSH key in order for me to do a Merge Request on https://open-store.io/app/trolly.alaskalinuxuser. Can someone please go thru this step-by-step?

johndoe

Hello @Opolork , as Bolly already pointed out, you can contact the developers over their gitlab (or github) accounts.
For the spelling error, you could open an issue like this:
1)

2)

3)

Please describe what the issue is ("Hello, I saw following spelling error at the description of the app in the open store...") and when the developer has time for it, he will maybe correct it. You do not need to set up an SSH key for this.

For directly suggesting a change to the source code, you can start a merge request. The description of the app in the open store is not part of the source code, so it can not be changed with a merge request. But should you see any spelling errors inside an app, you can most likely correct them with a merge request.
For a merge request you need to fork (make a copy with your own changes) the project first. Should you click on a file (for example po/es.po to change the Spanish translation) in the gitlab repository and than click on Edit > Edit single file at the top right, gitlab will automatically ask you, if you want to fork the project. Than you can edit your fork and make a merge request to the original repository. I will not explain it further, because I do not think that this is what you want to do here.

Please be aware that the translation for the core apps is done over a translation dashboard, so you should not make translation merge requests for them (https://docs.ubports.com/no/latest/contribute/translations.html#how-to).

For using SSH functionalities of git, you can add an SSH key to your gitlab profile. I will also not explain it further, because I do not think that this is what you want to do here. I think it is not even necessary for making a merge request. And I think you should even be able to push and pull your own projects without an SSH key. Here is some gitlab specific documentation about it, should you be interested: https://docs.gitlab.com/user/ssh/

TL;DR: Just open an issue. You do not need to make a merge request or to set up an SSH key.

Opolork

Hi @johndoe. Thank you. I'm not a coder so being able to simply contact the dev on GitLab in a straightforward way is just what I need.

Opolork

Done!

https://gitlab.com/alaskalinuxuser/trolly/-/issues

Opolork

Perhaps https://gitlab.com/theopenstore/openstore-meta/issues is also an option.

Edit: Perhaps not. It says "This project is archived. Its data is read-only." on that webpage.
It seems Telegram is the only way to contact the folks at Open Store, but I don't use Telegram. I wish good old fashioned email was always an option for contacting others.

Bolly

@Opolork No, that's not an option. The OpenStore maintainer has nothing to do with the text that each programmer puts in their applications. Besides, you had to open an issue in each application, not both in the same application.

Opolork

@Bolly said in Where can i highlight spelling errors on app pages on the OpenStore website?:

@Opolork No, that's not an option. The OpenStore maintainer has nothing to do with the text that each programmer puts in their applications.

Ok, understood.

Opolork

@Bolly said in Where can i highlight spelling errors on app pages on the OpenStore website?:

Besides, you had to open an issue in each application, not both in the same application.

Thanks for the heads up, I overlooked that mistake. I'll get around to fixing it.

Edit: Done!

CiberSheep

@Opolork the issue tracker is on the top level:

https://gitlab.com/groups/theopenstore/-/issues

As Bolly stated, each app has its own maintainer. It is a bit of work, as you have to contact each maintainer, but we will be more than happy to fix the spelling mistakes. Opening an issue (again, as stated before) might be the easiest way at least for now... Oh, and thank you