|
|
TLDR:
|
|
|
- **General user issues** [plasma-mobile product on bugzilla](https://bugs.kde.org/describecomponents.cgi?product=plasma-mobile)
|
|
|
- **General issue tracker (for developers)** [teams/plasma-mobile/issues on GitLab](https://invent.kde.org/teams/plasma-mobile/issues/-/issues)
|
|
|
- **Shell issue tracker (for developers)** [plasma/plasma-mobile/issues on GitLab](https://invent.kde.org/plasma/plasma-mobile/-/issues)
|
|
|
|
|
|
The stack that Plasma Mobile is built on is split into many repositories, which can make it hard for new contributors to decide what issue belongs where.
|
|
|
|
|
|
Your best bet would be to report issues to our **general issue tracker** first, over at the [plasma-mobile product on bugzilla](https://bugs.kde.org/describecomponents.cgi?product=plasma-mobile).
|
|
|
|
|
|
You may also report to our **GitLab general issue tracker** as well at [teams/plasma-mobile/issues](https://invent.kde.org/teams/plasma-mobile/issues/-/issues).
|
|
|
|
|
|
If there is a bug for the shell, it can be reported at [plasma/plasma-mobile/issues](https://invent.kde.org/plasma/plasma-mobile/-/issues).
|
|
|
|
|
|
If the bug is for a specific application or framework, find the respective product on [bugzilla](https://bugs.kde.org/describecomponents.cgi) or search on this GitLab instance for the project.
|
|
|
|
|
|
Some Plasma Mobile Gear applications **do not have a bugzilla category**, and so you will have to file an issue on Gitlab on the project. You can find the repos at [invent.kde.org/plasma-mobile](https://invent.kde.org/plasma-mobile).
|
... | ... | |