|
|
The stack that Plasma Mobile is built on is split into many repositories, which can make reporting issues daunting for new contributors.
|
|
|
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, so contributors can move the issue to the corresponding repository: https://invent.kde.org/plasma/plasma-mobile/-/issues
|
|
|
|
|
|
Issues that specifically pertain to the **Plasma Mobile shell** should be filed in the [GitLab issues](https://invent.kde.org/plasma/plasma-mobile/-/issues) page for the repository.
|
|
|
|
|
|
Applications that are released under the **Plasma Mobile Gear** release cycle generally also use GitLab issues for their corresponding repositories for issue reporting and tracking.
|
|
|
Applications that are released under the **Plasma Mobile Gear** release cycle generally also use GitLab issues for their [corresponding repositories](https://invent.kde.org/plasma-mobile) for issue reporting and tracking.
|
|
|
|
|
|
Generally, all **other** frameworks and applications will be using [KDE's Bugzilla instance](https://bugs.kde.org/) for issue tracking.
|
|
|
|
... | ... | |