jami-docs/locales/de/LC_MESSAGES/contribute.po

532 lines
19 KiB
Plaintext

# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018-2024 Savoir-faire Linux Inc. and contributors
# This file is distributed under the same license as the Jami package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# savoirfairelinux <support@savoirfairelinux.com>, 2023
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Jami\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-12-10 03:53+0000\n"
"PO-Revision-Date: 2022-09-14 17:52+0000\n"
"Last-Translator: savoirfairelinux <support@savoirfairelinux.com>, 2023\n"
"Language-Team: German (https://app.transifex.com/savoirfairelinux/teams/49466/de/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: de\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../../contribute.rst:3
msgid "Contribute to Jami"
msgstr "Mitwirken Sie bei Jami"
#: ../../../contribute.rst:5
msgid ""
"Contributions to Jami are always welcome and are much appreciated. There are"
" many ways to contribute to Jami, including reporting bugs and issues, "
"contributing code, helping package and maintain Jami for your GNU/Linux "
"distribution or other operating system, as well as contributing to these "
"very docs themselves."
msgstr ""
"Beiträge zu Jami sind immer willkommen und werden sehr geschätzt. Es gibt "
"viele Möglichkeiten, zu Jami beizutragen, einschließlich Fehler und Probleme"
" zu melden, Code zu beitragen, Jami für Ihre GNU/Linux-Distribution oder "
"andere Betriebssysteme zu verpacken und zu warten, sowie zu diesen Dokumente"
" selbst beizutragen."
#: ../../../contribute.rst:11
msgid "Please see below for how to get started contributing to Jami!"
msgstr ""
"Bitte sehen Sie unten, wie Sie mit der Arbeit bei Jami beginnen können!"
#: ../../../contribute.rst:18
msgid "Reporting bugs and issues"
msgstr "Berichterstattung über Fehler und Probleme"
#: ../../../contribute.rst:20
msgid ""
"Please see the :doc:`user/bug-report-guide` for step-by-step instructions on"
" how to report bugs and issues you encounter in Jami."
msgstr ""
"Bitte lesen Sie im :doc:`user/bug-report-guide` die Schritt-für-Schritt-"
"Anweisungen zur Berichterstattung von Fehlern und Problemen, die Sie in Jami"
" auftreten."
#: ../../../contribute.rst:24
msgid "Contributing code"
msgstr "Beitragscode"
#: ../../../contribute.rst:26
msgid ""
"If you want to start to contribute to Jami, you can start by looking good "
"first issues at: "
"https://git.jami.net/groups/savoirfairelinux/-/issues/?sort=created_date&state=opened&label_name%5B%5D=good-"
"first-issue"
msgstr ""
#: ../../../contribute.rst:29
msgid ""
"You can contact developers directly by adding a comment on the ticket you "
"want to start with. They will be able to guide you through the process."
msgstr ""
#: ../../../contribute.rst:32
msgid ""
"At some point, you will need to push a patch on https://review.jami.net. For"
" more information on how to do this, please refer to the "
":doc:`developer/working-with-gerrit` guide."
msgstr ""
#: ../../../contribute.rst:36
msgid "Commit message guidelines"
msgstr ""
#: ../../../contribute.rst:38
msgid ""
"When you submit a patch to Jami, please follow these guidelines for your "
"commit messages:"
msgstr ""
#: ../../../contribute.rst:40
msgid ""
"The first line should include the component or scope of the change, followed"
" by a short summary of the change in the imperative mood (e.g. \"add new "
"function\", \"fix bug\", \"update documentation\")."
msgstr ""
#: ../../../contribute.rst:41
msgid ""
"The subject can use the capitalization of the component or scope, but the "
"rest of the title should be lowercase."
msgstr ""
#: ../../../contribute.rst:42
msgid "The second line should be blank."
msgstr ""
#: ../../../contribute.rst:43
msgid ""
"The third line should be the beginning of a longer description of the change"
" in complete sentences, if necessary."
msgstr ""
#: ../../../contribute.rst:44
msgid ""
"50/72 rule: The first line should be no longer than 50 characters (ideally),"
" and the rest of the message should be wrapped at 72 characters per line. "
"This can be configured in your text editor."
msgstr ""
#: ../../../contribute.rst:45
msgid ""
"If the change is related to a specific issue in the Jami GitLab, include the"
" issue number in the commit message. For example: ``GitLab: #123``. If the "
"change is related to multiple issues, list them all. If the change is "
"related to an issue that is not part of the project, use a link to the issue"
" instead."
msgstr ""
#: ../../../contribute.rst:47
msgid "Template for a commit message:"
msgstr ""
#: ../../../contribute.rst:61
msgid "For example:"
msgstr "Zum Beispiel:"
#: ../../../contribute.rst:75
msgid "Packaging Jami"
msgstr "Verpackung Jami"
#: ../../../contribute.rst:77
msgid ""
"There is two possible ways to package Jami: + Via our internal process to "
"create packages available on the Snap Store or https://dl.jami.net + Via the"
" packaging process of your favorite GNU/Linux distribution"
msgstr ""
#: ../../../contribute.rst:82
msgid ""
"Jami is a quite complex project with a lot of dependencies. This isn't a "
"quick and easy task and ask for some maintainance."
msgstr ""
#: ../../../contribute.rst:85
msgid ""
"If you choose the second option, here are some useful notes: + For our "
"official release, we stick to a certain Qt version, because Qt is a big "
"dependency and we need to ensure that Jami works with the version we use. "
"Every slight change in the Qt version can break Jami or bring some small "
"unwanted changes (e.g. 6.2->6.4 broke the video pipeline) + We also fork "
"pjproject due to ICE over TCP that is not planned upstream + libupnp got "
"some patches to be sure that it's build with the non-blocking API. + FFMpeg "
"got some patches for screen sharing. + You can check how dependencies are "
"built in `daemon/contrib/src`"
msgstr ""
#: ../../../contribute.rst:95
msgid ""
"For internal packaging, everything is located in `extras/packaging/gnu-"
"linux`. You can follow previous patches to understand your needs. e.g.: "
"https://review.jami.net/c/jami-client-qt/+/28036"
msgstr ""
#: ../../../contribute.rst:98
msgid ""
"We use 3 channels: + Internal for testing purposes + Nightly/Beta/Edge for "
"public beta + Stable for public releases"
msgstr ""
#: ../../../contribute.rst:103
msgid ""
"We generally use internal when we test new distribution or when we package a"
" new Qt version Then we try to generate a nightly per week and one stable "
"per month (if unit tests are green)."
msgstr ""
#: ../../../contribute.rst:106
msgid ""
"Packages are pushed to: + dl.jami.net (2 machines, with a rsync every 15 "
"min) + Ubuntu store (snapcraft.io/jami)"
msgstr ""
#: ../../../contribute.rst:110
msgid ""
"If you want to add a new distribution, you will need to: + Add Dockerfile + "
"Change Makefile + Update packaging script + Cross fingers + Test the package"
" in a VM"
msgstr ""
#: ../../../contribute.rst:117
msgid "Chromium is a hard part to build. the 3 commons problems we got are:"
msgstr ""
#: ../../../contribute.rst:119
msgid "GCC is too recent:"
msgstr ""
#: ../../../contribute.rst:120
msgid ""
"Generally the fix consist of importing patches from chromium's gerrit to fix"
" GCC issues"
msgstr ""
#: ../../../contribute.rst:121
msgid "Python is too recent:"
msgstr ""
#: ../../../contribute.rst:122
msgid ""
"Generally the fix consist of using PyEnv to get a virtual environment with "
"the correct Python's version"
msgstr ""
#: ../../../contribute.rst:123
msgid "Missing dependencies:"
msgstr ""
#: ../../../contribute.rst:124
msgid ""
"During the configuration step of Qt, the list of built components is listed "
"and the missing dependencies are listed. Generally installing a package or "
"updating node.js fix the issue"
msgstr ""
#: ../../../contribute.rst:125
msgid ""
"Note that if Qt is generated without chromium, we must remove the package in"
" the cache of the build machines to regenerate a new one (/var/cache/jami)"
msgstr ""
#: ../../../contribute.rst:127
msgid ""
"If you want to remove a distribution: + If a distribution is EOL OR if there"
" is 2 more recent LTS, we can remove the distribution (e.g. ubuntu 20, 22, "
"24 - remove ubuntu 20) by removing related files and checks"
msgstr ""
#: ../../../contribute.rst:130
msgid "For the next big changes we want to:"
msgstr ""
#: ../../../contribute.rst:132
msgid "Use CMake instead autotools for jami-daemon"
msgstr ""
#: ../../../contribute.rst:133
msgid "Use core22 instead core20 in snap"
msgstr ""
#: ../../../contribute.rst:134
msgid ""
"Flatpak/AppImage support? This may simplify custom packaging for RPMs/Debs"
msgstr ""
#: ../../../contribute.rst:135
msgid "Only generate one deb instead one per distribution. Same for RPMs"
msgstr ""
#: ../../../contribute.rst:136
msgid ""
"Use Jenkinsfile to generate package for Linux/Windows/MacOs at the same time"
" if possible"
msgstr ""
#: ../../../contribute.rst:139
msgid ""
"For internal information (such as how to publish to stores, cf internal "
"wiki)."
msgstr ""
#: ../../../contribute.rst:143
msgid "Contributing to this documentation"
msgstr "Mitwirkung an dieser Dokumentation"
#: ../../../contribute.rst:145
msgid ""
"Contributions to these docs are always welcome and appreciated, from small "
"corrections to whole new chapters."
msgstr ""
"Die Beiträge zu diesen Dokumenten sind immer willkommen und geschätzt, von "
"kleinen Korrekturen bis hin zu ganz neuen Kapiteln."
#: ../../../contribute.rst:148
msgid ""
"This page will walk through the steps to create a new page or submit a "
"correction. The patch review process is the same as :doc:`for any other "
"Jami project <how-to-submit-a-patch>`, so we will not explain every command."
msgstr ""
"Diese Seite wird die Schritte durchlaufen, um eine neue Seite zu erstellen "
"oder eine Korrektur einzureichen. Der Patch-Review-Prozess ist derselbe wie "
"für jedes andere Jami-Projekt:"
#: ../../../contribute.rst:153
msgid ""
"By contributing to this documentation, you agree to make your contributions "
"available under the :doc:`fdl`, Version 1.3 or any later version published "
"by the Free Software Foundation; with no Invariant Sections, no Front-Cover "
"Texts, and no Back-Cover Texts."
msgstr ""
"Wenn Sie zu dieser Dokumentation beitragen, stimmen Sie zu, Ihre Beiträge "
"unter der :doc:`fdl`, Version 1.3 oder einer späteren Version zur Verfügung "
"zu stellen, die von der Free Software Foundation veröffentlicht wurde; ohne "
"unveränderliche Abschnitte, ohne Front-Cover-Texte und ohne Back-Cover-"
"Texte."
#: ../../../contribute.rst:159
msgid ""
"You are also promising that you are the author of your changes, or that you "
"copied them from a work in the public domain or a work released under a free"
" license that is compatible with the :doc:`fdl`. DO NOT SUBMIT COPYRIGHTED "
"WORK WITHOUT PERMISSION."
msgstr ""
"Sie versprechen außerdem, dass Sie der Autor Ihrer Änderungen sind oder dass"
" Sie sie aus einem Werk in der öffentlichen Domain oder einem Werk kopiert "
"haben, das unter einer kostenlosen Lizenz veröffentlicht wurde, die mit der "
":doc:`fdl` kompatibel ist."
#: ../../../contribute.rst:165
msgid ""
"If you want to help to translate this page, you can join the project and "
"start translating this page on "
"https://explore.transifex.com/savoirfairelinux/jami/"
msgstr ""
#: ../../../contribute.rst:170
msgid "Dependencies"
msgstr "Abhängigkeiten"
#: ../../../contribute.rst:172
msgid ""
"You will need Git installed and configured to use your SSH keypair, and an "
"account on the `Jami Gerrit <https://review.jami.net>`_, where you would "
"send your patches for review. If you need help with this, see :doc:`the "
"beginning of our patch submission guide <how-to-submit-a-patch>` (TODO)."
msgstr ""
"Sie benötigen Git installiert und konfiguriert, um Ihr SSH-Tastepaar zu "
"verwenden, und ein Konto auf dem `Jami Gerrit <https://review.jami.net>`_, "
"wo Sie Ihre Patches zur Überprüfung senden würden. Wenn Sie Hilfe hierfür "
"benötigen, siehe:doc:`den Beginn unseres Patch-Sendings-Guides <how-to-"
"submit-a-patch>` (TODO)."
#: ../../../contribute.rst:178
msgid ""
"If you want to preview your changes locally in your web browser, you need to"
" install `Sphinx <https://www.sphinx-doc.org>`_, the `Read the Docs Sphinx "
"theme <https://sphinx-rtd-theme.readthedocs.io/en/stable/>`_, and the `MyST "
"Markdown parser <https://myst-parser.readthedocs.io/en/latest/index.html>`_."
msgstr ""
"Wenn Sie Ihre Änderungen vor Ort in Ihrem Webbrowser sehen möchten, müssen "
"Sie `Sphinx <https://www.sphinx-doc.org>`_, den `Read the Docs Sphinx theme "
"<https://sphinx-rtd-theme.readthedocs.io/en/stable/>`_ und den `MyST "
"Markdown parser <https://myst-parser.readthedocs.io/en/latest/index.html>`_ "
"installieren."
#: ../../../contribute.rst:189
msgid ""
"If you want to use the auto-build and auto-refresh feature, also install "
"`sphinx-autobuild <https://github.com/executablebooks/sphinx-autobuild>`_."
msgstr ""
"Wenn Sie die Funktion Auto-Build und Auto-Refresh verwenden möchten, "
"installieren Sie auch `sphinx-autobuild "
"<https://github.com/executablebooks/sphinx-autobuild>`_."
#: ../../../contribute.rst:197
msgid "Cloning the repository"
msgstr "Klonen des Repositoriums"
#: ../../../contribute.rst:199
msgid "Clone the repository and configure the push settings like this:"
msgstr ""
"Klonen Sie das Repository und konfigurieren Sie die Push-Einstellungen wie "
"folgt:"
#: ../../../contribute.rst:207
msgid ""
"You may want to checkout a new branch for each contribution/change before "
"you make any change to the files, so that you could easily ``git pull`` any "
"future changes from upstream into your main local branch:"
msgstr ""
"Sie können eine neue Zweigstelle für jeden Beitrag/Änderung vor dem "
"Einführen von Änderungen an den Dateien abschließen, damit Sie alle "
"zukünftigen Änderungen von vorwärts in Ihre Hauptverwaltung aufnehmen "
"können:"
#: ../../../contribute.rst:217
msgid "Editing a page"
msgstr "Bearbeitung einer Seite"
#: ../../../contribute.rst:219
msgid ""
"Pages are written in either markdown or `reStructuredText "
"<https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html>`_."
" You can click \"View page source\" at the top of any page to open the raw "
"source of the page and see how it was written."
msgstr ""
"Seiten werden entweder in Markierung oder `reStructuredText "
"<https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html>`_ "
"geschrieben. Sie können oben auf jede Seite auf \"Seitenquelle anzeigen\" "
"klicken, um die Rohquelle der Seite zu öffnen und zu sehen, wie sie "
"geschrieben wurde."
#: ../../../contribute.rst:224
msgid "Go ahead and make your changes to the ``.rst`` or ``.md`` files."
msgstr ""
"Gehen Sie voran und machen Sie Ihre Änderungen an den ``.rst`` oder ``.md`` "
"Dateien."
#: ../../../contribute.rst:227
msgid "Previewing your work"
msgstr "Überprüfung Ihrer Arbeit"
#: ../../../contribute.rst:229
msgid "From the base of the repository, run:"
msgstr "Aus der Basis des Repository ausführen:"
#: ../../../contribute.rst:235
msgid ""
"You should now be able to view the documentation in your web browser. The "
"homepage is at ``_build/html/index.html``."
msgstr ""
"Sie sollten jetzt die Dokumentation in Ihrem Webbrowser anzeigen können."
#: ../../../contribute.rst:238
msgid ""
"This documentation does not currently build with the latest version of "
"sphinx. Please see `this issue on GitLab "
"<https://git.jami.net/savoirfairelinux/jami-docs/-/issues/15>`_ for a "
"workaround and updates regarding this problem."
msgstr ""
#: ../../../contribute.rst:243
msgid ""
"To automatically build the documentation and refresh your web browser "
"whenever you save changes, run:"
msgstr ""
"Um die Dokumentation automatisch zu erstellen und Ihren Webbrowser zu "
"aktualisieren, wenn Sie Änderungen speichern, laufen Sie:"
#: ../../../contribute.rst:250
msgid ""
"Keep this running in the background, then navigate to http://127.0.0.1:8000 "
"(*not* the local .html file)."
msgstr ""
"Halten Sie diese im Hintergrund laufen, dann navigieren Sie zu "
"http://127.0.0.1:8000 (* nicht* die lokale.html-Datei)."
#: ../../../contribute.rst:254
msgid "Saving your work"
msgstr "Du hast deine Arbeit gerettet."
#: ../../../contribute.rst:261
msgid ""
"Refer to the `commit message guidelines <contribute.html#commit-message-"
"guidelines>`_ for how to write a good commit message."
msgstr ""
#: ../../../contribute.rst:264
msgid "Submitting a change"
msgstr "Einreichung einer Änderung"
#: ../../../contribute.rst:266
msgid ""
"The first time you try to push your changes, Gerrit will complain that you "
"don't have a Change-Id in your commit, and provide an ``scp`` command to "
"install the commit hook. After running the command, you should be able to "
"recommit and push your change:"
msgstr ""
"Wenn Sie zum ersten Mal versuchen, Ihre Änderungen zu verschieben, wird sich"
" Gerrit beschweren, dass Sie keine Change-ID in Ihrem Commit haben, und "
"geben Sie einen ``scp`` Befehl zum Installieren des Commit-Hakels."
#: ../../../contribute.rst:278
msgid "Modifying your work"
msgstr "Ihre Arbeit zu ändern"
#: ../../../contribute.rst:280
msgid ""
"A reviewer may ask you to make changes to your patch before merging it. "
"This is no problem! Simply make the changes, ``git add`` them, and run "
"``git commit --amend`` to modify the patch. Note the ``--amend`` switch, "
"which is needed to tell git to *amend*/tweak the existing newest commit "
"rather than making a new commit. This is the workflow for updating a "
"proposed change when using Gerrit."
msgstr ""
"Ein Rezensierer kann Sie bitten, Änderungen an Ihrem Patch vor dem "
"Zusammenschluss vorzunehmen. Das ist kein Problem! Machen Sie einfach die "
"Änderungen, ``git add``` sie und laufen Sie ``git commit -amend`` get, um "
"den Patch zu ändern. Beachten Sie den ``--amend`` switch, der git dazu "
"angewiesen ist, das bestehende neueste Commit zu *amend*/tweak zu machen, "
"anstatt ein neues Commit zu machen. Dies ist der Workflow für die "
"Aktualisierung einer vorgeschlagenen Änderung bei der Verwendung von Gerrit."
#: ../../../contribute.rst:288
msgid "Adding a page"
msgstr "Hinzufügen einer Seite"
#: ../../../contribute.rst:290
msgid ""
"If you decide to add a whole new page to the documentation, you must also "
"add it to the ``toctree`` directive of that chapter."
msgstr ""
"Wenn Sie sich entscheiden, der Dokumentation eine ganz neue Seite "
"hinzuzufügen, müssen Sie sie auch der ``toctree`` Richtlinie dieses Kapitels"
" hinzufügen."
#: ../../../contribute.rst:293
msgid ""
"For instance, if you added a new page called ``hosting-jams-on-aws-"
"guide.md`` to the Jami user manual in the ``user`` folder, you should add it"
" in the ``toctree`` directive of ``user/index.rst``, *without* the file "
"extension:"
msgstr ""
"Wenn Sie beispielsweise eine neue Seite namens ``hosting-jams-on-aws-"
"guide.md`` in das Jami-Benutzerhandbuch in dem ``user`` Ordner hinzugefügt "
"haben, sollten Sie sie in der ``toctree`` Richtlinie von ``user/index.rst``,"
" *ohne* die Dateierweiterung hinzufügen:"