The translation is temporarily closed for contributions due to maintenance, please come back later.
Zen

Source string Source string

191/10000 · 191

This translation is currently locked.

English Actions
After Canonical suddenly announced `their plans to terminate support of Ubuntu Touch <https://insights.ubuntu.com/2017/04/05/growing-ubuntu-for-cloud-and-iot-rather-than-phone-and-convergence/>`_ in April of 2017, UBports and its sister projects began work on the open-source code, maintaining and expanding its possiblilities for the future.
After Canonical suddenly announced `plans to terminate support for Ubuntu Touch <https://insights.ubuntu.com/2017/04/05/growing-ubuntu-for-cloud-and-iot-rather-than-phone-and-convergence/>`_ in April of 2017, UBports and its sister projects began work on the source code; maintaining and expanding its possibilities for the future.
After Canonical suddenly announced `their plans to terminate support of Ubuntu Touch <https://insights.ubuntu.com/2017/04/05/growing-ubuntu-for-cloud-and-iot-rather-than-phone-and-convergence/>`_ in April 2017, UBports and its sister projects began work on the open-source code, maintaining and expanding its possibilities for the future.
After Canonical suddenly announced `plans to terminate support for Ubuntu Touch <https://insights.ubuntu.com/2017/04/05/growing-ubuntu-for-cloud-and-iot-rather-than-phone-and-convergence/>`_ in April of 2017, UBports and its sister projects began work on the source code; maintaining and expanding its possibilities for the future. Today, UBports is a volunteer group, formalised as a charitable foundation.
About the Documentation
Changes to the documentation are made by the UBports community. It is written in reStructuredText and converted into this readable form by `Sphinx <https://www.sphinx-doc.org/en/master/>`_, `recommonmark <http://recommonmark.readthedocs.io/en/latest/>`_, and `Read the Docs <https://readthedocs.io>`_. Start contributing by checking out the :doc:`Documentation contribution document </contribute/documentation>`.
This documentation is always improving thanks to the members of the UBports community. It is written in ReStructuredText and converted into this readable form by `Sphinx <http://www.sphinx-doc.org/en/stable/>`_, `ReCommonMark <http://recommonmark.readthedocs.io/en/latest/>`_, and `Read the Docs <https://readthedocs.io>`_. You can start contributing by checking out the :doc:`Documentation contribution document </contribute/documentation>`.
This documentation is always improving thanks to the members of the UBports community. It is written in ReStructuredText and converted into this readable form by `Sphinx <http://www.sphinx-doc.org/en/stable/>`_, `ReCommonMark <http://recommonmark.readthedocs.io/en/latest/>`_, and `Read the Docs <https://readthedocs.io>`_. You can start contributing by checking out the :doc:`Documentation intro </contribute/documentation>`.
All documents are licensed under the Creative Commons Attribution ShareAlike 4.0 (`CC-BY-SA 4.0 <https://creativecommons.org/licenses/by-sa/4.0/>`_) license. Please give attribution to "The UBports Community".
All documents are licensed Creative Commons Attribution ShareAlike 4.0 (`CC-BY-SA 4.0 <https://creativecommons.org/licenses/by-sa/4.0/>`_). Please give attribution to "The UBports Community".
Attribution
This documentation was heavily modeled after the `Godot Engine's Documentation <http://docs.godotengine.org/en/stable/>`_, attribution to Juan Linietsky, Ariel Manzur and the Godot community.
This documentation was heavily modeled after the `Godot Engine's Documentation <https://docs.godotengine.org/en/stable/>`_, by Juan Linietsky, Ariel Manzur and the Godot community.
Branch-naming convention
Our branch-naming conventions ensure that software can be built by our CI and tested easily by other developers.
Our branch-naming convention ensures software can be built by our CI and tested easily by other developers.
Every Git repository's README file should state which branch-naming convention is used and any deviations from the norm.
Every Git repository's README file should state which branch-naming convention is used and possible deviations from the norm.
Click-Packages
Software exclusively distributed as a click-package (and not also as a DEB) only uses one ``master`` branch that is protected. Separate temporary development branches with arbitrary descriptive names can be created and merged into master when the time comes. Ideally Git tags or GitHub releases should be used to mark and archive milestones in the development history.
Software that is exclusively distributed as a click-package (and not also as a deb) only uses one ``master`` branch that is protected. Separate temporary development branches with arbitrary descriptive names can be created and merged into master when the time comes. For marking and archiving milestones in development history, ideally Git tags or GitHub releases should be used.

Loading…

User avatar None

Source string added

  1. UBports
  2. docs.ubports.com - about page
  3. English
This documentation was heavily modeled after the `Godot Engine's Documentation <http://docs.godotengine.org/en/stable/>`_, attribution to Juan Linietsky, Ariel Manzur and the Godot community.
6 months ago
Browse all string changes

Things to check

Multiple failing checks

Following checks are failing:
Consecutive duplicated words: Albanian, Chinese (Simplified)

Reset

Glossary

English English
No related strings found in the glossary.

String information

Flags
read-only
Source string location
../../about/introduction.rst:23
String age
6 months ago
Last updated
6 months ago
Source string age
6 months ago
Translation file
locales/pot/about.pot, string 10