From 1c13b41f9da75a4855976b3cbad61ef68788df8e Mon Sep 17 00:00:00 2001 From: Markus Richter Date: Nov 27 2017 12:56:11 +0000 Subject: Add german translation Signed-off-by: Markus Richter --- diff --git a/source/_themes/modularity/boltron/index_boltron_de.html b/source/_themes/modularity/boltron/index_boltron_de.html new file mode 100644 index 0000000..1d2825f --- /dev/null +++ b/source/_themes/modularity/boltron/index_boltron_de.html @@ -0,0 +1,141 @@ + + + + +Fedora Modularity + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+
+
+ +
+
+

Boltron ist da!

+

Wir haben den ersten modularen Prototypen erstellt – Fedora 26 Boltron Server!

+
+
+ +
+
+

Herunterladen und testen von Boltron

+

Boltron ist verfügbar in vielen Artefakten, darunter ein Container-Image, Iso und ein QCOW-Image.

Testen Sie Boltron
+
+ + + +
+
+

Es sind 25 Module zum Spielen vorhanden

+

Folgendes ist eine Liste der in Boltron enthaltenen 25 Module. Viele von ihnen werden auch als Container erstellt.

+ +
+
    +
  • base-runtime-f26
    • +
  • container-runtime-f26
    • +
  • dhcp-f26
    • +
  • dhcp-server-f26
    • +
  • dnf-f26
    • +
  • haproxy-f26
    • +
  • httpd-f26
    • +
  • installer-f26
    • +
  • mariadb-f26
    • +
+
    +
  • memcached-f26
    • +
  • mongodb-f26
    • +
  • nginx-f26
    • +
  • nodejs-8
    • +
  • nodejs-f26
    • +
  • perl-f26
    • +
  • perl-Unicode-EastAsianWidth-f26
    • +
  • php-f26
    • +
  • postfix-f26
    • +
+
    +
  • postgresql-f26
    • +
  • shared-userspace-f26
    • +
  • shim-master
    • +
  • source-to-image-f26
    • +
  • sssd-f26
    • +
  • systemtools-f26
    • +
  • varnish-f26
    • +
+
Erfahren Sie mehr über Boltron Content
+
+ +
+
+

Wir würden uns über Ihr Feedback freuen!

+

Sie können uns entweder allgemeines Feedback zu Modularity geben oder den Walkthrough wählen für mehr Details und UX-Feedback.

+

Senden Sie uns Feedback & lesen Sie Antworten

+
+
+ +
+
+

Schauen Sie die Videos

+

Es wird eine Reihe von Videos auf YouTube geben, die Ihnen beim Start mit Boltron helfen. Schauen Sie unseren Fedora Modularity YouTube-Kanal.

Boltron auf Youtube
+
+ +
+
+
+ © Copyright 2017, Red Hat, Inc. und Andere. Inhalte lizenziert unter: https://creativecommons.org/licenses/by-sa/3.0/. Mit Sphinx erzeugt.
+
+
+ + + \ No newline at end of file diff --git a/source/_themes/modularity/index_home_de.html b/source/_themes/modularity/index_home_de.html new file mode 100644 index 0000000..aa2b257 --- /dev/null +++ b/source/_themes/modularity/index_home_de.html @@ -0,0 +1,172 @@ + + + + +Fedora Modularity + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+ + + + +
+
+ +
+
+

Erstellen eines modularen Linux OS

+

mit mehreren Versionen von Komponenten mit unterschiedlichen Lebenszyklen.

+

+ Lesen Sie die Dokumentation + +

+
+
+ +
+
+

Fedora 27 Beta Modular Server ist da!

+

Fedora 27 Modular Server wird unsere erste produktionsreife Version sein. Vorschau der Beta!

+

Download-Seite

+
+
+ + + +
+
+

Verschieben des Fokus von Paketen auf Komponenten

+ +

+ Modularity teilt die Linux-Distribution in kleinere Stücke, die sogenannten Module.
Module werden in mehreren Streams und mit voneinander unabhängigen Lebenszyklen angeboten.

+ + +
+
+ + + + +
+
+

Benutzern die Wahl geben und Paketierern Flexibilität

+

Module kommen in verschiedenen Streams mit unabhängigen Lebenszyklen.
Streams haben unterschiedliche Ziele – spezifische Version, Stabilität oder dem Upstream zu folgen.

+ +
+
+ +
+
+

Modul als ein ultimatives Build-Rezept

+

Paketbetreuer entscheiden, wie Sie bauen – durch die Definition von Komponenten, Build-Reihenfolge und Buildroot.

+ + +

Paketierer entscheiden, was Sie versenden – durch das Ausfiltern unnötiger Binärpakete.

+ +

Paketierer entscheiden, wie es verwendet wird – durch das Definieren einer unterstützten API und dem Installieren von Profilen.

+ +
+
+
+
+

Module laufen nahezu überall

+

Jedes Modul kann in mehreren Artefakten erzeugt werden.
Container für Cloud und Server, Flatpaks* für den Desktop, RPMs für Tradition.

+ +

* Flatpaks liegen noch etwas in der Zukunft, aber sind auf der Liste!

+
+
+ +
+
+

Folgen Sie unseren Fortschritten

+

Wir veröffentlichen regelmäßig auf unserem YouTube-Kanal zu Fedora Modularity.

+

Sehen Sie unsere Videos

+
+
+ +
+
+

Treten Sie mit uns in Verbindung!

+

Kommen Sie zu unseren regelmäßigen Treffen, fragen Sie uns auf der Mailingliste oder diskutieren Sie mit uns in unserem IRC-Channel.

+

Wiki-Seite Modularity Working Group

+
+
+ +
+
+
+ © Copyright 2017, Red Hat, Inc. and others, content licensed under: https://creativecommons.org/licenses/by-sa/3.0/. + + Built with Sphinx. +
+
+
+ + + diff --git a/source/locale/de/LC_MESSAGES/design/building-naming.po b/source/locale/de/LC_MESSAGES/design/building-naming.po new file mode 100644 index 0000000..9ffdcf0 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/design/building-naming.po @@ -0,0 +1,96 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/design/building-naming.rst:2 +msgid "Building and naming modular things" +msgstr "Erzeugen und Benennen von modularen Dingen" + +#: ../../source/design/building-naming.rst:4 +msgid "" +"We have some basic terminology confusion around modules. Is a container " +"image the same thing as a module? Is a software collection a single " +"module, or a group of modules? We can often get away with being vague, " +"but for technical planning we need to be able to distinguish between all " +"these concepts." +msgstr "Wir haben eine grundsätzliche Verwirrung bzgl. der Terminologie Module betreffend. Ist ein Container-Image das Gleiche wie ein Modul? Ist eine Software Collection ein einzelnes Modul oder eine Gruppe von Modulen? Wir kommen meist mit aus mit einer ungefähren Bezeichnung, aber für die technische Planung müssen wir zwischen all diesen Konzepten unterscheiden können." + +#: ../../source/design/building-naming.rst:10 +msgid "We use these terms:" +msgstr "Wir verwenden diese Begriffe:" + +#: ../../source/design/building-naming.rst:12 +msgid "" +"**Package**. Essentially, the same thing as an rpm. In the future it " +"might be non-rpm content but should fit the same role." +msgstr "**Paket** – Im Wesentlichen das Gleiche wie ein RPM. In der Zukunft ist es möglicherweise nicht mehr auf RPM basierend, sollte aber die gleiche Rolle ausfüllen." + +#: ../../source/design/building-naming.rst:14 +msgid "" +"**Module.** A set of packages tested and released together as a distinct " +"unit, complete with the metadata needed to manage it as a unit. May " +"depend on other modules." +msgstr "**Modul** – Ein Set von Paketen, zusammen getestet und veröffentlicht als eigenständige Einheit. Vervollständigt mit den Metadaten, die benötigt werden, um es als Einheit zu verwalten. Möglicherweise existieren Abhängigkeiten zu anderen Modulen." + +#: ../../source/design/building-naming.rst:17 +msgid "" +"**Stack.** A complete tree of modules. A stack can be thought of as a " +"top-level module, with the understanding that we’re implicitly including " +"all of that module’s dependencies in the stack. However, when the stack " +"is delivered to the end-user it appears as \"just another module.\"" +msgstr "**Stack** – Ein vollständiger Baum von Modulen. Einen Stack kann man sich vorstellen als ein Top-Level-Modul. Dies ist so zu verstehen, dass wir ausdrücklich alle Modulabhängigkeiten in dem Stack inkludieren. Dennoch erscheint der Stack, wenn er an den Endbenutzer verteilt wird, als \"lediglich ein weiteres Modul\"." + +#: ../../source/design/building-naming.rst:21 +msgid "" +"**Artifact** or **image**. An actual set of bits built out of modules, in" +" a format intended to be distributed or deployed in some way." +msgstr "**Artefakt** oder **Image** – Ein aktuelles Set von Bits erstellt aus Modulen. In einem Format, dass dazu gedacht ist, in irgendeiner Weise verteilt und eingesetzt zu werden." + +#: ../../source/design/building-naming.rst:25 +msgid "" +"Generally, these serve distinct purposes. A module is a building block; a" +" stack contains all the software for a complete solution; an artifact is " +"a concrete object containing a stack (or stacks) for distribution to " +"users." +msgstr "Allgemein dienen diese unterschiedlichen Zwecken. Ein Modul ist ein Baustein; ein Stack beinhaltet alles an Software für eine komplette Lösung; ein Artefakt ist ein konkretes Objekt, das einen Stack (oder mehrere) enthält, um so an Benutzer verteilt zu werden." + +#: ../../source/design/building-naming.rst:30 +msgid "We will also distinguish between:" +msgstr "Ebenso unterscheiden wir zwischen:" + +#: ../../source/design/building-naming.rst:32 +msgid "" +"A **Build** of a package: a process which involves compiling source code " +"and creating a packaged output" +msgstr "Einem **Build** eines Paketes: Ein Prozess, der das Kompilieren des Quellcodes beinhaltet und eine paketierte Ausgabe erstellt." + +#: ../../source/design/building-naming.rst:34 +msgid "" +"A **Compose** of a module: a process which assembles pre-compiled " +"packages into an organised module, but which includes no compilation step" +" itself. Sometimes we also use the term **Coallesce** for this scenario " +"to distinguish between the existing, Fedora term \"Compose\" which is " +"very similar but not quite the same." +msgstr "Einem **Compose** eines Moduls: Ein Prozess, der vorkompilierte Pakete in einem organisierten Modul zusammenführt, wobei dieser Prozess selbst keinerlei Kompilierung beinhaltet. Gelegentlich verwenden wir den Begriff **Coallesce** (Verbinden) für dieses Szenario, um zu dem existierenden Begriff \"Compose\" in Fedora abzugrenzen, welcher sehr ähnlich ist, aber nicht genau das Gleiche meint." + +#: ../../source/design/building-naming.rst:41 +msgid "TOC" +msgstr "TOC" + diff --git a/source/locale/de/LC_MESSAGES/design/building-naming/artifact.po b/source/locale/de/LC_MESSAGES/design/building-naming/artifact.po new file mode 100644 index 0000000..10f89d1 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/design/building-naming/artifact.po @@ -0,0 +1,48 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/design/building-naming/artifact.rst:2 +msgid "The Image or Artifact" +msgstr "Das Image oder Artefakt" + +#: ../../source/design/building-naming/artifact.rst:4 +msgid "" +"We build stacks into *images* or other *artifacts* such as ostree trees. " +"These are the formats in which we release a stack." +msgstr "Wir erzeugen Stacks innerhalb von **Images** oder anderen **Artefakten** wie OSTree-Bäumen. Dies sind die Formate, in denen wir Stacks veröffentlichen." + +#: ../../source/design/building-naming/artifact.rst:7 +msgid "" +"For example, we could take a single stack such as a LAMP stack, and build" +" and release it both as SCL rpms in a yum repository, and as container " +"images: indeed, we do so today. It’s the same stack in each artifact. We " +"could add more such formats: virtual appliances, vagrant boxes, anaconda " +"isos or ostree trees, and it would still be the same stack in each; only " +"the artifact / format / image has changed." +msgstr "Zum Beispiel können wir einen einzelnen Stack nehmen, wie den LAMP-Stack und diesen sowohl als SCL-RPM erzeugen und in einem YUM-Repository veröffentlichen, als auch als Container-Images. Und in der Tat, genau dies tun wir bereits. Es handelt sich um den gleichen Stack in jedem Artefakt. Wir können mehr solcher Formate veröffentlichen: Virtuelle Appliances, Vagrant-Boxen, Anaconda-ISOs oder OSTree-Bäume – und überall würde es sich um den gleichen Stack handeln. Lediglich das Artefakt / Format / Image hat sich geändert." + +#: ../../source/design/building-naming/artifact.rst:17 +msgid "" +"The format of the content we deliver may be different in each case, but " +"it’s the same binaries from the same stack inside, and the same stack " +"metadata describing that content." +msgstr "Das Format des Contents, den wir verteilen, mag in jedem einzelnen Fall unterschiedlich sein, aber es sind die gleichen Binärdateien vom gleichen Stack enthalten und die gleichen Stack-Metadaten beschreiben diesen Content." + diff --git a/source/locale/de/LC_MESSAGES/design/building-naming/fit-together.po b/source/locale/de/LC_MESSAGES/design/building-naming/fit-together.po new file mode 100644 index 0000000..1e3304f --- /dev/null +++ b/source/locale/de/LC_MESSAGES/design/building-naming/fit-together.po @@ -0,0 +1,66 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/design/building-naming/fit-together.rst:2 +msgid "How do these parts fit together?" +msgstr "Wie fügen sich diese Teile zusammen?" + +#: ../../source/design/building-naming/fit-together.rst:4 +msgid "" +"Let’s look at a couple of examples to make it (hopefully!) clear what " +"we’re talking about." +msgstr "Schauen wir uns ein paar Beispiele an, um es (hoffentlich) deutlich zu machen, worüber wir eigentlich reden." + +#: ../../source/design/building-naming/fit-together.rst:8 +msgid "Example 1: Our Atomic Host stack" +msgstr "Beispiel 1: Unser Atomic Host Stack" + +#: ../../source/design/building-naming/fit-together.rst:10 +msgid "" +"We already release content that is organised in much this way, just not " +"with any formal definition of modules or stacks." +msgstr "Wir veröffentlichen bereits Content, der im Wesentlichen auf diese Weise organisiert wird, lediglich nicht mit irgendwelchen formalen Definitionen von Modulen oder Stacks." + +#: ../../source/design/building-naming/fit-together.rst:13 +msgid "" +"Atomic, for example, is composed from multiple sources. Some content " +"comes from traditional Fedora with its usual 6-month lifecycle; and some " +"comes from other repos with much shorter lifecycle and rapid rebasing to " +"pick up new features." +msgstr "Beispielsweise wird Atomic aus mehreren Quellen erzeugt. Einige Inhalte stammen aus der traditionellen Fedora-Entwicklungslinie, mit dem üblichen 6-monatigen Lebenszyklus. Andere stammen von anderen Repos, mit wesentlich kürzeren Lebenszyklen und rapidem Rebasing, um neue Features aufzunehmen." + +#: ../../source/design/building-naming/fit-together.rst:18 +msgid "" +"And even within Fedora we have different levels of lifecycle. An obvious " +"example is Gnome; the Anaconda installer stack that we use for Atomic " +"installer ISO images depends on this faster-moving content, even when the" +" installed atomic host does not include it." +msgstr "Und auch innerhalb von Fedora arbeiten wir mit verschiedenen Stufen von Lebenszyklen. Ein offensichtliches Beispiel hierfür ist GNOME. Der Stack für den Anaconda-Installer, den wir für Images der Atomic Installer ISO verwenden, ist abhängig von diesem sich schneller entwickelnden Content, auch wenn der installierte Atomic Host diesen nicht enthält." + +#: ../../source/design/building-naming/fit-together.rst:23 +msgid "" +"But even though these distinct sets of components all have differing " +"lifecycles, they still belong within Fedora and we still produce coherent" +" output images or artifacts from them today, with planned releases that " +"require alignment between all the relevant parts. In the language of this" +" document, it might look like this:" +msgstr "Aber obwohl diese unterschiedlichen Sets von Komponenten divergierende Lebenszyklen besitzen, gehören sie immer noch zu Fedora. Wir produzieren dennoch kohärente Images oder Artefakte von diesen, mit geplanten Releases, die eine Abstimmung zwischen allen relevanten Teilen erfordern. In der Sprache dieses Dokuments könnte dies so aussehen:" + diff --git a/source/locale/de/LC_MESSAGES/design/building-naming/module.po b/source/locale/de/LC_MESSAGES/design/building-naming/module.po new file mode 100644 index 0000000..885d761 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/design/building-naming/module.po @@ -0,0 +1,77 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/design/building-naming/module.rst:2 +msgid "The Module" +msgstr "Das Modul" + +#: ../../source/design/building-naming/module.rst:4 +msgid "" +"We group these binary packages into *modules*. Note, we can pick just a " +"subset of the subpackages from a particular build into a given module, " +"eg. a hypothetical example base runtime module:" +msgstr "Wir gruppieren diese Binärpakete in *Modulen*. Beachten Sie, dass wir auch nur eine Teilmenge der Unterpakete aus einem bestimmten Build in ein Modul packen können. Hier ein Beispiel mit einem hypothetischen Base-Runtime-Modul:" + +#: ../../source/design/building-naming/module.rst:12 +msgid "" +"These are internal build groupings: basically *repositories*, but with " +"additional metadata and semantics that allow them to play nicely with " +"other modules and module tooling." +msgstr "Dies sind interne Build-Gruppierungen – im Grunde *Repositorys*, aber mit zusätzlichen Metadaten und Semantik. Die es ihnen ermöglichen, mit anderen Modulen und Modulwerkzeugen gut zusammenzuspielen." + +#: ../../source/design/building-naming/module.rst:16 +msgid "" +"We attach metadata to these modules, on top of the normal metadata in a " +"repository. Metadata may include: support metadata (SLAs or EOL dates for" +" the module); metadata on how to use the module (eg. its dependencies, " +"default installed packages); identity (builder, vendor, version etc), or " +"many other things that we’re still just starting to imagine." +msgstr "Wir fügen Metadaten zu diesen Modulen hinzu, zusätzlich zu den normalen Metadaten in einem Repository. Metadaten können umfassen: Metadaten, den Support betreffend (SLAs- oder EOL-Datierungen für das Modul); Metadaten, wie das Modul verwendet werden kann (z. B. seine Abhängigkeiten, die standardmäßig installierten Pakete); Identität (Builder, Hersteller, Version, etc.) oder viele andere Dinge, die noch heraus modelliert werden müssen." + +#: ../../source/design/building-naming/module.rst:22 +msgid "" +"We should be able to update the module as a unit: updating and testing " +"its component parts as necessary, but also testing the module as a whole " +"before releasing an update." +msgstr "Wir sollten in der Lage sein, das Modul als eine Einheit zu aktualisieren: Aktualisieren und Prüfen seiner Komponenten bei Bedarf, aber auch das Testen des Moduls als Ganzes vor dem Release eines Updates." + +#: ../../source/design/building-naming/module.rst:26 +msgid "" +"We refer to the assembly of a module by a build tool as a *compose*. This" +" step includes no compilation; it is merely the creation of a bundled set" +" of packages and metadata comprising a single module. The closest " +"analogue in today’s build system is the “puddle build”, where a custom " +"repository is created for a particular purpose." +msgstr "Wir beziehen uns bei der Montage eines Moduls durch ein Build-Tool auf einen *Compose*. Dieser Schritt beinhaltet keinerlei Kompilierung. Es handelt sich lediglich um die Kreierung eines gebündelten Sets von Paketen und Metadaten, zusammengesetzt in einem einzigen Modul. Die nächstliegende Analogie in heutigen Build-Systemen ist der `Puddle Build`, bei dem ein benutzerdefiniertes Repository für einen bestimmten Zweck erstellt wird." + +#: ../../source/design/building-naming/module.rst:32 +msgid "" +"When we talk about a **module compose**, we are *not* talking about “the " +"Compose” of a full distribution release. The two are similar, in that " +"they both assemble existing compiled packages into bundled output; but " +"the module compose is just one single targeted assembly, whereas the full" +" distribution Compose typically creates multiple repositories and images " +"as output in a single large job. Also note that we can, in theory, " +"perform the build (compilation) of the packages within a module, and the " +"compose of the module itself, as a single step; we might term this a " +"**module build.**" +msgstr "Wenn wir über einen **Modul-Compose** sprechen, reden wir *nicht* über »den Compose« einer vollständigen Distribution. Die beiden ähneln sich insofern, als beide bereits kompilierte Pakete zu einem gebündelten Output zusammenmontieren. Allerdings hat der Modul-Compose nur eine einzige Montage als Ziel, während die Zusammenstellung einer vollständigen Distribution in der Regel mehrere Repositorys und Images in einem einzigen großen Job als Output erzeugt. Ebenso ist zu beachten, dass in der Theorie, der Build (die Kompilierung) der Pakete innerhalb eines Moduls und der Compose des Moduls selbst, in einem einzigen Schritt ausgeführt werden können. Dies könnte man als einen **Modul-Build** bezeichnen." + diff --git a/source/locale/de/LC_MESSAGES/design/building-naming/package.po b/source/locale/de/LC_MESSAGES/design/building-naming/package.po new file mode 100644 index 0000000..688a694 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/design/building-naming/package.po @@ -0,0 +1,46 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/design/building-naming/package.rst:2 +msgid "The Package" +msgstr "Das Paket" + +#: ../../source/design/building-naming/package.rst:4 +msgid "" +"We can start with the familiar ''package ''and *subpackage*, *built* as " +"usual from a *component* (or *source package*):" +msgstr "Wir können mit dem bekannten *Paket* und *Unterpaket* beginnen, wie gewohnt *erzeugt* von einer *Komponente* (oder einem *Quellpaket*):" + +#: ../../source/design/building-naming/package.rst:10 +msgid "" +"We’re not changing anything at this level (yet… non-rpm packages are a " +"possible topic for the future!)" +msgstr "Auf dieser Ebene wird nichts geändert (noch nicht … nicht-RPM-basierte Pakete sind ein mögliches Thema für die Zukunft)." + +#: ../../source/design/building-naming/package.rst:13 +msgid "" +"It is important to distinguish the build of a package from the compose of" +" a module; the build here is the step which includes compilation and " +"creation of a reusable bundle of the compiled output. We might be " +"building specifically to compile for a module’s contents; but the build " +"step is still a distinct step." +msgstr "Es ist wichtig, den Build eines Pakets von dem Compose eines Moduls zu unterscheiden. Der Build ist der Schritt, der die Kompilierung und Erstellung eines wiederverwendbaren Bundles des kompilierten Outputs umfasst. Vielleicht erzeugen wir speziell für ein Modul die benötigten Inhalte, aber der Build ist nach wie vor ein separater Schritt." + diff --git a/source/locale/de/LC_MESSAGES/design/building-naming/stack.po b/source/locale/de/LC_MESSAGES/design/building-naming/stack.po new file mode 100644 index 0000000..96986da --- /dev/null +++ b/source/locale/de/LC_MESSAGES/design/building-naming/stack.po @@ -0,0 +1,64 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/design/building-naming/stack.rst:2 +msgid "The Stack" +msgstr "Der Stack" + +#: ../../source/design/building-naming/stack.rst:4 +msgid "We can then combine modules into *stacks*." +msgstr "Wir können anschließend Module in *Stacks* kombinieren." + +#: ../../source/design/building-naming/stack.rst:6 +msgid "" +"A stack should represent something distinct that the user wants. It may " +"be a traditional developer stack (LAMP, ruby-on-rails, etc.); or it may " +"be an application (but extended to include all the dependencies that the " +"application needs to run); or it could be the set of modules needed to " +"deliver something like Atomic Host or Cockpit." +msgstr "Ein Stack sollte etwas Spezielles darstellen, das der Benutzer benötigt. Es kann sich dabei um einen traditionellen Entwickler-Stack (LAMP, Ruby on Rails, etc.) handeln. Es kann sich aber auch um eine Anwendung handeln (allerdings erweitert, damit alle Abhängigkeiten enthalten sind, die die Applikation benötigt, um ausgeführt zu werden). Ebenso könnte es sich um das Set von Modulen handeln, das benötigt wird, um etwas wie Atomic Host oder Cockpit auszuliefern." + +#: ../../source/design/building-naming/stack.rst:15 +msgid "" +"The stack represents this full set of software. It doesn’t presume how we" +" distribute it, we’re still just talking about the set of modules making " +"up the stack." +msgstr "Der Stack repräsentiert dieses vollständige Set an Software. Es wird nicht vorgegeben, wie dieses letztendlich verteilt wird. Wir reden lediglich über das Set von Modulen, die den Stack bilden." + +#: ../../source/design/building-naming/stack.rst:19 +msgid "" +"**A stack is still just a module here.** It’s just a way of referring to " +"the module plus all its implied dependencies as a single unit, to " +"distinguish that from the individual modules within the stack; the stack " +"content and metadata may have exactly the same format as module metadata " +"(the metadata is the same colour here for a reason!) But it’s still " +"important (at least internally, probably not for end users) to make the " +"distinction between a single module, and a module plus all the external " +"dependencies it relies on." +msgstr "**Ein Stack ist lediglich ein Modul hier.** Dieser stellt lediglich eine Möglichkeit dar, auf das Modul, inklusiv all seiner Abhängigkeiten, als eine einzelne Unit zu referenzieren. Damit wird es abgegrenzt von den individuellen Modulen innerhalb des Stacks. Der Content des Stacks und seine Metadaten haben möglicherweise genau das gleiche Format wie die Metadaten der Module (die Metadaten haben aus einem guten Grund hier die gleiche Farbe). Aber es ist immer noch wichtig (zumindest intern, nicht unbedingt für Endbenutzer) zu unterscheiden zwischen einem einzelnem Modul und einem Modul mit all seinen externen Abhängigkeiten, die es benötigt." + +#: ../../source/design/building-naming/stack.rst:28 +msgid "" +"Importantly, we can take two modules with different lifecycles and " +"combine them in a single stack. The definition of the stack gives us the " +"way to plan and track the relationship or dependency between the modules." +msgstr "Wichtig ist, wir können zwei Module mit unterschiedlichen Lebenszyklen nehmen und diese in einem Stack kombinieren. Die Definition des Stacks gibt uns die Möglichkeit, die Beziehung oder Abhängigkeit zwischen den Modulen zu planen und zu überwachen." + diff --git a/source/locale/de/LC_MESSAGES/design/constructing.po b/source/locale/de/LC_MESSAGES/design/constructing.po new file mode 100644 index 0000000..691558a --- /dev/null +++ b/source/locale/de/LC_MESSAGES/design/constructing.po @@ -0,0 +1,81 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/design/constructing.rst:2 +msgid "Constructing a modular distribution" +msgstr "Konstruieren einer modularen Distribution" + +#: ../../source/design/constructing.rst:4 +msgid "" +"The fundamental objective of the Modularity effort is to break up the " +"monolithic concept of a “distribution release” or traditional Compose " +"into something more fine-grained. We should be able to release " +"applications or stacks such as LAMP or ruby-on-rails on a lifecycle that " +"suits the application, rather than being dictated by the distribution " +"release schedule; and we should be able to compose releases more flexibly" +" from the various components available." +msgstr "Die grundlegende Mission des Modularity-Unterfangens ist es, das monolithische Konzept eines »Distributions-Release« bzw. eines traditionellen Compose in etwas fein granulierteres aufzubrechen. Wir sollten in der Lage sein, Anwendungen oder Stacks, wie LAMP oder Ruby on Rails, zu veröffentlichen, die mit ihrem Lebenszyklus auf die Anwendung abgestimmt sind und nicht vom Release-Zeitplan der Distribution diktiert werden. Ebenso sollten wir in der Lage sein, den Compose der Releases unabhängiger von den diversen Komponenten durchführen zu können." + +#: ../../source/design/constructing.rst:13 +msgid "" +"But modularity is unlikely to succeed if it requires both users and " +"maintainers to immediately and completely discard the existing concept of" +" Releases and Editions of Fedora. So in this document we look at how to " +"break the traditional distribution down into a modular construction, " +"while still preserving the ability to build the traditional releases." +msgstr "Modularity wird sich nicht erfolgreich etablieren, wenn es sowohl von Benutzern und Maintainern verlangt, mit den bestehenden Konzepten von Releases und Editionen von Fedora unmittelbar und vollständig zu brechen. So werden wir in diesem Dokument schauen, wie wir die traditionelle Distribution herunterbrechen können in eine modulare Bauweise. Dabei soll die Möglichkeit erhalten bleiben, traditionelle Releases zu erzeugen." + +#: ../../source/design/constructing.rst:19 +msgid "" +"This document does not try to explore how we should organise a " +"distribution release in detail. Exact lifecycles for kernel vs. " +"applications, for containers vs. baremetal etc. are beyond the scope " +"here; indeed, our objective is explicitly ''not'' to assume what we need " +"in a release, but rather to add flexibility so we can change release " +"objectives later on. If we want Fedora Server to have a longer lifecycle " +"than Workstation; or for Atomic to rebase docker more rapidly than " +"Server; or for a new python to be released outside the normal " +"distribution cycle; all these things may be possible if we have a more " +"flexible underlying release structure. The flexibility is the subject " +"here; planning the actual releases is a different topic." +msgstr "Dieses Dokument versucht nicht zu erkunden, wie wir den Release einer Distribution im Detail organisieren sollten. Exakte Lebenszyklen für Kernel versus Applikationen, für Container versus Bare-Metal, etc. würden den Rahmen hier sprengen. Unser Zielsetzung ist in der Tat ausdrücklich *nicht* Annahmen darüber zu treffen, was wir in einem Release benötigen, sondern vielmehr Flexibilität hinzuzufügen, so dass wir Release-Vorgaben zu einem späteren Zeitpunkt immer noch ändern können. Wenn wir wollen, dass Fedora Server über einen längeren Lebenszyklus verfügt als Fedora Workstation; oder Docker zügiger für Atomic rebased wird als für Server; oder eine neue Python-Version außerhalb des normalen Distributions-Zyklus veröffentlicht wird. – So sind all diese Dinge möglicherweise umsetzbar, wenn wir darunterliegend eine flexiblere Release-Struktur haben. Die Flexibilität ist das Hauptthema hier, die Planung der aktuellen Releases ist ein anderes Thema." + +#: ../../source/design/constructing.rst:31 +msgid "" +"But, ultimately we still need the well-defined concept of a **release**, " +"so that all the modules we are maintaining can still come together into a" +" well-tested, planned release on a known schedule. We also define and " +"justify a **static manifest** to assign packages to modules." +msgstr "Aber letztendlich benötigen wir noch das klar definierte Konzept von einem **Release**, so dass alle Module, die wir betreuen, immer noch zusammengeführt werden können in einem solide getesteten und geplanten Release mit einem bekannten Zeitplan. Ebenso definieren und legitimieren wir ein **statisches Manifest** um Modulen Pakete zuzuweisen." + +#: ../../source/design/constructing.rst:36 +msgid "" +"Once we have parts of the distribution on different release cycles, we " +"also have the issue of how to maintain different versions branching on " +"different criteria and different schedules. Branching and versioning is " +"relevant here, but is a complex topic in its own right and is covered " +"under :doc:`/design/versioning`." +msgstr "Sobald wir Teile der Distribution auf verschiedenen Release-Zyklen haben, stellt sich auch die Frage, wie verschiedene Versionszweige betreut werden, die sich an verschiedenen Kriterien und unterschiedlichen Zeitintervallen orientieren. Branching und Versionierung ist hier von Relevanz, aber es ist ein komplexes Thema für sich und wird behandelt unter :doc:`/design/versioning`." + +#: ../../source/design/constructing.rst:43 +msgid "TOC" +msgstr "TOC" + diff --git a/source/locale/de/LC_MESSAGES/design/constructing/back-together.po b/source/locale/de/LC_MESSAGES/design/constructing/back-together.po new file mode 100644 index 0000000..d0eeb39 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/design/constructing/back-together.po @@ -0,0 +1,117 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/design/constructing/back-together.rst:2 +msgid "Putting it all back together" +msgstr "Alles wieder zusammensetzen" + +#: ../../source/design/constructing/back-together.rst:4 +msgid "" +"We need the flexibility of a smaller, more modular distribution that can " +"be reassembled in various different fashions. But we also need to be able" +" to reproduce our current product lineup, or something very similar, in " +"order not to disrupt our existing install base:" +msgstr "Wir brauchen die Flexibilität einer kleineren, mehr modular Distribution, die in unterschiedlichen Formen wieder zusammengefügt werden kann. Aber wir müssen auch in der Lage sein, unsere aktuelle Produktpalette zu reproduzieren oder etwas sehr Ähnliches, um nicht unsere existierende Installationsbasis zu stören:" + +#: ../../source/design/constructing/back-together.rst:10 +msgid "Example: Reproducing the traditional distribution versions" +msgstr "Beispiel: Reproduktion der traditionellen Distributions-Versionen" + +#: ../../source/design/constructing/back-together.rst:12 +msgid "" +"Having categorised the Fedora rpms into groups and composed those package" +" groups into distinct modules, creating what we have traditionally called" +" a distribution variant or edition can now be done simply by creating a " +"flat yum repository containing all the desired modules for that offering." +" In the terminology we are using here, the output repository is simply " +"another output artifact." +msgstr "Nachdem die Fedora-RPMs in Gruppen kategorisiert und diese Paketgruppen in verschiedenen Modulen zusammengesetzt wurden, kann die Erstellung dessen, was wir ursprünglich eine Distributions-Variante oder -Edition genannt haben, einfach durch das Kreieren eines flachen YUM-Repositorys erledigt werden – mit allen gewünschten Modulen für dieses Angebot. In der Terminologie, die wir hier verwenden, ist das Ausgabe-Repository einfach ein anderes Ausgabe-Artefakt." + +#: ../../source/design/constructing/back-together.rst:23 +msgid "" +"And of course we can repeat this for different Fedora editions. Having " +"separate GTK and Gnome modules would allow us to include those modules " +"when composing the Fedora Workstation repository, but omit those from the" +" Cloud Edition if we chose. It would also give us a natural way to " +"reflect that Gnome may rebase at a different cadence from the Base " +"Runtime." +msgstr "Und natürlich können wir dies für verschiedene Editionen von Fedora wiederholen. Separate Module für GTK und GNOME würden es uns ermöglichen, diese Module beizufügen, wenn wir das Repository für die Fedora Workstation zusammenstellen – aber diese von der Cloud Edition auszuschließen, wenn wir dies so entscheiden. Es würde uns auch ermöglichen, auf eine natürliche Art und Weise zu reflektieren, dass GNOME mit einer unterschiedlichen Frequenz von der Base-Runtime rebasen kann." + +#: ../../source/design/constructing/back-together.rst:30 +msgid "" +"So today’s editions can simply become different ways of selecting from " +"the available modules." +msgstr "Somit können die derzeitigen Editionen einfach zu verschiedenen Möglichkeiten werden aus den verfügbaren Modulen auszuwählen." + +#: ../../source/design/constructing/back-together.rst:33 +msgid "" +"The installer iso can also be composed from the various modules here, as " +"a separate output artifact. The main difference from the traditional " +"monolithic Compose is that the repositories, images etc. that are " +"composed today are still composed, but each is created as a logically " +"separate build." +msgstr "Die Installations-Iso kann auch aus den verschiedenen Modulen hier zusammengesetzt werden, als ein separates Ausgangs-Artefakt. Der wesentliche Unterschied zu dem traditionellen monolithischen Compose ist, dass die Repositorys, Images, etc., die derzeit zusammengesetzt werden, auch einen Zusammenstellungsprozess durchlaufen, aber jeweils als logisch getrennter Build." + +#: ../../source/design/constructing/back-together.rst:39 +msgid "" +"Add-ons are not drawn above. An add-on is almost completely synonymous " +"with a module here, and the modules composed as above can naturally " +"reflect the composition of add-ons." +msgstr "Add-Ons sind oben nicht eingezeichnet. Ein Add-On ist fast völlig gleichbedeutend mit einem Modul hier. Die Module, die wie oben beschrieben zusammengesetzt wurden, können die Komposition von Add-Ons reflektieren." + +#: ../../source/design/constructing/back-together.rst:44 +msgid "Example: Creating atomic host/container images" +msgstr "Beispiel: Kreieren eines Atomic Host/Container-Images" + +#: ../../source/design/constructing/back-together.rst:46 +msgid "" +"A key point of a broken-down, asynchronous build toolchain is that we can" +" create composes from different modules with different SLAs or " +"lifecycles, and can combine both modules and existing artifacts into yet " +"further artifacts." +msgstr "Ein wesentlicher Punkt einer heruntergebrochenen, asynchronen Build-Toolchain ist es, dass wir Composes erstellen können aus verschiedenen Modulen mit unterschiedlichen SLAs oder Lebenszyklen. Des Weiteren können wir sowohl Module und vorhandene Artefakte in noch weiteren Artefakten kombinieren." + +#: ../../source/design/constructing/back-together.rst:51 +msgid "" +"For example, we can define a tree of required artifact builds for Atomic " +"Host and our Docker container images (each purple box here represents a " +"distinct artifact created by a distinct compose task):" +msgstr "Zum Beispiel können wir einen Baum von benötigten Artefakt-Builds für Atomic Host und unsere Docker-Container-Images erstellen (jede lila Box steht für ein einzelnes, eindeutiges Artefakt, dass durch eine einzelne, eindeutige Compose-Aufgabe kreiert wurde):" + +#: ../../source/design/constructing/back-together.rst:59 +msgid "" +"The Fedora Server and COPR repos today already have distinct SLAs and " +"lifecycles. We could build atomic host trees out of both of those " +"sources, and this can be done easily as a compose step based on the Base " +"Runtime and Container Runtime modules in a modular build of the same " +"components." +msgstr "Der Fedora-Server und die COPR-Repos haben heute bereits unterschiedliche SLAs und Lebenszyklen. Wir können Atomic Host Bäume aus beiden Quellen erzeugen. Dies kann leicht als Compose-Schritt auf Basis der Base- und Container-Runtime-Module in einem modularen Build der gleichen Komponenten erledigt werden." + +#: ../../source/design/constructing/back-together.rst:65 +msgid "" +"But we also need to support layered builds, such as additional container " +"images layered on top of the base image, or Anaconda installs of an " +"existing ostree tree. As long as we can track which compose steps are " +"used as input to each compose task, we can track the relationship between" +" these output artifacts even when we have decomposed the monolithic " +"Compose into many parts." +msgstr "Aber wir müssen auch mehrschichtige Builds unterstützen, wie z. b. zusätzliche Container-Images, die auf dem Basis-Image aufgeschichtet liegen oder Anaconda-Installationen eines vorhandenen OSTree-Baums. Solange wir nachverfolgen können, welche Compose-Schritte als Input für jede Aufgabe im Zusammenstellungsprozess verwendet werden, können wir die Beziehung zwischen diesen Ausgabe-Artefakten auch dann nachverfolgen, wenn wir den monolithischen Compose in viele Teile zerlegt haben." + diff --git a/source/locale/de/LC_MESSAGES/design/constructing/breaking-down.po b/source/locale/de/LC_MESSAGES/design/constructing/breaking-down.po new file mode 100644 index 0000000..3e74b82 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/design/constructing/breaking-down.po @@ -0,0 +1,143 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/design/constructing/breaking-down.rst:2 +msgid "Breaking down the monolithic release" +msgstr "Herunterbrechen des monolithischen Release" + +#: ../../source/design/constructing/breaking-down.rst:4 +msgid "" +"We have many steps in the release pipeline today: starting with bugzilla " +"and dist-git; building and tagging in brew; the errata tool and mirrors " +"for pushing the bits out." +msgstr "Wir haben aktuell sehr viele Schritte in der Release-Pipeline: Beginnend mit Bugzilla und Dist-Git, Building und Tagging in Brew, das Errata-Tool und Mirrors, um das Ganze zu verteilen." + +#: ../../source/design/constructing/breaking-down.rst:8 +msgid "But currently it all comes together in The Compose." +msgstr "Aber momentan kommt alles zusammen in dem Compose." + +#: ../../source/design/constructing/breaking-down.rst:10 +msgid "" +"Remember, I’m not talking about branching and versioning in this " +"particular document. So let’s start with the assumption that we’ve " +"already built our individual packages, and that (for now) we have a flat " +"namespace of binary rpms already built from all our components. That " +"namespace could be living in a yum repository like the rawhide repo, or a" +" koji tag such as fedora-24.0-candidate." +msgstr "Zur Erinnerung: Wir sprechen nicht über Branching und Versionierung in diesem Abschnitt der Dokumentation. Wir beginnen somit mit der Annahme, dass wir unsere individuellen Pakete bereits erzeugt haben und dass wir (erst einmal) einen flachen Namensraum für Binär-RPMs besitzen, die bereits aus all unseren Komponenten gebaut wurden. Dieser Namensraum könnte in einem YUM-Repository wie dem Rawhide-Repo existieren oder ein Koji-Tag sein, wie `fedora-24.0-candidate`." + +#: ../../source/design/constructing/breaking-down.rst:21 +msgid "" +"We build all of the images and repositories, for all of the architectures" +" and their addons, for all of the variants, all at once. Fedora’s " +"Editions have a similar structure." +msgstr "Wir erzeugen alle Images und Repositorys, für alle Architekturen und deren Add-Ons, für alle Varianten, alle auf einmal. Die diversen Editionen von Fedora haben eine sehr ähnliche Struktur." + +#: ../../source/design/constructing/breaking-down.rst:25 +msgid "" +"This served us well once upon a time. It enabled a single consistent " +"major or minor release, and it built everything necessary for that " +"release." +msgstr "Dies hat uns in der Vergangenheit gute Dienste geleistet. Es ermöglichte ein einzelnes konsistentes Major- oder Minor-Release und erzeugte alles Notwendige für das jeweilige Release." + +#: ../../source/design/constructing/breaking-down.rst:29 +msgid "But it now falls short on multiple fronts:" +msgstr "Aber diese Methode versagt nun an mehreren Fronten:" + +#: ../../source/design/constructing/breaking-down.rst:31 +msgid "" +"We have many more types of artifacts being built than are handled by the " +"compose. We have ostree trees and installer images; there are cloud " +"targets such as qcow images and AMIs; and docker base and layered images." +" We have additional, often ad-hoc, incompletely-automated builds to " +"create this additional content." +msgstr "Wir haben wesentlich mehr Arten von Artefakten die erzeugt werden, als vom Compose gemanagt werden. Wir haben OSTree-Bäume und Installer-Images, es gibt Cloud-Varianten, wie QCOW-Images und AMIs, sowie Docker Base und Images mit mehreren Layern. Wir haben zusätzliche, oftmals ad-hoc erstellte, nicht vollständig automatisierte Builds, die diesen zusätzlichen Content erzeugen." + +#: ../../source/design/constructing/breaking-down.rst:36 +msgid "" +"The modularity effort is explicitly trying to get away from the concept " +"of a single monolithic distribution, and to release modular parts of the " +"distribution on independent release cycles." +msgstr "Der Modularity-Ansatz versucht sich explizit von dem Konzept einer einzigen monolithischen Distribution zu lösen und Teile der Distribution modular, mit voneinander unabhängigen Release-Zyklen, zu veröffentlichen." + +#: ../../source/design/constructing/breaking-down.rst:39 +msgid "" +"Scaling: as we increase the number of modules, we do not want to spend " +"the effort of rebuilding the entire distribution when any small part " +"changes. For example, with more container images to build, we should be " +"trying to rebuild only those affected by any change." +msgstr "Skalierung: Wenn wir die Anzahl der Module erhöhen, wollen wir nicht die Anstrengung aufwenden, jedes Mal die gesamte Distribution neu zu bauen, nur weil kleinere Teile sich verändern. Zum Beispiel sollten wir versuchen, mit wachsender Zahl von zu erzeugenden Container-Images, lediglich die neu zu erzeugen, die von den Änderungen betroffen sind." + +#: ../../source/design/constructing/breaking-down.rst:43 +msgid "" +"Self-service: to scale the modular decomposition of the distribution, we " +"will need the ability for individual engineers or groups who own a module" +" or image to build that themselves, not dependent on release engineering." +msgstr "Self-Service: um die modulare Aufteilung der Distribution zu skalieren, benötigen wir für einzelne Ingenieure oder Gruppen, die ein Modul oder ein Image betreuen, die Möglichkeit, dass sie dieses, unabhängig vom Release Engineering, selbst erzeugen können." + +#: ../../source/design/constructing/breaking-down.rst:47 +msgid "" +"Continuous Integration. For automated testing, we want rebuilds to happen" +" automatically when a dependency changes, instead of having to wait for a" +" compose that happens on a predetermined schedule, or when manually " +"triggered by release engineering." +msgstr "Continuous Integration. Für das automatisierte Testen wollen wir, sobald sich eine Abhängigkeit ändert, Rebuilds automatisiert ablaufen lassen. Anstatt warten zu müssen, bis ein Compose zu einem vorgegebenen Zeitpunkt abläuft oder dieser manuell durch das Release Engineering ausgelöst wird." + +#: ../../source/design/constructing/breaking-down.rst:52 +msgid "So how can we address some of these concerns? We take the following steps:" +msgstr "Also, wie können einige dieser Problemstellungen angehen? Wir nehmen folgenden Schritte vor:" + +#: ../../source/design/constructing/breaking-down.rst:55 +msgid "Break down the distribution compose into smaller parts:" +msgstr "Herunterbrechen des Distributions-Compose in kleinere Teile:" + +#: ../../source/design/constructing/breaking-down.rst:56 +msgid "" +"Ensure each part can be composed based on configuration and content in " +"SCM. **Everything must be recomposable based on static content**: never, " +"ever require manual configuration of a compose. That way composes can be " +"automated;" +msgstr "Es ist sicher zustellen, dass jedes Teil zusammengesetzt werden kann, basierend auf Konfiguration und Content im SCM. **Alles muss neu zusammensetzbar sein, basierend auf statischem Content**: Niemals, in keinem Fall, darf eine manuelle Konfiguration eines Compose erforderlich sein. Auf diese Weise können Composes automatisiert werden." + +#: ../../source/design/constructing/breaking-down.rst:60 +msgid "" +"Combine the smaller composes up in stages building towards a full " +"distribution;" +msgstr "Schrittweises kombinieren der kleineren Composes in Phasen, die dann hin zu einer vollständigen Distribution führen." + +#: ../../source/design/constructing/breaking-down.rst:62 +msgid "" +"Record a compose ID for every stage of the compose, and record which " +"compose IDs are used as input to subsequent layered composes" +msgstr "Speichern einer Compose-ID für jede Phase des Compose. Des Weiteren wird protokolliert, welche Compose-IDs verwendet werden als Input für nachfolgende Compose-Layer." + +#: ../../source/design/constructing/breaking-down.rst:64 +msgid "" +"Record the most recent successful compose for each module, so that failed" +" composes (or composes that fail testing) do not impact layered modules" +msgstr "Aufzeichnen der jeweils aktuell erfolgreichsten Composes für jedes Modul, so dass fehlgeschlagene Composes (oder Composes, die die Testläufe nicht bestanden haben) keine Auswirkungen auf Modul-Layer haben können." + +#: ../../source/design/constructing/breaking-down.rst:67 +msgid "" +"Optionally, we can automate the process of chain composes and add CI to " +"the mix to achieve a fully automatic build toolchain." +msgstr "Optional können wir den Prozess des Verkettens von Composes automatisieren und CI zu dem Mix hinzufügen, um eine vollständig automatisierte Build-Toolchain zu erreichen." + diff --git a/source/locale/de/LC_MESSAGES/design/constructing/compose-distribution.po b/source/locale/de/LC_MESSAGES/design/constructing/compose-distribution.po new file mode 100644 index 0000000..9f384f0 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/design/constructing/compose-distribution.po @@ -0,0 +1,423 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/design/constructing/compose-distribution.rst:2 +msgid "Incremental compose of the distribution" +msgstr "Inkrementeller Compose der Distribution" + +#: ../../source/design/constructing/compose-distribution.rst:4 +msgid "**1. Break the distribution into distinct modules**" +msgstr "**1. Aufbrechen der Distribution in einzelne Module**" + +#: ../../source/design/constructing/compose-distribution.rst:6 +msgid "" +"Let’s take this in stages. We can start by simply assigning individual " +"packages to modules (at the sub-package level: we may have a need to have" +" a library in a base module but have its -devel subpackage in a " +"developer-only module, for example.) This ignores the branching of " +"packages and modules, but as stated before, that’s a separate topic." +msgstr "Wir zerlegen dies einmal in Phasen. Wir können damit anfangen, einzelne Pakete Modulen zuzuweisen (auf Unterpaketebene: Wir haben eventuell Bedarf eine Bibliothek in einem Basismodul zu haben, aber z. B. sein `devel`-Unterpaket in einem Modul ausschließlich für Entwickler.). Dies ignoriert das Branching von Paketen und Modulen, aber wie bereits betont, ist dies ein separates Thema." + +#: ../../source/design/constructing/compose-distribution.rst:12 +msgid "" +"Note: `The module boundaries here are just examples.` They are " +"illustrations to show how we can break the monolithic distribution up. " +"They are *not* proposals that we should draw the lines between modules in" +" any particular places: that is an entirely separate discussion." +msgstr "Hinweis: `Die Modulverbindungen hier sind lediglich Beispiele.` Sie sind Illustrationen, die zeigen, wie wir die monolithische Distribution aufbrechen können. Sie sind *keine* Vorschläge, an welchen Stellen wir die Verbindungslinien zwischen den Modulen ziehen sollten: Das ist eine hiervon völlig losgelöste Diskussion." + +#: ../../source/design/constructing/compose-distribution.rst:17 +msgid "" +"We can start with some obvious “core” modules such as hardware " +"enablement, system runtime and core application runtime." +msgstr "Wir beginnen mit einigen offensichtlichen »Kern«-Modulen, wie Hardware-Enablement (HWE), System-Runtime und Kernanwendungs-Runtime." + +#: ../../source/design/constructing/compose-distribution.rst:20 +msgid "" +"The installer needs GTK and Anaconda; let’s make sure we have homes for " +"those." +msgstr "Das Installationsprogramm benötigt GTK und Anaconda. Es ist sicherzustellen, dass diese ein Zuhause haben." + +#: ../../source/design/constructing/compose-distribution.rst:23 +msgid "" +"This leaves a lot of content currently not assigned to a module. That’s " +"fine, we can figure out how to handle those; for example, we could choose" +" to define a module for “uncategorised” for now." +msgstr "Dies lässt immer noch eine Menge an Content übrig, der derzeit keinem Modul zugewiesen ist. Das ist in Ordnung, wir können herausfinden, wie wir diesen handhaben. Zum Beispiel könnten wir uns entscheiden vorläufig ein Modul für `uncategorised` zu definieren." + +#: ../../source/design/constructing/compose-distribution.rst:27 +msgid "" +"All we have done so far is to draw boundaries around groups of existing " +"packages:" +msgstr "Alles, was wir bisher getan haben, ist es, Grenzlinien rund um Gruppen von bestehenden Paketen zu ziehen:" + +#: ../../source/design/constructing/compose-distribution.rst:34 +msgid "" +"We can add Apache, php and mariadb, and we could have the components of a" +" LAMP stack, etc; there are plenty more groups we can imagine here." +msgstr "Wir können Apache, PHP und MariaDB hinzufügen und wir könnten die Komponenten eines LAMP-Stacks haben, usw. Es gibt eine Fülle weiterer Gruppen, die wir uns hier vorstellen können." + +#: ../../source/design/constructing/compose-distribution.rst:37 +msgid "" +"Note: This picture shows a static allocation of packages to modules. So, " +"modules have a **static manifest**. This is deliberate:" +msgstr "Hinweis: Dieses Bild zeigt eine statische Zuordnung der Pakete zu Modulen. Module haben ein **statisches Manifest**. Das ist bewusst so gewählt:" + +#: ../../source/design/constructing/compose-distribution.rst:40 +msgid "" +"If, over time, a package in a module picks up a new dependency, then it " +"should be a human decision to determine which module that new dependency " +"should live in (or even whether we want that dependency at all.) This " +"allows us to combat dependency sprawl over time, and also to record *why*" +" a particular package lives in a particular module, at the time we add a " +"dependency." +msgstr "Wenn im Laufe der Zeit ein Paket in einem Modul eine neue Abhängigkeit benötigt, dann sollte es eine menschliche Entscheidung geben, festzustellen, in welchem Modul diese neue Abhängigkeit existieren sollte (oder auch, ob wir diese Abhängigkeit überhaupt wollen). Dies ermöglicht es uns, Abhängigkeitswildwuchs, der im Laufe der Zeit entsteht, zu bekämpfen. Ebenso kann dabei protokolliert werden, *warum* ein bestimmtes Paket in einem bestimmten Modul existiert, zu dem Zeitpunkt, zu dem wir eine Abhängigkeit hinzufügen." + +#: ../../source/design/constructing/compose-distribution.rst:47 +msgid "" +"To enable an engineer to manually allocate new dependencies to modules, " +"it it necessary that module manifests should not just be automatically " +"generated. We consider that manifest to be one of the defining properties" +" of the module." +msgstr "Um es einem Entwickler zu ermöglichen manuell neue Abhängigkeiten zu Modulen hinzuzufügen, ist es notwendig, dass Modulmanifeste nicht nur automatisch generiert werden. Wir betrachten das Manifest als eines der definierenden Eigenschaften des Moduls." + +#: ../../source/design/constructing/compose-distribution.rst:52 +msgid "**2. Automate the composing of modules from packages**" +msgstr "**2. Automatisieren des Compose von Modulen aus Paketen**" + +#: ../../source/design/constructing/compose-distribution.rst:54 +msgid "" +"We now want to compose a module. Bear in mind, “composing” the module " +"here involves assembling pre-existing binaries: it’s more a “createrepo” " +"than “rpmbuild” (and is similar to a “puddle” build in current RCM " +"terms.) And the automation we’re talking about here is the execution of " +"the module compose, even if the compose is actually triggered manually." +msgstr "Wir wollen nun ein Modul zusammensetzen. Denken Sie daran, der »Compose« des Moduls beinhaltet hier das Zusammenfügen bereits existierender Binärdateien: Es ist mehr ein ``createrepo`` als ein ``rpmbuild`` (und ist vergleichbar mit einem `puddle`-Build in aktueller RCM-Terminologie). Die Automatisierung, über die wir hier reden, ist die Durchführung des Modul-Compose, auch wenn der Compose derzeitig manuell ausgelöst wird." + +#: ../../source/design/constructing/compose-distribution.rst:60 +msgid "" +"A module compose is now simply the creation of a yum repository of the " +"required packages or subpackages, with the addition of a small amount of " +"module metadata as described in :doc:`../building-naming`." +msgstr "Ein Modul zusammenzustellen bedeutet jetzt einfach die Schaffung eines YUM-Repository der benötigten Pakete oder Unterpakete, mit dem Zusatz einer geringen Menge von Modul-Metadaten, wie beschrieben in :doc:`../building-naming`." + +#: ../../source/design/constructing/compose-distribution.rst:68 +msgid "" +"We plan the module definition metadata living in dist-git, similarly to " +"how we currently maintain component spec files, sources definitions and " +"patches. Regardless of where it lives, **the module compose must be well-" +"defined based on static content.** The essence of an automated build " +"system is that when a compose is required, there should be no compose-" +"time configuration added; everything to compose the module is stored in " +"SCM and should be completely repeatable from there." +msgstr "Wir planen die Metadaten für die Moduldefinition in Dist-Git existieren zu lassen, ähnlich wie wir derzeit ``.spec``-Dateien der Komponenten betreuen, Definitionen der Quellen und Patches. Unabhängig davon, wo sie gehalten werden, **der Modul-Compose muss klar definiert sein, basierend auf statischem Content**. Die Essenz eines automatisierten Build-Systems ist es, dass, wenn ein Compose erforderlich ist, keine Konfiguration zur Compose-Zeit hinzugefügt werden sollte. Alles, was benötigt wird, um das Modul zusammenzusetzen ist im SCM gespeichert und sollte von dort vollständig reproduzierbar sein." + +#: ../../source/design/constructing/compose-distribution.rst:76 +msgid "" +"This workflow mirrors existing practice for building binaries, where a " +"developer expects to be able to build and test an rpm locally for a " +"single architecture, before submitting to the build system to be built on" +" multiple architectures. In the same way, we would expect the build-" +"system module compose tool to pull together the necessary packages and to" +" create arch-specific modules for each required architecture." +msgstr "Dieser Workflow spiegelt die existierende Praxis für den Bau von Binärdateien, bei der ein Entwickler erwartet in der Lage zu sein, ein RPM lokal für eine einzelne Architektur zu erstellen und zu testen, bevor dieses an das Build-System übermittelt wird, um für mehrere Architekturen gebaut zu werden. In gleicher Weise würden wir erwarten, dass das Modul-Compose-Tool des Build-Systems die notwendigen Pakete heranzieht, um die verschiedenen architekturspezifischen Module zu erstellen." + +#: ../../source/design/constructing/compose-distribution.rst:83 +msgid "" +"We mentioned before that we expect modules to have a static manifest. " +"During module compose, however, we would still expect to perform " +"*repoclosure* on the module: ie. to verify that the module satisfies the " +"dependency requirements of all packages it includes. Failure of " +"repoclosure should constitute a failed compose of the module. The tooling" +" may still attempt to solve missing dependencies automatically, but " +"should only report to the user which packages could be included to " +"satisfy those dependencies; it should not include those in the output " +"without confirmation from the module owner." +msgstr "Wie bereits zuvor erwähnt, erwarten wir, dass die Module ein statisches Manifest besitzen. Während des Modul-Compose würden wir allerdings erwarten, dass ein ``repoclosure`` auf dem Modul durchgeführt wird. Das heisst sicherzustellen, dass das Modul die Abhängigkeitsanforderungen aller Pakete erfüllt, die es enthält. Ein fehlgeschlagenes ``repoclosure`` sollte in einem fehlgeschlagenen Compose des Moduls münden. Das Werkzeug kann noch versuchen, fehlende Abhängigkeiten automatisch zu lösen, aber sollte es letztendlich lediglich dem Benutzer melden, welche Pakete hinzugefügt werden sollten, um diese Abhängigkeiten zu erfüllen. Es sollte diese nicht der Ausgabe hinzufügen, ohne eine Bestätigung von dem Modulbesitzer." + +#: ../../source/design/constructing/compose-distribution.rst:93 +msgid "" +"To automate module composes it will be vital to know exactly which " +"version of which packages should be used to compose any given module (eg." +" for koji builds, this would be selected by koji tag.) The important " +"point is that all of this should be configured in the module metadata so " +"that we can compose the entire module automatically." +msgstr "Um das Zusammensetzen von Modulen zu automatisieren, ist es notwendig zu wissen, welche Version welcher Pakete exakt verwendet werden sollte, um jegliches gegebene Modul zusammenzustellen (z. B. für Koji-Builds würde diese mittels Koji-Tags ausgewählt werden). Der wichtige Punkt ist, dass all dies in den Metadaten des Moduls konfiguriert werden sollte, so dass wir das gesamte Modul automatisiert zusammensetzen können." + +#: ../../source/design/constructing/compose-distribution.rst:99 +msgid "**3. Automate the composing of stacks from modules**" +msgstr "**3. Automatisieren des Zusammensetzens von Modul-Stacks**" + +#: ../../source/design/constructing/compose-distribution.rst:101 +msgid "" +"Recall that a stack is nothing more than a module that depends on other " +"modules; the stack simply refers to that whole tree of dependencies." +msgstr "Erinnern Sie sich daran, dass ein Stack nichts anderes ist als ein Modul, das von anderen Modulen abhängig ist. Der Stack verweist lediglich auf diesen ganzen Baum von Abhängigkeiten." + +#: ../../source/design/constructing/compose-distribution.rst:104 +msgid "" +"So composing a stack requires nothing more than composing a module that " +"has dependencies. We define that top-level module via a metadata file in " +"dist-git just as for any other module. The required dependent modules are" +" listed in the module’s defining metadata. This is important: just as for" +" a compose of an independent module, the entire module compose is well-" +"defined based on static content." +msgstr "So erfordert das Zusammenstellen einen Stacks nicht mehr als die Zusammenstellung eines Moduls, das Abhängigkeiten besitzt. Wir definieren das Top-Level-Modul über eine Metadaten-Datei in Dist-Git, genau wie bei jedem anderen Modul. Die erforderlichen abhängigen Module sind in den Metadaten, die das Modul definieren, aufgeführt. Dies ist wichtig: Wie bei dem Zusammensetzen eines eigenständigen Moduls, basiert auch hier der gesamte Modul-Compose wohldefiniert auf statischem Inhalt." + +#: ../../source/design/constructing/compose-distribution.rst:111 +msgid "" +"The only difference in the compose of such a higher-level module is in " +"the checking of internal rpm dependencies: both the repoclosure test, and" +" any hinting done to suggest missing packages, should be performed on " +"*all* packages in the entire stack, including all of the packages from " +"other modules that this module depends on." +msgstr "Der einzige Unterschied in dem Compose so eines übergeordneten Moduls besteht in der Überprüfung der internen RPM-Abhängigkeiten: Sowohl der ``repoclosure``-Test und jegliche Hinweise, um fehlende Pakete vorzuschlagen, sollte auf *allen* Paketen in dem gesamten Stack durchgeführt werden. Dies einschließlich aller Pakete von anderen Modulen, von denen dieses Modul abhängig ist." + +#: ../../source/design/constructing/compose-distribution.rst:117 +msgid "" +"Of course, we may be composing a module multiple times. And to manage " +"consistency between modules when things are changing, we really need to " +"be able to determine exactly which version of a module has been composed " +"from exactly which versions of its dependencies. So \"each module compose" +" must have a unique compose identifier\" of some form; and during a " +"layered module compose, we must record the compose IDs of all the modules" +" used as input for this compose." +msgstr "Natürlich können wir ein Modul mehrmals zusammensetzen. Und um die Konsistenz zwischen den Modulen zu verwalten, wenn sich Dinge ändern, müssen wir wirklich in der Lage sein exakt festzustellen, welche Version eines Moduls aus genau welchen Versionen seiner Abhängigkeiten zusammengestellt wurde. Also **jeder Compose eines Moduls muss einen einzigartigen Bezeichner besitzen**, in irgendeiner Form. Und während eines mehrschichtigen Modul-Compose müssen wir die Compose-IDs aller Module erfassen, die als Input für diesen Compose verwendet wurden." + +#: ../../source/design/constructing/compose-distribution.rst:125 +msgid "" +"So to compose a PHP-on-Apache stack we might simply compose the base " +"runtime module, then a layered Apache module, and finally a php module on" +" top, in that order:" +msgstr "Also, um einen PHP-auf-Apache-Stack zusammenzustellen, müssen wir möglicherweise einfach das Base-Runtime-Modul zusammenstellen, dann ein geschichtetes Apache-Modul und schließlich ein PHP-Modul oben drauf. In dieser Reihenfolge:" + +#: ../../source/design/constructing/compose-distribution.rst:133 +msgid "**4. Automate the composing of images and other artifacts**" +msgstr "**4. Automatisieren des Composing von Images und anderen Artefakten**" + +#: ../../source/design/constructing/compose-distribution.rst:135 +msgid "" +"So, now we’ve got enough modules to represent entire stacks of content " +"suitable for installation to solve some user problem. But still, these " +"are no more than repositories of available content; we still need to " +"actually install them to use them." +msgstr "So, jetzt haben wir genug Module zur Darstellung ganzer Stacks von Content, die geeignet sind für die Installation, um einige Probleme von Benutzern zu lösen. Aber zu diesem Zeitpunkt sind diese nicht mehr als Repositorys mit verfügbaren Inhalten. Wir müssen sie immer noch installieren, um sie zu benutzen." + +#: ../../source/design/constructing/compose-distribution.rst:140 +msgid "" +"Sometimes the user will install them themselves; the module client can " +"automate the complete installation of an entire stack of dependent " +"modules seamlessly." +msgstr "Manchmal wird der Benutzer sie selbst installieren. Der Modul-Client kann die komplette Installation aus einen ganzen Stapel von abhängigen Modulen nahtlos automatisieren." + +#: ../../source/design/constructing/compose-distribution.rst:144 +msgid "" +"But sometimes we’ll want to pre-install the content into some other " +"artifact: a container image, an installer iso, or an ostree tree, for " +"subsequent delivery to the user. That’s fine, we can drive whatever tools" +" we need to build these artifacts. The only principles we rely on are the" +" ones we’ve already mentioned:" +msgstr "Aber manchmal wollen wir den Content in einem anderen Artefakt vorinstallieren: ein Container-Image, ein Installer-Iso oder ein OSTree-Baum, für die anschließende Verteilung an die Nutzer. Das ist in Ordnung, wir können jegliche Werkzeuge verwenden, die wir benötigen, um diese Artefakte zu bauen. Die einzigen Grundsätze, an die wir uns halten müssen, sind die, die wir bereits erwähnt haben:" + +#: ../../source/design/constructing/compose-distribution.rst:150 +msgid "" +"We need to compose the images from static configuration/manifests: no " +"manual invocation of builds with magic command line parameters, the tools" +" should be able to find all the configuration/input they need from SCM " +"etc." +msgstr "Wir müssen die Images aus statischen Konfigurationen/Manifesten zusammensetzen: Kein manueller Aufruf des Builds mit magischen Kommandozeilen-Parametern. Die Tools sollten in der Lage sein, jede Konfiguration/Eingabe zu finden, die sie vom SCM usw. benötigen." + +#: ../../source/design/constructing/compose-distribution.rst:154 +msgid "" +"Record compose IDs of everything we consume as input, and generate a " +"build ID from the output;" +msgstr "Erfassen der Compose-IDs zu allem, was wir als Eingabe konsumieren und generieren einer Build-ID von der Ausgabe." + +#: ../../source/design/constructing/compose-distribution.rst:156 +msgid "" +"Each compose produces just one artifact (or as few as possible); no " +"monolithic composes that try to build massive amounts of the distro in a " +"single step. We end up with the same traceability because the composes " +"can all use the same exact inputs guaranteeing the artifacts are the same" +" except for their distribution packaging." +msgstr "Jeder Compose produziert nur ein Artefakt (oder so wenig wie möglich). Keine monolithischen Composes, die versuchen, große Mengen der Distribution in einem einzigen Schritt zu bauen. Wir enden mit der gleichen Rückverfolgbarkeit, weil die Zusammenstellungen alle genau die gleichen Inputs verwenden können. Dies garantiert, dass die Artefakte identisch sind, außer deren Paketierung für die Distribution." + +#: ../../source/design/constructing/compose-distribution.rst:162 +msgid "**5. What happens when a compose fails?**" +msgstr "**5. Was passiert, wenn ein Compose scheitert?**" + +#: ../../source/design/constructing/compose-distribution.rst:164 +msgid "" +"One problem with a monolithic compose is that a single problem can fail " +"the entire compose." +msgstr "Ein Problem mit einem monolithischen Compose ist, dass ein einziges Problem den gesamten Compose scheitern lassen kann." + +#: ../../source/design/constructing/compose-distribution.rst:167 +msgid "" +"How do we prevent a similar situation where a broken compose of a Base " +"Runtime module causes compose failures for all other modules depending on" +" it?" +msgstr "Wie können wir eine ähnliche Situation verhindern, bei der ein fehlerhafter Compose eines Base-Runtime-Moduls Fehler verursacht bei der Zusammenstellung aller anderen Module, die von diesem abhängen?" + +#: ../../source/design/constructing/compose-distribution.rst:171 +msgid "" +"Having a granular compose process actually improves this situation " +"significantly. We simply need to remember the most recent *successful* " +"compose for any given module, and use that compose for any subsequent " +"layered composes." +msgstr "Ein granularer Compose-Prozess verbessert diese Situation erheblich. Wir müssen uns einfach daran erinnern, welche die letzte *erfolgreiche* Zusammensetzung für jedes Modul war. Diese verwenden wir dann jeweils für jeden nachfolgenden Compose-Layer." + +#: ../../source/design/constructing/compose-distribution.rst:180 +msgid "" +"So composing modules here from left to right still works fine; the failed" +" compose #3 of our base runtime module does not prevent a subsequent " +"compose #4 of the Apache module from succeeding; that compose simply " +"picks up the most recent successful compose of the base runtime. And when" +" a new compose of the base runtime does eventually succeed, then it " +"becomes available to future composes of the Apache module on top." +msgstr "Somit funktioniert die Komposition von Modulen hier von links nach rechts dennoch gut. Der gescheiterte Compose in #3 unseres Base-Runtime-Moduls kann nicht verhindern, dass eine anschließende Zusammensetzung des Apache-Moduls in #4 erfolgreich verläuft. Dieser Compose nimmt einfach den letzten erfolgreichen Compose der Base-Runtime. Und wenn eine neue Zusammensetzung der Base-Runtime schließlich erfolgreich verläuft, dann steht diese für zukünftige Zusammenstellungen des darauf aufbauenden Apache-Moduls zur Verfügung." + +#: ../../source/design/constructing/compose-distribution.rst:187 +msgid "**6. Chaining recomposes**" +msgstr "**6. Verketten von Recomposes**" + +#: ../../source/design/constructing/compose-distribution.rst:189 +msgid "" +"So far we have talked about “composing” a module in terms of re-running " +"the creation of that module from its component parts (the packages it " +"contains, and the metadata belonging to the module) on demand. When a " +"module compose is requested, the build system must have enough " +"information to complete that compose on its own, but the build system " +"does not necessarily know itself *when* to compose a module." +msgstr "Bisher haben wir über das »Composing« eines Moduls bei Bedarf gesprochen, im Hinblick auf die erneute Ausführung des Compose dieses Moduls aus seinen Komponenten (die Pakete, die es enthält und die Metadaten, die zum Modul gehören). Wenn ein Modul-Compose angefordert wird, muss das Build-System genügend Informationen besitzen, um den Zusammenstellungsprozess eigenständig abzuschließen. Allerdings weiß das Build-System nicht unbedingt von sich aus, *wann* ein Modul zusammengesetzt werden soll." + +#: ../../source/design/constructing/compose-distribution.rst:196 +msgid "" +"But of course, we can automate that part too. Just as a CI package " +"workflow might want to rebuild and retest an rpm when a dist-git event " +"occurs, we want to be able to recompose both modules and artifacts " +"whenever their content changes." +msgstr "Aber natürlich können wir auch diesen Teil automatisieren. So wie möglicherweise ein Workflow für ein CI-Paket ein RPM neu erstellen und testen möchte, wenn ein Dist-Git-Ereignis eintritt, so wollen wir in der Lage sein, sowohl Module als auch Artefakte wieder neu zusammenzusetzen, wann immer sich deren Inhalte ändern." + +#: ../../source/design/constructing/compose-distribution.rst:201 +msgid "" +"The details of each individual task here are not important; indeed, it is" +" important to include many different types of tasks in this automation. " +"Recomposing a module may be triggered by an rpm rebuild; that recompose " +"may trigger other module recomposes, and additionally may trigger other " +"image rebuilds. We may add CI to the mix so that testing tasks are also " +"triggered when appropriate." +msgstr "Die Details der einzelnen Aufgaben hier sind nicht wichtig. Von Relevanz ist es, viele verschiedene Arten von Aufgaben in dieser Automatisierung einzubringen. Die Neukomposition eines Moduls kann ausgelöst werden durch den Rebuild eines RPMs. Dieser Recompose kann weitere Neukompositionen von Modulen auslösen und zusätzlich andere Rebuilds von Images auslösen. Wir können CI zu diesem Mix hinzufügen, so dass Testaufgaben bei Bedarf ausgelöst werden, wenn es sinnvoll ist." + +#: ../../source/design/constructing/compose-distribution.rst:208 +msgid "" +"What *is* important is that the chaining of tasks is automatic. When " +"something changes in the content tree, the build system **must** know (or" +" be able to tell us) what else needs to be rebuilt or recomposed as a " +"consequence; it **must** have the information needed to perform those " +"rebuilds without additional manual configuration; and it **should** have " +"the ability to trigger those rebuilds automatically subject to rel-eng " +"policy." +msgstr "Was wichtig *ist*, ist dass die Verkettung von Aufgaben automatisiert erfolgt. Sobald sich etwas im Content-Baum ändert, **muss** das Build-System wissen (oder in der Lage sein, uns zu sagen), was daraus resultierend noch neu erstellt oder erneut zusammengesetzt werden muss. Es **muss** die benötigten Informationen besitzen, um diese Rebuilds ohne zusätzliche manuelle Konfiguration durchzuführen. Ebenso **sollte** es die Fähigkeit besitzen, diese Rebuilds automatisch konform zu den Richtlinien des Release Engineering anzustoßen" + +#: ../../source/design/constructing/compose-distribution.rst:216 +msgid "Which leads us to:" +msgstr "Das führt uns zu:" + +#: ../../source/design/constructing/compose-distribution.rst:218 +msgid "**7. The Release Concept**" +msgstr "**7. Das Release-Konzept**" + +#: ../../source/design/constructing/compose-distribution.rst:220 +msgid "" +"A CI / chain-build toolchain is fundamentally asynchronous. Content is " +"rebuilt, recomposed or re-tested when its dependencies change. This is " +"deliberate: a modular release is, by definition, attempting to break up " +"the monolithic, synchronous Compose." +msgstr "Eine Toolchain für CI/Chain-Build ist grundsätzlich asynchron. Inhalte werden neu erzeugt, neu zusammengesetzt oder erneut getestet, sobald ihre Abhängigkeiten sich ändern. Das ist gewollt: Ein modulares Release ist, per Definition, der Versuch, den monolithischen, synchronen Compose aufzubrechen." + +#: ../../source/design/constructing/compose-distribution.rst:225 +msgid "" +"But ultimately, Fedora still wants to be able to produce a planned " +"release spanning many modules, and users still want to have controlled, " +"predictable releases, rather than having modules dribble into a release " +"in drips. We still have major release events such as Fedora major/minor " +"updates." +msgstr "Aber letztendlich, möchte Fedora weiterhin in der Lage sein, ein geplantes Release zu produzieren, das viele Module umfasst. Ebenso wollen Benutzer immer noch kontrollierte, vorhersehbare Releases erhalten, anstatt Module in ein Release hereintropfen zu sehen. Wir haben immer noch Major-Releases, ebenso wie Major-/Minor-Updates in Fedora." + +#: ../../source/design/constructing/compose-distribution.rst:231 +msgid "" +"So decomposing the release into loosely-coupled compose steps is all well" +" enough, but we need more than just chain rebuilds to bring it all back " +"together. We need to know what modules need to come together on what date" +" to make a given release." +msgstr "So ist das Zerlegen des Release in lose miteinander verbundene Compose-Schritte schon eine gute Sache, aber wir benötigen mehr als nur Rebuilds zu verketten, um alles wieder zusammenzufügen. Wir müssen wissen, welche Module an welchem Datum zusammenkommen müssen, um ein bestimmtes Release zu erzeugen." + +#: ../../source/design/constructing/compose-distribution.rst:236 +msgid "" +"So we introduce the formal concept of a **release** as a concept that " +"defines requirements across multiple modules. The release would define, " +"for example:" +msgstr "Somit führen wir das formale Konzept eines **Release** ein, als ein Konzept, das über mehrere Module hinweg Voraussetzungen definiert. Zum Beispiel würde das Release definieren:" + +#: ../../source/design/constructing/compose-distribution.rst:240 +msgid "" +"Which modules are included in the release (and, if those modules have " +"multiple versions available, which versions come together for this " +"release);" +msgstr "Welche Module in dem Release enthalten sind (und sofern diese Module in mehreren Versionen verfügbar sind, welche Versionen für dieses Release zusammengestellt werden)." + +#: ../../source/design/constructing/compose-distribution.rst:243 +msgid "The date scheduled for the release;" +msgstr "Das Datum, das für dieses Release vorgesehen ist." + +#: ../../source/design/constructing/compose-distribution.rst:244 +msgid "" +"Minimum SLA and lifecycle expectations for the release, so that we can " +"verify during planning that all the required modules and all their " +"dependencies have the required support" +msgstr "Minimale SLA- und Lifecycle-Erwartungen für das Release, damit wir während der Planung überprüfen können, dass all die benötigten Module und deren Abhängigkeiten, die benötigte Unterstützung haben." + +#: ../../source/design/constructing/compose-distribution.rst:248 +msgid "" +"This information cannot be inferred from the individual modules " +"comprising a release. The reason is simple: it’s a primary assumption in " +"modularity that any one module may be included in multiple products " +"and/or multiple releases." +msgstr "Diese Information kann nicht aus den einzelnen Modulen abgeleitet werden aus denen ein Release besteht. Der Grund ist einfach: Es ist eine primäre Annahme in Modularity, dass jegliches Modul in mehreren Produkten und/oder mehreren Releases enthalten sein kann." + +#: ../../source/design/constructing/compose-distribution.rst:253 +msgid "" +"Furthermore, there is a chicken-and-egg situation involving build-system " +"automation of modules. If module definitions live in dist-git, then how " +"does a build system know which dist-git repositories to look up to know " +"what builds need to be performed automatically? The release is a natural " +"place to define that." +msgstr "Darüber hinaus gibt es eine Henne-Ei-Situation mit der Automatisierung von Modulen in Build-Systemen. Wenn Modul-Definitionen in Dist-Git existieren, woher weiß dann das Build-System, in welchen Dist-Git-Repositorys nachzuschauen ist, um zu wissen, welche Builds automatisiert durchgeführt werden müssen? Das Release ist ein natürlicher Ort dies zu definieren." + +#: ../../source/design/constructing/compose-distribution.rst:259 +msgid "" +"Note: Technically, a release could easily be encoded as yet another dist-" +"git module itself, one with many dependencies and no additional content " +"of its own. It could be similar to an rpm meta-package in this regard. " +"But it is still a distinct concept." +msgstr "Hinweis: Technisch gesehen, könnte eine Release leicht als weiteres Dist-Git-Modul verstanden werden, eins mit vielen Abhängigkeiten und keinem zusätzlichen eigenständigen Content. Es könnte in dieser Hinsicht ähnlich wie ein RPM-Metapaket sein. Aber es ist immer noch ein eigenständiges Konzept." + diff --git a/source/locale/de/LC_MESSAGES/design/versioning.po b/source/locale/de/LC_MESSAGES/design/versioning.po new file mode 100644 index 0000000..81f46bb --- /dev/null +++ b/source/locale/de/LC_MESSAGES/design/versioning.po @@ -0,0 +1,118 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/design/versioning.rst:2 +msgid "Module versioning and branching" +msgstr "Modul-Versionierung und Branching" + +#: ../../source/design/versioning.rst:4 +msgid "" +"The primary core principle of Modularity is that our content should be " +"released not as large, monolithic distribution releases, but in units of " +"smaller modules designed to be assembled in different combinations." +msgstr "Das elementare Grundprinzip von Modularity ist es, dass unser Content nicht als große, monolithische Distributions-Releases veröffentlicht werden sollen, sondern in Einheiten von kleineren Modulen, die so konzipiert sind, dass sie in verschiedenen Kombinationen zusammengefügt werden können." + +#: ../../source/design/versioning.rst:8 +msgid "" +"Closely related is a second core principle: we should be able to release " +"new major versions of these modules on their own schedules to serve a " +"component's requirements; they should not all be tied to the master " +"cadence of today’s major release cycles." +msgstr "Eng verbunden damit ist ein zweites Grundprinzip: Wir sollten in der Lage sein, neue Hauptversionen dieser Module mit ihren eigenen Zeitplänen zu veröffentlichen, um den Anforderungen von Komponenten zu genügen. Sie sollten nicht alle an die Mastertaktung der jeweils aktuellen Major-Releasezyklen gebunden sein." + +#: ../../source/design/versioning.rst:13 +msgid "" +"So, at a deep level, Modularity requires us to branch and version modules" +" independently of each other." +msgstr "Also, auf einem tieferen Level, zwingt uns Modularity dazu Module unabhängig voneinander zu verzweigen und zu versionieren." + +#: ../../source/design/versioning.rst:16 +msgid "" +"Yet we need to control this complexity: the engineering involved has to " +"be sustainable, and the combinations we offer to the user need to be " +"manageable. This is especially true as different tools represent branches" +" in different ways (eg. bugzilla represents branches as the “version” " +"field for a product, and also has version-specific flags; koji has koji " +"tags which act as branches, etc.)" +msgstr "Dennoch müssen wir diese Komplexität kontrollieren: Das eingebundene Engineering muss kontinuierlich sein und die Kombinationen, die wir dem Benutzer bieten, müssen verwaltbar sein. Dies gilt insbesondere, da verschiedene Tools Branches auf unterschiedliche Weise darstellen (z. B. stellt Bugzilla Zweige als Feld »Version« für ein Produkt dar und hat auch versionsspezifische Flaggen; Koji hat Koji-Tags, die als Zweige fungieren, usw.)" + +#: ../../source/design/versioning.rst:23 +msgid "" +"This leads to some complex constraints, which we will explore in this " +"document." +msgstr "Dies führt zu einigen komplexen Restriktionen, die wir in diesem Dokument erkunden werden." + +#: ../../source/design/versioning.rst:26 +msgid "" +"Ultimately, we can identify many distinct variants on branching: " +"sometimes different parts of the release pipeline end up with multiple " +"different views of the underlying branches. Just consider Fedora fXX " +"branches: these either look like a continuous update stream to the end " +"user, or *some* of the branches end up having distinct lifespans." +msgstr "Letztendlich können wir viele unterschiedliche Varianten beim Branching identifizieren: Manchmal enden verschiedene Teile der Release-Pipeline mit mehreren unterschiedlichen Ansichten der zugrundeliegenden Zweige. Denken Sie nur an Fedora fXX Zweige: entweder sehen diese aus wie ein kontinuierlicher Update-Stream an den Endverbraucher oder *einige* der Äste enden mit unterschiedlichen Laufzeiten." + +#: ../../source/design/versioning.rst:32 +msgid "" +"So while a single consistent end-to-end branching model for any module is" +" possible in simple cases, it is unlikely to satisfy all the product " +"demands for complex release structures. This suggests an approach to " +"branching involving:" +msgstr "Während also ein einziges konsistentes End-to-End Branching-Modell für jedes Modul in einfachen Fällen möglich ist, ist es unwahrscheinlich, allen Produktanforderungen für komplexe Release-Strukturen gerecht zu werden. Dies legt einen Ansatz zur Verzweigung nahe, der Folgendes beinhaltet:" + +#: ../../source/design/versioning.rst:37 +msgid "" +"A centralised representation of the current branching at any point in " +"time;" +msgstr "Eine zentralisierte Darstellung der derzeitigen Verzweigung an jedem beliebigen Punkt in der Zeit." + +#: ../../source/design/versioning.rst:39 +msgid "" +"Retain separate branch definitions in our various tools such as bugzilla," +" koji, bodhi, etc, as we have today;" +msgstr "Separate Branch-Definitionen sind in unseren verschiedenen Tools (wie Bugzilla, Koji, Bodhi, etc.) so beizubehalten, wie wir sie heute haben." + +#: ../../source/design/versioning.rst:41 +msgid "" +"A flexible scripting approach to automating creation of new branches and " +"key transitions on existing branches (dev to beta to release etc), to " +"keep branches on the different tools synchronised." +msgstr "Ein flexibler Scripting-Ansatz zum Automatisieren der Generierung neuer Zweige und von relevanten Übergängen auf bestehenden Zweigen (Dev zu Beta zu Release etc.), um Zweige auf den verschiedenen Tools synchronisiert zu halten." + +#: ../../source/design/versioning.rst:45 +msgid "" +"This splits *mechanism* — the central branching repository and the branch" +" definitions in the different tools — from *policy* — the specific " +"branches and transitions actioned by the scripts." +msgstr "Dies trennt den *Mechanismus* — das zentrale Branching-Repository und die Branch-Definitionen in den verschiedenen Tools — von den *Richtlinien* — die spezifischen Zweige und Übergänge, die durch die Skripte angestoßen werden." + +#: ../../source/design/versioning.rst:49 +msgid "" +"It is important to remember that the mechanism needs to be flexible " +"enough to represent any potential desired branching structure; but this " +"does not mean that all modules have to have complex branching we can " +"still (and we should) adopt branching policy that is as simple as " +"possible for any given module." +msgstr "Es ist wichtig zu bedenken, dass der Mechanismus flexibel genug sein muss, jede mögliche gewünschte Verzweigungsstruktur darstellen zu können. Dies bedeutet allerdings nicht, dass alle Module eine komplexe Verzweigung haben müssen. Wir können nach wie vor (und wir sollten) eine Branching-Politik adaptieren, die so einfach wie möglich für jedes Modul ist." + +#: ../../source/design/versioning.rst:57 +msgid "TOC" +msgstr "TOC" + diff --git a/source/locale/de/LC_MESSAGES/design/versioning/coherency.po b/source/locale/de/LC_MESSAGES/design/versioning/coherency.po new file mode 100644 index 0000000..4151754 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/design/versioning/coherency.po @@ -0,0 +1,141 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/design/versioning/coherency.rst:2 +msgid "Coherency of branching" +msgstr "Kohärenz beim Branching" + +#: ../../source/design/versioning/coherency.rst:4 +msgid "" +"There are many advantages to be had in a single, coherent view of the " +"branching structure for a given module." +msgstr "Es gibt viele Vorteile, eine einzige einheitliche Ansicht der Verzweigungsstruktur für ein bestimmtes Modul zu haben." + +#: ../../source/design/versioning/coherency.rst:7 +msgid "Maintainers and users alike have to deal with branches in multiple places:" +msgstr "Entwickler und Anwender müssen sich gleichermaßen mit Branches an mehreren Orten befassen:" + +#: ../../source/design/versioning/coherency.rst:10 +msgid "" +"We plan, develop and build content in bugzilla, dist-git and koji, then " +"release it through bodhi. All of these tools share a common understanding" +" of the various product branches (fXX etc.) and work flows naturally " +"between them." +msgstr "Wir planen, entwickeln und erstellen Content in Bugzilla, Dist-Git und Koji, dann veröffentlichen wir es durch Bodhi. Alle diese Tools teilen ein gemeinsames Verständnis der verschiedenen Produktzweige (fXX etc.) und natürlichen Workflows zwischen diesen." + +#: ../../source/design/versioning/coherency.rst:14 +msgid "" +"Users consume products knowing which branch they are on; they have the " +"option to choose between branches (F25 after F26 has been released), and " +"they report bugs and review CVEs corresponding to those branches" +msgstr "Nutzer konsumieren Produkte mit dem Wissen, auf welchem Zweig sie sich befinden. Sie haben die Möglichkeit zwischen Zweigen zu wählen (F25, nachdem F26 freigegeben worden ist), sie melden Fehler und überprüfen CVEs, die mit diesen Zweigen korrespondieren." + +#: ../../source/design/versioning/coherency.rst:19 +msgid "" +"It also seems highly desirable to automate creation of branches, " +"especially when we consider a future with many more modules than we have " +"today, each with their own branches." +msgstr "Es scheint auch sehr erstrebenswert, die Erstellung von Zweigen zu automatisieren. Insbesondere, wenn wir uns eine Zukunft mit wesentlich mehr Modulen vorstellen als wir heute haben, dabei alle mit ihren eigenen Zweigen." + +#: ../../source/design/versioning/coherency.rst:23 +msgid "" +"But the idea of a clean, consistent view of branching that is unified " +"end-to-end falls down in several places. Some of the difficulties " +"include:" +msgstr "Aber die Idee einer sauberen, konsistenten Ansicht auf die Verzweigung, die End-to-End vereinheitlicht ist, scheitert an mehreren Stellen. Einige der Schwierigkeiten beinhalten:" + +#: ../../source/design/versioning/coherency.rst:27 +msgid "" +"**Utility side-branches:** Some of our tools have slight variants on the " +"main branch naming to support specific workflow requirements." +msgstr "**Utility-Seitenzweige:** Einige unserer Werkzeuge haben leichte Varianten bei der Hauptzweigbenennung, um spezifische Workflow-Anforderungen zu unterstützen." + +#: ../../source/design/versioning/coherency.rst:30 +msgid "" +"For example, in CI we can have staging branches alongside the production " +"release branches, and in koji we have scratch builds; these follow the " +"main branching but are intended for developer use cases, rather than " +"automatically being candidates for release." +msgstr "Zum Beispiel, in CI können wir neben den Produktions-Release-Zweigen auch Staging-Zweige haben und in Koji haben wir Scratch-Builds. Diese folgen dem Hauptzweig, aber sind vorgesehen für Anwendungsfälle von Entwicklern und sind somit eben nicht automatisch Kandidaten für ein Release." + +#: ../../source/design/versioning/coherency.rst:35 +msgid "" +"We have candidate tags, beta tags and release tags in koji, indicating " +"packages on various different stages of the lifecycle from development to" +" release. Beta branches in general represent a special case here." +msgstr "Wir haben Candidate-Tags, Beta-Tags und Release-Tags in Koji, die auf unterschiedliche, verschiedene Phasen im Lebenszyklus von Paketen hinweisen, von der Entwicklung zur Freigabe. Beta-Zweige repräsentieren hier generell einen Sonderfall." + +#: ../../source/design/versioning/coherency.rst:39 +msgid "" +"**Multiple views of branching:** There are several places where two " +"different parts of the release pipeline can treat branching differently " +"from each other. Two important examples here include **minor version " +"branching** and **per-edition views** of a component:" +msgstr "**Mehrere Ansichten der Verzweigung:** Es gibt mehrere Orte, wo zwei verschiedene Teile der Release-Pipeline das Branching unterschiedlich zueinander behandeln können. Zwei wichtige Beispiele hier beinhalten **Verzweigung von Unterversionen** und **Ansichten nach Edition** einer Komponente:" + +#: ../../source/design/versioning/coherency.rst:44 +msgid "**Minor-version branching**: TBD" +msgstr "**Verzweigung von Unterversionen**: TBD" + +#: ../../source/design/versioning/coherency.rst:46 +msgid "**Per-edition views** of branching: TBD" +msgstr "**Ansichten nach Edition** der Verzweigung: TBD" + +#: ../../source/design/versioning/coherency.rst:48 +msgid "**Branch fluidity:** TBD" +msgstr "**Fluidität von Zweigen**: TBD" + +#: ../../source/design/versioning/coherency.rst:50 +msgid "**Naming policy:** TBD" +msgstr "**Namensrichtlinien**: TBD" + +#: ../../source/design/versioning/coherency.rst:52 +msgid "" +"**Consistency of release:** Finally, we need to consider the granularity " +"of branches. The purpose of modularity is to allow us to release modules " +"independently from a single master release cadence. But do we really want" +" all modules to be released without any synchronisation or common " +"branching at all?" +msgstr "**Konsistenz in der Veröffentlichung:** Abschließend müssen wir die Granularität der Zweige betrachten. Der Zweck der Modularisierung ist es uns zu ermöglichen, Module unabhängig zu veröffentlichen von der Zeittaktung eines Single-Master-Release. Aber wollen wir wirklich alle Module freigeben ohne jegliche Synchronisation oder gemeinsames Branching?" + +#: ../../source/design/versioning/coherency.rst:58 +msgid "History suggests we do not." +msgstr "Die Geschichte lehrt uns, dass wir das nicht tun sollten." + +#: ../../source/design/versioning/coherency.rst:60 +msgid "" +"In the future we likely have many completely-decoupled modules for " +"additional content outside the base Fedora runtime platform. But we may " +"still eventually decide that we want to have synchronised releases of new" +" content across different modules." +msgstr "In Zukunft werden wir wahrscheinlich viele vollständig entkoppelte Module für zusätzlichen Content außerhalb der Base-Runtime für die Fedora-Plattform haben. Aber wir könnten möglicherweise beschließen, dass wir synchronisierte Releases von neuem Content über verschiedene Module hinweg haben wollen." + +#: ../../source/design/versioning/coherency.rst:65 +msgid "" +"So while modules can have independent branches, we still need the ability" +" to drive a common branching structure across a set of modules when that " +"is needed for product release requirements. First-class support for such " +"a **consolidated release** is absolutely necessary; to devolve the " +"distribution into an unmanaged, completely-uncoordinated set of " +"independent modules is likely unsustainable for both engineers, " +"maintainers, and users alike." +msgstr "Also während Module voneinander unabhängige Zweige haben können, benötigen wir dennoch die Möglichkeit eine gemeinsame Verzweigungsstruktur über eine Reihe von Modulsets zu legen, wenn dies die Anforderungen an Produkt-Releases darstellt. Erstklassige Unterstützung für solch ein **konsolidiertes Release** ist unbedingt notwendig. Die Distribution in einen nicht verwalteten, völlig unkoordinierten Set von unabhängigen Modulen übergehen zu lassen, wäre gleichermaßen untragbar sowohl für Ingenieure und Entwickler, als auch Anwender gleichermaßen." + diff --git a/source/locale/de/LC_MESSAGES/design/versioning/constraints.po b/source/locale/de/LC_MESSAGES/design/versioning/constraints.po new file mode 100644 index 0000000..6cfea9e --- /dev/null +++ b/source/locale/de/LC_MESSAGES/design/versioning/constraints.po @@ -0,0 +1,113 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/design/versioning/constraints.rst:2 +msgid "Constraints on branching" +msgstr "Restriktionen beim Branching" + +#: ../../source/design/versioning/constraints.rst:4 +msgid "" +"Everything so far seems to say “branching is hard, let’s not assume what " +"it looks like but just store a flexible representation that we can adapt " +"as we need.”" +msgstr "Alles scheint so weit zu sagen, »Branching ist schwierig, es ist wohl besser, sich nicht vorzustellen, wie dies aussieht. Es ist besser, lediglich eine flexible Darstellung zu platzieren, die wir uns bei Bedarf anpassen können.«" + +#: ../../source/design/versioning/constraints.rst:8 +msgid "" +"That’s true to some extent… but there *are* concerns we can anticipate " +"that we need to handle in our branching structure. Having covered the " +"fundamental principle that branching policy needs to remain flexible, " +"let’s look at some of the issues we need to handle as we define that " +"policy." +msgstr "Das ist wahr, bis zu einem gewissen Grad… aber da *sind* Problematiken, die wir bereits vorhersehen können und mit denen wir umgehen können müssen in unserer Branching-Struktur. Wenn das fundamentale Grundprinzip, dass Branching-Richtlinien flexibel bleiben müssen, abgehandelt ist, schauen wir auf einige der Probleme, die zu bewältigen sind, wenn wir diese Richtlinie definieren." + +#: ../../source/design/versioning/constraints.rst:15 +msgid "Splitting a binary package build over multiple modules" +msgstr "Aufteilen eines Binärpakets über mehrere Module" + +#: ../../source/design/versioning/constraints.rst:17 +msgid "This is something that is surprisingly common." +msgstr "Dies ist etwas, das überraschend häufig vorkommt." + +#: ../../source/design/versioning/constraints.rst:19 +msgid "" +"Examples might be when we want to include a library to support our own " +"package/application, but do not want to give it full support for end-" +"users; we might include the library itself, but not include the " +"components that provide the ability to develop against it (the include " +"files, static libraries etc. that typically land in a -devel binary rpm)." +msgstr "Beispiele könnten sein, wenn wir eine Bibliothek hinzufügen wollen, um unser eigenes Paket oder Anwendung zu unterstützen, aber keine volle Unterstützung für Endbenutzer geben wollen. Wir könnten die Bibliothek selbst integrieren, jedoch nicht die Komponenten, die die Möglichkeit bieten, gegen diese zu entwickeln (die Include-Dateien, statische Bibliotheken, usw., die typischerweise in einem `devel`-Binary-RPM landen)." + +#: ../../source/design/versioning/constraints.rst:25 +msgid "" +"Can we do this naturally in a modular build chain? Clearly it breaks any " +"assumption that a module can be both compiled and composed in complete " +"independence from any other: if a package build ends up in multiple " +"modules, then the compile phase of building those modules is now linked. " +"We need to determine how important it is to support this." +msgstr "Können wir dies auf natürliche Weise in einer modularen Build-Chain tun? Natürlich bricht es mit jeglicher Annahme, dass ein Modul sowohl kompiliert und zusammengesetzt werden kann in völliger Unabhängigkeit von dem jeweils Anderen: Wenn ein Paket-Build in mehreren Modulen landet, dann ist die Kompilierungsphase dieser erzeugten Module nun verlinkt. Wir müssen herausfinden, wie wichtig es ist, dies zu unterstützen." + +#: ../../source/design/versioning/constraints.rst:31 +msgid "" +"But it is still quite possible to achieve, if the modules which are to " +"share binaries have matching branches. In that case, module composes can " +"always agree on which koji branches [tags] to consume packages from. So " +"this may be fairly easy for modules which are part of a single " +"consolidated release, as defined above; it would be fair to restrict this" +" possibility to that case." +msgstr "Sofern die Module, die Binärdateien zu teilen haben, auch übereinstimmende Zweige haben ist es durchaus möglich, dies zu erreichen. In diesem Fall können Modul-Composes sich immer verständigen von welchen Koji-Zweigen [Tags] Pakete zu konsumieren sind. So kann dies ziemlich einfach für Module sein, die Teil eines einzelnen konsolidierten Release sind, wie oben definiert. Es wäre sinnvoll, diese Möglichkeit auf diesem Fall zu beschränken." + +#: ../../source/design/versioning/constraints.rst:39 +msgid "Building a module in multiple build roots" +msgstr "Erzeugen eines Moduls in mehreren Buildroots" + +#: ../../source/design/versioning/constraints.rst:41 +msgid "" +"Does a single module source branch result in a single composed binary " +"branch? Or do we build that same source multiple times against different " +"base distribution build roots?" +msgstr "Resultiert ein einzelner Modulquellen-Zweig in einem einzelnen Compose eines Binärzweigs? Oder erzeugen wir die gleiche Quelle mehrfach gegen verschiedene Buildroots der Basisdistribution?" + +#: ../../source/design/versioning/constraints.rst:45 +msgid "" +"Clearly, branching becomes enormously more complicated if we need to " +"support builds for multiple different build roots in a single branch. The" +" idea of a single coherent branching structure from git to release is " +"broken if we have multiple output branches from a single input branch." +msgstr "Natürlich wird Branching um einiges komplizierter, wenn wir Builds für mehrere unterschiedliche Buildroots in einem einzigen Zweig unterstützen müssen. Die Idee einer einzigen kohärenten Branching-Struktur von Git zum Release ist gebrochen, wenn wir mehrere Ausgabe-Zweige von einem einzelnen Eingabe-Zweig haben." + +#: ../../source/design/versioning/constraints.rst:50 +msgid "" +"But the entire point of ABI forwards compatibility is to avoid the need " +"to do this: to run a module on a set of major runtimes, it should, in " +"theory, be necessary simply to build it on the oldest runtime in that " +"set. A module built on F25 should run on F26 or f27, as long as it is " +"using only dependencies with long-term stability guarantees." +msgstr "Aber der gesamte Punkt der ABI-Aufwärtskompatibilität ist es zu vermeiden, dies tun zu müssen: Um ein Modul auf einer Reihe von Major-Runtimes auszuführen, sollte es in der Theorie notwendig sein, dies einfach auf der ältesten Runtime in diesem Set zu erzeugen. Ein Modul, dass in F25 gebaut wurde, sollte in F26 oder F27 laufen, solange es nur Abhängigkeiten mit langfristigen Stabilitätsgarantien verwendet." + +#: ../../source/design/versioning/constraints.rst:56 +msgid "" +"So before working through the complexities of commit-once, compile-" +"multiple-times, it will be important to determine to what extent we can " +"simply depend on ABI compatibility to ensure a module works against " +"multiple runtimes." +msgstr "Also bevor man sich durch die Komplexität des »commit-once, compile-multiple-times« durcharbeitet, wird es wichtig sein zu bestimmen, in welchem Umfang wir ABI-Kompatibilität benötigen, um zu gewährleisten, dass ein Modul gegen diverse Laufzeiten funktioniert." + diff --git a/source/locale/de/LC_MESSAGES/design/versioning/managing.po b/source/locale/de/LC_MESSAGES/design/versioning/managing.po new file mode 100644 index 0000000..9bb86f1 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/design/versioning/managing.po @@ -0,0 +1,222 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/design/versioning/managing.rst:2 +msgid "Managing this branching complexity" +msgstr "Verwalten dieser Verzweigungskomplexität" + +#: ../../source/design/versioning/managing.rst:4 +msgid "" +"Given that the exact branching policy for a module is currently " +"inconsistent, needs to remain flexible, and changes over time, how do we " +"manage this? The question is especially significant given that we are " +"looking at significant changes to the way we divide and release the " +"distribution in the future; our future branching model is currently " +"completely unknown." +msgstr "Angesichts dessen, dass die exakten Richtlinien für das Branching eines Moduls derzeit inkonsistent sind, flexibel bleiben müssen und sich im Laufe der Zeit auch ändern – wie können wir das verwalten? Die Frage ist besonders wichtig angesichts der Tatsache, dass wir grundlegenden Änderungen gegenüberstehen bzgl. der Art und Weise, wie wir die Distribution zukünftig aufteilen und veröffentlichen. Unser zukünftiges Branching-Modell ist derzeit völlig unbekannt." + +#: ../../source/design/versioning/managing.rst:11 +msgid "" +"This suggests that we should not try to formalise a branching and naming " +"policy at all. But we **must** eventually have automation for the " +"creation of branches and for branch transitions, especially given that " +"release consistency may require us to coordinate new branches across many" +" modules simultaneously. And our tools still need consistent views across" +" this complex branching structure." +msgstr "Dies deutet darauf hin, dass wir nicht versuchen sollten, Branching und Namensrichtlinien zu formalisieren. Aber wir **müssen** eventuell Automatisierung für die Generierung von Zweigen und Branch-Übergänge ermöglichen. Insbesondere, wenn die Release-Konsistenz es erforderlich macht, neue Zweige über mehrere Module hinweg zu koordinieren. Und unsere Tools benötigen konsistente Ansichten über diese komplexe Verzweigungsstruktur." + +#: ../../source/design/versioning/managing.rst:19 +msgid "Separation of policy from representation" +msgstr "Trennen der Richtlinien von der Repräsentation" + +#: ../../source/design/versioning/managing.rst:21 +msgid "This suggests that we need:" +msgstr "Dies deutet darauf hin, dass wir folgendes brauchen:" + +#: ../../source/design/versioning/managing.rst:23 +msgid "" +"A canonical definition of our modules and their branches at any point in " +"time, including the way those branch names are represented in different " +"tools:" +msgstr "Eine kanonische Definition unserer Module und deren Zweigen an jedem beliebigen Punkt in der Zeit, einschließlich der Art und Weise, wie diese Brach-Namen in verschiedenen Werkzeugen vertreten sind:" + +#: ../../source/design/versioning/managing.rst:26 +msgid "" +"Consistent use of that canonical branching structure within our tools, " +"but with" +msgstr "Konsequente Nutzung dieser kanonischen Verzweigungsstruktur innerhalb unserer Werkzeuge, aber mit" + +#: ../../source/design/versioning/managing.rst:28 +msgid "Flexible, scripted events to drive changes in the branching." +msgstr "flexiblen, geskripteten Ereignissen, um Änderungen in den Zweigen durchzuführen." + +#: ../../source/design/versioning/managing.rst:30 +msgid "" +"We can do this by separating the central representation of branching (eg." +" in PDC) from the mechanism used to define and update that branching." +msgstr "Wir erreichen dies durch die Trennung von der zentralen Darstellung der Verzweigung (z. B. in PDC) vom Mechanismus, der verwendet wird zum Definieren und Aktualisieren dieser Verzweigung." + +#: ../../source/design/versioning/managing.rst:34 +msgid "" +"Changes in branching also need to be orchestrated: we should not define a" +" new branch and allow a developer to start building on that branch, " +"before the branch has been created in bugzilla, dist-git, koji etc. There" +" are many tools that could be used here: ansible is just one such tool. " +"The point here is to identify that as a separate concern. Automation here" +" is important if we want to be able to support coordinated release " +"branching across a set of modules." +msgstr "Änderungen in der Verzweigung müssen auch orchestriert werden: Wir sollten keinen neuen Zweig definieren und es einem Entwickler ermöglichen auf diesem Zweig etwas zu erstellen, bevor dieser Zweig in Bugzilla, Dist-Git, Koji usw. kreiert wurde. Es gibt viele Tools, die hier verwendet werden könnten: Ansible ist ein solches Tool. Hierbei ist es von Relevanz, dies als separates Problem zu identifizieren. Automatisierung ist hier wichtig, wenn wir in der Lage sein wollen, koordiniertes Release-Branching zu ermöglichen über ein Set von Modulen hinweg." + +#: ../../source/design/versioning/managing.rst:42 +msgid "" +"For now, we are dealing with a relatively simple branching structure, " +"building simple modules out of the latest Fedora. We don’t *need* complex" +" branching policy right now. But separating out representation from " +"policy allows us to start with a simple branching structure initially, " +"and still lets us define, and script, more complex, product-specific " +"branching requirements later, while having those consistently represented" +" in a central database that our tools can refer to and agree on." +msgstr "Im Moment beschäftigen wir uns mit einer relativ einfachen Branching-Struktur, erzeugen einfache Module aus dem aktuellsten Fedora. Aktuell *benötigen* wir keine komplexen Branching-Richtlinien. Aber die Trennung der Darstellung von den Richtlinien ermöglicht es uns, zunächst mit einer einfachen Zweigstruktur zu beginnen und lässt uns später immer noch komplexere, produktspezifische Branching-Anforderungen definieren und skripten. Dabei werden diese konsistent dargestellt in einer zentralen Datenbank, auf die unsere Tools sich beziehen und verständigen können." + +#: ../../source/design/versioning/managing.rst:52 +msgid "Forking a new branch" +msgstr "Forken eines neuen Zweigs" + +#: ../../source/design/versioning/managing.rst:54 +msgid "" +"We have mentioned that creating a new branch for a module involves " +"branching multiple different tools: we need a branch for the module in " +"dist-git, new branches for its components, and corresponding branches in " +"bugzilla; we may need new tags in koji." +msgstr "Wir haben erwähnt, dass die Schaffung eines neuen Zweigs für ein Modul das Branching mehrerer verschiedener Werkzeuge umfasst: Wir brauchen einen Branch für das Modul in Dist-Git, neue Zweige für seine Komponenten, korrespondierende Branches in Bugzilla und wir brauchen möglicherweise neue Tags in Koji." + +#: ../../source/design/versioning/managing.rst:59 +msgid "" +"This implies that the branching for a module is (usually) the same thing " +"as the branching for all the component packages of that module." +msgstr "Dies bedeutet, dass das Branching für ein Modul (meist) die gleiche Sache ist, wie das Branching für alle Komponentenpakete dieses Moduls." + +#: ../../source/design/versioning/managing.rst:62 +msgid "" +"But sometimes we will not want to branch *all* packages; we may want a " +"variant branch of a module which overrides just some of the packages, and" +" which otherwise inherits the content (''including new content) ''from " +"its base branch." +msgstr "Aber manchmal wollen wir nicht *alle* Pakete verzweigen. Eventuell möchten wir einen leicht abweichenden Branch eines Moduls, der nur einige der Pakete überschreibt und der ansonsten die Inhalte (einschließlich neuen Inhalts) von seinem Basiszweig erbt." + +#: ../../source/design/versioning/managing.rst:67 +msgid "" +"There are many examples which would suit such a **inheriting branch.** " +"The f-stream model which allows early access to new features prior to an " +"update, is an example. Another might be the specialized version of the " +"virtualisation stack, which contains a version of kvm-qemu with newer " +"features but which otherwise follows Fedora. The model also works for " +"scratch or staging branches, where we can build and test updates to an " +"existing branch as needed to suit internal developer needs." +msgstr "Es gibt viele Beispiele, die auf so einen **vererbten Branch** passen würden. Das f-Stream-Modell, welches frühen Zugang zu neuen Funktionen vor einem Update ermöglicht, ist so ein Beispiel. Eine Anderes mag möglicherweise die spezialisierte Version des Virtualisierungs-Stacks sein, die eine Version von KVM-QEMU mit neueren Features enthält, aber die ansonsten Fedora folgt. Das Modell funktioniert auch für Scratch- oder Staging-Zweige, auf denen wir nach Bedarf Updates erstellen und testen können für einen vorhandenen Zweig, um die Bedürfnisse interner Entwickler zu befriedigen." + +#: ../../source/design/versioning/managing.rst:76 +msgid "" +"This suggests that we want to include tooling support for inheriting such" +" a branch. Technically, this might involve creating new branches for only" +" a subset of the packages of a module; and recording the base module from" +" which we pull other packages during a module compose." +msgstr "Dies deutet darauf hin, dass wir Unterstützung für Werkzeuge integrieren wollen, um solch einen Zweig zu vererben. Technisch gesehen könnte dies beinhalten, neue Zweige nur für eine Teilmenge der Pakete eines Moduls zu erzeugen und das Basismodul mitzuerfassen, aus dem heraus wir andere Pakete während eines Modul-Compose ziehen." + +#: ../../source/design/versioning/managing.rst:82 +msgid "Converging branches" +msgstr "Zusammenführen von Branches" + +#: ../../source/design/versioning/managing.rst:84 +msgid "" +"Just as important as forking a new branch is converging existing " +"branches. In an f-stream model, a new feature scheduled for the next " +"release is made available in a prior release. The f-stream is the early-" +"access branch; the intent is that when the next release occurs, it " +"introduces that feature into the mainline stream, and the f-stream is no " +"longer needed: any component depending on that feature moves back off the" +" f-stream branch and onto the mainline." +msgstr "Genauso wichtig wie das Forken eines neuen Zweigs, ist es von Relevanz bestehende Zweige zusammenzuführen. In einem f-Stream-Modell wird ein neues Feature, das für die nächste Version geplant ist, in einem früheren Release zur Verfügung gestellt. Der f-Stream ist der Early-Access-Branch. Die Absicht ist, dass, wenn der nächste Release fällig wird, es dieses Feature in den Mainline-Stream einführt und der f-Stream nicht mehr länger benötigt wird: Jede Komponente, abhängig von diesem Feature, wechselt aus dem f-Stream auf den Mainline-Stream." + +#: ../../source/design/versioning/managing.rst:92 +msgid "" +"Extending this to a modular build, we can imagine a component needing a " +"new feature within any module in our stack. If that module does not plan " +"the feature to be released in time, we can fork a specific version of the" +" module to serve the needs of the one component needing the new feature; " +"but if and when that feature is released in some mainline version of the " +"module, we want the ability to move the component off the forked feature " +"branch and back onto mainline." +msgstr "Dies erweitert auf einen modularen Build, können wir uns eine Komponente vorstellen, die ein neues Feature benötigt, in einem beliebigen Modul in unserem Stack. Wenn dieses Modul nicht plant, dieses Feature rechtzeitig zu veröffentlichen, können wir eine bestimmte Version des Moduls forken, um die Bedürfnisse der einzelnen Komponente, die das neue Feature benötigt, zu befriedigen. Aber wenn bzw. sobald dieses Feature in einer Hauptversion des Moduls veröffentlicht wird, wollen wir die Möglichkeit, diese Komponente aus dem geforkten Feature-Zweig zurück in die Mainline zu verschieben." + +#: ../../source/design/versioning/managing.rst:100 +msgid "" +"There are likely to be many complexities here; the important point is to " +"imagine up-front that forking a new branch is only half the picture, it " +"will be useful to have tooling support for converging branches again " +"afterwards too." +msgstr "Es gibt voraussichtlich ein Zuviel an Komplexität hier. Der wichtige Punkt ist hier, sich bereits im Vorfeld vorzustellen, dass das Forken auf einen neuen Branch lediglich das halbe Bild ist. Es wird nützlich sein, Unterstützung für Werkzeuge zu haben, mit denen man danach Zweige auch wieder zusammenzuführen kann." + +#: ../../source/design/versioning/managing.rst:106 +msgid "Managing unsynchronised stacks of branches" +msgstr "Verwalten unsynchronisierter Stacks von Zweigen" + +#: ../../source/design/versioning/managing.rst:108 +msgid "" +"Modules can depend in turn on other modules. We have defined a “stack” as" +" the entire tree of modules needed to satisfy dependencies for one top-" +"level module or application. But as we combine modules in this way, not " +"all those modules will have the same branches or lifecycle." +msgstr "Module können wiederum von anderen Module abhängig sein. Wir haben einen »Stack« definiert, als den vollständigen Baum von Modulen, die benötigt werden, um die Abhängigkeiten für ein Top-Level-Modul oder eine Anwendung zu erfüllen. Aber wenn wir Module auf diese Weise kombinieren, werden nicht alle Module die gleichen Zweige oder Lebenszyklen haben." + +#: ../../source/design/versioning/managing.rst:113 +msgid "" +"So when we have multiple, different, unsynchronised branching models for " +"different modules within a stack, how do we know exactly which branches " +"of which modules we need to combine together? We can agree that we need " +"to constrain this complexity, and define specific subsets of modules " +"which we will test and support together. The issue is where, and how, to " +"define this." +msgstr "Wenn wir mehrere, unterschiedliche, unsynchronisierte Branching-Modelle für verschiedene Module innerhalb eines Stacks besitzen, woher wissen wir genau, welche Branches wir mit welchen Modulen kombinieren müssen? Wir können vereinbaren, dass wir diese Komplexität beschränken und spezielle Subsets von Modulen definieren müssen, die wir gemeinsam testen und unterstützen. Die Frage ist, wo und wie dies zu definieren ist." + +#: ../../source/design/versioning/managing.rst:120 +msgid "" +"This is an issue we still need to solve. There two obvious places to hold" +" this structure: in the **release** that defines multiple modules and " +"their combined release schedules; or by defining specific branch " +"dependencies in each module’s own module metadata." +msgstr "Dies ist ein Thema, das wir noch lösen müssen. Es gibt zwei offensichtlich Orte, um diese Struktur aufzubewahren: In dem **Release**, das mehrere Module definiert und ihre kombinierten Release-Zeitpläne. Oder aber durch die Festlegung von bestimmten Branch-Abhängigkeiten in den jeweiligen Modul-Metadaten in den einzelnen Modulen." + +#: ../../source/design/versioning/managing.rst:125 +msgid "" +"Both have pros and cons. Defining specific branch dependencies in a " +"module’s metadata helps by keeping more of the module’s defining " +"structure in one place. However, the downside is that it becomes " +"impossible to use that same metadata in multiple places without changing " +"it: eg. building a single module from the same module source on multiple " +"buildroots is impossible if the module source itself defines its " +"buildroot dependency." +msgstr "Beide Optionen haben ihre Vor- und Nachteile. Das Definieren von spezifischen Branch-Abhängigkeiten in den Metadaten eines Moduls hilft, indem es mehr von der definierenden Struktur eines Moduls an einem Ort bereithält. Der Nachteil ist jedoch, dass es unmöglich wird, die gleichen Metadaten an mehreren Stellen zu verwenden, ohne sie zu verändern: Zum Beispiel ist es unmöglich, ein einzelnes Modul aus der gleichen Modulquelle auf mehreren Buildroots zu bauen, wenn die Modulquelle selbst seine Buildroot-Abhängigkeit definiert." + +#: ../../source/design/versioning/managing.rst:133 +msgid "So this is a topic for future consideration." +msgstr "So ist dies als ein Thema für die Zukunft zu berücksichtigen." + diff --git a/source/locale/de/LC_MESSAGES/design/versioning/properties.po b/source/locale/de/LC_MESSAGES/design/versioning/properties.po new file mode 100644 index 0000000..b3b01e3 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/design/versioning/properties.po @@ -0,0 +1,134 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/design/versioning/properties.rst:2 +msgid "Properties of branches and update streams" +msgstr "Eigenschaften von Branches und Update-Streams" + +#: ../../source/design/versioning/properties.rst:4 +msgid "" +"**ABI Compatibility:** Updates within a single update stream are likely " +"to maintain ABI backwards compatibility in most cases. Users should be " +"able to consume updates from an update stream without being concerned " +"about breaking applications that depend on that module. A major change " +"introducing an incompatible ABI would normally be expected to require a " +"new version branch." +msgstr "**ABI-Kompatibilität:** Updates in einem einzelnen Update-Stream werden voraussichtlich in den meisten Fällen ABI-Rückwärtskompatibilität gewährleisten. Benutzer sollten in der Lage sein, Updates von einem Update-Stream zu konsumieren, ohne Sorgen, dass Anwendungen nicht mehr lauffähig sind, die von diesem Modul abhängig sind. Bei einer wesentlichen Änderung, die eine inkompatible ABI einführt, sollte dies normalerweise einen neuen Versionszweig erfordern." + +#: ../../source/design/versioning/properties.rst:11 +msgid "" +"But this is ultimately a policy decision: there is nothing technical to " +"stop ABI breakage within a version stream. For example, the container-" +"runtime is rapidly changing so it has broken compatibility across " +"versions. Our tools should be able to detect incompatible ABI changes as " +"far as possible, but should not prevent them if we have an exceptional " +"case where such a change is desired." +msgstr "Aber das ist letztlich eine Entscheidung, die die Richtlinien betrifft: Es gibt keinerlei technische Gründe, die einen ABI-Bruch innerhalb eines Versions-Streams verhindern. Beispielsweise ändert sich die Container-Runtime fortlaufend sehr schnell, so kommt es zu gebrochener Kompatibilität zwischen den Versionen. Unsere Werkzeuge sollten inkompatible ABI-Änderungen so weit wie möglich erkennen. Sie sollten Sie aber nicht verhindern, wenn wir einen Ausnahmefall haben, in dem eine solche Änderung gewünscht ist." + +#: ../../source/design/versioning/properties.rst:18 +msgid "" +"(ABI compatibility here includes anything that may have a compatibility " +"on user or application compatibility, including for example semantics of " +"configuration files, library ABIs, command line option handling and error" +" codes, and so on.)" +msgstr "(ABI-Kompatibilität umfasst hier alles, was möglicherweise Kompatibilität bezogen auf Benutzer oder eine Anwendungskompatibilität bedeutet, darunter z. B. die Semantik von Konfigurationsdateien, ABIs von Bibliotheken, die Handhabung von Kommandozeilenoptionen und Fehlercodes, usw.)." + +#: ../../source/design/versioning/properties.rst:23 +msgid "" +"**Constraining the scope of ABI dependency:** As preserving ABI on " +"updates is a burden which imposes constraints on our maintenance of a " +"module within a single version branch, we would like the ability to limit" +" the parts of a module to which ABI stability applies. We currently " +"define which packages within a module form the **external ABI** of the " +"module: this is defined by the maintainer of a given module’s metadata. " +"Conversely, packages not declared as external are implicit internal " +"implementation details of the module." +msgstr "**Den Umfang der ABI-Abhängigkeit einschränken:** Die ABI bei Aktualisierungen zu erhalten ist eine Last, die uns Einschränkungen auferlegt bei der Wartung eines Moduls in einem einzelnen Versionszweig. Wir würden gern die Möglichkeit haben, die Teile eines Moduls zu beschränken, für die ABI-Stabilität von Relevanz ist. Aktuell definieren wir, welche Pakete innerhalb eines Moduls die **externe ABI** des Moduls formen: Dies wird durch den Maintainer der zugehörigen Modul-Metadaten definiert. Umgekehrt sind Pakete, die nicht als extern deklariert sind, implizit interne Implementierungsdetails des Moduls." + +#: ../../source/design/versioning/properties.rst:32 +msgid "Defining the external ABI as a set of packages will allow us to:" +msgstr "Das Definieren der externen ABI als eine Sammlung von Paketen wird es uns ermöglichen:" + +#: ../../source/design/versioning/properties.rst:34 +msgid "" +"Rebase internal packages without constraint from ABI guarantees, removing" +" overhead from the module maintenance burden over time;" +msgstr "Interne Pakete zu rebasen ohne Beschränkung von ABI-Garantien. Somit wird langfristig Overhead entfernt von dem Aufwand bzgl. der Modulwartung." + +#: ../../source/design/versioning/properties.rst:36 +msgid "" +"Verify that layered modules or applications depend only on packages " +"defined as external ABI, by checking rpm dependency chains" +msgstr "Zu versichern, dass geschichtete Module oder Anwendungen nur von Paketen abhängig sind, die als externe ABI definiert sind. Dies geschieht durch Überprüfung der Abhängigkeitsketten von RPMs." + +#: ../../source/design/versioning/properties.rst:39 +msgid "" +"Over time, we may find other ways to describe the external ABI of a " +"module but, at present, RPMs are the best stand in." +msgstr "Im Laufe der Zeit finden wir eventuell andere Wege, um die externe ABI eines Moduls zu beschreiben, aber derzeit sind RPMs die beste Möglichkeit hierzu." + +#: ../../source/design/versioning/properties.rst:42 +msgid "" +"**Lifecycle:** Given that we define no formal policy on ABI " +"lifecycle—rather leaving this up to policy—it follows that there is no " +"strong requirement that version numbers of packages within a single " +"update stream have to follow any particular pattern. We can easily rebase" +" a package within an update stream, even adding new features, as long as " +"any claimed backwards compatibility is preserved." +msgstr "**Lifecycle:** Angesichts der Tatsache, dass wir keine formalen Richtlinien für den ABI-Lebenszyklus definieren – vielmehr überlassen wir dies den individuellen Richtlinien – folgt daraus, dass es keine strenge Anforderung gibt, das Versionsnummern von Paketen in einem einzelnen Update-Stream bestimmten Mustern folgen müssen. Wir können ganz einfach ein Paket in einem Update-Stream rebasen, sogar neue Features hinzufügen, solange jegliche geforderte Rückwärtskompatibilität beibehalten wird." + +#: ../../source/design/versioning/properties.rst:49 +msgid "" +"We do need to be concerned about whether 3rd-party application " +"\"certification\" is expected to be preserved when such an application " +"depends on a module’s version branch containing rebased packages. This is" +" an important question, and we need to add tooling and policy around it; " +"but for now this is primarily a policy question, and beyond the scope of " +"this document. Different modules may have different appetite for risk and" +" rebases, and hence have different policy around \"certification.\"" +msgstr "Wir müssen uns Gedanken darüber machen, ob die 3rd-Party-Anwendungs-»Zertifizierung« beibehalten werden soll, wenn eine derartige Anwendung von einem Versionszweig eines Moduls abhängig ist, dass Pakete enthält, die rebased wurden. Dies ist eine wichtige Frage, und wir müssen Werkzeuge und Richtlinien hinzufügen. Allerdings ist dies für jetzt in erster Linie eine Frage der Richtlinien – und außerhalb des Rahmens dieses Dokuments. Unterschiedliche Module haben möglicherweise unterschiedlichen Appetit auf Risiko und Rebases und haben daher verschiedene Vorgaben rund um die »Zertifizierung«." + +#: ../../source/design/versioning/properties.rst:58 +msgid "" +"**Parallel Availability:** The update streams for different module " +"version branches must be able to coexist in our pipeline and released " +"content, without interfering with each other. If a given base system " +"install has both httpd-2.2 and httpd-2.4 available in different version " +"branches, then it is important that these remain independent." +msgstr "**Parallele Verfügbarkeit:** Die Update-Streams für verschiedene Modulversionszweige müssen in unserer Pipeline und Content-Releases koexistieren können, ohne sich gegenseitig zu beeinträchtigen. Wenn ein vorhandenes, installiertes Basissystem sowohl `httpd-2.2` und `httpd-2.4` in unterschiedlichen Versionszweigen zur Verfügung stellt, dann ist es wichtig, dass diese unabhängig bleiben." + +#: ../../source/design/versioning/properties.rst:64 +msgid "" +"The update streams must not interfere with each other. If httpd-2.2 is " +"installed, then updating it via yum or dnf should update it to the most " +"recent version in the httpd-2.2 update stream, and must not automatically" +" update it to 2.4. Any dependencies brought in by either must also " +"prevent such interference." +msgstr "Die Update-Streams dürfen nicht miteinander kollidieren. Wenn `httpd-2.2` installiert ist, dann sollte eine Aktualisierung via YUM oder DNF es auf die neueste Version im `httpd-2.2`-Update-Stream aktualisieren und es nicht automatisch auf `2.4` aktualisieren. Alle eingebrachten Abhängigkeiten müssen ebenfalls solche Interferenzen verhindern." + +#: ../../source/design/versioning/properties.rst:70 +msgid "" +"And yet if a certain package *does* support parallel installation of " +"different version branches at the same time (eg. software collection-" +"based packages), then the separate installed versions at any time must " +"each be updatable by their own specific update stream." +msgstr "Und dennoch, wenn ein bestimmtes Paket es unterstützt, parallele Installationen unterschiedlicher Versionszweige zur gleichen Zeit vorzunehmen (z. B. Pakete basierend auf Software Collections), dann müssen die einzelnen, separat installierten Versionen jederzeit jeweils durch ihre eigenen speziellen Update-Streams aktualisiert werden können." + diff --git a/source/locale/de/LC_MESSAGES/design/versioning/terminology.po b/source/locale/de/LC_MESSAGES/design/versioning/terminology.po new file mode 100644 index 0000000..55f7815 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/design/versioning/terminology.po @@ -0,0 +1,79 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/design/versioning/terminology.rst:2 +msgid "Basic branching terminology" +msgstr "Grundlegende Branching-Terminologie" + +#: ../../source/design/versioning/terminology.rst:4 +msgid "" +"First, though, note that the very word “version” is overloaded here. It " +"can refer either to a completely separate branch of some module, or to a " +"single specific instance or compose of a module. To keep terminology " +"straight, we need to distinguish between:" +msgstr "Zuerst wäre anzumerken, dass das Wort »Version« hier überstrapaziert wird. Es kann sich entweder auf einen völlig separaten Zweig irgendeines Moduls beziehen oder auf eine einzelne, spezifische Instanz oder den Compose eines Moduls. Um die Terminologie eindeutig zu halten, müssen wir unterscheiden zwischen:" + +#: ../../source/design/versioning/terminology.rst:9 +msgid "" +"A **version branch**: or more simply just a **branch**: a completely new," +" carefully planned version stream for a module. This might correspond to " +"a major Fedora release, or a new Fedora SCL release. Creating a new " +"branch should come with a new **release** target for the branch (or " +"branches if we’re releasing multiple modules simultaneously.)" +msgstr "Einem **Versionszweig**: oder einfach nur ein **Zweig**: Ein völlig neuer, sorgfältig geplanter Versionsstream für ein Modul. Dies könnte mit einem Hauptrelease von Fedora korrespondieren oder einem neuen Fedora SCL Release. Das Kreieren eines neuen Zweigs sollte einhergehen mit einem neuen **Release**-Ziel für diesen Branch (oder mehrere Zweige, wenn wir mehrere Module gleichzeitig veröffentlichen)." + +#: ../../source/design/versioning/terminology.rst:16 +msgid "" +"A version branch **may** correspond to a new **major version** of the " +"module, but there may be exceptions: for example, when we add specific " +"features as a side-branch of an existing major version. The new branch " +"may differ by SLA (eg. a faster moving Python) or by feature (eg. an " +"“f-stream” branch giving early access to a specific new feature planned " +"to be released in a subsequent update)." +msgstr "Ein Versionszweig mag **möglicherweise** einer neuen **Hauptversion** des Moduls entsprechen, aber möglicherweise gibt es Ausnahmen: Zum Beispiel, wenn wir spezielle Features als einem Seitenast zu einer vorhandenen Hautversion hinzufügen. Der neue Branch mag abweichen von der SLA (z. B. ein sich schneller fortbewegendes Python) oder bzgl. der Funktionalität (z. B. ein »f-Stream«-Zweig, der frühen Zugang zu einem speziellen neuen Feature gibt, das in einem späteren Update freigegeben werden soll)." + +#: ../../source/design/versioning/terminology.rst:23 +msgid "" +"Users must opt into a new version branch. By definition here, creating a " +"new version branch **must** have no impact on users who have already " +"enabled an existing branch of a module. If a user provisions a new " +"environment and asks for the most recent version branch, then they may " +"get the new version branch automatically; but no existing environments " +"will transparently receive content for the new version branch." +msgstr "Benutzer gelangen in einen neuen Versionszweig via Opt-In. Per Definition hier, darf das Kreieren eines neuen Versionszweiges **keinerlei** Auswirkungen auf Benutzer haben, die bereits einen vorhandenen Branch eines Moduls aktiviert haben. Wenn ein Benutzer sich eine neue Umgebung einrichtet und nach dem aktuellsten Versionszweig fragt, können sie möglicherweise automatisch den neuen Versionszweig erhalten. Allerdings werden keine bereits existierenden Umgebungen Content für den neuen Versionszweig erhalten." + +#: ../../source/design/versioning/terminology.rst:31 +msgid "" +"A **point-in-time version** or **instance** representing a single compose" +" of a module on a single version branch, built by and identifiable by the" +" **compose ID** of the task used to compose the module within the build " +"system." +msgstr "Eine **Point-in-Time-Version** oder **Instanz** repräsentiert einen einzelnen Compose eines Moduls auf einem einzelnen Versionszweig. Erzeugt und erkennbar durch die **Compose-ID** des Task, der verwendet wird, das Modul innerhalb des Build-Systems zu erzeugen." + +#: ../../source/design/versioning/terminology.rst:36 +msgid "" +"Such a point-in-time update may be just a scratch build, or may be " +"internal-only and not released to the user. But once it is released, it " +"forms a new **update** for that version branch of the module. Multiple " +"released point-in-time updates therefore form an **update stream** over " +"time for that branch." +msgstr "Solch ein Point-in-Time-Update ist möglicherweise nur ein Scratch-Build oder möglicherweise nur intern und nicht für den Benutzer freigegeben. Aber sobald es veröffentlicht wird, erzeugt es ein neues **Update** für diesen Versionszweig des Moduls. Mehrere freigegebene Point-in-Time-Aktualisierungen formen daher einen **Update-Stream** im Laufe der Zeit für diesen Zweig." + diff --git a/source/locale/de/LC_MESSAGES/development/building-containers.po b/source/locale/de/LC_MESSAGES/development/building-containers.po new file mode 100644 index 0000000..29cd133 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/development/building-containers.po @@ -0,0 +1,29 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/development/building-containers.rst:2 +msgid "Building Containers" +msgstr "Erstellen von Containern" + +#: ../../source/development/building-containers.rst:5 +msgid "TOC" +msgstr "TOC" + diff --git a/source/locale/de/LC_MESSAGES/development/building-containers/containers-infra.po b/source/locale/de/LC_MESSAGES/development/building-containers/containers-infra.po new file mode 100644 index 0000000..88eef0f --- /dev/null +++ b/source/locale/de/LC_MESSAGES/development/building-containers/containers-infra.po @@ -0,0 +1,76 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/development/building-containers/containers-infra.rst:2 +msgid "Building containers in Fedora" +msgstr "Erstellen von Containern in Fedora" + +#: ../../source/development/building-containers/containers-infra.rst:4 +msgid "" +"Your Dockerfile needs to be formally reviewed before becoming a part of " +"Fedora. The review process is described in the `Fedora wiki " +"`__." +msgstr "Ihre Dockerfile muss formal geprüft werden, bevor es zu einem Teil von Fedora werden kann. Das Prüfverfahren ist beschrieben im `Fedora Wiki `__." + +#: ../../source/development/building-containers/containers-infra.rst:10 +msgid "Builds in production" +msgstr "Builds in der Produktion" + +#: ../../source/development/building-containers/containers-infra.rst:12 +msgid "" +"Production builds of container images are documented in `this section " +"`__ " +"of the review process document mentioned above. Please follow the process" +" to perform an infrastructure build of your container image." +msgstr "Produktions-Builds von Container-Images sind dokumentiert in `diesem Abschnitt `__ des Prüfverfahren-Dokuments, das weiter oben genannt wurde. Halten Sie sich bitte an diesen Ablauf, um einen Infrastruktur-Build des Container-Images durchzuführen." + +#: ../../source/development/building-containers/containers-infra.rst:17 +msgid "" +"In order to get the correct content (modules, RPMs) in your container " +"image, you should make sure that those artifacts are released and " +"available:" +msgstr "Um den richtigen Content (Module, RPMs) in Ihrem Container-Image zu erhalten, sollten Sie sicherstellen, dass diese Artefakte freigegeben und verfügbar sind:" + +#: ../../source/development/building-containers/containers-infra.rst:20 +msgid "" +"For modules, this means to have a valid compose with your module. The " +"module needs to be incorporated inside `this pungi configuration file " +"`__, " +"if you want the module to be part of a compose." +msgstr "Für Module bedeutet dies, in einem validen Compose in Ihrem Modul eingebunden zu werden. Das Modul muss in `dieser Pungi-Konfigurationsdatei `__ enthalten sein, wenn Sie wollen, dass das Modul Teil eines Compose ist." + +#: ../../source/development/building-containers/containers-infra.rst:25 +msgid "" +"For RPMs, the package should pass the Bodhi update process and be " +"available in repositories." +msgstr "Für RPMs sollte das Paket den Bodhi-Updateprozess durchlaufen und in Repositorys verfügbar sein." + +#: ../../source/development/building-containers/containers-infra.rst:30 +msgid "Inspecting registry" +msgstr "Inspizieren der Registry" + +#: ../../source/development/building-containers/containers-infra.rst:32 +msgid "" +"At the time of writing (Aug 2017), the Fedora docker image registry " +"doesn't have any frontend. You can access its API to get a list of " +"available images:" +msgstr "Zum Zeitpunkt des Schreibens (August 2017) hat die Registry für das Fedora Docker Image keinerlei Front-End. Sie können auf die API zugreifen, um eine Liste der verfügbaren Images zu erhalten:" + diff --git a/source/locale/de/LC_MESSAGES/development/building-containers/containers-local.po b/source/locale/de/LC_MESSAGES/development/building-containers/containers-local.po new file mode 100644 index 0000000..df753c4 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/development/building-containers/containers-local.po @@ -0,0 +1,79 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/development/building-containers/containers-local.rst:2 +msgid "Building containers locally" +msgstr "Lokales Erzeugen von Containern" + +#: ../../source/development/building-containers/containers-local.rst:4 +msgid "" +"When you have your module built, let's put it in a container, so we can " +"use it. As an example, we will use the `perl image `__." +msgstr "Wenn Sie Ihr Modul gebaut haben, packen Sie es in einen Container, damit es verwendet werden kann. Als Beispiel verwenden wir das `Perl-Image `__." + +#: ../../source/development/building-containers/containers-local.rst:9 +msgid "Module RPM repository" +msgstr "Modul-RPM-Repository" + +#: ../../source/development/building-containers/containers-local.rst:11 +msgid "" +"First, upload your RPM repository from the previous step somewhere " +"publicly accessible. For example, you can use Fedorapeople to host your " +"packages:" +msgstr "Laden Sie zunächst Ihr RPM-Repository aus dem vorherigen Schritt irgendwo hoch, wo es öffentlich zugänglich ist. Zum Beispiel können Sie Fedorapeople verwenden um Ihre Pakete zu hosten:" + +#: ../../source/development/building-containers/containers-local.rst:22 +msgid "Dockerfile" +msgstr "Dockerfile" + +#: ../../source/development/building-containers/containers-local.rst:24 +msgid "" +"Next step will be writing a Dockerfile to build a container image with " +"your module." +msgstr "Im nächten Schritt wird ein Dockerfile geschrieben, um ein Container-Image mit Ihrem Modul zu erzeugen." + +#: ../../source/development/building-containers/containers-local.rst:27 +msgid "" +"The Base Runtime image is currently only available from Docker Hub and " +"you can use it as your base image by specifying ``FROM " +"/baseruntime/baseruntime``." +msgstr "Das Image der Base-Runtime ist derzeit nur von Docker Hub zu beziehen. Sie können es als Ihr Basis-Image verwenden durch die Angabe ``FROM /baseruntime/baseruntime``." + +#: ../../source/development/building-containers/containers-local.rst:30 +msgid "" +"You also need to write a repo file for your module and add it to your " +"container, so you can install the module in it. See the example of the " +"repo file in ``__. The following snippet then shows how " +"you copy the repo and install the files from it in your container:" +msgstr "Außerdem müssen Sie eine `.repo`-Datei für Ihr Modul schreiben und Ihrem Container hinzufügen, damit Sie das Modul in ihm installieren können. Ein Beispiel für eine `.repo`-Datei findet sich hier: ``__. Der folgende Codeausschnitt zeigt dann, wie Sie das Repo kopieren und daraus die Dateien in dem Container installieren:" + +#: ../../source/development/building-containers/containers-local.rst:59 +msgid "Building the image" +msgstr "Erzeugen des Images" + +#: ../../source/development/building-containers/containers-local.rst:61 +msgid "" +"Finally, when you have your repository and Dockerfile ready, use the " +"``docker build --tag=`` command to build the container image." +msgstr "Schließlich, wenn Sie Ihr Repository haben und Ihr Dockerfile erstellt ist, verwenden Sie das ``docker build --tag=``-Kommando, um das Container-Image zu erstellen." + diff --git a/source/locale/de/LC_MESSAGES/development/building-containers/standalone-containers.po b/source/locale/de/LC_MESSAGES/development/building-containers/standalone-containers.po new file mode 100644 index 0000000..427b711 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/development/building-containers/standalone-containers.po @@ -0,0 +1,147 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/development/building-containers/standalone-containers.rst:2 +msgid "Standalone containers" +msgstr "Standalone-Container" + +#: ../../source/development/building-containers/standalone-containers.rst:6 +msgid "About" +msgstr "Über" + +#: ../../source/development/building-containers/standalone-containers.rst:8 +msgid "" +"Standalone containers enable you to use containers in a similar way as " +"you use traditional system services. The goal is to preserve muscle " +"memory so you don't have to learn new commands while still being able to " +"work with containers." +msgstr "Standalone-Container ermöglichen es Ihnen, Container in ähnlicher Weise zu verwenden, wie Sie traditionelle Systemdienste verwenden. Ziel ist es, Sie keine neuen Befehle lernen zu lassen und Sie dennoch in die Lage zu versetzen, mit Containern zu arbeiten." + +#: ../../source/development/building-containers/standalone-containers.rst:14 +msgid "Requirements" +msgstr "Anforderungen" + +#: ../../source/development/building-containers/standalone-containers.rst:16 +msgid "" +"Only a single instance of a standalone container is supported to run on a" +" host (installation of the same container image twice won't be " +"successful)." +msgstr "Nur eine einzelne Instanz eines Standalone-Containers wird unterstützt, um auf einem Host ausgeführt zu werden (eine weitere Installation des gleichen Container-Images würde nicht erfolgreich verlaufen)." + +#: ../../source/development/building-containers/standalone-containers.rst:18 +msgid "Services are managed via systemd unit files." +msgstr "Dienste werden über Unit-Dateien in systemd verwaltet." + +#: ../../source/development/building-containers/standalone-containers.rst:19 +msgid "Containers are installed to a system." +msgstr "Container sind auf einem System installiert." + +#: ../../source/development/building-containers/standalone-containers.rst:20 +msgid "There is no dedicated network namespace." +msgstr "Es gibt keinen dedizierten Netzwerk-Namensraum." + +#: ../../source/development/building-containers/standalone-containers.rst:21 +msgid "" +"Configuration is stored in the same locations on the host as a non-" +"containerized service." +msgstr "Konfiguration wird an den gleichen Orten auf dem Host gespeichert, wie von nicht-containerisierten Diensten." + +#: ../../source/development/building-containers/standalone-containers.rst:23 +msgid "" +"Persistent data can be found in the same locations on the host as for " +"non-containerized service." +msgstr "Persistente Daten finden sich an den gleichen Orten auf dem Host, wie von nicht-containerisierten Diensten." + +#: ../../source/development/building-containers/standalone-containers.rst:25 +msgid "" +"Service presence, configuration and persistent data are tracked by the " +"RPM database." +msgstr "Servicepräsenz, Konfiguration und persistente Daten werden durch die RPM-Datenbank nachverfolgt." + +#: ../../source/development/building-containers/standalone-containers.rst:27 +msgid "Application lifecycle is close to services deployed as RPMs." +msgstr "Der Anwendungslebenszyklus liegt in der Nähe von Diensten, die als RPMs bereitgestellt werden." + +#: ../../source/development/building-containers/standalone-containers.rst:28 +msgid "" +"Some commands may need to be executed inside the container since the " +"service is not running directly on host." +msgstr "Einige Befehle müssen im Inneren des Containers ausgeführt werden, da der Dienst nicht direkt auf dem Host ausgeführt wird." + +#: ../../source/development/building-containers/standalone-containers.rst:33 +msgid "Quick how-to" +msgstr "Schnelles HowTo" + +#: ../../source/development/building-containers/standalone-containers.rst:35 +msgid "We utilize the atomic command to install a container image on a host." +msgstr "Wir verwenden das ``atomic``-Kommando, um ein Container-Image auf einem Host zu installieren." + +#: ../../source/development/building-containers/standalone-containers.rst:37 +msgid "" +"In order to get files from a container image to the host, you should have" +" a specific directory structure inside your container image. Here's an " +"example of nginx container image:" +msgstr "Um Dateien von einem Container-Image auf dem Host zu erhalten, sollten Sie eine bestimmte Verzeichnisstruktur in Ihrem Container-Image haben. Hier ist ein Beispiel eines Container-Image für Nginx:" + +#: ../../source/development/building-containers/standalone-containers.rst:80 +msgid "" +"**exports** directory is what atomic uses, it is in a root of the " +"container image" +msgstr "**exports** ist das Verzeichnis, das ``atomic`` verwendet, es liegt im Root des Container-Images." + +#: ../../source/development/building-containers/standalone-containers.rst:82 +msgid "" +"**hostfs** is a tree of directories and files which will land on the " +"host, tracked by a generated RPM" +msgstr "**hostfs** ist ein Baum von Verzeichnissen und Dateien, die auf dem Host landen. Dieses Verzeichnis wird überwacht von einem generierten RPM." + +#: ../../source/development/building-containers/standalone-containers.rst:84 +msgid "" +"a systemd unit :code:`nginx-container.service`, which controls the " +"containerized nginx, is placed in " +":code:`/exports/hostfs/usr/lib/systemd/system`" +msgstr "Eine systemd-Einheit :code:`nginx-container.service`, welche das containerisierte Nginx kontrolliert, befindet sich in :code:`/exports/hostfs/usr/lib/systemd/system`." + +#: ../../source/development/building-containers/standalone-containers.rst:88 +msgid "Here's the mentioned :code:`nginx-container.service`:" +msgstr "Hier ist der erwähnte :code:`nginx-container.service`:" + +#: ../../source/development/building-containers/standalone-containers.rst:105 +msgid "Once the image is built, you can install it like this:" +msgstr "Nachdem das Image erstellt wurde, können Sie es wie folgt installieren:" + +#: ../../source/development/building-containers/standalone-containers.rst:112 +msgid "" +"There is no released version of atomic with this functionality, yet. The " +"version of atomic command built `in this copr repo " +"`__ contains " +"the functionality to install standalone container image." +msgstr "Es gibt derzeit noch keine Release-Version des ``atomic``-Befehls mit dieser Funktionalität. Die Version des Builts des ``atomic``-Kommandos `in diesem Copr Repo `__ enthält die Funktionalität, um Standalone-Container-Images zu installieren." + +#: ../../source/development/building-containers/standalone-containers.rst:117 +msgid "" +"Most of the principles of standalone containers are based on the model & " +"technology of system containers. If you would like to know more about " +"system containers read `the blog post " +"`__." +msgstr "Die meisten Prinzipien von Standalone-Containern basieren auf dem Modell & der Technologie von System-Containern. Wenn Sie mehr wissen möchten über System-Container, lesen Sie `diesen Blog-Post `__." + diff --git a/source/locale/de/LC_MESSAGES/development/building-modules.po b/source/locale/de/LC_MESSAGES/development/building-modules.po new file mode 100644 index 0000000..e864ebf --- /dev/null +++ b/source/locale/de/LC_MESSAGES/development/building-modules.po @@ -0,0 +1,90 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/development/building-modules.rst:2 +msgid "Building Modules" +msgstr "Erstellen von Modulen" + +#: ../../source/development/building-modules.rst:4 +msgid "" +"Historically, all packages in Fedora have followed the same branching " +"structure in dist-git: each package had a separate branch for every " +"numbered Fedora release, and if you wanted to update a package across all" +" supported releases, you needed to submit the same change for each " +"release branch." +msgstr "Historisch gesehen folgten alle Pakete in Fedora der gleichen Verzweigungsstruktur in Dist-Git: Jedes Paket hatte einen separaten Zweig für jedes nummerierte Fedora-Release. Wenn ein Paket über alle unterstützten Releases aktualisiert werden sollte, musste die gleiche Änderung für jeden Release-Branch übertragen werden." + +#: ../../source/development/building-modules.rst:12 +msgid "" +"The module definition mechanism introduced in Fedora 27 allows this to be" +" separated such that:" +msgstr "Der in Fedora 27 eingeführte Mechanismus für Modul-Definitionen ermöglicht dies derart zu trennen, dass:" + +#: ../../source/development/building-modules.rst:15 +msgid "" +"package definitions in the `RPMs section " +"`__ of dist-git can use " +"branches that reflect *upstream* API and ABI compatibility assurances " +"(for example, using Python's X.Y release numbers for ``python3`` package " +"branches)" +msgstr "Paketdefinitionen aus dem `RPM-Bereich `__ von Dist-Git Branches verwenden können, die *Upstream* API- und ABI-Kompatibilitätsgarantien reflektieren (z. b. verwenden von Pythons X.Y-Release-Nummern für ``python3``-Paketzweige)" + +#: ../../source/development/building-modules.rst:20 +msgid "" +"module definitions in the `modules section " +"`__ of dist-git can " +"use branches that reflect a chosen stability period, whether that's " +"tracking a particular upstream release series, a set of arbitrary " +"calendar dates, a particular Fedora release, or even just the main line " +"of upstream development." +msgstr "Moduldefinitionen aus dem `Modulbereich `__ von Dist-Git Branches verwenden können, die einen gewählten Stabilitätszeitraum widerspiegeln, unabhängig davon, ob eine bestimmte Release-Serie im Upstream verfolgt wird, eine Reihe von frei wählbaren Kalenderterminen, ein bestimmtes Fedora-Release oder einfach nur die Hauptlinie der Upstream-Entwicklung." + +#: ../../source/development/building-modules.rst:26 +msgid "" +"the system profile for a given release then nominates the default streams" +" for each module known to the system. For example, the system profile for" +" the F27 modular server release can be found in the f27 branch of the " +"`fedora-modular-server repo`_ in dist-git." +msgstr "das Systemprofil für ein bestimmtes Release dann die Standard-Streams für jedes Modul benennt, das dem System bekannt ist. Das Systemprofil für das F27 Modular Server-Release kann beispielsweise im `f27`-Zweig des `fedora-modular-server repo`_ auf Dist-Git gefunden werden." + +#: ../../source/development/building-modules.rst:37 +msgid "" +"On the Fedora usage side, the advantage to end users of the module " +"system, is that while the system profile specifies a *default* stream, it" +" typically doesn't keep end users from *changing* that stream (modules " +"with streams that specifically track particular Fedora releases may be an" +" exception)." +msgstr "Auf der Fedora-Anwendungsseite ist der Vorteil für Endbenutzer des Modulsystems, dass, während das Systemprofil einen *Standard*-Stream spezifiziert, es in der Regel Endbenutzer nicht davon abhält diesen Stream zu *ändern* (Module mit Streams, die gezielt spezielle Fedora-Releases verfolgen, können eine Ausnahme sein)." + +#: ../../source/development/building-modules.rst:42 +msgid "" +"For example, Fedora 27 will select ``8`` as the default stream for the " +"Node.js module. If you run ``dnf install nodejs`` in F27 Modular Server, " +"it will implicitly give you a ``nodejs-8`` RPM. However, unlike a " +"traditional Fedora release, you're also able to explicitly opt-in to " +"downgrading to the Node.js 6 LTS release by running the command ``dnf " +"install nodejs:6``." +msgstr "Beispielsweise wird Fedora 27 ``8`` als Standard-Stream für das Node.js-Modul auswählen. Wenn Sie ``dnf install nodejs`` in F27 Modular Server ausführen, gibt es implizit ein ``nodejs-8``-RPM heraus. Allerdings, im Gegensatz zu einem herkömmlichen Fedora-Release, sind Sie auch in der Lage, explizit ein Opt-In zu einem Downgrade auf den Node.js 6 LTS Release auszuführen mittels des Befehls ``dnf install nodejs:6``." + +#: ../../source/development/building-modules.rst:52 +msgid "Module Development Guidelines" +msgstr "Leitfaden für die Entwicklung von Modulen" + diff --git a/source/locale/de/LC_MESSAGES/development/building-modules/adding-modules-to-fedora.po b/source/locale/de/LC_MESSAGES/development/building-modules/adding-modules-to-fedora.po new file mode 100644 index 0000000..0bb0ec2 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/development/building-modules/adding-modules-to-fedora.po @@ -0,0 +1,44 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/development/building-modules/adding-modules-to-fedora.rst:2 +msgid "Adding modules to Fedora" +msgstr "Hinzufügen von Modulen zu Fedora" + +#: ../../source/development/building-modules/adding-modules-to-fedora.rst:4 +msgid "" +"The `packaging guidelines for modules " +"`__ and the `review " +"process `__ are " +"final and approved. Please, go ahead and submit that review request! Make" +" sure to search for a reviewer on the Freenode IRC channel :code" +":`#fedora-modularity`." +msgstr "Die `Paketierungsrichtlinien für Module `__ und der `Review-Prozess `__ sind endgültig und genehmigt. Fahren Sie fort und stellen Sie eine Review-Anfrage! Denken Sie daran, einen Rezensenten auf dem Freenode-IRC-Channel zu suchen :code:`#fedora-modularitiy`." + +#: ../../source/development/building-modules/adding-modules-to-fedora.rst:11 +msgid "" +"Modular repositories are available in the `fedora dist-git " +"`__ under the module namespace. See the " +"`httpd module `__ as an " +"example or `many others " +"`__." +msgstr "Modulare Repositorys sind verfügbar in `Fedora Dist-Git `__ unter dem Modul-Namensraum. Siehe `httpd module `__ als Beispiel oder auch `viele andere `__." + diff --git a/source/locale/de/LC_MESSAGES/development/building-modules/building-infra.po b/source/locale/de/LC_MESSAGES/development/building-modules/building-infra.po new file mode 100644 index 0000000..976af98 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/development/building-modules/building-infra.po @@ -0,0 +1,33 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity package. +# FIRST AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-18 20:27+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Translate Toolkit 2.2.5\n" + +#: ../../source/development/building-modules/building-infra.rst:2 +msgid "Building modules in Fedora" +msgstr "Erzeugen von Modulen in Fedora" + +#: ../../source/development/building-modules/building-infra.rst:4 +msgid "Module builds in Fedora are currently managed by fedpkg. First step is to clone the dist-git repository of your module. For example to clone an existing `nodejs` module and checkout to the `8` stream, run:" +msgstr "Modul-Builds in Fedora werden derzeit mittels Fedpkg verwaltet. Der erste Schritt besteht darin, das Dist-Git-Repository Ihres Moduls zu klonen. Um beispielsweise ein vorhandenes `nodejs`-Modul zu klonen und den `8`-Stream auszuchecken, führen Sie Folgendes aus:" + +#: ../../source/development/building-modules/building-infra.rst:15 +msgid "A new build is submitted by the following command:" +msgstr "Ein neuer Build wird mit dem folgenden Befehl übermittelt:" + +#: ../../source/development/building-modules/building-infra.rst:21 +msgid "Fedpkgs provides other modularity-related subcommands:" +msgstr "Fedpkg stellt weitere modularitätsbezogene Unterbefehle zur Verfügung:" diff --git a/source/locale/de/LC_MESSAGES/development/building-modules/building-local.po b/source/locale/de/LC_MESSAGES/development/building-modules/building-local.po new file mode 100644 index 0000000..1a51bcc --- /dev/null +++ b/source/locale/de/LC_MESSAGES/development/building-modules/building-local.po @@ -0,0 +1,112 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/development/building-modules/building-local.rst:2 +msgid "Building modules locally" +msgstr "Lokales Erzeugen von Modulen" + +#: ../../source/development/building-modules/building-local.rst:4 +msgid "" +"To build a modulemd, you need to have the `Module Build Service " +"`__ installed on your system." +msgstr "Um ein Modulemd zu erstellen, müssen Sie den `Module Build Service `__ auf Ihrem System installiert haben." + +#: ../../source/development/building-modules/building-local.rst:8 +msgid "Install it like this:" +msgstr "Installieren Sie es wie folgt:" + +#: ../../source/development/building-modules/building-local.rst:14 +msgid "" +"``mock-scm`` currently needs to be installed explicitly due to a missing " +"runtime dependency declaration in the ``module-build-service`` RPM." +msgstr "Derzeit muss ``mock-scm`` noch ausdrücklich installiert werden, aufgrund der fehlenden Deklarierung einer Runtime-Abhängigkeit im ``module-build-service``-RPM." + +#: ../../source/development/building-modules/building-local.rst:18 +msgid "Then add your user to the mock group:" +msgstr "Fügen Sie Ihren Benutzer zur `mock`-Gruppe bei:" + +#: ../../source/development/building-modules/building-local.rst:24 +msgid "" +"To build your module, run a command similar to the following in the local" +" git repository of your module:" +msgstr "Um Ihr Modul zu erstellen, führen Sie einen Befehl ähnlich dem folgenden, im lokalen Git-Repository Ihres Moduls aus:" + +#: ../../source/development/building-modules/building-local.rst:31 +msgid "" +"With the default configuration, this should generate a yum/dnf repository" +" beneath the directory ``modulebuild`` in the home of the user." +msgstr "Mit der Standardkonfiguration sollte dies ein YUM-/DNF-Repository unter dem Verzeichnis `modulebuild` im Heimverzeichnis des Benutzers generieren." + +#: ../../source/development/building-modules/building-local.rst:34 +msgid "" +"To test your local build environment on Fedora, the ``haproxy`` module is" +" a reasonable example module to start with:" +msgstr "Um Ihre lokale Build-Umgebung auf Fedora zu testen, ist das ``haproxy``-Modul ein sinnvolles Beispielmodul für den Beginn:" + +#: ../../source/development/building-modules/building-local.rst:45 +msgid "" +"As an interim bootstrapping technique, many of the F26 Boltron modules " +"will download and cache around 15k RPMs from Koji as potential build " +"dependencies. ``haproxy`` is recommended as an example module " +"specifically because it *doesn't* do that and instead only downloads what" +" it needs to build the RPMs it contains." +msgstr "Als eine vorläufige Bootstrapping-Technik, werden viele der F26 Boltron Module rund 15.000 RPMs von Koji als potenzielle Build-Abhängigkeiten herunterladen und cachen. ``haproxy`` wird als Beispielmodul empfohlen, speziell, weil es eben genau das *nicht* tut und stattdessen nur herunterlädt, was es braucht, um die RPMs zu bauen, die es enthält." + +#: ../../source/development/building-modules/building-local.rst:51 +msgid "" +"Replacing that bulk download with proper build dependency management more" +" generally is part of the work being undertaken in F27." +msgstr "Diesen Massendownload mit einem ordentlichen Management für die Build-Abhängigkeiten zu ersetzen ist Bestandteil der Arbeit, die in F27 vorgenommen wird." + +#: ../../source/development/building-modules/building-local.rst:55 +msgid "Building against other locally built modules" +msgstr "Erzeugen gegen andere lokal erstellte Module" + +#: ../../source/development/building-modules/building-local.rst:57 +msgid "" +"Normally, the module build service obtains all build-time dependencies of" +" your module from the Koji server. If you want to build multiple modules " +"depending on each other you can do that by using the ``--add-local-" +"build`` (or ``-l``) option of ``mbs-build``." +msgstr "Normalerweise erhält der Modul-Build-Service alle Build-Time-Abhängigkeiten Ihres Moduls vom Koji-Server. Wenn Sie mehrere Module bauen möchten, die voneinander abhängig sind, können Sie dies mithilfe der ``--add-local-build``- (oder ``-l``-)Option von ``mbs-build`` tun." + +#: ../../source/development/building-modules/building-local.rst:63 +msgid "" +"This option is only available in version 1.3.26 or later of the module " +"build service." +msgstr "Diese Option ist nur verfügbar ab der Version 1.3.26 des Modul-Build-Service." + +#: ../../source/development/building-modules/building-local.rst:66 +msgid "" +"For example, to build a module against a locally built ``perl`` module, " +"you can do the following:" +msgstr "Um ein Modul gegen ein lokal gebautes ``perl``-Modul zu erstellen, können Sie z. B. Folgendes tun:" + +#: ../../source/development/building-modules/building-local.rst:73 +msgid "Specify multiple local module builds like this:" +msgstr "So legen Sie mehrere lokale Modul-Builds fest:" + +#: ../../source/development/building-modules/building-local.rst:79 +msgid "" +"You can even specify particular streams and versions of local module " +"builds which should be used as dependencies:" +msgstr "Sie können sogar bestimmte Streams und Versionen von lokalen Modul-Builds spezifizieren, die als Abhängigkeiten verwendet werden sollen:" + diff --git a/source/locale/de/LC_MESSAGES/development/building-modules/developing.po b/source/locale/de/LC_MESSAGES/development/building-modules/developing.po new file mode 100644 index 0000000..9079c83 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/development/building-modules/developing.po @@ -0,0 +1,213 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity package. +# FIRST AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-18 20:27+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Translate Toolkit 2.2.5\n" + +#: ../../source/development/building-modules/developing.rst:2 +msgid "Defining modules in modulemd" +msgstr "Definieren von Modulen in Modulemd" + +#: ../../source/development/building-modules/developing.rst:4 +msgid "To have your module build, you need to write a `modulemd `__ file which is the definition of your module including the components, dependencies, API, and more. This page describes all the steps a module developer needs to do to define a module." +msgstr "Um Ihr Modul zu erzeugen, müssen Sie mit dem Schreiben einer `Modulemd `__-Datei beginnen, die eine Definition Ihres Moduls ist, einschließlich der Komponenten, Abhängigkeiten, API und mehr. Diese Seite beschreibt alle Schritte, die ein Modulentwickler benötigt, um ein Modul zu definieren." + +#: ../../source/development/building-modules/developing.rst:10 +msgid "Examples" +msgstr "Beispiele" + +#: ../../source/development/building-modules/developing.rst:12 +msgid "To have an idea about the final result, please have a look at some existing modules in the Fedora dist-git:" +msgstr "Um sich eine Idee zu machen von dem Endergebnis, schauen Sie sich bitte einige existierende Module in Fedora Dist-Git an:" + +#: ../../source/development/building-modules/developing.rst:15 +msgid "`PostgreSQL 9.6 `__" +msgstr "`PostgreSQL 9.6 `__" + +#: ../../source/development/building-modules/developing.rst:16 +msgid "`Node.js 8 `__" +msgstr "`Node.js 8 `__" + +#: ../../source/development/building-modules/developing.rst:17 +msgid "`Node.js 6 `__" +msgstr "`Node.js 6 `__" + +#: ../../source/development/building-modules/developing.rst:18 +msgid "`autotools `__" +msgstr "`autotools `__" + +#: ../../source/development/building-modules/developing.rst:20 +msgid "The final module definition will be similar to the following example. Please note that the example might not represent an actual buildable module - dependencies or package names have changed - but it shows the overall structure with all the fields this guide will be going through." +msgstr "Die endgültige Moduldefinition wird dem folgenden Beispiel ähneln. Bitte beachten Sie, dass das Beispiel möglicherweise kein aktuell erzeugbares Modul repräsentiert. – Abhängigkeiten oder Paketnamen haben sich eventuell geändert. Aber es zeigt die Gesamtstruktur mit allen Feldern, die dieser Leitfaden durchlaufen wird." + +#: ../../source/development/building-modules/developing.rst:26 +msgid "Prerequisites - tooling" +msgstr "Voraussetzungen – Werkzeuge" + +#: ../../source/development/building-modules/developing.rst:28 +msgid "`Fedmod `__ is a tool providing basic operation that significantly simplify the process of creating a new module. Please install it before we start:" +msgstr "`Fedmod `__ ist ein Tool, das grundlegende Operationen bereitstellt, die den Prozess der Erstellung eines neuen Moduls erheblich vereinfachen. Bitte installieren Sie es, bevor wir beginnen:" + +#: ../../source/development/building-modules/developing.rst:40 +msgid "Defining the module" +msgstr "Definieren des Moduls" + +#: ../../source/development/building-modules/developing.rst:42 +msgid "Let's start with the following template and fill it in as we go." +msgstr "Beginnen wir mit der folgenden Vorlage und füllen diese im weiteren Verlauf aus." + +#: ../../source/development/building-modules/developing.rst:85 +msgid "Step 1: Deciding what the module is" +msgstr "Schritt 1: Entscheiden, was das Modul ausmacht" + +#: ../../source/development/building-modules/developing.rst:87 +msgid "The first step is to identify a package (or a set of packages) that form the core of the module. For example, to create an `nginx` module for the NGINX web server, the `nginx` package will be the core." +msgstr "Der erste Schritt besteht darin, ein Paket (oder eine Reihe von Paketen) zu identifizieren, die den Kern des Moduls bilden. Zum Beispiel, um ein `nginx`-Modul für den Nginx-Webserver zu erstellen, wird das `nginx`-Paket den Kern bilden." + +#: ../../source/development/building-modules/developing.rst:91 +msgid "Based on this, fill in the `summary`, `description`, `license`, and `references` fields. Also add the main package(s) to `components`. Please note that the `components.rpms` field expects SRPM package names." +msgstr "Füllen Sie dazu die Felder `summary`, `description`, `license`, und `references` aus. Fügen Sie auch das Hauptpaket(e) zu `components` hinzu. Bitte beachten Sie, dass das Feld `components.rpms` SRPM-Paketnamen erwartet." + +#: ../../source/development/building-modules/developing.rst:119 +msgid "Step 2: Dependencies" +msgstr "Schritt 2: Abhängigkeiten" + +#: ../../source/development/building-modules/developing.rst:121 +msgid "Every module needs to specify its runtime and build dependencies. These are modular dependencies (usually at least the `platform` module), and RPM dependencies (everything else that is not provided by the modular dependencies)." +msgstr "Jedes Modul muss seine Runtime und Build-Abhängigkeiten spezifizieren. Hierbei handelt es sich um modulare Abhängigkeiten (normalerweise zumindest das `platform`-Modul) und RPM-Abhängigkeiten (alles andere, was nicht von den modularen Abhängigkeiten bereitgestellt wird)." + +#: ../../source/development/building-modules/developing.rst:126 +msgid "This is where the Fedmod tool becomes handy. To list all dependencies of a given package (`nginx` in this case), run:" +msgstr "An dieser Stelle wird das Fedmod-Werkzeug nützlich. Um alle Abhängigkeiten eines bestimmten Pakets (`nginx` in diesem Fall) aufzulisten, führen Sie Folgendes aus:" + +#: ../../source/development/building-modules/developing.rst:134 +msgid "This will return a very long list of packages. Many of these are included in the `platform` module. Let's get all the missing dependencies that are not in `platform` by running:" +msgstr "Dadurch wird eine sehr lange Liste von Paketen zurückgegeben. Viele davon sind im `platform`-Modul enthalten. Lassen Sie uns alle fehlenden Abhängigkeiten finden, die nicht in `platform` enthalten sind:" + +#: ../../source/development/building-modules/developing.rst:143 +msgid "This looks much better, right? At the time of writing this document, fedmod returned the following four packages:" +msgstr "Das sieht viel besser aus, oder? Zum Zeitpunkt der Erstellung dieses Dokuments gab Fedmod die folgenden vier Pakete aus:" + +#: ../../source/development/building-modules/developing.rst:154 +msgid "Fedmod can also tell if a certain package has been already added to an existing module. To find whether the `gperftools-libs` is already somewhere, run:" +msgstr "Fedmod kann auch erkennen, ob ein bestimmtes Paket bereits zu einem vorhandenen Modul hinzugefügt wurde. Um herauszufinden, ob die `gperftools-libs` bereits irgendwo vorliegen, führen wir dieses Kommando aus:" + +#: ../../source/development/building-modules/developing.rst:162 +msgid "At the time of writing, the `gperftools-libs` package is already in one module, the `389-ds` module which is an LDAP server. In this case, it doesn't make sense to use the `389-ds` module as a dependency of `nginx`. There are two ways how to resolve this problem:" +msgstr "Zum Zeitpunkt des Schreibens ist das `gperftools-libs`-Paket bereits in einem Modul vorhanden: dem `389-ds`-Modul, welches ein LDAP-Server ist. In diesem Fall ist es nicht sinnvoll, das `389-ds`-Modul als Abhängigkeit von `nginx` zu verwenden. Es gibt zwei Möglichkeiten, dieses Problem zu beheben:" + +#: ../../source/development/building-modules/developing.rst:167 +msgid "Work with a maintainer of the `389-ds` module and get the `gperftools-libs` package separated into another, shared module. Maybe it could be added to the `platform` module." +msgstr "Arbeiten Sie mit einem Maintainer des `389-ds`-Moduls und bekommen Sie so das `gperftools-libs`-Paket separiert in ein anderes Modul, dass diese Bibliothek allgemein zur Verfügung stellt. Eventuell könnte es zum `platform`-Modul hinzugefügt werden." + +#: ../../source/development/building-modules/developing.rst:170 +msgid "Bundle the package in your module. Please note that this might make the `nginx` module conflict with the `389-ds` module. But this is the way we go in this guide." +msgstr "Bündeln Sie das Paket in Ihrem Modul. Bitte beachten Sie, dass dies zu einem Konflikt des `nginx`-Moduls mit dem `389-ds`-Modul führen könnte. Aber dies ist der Weg, den wir in diesem Leitfaden einschlagen." + +#: ../../source/development/building-modules/developing.rst:174 +msgid "As mentioned before, the modulemd file expect components to be listed as SRPM packages. Fedmod can give you an SRPM package name for a given RPM. Let's try it for the `nginx-mimetypes` package by running:" +msgstr "Wie bereits erwähnt, erwartet die Modulemd-Datei, dass Komponenten als SRPM-Pakete aufgelistet werden. Fedmod kann Ihnen einen SRPM-Paketnamen für ein gegebenes RPM geben. Versuchen wir es für das `nginx-mimetypes`-Paket, durch das Ausführen von:" + +#: ../../source/development/building-modules/developing.rst:183 +msgid "By doing this for all the packages, the result was:" +msgstr "Indem wir dies für alle Pakete tun, wird das Ergebnis wie folgt aussehen:" + +#: ../../source/development/building-modules/developing.rst:193 +msgid "The `nginx` package is already present in the `components.rpms` field. We just need to add the mailcap and gperftools packages in the `components.rpms` field and the platform module as a runtime dependency." +msgstr "Das `nginx`-Paket ist bereits im Feld `components.rpms` vorhanden. Wir müssen lediglich die `mailcap`- und `gperftools`-Pakete im `components.rpms`-Feld und das `platform`-Modul als Laufzeitabhängigkeit hinzufügen." + +#: ../../source/development/building-modules/developing.rst:197 +msgid "With this, we have resolved the runtime dependencies. The next step would be resolving all the build dependencies for this module. However, not all build dependencies might have been modularized. As a workaround, we use a `bootstrap` module as the only build dependency right now." +msgstr "Damit haben wir die Laufzeitabhängigkeiten aufgelöst. Im nächsten Schritt werden alle Build-Abhängigkeiten für dieses Modul aufgelöst. Möglicherweise wurden jedoch nicht alle Build-Abhängigkeiten modularisiert. Als Workaround verwenden wir deswegen jetzt ein `bootstrap`-Modul als die einzige Build-Abhängigkeit." + +#: ../../source/development/building-modules/developing.rst:202 +msgid "After doing these changes, our modulemd will look as follows:" +msgstr "Nach diesen Änderungen wird unsere Modulemd wie folgt aussehen:" + +#: ../../source/development/building-modules/developing.rst:241 +msgid "What do you support" +msgstr "Was Sie supporten" + +#: ../../source/development/building-modules/developing.rst:243 +msgid "As modules contain the main packages, along with their dependencies, it is useful to distinguish between these two. The module maintainer will probably offer an API/ABI stability on the main packages, but the dependencies might be considered an implementation detail. To communicate this clearly, add all the main packages to the `api` field in your modulemd. In this case, it could be the `nginx`, `nginx-filesystem`, and the `nginx-mimetypes` packages." +msgstr "Da Module die Hauptpakete zusammen mit ihren Abhängigkeiten enthalten, ist es sinnvoll, zwischen diesen beiden zu unterscheiden. Der Modulentwickler wird möglicherweise eine API-/ABI-Stabilität auf den Hauptpaketen anbieten, aber die Abhängigkeiten können als Implementierungsdetail betrachtet werden. Um dies klar zu kommunizieren, fügen Sie alle Hauptpakete in das `api`-Feld in Ihrer Modulemd ein. In diesem Fall könnten es die `nginx`-, `nginx-filesystem`-, und `nginx-mimetypes`-Pakete sein." + +#: ../../source/development/building-modules/developing.rst:291 +msgid "Pre-defined installation profiles" +msgstr "Vordefinierte Installationsprofile" + +#: ../../source/development/building-modules/developing.rst:293 +msgid "To help users with installing this module, a set of installation profiles can and at least one should be defined for the module." +msgstr "Um Benutzern bei der Installation dieses Moduls zu helfen, kann eine Reihe von Installationsprofilen für das Modul definiert werden – und mindestens eines sollte vorliegen." + +#: ../../source/development/building-modules/developing.rst:296 +msgid "Profiles are very nicely described in the `modulemd `__ specification. In short, they are lists of packages to be installed on a system." +msgstr "Profile sind in der `Modulemd `__-Spezifikation sehr schön beschrieben. Kurz gesagt, es sind Listen von Paketen, die auf einem System installiert werden sollen." + +#: ../../source/development/building-modules/developing.rst:300 +msgid "For example, a database module might define two installation profiles, `client` and `server`, to help the user install the right package for each use case." +msgstr "Ein Datenbankmodul kann z. b. zwei Installationsprofile definieren: `client` und `server`, um dem Benutzer zu helfen, das richtige Paket für jeden Anwendungsfall zu installieren." + +#: ../../source/development/building-modules/developing.rst:304 +msgid "Some profile names, such as `default`, are reserved. The `default` profile is installed by default if user doesn't specify any other profile. In this case, our module will only contain this `default` profile." +msgstr "Einige Profilnamen, z. b. `default`, sind reserviert. Das `default`-Profil wird standardmäßig installiert, wenn der Benutzer kein anderes Profil angibt. In diesem Fall enthält unser Modul nur dieses `default`-Profil." + +#: ../../source/development/building-modules/developing.rst:353 +msgid "Validating the modulemd syntax" +msgstr "Validieren der Modulemd-Syntax" + +#: ../../source/development/building-modules/developing.rst:355 +msgid "Once the modulemd file is finished, it is a good idea to check if there any errors in the yaml syntax. The `check\\_modulemd `__ program checks modulemd files for errors. You need to install some packages to use this:" +msgstr "Sobald die Modulemd-Datei erstellt ist, ist es eine gute Idee zu überprüfen, ob es irgendwelche Fehler in der YAML-Syntax gibt. Das `check\\_modulemd `__-Programm überprüft Modulemd-Dateien auf Fehler. Sie müssen einige Pakete installieren, um es zu verwenden:" + +#: ../../source/development/building-modules/developing.rst:361 +msgid "python2-aexpect - dependency for python-avocado" +msgstr "`python2-aexpect` – Abhängigkeit für `python-avocado`" + +#: ../../source/development/building-modules/developing.rst:362 +msgid "python2-avocado - avocado testing framework" +msgstr "`python2-avocado` – avocado-testing-Framework" + +#: ../../source/development/building-modules/developing.rst:363 +msgid "python2-modulemd - Module metadata manipulation library" +msgstr "`python2-modulemd` – Manipulationsbibliothek für Modulmetadaten" + +#: ../../source/development/building-modules/developing.rst:364 +msgid "python-enchant - spell checker library (needed only for check\\_modulemd.py)" +msgstr "`python-enchant` – Bibliothek für die Rechtschreibprüfung (lediglich für `check\\_modulemd.py` benötigt)" + +#: ../../source/development/building-modules/developing.rst:366 +msgid "hunspell-en-US - English dictionary (needed only for check\\_modulemd.py)" +msgstr "`hunspell-en-US` – Englisch-Wörterbuch (nur für `check\\_modulemd.py` benötigt)" + +#: ../../source/development/building-modules/developing.rst:370 +msgid "Then run" +msgstr "Führen Sie dann folgendes aus" + +#: ../../source/development/building-modules/developing.rst:376 +msgid "and check the output for errors:" +msgstr "und überprüfen Sie die Ausgabe nach Fehlern:" + +#: ../../source/development/building-modules/developing.rst:398 +msgid "So this isn't quite right yet, lets have a look at the logfile mentioned in the output." +msgstr "So ist es noch nicht ganz richtig. Werfen wir einen Blick auf die Log-Datei, die in der Ausgabe erwähnt wurde." + +#: ../../source/development/building-modules/developing.rst:407 +msgid "It seems that rationales need to end with a period. Change all those lines so that they look like this:" +msgstr "Es scheint, dass Zeilen mit Erläuterungen (`rationale:`) mit einem Punkt enden müssen. Ändern Sie diese Zeilen, damit sie so aussehen:" + +#: ../../source/development/building-modules/developing.rst:432 +msgid "Another run of check\\_modulemd.py completes without errors." +msgstr "Ein neuer Durchlauf von `check\\_modulemd.py` wird ohne Fehler abgeschlossen." diff --git a/source/locale/de/LC_MESSAGES/development/building-modules/installation-dependency-issues.po b/source/locale/de/LC_MESSAGES/development/building-modules/installation-dependency-issues.po new file mode 100644 index 0000000..f1ce84c --- /dev/null +++ b/source/locale/de/LC_MESSAGES/development/building-modules/installation-dependency-issues.po @@ -0,0 +1,141 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity package. +# FIRST AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-18 20:27+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: Translate Toolkit 2.2.5\n" + +#: ../../source/development/building-modules/installation-dependency-issues.rst:5 +msgid "Examining dependency issues during the installation of modules" +msgstr "Untersuchen von Abhängigkeitsproblemen bei der Installation von Modulen" + +#: ../../source/development/building-modules/installation-dependency-issues.rst:7 +msgid "A common problem while installing a module is that one or more of its components have requirements which cannot be fulfilled." +msgstr "Ein häufiges Problem beim Installieren eines Moduls besteht darin, dass eine oder mehrere seiner Komponenten Anforderungen haben, die nicht erfüllt werden können." + +#: ../../source/development/building-modules/installation-dependency-issues.rst:10 +msgid "This document describes scenarios in which this can happen and possible solutions. It assumes that the module in question is successfully built in official infrastructure and available on the examined system for installation. You can verify the latter with ``dnf module list`` or ``dnf module list ``." +msgstr "Dieses Dokument beschreibt Szenarien, in denen so etwas passieren kann und benennt mögliche Lösungen. Es geht davon aus, dass das fragliche Modul erfolgreich in der offiziellen Infrastruktur erzeugt wurde und auf dem zu prüfenden System zur Installation verfügbar ist. Sie können Letzteres mit ``dnf module list`` oder ``dnf module list `` überprüfen." + +#: ../../source/development/building-modules/installation-dependency-issues.rst:17 +msgid "Scenarios" +msgstr "Szenarien" + +#: ../../source/development/building-modules/installation-dependency-issues.rst:19 +msgid "Dependency problems while installing a module can happen for a variety of reasons:" +msgstr "Abhängigkeitsprobleme bei der Installation eines Moduls können aus einer Vielzahl von Gründen passieren:" + +#: ../../source/development/building-modules/installation-dependency-issues.rst:23 +msgid "RPM-level packaging errors" +msgstr "Paketierungsfehler auf RPM-Level" + +#: ../../source/development/building-modules/installation-dependency-issues.rst:25 +msgid "One of the packages involved is packaged wrongly, i.e. that the package is available but carries a requirement which can't be fulfilled, for instance because of typos, versioning issues, requiring a private library that isn't listed as being satisfied by the package carrying it. Solving this is beyond the scope of this document." +msgstr "Eines der beteiligten Pakete ist fehlerhaft paketiert, d. h., dass das Paket verfügbar ist, aber eine Anforderung stellt, die nicht erfüllt werden kann. Zum Beispiel aufgrund von Tippfehlern, Versionierungsproblemen oder dem Benötigen einer privaten Bibliothek, die als nicht erfüllbar gelistet wird durch das Paket, dass diese enthält. Dies zu lösen ist außerhalb des Rahmens dieses Dokuments." + +#: ../../source/development/building-modules/installation-dependency-issues.rst:32 +msgid "The dependency can be satisfied by another module" +msgstr "Die Abhängigkeit kann von einem anderen Modul erfüllt werden" + +#: ../../source/development/building-modules/installation-dependency-issues.rst:34 +msgid "Another available module contains a package which would satisfy the requirement but that module isn't pulled in as a runtime dependency. In most cases adding that missing dependency should fix the issue." +msgstr "Ein weiteres verfügbares Modul enthält ein Paket, das die Anforderung erfüllen würde, aber dieses Modul wird nicht als Runtime-Abhängigkeit mit hereingezogen. In den meisten Fällen sollte das Hinzufügen der fehlenden Abhängigkeit das Problem beheben." + +#: ../../source/development/building-modules/installation-dependency-issues.rst:39 +msgid "Another module could satisfy the dependency in theory but doesn't" +msgstr "Ein anderes Modul könnte die Abhängigkeit theoretisch zur Verfügung stellen, aber tut dies nicht" + +#: ../../source/development/building-modules/installation-dependency-issues.rst:41 +msgid "A package that would satisfy the requirement is built by this or another available module but is filtered out after building, by being listed in the ``data/filter/rpms`` section of the modulemd file. A likely reason that it is listed there is that it in turn isn't installable because one of its requirements can't be fulfilled. Depending on the circumstances, there are different possible approaches:" +msgstr "Ein Paket, das die Anforderung erfüllen würde, wird von diesem oder einem anderen verfügbaren Modul erstellt. Allerdings wird es nach dem Erstellen ausgefiltert, indem es im Abschnitt ``data/filter/rpms`` der Modulemd-Datei aufgelistet wird. Ein wahrscheinlicher Grund, dass es dort aufgeführt wird, ist dass es nicht installierbar ist, da eine seiner Anforderungen nicht erfüllt werden kann. Je nach den Umständen gibt es verschiedene Ansätze:" + +#: ../../source/development/building-modules/installation-dependency-issues.rst:48 +msgid "Not filter the package out in the other module (and solve any issues it may have in the process)." +msgstr "Filtern Sie das Paket in dem anderen Modul nicht aus (und lösen Sie anfallende Probleme innerhalb des Prozesses)." + +#: ../../source/development/building-modules/installation-dependency-issues.rst:50 +msgid "Remove the hard dependency from the package that depends on it. For instance, there are a lot of packages with hard dependencies which should rather be weak ones, but weak dependencies didn't exist in Fedora by the time these dependencies were created. In this case converting that hard (\"Requires:\") to a weak dependency (\"Recommends:\") can do the trick." +msgstr "Entfernen Sie die harte Abhängigkeit von dem Paket, das davon abhängt. Zum Beispiel gibt es eine Menge von Paketen mit harten Abhängigkeiten, die eher schwach sein sollten, aber schwache Abhängigkeiten existierten nicht in Fedora als diese Abhängigkeiten erstellt wurden. In diesem Fall kann das Konvertieren der harten (\"Requires:\") zu einer schwachen Abhängigkeit (\"Recommends:\") ausreichend sein." + +#: ../../source/development/building-modules/installation-dependency-issues.rst:55 +msgid "Filter out the package pulling in the dependency in the first place." +msgstr "Filtern Sie das Paket aus, das die Abhängigkeit ursprünglich hereinzieht." + +#: ../../source/development/building-modules/installation-dependency-issues.rst:58 +msgid "The package isn't part of any available module" +msgstr "Das Paket ist nicht Teil irgendeines verfügbaren Moduls" + +#: ../../source/development/building-modules/installation-dependency-issues.rst:60 +msgid "If a package that would fulfill a dependency isn't part of any available module, one can add it to an existing module as a component or to create a new module for it (if filtering out the package that causes the dependency isn't an option). If the component on its own is only useful in conjunction with the software contained in the module that can't be installed the best place is to put it there. If it has wider uses, a decision needs to be made if another existing module or a newly created one is the best place for it." +msgstr "Wenn ein Paket, das eine Abhängigkeit erfüllen würde, nicht Teil eines verfügbaren Moduls ist, sind die vorhandenen Optionen: Es einem vorhandenen Modul als Komponente hinzuzufügen oder ein neues Modul für dieses zu kreieren (falls das Ausfiltern des Paketes, das diese Abhängigkeit benötigt, keine Option darstellt). Wenn die Komponente für sich allein nur in Verbindung mit der Software in dem Modul nützlich ist, die nicht installiert werden kann, ist dies der Ort sie zu platzieren. Wenn es darüber hinausgehende Verwendungen hat, muss eine Entscheidung getroffen werden, ob ein anderes vorhandenes Modul oder ein neu erstelltes der beste Ort dafür ist." + +#: ../../source/development/building-modules/installation-dependency-issues.rst:69 +msgid "Package conflicts" +msgstr "Paketkonflikte" + +#: ../../source/development/building-modules/installation-dependency-issues.rst:71 +msgid "If any of the packages which are installed on the system or would be installed with the module conflict with each other because of the contained files, version requirements or the like, these need to be resolved. How that is done is outside the scope of this document." +msgstr "Wenn irgendwelche Pakete, die auf dem System installiert sind oder zusammen mit dem Modul installiert würden, in Konflikt miteinander stehen aufgrund der enthaltenen Dateien, Versionsanforderungen oder dergleichen, muss dies gelöst werden. Wie dies geschieht, liegt außerhalb des Rahmens dieses Dokuments." + +#: ../../source/development/building-modules/installation-dependency-issues.rst:77 +msgid "More detailed recipes" +msgstr "Detailliertere Rezepte" + +#: ../../source/development/building-modules/installation-dependency-issues.rst:80 +msgid "General considerations" +msgstr "Allgemeine Überlegungen" + +#: ../../source/development/building-modules/installation-dependency-issues.rst:82 +msgid "Fixing component-level dependency issues can generally be done in two ways: Either by providing whatever is missing or by removing the need for it in the first place." +msgstr "Das Beheben von Abhängigkeitsproblemen auf Komponentenebene kann in der Regel auf zwei Arten erfolgen: Entweder dadurch, bereitzustellen, was auch immer fehlt oder durch Entfernen der Notwendigkeit." + +#: ../../source/development/building-modules/installation-dependency-issues.rst:87 +msgid "Filtering out packages" +msgstr "Ausfiltern von Paketen" + +#: ../../source/development/building-modules/installation-dependency-issues.rst:89 +msgid "If a package whose dependency can't be fulfilled isn't part of the API of the module or required directly or indirectly by an API package it can be filtered out by adding it to the ``data/filter/rpms`` list in the modulemd file. This is an approach that usually requires little work beyond establishing that these prerequisites are met." +msgstr "Wenn ein Paket, dessen Abhängigkeit nicht erfüllt werden kann, nicht Teil der API des Moduls ist oder direkt oder indirekt durch ein API-Paket benötigt wird, kann es herausgefiltert werden, indem es zur ``data/filter/rpms``-Liste in der Modulemd-Datei hinzugefügt wird. Dies ist ein Ansatz, der in der Regel wenig Arbeit erfordert, außer der Einrichtung, damit diese Voraussetzungen erfüllt sind." + +#: ../../source/development/building-modules/installation-dependency-issues.rst:96 +msgid "Making a component available" +msgstr "Verfügbar machen einer Komponente " + +#: ../../source/development/building-modules/installation-dependency-issues.rst:98 +msgid "Adding a component to a module (or creating a new one) isn’t a one-step process because the component may have unfulfilled dependencies of its own (which can have other dependencies and so forth). Using a lather-rinse-repeat approach is time-consuming (you’d have to wait for a compose to happen before testing the changed module is possible) but the information to resolve these issues is available from the outset, assuming that the dependencies are resolvable within the set of Fedora packages. Instead of trying to resolve this manually (which can be time-consuming on its own), one can use tools like |fedmod|_ to generate the whole dependency chain programmatically." +msgstr "Das Hinzufügen einer Komponente zu einem Modul (oder das Erstellen eines neuen Moduls) ist kein einstufiger Prozess, da die Komponente möglicherweise von sich aus nicht erfüllte Abhängigkeiten besitzt (die weitere Abhängigkeiten haben können usw.). Mit einem Shampoo-Algorithmus zu arbeiten ist zeitaufwendig (Sie müssten warten, bis ein Compose stattfindet, bevor die Prüfung des geänderten Moduls möglich ist). Die Information zur Behebung dieser Probleme ist aber von Anfang an verfügbar. – Vorausgesetzt, dass die Abhängigkeiten aufgelöst werden können innerhalb des Sets von Fedora-Paketen. Anstatt zu versuchen, dies manuell zu lösen (das kann für sich selbst schon wieder zeitaufwendig sein), kann man Werkzeuge wie |fedmod|_ verwenden, um die gesamte Abhängigkeitskette programmatisch zu generieren." + +#: ../../source/development/building-modules/installation-dependency-issues.rst:111 +msgid "The first step is to use ``fedmod rpm2module `` which creates a modulemd file for a module containing the component and its dependencies. If one wanted to do just that (and nothing failed) besides getting the module reviewed and made available. Regardless of if the component should go into an existing module or shouldn't be filtered out any longer, the information in the generated modulemd file can be used to augment the module that should carry it (arguably more work but still less than resolving dependencies manually, one at a time)." +msgstr "Der erste Schritt besteht darin, ``fedmod rpm2module `` zu verwenden, das eine Modulemd-Datei für ein Modul erstellt, das die Komponente und seine Abhängigkeiten enthält. – Sofern lediglich dies gewollt ist (und nichts fehlschlägt), besteht noch die Aufgabe darin, das Modul einem Review unterziehen zu lassen und zur Verfügung zu stellen. Unabhängig davon, ob die Komponente in ein vorhandenes Modul eingehen soll oder nicht mehr weiter ausgefiltert wird, können die Informationen in der generierten Modulemd-Datei verwendet werden, um das Modul zu erweitern, das sie aufnehmen soll (mehr Arbeit, aber immer noch weniger als Abhängigkeiten einzeln hintereinander manuell aufzulösen)." + +#: ../../source/development/building-modules/installation-dependency-issues.rst:121 +msgid "Identifying components" +msgstr "Identifizieren von Komponenten" + +#: ../../source/development/building-modules/installation-dependency-issues.rst:123 +msgid "Consider this error while attempting to install a module ``389-ds``::" +msgstr "Betrachten Sie diesen Fehler beim Versuch ein Modul ``389-ds`` zu installieren::" + +#: ../../source/development/building-modules/installation-dependency-issues.rst:134 +msgid "In this case one needs to find out which package provides ``libtcmalloc.so.4()(64bit)``, e.g. by running ``dnf repoquery --whatprovides `` on an (as of now at least) not yet modular Fedora system and if necessary ``dnf info `` to find out the source package which can then be added to a module." +msgstr "In diesem Fall muss man herausfinden, welches Paket ``libtcmalloc.so.4()(64bit)`` bereitstellt. Zum Beispiel durch das Ausführen von ``dnf repoquery --whatprovides `` auf einem (zumindest derzeit) noch nicht modularen Fedora System und, wenn notwendig, ``dnf info ``, um das Quellpaket herauszufinden, das dann einem Modul hinzugefügt werden kann." + +#: ../../source/development/building-modules/installation-dependency-issues.rst:141 +msgid "Removing dependencies" +msgstr "Entfernen von Abhängigkeiten" + +#: ../../source/development/building-modules/installation-dependency-issues.rst:143 +msgid "Often, removing dependencies is done by disabling a component feature that is not needed in a module but would pull in a whole tree of other dependencies. It would be the right approach more often for components that aren’t part of a module’s API. This approach is trickier because you then need to introduce a macro to enable or disable the functionality (and the dependencies in question) in the spec file of the component, and you need to take care that its use in ``data/buildopts/rpms/macros`` doesn’t introduce side effects in the other components which are built as part of the module." +msgstr "Häufig werden Abhängigkeiten entfernt durch das Deaktivieren eines Komponenten-Features, das in einem Modul nicht benötigt wird, aber einen ganzen Baum anderer Abhängigkeiten hereinziehen würde. Es wäre oftmals der richtige Ansatz für Komponenten, die nicht Teil der API eines Moduls sind. Dieser Ansatz ist schwieriger, da Sie dann ein Makro einführen müssen, um die Funktionalität (und die fraglichen Abhängigkeiten) in der ``.spec``-Datei der Komponente zu aktivieren oder zu deaktivieren. Sie müssen dann ebenso darauf achten, dass dessen Verwendung in ``data/buildopts/rpms/macros`` nicht zu Nebeneffekten in den anderen Komponenten führt, die als Teil des Moduls erzeugt wurden." diff --git a/source/locale/de/LC_MESSAGES/development/building-modules/naming-policy.po b/source/locale/de/LC_MESSAGES/development/building-modules/naming-policy.po new file mode 100644 index 0000000..a0f1ae5 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/development/building-modules/naming-policy.po @@ -0,0 +1,281 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/development/building-modules/naming-policy.rst:3 +msgid "Naming Policy" +msgstr "Namensrichtlinie" + +#: ../../source/development/building-modules/naming-policy.rst:4 +msgid "" +"This document defines naming policy for modulemd metadata of final " +"(built) modules. This policy does **NOT** apply on sources such as " +"modulemd yaml in dist-git." +msgstr "Dieses Dokument definiert eine Namensrichtlinie für die Modulemd-Metadaten finaler (erzeugter) Module. Diese Richtlinie ist **nicht** gültig für Quellen wie YAML-Dateien für Modulemd in Dist-Git." + +#: ../../source/development/building-modules/naming-policy.rst:7 +msgid "" +"The goal is to provide unique identifiers for modules that are both human" +" readable and also suitable for machine processing." +msgstr "Ziel ist es, eindeutige Bezeichner für Module zur Verfügung zu stellen, die sowohl menschlich lesbar und ebenso für die maschinelle Verarbeitung geeignet sind." + +#: ../../source/development/building-modules/naming-policy.rst:12 +msgid "Fields" +msgstr "Felder" + +#: ../../source/development/building-modules/naming-policy.rst:14 +#: ../../source/development/building-modules/naming-policy.rst:83 +msgid "**N** - Name" +msgstr "**N** – Name" + +#: ../../source/development/building-modules/naming-policy.rst:15 +#: ../../source/development/building-modules/naming-policy.rst:85 +msgid "**S** - Stream" +msgstr "**S** – Stream" + +#: ../../source/development/building-modules/naming-policy.rst:16 +#: ../../source/development/building-modules/naming-policy.rst:87 +msgid "**V** - Version" +msgstr "**V** – Version" + +#: ../../source/development/building-modules/naming-policy.rst:17 +#: ../../source/development/building-modules/naming-policy.rst:89 +msgid "**C** - Context" +msgstr "**C** – Context" + +#: ../../source/development/building-modules/naming-policy.rst:18 +#: ../../source/development/building-modules/naming-policy.rst:91 +msgid "**A** - Arch" +msgstr "**A** – Arch" + +#: ../../source/development/building-modules/naming-policy.rst:19 +#: ../../source/development/building-modules/naming-policy.rst:94 +msgid "**P** - Profile" +msgstr "**P** – Profile" + +#: ../../source/development/building-modules/naming-policy.rst:23 +msgid "Separators" +msgstr "Separatoren" + +#: ../../source/development/building-modules/naming-policy.rst:24 +msgid "Fields are separated with ':' (colon): N:S:V:C:A." +msgstr "Felder werden getrennt mit '`:`' (colon): `N:S:V:C:A`." + +#: ../../source/development/building-modules/naming-policy.rst:25 +msgid "" +"If P is specified, it's separated from N:S:V:C:A with '/' (forward " +"slash): N:S:V:C:A/P." +msgstr "Wenn `P` spezifiziert ist, ist es getrennt von `N:S:V:C:A` mit '`/`' (Schrägstrich): `N:S:V:C:A/P`." + +#: ../../source/development/building-modules/naming-policy.rst:27 +msgid "Examples::" +msgstr "Beispiele::" + +#: ../../source/development/building-modules/naming-policy.rst:37 +msgid "Forms" +msgstr "Formen" + +#: ../../source/development/building-modules/naming-policy.rst:38 +msgid "" +"A form is a sequence of fields that fully or partially identifies a " +"module." +msgstr "Eine Form ist eine Sequenz von Feldern, die vollständig oder teilweise ein Modul identifizieren." + +#: ../../source/development/building-modules/naming-policy.rst:42 +msgid "Full Forms" +msgstr "Vollständige Formen" + +#: ../../source/development/building-modules/naming-policy.rst:44 +msgid "N:S:V:C:A" +msgstr "N:S:V:C:A" + +#: ../../source/development/building-modules/naming-policy.rst:45 +msgid "Unique identifier of a module." +msgstr "Eindeutiger Bezeichner eines Moduls." + +#: ../../source/development/building-modules/naming-policy.rst:48 +msgid "N:S:V:C:A/P" +msgstr "N:S:V:C:A/P" + +#: ../../source/development/building-modules/naming-policy.rst:47 +msgid "Unique identifier of a module profile." +msgstr "Eindeutiger Bezeichner eines Modulprofils." + +#: ../../source/development/building-modules/naming-policy.rst:51 +msgid "Partial Forms" +msgstr "Teilformen" + +#: ../../source/development/building-modules/naming-policy.rst:53 +msgid "Supported partial forms are: N [ : S [ :V [ :C ] ] ] [ :A ] [ /P ]" +msgstr "Unterstützten Teilformen sind: `N [ : S [ :V [ :C ] ] ] [ :A ] [ /P ]`" + +#: ../../source/development/building-modules/naming-policy.rst:55 +msgid "Namely:" +msgstr "Nämlich:" + +#: ../../source/development/building-modules/naming-policy.rst:57 +msgid "N" +msgstr "`N`" + +#: ../../source/development/building-modules/naming-policy.rst:58 +msgid "N::A" +msgstr "`N::A`" + +#: ../../source/development/building-modules/naming-policy.rst:59 +msgid "N:S" +msgstr "`N:S`" + +#: ../../source/development/building-modules/naming-policy.rst:60 +msgid "N:S::A" +msgstr "`N:S::A`" + +#: ../../source/development/building-modules/naming-policy.rst:61 +msgid "N:S:V" +msgstr "`N:S:V`" + +#: ../../source/development/building-modules/naming-policy.rst:62 +msgid "N:S:V::A" +msgstr "`N:S:V::A`" + +#: ../../source/development/building-modules/naming-policy.rst:63 +msgid "N:S:V:C" +msgstr "`N:S:V:C`" + +#: ../../source/development/building-modules/naming-policy.rst:64 +msgid "N:S:V:C:A (identical to N:S:V:C::A)" +msgstr "`N:S:V:C:A` (identisch mit `N:S:V:C::A`)" + +#: ../../source/development/building-modules/naming-policy.rst:65 +msgid "and all combinations with /P" +msgstr "und alle Kombinationen mit `/P`" + +#: ../../source/development/building-modules/naming-policy.rst:67 +msgid "Missing fields **SHOULD** be populated with recommended defaults:" +msgstr "Fehlende Felder **sollten** mit empfohlenen Standardeinstellungen besetzt werden:" + +#: ../../source/development/building-modules/naming-policy.rst:69 +msgid "Stream" +msgstr "Stream" + +#: ../../source/development/building-modules/naming-policy.rst:70 +msgid "" +"defaults to the enabled or system default stream for the module in this " +"particular order" +msgstr "Standardwert auf den jeweils Aktivierten oder der Systemstandard-Stream für das Modul – in dieser konkreten Reihenfolge." + +#: ../../source/development/building-modules/naming-policy.rst:71 +msgid "Version" +msgstr "Version" + +#: ../../source/development/building-modules/naming-policy.rst:72 +msgid "defaults to the latest available version in the module stream" +msgstr "Standardwert auf die aktuellste verfügbare Version im Modulstream." + +#: ../../source/development/building-modules/naming-policy.rst:73 +msgid "Context" +msgstr "Context" + +#: ../../source/development/building-modules/naming-policy.rst:74 +msgid "" +"defaults to a value matching with already installed modules or modules " +"involved in the transaction (not yet installed)" +msgstr "Standardwert auf einen Wert, der übereinstimmt mit bereits installierten Modulen oder Modulen, die an der Transaktion beteiligt sind (noch nicht installiert)." + +#: ../../source/development/building-modules/naming-policy.rst:75 +msgid "Arch" +msgstr "Arch" + +#: ../../source/development/building-modules/naming-policy.rst:76 +msgid "defaults to the system arch (e.g. DNF's $basearch)" +msgstr "Standardwert für die Systemarchitektur (z. B. DNFs ``$basearch``)." + +#: ../../source/development/building-modules/naming-policy.rst:79 +msgid "Profile" +msgstr "Profile" + +#: ../../source/development/building-modules/naming-policy.rst:78 +msgid "defaults to the system default or 'default' profile" +msgstr "Standardwert auf den Systemstandard oder das `default`-Profil." + +#: ../../source/development/building-modules/naming-policy.rst:82 +msgid "Allowed Characters" +msgstr "Zulässige Zeichen" + +#: ../../source/development/building-modules/naming-policy.rst:84 +#: ../../source/development/building-modules/naming-policy.rst:86 +#: ../../source/development/building-modules/naming-policy.rst:92 +#: ../../source/development/building-modules/naming-policy.rst:94 +msgid "a-z A-Z 0-9 . - _ +" +msgstr "a-z A-Z 0-9 . - _ +" + +#: ../../source/development/building-modules/naming-policy.rst:88 +msgid "0-9" +msgstr "0-9" + +#: ../../source/development/building-modules/naming-policy.rst:90 +msgid "0-9 a-f" +msgstr "0-9 a-f" + +#: ../../source/development/building-modules/naming-policy.rst:96 +msgid "" +"All fields **MUST** start and end with an alphanumeric character: a-z A-Z" +" 0-9" +msgstr "Alle Felder **müssen** mit einem alphanumerischen Zeichen beginnen und enden: a-z A-Z 0-9" + +#: ../../source/development/building-modules/naming-policy.rst:101 +msgid "Forbidden Characters" +msgstr "Verbotene Zeichen" + +#: ../../source/development/building-modules/naming-policy.rst:102 +msgid "This paragraph serves as a design decision for future changes." +msgstr "Dieser Absatz dient als eine Entwurfsentscheidung für zukünftige Änderungen." + +#: ../../source/development/building-modules/naming-policy.rst:104 +msgid "Following characters **MUST NOT** be part of any field:" +msgstr "Folgende Zeichen **dürfen nicht** Teil irgendeines Felds sein:" + +#: ../../source/development/building-modules/naming-policy.rst:106 +msgid "':' (colon) - separator" +msgstr "'`:`' (Doppelpunkt) – Separator" + +#: ../../source/development/building-modules/naming-policy.rst:107 +msgid "'/' (forward slash) - profile separator" +msgstr "'`/`' (Schrägstrich) – Profil-Separator" + +#: ../../source/development/building-modules/naming-policy.rst:108 +msgid "'\\\\\\\\' (backslash) - comon control character" +msgstr "'`\\`' (Backslash) – reguläres Steuerzeichen" + +#: ../../source/development/building-modules/naming-policy.rst:109 +msgid "'*' (asterisk) - common wildcard" +msgstr "'`*`' (Sternchen) – reguläre Wildcard" + +#: ../../source/development/building-modules/naming-policy.rst:110 +msgid "'?' (question mark) - common wildcard" +msgstr "'`?`' (Fragezeichen) – reguläre Wildcard" + +#: ../../source/development/building-modules/naming-policy.rst:111 +msgid "'@' (at) - grpspec in YUM and DNF" +msgstr "'`@`' (at) – grpspec in YUM und DNF" + +#: ../../source/development/building-modules/naming-policy.rst:112 +msgid "' ' (space) - common separator" +msgstr "` ` (Leerzeichen) – regulärer Separator" + diff --git a/source/locale/de/LC_MESSAGES/development/building-modules/testing.po b/source/locale/de/LC_MESSAGES/development/building-modules/testing.po new file mode 100644 index 0000000..bd281b6 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/development/building-modules/testing.po @@ -0,0 +1,261 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-22 17:19+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/development/building-modules/testing.rst:2 +msgid "Testing modular content in Fedora" +msgstr "Testen modularen Contents in Fedora" + +#: ../../source/development/building-modules/testing.rst:5 +msgid "Interactive Testing" +msgstr "Interaktive Testverfahren" + +#: ../../source/development/building-modules/testing.rst:7 +#, fuzzy +msgid "" +"If the automated tests are failing, or if a new module is being built for" +" the first time, it is useful to be able to check modules interactively " +"before they make their way into an official compose. (For details on the " +"regular testing of modules and their contents, see the :ref:`automated-" +"testing` section below)" +msgstr "Wenn die automatisierten Tests fehlschlagen oder wenn ein neues Modul zum ersten Mal erzeugt wird, ist es sinnvoll in der Lage zu sein, Module interaktiv zu prüfen, bevor sie ihren Weg in einen offiziellen Compose machen. (Einzelheiten zum regelmäßigen Testen von Modulen und deren Inhalten finden Sie im Abschnitt :ref:`automated-testing` weiter unten)" + +#: ../../source/development/building-modules/testing.rst:12 +msgid "" +"The interactive testing guide below assumes that ``fedpkg module-build`` " +"is succeeding - if that isn't the case, then the module and package build" +" logs should provide details as to what is going wrong." +msgstr "In der nachfolgenden interaktiven Testanleitung wird vorausgesetzt, dass ``fedpkg module-build`` erfolgreich ist – wenn das nicht der Fall ist, sollten die Modul- und Paket-Build-Logs Details zur Verfügung stellen, was schief gelaufen ist." + +#: ../../source/development/building-modules/testing.rst:18 +msgid "Resolving dependency issues" +msgstr "Auflösen von Abhängigkeitsproblemen" + +#: ../../source/development/building-modules/testing.rst:20 +msgid "" +"The most common problems that are encountered despite a successful build " +"and passing integration tests are dependency resolution issues when " +"attempting to install a module. The :ref:`resolving-dependency-issues` " +"section provides more guidance on dealing with such situations." +msgstr "Die häufigsten Probleme, die trotz erfolgreicher Erstellung und dem Bestehen von Integrationstests auftreten, sind Probleme bei der Auflösung von Abhängigkeiten, wenn versucht wird ein Modul zu installieren. Der Abschnitt :ref:`resolving-dependency-issues` bietet weitere Anleitung zum Umgang mit solchen Situationen." + +#: ../../source/development/building-modules/testing.rst:27 +msgid "Boltron testing images" +msgstr "Test-Images von Boltron" + +#: ../../source/development/building-modules/testing.rst:29 +msgid "" +"The original Fedora 26 Boltron prototype lives on as a set of `test " +"container images `__, " +"which build atop the Fedora modular composes, but include some additional" +" utililties to help out with testing modules prior to their release in " +"Fedora." +msgstr "Der originale Fedora 26 Boltron Prototyp lebt weiter als ein Set von `Test-Container-Images `__, die auf Basis der modularen Fedora Composes erzeugt werden, aber einige zusätzliche Utilitys enthalten, die das Testen von Modulen unterstützen vor ihrem Release in Fedora." + +#: ../../source/development/building-modules/testing.rst:34 +msgid "" +"Two variants of the image are provided, a ``boltron-27`` image with " +"module definitions from the Fedora 27 Modular Server release, and a " +"``boltron-bikeshed`` with the latest module definitions from the module " +"build service that have passed their self-tests in Taskotron::" +msgstr "Zwei Varianten des Images werden zur Verfügung gestellt: Ein ``boltron-27``-Image mit Moduldefinitionen aus dem Fedora 27 Modular Server Release und ein ``boltron-bikeshed`` mit den neuesten Moduldefinitionen aus dem Modul-Build-Service, die ihre Selbsttests in Taskotron bestanden haben::" + +#: ../../source/development/building-modules/testing.rst:42 +msgid "" +"See the ``README`` in the image source repository for more information on" +" the available utilities." +msgstr "Weitere Informationen zu den verfügbaren Dienstprogrammen finden Sie in der ``README`` im Quell-Repository der Images." + +#: ../../source/development/building-modules/testing.rst:47 +msgid "Enabling access to unreleased modules" +msgstr "Aktivieren des Zugriffs auf unveröffentlichte Module" + +#: ../../source/development/building-modules/testing.rst:49 +#, fuzzy +msgid "" +"Module releases may take a day or more to become available in the default" +" image, so the Boltron image provides a helper script to download built " +"modules directly from the Module Build Service and incorporate them into " +"the currently running image. For example::" +msgstr "Modul-Releases können einen Tag oder länger benötigen, um im Standard-Image zur Verfügung zu stehen. Aus diesem Grund stellt das Boltron-Image ein Hilfs-Skript bereit, um erstellte Module direkt aus dem Modul-Build-Service herunterzuladen und in das aktuell ausgeführte Image zu integrieren. Zum Beispiel::" + +#: ../../source/development/building-modules/testing.rst:56 +msgid "" +"This will download the binary artifacts for that particular build of the " +"PostreSQL 9.6 stream, set up a local repository for them (including the " +"module metadata), enable that repository, and then install the module " +"with its default profile." +msgstr "Dies wird die binären Artefakte für diesen speziellen Build des PostreSQL 9.6 Streams herunterladen, ein lokales Repository für diese einrichten (einschließlich der Modul-Metadaten), das Repository aktivieren und anschließend das Modul mit seinem Standardprofil installieren." + +#: ../../source/development/building-modules/testing.rst:61 +#, fuzzy +msgid "" +"A non-default install profile can be requested by appending the profile " +"name to the build identifer, separated by a ``/``::" +msgstr "Ein nicht-Standard-Installationsprofil kann angefordert werden, indem der Profilname an den Build-Bezeichner angehängt wird, getrennt durch ein ``/``::" + +#: ../../source/development/building-modules/testing.rst:68 +msgid "Finding module build identifiers" +msgstr "Finden von Modul-Build-Bezeichnern" + +#: ../../source/development/building-modules/testing.rst:70 +msgid "" +"The list of currently build modules and their identifiers is available at" +" http://modularity.fedorainfracloud.org/modularity/mbs/." +msgstr "Die Liste der zurzeit erzeugten Module und ihrer Bezeichner ist verfügbar unter: http://modularity.fedorainfracloud.org/modularity/mbs/" + +#~ msgid "" +#~ msgstr "" + +#~ msgid "Automated Testing" +#~ msgstr "Automatisierte Tests" + +#~ msgid "" +#~ "As described in the `Continuous " +#~ "Integration `__ page" +#~ " on the Fedora wiki, Fedora is " +#~ "currently working to improve the level" +#~ " of automated test coverage for the" +#~ " entire distribution." +#~ msgstr "" +#~ "Wie in der `Continuous Integration " +#~ "`__ Seite im " +#~ "Fedora Wiki beschrieben, arbeitet Fedora " +#~ "derzeit an der Verbesserung des Levels" +#~ " der automatisierten Testabdeckung für die" +#~ " gesamte Distribution." + +#~ msgid "Modular compose tests" +#~ msgstr "Modulare Compose-Tests" + +#~ msgid "" +#~ "A base set of automated tests " +#~ "check that the core set of modules" +#~ " defined in Fedora's system profile " +#~ "can all be installed and updated." +#~ msgstr "" +#~ "Ein Basis-Set von automatisierten Tests" +#~ " überprüft, ob das Set von " +#~ "Kernmodulen, das in Fedoras Systemprofil " +#~ "definiert wurde, vollständig installiert und" +#~ " aktualisiert werden kann." + +#~ msgid "" +#~ "These tests are written as Ansible " +#~ "playbooks, and can be found in the" +#~ " `compose-tests repository `__." +#~ msgstr "" +#~ "Diese Tests werden als Ansible Playbooks" +#~ " verfasst und finden sich im " +#~ "`Repository für Compose-Tests " +#~ "`__." + +#~ msgid "These tests are executed in the CentOS CI infrastructure:" +#~ msgstr "Diese Tests werden in der Infrastruktur von CentOS CI ausgeführt:" + +#~ msgid "" +#~ "`Last successful build `__" +#~ msgstr "" +#~ "`Letzter erfolgreicher Build " +#~ "`__" + +#~ msgid "" +#~ "`Latest build `__" +#~ msgstr "" +#~ "`Neuester Build `__" + +#~ msgid "Per-module tests in dist-git" +#~ msgstr "Tests pro Modul in Dist-Git" + +#~ msgid "" +#~ "Modules may also define their own " +#~ "individual automated tests, in the " +#~ "``tests/`` subdirectory of their respective" +#~ " `dist-git module repositories " +#~ "`__" +#~ msgstr "" +#~ "Module können auch ihre eigenen " +#~ "individuellen automatisierten Tests definieren, " +#~ "im ``tests/``-Unterverzeichnis ihrer jeweiligen " +#~ "`Dist-Git Modul-Repositorys " +#~ "`__." + +#~ msgid "" +#~ "The `Meta Test Family `__ project is used" +#~ " to define test cases for whole " +#~ "modules and their resulting RPMs and " +#~ "container images." +#~ msgstr "" +#~ "Das `Meta Test Family `__-Projekt wird verwendet," +#~ " um Testfälle für ganze Module und" +#~ " ihre resultierenden RPMs und Container-" +#~ "Images zu definieren." + +#~ msgid "" +#~ "When a module is built in Fedora's" +#~ " infrastructure and MTF tests are " +#~ "available in its repository, they will" +#~ " be run afterwards by `Taskotron " +#~ "`__." +#~ msgstr "" +#~ "Wenn ein Modul in der Infrastruktur " +#~ "von Fedora erzeugt wurde und MTF-" +#~ "Tests in seinem Repository verfügbar " +#~ "sind, werden diese anschließend von " +#~ "`Taskotron `__ " +#~ "ausgeführt." + +#~ msgid "Per-package tests" +#~ msgstr "Tests pro Paket" + +#~ msgid "" +#~ "Independently of the modular build " +#~ "process, individual packages may also " +#~ "define their own automated tests, both" +#~ " as part of the ``%check`` section" +#~ " in their RPM spec file, as " +#~ "well as in the ``tests/`` subdirectory" +#~ " of their respective `dist-git RPM" +#~ " repositories " +#~ "`__" +#~ msgstr "" +#~ "Unabhängig vom modularen Buildprozess können" +#~ " einzelne Pakete auch ihre eigenen " +#~ "automatisierten Tests definieren, sowohl als" +#~ " Teil des ``%check``-Abschnitts in der " +#~ "``.spec``-Datei ihres RMPs, wie auch im" +#~ " ``tests/``-Unterverzeichnis ihrer jeweiligen " +#~ "`Dist-Git RPM-Repositorys " +#~ "`__." + +#~ msgid "# /LOCAL.sh postgresql:9.6:20171018083530" +#~ msgstr "# /LOCAL.sh postgresql:9.6:20171018083530" + +#~ msgid "# /LOCAL.sh postgresql:9.6:20171018083530/client" +#~ msgstr "# /LOCAL.sh postgresql:9.6:20171018083530/client" + diff --git a/source/locale/de/LC_MESSAGES/development/integration/coding-style-python.po b/source/locale/de/LC_MESSAGES/development/integration/coding-style-python.po new file mode 100644 index 0000000..bc529d6 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/development/integration/coding-style-python.po @@ -0,0 +1,681 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/development/integration/coding-style-python.rst:2 +msgid "Coding Style (Python)" +msgstr "Coding Style (Python)" + +#: ../../source/development/integration/coding-style-python.rst:4 +msgid "Read this if you plan to contribute code written in the Python language." +msgstr "Read this if you plan to contribute code written in the Python language." + +#: ../../source/development/integration/coding-style-python.rst:7 +msgid "Upstream guidelines" +msgstr "Upstream guidelines" + +#: ../../source/development/integration/coding-style-python.rst:9 +msgid "" +"Fortunately, with PEP 8 there's an extensive official `Style Guide for " +"Python Code `__. All new " +"Python code you submit should conform to it, unless you have good reasons" +" to deviate from it, `for instance readability " +"`__." +msgstr "Fortunately, with PEP 8 there's an extensive official `Style Guide for Python Code `__. All new Python code you submit should conform to it, unless you have good reasons to deviate from it, `for instance readability `__." + +#: ../../source/development/integration/coding-style-python.rst:15 +msgid "" +"Keep PEP 20, the `Zen of Python " +"`__, under your pillow." +msgstr "Keep PEP 20, the `Zen of Python `__, under your pillow." + +#: ../../source/development/integration/coding-style-python.rst:20 +msgid "Keep It Simple" +msgstr "Keep It Simple" + +#: ../../source/development/integration/coding-style-python.rst:22 +msgid "" +"The code you write now probably needs to be touched by someone else down " +"the road, and that someone else might be less experienced than you, or " +"have a terrible headache and be under pressure of time. So while a " +"particular construct may be a clever way of doing something, a simple way" +" of doing the same thing can be and often is preferrable. If (when) " +"complexity can't be avoided, try to isolate it: put a difficult operation" +" into its own function, method or class, add comments. If complexity can " +"be hidden from upper layers of the code, do so." +msgstr "The code you write now probably needs to be touched by someone else down the road, and that someone else might be less experienced than you, or have a terrible headache and be under pressure of time. So while a particular construct may be a clever way of doing something, a simple way of doing the same thing can be and often is preferrable. If (when) complexity can't be avoided, try to isolate it: put a difficult operation into its own function, method or class, add comments. If complexity can be hidden from upper layers of the code, do so." + +#: ../../source/development/integration/coding-style-python.rst:32 +msgid "Comments and Docstrings" +msgstr "Comments and Docstrings" + +#: ../../source/development/integration/coding-style-python.rst:34 +msgid "" +"Be generous when it comes to commenting your code, it's better to have a " +"superfluous comment than if one were necessary but is missing. However, " +"if there is a comment it should be correct and agree with the code, " +"otherwise people have to guess if the comment or the code needs to be " +"straightened out." +msgstr "Be generous when it comes to commenting your code, it's better to have a superfluous comment than if one were necessary but is missing. However, if there is a comment it should be correct and agree with the code, otherwise people have to guess if the comment or the code needs to be straightened out." + +#: ../../source/development/integration/coding-style-python.rst:40 +msgid "" +"Adding `docstrings `__ to " +"modules, classes, methods and functions is encouraged. If you use the " +"`Sphinx format `__ to describe parameters, return values, etc., even " +"better!" +msgstr "Adding `docstrings `__ to modules, classes, methods and functions is encouraged. If you use the `Sphinx format `__ to describe parameters, return values, etc., even better!" + +#: ../../source/development/integration/coding-style-python.rst:47 +msgid "Python 2 and 3" +msgstr "Python 2 and 3" + +#: ../../source/development/integration/coding-style-python.rst:49 +msgid "Python comes in two major versions nowadays:" +msgstr "Python comes in two major versions nowadays:" + +#: ../../source/development/integration/coding-style-python.rst:51 +msgid "" +"The legacy version 2, of which the `first release 2.0 came out in October" +" 2000 `__. The Python " +"project `will maintain its final minor release 2.7 until 2020 " +"`__." +msgstr "The legacy version 2, of which the `first release 2.0 came out in October 2000 `__. The Python project `will maintain its final minor release 2.7 until 2020 `__." + +#: ../../source/development/integration/coding-style-python.rst:56 +msgid "" +"The current version 3, its `first release 3.0 was published in December " +"2008 `__. At the time of " +"writing, the current minor release is version 3.5, to be superseded by " +"3.6 around the end of 2016." +msgstr "The current version 3, its `first release 3.0 was published in December 2008 `__. At the time of writing, the current minor release is version 3.5, to be superseded by 3.6 around the end of 2016." + +#: ../../source/development/integration/coding-style-python.rst:61 +msgid "" +"Version 3 is not backwards compatible to version 2. While we mainly " +"target \"the future\", there are some components we have to work with " +"that haven't yet been ported over the Python 3, most notably `koji " +"`__. Additionally, we may also want to " +"support the \"user tools\" we create on legacy systems, so we can't write" +" code that uses all the latest features. Fortunately, many of the " +"original Python 3 features have been back-ported to Python 2.7, so we can" +" and should write code that is very close to writing idiomatic Python 3 " +"but can still be run on version 2.7. Targeting older minor releases " +"(Python 2.6 and earlier) is much more of a balancing act, so we won't aim" +" for it." +msgstr "Version 3 is not backwards compatible to version 2. While we mainly target \"the future\", there are some components we have to work with that haven't yet been ported over the Python 3, most notably `koji `__. Additionally, we may also want to support the \"user tools\" we create on legacy systems, so we can't write code that uses all the latest features. Fortunately, many of the original Python 3 features have been back-ported to Python 2.7, so we can and should write code that is very close to writing idiomatic Python 3 but can still be run on version 2.7. Targeting older minor releases (Python 2.6 and earlier) is much more of a balancing act, so we won't aim for it." + +#: ../../source/development/integration/coding-style-python.rst:73 +msgid "" +"The following sections cover areas that require some attention. The " +"Python project itself has a great `Porting Python 2 Code to Python 3 " +"`__ document which goes " +"into much detail about the differences and is worth a read, even though " +"it mainly addresses existing Python 2 code bases." +msgstr "The following sections cover areas that require some attention. The Python project itself has a great `Porting Python 2 Code to Python 3 `__ document which goes into much detail about the differences and is worth a read, even though it mainly addresses existing Python 2 code bases." + +#: ../../source/development/integration/coding-style-python.rst:80 +msgid "Absolute and relative imports" +msgstr "Absolute and relative imports" + +#: ../../source/development/integration/coding-style-python.rst:82 +msgid "" +"In Python 2, importing modules can be ambiguous when a module of that " +"name exists in the same package and elsewhere in the module search path " +"``sys.path``. To work around this ambiguity, programmers often resorted " +"to adding paths private to the project to the beginning of ``sys.path`` " +"to force loading modules from a project-internal location (which adds " +"unwanted noise and can make e.g. testing code that isn't installed " +"difficult). Python 3 introduces new syntax for import statements which " +"makes both cases distinct, this is available since version 2.5 from the " +"``__future__`` module:" +msgstr "In Python 2, importing modules can be ambiguous when a module of that name exists in the same package and elsewhere in the module search path ``sys.path``. To work around this ambiguity, programmers often resorted to adding paths private to the project to the beginning of ``sys.path`` to force loading modules from a project-internal location (which adds unwanted noise and can make e.g. testing code that isn't installed difficult). Python 3 introduces new syntax for import statements which makes both cases distinct, this is available since version 2.5 from the ``__future__`` module:" + +#: ../../source/development/integration/coding-style-python.rst:106 +msgid "Print function" +msgstr "Print function" + +#: ../../source/development/integration/coding-style-python.rst:108 +msgid "" +"Python 3 did away with ``print`` as a statement and introduced it as a " +"function. In order to use it the same way in Python 2.7, add the " +"following to the top of source code files where you use ``print``:" +msgstr "Python 3 did away with ``print`` as a statement and introduced it as a function. In order to use it the same way in Python 2.7, add the following to the top of source code files where you use ``print``:" + +#: ../../source/development/integration/coding-style-python.rst:117 +msgid "Numbers" +msgstr "Numbers" + +#: ../../source/development/integration/coding-style-python.rst:119 +msgid "" +"Python 2 has two integer types, \\`int\\` which is whatever integer-type " +"is native to the system (which has certain maximal and minimal values and" +" can overflow) and \\`long\\` which can store arbitrary integer numbers. " +"Python 3 only the latter type, but it's called ``int``." +msgstr "Python 2 has two integer types, \\`int\\` which is whatever integer-type is native to the system (which has certain maximal and minimal values and can overflow) and \\`long\\` which can store arbitrary integer numbers. Python 3 only the latter type, but it's called ``int``." + +#: ../../source/development/integration/coding-style-python.rst:124 +msgid "" +"Dividing integer numbers using ``/`` truncates the result to an integer " +"in Python 2 by default, but yields a floating point number in Python 3. " +"In order for code to do the same thing on either version, include the " +"following line at the top of your source files where you divide numbers, " +"and use ``/`` for normal divisions and ``//`` for divisions that should " +"truncate the result:" +msgstr "Dividing integer numbers using ``/`` truncates the result to an integer in Python 2 by default, but yields a floating point number in Python 3. In order for code to do the same thing on either version, include the following line at the top of your source files where you divide numbers, and use ``/`` for normal divisions and ``//`` for divisions that should truncate the result:" + +#: ../../source/development/integration/coding-style-python.rst:136 +msgid "Strings" +msgstr "Strings" + +#: ../../source/development/integration/coding-style-python.rst:138 +msgid "" +"Some consider this the main difference between Python 2 and 3: Both " +"versions have a type for strings of bytes and strings of Unicode " +"character points. They are called ``str`` and ``unicode`` in version 2 " +"and ``bytes`` and ``str`` in version 3, respectively." +msgstr "Some consider this the main difference between Python 2 and 3: Both versions have a type for strings of bytes and strings of Unicode character points. They are called ``str`` and ``unicode`` in version 2 and ``bytes`` and ``str`` in version 3, respectively." + +#: ../../source/development/integration/coding-style-python.rst:144 +msgid "String Literals" +msgstr "String Literals" + +#: ../../source/development/integration/coding-style-python.rst:146 +msgid "" +"Python 2 and 3 use different ways of marking literals of the different " +"types by default. Byte strings can have no prefix or ``b`` in Python 2.7," +" but must be prefixed in Python 3, and text strings must have the ``u`` " +"prefix in Python 2 which can be and usually is omitted in Python 3:" +msgstr "Python 2 and 3 use different ways of marking literals of the different types by default. Byte strings can have no prefix or ``b`` in Python 2.7, but must be prefixed in Python 3, and text strings must have the ``u`` prefix in Python 2 which can be and usually is omitted in Python 3:" + +#: ../../source/development/integration/coding-style-python.rst:163 +msgid "" +"In order to ease writing code that is compatible between the versions, " +"you can switch Python 2 to treat unprefixed string literals as " +"``unicode``, the text string type, by adding this snippet to the top of " +"the relevant source code files:" +msgstr "In order to ease writing code that is compatible between the versions, you can switch Python 2 to treat unprefixed string literals as ``unicode``, the text string type, by adding this snippet to the top of the relevant source code files:" + +#: ../../source/development/integration/coding-style-python.rst:173 +msgid "Explicit Encoding and Decoding" +msgstr "Explicit Encoding and Decoding" + +#: ../../source/development/integration/coding-style-python.rst:175 +msgid "" +"In Python 2, the byte and text string types are exchangeable in many " +"places, taking the user's or system default locale into account (and " +"sometimes failing, when the locale didn't match up with encoded data). " +"Apart from the change in type names and how literals look like, Python 3 " +"requires you to explicitly encode ``str`` and decode ``bytes`` objects if" +" you need them cast into the respective other string type. It is good " +"practice to exclusively use text strings for strings that represent text " +"in a program and decode byte strings as early and encode text strings as " +"late as possible at interfaces that produce or consume encoded data." +msgstr "In Python 2, the byte and text string types are exchangeable in many places, taking the user's or system default locale into account (and sometimes failing, when the locale didn't match up with encoded data). Apart from the change in type names and how literals look like, Python 3 requires you to explicitly encode ``str`` and decode ``bytes`` objects if you need them cast into the respective other string type. It is good practice to exclusively use text strings for strings that represent text in a program and decode byte strings as early and encode text strings as late as possible at interfaces that produce or consume encoded data." + +#: ../../source/development/integration/coding-style-python.rst:206 +msgid "String formatting" +msgstr "String formatting" + +#: ../../source/development/integration/coding-style-python.rst:208 +msgid "" +"With version 3.6 around the corner, there are four ways to format strings" +" in Python now:" +msgstr "With version 3.6 around the corner, there are four ways to format strings in Python now:" + +#: ../../source/development/integration/coding-style-python.rst:211 +msgid "using the ``%`` operator" +msgstr "using the ``%`` operator" + +#: ../../source/development/integration/coding-style-python.rst:212 +msgid "" +"using ``string.Template`` of `PEP 292 " +"`__" +msgstr "using ``string.Template`` of `PEP 292 `__" + +#: ../../source/development/integration/coding-style-python.rst:214 +msgid "with the ``str.format()`` method" +msgstr "with the ``str.format()`` method" + +#: ../../source/development/integration/coding-style-python.rst:215 +msgid "" +"using `PEP 498 literal string interpolation " +"`__" +msgstr "using `PEP 498 literal string interpolation `__" + +#: ../../source/development/integration/coding-style-python.rst:218 +msgid "" +"The last method isn't available yet in a stable Python release and will " +"never be in Python 2, so it's not suitable for our purposes. The other " +"three variants work in all Python versions we're interested in, " +"formatting with ``string.Template`` is very rarely done however. The " +"remaining two ways, commonly called old-style (``%`` operator) and new-" +"style (``str.format()``), are both in wide-spread use, `here's a site " +"showcasing the differences between them `__. New-" +"style formatting is more powerful and often easier to read, but on the " +"other hand can be a little more to type. From a technical point of view, " +"this is a case of \"use what works for you\", but for consistency sake " +"the new-style ``str.format()`` way is preferrable if you're comfortable " +"with using it. If not, others can convert old-style to new-style " +"formatting for you during review or when happening across it. At any " +"rate, consistently use one way or the other in what you submit." +msgstr "The last method isn't available yet in a stable Python release and will never be in Python 2, so it's not suitable for our purposes. The other three variants work in all Python versions we're interested in, formatting with ``string.Template`` is very rarely done however. The remaining two ways, commonly called old-style (``%`` operator) and new-style (``str.format()``), are both in wide-spread use, `here's a site showcasing the differences between them `__. New-style formatting is more powerful and often easier to read, but on the other hand can be a little more to type. From a technical point of view, this is a case of \"use what works for you\", but for consistency sake the new-style ``str.format()`` way is preferrable if you're comfortable with using it. If not, others can convert old-style to new-style formatting for you during review or when happening across it. At any rate, consistently use one way or the other in what you submit." + +#: ../../source/development/integration/coding-style-python.rst:235 +msgid "Old- and New-style Classes" +msgstr "Old- and New-style Classes" + +#: ../../source/development/integration/coding-style-python.rst:237 +msgid "" +"Python 2 and earlier knows two types of classes, old-style which have no " +"base class, and new-style which have ``object`` as the base class. " +"Because their behavior is slightly different in some places, and some " +"things can't be done with old-style classes, we want to stick to new-" +"style classes wherever possible." +msgstr "Python 2 and earlier knows two types of classes, old-style which have no base class, and new-style which have ``object`` as the base class. Because their behavior is slightly different in some places, and some things can't be done with old-style classes, we want to stick to new-style classes wherever possible." + +#: ../../source/development/integration/coding-style-python.rst:243 +msgid "" +"The syntactical difference is that new-style classes have to explicitly " +"be derived from ``object`` or another new-style class." +msgstr "The syntactical difference is that new-style classes have to explicitly be derived from ``object`` or another new-style class." + +#: ../../source/development/integration/coding-style-python.rst:262 +msgid "" +"Python 3 only knows new-style classes and the requirement to explicitly " +"derive from ``object`` was dropped. In projects that will only ever run " +"on Python 3, it's acceptable not to explicitly derive classes without " +"parents from ``object``, but if in doubt, do it just the same." +msgstr "Python 3 only knows new-style classes and the requirement to explicitly derive from ``object`` was dropped. In projects that will only ever run on Python 3, it's acceptable not to explicitly derive classes without parents from ``object``, but if in doubt, do it just the same." + +#: ../../source/development/integration/coding-style-python.rst:268 +msgid "Idiomatic code" +msgstr "Idiomatic code" + +#: ../../source/development/integration/coding-style-python.rst:270 +msgid "" +"In Python, it's easy to inadvertently emulate idiomatic styles of other " +"languages like C/C++ or Java. In cases where there are constructs " +"\"native\" to the language, it's preferrable to use them." +msgstr "In Python, it's easy to inadvertently emulate idiomatic styles of other languages like C/C++ or Java. In cases where there are constructs \"native\" to the language, it's preferrable to use them." + +#: ../../source/development/integration/coding-style-python.rst:275 +msgid "Literals and Comprehensions" +msgstr "Literals and Comprehensions" + +#: ../../source/development/integration/coding-style-python.rst:277 +msgid "" +"Python has special syntax for literals for a couple of built-in compound " +"data types: lists, tuples, dictionaries, strings, sets. It's customary to" +" use that syntax instead of the class constructor to create objects for " +"these data types unless you have good reason not to. Apart from how it " +"looks, the literal syntax is performing a little bit better (because it " +"doesn't have to look up the class name in the current scope). NB: Set " +"literals are peculiar in that you can't create empty ones­—they would " +"look the same as empty dicts." +msgstr "Python has special syntax for literals for a couple of built-in compound data types: lists, tuples, dictionaries, strings, sets. It's customary to use that syntax instead of the class constructor to create objects for these data types unless you have good reason not to. Apart from how it looks, the literal syntax is performing a little bit better (because it doesn't have to look up the class name in the current scope). NB: Set literals are peculiar in that you can't create empty ones­—they would look the same as empty dicts." + +#: ../../source/development/integration/coding-style-python.rst:287 +#: ../../source/development/integration/coding-style-python.rst:334 +msgid "Data Type" +msgstr "Data Type" + +#: ../../source/development/integration/coding-style-python.rst:287 +msgid "Good" +msgstr "Good" + +#: ../../source/development/integration/coding-style-python.rst:287 +msgid "Bad" +msgstr "Bad" + +#: ../../source/development/integration/coding-style-python.rst:289 +msgid "``str``" +msgstr "``str``" + +#: ../../source/development/integration/coding-style-python.rst +msgid "``a_str = \"abc\"``" +msgstr "``a_str = \"abc\"``" + +#: ../../source/development/integration/coding-style-python.rst +msgid "``empty_str = \"\"``" +msgstr "``empty_str = \"\"``" + +#: ../../source/development/integration/coding-style-python.rst:289 +msgid "``empty_str = str()``" +msgstr "``empty_str = str()``" + +#: ../../source/development/integration/coding-style-python.rst:292 +#: ../../source/development/integration/coding-style-python.rst:336 +msgid "``list``" +msgstr "``list``" + +#: ../../source/development/integration/coding-style-python.rst +msgid "``a_list = [1, 2]``" +msgstr "``a_list = [1, 2]``" + +#: ../../source/development/integration/coding-style-python.rst +msgid "``empty_str = []``" +msgstr "``empty_str = []``" + +#: ../../source/development/integration/coding-style-python.rst +msgid "``a_list = list((1, 2))``" +msgstr "``a_list = list((1, 2))``" + +#: ../../source/development/integration/coding-style-python.rst +msgid "``empty_list = list()``" +msgstr "``empty_list = list()``" + +#: ../../source/development/integration/coding-style-python.rst:295 +msgid "``tuple``" +msgstr "``tuple``" + +#: ../../source/development/integration/coding-style-python.rst +msgid "``a_tuple = ('a', 'b', 3)``" +msgstr "``a_tuple = ('a', 'b', 3)``" + +#: ../../source/development/integration/coding-style-python.rst +msgid "``empty_tuple = ()``" +msgstr "``empty_tuple = ()``" + +#: ../../source/development/integration/coding-style-python.rst +msgid "``a_tuple = tuple(['a', 'b', 3])``" +msgstr "``a_tuple = tuple(['a', 'b', 3])``" + +#: ../../source/development/integration/coding-style-python.rst +msgid "``empty_tuple = tuple()``" +msgstr "``empty_tuple = tuple()``" + +#: ../../source/development/integration/coding-style-python.rst:298 +#: ../../source/development/integration/coding-style-python.rst:338 +msgid "``dict``" +msgstr "``dict``" + +#: ../../source/development/integration/coding-style-python.rst +msgid "``a_dict = {'a': 1}``" +msgstr "``a_dict = {'a': 1}``" + +#: ../../source/development/integration/coding-style-python.rst +msgid "``empty_dict = {}``" +msgstr "``empty_dict = {}``" + +#: ../../source/development/integration/coding-style-python.rst +msgid "``a_dict = dict(('a', 1))``" +msgstr "``a_dict = dict(('a', 1))``" + +#: ../../source/development/integration/coding-style-python.rst +msgid "``empty_dict = dict()``" +msgstr "``empty_dict = dict()``" + +#: ../../source/development/integration/coding-style-python.rst:301 +#: ../../source/development/integration/coding-style-python.rst:342 +msgid "``set``" +msgstr "``set``" + +#: ../../source/development/integration/coding-style-python.rst +msgid "``a_set = {\"banana\", \"apple\"}``" +msgstr "``a_set = {\"banana\", \"apple\"}``" + +#: ../../source/development/integration/coding-style-python.rst +msgid "**``empty_set = set()``**" +msgstr "**``empty_set = set()``**" + +#: ../../source/development/integration/coding-style-python.rst:301 +msgid "``a_set = set([\"banana\", \"apple\"])``" +msgstr "``a_set = set([\"banana\", \"apple\"])``" + +#: ../../source/development/integration/coding-style-python.rst:305 +msgid "Table: Creating compound objects" +msgstr "Table: Creating compound objects" + +#: ../../source/development/integration/coding-style-python.rst:307 +msgid "" +"Often the initial contents of a compound object are only known when it's " +"created at runtime. For simple cases like mere type conversions, calling " +"the class constructors are the way to go:" +msgstr "Often the initial contents of a compound object are only known when it's created at runtime. For simple cases like mere type conversions, calling the class constructors are the way to go:" + +#: ../../source/development/integration/coding-style-python.rst:311 +msgid "Converting a tuple to a list or vice versa:" +msgstr "Converting a tuple to a list or vice versa:" + +#: ../../source/development/integration/coding-style-python.rst:313 +msgid "``   a_tuple = (1, 2, 3)``" +msgstr "``   a_tuple = (1, 2, 3)``" + +#: ../../source/development/integration/coding-style-python.rst:314 +#: ../../source/development/integration/coding-style-python.rst:316 +#: ../../source/development/integration/coding-style-python.rst:318 +#: ../../source/development/integration/coding-style-python.rst:324 +msgid "``   ...``" +msgstr "``   ...``" + +#: ../../source/development/integration/coding-style-python.rst:315 +msgid "``   a_list = list(a_tuple)``" +msgstr "``   a_list = list(a_tuple)``" + +#: ../../source/development/integration/coding-style-python.rst:317 +msgid "``   another_list = [4, 5, 6]``" +msgstr "``   another_list = [4, 5, 6]``" + +#: ../../source/development/integration/coding-style-python.rst:319 +msgid "``   another_tuple = tuple(another_list)``" +msgstr "``   another_tuple = tuple(another_list)``" + +#: ../../source/development/integration/coding-style-python.rst:321 +msgid "Convert a list to a set, e.g. to filter out duplicates:" +msgstr "Convert a list to a set, e.g. to filter out duplicates:" + +#: ../../source/development/integration/coding-style-python.rst:323 +msgid "``   a_list = [1, 2, 3, 2]``" +msgstr "``   a_list = [1, 2, 3, 2]``" + +#: ../../source/development/integration/coding-style-python.rst:325 +msgid "``   a_set = set(a_list)``" +msgstr "``   a_set = set(a_list)``" + +#: ../../source/development/integration/coding-style-python.rst:327 +msgid "" +"For more involved cases, say some values need to be filtered or a " +"specific attribute of the objects is wanted, Python has so-called " +"comprehensions to create compound objects in a syntactically \"nice\" " +"way. These largely supersede the old (ugly) way of using ``map()`` and " +"``filter()`` in conjunction with class constructors." +msgstr "For more involved cases, say some values need to be filtered or a specific attribute of the objects is wanted, Python has so-called comprehensions to create compound objects in a syntactically \"nice\" way. These largely supersede the old (ugly) way of using ``map()`` and ``filter()`` in conjunction with class constructors." + +#: ../../source/development/integration/coding-style-python.rst:334 +msgid "Comprehension type" +msgstr "Comprehension type" + +#: ../../source/development/integration/coding-style-python.rst:334 +msgid "Example" +msgstr "Example" + +#: ../../source/development/integration/coding-style-python.rst:334 +msgid "Remarks" +msgstr "Remarks" + +#: ../../source/development/integration/coding-style-python.rst:336 +msgid "" +"`List Comprehension " +"`__" +msgstr "`List Comprehension `__" + +#: ../../source/development/integration/coding-style-python.rst:336 +msgid "``a_list = [x for x in range(20) if x % 2]``" +msgstr "``a_list = [x for x in range(20) if x % 2]``" + +#: ../../source/development/integration/coding-style-python.rst:336 +msgid "Put all odd numbers smaller than 20 into a list." +msgstr "Put all odd numbers smaller than 20 into a list." + +#: ../../source/development/integration/coding-style-python.rst:338 +msgid "" +"`Dict Comprehension " +"`__" +msgstr "`Dict Comprehension `__" + +#: ../../source/development/integration/coding-style-python.rst +msgid "``a_dict = {k: getattr(an_obj, k)``" +msgstr "``a_dict = {k: getattr(an_obj, k)``" + +#: ../../source/development/integration/coding-style-python.rst +msgid "``    for k in dir(an_obj)``" +msgstr "``    for k in dir(an_obj)``" + +#: ../../source/development/integration/coding-style-python.rst +msgid "``    if not k.startswith(\"_\")}``" +msgstr "``    if not k.startswith(\"_\")}``" + +#: ../../source/development/integration/coding-style-python.rst:338 +msgid "" +"Fill a dict with those attribute names and values of an object that " +"aren't considered \"protected\" or \"private\" (names with one or two " +"leading underscores, respectively)." +msgstr "Fill a dict with those attribute names and values of an object that aren't considered \"protected\" or \"private\" (names with one or two leading underscores, respectively)." + +#: ../../source/development/integration/coding-style-python.rst:342 +msgid "" +"`Set Comprehension " +"`__" +msgstr "`Set Comprehension `__" + +#: ../../source/development/integration/coding-style-python.rst:342 +msgid "``a_set = {o.name for o in a_list}``" +msgstr "``a_set = {o.name for o in a_list}``" + +#: ../../source/development/integration/coding-style-python.rst:342 +msgid "" +"Create a set containing the value of the attribute ``name`` of objects in" +" a list." +msgstr "Create a set containing the value of the attribute ``name`` of objects in a list." + +#: ../../source/development/integration/coding-style-python.rst:345 +msgid "Table: Using comprehensions to create compound objects" +msgstr "Table: Using comprehensions to create compound objects" + +#: ../../source/development/integration/coding-style-python.rst:348 +msgid "Looping" +msgstr "Looping" + +#: ../../source/development/integration/coding-style-python.rst:350 +msgid "Languages like C normally use incremented indices to loop over arrays:" +msgstr "Languages like C normally use incremented indices to loop over arrays:" + +#: ../../source/development/integration/coding-style-python.rst:365 +msgid "" +"Implementing the loop like this would give away that you've programmed in" +" C or a similar language before:" +msgstr "Implementing the loop like this would give away that you've programmed in C or a similar language before:" + +#: ../../source/development/integration/coding-style-python.rst:379 +msgid "Here's the \"native\" way to implement the above loop:" +msgstr "Here's the \"native\" way to implement the above loop:" + +#: ../../source/development/integration/coding-style-python.rst:392 +msgid "" +"It yields pairs of count (starting at 0 by default) and the current value" +" like this:" +msgstr "It yields pairs of count (starting at 0 by default) and the current value like this:" + +#: ../../source/development/integration/coding-style-python.rst:404 +msgid "Properties rather than explicit accessor methods" +msgstr "Properties rather than explicit accessor methods" + +#: ../../source/development/integration/coding-style-python.rst:406 +msgid "" +"In order to allow future changes in how object attributes (member " +"variables) are set, some languages encourage always using getter and/or " +"setter methods. This is unnecessary in Python, as you can intercept " +"access to an attribute by wrapping it into a `property " +"`__ if and " +"when this becomes necessary. Properties allow having accessor methods " +"without making the user of the class have to use them explicitly. This " +"way you can validate values when an attribute is set, or translate back " +"and forth between the interface used on the attribute and an internal " +"representation." +msgstr "In order to allow future changes in how object attributes (member variables) are set, some languages encourage always using getter and/or setter methods. This is unnecessary in Python, as you can intercept access to an attribute by wrapping it into a `property `__ if and when this becomes necessary. Properties allow having accessor methods without making the user of the class have to use them explicitly. This way you can validate values when an attribute is set, or translate back and forth between the interface used on the attribute and an internal representation." + +#: ../../source/development/integration/coding-style-python.rst:418 +msgid "Validating a value when setting an attribute" +msgstr "Validating a value when setting an attribute" + +#: ../../source/development/integration/coding-style-python.rst:420 +msgid "" +"To ensure that an ``Employee`` object only has positive values for its " +"``salary`` attribute, you'd put a property in its place which checks " +"values before storing them in an attribute called e.g. ``_salary``:" +msgstr "To ensure that an ``Employee`` object only has positive values for its ``salary`` attribute, you'd put a property in its place which checks values before storing them in an attribute called e.g. ``_salary``:" + +#: ../../source/development/integration/coding-style-python.rst:443 +msgid "Translating between attribute interface and internal representation" +msgstr "Translating between attribute interface and internal representation" + +#: ../../source/development/integration/coding-style-python.rst:445 +msgid "Take these classes of geometric primitives, ``Point`` and ``Circle``:" +msgstr "Take these classes of geometric primitives, ``Point`` and ``Circle``:" + +#: ../../source/development/integration/coding-style-python.rst:459 +msgid "" +"If you wanted to add a ``diameter`` attribute to ``Circle``, you can do " +"so as a property which translates back and forth between it and the " +"existing ``radius`` attribute:" +msgstr "If you wanted to add a ``diameter`` attribute to ``Circle``, you can do so as a property which translates back and forth between it and the existing ``radius`` attribute:" + +#: ../../source/development/integration/coding-style-python.rst:485 +msgid "" +"Even setting ``self.diameter`` in the constructor goes by way of the " +"property and therefore the setter method." +msgstr "Even setting ``self.diameter`` in the constructor goes by way of the property and therefore the setter method." + +#: ../../source/development/integration/coding-style-python.rst:489 +msgid "External links" +msgstr "External links" + +#: ../../source/development/integration/coding-style-python.rst:491 +msgid "" +"`Python Design and History FAQ " +"`__" +msgstr "`Python Design and History FAQ `__" + +#: ../../source/development/integration/coding-style-python.rst:493 +msgid "" +"`PEP8: Style Guide for Python Code " +"`__" +msgstr "`PEP8: Style Guide for Python Code `__" + +#: ../../source/development/integration/coding-style-python.rst:495 +msgid "`PEP20: The Zen of Python `__" +msgstr "`PEP20: The Zen of Python `__" + +#: ../../source/development/integration/coding-style-python.rst:497 +msgid "" +"`PyFormat `__: Using ``%`` and ``.format()`` for " +"great good!" +msgstr "`PyFormat `__: Using ``%`` and ``.format()`` for great good!" + +#: ../../source/development/integration/coding-style-python.rst:499 +msgid "" +"`Sphinx Info field lists " +"`__ for docstrings" +msgstr "`Sphinx Info field lists `__ for docstrings" + diff --git a/source/locale/de/LC_MESSAGES/development/integration/grooming.po b/source/locale/de/LC_MESSAGES/development/integration/grooming.po new file mode 100644 index 0000000..be21592 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/development/integration/grooming.po @@ -0,0 +1,244 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/development/integration/grooming.rst:2 +msgid "Grooming Your Changes" +msgstr "Grooming Your Changes" + +#: ../../source/development/integration/grooming.rst:4 +msgid "" +"Apart from coding style concerns, there are some things that you should " +"keep in mind regarding the changes you submit. Normally you'd develop " +"your changes in a private branch on your fork of a repository and, when " +"you're done, submit them as pull requests (\"PR\") against a public " +"branch of the repository. The following guidelines concentrate on changes" +" in this format, their goal is to enable you to groom the commits forming" +" your pull request so that another person can review it without great " +"effort, that the changes can be integrated well with the existing code " +"and can be easily debugged later if necessary." +msgstr "Apart from coding style concerns, there are some things that you should keep in mind regarding the changes you submit. Normally you'd develop your changes in a private branch on your fork of a repository and, when you're done, submit them as pull requests (\"PR\") against a public branch of the repository. The following guidelines concentrate on changes in this format, their goal is to enable you to groom the commits forming your pull request so that another person can review it without great effort, that the changes can be integrated well with the existing code and can be easily debugged later if necessary." + +#: ../../source/development/integration/grooming.rst:14 +msgid "Pull Requests" +msgstr "Pull Requests" + +#: ../../source/development/integration/grooming.rst:17 +msgid "Scope" +msgstr "Scope" + +#: ../../source/development/integration/grooming.rst:19 +msgid "" +"One pull request should really be about implementing one feature or " +"solving one problem. For instance, when developing your changes you might" +" spot a bug in existing code and fix it. Mixing these changes with your " +"new feature make reviewing them more work because the person doing it " +"needs to assess if a chunk of your changes is related to the feature, or " +"the bug fix. Similarly, if the review of your feature drags out, the bug " +"fix might take that much longer before it's available to others. In most " +"cases you should therefore create separate pull requests for both sets of" +" changes." +msgstr "One pull request should really be about implementing one feature or solving one problem. For instance, when developing your changes you might spot a bug in existing code and fix it. Mixing these changes with your new feature make reviewing them more work because the person doing it needs to assess if a chunk of your changes is related to the feature, or the bug fix. Similarly, if the review of your feature drags out, the bug fix might take that much longer before it's available to others. In most cases you should therefore create separate pull requests for both sets of changes." + +#: ../../source/development/integration/grooming.rst:29 +msgid "" +"As an exception to that, merely janitorial changes to the parts of the " +"code your pull request touches anyway—say, fixing trailing whitespace or " +"indentation, superficial changes that make the code you worked on better " +"to read or understand—are acceptable as long as you put these changes in " +"a commit or commits of their own, ideally put before your \"real\" " +"changes in the commit order. This makes it easier to cope with other PRs " +"that might fix the same things." +msgstr "As an exception to that, merely janitorial changes to the parts of the code your pull request touches anyway—say, fixing trailing whitespace or indentation, superficial changes that make the code you worked on better to read or understand—are acceptable as long as you put these changes in a commit or commits of their own, ideally put before your \"real\" changes in the commit order. This makes it easier to cope with other PRs that might fix the same things." + +#: ../../source/development/integration/grooming.rst:38 +msgid "Describing your changes" +msgstr "Describing your changes" + +#: ../../source/development/integration/grooming.rst:40 +msgid "" +"The bigger the changes you submit are, the more important it is to give " +"the reviewer a high level summary of what it is they are reviewing. If a " +"pull request consists only of one commit, then its commit log should be " +"sufficient in most cases and the forges hosting our repositories (Pagure " +"and GitHub) use it as the default description text on submission. If it " +"is longer, you may need to condense the individual changes of your " +"commits, and maybe lose some comments about the problem you wanted to " +"solve and your approach. If you are unsure about parts of your changes, " +"this is also the place give the reviewer a heads-up." +msgstr "The bigger the changes you submit are, the more important it is to give the reviewer a high level summary of what it is they are reviewing. If a pull request consists only of one commit, then its commit log should be sufficient in most cases and the forges hosting our repositories (Pagure and GitHub) use it as the default description text on submission. If it is longer, you may need to condense the individual changes of your commits, and maybe lose some comments about the problem you wanted to solve and your approach. If you are unsure about parts of your changes, this is also the place give the reviewer a heads-up." + +#: ../../source/development/integration/grooming.rst:51 +msgid "Linear History and Rebasing" +msgstr "Linear History and Rebasing" + +#: ../../source/development/integration/grooming.rst:53 +msgid "" +"The changes you submit for reviewing should be a linear string of " +"commits, please don't have merges in there. Therefore, in order to track " +"upstream changes while you are still developing in a private branch, you " +"should rebase it on top of the upstream branch you track. You can of " +"course do that manually, but it's easier to tell git to automatically " +"attempt to rebase your changes on top of the branch from which you pull " +"(replace ``$branchname`` with the actual name of your local branch):" +msgstr "The changes you submit for reviewing should be a linear string of commits, please don't have merges in there. Therefore, in order to track upstream changes while you are still developing in a private branch, you should rebase it on top of the upstream branch you track. You can of course do that manually, but it's easier to tell git to automatically attempt to rebase your changes on top of the branch from which you pull (replace ``$branchname`` with the actual name of your local branch):" + +#: ../../source/development/integration/grooming.rst:61 +msgid "``   git config branch.$branchname.rebase true``" +msgstr "``   git config branch.$branchname.rebase true``" + +#: ../../source/development/integration/grooming.rst:63 +msgid "" +"You can also set this globally for any newly created branch (you'd have " +"to do the above for all existing branches, though):" +msgstr "You can also set this globally for any newly created branch (you'd have to do the above for all existing branches, though):" + +#: ../../source/development/integration/grooming.rst:66 +msgid "``   git config --global branch.autosetuprebase always``" +msgstr "``   git config --global branch.autosetuprebase always``" + +#: ../../source/development/integration/grooming.rst:68 +msgid "" +"Set up this way, pulling from upstream will attempt to apply your private" +" commits in order on top of the new upstream ones, one after another. If " +"that fails at some point, e.g. because of conflicts, it'll interrupt the " +"rebasing process, so that you can resolve the issue, and continue with " +"``git rebase --cont``. Alternatively, you could also restore the previous" +" state by running ``git rebase --abort``, e.g. to assess the differences " +"between your (unrebased) branch and upstream before giving it a go again." +msgstr "Set up this way, pulling from upstream will attempt to apply your private commits in order on top of the new upstream ones, one after another. If that fails at some point, e.g. because of conflicts, it'll interrupt the rebasing process, so that you can resolve the issue, and continue with ``git rebase --cont``. Alternatively, you could also restore the previous state by running ``git rebase --abort``, e.g. to assess the differences between your (unrebased) branch and upstream before giving it a go again." + +#: ../../source/development/integration/grooming.rst:78 +msgid "The Review" +msgstr "The Review" + +#: ../../source/development/integration/grooming.rst:80 +msgid "" +"When you've submitted your changes as a pull request, hopefully someone " +"will pick it up soon (if not, poke some people on IRC: `#fedora-" +"modularity on Freenode `__) " +"and give you feedback in form of comments, questions or suggestions. The " +"comment section of a pull request isn't very suitable for longer " +"discussions, so you might switch to email, IRC or another medium to " +"discuss a topic, and then summarize in the PR. Consulting other " +"contributors is encouraged, if additional opinions are needed. The job of" +" a reviewer is not just to act as a gatekeeper for the project, but also " +"to assist you in getting your changes into an acceptable state. This can " +"go as far as making minor fixes on the fly rather than asking you to do " +"it, or bringing the stack of commits \"into shape\" before merging the " +"pull request." +msgstr "When you've submitted your changes as a pull request, hopefully someone will pick it up soon (if not, poke some people on IRC: `#fedora-modularity on Freenode `__) and give you feedback in form of comments, questions or suggestions. The comment section of a pull request isn't very suitable for longer discussions, so you might switch to email, IRC or another medium to discuss a topic, and then summarize in the PR. Consulting other contributors is encouraged, if additional opinions are needed. The job of a reviewer is not just to act as a gatekeeper for the project, but also to assist you in getting your changes into an acceptable state. This can go as far as making minor fixes on the fly rather than asking you to do it, or bringing the stack of commits \"into shape\" before merging the pull request." + +#: ../../source/development/integration/grooming.rst:95 +msgid "Individual commits" +msgstr "Individual commits" + +#: ../../source/development/integration/grooming.rst:98 +msgid "Commit Scope and Size" +msgstr "Commit Scope and Size" + +#: ../../source/development/integration/grooming.rst:100 +msgid "" +"Like a pull request itself, a commit should also be about just one thing." +" For example, you should split the implementation of a new class from " +"where existing code is converted to use it, as well as removing the " +"legacy code it replaces. The reverse also holds true—one concern should " +"be dealt with in one commit: if you discover bugs in a newly introduced " +"piece of code while you're still developing it, the buggy commit " +"introducing it and the fix should be rolled into one. This keeps the " +"number of broken commits down which e.g. makes it easier to use ``git " +"bisect`` at a later point." +msgstr "Like a pull request itself, a commit should also be about just one thing. For example, you should split the implementation of a new class from where existing code is converted to use it, as well as removing the legacy code it replaces. The reverse also holds true—one concern should be dealt with in one commit: if you discover bugs in a newly introduced piece of code while you're still developing it, the buggy commit introducing it and the fix should be rolled into one. This keeps the number of broken commits down which e.g. makes it easier to use ``git bisect`` at a later point." + +#: ../../source/development/integration/grooming.rst:115 +msgid "Commit Log Messages" +msgstr "Commit Log Messages" + +#: ../../source/development/integration/grooming.rst:117 +msgid "" +"The purpose of a commit log message is to briefly summarize the changes " +"in the commit, but it's also where background information should be put, " +"e.g. why some approach was used and not another." +msgstr "The purpose of a commit log message is to briefly summarize the changes in the commit, but it's also where background information should be put, e.g. why some approach was used and not another." + +#: ../../source/development/integration/grooming.rst:122 +msgid "Format" +msgstr "Format" + +#: ../../source/development/integration/grooming.rst:124 +msgid "" +"A commit log should consist of a short summary line (<50 characters, also" +" called \"title\"), optionally followed by a blank line and a more " +"thorough description. The summary should tersely describe the objective " +"of the commit, while the description would go into detail about the " +"actual implementation." +msgstr "A commit log should consist of a short summary line (<50 characters, also called \"title\"), optionally followed by a blank line and a more thorough description. The summary should tersely describe the objective of the commit, while the description would go into detail about the actual implementation." + +#: ../../source/development/integration/grooming.rst:131 +msgid "Building a Commit" +msgstr "Building a Commit" + +#: ../../source/development/integration/grooming.rst:133 +msgid "" +"Often you'll want to pick only parts of your uncommitted changes, in " +"order to follow these guidelines, or to leave out debugging statements " +"which you don't want to submit. You can select the parts in your changes " +"you want to commit by using ``git add --patch`` which presents the " +"differences as hunks in unified diff format and lets you choose which " +"ones to add to the staging area and which to skip. After committing these" +" staged changes, you can repeat the process until all changes you want to" +" submit are taken care of. There are ways to separate a large commit into" +" smaller ones, but this approach is often more difficult one of the two." +msgstr "Often you'll want to pick only parts of your uncommitted changes, in order to follow these guidelines, or to leave out debugging statements which you don't want to submit. You can select the parts in your changes you want to commit by using ``git add --patch`` which presents the differences as hunks in unified diff format and lets you choose which ones to add to the staging area and which to skip. After committing these staged changes, you can repeat the process until all changes you want to submit are taken care of. There are ways to separate a large commit into smaller ones, but this approach is often more difficult one of the two." + +#: ../../source/development/integration/grooming.rst:145 +msgid "Tools" +msgstr "Tools" + +#: ../../source/development/integration/grooming.rst:147 +msgid "" +"Adding using patch mode: With ``git add --patch ...`` you can pick which " +"changes you want to commit." +msgstr "Adding using patch mode: With ``git add --patch ...`` you can pick which changes you want to commit." + +#: ../../source/development/integration/grooming.rst:149 +msgid "" +"Interactive rebasing: Use ``git rebase -i ... @{u}`` to reorder your " +"commits, reword their commit messages, merge or amend them. It's " +"important to not do this to upstream commits, therefore ``@{u}`` " +"specifies the point where your branch split off from upstream." +msgstr "Interactive rebasing: Use ``git rebase -i ... @{u}`` to reorder your commits, reword their commit messages, merge or amend them. It's important to not do this to upstream commits, therefore ``@{u}`` specifies the point where your branch split off from upstream." + +#: ../../source/development/integration/grooming.rst:163 +msgid "See also" +msgstr "See also" + +#: ../../source/development/integration/grooming.rst:165 +msgid "The `Pro Git book `__" +msgstr "The `Pro Git book `__" + +#: ../../source/development/integration/grooming.rst:167 +msgid "" +"The `\"Rewriting History\" `__ chapter for more detailed information about " +"amending, interactive rebasing, and other advanced ways of screwing up " +"your repository ;)" +msgstr "The `\"Rewriting History\" `__ chapter for more detailed information about amending, interactive rebasing, and other advanced ways of screwing up your repository ;)" + diff --git a/source/locale/de/LC_MESSAGES/development/resources.po b/source/locale/de/LC_MESSAGES/development/resources.po new file mode 100644 index 0000000..7fa9b71 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/development/resources.po @@ -0,0 +1,95 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/development/resources.rst:2 +msgid "Resources" +msgstr "Ressourcen" + +#: ../../source/development/resources.rst:4 +msgid "This page lists our Git repositories and other resources we use." +msgstr "Diese Seite enthält unsere Git-Repositorys und andere Ressourcen, die wir verwenden." + +#: ../../source/development/resources.rst:8 +msgid "Git Repositories" +msgstr "Git-Repositorys" + +#: ../../source/development/resources.rst:11 +msgid "Specifications" +msgstr "Spezifikationen" + +#: ../../source/development/resources.rst:13 +msgid "" +"`Modulemd `__ - This repository contains the " +"definition of metadata format (Modulemd) used to describe every module. " +"It also contains Python library used to manipulate files in this format." +msgstr "`Modulemd `__ – Dieses Repository enthält die Definition des Metadaten-Formats (Modulemd), das zur Beschreibung jeden Moduls verwendet wird. Es enthält auch die Python-Bibliothek, die zum Manipulieren von Dateien in diesem Format verwendet wird." + +#: ../../source/development/resources.rst:19 +msgid "Content" +msgstr "Content" + +#: ../../source/development/resources.rst:21 +msgid "" +"`Fedora 27 Content Tracking `__ - Content (modules) delivered by the Modularity WG " +"is tracked here." +msgstr "`Fedora 27 Content Tracking `__ – Content (Module), der von der Modularity WG bereit gestellt wird, wird hier erfasst." + +#: ../../source/development/resources.rst:24 +msgid "" +"`Host & Platform upstream `__ - " +"Host and Platform is a set of modules or module stacks defining the base " +"operating system, effectively replacing Fedora 26 Boltron Base Runtime " +"module & concept." +msgstr "`Host & Platform Upstream `__ – Host & Plattform ist ein Set von Modulen oder Modul-Stacks, die das Basissystem definieren. Effektiv ersetzen diese das Fedora 26 Boltron Base-Runtime-Modul & -Konzept." + +#: ../../source/development/resources.rst:29 +msgid "" +"`Fedora dist-git `__ - Module definitions" +" are stored in a Fedora dist-git `/modules` namespace. There is no URL to" +" the namespace itself, only to individual modules. Please see the " +"`platform module definition " +"`__ as an example." +msgstr "`Fedora Dist-Git `__ – Moduldefinitionen werden in einem Fedora Dist-Git`/modules`-Namensraum abgespeichert. Es existiert keine URL für den Namensraum selbst, nur für einzelne Module. Bitte beachten Sie die `platform module definition `__ als ein Beispiel." + +#: ../../source/development/resources.rst:37 +msgid "Scripts and tooling" +msgstr "Skripte und Werkzeuge" + +#: ../../source/development/resources.rst:39 +msgid "" +"`FedMod `__ - A tool developed by " +"the Modularity WG helping packagers to develop new modules, and to query " +"information about existing ones." +msgstr "`FedMod `__ – Ein Werkzeug, entwickelt von der Modularity Working Group, das Paketbetreuern hilft neue Module zu entwickeln und Informationen über existierende abzufragen." + +#: ../../source/development/resources.rst:43 +msgid "" +"`Modularity on GitHub `__ - Other " +"repositories on GitHub." +msgstr "`Modularity on GitHub `__ – andere Repositorys auf GitHub." + +#: ../../source/development/resources.rst:46 +msgid "" +"`Modularity on Pagure `__ - Other " +"repositories on Pagure." +msgstr "`Modularity on Pagure `__ – andere Repositorys auf Pagure." + diff --git a/source/locale/de/LC_MESSAGES/docs.po b/source/locale/de/LC_MESSAGES/docs.po new file mode 100644 index 0000000..71a01d2 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/docs.po @@ -0,0 +1,50 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Markus Richter \n" +"Language-Team: de_DE <>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" +"Language: de_DE\n" + +#: ../../source/docs.rst:7 +msgid "Documentation Index" +msgstr "Dokumentationsverzeichnis" + +#: ../../source/docs.rst:10 +msgid "Prototype" +msgstr "Prototyp" + +#: ../../source/docs.rst:17 +msgid "Design" +msgstr "Design" + +#: ../../source/docs.rst:26 +msgid "Development" +msgstr "Entwicklung" + +#: ../../source/docs.rst:35 +msgid "Infrastructure" +msgstr "Infrastruktur" + +#: ../../source/docs.rst:42 +msgid "Usability" +msgstr "Usability" + +#: ../../source/docs.rst:48 +msgid "Project" +msgstr "Projekt" + diff --git a/source/locale/de/LC_MESSAGES/infrastructure/infrastructure.po b/source/locale/de/LC_MESSAGES/infrastructure/infrastructure.po new file mode 100644 index 0000000..ea3f127 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/infrastructure/infrastructure.po @@ -0,0 +1,74 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/infrastructure/infrastructure.rst:2 +msgid "Infrastructure" +msgstr "Infrastruktur" + +#: ../../source/infrastructure/infrastructure.rst:4 +msgid "" +"Modularity will be built using the `Factory 2.0, documented on the Fedora" +" wiki `__." +msgstr "Modularity wird erzeugt mittels `Factory 2.0, dokumentiert im Fedora Wiki `__." + +#: ../../source/infrastructure/infrastructure.rst:9 +msgid "Focus Documents" +msgstr "Focus Documents" + +#: ../../source/infrastructure/infrastructure.rst:11 +msgid "" +"The Factory 2.0 team produces a confusing number of documents. The first " +"round was about the Problem Statements we were trying to solve. Let’s " +"retroactively call them Problem Documents. The `Focus Documents " +"`__ focus " +"on some system or some aspect of our solutions that cut across different " +"problems. The content here doesn’t fit cleanly in one problem statement " +"document, which is why we broke it out." +msgstr "Das Factory 2.0 Team fertigt eine verwirrende Anzahl von Dokumenten an. Die erste Runde waren Problemdarstellungen, die wir zu lösen versuchen. Wir nennen sie rückwirkend Problemdokumente. Die `Focus Documents `__ konzentrieren sich auf ein System oder einen Aspekt unserer Lösungen, die sich über unterschiedliche Problembereiche erstrecken. Der Inhalt hier passt nicht sauber in ein Dokument für Problembeschreibungen, weshalb wir ihn herausbrechen." + +#: ../../source/infrastructure/infrastructure.rst:19 +msgid "**The most important ones related to Modularity include**:" +msgstr "**Die wichtigsten Dokumente im Zusammenhang mit Modularity:**" + +#: ../../source/infrastructure/infrastructure.rst:21 +msgid "" +"`Module Build Service (MBS) " +"`__ - A" +" service that orchestrates module builds in the Fedora infrastructure." +msgstr "`Module Build Service (MBS) `__ – Ein Service, der Module-Builds orchestriert in der Fedora Infrastruktur." + +#: ../../source/infrastructure/infrastructure.rst:25 +msgid "" +"`Arbitrary Branching " +"`__" +" - Support of version branches in dist-git which allows us to maintain " +"multiple versions of packages and modules." +msgstr "`Arbitrary Branching `__ – Unterstützung von Versionszweigen in DistGit, was es uns erlaubt, mehrere Versionen der Pakete und Module zu verwalten." + +#: ../../source/infrastructure/infrastructure.rst:30 +msgid "" +"`Freshmaker " +"`__" +" - A service that will automatically rebuild artifacts (like module " +"repositories or container images) to make sure that everything is up to " +"date." +msgstr "`Freshmaker `__ – Ein Dienst, der automatisch Artefakte (wie Modul-Repositorys oder Container-Images) neu erstellt, um sicherzustellen, dass alles auf dem neuesten Stand bleibt." + diff --git a/source/locale/de/LC_MESSAGES/project/get-involved.po b/source/locale/de/LC_MESSAGES/project/get-involved.po new file mode 100644 index 0000000..49f0d52 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/project/get-involved.po @@ -0,0 +1,123 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/project/get-involved.rst:2 +msgid "Get Involved" +msgstr "Sich einbringen" + +#: ../../source/project/get-involved.rst:5 +msgid "Steps to get involved" +msgstr "Schritte, um sich zu einzubringen" + +#: ../../source/project/get-involved.rst:11 +msgid "" +"To get involved with the Modularity Working Group, please follow the " +"following steps for becoming a part of the team." +msgstr "Um sich in der Modularity Working Group zu engagieren, befolgen Sie die folgenden Schritte, um ein Teil des Teams zu werden." + +#: ../../source/project/get-involved.rst:14 +msgid "" +"Read this wiki page and understand the development methods and technical " +"details." +msgstr "Lesen Sie diese Wiki-Seite und verstehen Sie die Entwicklungsmethoden und technischen Details." + +#: ../../source/project/get-involved.rst:16 +msgid "" +"Get in touch with us on the `devel mailing list " +"`__" +" and our IRC channel, `#fedora-modularity " +"`__." +msgstr "Nehmen Sie Kontakt mit uns auf in der `devel Mailinglist `__ und unserem IRC-Channel `#fedora-modularity `__." + +#: ../../source/project/get-involved.rst:20 +msgid "" +"Attend one of our `weekly meetings " +"`__ and introduce " +"yourself." +msgstr "Besuchen Sie eines unserer `zweiwöchentlichen Meetings `__ und stellen Sie sich vor." + +#: ../../source/project/get-involved.rst:23 +msgid "" +"Create an account on `Pagure `__ and file an issue in" +" the `Fedora @modularity group `__ " +"requesting membership." +msgstr "Erstellen Sie ein Konto auf `Pagure `__ und reichen Sie ein Issue in der `Fedora @modularity group `__ ein, um eine Mitgliedschaft anzufordern." + +#: ../../source/project/get-involved.rst:28 +msgid "Get in touch" +msgstr "In Kontakt treten" + +#: ../../source/project/get-involved.rst:30 +msgid "" +"There's no dedicated mailing list for this effort, everything regarding " +"this topic should be discussed on the general `Fedora Development list " +"`__." +" Most of us also hang out on the #fedora-modularity channel on Freenode." +msgstr "Es gibt keine gesonderte Mailingliste für diesen Bereich, alles zu diesem Thema sollte daher diskutiert werden auf der allgemeinen `Fedora Development Mailingliste `__. Viele von uns sind auf dem Freenode-Channel #fedora-modularity anzutreffen." + +#: ../../source/project/get-involved.rst:36 +msgid "Planning" +msgstr "Planung" + +#: ../../source/project/get-involved.rst:38 +msgid "" +"Formal meetings are held once every two weeks by the Modularity Working " +"Group. See the `Fedocal " +"`__ to find out when" +" the group will meet." +msgstr "Formelle Sitzungen werden einmal alle zwei Wochen durch die Modularity Working Group abgehalten. Siehe im `Fedocal `__, um herauszufinden, wann die Gruppe sich trifft." + +#: ../../source/project/get-involved.rst:44 +msgid "Technical details" +msgstr "Technische Details" + +#: ../../source/project/get-involved.rst:47 +msgid "Project repositories" +msgstr "Projekt-Repositorys" + +#: ../../source/project/get-involved.rst:49 +msgid "" +"We host our individual projects either on `Pagure " +"`__, `GitHub `__ or in the " +"`Fedora Packages repository `__." +msgstr "Wir hosten unsere individuellen Projekte entweder auf `Pagure `__, `GitHub `__ oder in dem `Fedora Packages Repository `__." + +#: ../../source/project/get-involved.rst:53 +msgid "" +"Tooling and infrastructure projects can be found in the `Pagure group for" +" Modularity `__ or the |gh-fedmod-" +"org|_. Modules themselves are in the `Fedora Packages repository " +"`__ under the ``modules`` namespace, they " +"have counterparts in the |gh-modmod-org|_ which deal with their " +"individual package components." +msgstr "Werkzeuge und Infrastrukturprojekte finden Sie in der `Pagure group for Modularity `__ oder der |gh-fedmod-org|_. Module selbst sind im `Fedora Packages Repository `__ unter dem ``modules``-Namensraum, diese haben Gegenstücke in der |gh-modmod-org|_, die mit ihren individuellen Paketkomponenten ausgestattet sind." + +#: ../../source/project/get-involved.rst:66 +msgid "Integration of changes" +msgstr "Integration von Änderungen" + +#: ../../source/project/get-involved.rst:68 +msgid "" +"In order so that our code base is always clean and maintainable, we have " +"to enforce certain rules on how code is written or formatted, how changes" +" are broken up into commits and how pull requests are handled." +msgstr "Um unsere Code-Basis immer sauber und wartbar zu halten, müssen bestimmte Regeln eingehalten werden: wie Code geschrieben oder formatiert wird, wie Änderungen in Commits aufgespalten werden und wie Pull Requests verarbeitet werden." + diff --git a/source/locale/de/LC_MESSAGES/prototype/boltron.po b/source/locale/de/LC_MESSAGES/prototype/boltron.po new file mode 100644 index 0000000..10fe201 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/prototype/boltron.po @@ -0,0 +1,33 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/prototype/boltron.rst:2 +msgid "Fedora 26 Boltron Server" +msgstr "Fedora 26 Boltron Server" + +#: ../../source/prototype/boltron.rst:5 +msgid "Fedora 26 Boltron Server is a first prototype of a modular distribution." +msgstr "Fedora 26 Boltron Server ist ein erster Prototyp einer modularen Distribution." + +#: ../../source/prototype/boltron.rst:15 +msgid "Other sections" +msgstr "TOC" + diff --git a/source/locale/de/LC_MESSAGES/prototype/boltron/content.po b/source/locale/de/LC_MESSAGES/prototype/boltron/content.po new file mode 100644 index 0000000..b595134 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/prototype/boltron/content.po @@ -0,0 +1,139 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/prototype/boltron/content.rst:2 +msgid "Boltron Content" +msgstr "Content für Boltron " + +#: ../../source/prototype/boltron/content.rst:4 +msgid "" +"The following is a list of modules that we have completed. Many of the " +"`modules are also available as containers " +"`__ on dockerhub." +msgstr "Das Folgende stellt eine Auflistung der Module dar, die wir bisher abgeschlossen haben. Viele dieser `Module stehen ebenso als Container zur Verfügung `__ auf Docker Hub." + +#: ../../source/prototype/boltron/content.rst:8 +msgid "`base-runtime-f26`" +msgstr "`base-runtime-f26`" + +#: ../../source/prototype/boltron/content.rst:9 +msgid "`container-runtime-f26`" +msgstr "`container-runtime-f26`" + +#: ../../source/prototype/boltron/content.rst:10 +msgid "`dhcp-f26`" +msgstr "`dhcp-f26`" + +#: ../../source/prototype/boltron/content.rst:11 +msgid "`dhcp-server-f26`" +msgstr "`dhcp-server-f26`" + +#: ../../source/prototype/boltron/content.rst:12 +msgid "`dnf-f26`" +msgstr "`dnf-f26`" + +#: ../../source/prototype/boltron/content.rst:13 +msgid "`haproxy-f26`" +msgstr "`haproxy-f26`" + +#: ../../source/prototype/boltron/content.rst:14 +msgid "`httpd-f26`" +msgstr "`httpd-f26`" + +#: ../../source/prototype/boltron/content.rst:15 +msgid "`installer-f26`" +msgstr "`installer-f26`" + +#: ../../source/prototype/boltron/content.rst:16 +msgid "`mariadb-f26`" +msgstr "`mariadb-f26`" + +#: ../../source/prototype/boltron/content.rst:17 +msgid "`memcached-f26`" +msgstr "`memcached-f26`" + +#: ../../source/prototype/boltron/content.rst:18 +msgid "`mongodb-f26`" +msgstr "`mongodb-f26`" + +#: ../../source/prototype/boltron/content.rst:19 +msgid "`nginx-f26`" +msgstr "`nginx-f26`" + +#: ../../source/prototype/boltron/content.rst:20 +msgid "`nodejs-8`" +msgstr "`nodejs-8`" + +#: ../../source/prototype/boltron/content.rst:21 +msgid "`nodejs-f26`" +msgstr "`nodejs-f26`" + +#: ../../source/prototype/boltron/content.rst:22 +msgid "`perl-f26`" +msgstr "`perl-f26`" + +#: ../../source/prototype/boltron/content.rst:23 +msgid "`perl-Unicode-EastAsianWidth-f26`" +msgstr "`perl-Unicode-EastAsianWidth-f26`" + +#: ../../source/prototype/boltron/content.rst:24 +msgid "`php-f26`" +msgstr "`php-f26`" + +#: ../../source/prototype/boltron/content.rst:25 +msgid "`postfix-f26`" +msgstr "`postfix-f26`" + +#: ../../source/prototype/boltron/content.rst:26 +msgid "`postgresql-f26`" +msgstr "`postgresql-f26`" + +#: ../../source/prototype/boltron/content.rst:27 +msgid "`shared-userspace-f26`" +msgstr "`shared-userspace-f26`" + +#: ../../source/prototype/boltron/content.rst:28 +msgid "`shim-master`" +msgstr "`shim-master`" + +#: ../../source/prototype/boltron/content.rst:29 +msgid "`source-to-image-f26`" +msgstr "`source-to-image-f26`" + +#: ../../source/prototype/boltron/content.rst:30 +msgid "`sssd-f26`" +msgstr "`sssd-f26`" + +#: ../../source/prototype/boltron/content.rst:31 +msgid "`systemtools-f26`" +msgstr "`systemtools-f26`" + +#: ../../source/prototype/boltron/content.rst:32 +msgid "`varnish-f26`" +msgstr "`varnish-f26`" + +#: ../../source/prototype/boltron/content.rst:34 +msgid "" +"For more information about individual modules - both completed and in " +"progress - see the `Fedora Modularity: Modules GitHub space " +"`__." +msgstr "Für weitere Informationen zu einzelnen Modulen – sowohl abgeschlossen als auch in Entwicklung: `Fedora Modularity: Modules GitHub Space `__." + diff --git a/source/locale/de/LC_MESSAGES/prototype/boltron/feedback.po b/source/locale/de/LC_MESSAGES/prototype/boltron/feedback.po new file mode 100644 index 0000000..06cc847 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/prototype/boltron/feedback.po @@ -0,0 +1,632 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/prototype/boltron/feedback.rst:2 +msgid "Boltron Feedback" +msgstr "Feedback zu Boltron" + +#: ../../source/prototype/boltron/feedback.rst:5 +msgid "Give Feedback" +msgstr "Einbringen von Feedback" + +#: ../../source/prototype/boltron/feedback.rst:7 +msgid "" +"You can give us either general Modularity feedback or try the walkthrough" +" for more detailed and UX feedback. You can also get in touch on our " +"`#fedora-modularity irc channel " +"`__." +msgstr "Es ist möglich, an uns Feedback allgemeiner Natur zu Modularity zu geben oder aber den Walkthrough zu verwenden für ein detaillierteres Feedback, das auch die Benutzererfahrung (UX) umfasst. Kontakt kann auch über den `#fedora-modularity IRC-Channel `__ zustande kommen." + +#: ../../source/prototype/boltron/feedback.rst:23 +msgid "Reponses" +msgstr "Rückmeldungen" + +#: ../../source/prototype/boltron/feedback.rst:25 +msgid "This section is being updated every Monday, starting 2017-08-07." +msgstr "Dieser Abschnitt wird jeden Montag aktualisiert, beginnend mit dem 07.08.2017." + +#: ../../source/prototype/boltron/feedback.rst:27 +msgid "" +"The responses contain many questions - anwers are not part of this first " +"update, but they will be coming out soon." +msgstr "Die Rückmeldungen beinhalten viele Fragen – Antworten sind nicht Teil der ersten Aktualisierung, werden aber bald nachgereicht." + +#: ../../source/prototype/boltron/feedback.rst:30 +msgid "User Experience Walkthrough and Feedback" +msgstr "Walkthrough Benutzererfahrung und Feedback" + +#: ../../source/prototype/boltron/feedback.rst:32 +msgid "Updated: 2017-07-31" +msgstr "Aktualisiert: 31.07.2017" + +#: ../../source/prototype/boltron/feedback.rst:35 +msgid "How do you like the following commands?" +msgstr "Wie gefallen Ihnen die folgenden Kommandos?" + +#: ../../source/prototype/boltron/feedback.rst:41 +msgid "Please rate the following commands in terms of backwards compatibility." +msgstr "Bewerten Sie bitte die folgenden Kommandos im Hinblick auf die Rückwärtskompatibilität." + +#: ../../source/prototype/boltron/feedback.rst:47 +msgid "Anything else about the install syntax?" +msgstr "Weitere Anmerkungen zur Syntax der Installation?" + +#: ../../source/prototype/boltron/feedback.rst:49 +msgid "" +"The \"automatic module or package\" syntax overriding the original \"dnf " +"install httpd\" is BAD. At least there MUST be a new \"dnf package " +"install httpd\" for those that know they want to install a package and " +"not a same-named module." +msgstr "The \"automatic module or package\" syntax overriding the original \"dnf install httpd\" is BAD. At least there MUST be a new \"dnf package install httpd\" for those that know they want to install a package and not a same-named module." + +#: ../../source/prototype/boltron/feedback.rst:50 +msgid "Please do not reuse same sintax for modules." +msgstr "Please do not reuse same sintax for modules." + +#: ../../source/prototype/boltron/feedback.rst:51 +msgid "" +"Dnf install_module httpd clarity and auto-completion. Or make modules and" +" package names unique httpd-module" +msgstr "Dnf install_module httpd clarity and auto-completion. Or make modules and package names unique httpd-module" + +#: ../../source/prototype/boltron/feedback.rst:52 +msgid "dnf install-module httpd" +msgstr "dnf install-module httpd" + +#: ../../source/prototype/boltron/feedback.rst:53 +msgid "it is confusing of what is happening." +msgstr "it is confusing of what is happening." + +#: ../../source/prototype/boltron/feedback.rst:54 +msgid "" +"I think it should be clear if one installs a package or a module. Groups " +"could be considered the same as modules, though." +msgstr "I think it should be clear if one installs a package or a module. Groups could be considered the same as modules, though." + +#: ../../source/prototype/boltron/feedback.rst:55 +msgid "" +"Please keep current behaviour, \"dnf install httpd\" shall install the " +"package. There may be added a \"dnf package install\" and make the " +"previous one configurable." +msgstr "Please keep current behaviour, \"dnf install httpd\" shall install the package. There may be added a \"dnf package install\" and make the previous one configurable." + +#: ../../source/prototype/boltron/feedback.rst:56 +msgid "" +"Actually, I thought you will 'enable'/disable a module rather than " +"'installing'/removing it! :P" +msgstr "Actually, I thought you will 'enable'/disable a module rather than 'installing'/removing it! :P" + +#: ../../source/prototype/boltron/feedback.rst:57 +msgid "" +"Clear differentation between module and regular package. Consider " +"ansible/chef/puppet use cases too" +msgstr "Clear differentation between module and regular package. Consider ansible/chef/puppet use cases too" + +#: ../../source/prototype/boltron/feedback.rst:58 +msgid "Someone may get a modular package when they want just the most current." +msgstr "Someone may get a modular package when they want just the most current." + +#: ../../source/prototype/boltron/feedback.rst:59 +msgid "" +"You're in a losing battle here. You can't reuse syntax without tripping " +"up existing work flows but adding new syntax is just annoying. I think it" +" needs to be obvious it's not a 'standard' install, but I don't think you" +" can reuse group nomenclature." +msgstr "You're in a losing battle here. You can't reuse syntax without tripping up existing work flows but adding new syntax is just annoying. I think it needs to be obvious it's not a 'standard' install, but I don't think you can reuse group nomenclature." + +#: ../../source/prototype/boltron/feedback.rst:60 +msgid "" +"It should be possible to install both modules and packages in a single " +"yum/dnf command." +msgstr "It should be possible to install both modules and packages in a single yum/dnf command." + +#: ../../source/prototype/boltron/feedback.rst:61 +msgid "" +"I think that since there are existing users, we shouldn't overload them " +"with significantly different functionality." +msgstr "I think that since there are existing users, we shouldn't overload them with significantly different functionality." + +#: ../../source/prototype/boltron/feedback.rst:62 +msgid "" +"I think 'dnf install $package' makes sense for base packages ie. kernel " +"images, kernel headers, kernel modules, shells. 'dnf module install " +"$package' makes more sense for applications such as mariadb, postgres, " +"httpd, php, etc." +msgstr "I think 'dnf install $package' makes sense for base packages ie. kernel images, kernel headers, kernel modules, shells. 'dnf module install $package' makes more sense for applications such as mariadb, postgres, httpd, php, etc." + +#: ../../source/prototype/boltron/feedback.rst:65 +msgid "" +"Only one stream of a module can be installed at a time. How do you like " +"this decison?" +msgstr "Es kann lediglich jeweils ein Stream eines Moduls installiert werden. Was halten Sie von dieser Entscheidung?" + +#: ../../source/prototype/boltron/feedback.rst:71 +msgid "Anything else about \"Only one stream of a module can be installed\"?" +msgstr "Weitere Anmerkungen dazu, dass lediglich jeweils ein Stream eines Moduls installiert werden kann?" + +#: ../../source/prototype/boltron/feedback.rst:73 +msgid "" +"It would be better if multiple versions are allowed, but I didn't think " +"of the best way to run one over the other." +msgstr "It would be better if multiple versions are allowed, but I didn't think of the best way to run one over the other." + +#: ../../source/prototype/boltron/feedback.rst:74 +msgid "" +"It's common to need to test against a stable and development version side" +" by side." +msgstr "It's common to need to test against a stable and development version side by side." + +#: ../../source/prototype/boltron/feedback.rst:75 +msgid "" +"wondering about the case where other components might need different " +"streams of a module together (for example, openshift needs docker-1.12.6 " +"and something else needs docker-1.13, has that been accounted for? (IIUC," +" docker in this case would have 2 streams 1.12.6 and 1.13.1, is that " +"right?)" +msgstr "wondering about the case where other components might need different streams of a module together (for example, openshift needs docker-1.12.6 and something else needs docker-1.13, has that been accounted for? (IIUC, docker in this case would have 2 streams 1.12.6 and 1.13.1, is that right?)" + +#: ../../source/prototype/boltron/feedback.rst:76 +msgid "parallel installable modules (like scl?)" +msgstr "parallel installable modules (like scl?)" + +#: ../../source/prototype/boltron/feedback.rst:77 +msgid "" +"it should be possible to install several and allow easy switching, much " +"like alternatives would do" +msgstr "it should be possible to install several and allow easy switching, much like alternatives would do" + +#: ../../source/prototype/boltron/feedback.rst:78 +msgid "" +"We should have something like Software Collections, or Python virtualenv," +" i.e., streams which we can activate or de-activate at will" +msgstr "We should have something like Software Collections, or Python virtualenv, i.e., streams which we can activate or de-activate at will" + +#: ../../source/prototype/boltron/feedback.rst:79 +msgid "" +"This is hard to answer without better examples about modules. How does it" +" work with e.g., language versions? Can you parallel install two Python " +"versions like this?" +msgstr "This is hard to answer without better examples about modules. How does it work with e.g., language versions? Can you parallel install two Python versions like this?" + +#: ../../source/prototype/boltron/feedback.rst:80 +msgid "Always with \"dnf module install\" ... or configurable but not by default" +msgstr "Always with \"dnf module install\" ... or configurable but not by default" + +#: ../../source/prototype/boltron/feedback.rst:81 +msgid "" +"I'd not like to have this limitation as a design decision. I prefer if " +"tools (dnf/rpm) allow for installing packages from different streams of a" +" module simultaneously. It should fail naturally if those packages have " +"file conflicts, but if not, it should work fine." +msgstr "I'd not like to have this limitation as a design decision. I prefer if tools (dnf/rpm) allow for installing packages from different streams of a module simultaneously. It should fail naturally if those packages have file conflicts, but if not, it should work fine." + +#: ../../source/prototype/boltron/feedback.rst:82 +msgid "" +"I thought it was said you could have both apache-2.4 and 2.6 at the same " +"time in one of the examples given..." +msgstr "I thought it was said you could have both apache-2.4 and 2.6 at the same time in one of the examples given..." + +#: ../../source/prototype/boltron/feedback.rst:83 +msgid "" +"What's the purpose of differentiating if only one can be installed at a " +"time? What makes this any different than an RPM pinned to a specific " +"version?" +msgstr "What's the purpose of differentiating if only one can be installed at a time? What makes this any different than an RPM pinned to a specific version?" + +#: ../../source/prototype/boltron/feedback.rst:84 +msgid "It would be too complicated to install multiple streams in parallel." +msgstr "It would be too complicated to install multiple streams in parallel." + +#: ../../source/prototype/boltron/feedback.rst:85 +msgid "" +"If I am trying to do A-B testing.. do I need two different systems. One " +"with the new version of say wordpress-old and another with wordpress-new?" +msgstr "If I am trying to do A-B testing.. do I need two different systems. One with the new version of say wordpress-old and another with wordpress-new?" + +#: ../../source/prototype/boltron/feedback.rst:86 +msgid "" +"Ideally, the streams would be parallel installable. However, this might " +"not be technically possible in all cases. Parallel installability is " +"hard." +msgstr "Ideally, the streams would be parallel installable. However, this might not be technically possible in all cases. Parallel installability is hard." + +#: ../../source/prototype/boltron/feedback.rst:87 +msgid "" +"Ideally you would be able to do multiple streams, but for most use cases " +"it shouldn't be an issue." +msgstr "Ideally you would be able to do multiple streams, but for most use cases it shouldn't be an issue." + +#: ../../source/prototype/boltron/feedback.rst:88 +msgid "" +"it'd be nice to be able to run httpd-stable and httpd-current at the same" +" time" +msgstr "it'd be nice to be able to run httpd-stable and httpd-current at the same time" + +#: ../../source/prototype/boltron/feedback.rst:91 +msgid "How do you like using the install command to switch streams?" +msgstr "Wie würde es Ihnen gefallen, das Kommando zur Installation zum Wechseln von Streams zu verwenden?" + +#: ../../source/prototype/boltron/feedback.rst:98 +msgid "Anything else about switching streams?" +msgstr "Weitere Anmerkungen zum Wechseln von Streams?" + +#: ../../source/prototype/boltron/feedback.rst:100 +msgid "" +"Is this going to warn me that I'm switching streams? Presumably, the " +"older stream will be uninstalled, right?" +msgstr "Is this going to warn me that I'm switching streams? Presumably, the older stream will be uninstalled, right?" + +#: ../../source/prototype/boltron/feedback.rst:101 +msgid "" +"It relates to the \"One Stream\" question, if multiple streams are to be " +"installed, there should be another way." +msgstr "It relates to the \"One Stream\" question, if multiple streams are to be installed, there should be another way." + +#: ../../source/prototype/boltron/feedback.rst:102 +msgid "" +"What about version upgrade downgrade logic? If developer version is " +"installed, and switch to stable (older) version, is that a downgrade or a" +" forced switch? What about config files, .rpmnew handling etc?" +msgstr "What about version upgrade downgrade logic? If developer version is installed, and switch to stable (older) version, is that a downgrade or a forced switch? What about config files, .rpmnew handling etc?" + +#: ../../source/prototype/boltron/feedback.rst:103 +msgid "Ok if there is a clear message" +msgstr "Ok if there is a clear message" + +#: ../../source/prototype/boltron/feedback.rst:104 +msgid "" +"not required if multiple versions of modules are installable at the same " +"time" +msgstr "not required if multiple versions of modules are installable at the same time" + +#: ../../source/prototype/boltron/feedback.rst:105 +msgid "very confusing" +msgstr "very confusing" + +#: ../../source/prototype/boltron/feedback.rst:106 +msgid "install does not imply replace to me, but that is what is happening!" +msgstr "install does not imply replace to me, but that is what is happening!" + +#: ../../source/prototype/boltron/feedback.rst:107 +msgid "Being more explicit could be useful." +msgstr "Being more explicit could be useful." + +#: ../../source/prototype/boltron/feedback.rst:108 +msgid "" +"It can overwrite running modules. \"dnf module upgrade\" or \"dnf module " +"switch\" are more understandable. Keep current behaviour as it is." +msgstr "It can overwrite running modules. \"dnf module upgrade\" or \"dnf module switch\" are more understandable. Keep current behaviour as it is." + +#: ../../source/prototype/boltron/feedback.rst:109 +msgid "" +"The user might expect the new stream to be installed in addition to the " +"existing one. I'd prefer an explicit update command, e.g. dnf module " +"update" +msgstr "The user might expect the new stream to be installed in addition to the existing one. I'd prefer an explicit update command, e.g. dnf module update" + +#: ../../source/prototype/boltron/feedback.rst:110 +msgid "" +"Feel there should be a specific \"upgrade\" or \"switch\" command. " +"\"install\" could be aliased to assume an upgrade is desired in the case " +"where an older package is already installed and to prompt the user." +msgstr "Feel there should be a specific \"upgrade\" or \"switch\" command. \"install\" could be aliased to assume an upgrade is desired in the case where an older package is already installed and to prompt the user." + +#: ../../source/prototype/boltron/feedback.rst:111 +msgid "It should also be possible to do it without installing anything" +msgstr "It should also be possible to do it without installing anything" + +#: ../../source/prototype/boltron/feedback.rst:112 +msgid "" +"I would love if dnf clearly stated that the operation will result into " +"changing streams" +msgstr "I would love if dnf clearly stated that the operation will result into changing streams" + +#: ../../source/prototype/boltron/feedback.rst:113 +msgid "dnf switch-stream would be clearer and less prone to error." +msgstr "dnf switch-stream would be clearer and less prone to error." + +#: ../../source/prototype/boltron/feedback.rst:114 +msgid "" +"I think we should have a different delimiter than hyphen to indicate " +"where a name stops and a stream starts. Perhaps a colon?" +msgstr "I think we should have a different delimiter than hyphen to indicate where a name stops and a stream starts. Perhaps a colon?" + +#: ../../source/prototype/boltron/feedback.rst:115 +msgid "" +"The install subcommand makes the admin (me) believe I am going from state" +" => \"no files present\" to state => \"some files present\". There really" +" should be a stream, jump, or switch subcommand." +msgstr "The install subcommand makes the admin (me) believe I am going from state => \"no files present\" to state => \"some files present\". There really should be a stream, jump, or switch subcommand." + +#: ../../source/prototype/boltron/feedback.rst:116 +msgid "i'd like to be able to use multiple streams" +msgstr "i'd like to be able to use multiple streams" + +#: ../../source/prototype/boltron/feedback.rst:119 +msgid "How do you like that updates won't jump to another stream?" +msgstr "Wie gefällt es Ihnen, dass Updates nicht zu einem anderen Stream springen?" + +#: ../../source/prototype/boltron/feedback.rst:126 +msgid "Anything else about not jumping streams during updates?" +msgstr "Weitere Anmerkungen dazu, dass Updates nicht zu einem anderen Stream springen?" + +#: ../../source/prototype/boltron/feedback.rst:128 +msgid "Yes. What happens when a stream is EOL, though?" +msgstr "Yes. What happens when a stream is EOL, though?" + +#: ../../source/prototype/boltron/feedback.rst:129 +msgid "" +"Would like a notification that a new stream is available, even though it " +"isn't updated automatically." +msgstr "Would like a notification that a new stream is available, even though it isn't updated automatically." + +#: ../../source/prototype/boltron/feedback.rst:130 +msgid "À message about available modules" +msgstr "À message about available modules" + +#: ../../source/prototype/boltron/feedback.rst:131 +msgid "would mess the parallel/multiple simultaneous modules versions" +msgstr "would mess the parallel/multiple simultaneous modules versions" + +#: ../../source/prototype/boltron/feedback.rst:132 +msgid "It's what consumers (i.e. developers) would expect. Cool!!" +msgstr "It's what consumers (i.e. developers) would expect. Cool!!" + +#: ../../source/prototype/boltron/feedback.rst:133 +msgid "" +"Jumping automatically to a potentially incompatible version is certainly " +"not liked. It is like upgrading to next Fedora version automatically with" +" 'dnf update'. So, how you would NOT jump to the next stream?!" +msgstr "Jumping automatically to a potentially incompatible version is certainly not liked. It is like upgrading to next Fedora version automatically with 'dnf update'. So, how you would NOT jump to the next stream?!" + +#: ../../source/prototype/boltron/feedback.rst:134 +msgid "That fits in line with what I would expect." +msgstr "That fits in line with what I would expect." + +#: ../../source/prototype/boltron/feedback.rst:135 +msgid "" +"streams shouldn't be jumped during updates, but streams probably " +"shouldn't track specific software versions either" +msgstr "streams shouldn't be jumped during updates, but streams probably shouldn't track specific software versions either" + +#: ../../source/prototype/boltron/feedback.rst:138 +msgid "Is having pre-defined profiles important to you?" +msgstr "Ist es wichtig für Sie, vordefinierte Profile zu haben?" + +#: ../../source/prototype/boltron/feedback.rst:145 +msgid "" +"Is the ability to install individual packages from any module important " +"to you?" +msgstr "Ist die Möglichkeit, individuelle Pakete von jedem Modul zu installieren, von Relevanz für Sie?" + +#: ../../source/prototype/boltron/feedback.rst:152 +msgid "Anything else about profiles?" +msgstr "Weitere Anmerkungen zu Profilen?" + +#: ../../source/prototype/boltron/feedback.rst:154 +msgid "" +"Installing individual packages \"from any module\" is not important. " +"Ability to install specific individual packages from somewhere is very " +"important." +msgstr "Installing individual packages \"from any module\" is not important. Ability to install specific individual packages from somewhere is very important." + +#: ../../source/prototype/boltron/feedback.rst:155 +msgid "" +"This section need a lot of expansion. I still don't clearly understand " +"how a profile is different from a RPM metapackage." +msgstr "This section need a lot of expansion. I still don't clearly understand how a profile is different from a RPM metapackage." + +#: ../../source/prototype/boltron/feedback.rst:156 +msgid "" +"Default profile should be lean and stable during the lifecycle. Add " +"complex profiles on top." +msgstr "Default profile should be lean and stable during the lifecycle. Add complex profiles on top." + +#: ../../source/prototype/boltron/feedback.rst:157 +msgid "Is there only 1 default profile or multiple choices?" +msgstr "Is there only 1 default profile or multiple choices?" + +#: ../../source/prototype/boltron/feedback.rst:158 +msgid "" +"Define 'any module' and it might change a bit - if 'any module' means " +"anything in the universe of modules, then it's not very important. If you" +" define it to mean 'any module that you have enabled on your system' then" +" it's fairly important." +msgstr "Define 'any module' and it might change a bit - if 'any module' means anything in the universe of modules, then it's not very important. If you define it to mean 'any module that you have enabled on your system' then it's fairly important." + +#: ../../source/prototype/boltron/feedback.rst:159 +msgid "individual packages from the same stream yes" +msgstr "individual packages from the same stream yes" + +#: ../../source/prototype/boltron/feedback.rst:160 +msgid "" +"not clear on what profiles are... is this supposed to be like whether to " +"include -devel packages or something?" +msgstr "not clear on what profiles are... is this supposed to be like whether to include -devel packages or something?" + +#: ../../source/prototype/boltron/feedback.rst:163 +msgid "" +"Enabling a module first is required to install a custom set of packages " +"from the module. How do you like this functionality?" +msgstr "Die Aktivierung eines Moduls ist notwendig, bevor ein benutzerdefiniertes Set an Paketen von diesem Modul installiert werden kann. Wie gefällt Ihnen diese Funktionalität?" + +#: ../../source/prototype/boltron/feedback.rst:170 +msgid "" +"Anything else aboyut \"Enabling a module first is required to install a " +"custom set of packages from the module\"?" +msgstr "Weitere Anmerkungen dazu, dass die Aktivierung eines Moduls notwendig ist, bevor ein benutzerdefiniertes Set an Paketen von diesem Modul installiert werden kann?" + +#: ../../source/prototype/boltron/feedback.rst:172 +msgid "" +"If a package isn't available from any enabled module, but is available " +"from one or more non-enabled modules, list those modules so the user can " +"elect to enable one of them. This is like the RHEL repo conundrum (\"what" +" repo contains the package I want?)" +msgstr "If a package isn't available from any enabled module, but is available from one or more non-enabled modules, list those modules so the user can elect to enable one of them. This is like the RHEL repo conundrum (\"what repo contains the package I want?)" + +#: ../../source/prototype/boltron/feedback.rst:173 +msgid "I wish dnf to have feature like auto-enabling or suggesting modules" +msgstr "I wish dnf to have feature like auto-enabling or suggesting modules" + +#: ../../source/prototype/boltron/feedback.rst:174 +msgid "Not very clear," +msgstr "Not very clear," + +#: ../../source/prototype/boltron/feedback.rst:175 +msgid "keep the dependancy as light as possible, no bloated requirements" +msgstr "keep the dependancy as light as possible, no bloated requirements" + +#: ../../source/prototype/boltron/feedback.rst:176 +msgid "" +"For backwards compatibility, it should be possible to just install the " +"package, i.e. in its highest version available." +msgstr "For backwards compatibility, it should be possible to just install the package, i.e. in its highest version available." + +#: ../../source/prototype/boltron/feedback.rst:177 +msgid "" +"Packages should have a default module associated. A message stating which" +" module was enabled should be displayed. This will habilitate the new " +"feature to current users in a seamless way" +msgstr "Packages should have a default module associated. A message stating which module was enabled should be displayed. This will habilitate the new feature to current users in a seamless way" + +#: ../../source/prototype/boltron/feedback.rst:178 +msgid "Having no default is just annoying and just another config step" +msgstr "Having no default is just annoying and just another config step" + +#: ../../source/prototype/boltron/feedback.rst:179 +msgid "" +"Does enable mean that it gets started? What if the system isn't ready or " +"broken when started even with a default profile?" +msgstr "Does enable mean that it gets started? What if the system isn't ready or broken when started even with a default profile?" + +#: ../../source/prototype/boltron/feedback.rst:180 +msgid "" +"Its ok as long as it happens in the background. I would not like being " +"forced to execute 2 commands when I am used executing one." +msgstr "Its ok as long as it happens in the background. I would not like being forced to execute 2 commands when I am used executing one." + +#: ../../source/prototype/boltron/feedback.rst:181 +msgid "seems reasonable." +msgstr "seems reasonable." + +#: ../../source/prototype/boltron/feedback.rst:184 +msgid "How do you like the concept of a system profile?" +msgstr "Wie gefällt Ihnen das Konzept eines Systemprofils" + +#: ../../source/prototype/boltron/feedback.rst:191 +msgid "Anything else about the concept of a system profile?" +msgstr "Weitere Anmerkungen zu dem Konzept eines Systemprofils?" + +#: ../../source/prototype/boltron/feedback.rst:193 +msgid "I think this is going to be confusing to users. We'll see how it goes!" +msgstr "I think this is going to be confusing to users. We'll see how it goes!" + +#: ../../source/prototype/boltron/feedback.rst:194 +msgid "I think it should default to latest release." +msgstr "I think it should default to latest release." + +#: ../../source/prototype/boltron/feedback.rst:195 +msgid "" +"Does this imply that every package is part of a (default) module and " +"stream?" +msgstr "Does this imply that every package is part of a (default) module and stream?" + +#: ../../source/prototype/boltron/feedback.rst:196 +msgid "Use the latest stable by default" +msgstr "Use the latest stable by default" + +#: ../../source/prototype/boltron/feedback.rst:197 +msgid "A great way to define a release, I think." +msgstr "A great way to define a release, I think." + +#: ../../source/prototype/boltron/feedback.rst:198 +msgid "A default profile shall be provided. Lean and simple." +msgstr "A default profile shall be provided. Lean and simple." + +#: ../../source/prototype/boltron/feedback.rst:199 +msgid "" +"I don't understand the difference between system profiles (where " +"apparently there are defaults?) and modules (where it was stated there " +"are no defaults)." +msgstr "I don't understand the difference between system profiles (where apparently there are defaults?) and modules (where it was stated there are no defaults)." + +#: ../../source/prototype/boltron/feedback.rst:200 +msgid "Not enough info given to be useful to get what concept means" +msgstr "Not enough info given to be useful to get what concept means" + +#: ../../source/prototype/boltron/feedback.rst:201 +msgid "" +"Not quite sure what this means - is what 'dnf install httpd' means " +"different on F27 and F28 (such as those designations are relevant any " +"longer)? For example, at some point does 'dnf install httpd' mean to " +"install some future httpd-2.6? Who makes that decision? How is that " +"technically implemented?" +msgstr "Not quite sure what this means - is what 'dnf install httpd' means different on F27 and F28 (such as those designations are relevant any longer)? For example, at some point does 'dnf install httpd' mean to install some future httpd-2.6? Who makes that decision? How is that technically implemented?" + +#: ../../source/prototype/boltron/feedback.rst:204 +msgid "Anything else about Modularity?" +msgstr "Weitere Anmerkungen zu Modularity?" + +#: ../../source/prototype/boltron/feedback.rst:206 +msgid "How are package dependencies tracked/managed across steams, or are they?" +msgstr "How are package dependencies tracked/managed across steams, or are they?" + +#: ../../source/prototype/boltron/feedback.rst:207 +msgid "I'm not have good understand about modules' dependency" +msgstr "I'm not have good understand about modules' dependency" + +#: ../../source/prototype/boltron/feedback.rst:208 +msgid "" +"The message and usage is confusing. But do we really need to know the " +"difference between package and module? But what I miss is a dependency " +"graph option" +msgstr "The message and usage is confusing. But do we really need to know the difference between package and module? But what I miss is a dependency graph option" + +#: ../../source/prototype/boltron/feedback.rst:209 +msgid "" +"It's superb. Just keep the \"principle of least annoyance\" in mind when " +"making changes." +msgstr "It's superb. Just keep the \"principle of least annoyance\" in mind when making changes." + +#: ../../source/prototype/boltron/feedback.rst:210 +msgid "I really love it" +msgstr "I really love it" + +#: ../../source/prototype/boltron/feedback.rst:211 +msgid "Its not explained here how the exclusivity of streams is achieved." +msgstr "Its not explained here how the exclusivity of streams is achieved." + +#: ../../source/prototype/boltron/feedback.rst:212 +msgid "" +"Are there dependencies between modules? What happens if two different " +"modules need different versions of the same library? Can I break modules " +"by installing rpms of wrong versions? 'dnf help module' doesn't tell you " +"which sub commands can follow 'module'. Nor does 'dnf module ---help'. " +"Also 'dnf module install --help' gives you the general help for 'dnf " +"module' instead of specific help for 'dnf module install'." +msgstr "Are there dependencies between modules? What happens if two different modules need different versions of the same library? Can I break modules by installing rpms of wrong versions? 'dnf help module' doesn't tell you which sub commands can follow 'module'. Nor does 'dnf module ---help'. Also 'dnf module install --help' gives you the general help for 'dnf module' instead of specific help for 'dnf module install'." + +#: ../../source/prototype/boltron/feedback.rst:213 +msgid "" +"seems like a neat idea. if there's a clean UI & good integration with the" +" base system (services, etc) it sounds like a useful way to handle this" +msgstr "seems like a neat idea. if there's a clean UI & good integration with the base system (services, etc) it sounds like a useful way to handle this" + diff --git a/source/locale/de/LC_MESSAGES/prototype/boltron/instructions.po b/source/locale/de/LC_MESSAGES/prototype/boltron/instructions.po new file mode 100644 index 0000000..5aa31e2 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/prototype/boltron/instructions.po @@ -0,0 +1,107 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/prototype/boltron/instructions.rst:2 +msgid "Boltron Instructions" +msgstr "Instruktionen für Boltron" + +#: ../../source/prototype/boltron/instructions.rst:4 +msgid "" +"Boltron is shipped as a container image. Use the following commands to " +"pull it and run it:" +msgstr "Boltron wird ausgeliefert als Container-Image. Die folgenden Befehle werden verwendet, um es herunterzuziehen und auszuführen:" + +#: ../../source/prototype/boltron/instructions.rst:12 +msgid "Now you are ready to try Boltron!" +msgstr "Von diesem Punkt aus kann Boltron getestet werden." + +#: ../../source/prototype/boltron/instructions.rst:16 +msgid "Managing modules with DNF" +msgstr "Verwalten von Modulen mit DNF" + +#: ../../source/prototype/boltron/instructions.rst:18 +msgid "" +"You can find very similar guide on the `Walkthrough and UX Feedback " +"`__ form - and give us feedback " +"on the go." +msgstr "Eine ähnliche Anleitung findet sich in dem `Walkthrough und UX Feedback `__-Formular – hier kann uns gleichzeitig Feedback gegeben werden." + +#: ../../source/prototype/boltron/instructions.rst:23 +msgid "Listing modules" +msgstr "Auflisten von Modulen" + +#: ../../source/prototype/boltron/instructions.rst:25 +msgid "List all available modules:" +msgstr "Auflisten aller verfügbaren Module:" + +#: ../../source/prototype/boltron/instructions.rst:31 +msgid "List all installed modules:" +msgstr "Auflisten aller installierten Module:" + +#: ../../source/prototype/boltron/instructions.rst:39 +msgid "Installing modules" +msgstr "Installieren von Modulen" + +#: ../../source/prototype/boltron/instructions.rst:41 +msgid "" +"Modules are identified by name-stream-version. Each module might have one" +" or more install profiles - pre-defined sets of packages to be installed." +msgstr "Module werden identifiziert mittels eines Tripels von Name-Stream-Version. Jedes Modul besitzt möglicherweise ein oder mehrere Installationsprofile – vordefinierte Sets von installierbaren Paketen." + +#: ../../source/prototype/boltron/instructions.rst:44 +msgid "Modules can be installed by one of the following commands." +msgstr "Module können installiert werden mittels eines der folgenden Befehle:" + +#: ../../source/prototype/boltron/instructions.rst:56 +msgid "Specific examples:" +msgstr "Konkrete Beispiele:" + +#: ../../source/prototype/boltron/instructions.rst:64 +msgid "Updating the system" +msgstr "Aktualisieren des Systems" + +#: ../../source/prototype/boltron/instructions.rst:66 +msgid "" +"The system can be updated the same way as a traditional Fedora. The " +"modules will always follow their streams. That means that if you have " +"nodejs 6 (nodejs-f26) installed, it will not get upgraded to nodejs 8 " +"(nodejs-8) even when it is available." +msgstr "Das System lässt sich über den gleichen Weg aktualisieren wie ein traditionelles Fedora-System. Die Module werden immer ihren Streams folgen. Dies bedeutet, wenn man `nodejs 6` (`nodejs-f26`) installiert hat, wird es auch bei Verfügbarkeit nicht aktualisiert auf `nodejs 8` (`nodejs-8`)." + +#: ../../source/prototype/boltron/instructions.rst:76 +msgid "Changing streams" +msgstr "Wechseln der Streams" + +#: ../../source/prototype/boltron/instructions.rst:78 +msgid "" +"If you want to change a stream of an installed module, run the same " +"command as if you were installing it, specifying the stream you want to " +"change to." +msgstr "Zum Wechseln des Streams eines installierten Moduls, führt man das gleiche Kommando aus, wie bei der Installation des Moduls. Zudem wird der Stream spezifiziert, auf den man wechseln möchte." + +#: ../../source/prototype/boltron/instructions.rst:87 +msgid "How DNF keeps track what modules are installed?" +msgstr "Wie verfolgt DNF, welche Module installiert sind?" + +#: ../../source/prototype/boltron/instructions.rst:89 +msgid "DNF creates a .module file for each installed or enabled module." +msgstr "DNF erzeugt eine `.module`-Datei für jedes installierte oder aktivierte Modul." + diff --git a/source/locale/de/LC_MESSAGES/prototype/boltron/issues.po b/source/locale/de/LC_MESSAGES/prototype/boltron/issues.po new file mode 100644 index 0000000..fffe650 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/prototype/boltron/issues.po @@ -0,0 +1,103 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 23:30+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/prototype/boltron/issues.rst:2 +msgid "Known Issues" +msgstr "Bekannte Probleme" + +#: ../../source/prototype/boltron/issues.rst:4 +msgid "Please see the Modularity issue tracker below to see and report issues." +msgstr "Verwenden Sie bitte den Issue-Tracker von Modularity, um bereits gemeldete Probleme zu sehen und weitere zu melden." + +#~ msgid "" +#~ "This page tracks the known issues " +#~ "in the Boltron release. If you " +#~ "find anything that is not here, " +#~ "you can submit it into the issue" +#~ " tracker." +#~ msgstr "" + +#~ msgid "Issue tracker" +#~ msgstr "" + +#~ msgid "" +#~ "Apart from the `main modularity issue" +#~ " tracker `__, " +#~ "there are also issue trackers for " +#~ "the individual modules, available in the" +#~ " `Fedora Modularity: Modules GitHub space" +#~ " `__." +#~ msgstr "" + +#~ msgid "" +#~ "For any DNF related BZes please " +#~ "use Bugzilla. Also mind to check " +#~ "already `reported modularity DNF related " +#~ "BZes`_." +#~ msgstr "" + +#~ msgid "" +#~ "You can also use one of the " +#~ "feedback forms: :doc:`/prototype/boltron/feedback`." +#~ msgstr "" + +#~ msgid "List of known Issues" +#~ msgstr "" + +#~ msgid "DNF doesn't show some modules as installed" +#~ msgstr "" + +#~ msgid "" +#~ "This is specificaly about the `base-" +#~ "runtime`, `shared-userspace`, and `dnf` " +#~ "modules. The packages from these modules" +#~ " are avilable, but the `dnf module" +#~ " list --installed` won't list them." +#~ msgstr "" + +#~ msgid "Microdnf and rpm-ostree don't support modules" +#~ msgstr "" + +#~ msgid "" +#~ "Besides `dnf`, there are two other " +#~ "package managers in Fedora. Both " +#~ "`microdnf` and `rpm-ostree` use " +#~ "`libdnf`, which does not yet support " +#~ "modules. If you're building a container," +#~ " use the non-minimal image. A " +#~ "future version of Atomic Host's " +#~ "`rpm-ostree` package layering may support" +#~ " modules." +#~ msgstr "" + +#~ msgid "Update command is `dnf module update`, not `dnf update`" +#~ msgstr "" + +#~ msgid "" +#~ "As Boltron won't get any updates, " +#~ "the update functionality wasn't the " +#~ "biggest priority. Even with this it " +#~ "has been fully implemented client-side" +#~ " in a 'dnf module update' command." +#~ " The 'dnf update' command will work" +#~ " as expected in F27." +#~ msgstr "" + diff --git a/source/locale/de/LC_MESSAGES/usability/personas.po b/source/locale/de/LC_MESSAGES/usability/personas.po new file mode 100644 index 0000000..9670648 --- /dev/null +++ b/source/locale/de/LC_MESSAGES/usability/personas.po @@ -0,0 +1,1147 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2017, Red Hat, Inc. and others, content licensed under: +# https://creativecommons.org/licenses/by-sa/3.0/. +# This file is distributed under the same license as the Fedora Modularity +# package. +# FIRST AUTHOR , 2017. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Fedora Modularity 1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2017-11-09 16:37+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" + +#: ../../source/usability/personas.rst:2 +msgid "Personas" +msgstr "Personas" + +#: ../../source/usability/personas.rst:4 +msgid "" +"The information below relates to personas developed for the use of the " +"Modularity working group. These personas will be continually updated as " +"more information is gathered from existing users that fit these roles. " +"Also, any information provided by community members or working group team" +" members will be incorporated as well." +msgstr "The information below relates to personas developed for the use of the Modularity working group. These personas will be continually updated as more information is gathered from existing users that fit these roles. Also, any information provided by community members or working group team members will be incorporated as well." + +#: ../../source/usability/personas.rst:11 +msgid "What is a Persona" +msgstr "What is a Persona" + +#: ../../source/usability/personas.rst:13 +msgid "" +"Personas are fictional characters created to represent the different user" +" types that might interact with a product in different ways. They are not" +" market segments but should be thought of as user archetypes." +msgstr "Personas are fictional characters created to represent the different user types that might interact with a product in different ways. They are not market segments but should be thought of as user archetypes." + +#: ../../source/usability/personas.rst:17 +msgid "" +"Personas are useful in considering the goals, desires and limitations of " +"users in order to guide decisions about the product. They should be based" +" on user research and should by 1-2 page descriptions that include " +"behavior patterns, goals, skills, attitudes and environment details." +msgstr "Personas are useful in considering the goals, desires and limitations of users in order to guide decisions about the product. They should be based on user research and should by 1-2 page descriptions that include behavior patterns, goals, skills, attitudes and environment details." + +#: ../../source/usability/personas.rst:22 +msgid "" +"There should be a primary persona defined along with secondary personas. " +"More than one can be primary, but no more than 3 in order to keep the " +"team focused in their design and implementation work." +msgstr "There should be a primary persona defined along with secondary personas. More than one can be primary, but no more than 3 in order to keep the team focused in their design and implementation work." + +#: ../../source/usability/personas.rst:27 +msgid "Benefits of Personas" +msgstr "Benefits of Personas" + +#: ../../source/usability/personas.rst:29 +msgid "Common benefits include:" +msgstr "Common benefits include:" + +#: ../../source/usability/personas.rst:31 +msgid "" +"Help the team share a common understanding of their various users groups " +"and audiences" +msgstr "Help the team share a common understanding of their various users groups and audiences" + +#: ../../source/usability/personas.rst:33 +msgid "" +"Proposed designs can be guided by how well they meet the needs of certain" +" personas" +msgstr "Proposed designs can be guided by how well they meet the needs of certain personas" + +#: ../../source/usability/personas.rst:35 +msgid "" +"Features can be prioritized based on how well they address the needs of " +"one or more personas" +msgstr "Features can be prioritized based on how well they address the needs of one or more personas" + +#: ../../source/usability/personas.rst:37 +msgid "" +"Provides a human “face” to the user that can help create empathy for the " +"people represented" +msgstr "Provides a human “face” to the user that can help create empathy for the people represented" + +#: ../../source/usability/personas.rst:41 +msgid "Personas Types" +msgstr "Personas Types" + +#: ../../source/usability/personas.rst:43 +msgid "The following have been identified as the first set of personas:" +msgstr "The following have been identified as the first set of personas:" + +#: ../../source/usability/personas.rst:45 +#: ../../source/usability/personas.rst:71 +msgid "Student" +msgstr "Student" + +#: ../../source/usability/personas.rst:46 +#: ../../source/usability/personas.rst:90 +msgid "Educator" +msgstr "Educator" + +#: ../../source/usability/personas.rst:47 +#: ../../source/usability/personas.rst:107 +msgid "Researcher" +msgstr "Researcher" + +#: ../../source/usability/personas.rst:48 +msgid "IT Executive" +msgstr "IT Executive" + +#: ../../source/usability/personas.rst:49 +msgid "IT Manager" +msgstr "IT Manager" + +#: ../../source/usability/personas.rst:50 +msgid "Business Analyst" +msgstr "Business Analyst" + +#: ../../source/usability/personas.rst:51 +msgid "Enterprise System Admin" +msgstr "Enterprise System Admin" + +#: ../../source/usability/personas.rst:52 +msgid "Enterprise System Architect" +msgstr "Enterprise System Architect" + +#: ../../source/usability/personas.rst:53 +msgid "Enterprise Developer" +msgstr "Enterprise Developer" + +#: ../../source/usability/personas.rst:54 +msgid "Enterprise DevOps and Systems of Differentiation Developer" +msgstr "Enterprise DevOps and Systems of Differentiation Developer" + +#: ../../source/usability/personas.rst:55 +msgid "Enterprise DevOps Developer" +msgstr "Enterprise DevOps Developer" + +#: ../../source/usability/personas.rst:56 +msgid "" +"Enterprise and Independent Software Vendor Developer - Systems of " +"Innovation" +msgstr "Enterprise and Independent Software Vendor Developer - Systems of Innovation" + +#: ../../source/usability/personas.rst:58 +msgid "Traditional Independent Software Vendor" +msgstr "Traditional Independent Software Vendor" + +#: ../../source/usability/personas.rst:59 +msgid "Next Gen Independent Software Vendor" +msgstr "Next Gen Independent Software Vendor" + +#: ../../source/usability/personas.rst:60 +msgid "Business Operations" +msgstr "Business Operations" + +#: ../../source/usability/personas.rst:61 +msgid "Product Manager" +msgstr "Product Manager" + +#: ../../source/usability/personas.rst:68 +msgid "Detailed Information" +msgstr "Detailed Information" + +#: ../../source/usability/personas.rst:73 +#: ../../source/usability/personas.rst:92 +#: ../../source/usability/personas.rst:121 +#: ../../source/usability/personas.rst:150 +#: ../../source/usability/personas.rst:195 +#: ../../source/usability/personas.rst:245 +#: ../../source/usability/personas.rst:298 +#: ../../source/usability/personas.rst:347 +#: ../../source/usability/personas.rst:390 +#: ../../source/usability/personas.rst:442 +#: ../../source/usability/personas.rst:526 +#: ../../source/usability/personas.rst:585 +msgid "**Background**" +msgstr "**Background**" + +#: ../../source/usability/personas.rst:75 +msgid "Engineering or Computer Science student" +msgstr "Engineering or Computer Science student" + +#: ../../source/usability/personas.rst:76 +msgid "Multiple developer environment experience" +msgstr "Multiple developer environment experience" + +#: ../../source/usability/personas.rst:77 +msgid "Plays 3D games" +msgstr "Plays 3D games" + +#: ../../source/usability/personas.rst:79 +#: ../../source/usability/personas.rst:98 +#: ../../source/usability/personas.rst:128 +#: ../../source/usability/personas.rst:155 +#: ../../source/usability/personas.rst:203 +#: ../../source/usability/personas.rst:252 +#: ../../source/usability/personas.rst:306 +#: ../../source/usability/personas.rst:353 +#: ../../source/usability/personas.rst:398 +#: ../../source/usability/personas.rst:450 +#: ../../source/usability/personas.rst:468 +#: ../../source/usability/personas.rst:484 +#: ../../source/usability/personas.rst:502 +#: ../../source/usability/personas.rst:533 +#: ../../source/usability/personas.rst:594 +msgid "**Primary Goals**" +msgstr "**Primary Goals**" + +#: ../../source/usability/personas.rst:81 +msgid "Needs a personal system for software classwork and personal projects" +msgstr "Needs a personal system for software classwork and personal projects" + +#: ../../source/usability/personas.rst:82 +msgid "Software class work may require particular tool chain versions" +msgstr "Software class work may require particular tool chain versions" + +#: ../../source/usability/personas.rst:83 +msgid "To try out new versions of open source applications when released" +msgstr "To try out new versions of open source applications when released" + +#: ../../source/usability/personas.rst:84 +msgid "Play computer games" +msgstr "Play computer games" + +#: ../../source/usability/personas.rst:85 +msgid "Listen to music" +msgstr "Listen to music" + +#: ../../source/usability/personas.rst:86 +msgid "" +"Interact with friends and family through social media primarily through " +"cellphone" +msgstr "Interact with friends and family through social media primarily through cellphone" + +#: ../../source/usability/personas.rst:94 +msgid "B.A. in Education" +msgstr "B.A. in Education" + +#: ../../source/usability/personas.rst:95 +msgid "" +"15 years in academia with different roles related to teaching and " +"administration" +msgstr "15 years in academia with different roles related to teaching and administration" + +#: ../../source/usability/personas.rst:100 +msgid "Create lesson plans and make available to students, i.e., blackboard" +msgstr "Create lesson plans and make available to students, i.e., blackboard" + +#: ../../source/usability/personas.rst:101 +msgid "" +"Keep up to date with entering grades into on-line systems for " +"transparency with students" +msgstr "Keep up to date with entering grades into on-line systems for transparency with students" + +#: ../../source/usability/personas.rst:103 +msgid "Keep up with responding to emails from colleagues and students" +msgstr "Keep up with responding to emails from colleagues and students" + +#: ../../source/usability/personas.rst:104 +msgid "Create meaningful and engaging presentations" +msgstr "Create meaningful and engaging presentations" + +#: ../../source/usability/personas.rst:109 +msgid "TBD" +msgstr "TBD" + +#: ../../source/usability/personas.rst:112 +msgid "IT Executive - David" +msgstr "IT Executive - David" + +#: ../../source/usability/personas.rst:114 +msgid "*Aligns IT initiatives with business goals*" +msgstr "*Aligns IT initiatives with business goals*" + +#: ../../source/usability/personas.rst:116 +#: ../../source/usability/personas.rst:190 +#: ../../source/usability/personas.rst:237 +#: ../../source/usability/personas.rst:289 +#: ../../source/usability/personas.rst:385 +#: ../../source/usability/personas.rst:576 +msgid "**Quote**" +msgstr "**Quote**" + +#: ../../source/usability/personas.rst:118 +msgid "" +"“In this competitive market, we need to be fast, efficient, and use " +"technologies that attract developers to the company.”" +msgstr "“In this competitive market, we need to be fast, efficient, and use technologies that attract developers to the company.”" + +#: ../../source/usability/personas.rst:123 +#: ../../source/usability/personas.rst:152 +#: ../../source/usability/personas.rst:349 +msgid "BS in Computer Science" +msgstr "BS in Computer Science" + +#: ../../source/usability/personas.rst:124 +msgid "30 years experience" +msgstr "30 years experience" + +#: ../../source/usability/personas.rst:125 +msgid "15 years of management experience" +msgstr "15 years of management experience" + +#: ../../source/usability/personas.rst:126 +msgid "Advanced analytical skills" +msgstr "Advanced analytical skills" + +#: ../../source/usability/personas.rst:130 +msgid "Improve IT operations, system performance, and risk management" +msgstr "Improve IT operations, system performance, and risk management" + +#: ../../source/usability/personas.rst:131 +msgid "Implements new systems/architecture" +msgstr "Implements new systems/architecture" + +#: ../../source/usability/personas.rst:132 +msgid "Cultivates IT and business partnerships" +msgstr "Cultivates IT and business partnerships" + +#: ../../source/usability/personas.rst:133 +msgid "Sell IT solutions internally" +msgstr "Sell IT solutions internally" + +#: ../../source/usability/personas.rst:134 +msgid "" +"Selects vendors that can meet his/her challenges. Convinces c-suite peers" +" to adopt the chosen vendor." +msgstr "Selects vendors that can meet his/her challenges. Convinces c-suite peers to adopt the chosen vendor." + +#: ../../source/usability/personas.rst:137 +#: ../../source/usability/personas.rst:165 +#: ../../source/usability/personas.rst:209 +#: ../../source/usability/personas.rst:263 +#: ../../source/usability/personas.rst:316 +#: ../../source/usability/personas.rst:359 +#: ../../source/usability/personas.rst:409 +#: ../../source/usability/personas.rst:456 +#: ../../source/usability/personas.rst:474 +#: ../../source/usability/personas.rst:492 +#: ../../source/usability/personas.rst:515 +#: ../../source/usability/personas.rst:546 +#: ../../source/usability/personas.rst:608 +msgid "**Pain Points**" +msgstr "**Pain Points**" + +#: ../../source/usability/personas.rst:139 +msgid "" +"Provide security while focusing on efficiency, mobility, innovation, and " +"downtime" +msgstr "Provide security while focusing on efficiency, mobility, innovation, and downtime" + +#: ../../source/usability/personas.rst:141 +msgid "" +"Doing more with less budget, skills, staff, financial transparency and " +"time" +msgstr "Doing more with less budget, skills, staff, financial transparency and time" + +#: ../../source/usability/personas.rst:143 +msgid "Reducing server footprint while expanding services" +msgstr "Reducing server footprint while expanding services" + +#: ../../source/usability/personas.rst:146 +msgid "IT Manager - Stan" +msgstr "IT Manager - Stan" + +#: ../../source/usability/personas.rst:148 +msgid "*Manages team that oversees infrastructure components*" +msgstr "*Manages team that oversees infrastructure components*" + +#: ../../source/usability/personas.rst:153 +#: ../../source/usability/personas.rst:248 +msgid "15 years experience" +msgstr "15 years experience" + +#: ../../source/usability/personas.rst:157 +msgid "Determine execution plans for specific IT objectives" +msgstr "Determine execution plans for specific IT objectives" + +#: ../../source/usability/personas.rst:158 +msgid "Select solutions for the objectives and budgets specified by IT Executive" +msgstr "Select solutions for the objectives and budgets specified by IT Executive" + +#: ../../source/usability/personas.rst:160 +msgid "" +"Make decisions for smaller, tactical purchases and influence larger " +"purchases" +msgstr "Make decisions for smaller, tactical purchases and influence larger purchases" + +#: ../../source/usability/personas.rst:162 +msgid "Ensures reliable, 24x7 operations of existing infrastructures" +msgstr "Ensures reliable, 24x7 operations of existing infrastructures" + +#: ../../source/usability/personas.rst:163 +msgid "Identifies paths to resolution when issues arise" +msgstr "Identifies paths to resolution when issues arise" + +#: ../../source/usability/personas.rst:167 +msgid "Doing more with less resources" +msgstr "Doing more with less resources" + +#: ../../source/usability/personas.rst:168 +msgid "Getting the blame when things go wrong" +msgstr "Getting the blame when things go wrong" + +#: ../../source/usability/personas.rst:169 +msgid "" +"Handling staffing issues (not having people trained in the skills and " +"capabilities required)" +msgstr "Handling staffing issues (not having people trained in the skills and capabilities required)" + +#: ../../source/usability/personas.rst:171 +msgid "Meeting regulatory and security compliance" +msgstr "Meeting regulatory and security compliance" + +#: ../../source/usability/personas.rst:173 +#: ../../source/usability/personas.rst:218 +#: ../../source/usability/personas.rst:271 +#: ../../source/usability/personas.rst:325 +#: ../../source/usability/personas.rst:366 +#: ../../source/usability/personas.rst:418 +#: ../../source/usability/personas.rst:551 +#: ../../source/usability/personas.rst:616 +msgid "**A Day in the Life**" +msgstr "**A Day in the Life**" + +#: ../../source/usability/personas.rst:175 +msgid "" +"Stan starts his day before arriving in the office by checking email and " +"making note of any issues that have arisen over night. Anything that " +"needs his immediate attention can be handled through email and requests " +"to others to get started on solutions. After getting to the office, he " +"touch base with his manager to make sure we are in sync for the day. Then" +" he has a quick meeting with his team to make sure they know the goals " +"and issues to be addressed that have come up over night. Most of the rest" +" of his day is spent putting out fires, dealing with email and sitting in" +" project meetings." +msgstr "Stan starts his day before arriving in the office by checking email and making note of any issues that have arisen over night. Anything that needs his immediate attention can be handled through email and requests to others to get started on solutions. After getting to the office, he touch base with his manager to make sure we are in sync for the day. Then he has a quick meeting with his team to make sure they know the goals and issues to be addressed that have come up over night. Most of the rest of his day is spent putting out fires, dealing with email and sitting in project meetings." + +#: ../../source/usability/personas.rst:186 +msgid "Business Analyst - Karen" +msgstr "Business Analyst - Karen" + +#: ../../source/usability/personas.rst:188 +msgid "*Identifies the need for changing how the company works*" +msgstr "*Identifies the need for changing how the company works*" + +#: ../../source/usability/personas.rst:192 +msgid "" +"“In my job I need to be a master multi-tasker. I love that there is " +"constant change and that every day is different.”" +msgstr "“In my job I need to be a master multi-tasker. I love that there is constant change and that every day is different.”" + +#: ../../source/usability/personas.rst:197 +msgid "BS in Business or Management" +msgstr "BS in Business or Management" + +#: ../../source/usability/personas.rst:198 +#: ../../source/usability/personas.rst:393 +#: ../../source/usability/personas.rst:445 +msgid "10 years experience" +msgstr "10 years experience" + +#: ../../source/usability/personas.rst:199 +msgid "Strong written and communication skills" +msgstr "Strong written and communication skills" + +#: ../../source/usability/personas.rst:200 +msgid "Strong analytical and conceptual skills" +msgstr "Strong analytical and conceptual skills" + +#: ../../source/usability/personas.rst:201 +msgid "Working knowledge of software development processes" +msgstr "Working knowledge of software development processes" + +#: ../../source/usability/personas.rst:205 +msgid "Be a change agent for the company" +msgstr "Be a change agent for the company" + +#: ../../source/usability/personas.rst:206 +msgid "Successfully broker change between company stakeholders and IT" +msgstr "Successfully broker change between company stakeholders and IT" + +#: ../../source/usability/personas.rst:207 +msgid "Be on top of industry trends to know when change may be needed" +msgstr "Be on top of industry trends to know when change may be needed" + +#: ../../source/usability/personas.rst:211 +msgid "Managing urgencies, crises, and timelines" +msgstr "Managing urgencies, crises, and timelines" + +#: ../../source/usability/personas.rst:212 +msgid "" +"Expectation that better outcomes can be achieved faster with new analysis" +" and technology" +msgstr "Expectation that better outcomes can be achieved faster with new analysis and technology" + +#: ../../source/usability/personas.rst:214 +msgid "" +"Difficult to achieve organizational and cultural changes necessary to " +"implement some solutions" +msgstr "Difficult to achieve organizational and cultural changes necessary to implement some solutions" + +#: ../../source/usability/personas.rst:216 +msgid "An ever increasing pace of change in the marketplace" +msgstr "An ever increasing pace of change in the marketplace" + +#: ../../source/usability/personas.rst:220 +msgid "" +"Karen starts her day by checking email and reading the latest articles " +"from her feeds. Ideally, she can spend a few hours in the morning going " +"through industry trend documents and identifying potential items that can" +" be leveraged. Most days however, get full of stakeholder meetings and " +"project meetings where she helps to keep things on track and making sure " +"the business objectives are still going to be achieved." +msgstr "Karen starts her day by checking email and reading the latest articles from her feeds. Ideally, she can spend a few hours in the morning going through industry trend documents and identifying potential items that can be leveraged. Most days however, get full of stakeholder meetings and project meetings where she helps to keep things on track and making sure the business objectives are still going to be achieved." + +#: ../../source/usability/personas.rst:227 +msgid "" +"In the afternoon, her goals are to write up proposal and plans. She also " +"prefers to spend at least one hour looking through the data to support " +"upcoming proposals and making sure that they still make sense for the " +"business." +msgstr "In the afternoon, her goals are to write up proposal and plans. She also prefers to spend at least one hour looking through the data to support upcoming proposals and making sure that they still make sense for the business." + +#: ../../source/usability/personas.rst:233 +msgid "Enterprise System Administrator - Yvonne" +msgstr "Enterprise System Administrator - Yvonne" + +#: ../../source/usability/personas.rst:235 +msgid "*Ensure current IT infrastructure works seamlessly*" +msgstr "*Ensure current IT infrastructure works seamlessly*" + +#: ../../source/usability/personas.rst:239 +msgid "" +"“What people don’t realize is that being an System Administrator is a " +"24/7 job. There is a constant stream of emails with requests and issues " +"from all fronts and you really have to know how to prioritize and triage " +"effectively to be successful at this job. It is definitely not for " +"everyone, but I enjoy the pace and the constant challenge.”" +msgstr "“What people don’t realize is that being an System Administrator is a 24/7 job. There is a constant stream of emails with requests and issues from all fronts and you really have to know how to prioritize and triage effectively to be successful at this job. It is definitely not for everyone, but I enjoy the pace and the constant challenge.”" + +#: ../../source/usability/personas.rst:247 +#: ../../source/usability/personas.rst:300 +#: ../../source/usability/personas.rst:392 +#: ../../source/usability/personas.rst:444 +#: ../../source/usability/personas.rst:587 +msgid "B.S. in Computer Science" +msgstr "B.S. in Computer Science" + +#: ../../source/usability/personas.rst:249 +msgid "Shell script expert" +msgstr "Shell script expert" + +#: ../../source/usability/personas.rst:250 +msgid "Good at putting all the parts together" +msgstr "Good at putting all the parts together" + +#: ../../source/usability/personas.rst:254 +msgid "" +"Suggest useful, secure and flexible tools that can be adopted by the " +"organization to achieve day-to-day tasks" +msgstr "Suggest useful, secure and flexible tools that can be adopted by the organization to achieve day-to-day tasks" + +#: ../../source/usability/personas.rst:256 +msgid "" +"Make sure upgrades and new deployments are smooth with little to no " +"downtime" +msgstr "Make sure upgrades and new deployments are smooth with little to no downtime" + +#: ../../source/usability/personas.rst:258 +msgid "Be a reliable source of information for co-workers and users" +msgstr "Be a reliable source of information for co-workers and users" + +#: ../../source/usability/personas.rst:259 +msgid "Unified management of server resources" +msgstr "Unified management of server resources" + +#: ../../source/usability/personas.rst:260 +msgid "" +"Ability to understand resource usage across server inventory to identify " +"underutilized resources" +msgstr "Ability to understand resource usage across server inventory to identify underutilized resources" + +#: ../../source/usability/personas.rst:265 +msgid "Constant interruptions" +msgstr "Constant interruptions" + +#: ../../source/usability/personas.rst:266 +msgid "Having to be available 24/7 depending on the issue" +msgstr "Having to be available 24/7 depending on the issue" + +#: ../../source/usability/personas.rst:267 +msgid "Stress due to picking the right technology" +msgstr "Stress due to picking the right technology" + +#: ../../source/usability/personas.rst:268 +msgid "Proliferation of various management console interfaces to have to manage" +msgstr "Proliferation of various management console interfaces to have to manage" + +#: ../../source/usability/personas.rst:273 +msgid "" +"Yvonne starts her day by checking email before she even gets out of bed " +"to make sure there were no failures overnight and there are no fires that" +" can’t wait until she gets to the office. Once satisfied that all is " +"well, she gets ready, takes care of her family and heads into the office." +" Upon arriving at the office, she makes a pot of coffee and again checks " +"her email. Her priorities include correcting any issues that are stopping" +" others from working and escalating anything that she cannot work on " +"herself. Yvonne then checks in with her supervisor on the day's " +"activities, checks on any hardware deliveries and communicates with co-" +"workers on overall system status." +msgstr "Yvonne starts her day by checking email before she even gets out of bed to make sure there were no failures overnight and there are no fires that can’t wait until she gets to the office. Once satisfied that all is well, she gets ready, takes care of her family and heads into the office. Upon arriving at the office, she makes a pot of coffee and again checks her email. Her priorities include correcting any issues that are stopping others from working and escalating anything that she cannot work on herself. Yvonne then checks in with her supervisor on the day's activities, checks on any hardware deliveries and communicates with co-workers on overall system status." + +#: ../../source/usability/personas.rst:285 +msgid "Enterprise System Architect - Kevin" +msgstr "Enterprise System Architect - Kevin" + +#: ../../source/usability/personas.rst:287 +msgid "*Links the business mission, strategy and processes to the IT strategy*" +msgstr "*Links the business mission, strategy and processes to the IT strategy*" + +#: ../../source/usability/personas.rst:291 +msgid "" +"“I love my job...I am one of a few who get to work strategically with " +"Leadership and still maintain a technological connection to the product. " +"Exploring new technologies and innovations and figuring out how our " +"product can benefit is one of my favorite aspects of the job. It can be " +"very stressful and demanding, but that is how I know I am making a " +"difference to my team, product and company.”" +msgstr "“I love my job...I am one of a few who get to work strategically with Leadership and still maintain a technological connection to the product. Exploring new technologies and innovations and figuring out how our product can benefit is one of my favorite aspects of the job. It can be very stressful and demanding, but that is how I know I am making a difference to my team, product and company.”" + +#: ../../source/usability/personas.rst:301 +msgid "25 years experience" +msgstr "25 years experience" + +#: ../../source/usability/personas.rst:302 +msgid "Expert skills in software design and testing; Agile" +msgstr "Expert skills in software design and testing; Agile" + +#: ../../source/usability/personas.rst:303 +msgid "Knows Java, JavaScript, C, C++, HTML5 and CSS" +msgstr "Knows Java, JavaScript, C, C++, HTML5 and CSS" + +#: ../../source/usability/personas.rst:304 +msgid "Uses Eclipse IDE" +msgstr "Uses Eclipse IDE" + +#: ../../source/usability/personas.rst:308 +msgid "To set strategic goals through collaboration with senior leadership." +msgstr "To set strategic goals through collaboration with senior leadership." + +#: ../../source/usability/personas.rst:309 +msgid "Ensure the overall integrity of the application." +msgstr "Ensure the overall integrity of the application." + +#: ../../source/usability/personas.rst:310 +msgid "Document and communicate industry trends and a roadmap for implementing." +msgstr "Document and communicate industry trends and a roadmap for implementing." + +#: ../../source/usability/personas.rst:312 +msgid "High-level understanding of the entire system." +msgstr "High-level understanding of the entire system." + +#: ../../source/usability/personas.rst:313 +msgid "" +"Responsible for selecting systems and specifying deployment lifecycles " +"and system configuration." +msgstr "Responsible for selecting systems and specifying deployment lifecycles and system configuration." + +#: ../../source/usability/personas.rst:318 +msgid "Constantly need to sell ideas that may result in deadline changes." +msgstr "Constantly need to sell ideas that may result in deadline changes." + +#: ../../source/usability/personas.rst:319 +msgid "Not enough resources to keep things as current as needed." +msgstr "Not enough resources to keep things as current as needed." + +#: ../../source/usability/personas.rst:320 +msgid "" +"No authority to make things happen; always negotiating between timeline, " +"budget and technology." +msgstr "No authority to make things happen; always negotiating between timeline, budget and technology." + +#: ../../source/usability/personas.rst:322 +msgid "" +"Spend a lot of time documenting requirements, needs and trends in order " +"to communicate to all stakeholders." +msgstr "Spend a lot of time documenting requirements, needs and trends in order to communicate to all stakeholders." + +#: ../../source/usability/personas.rst:327 +msgid "" +"Kevin starts his day by catching up on his feeds related to security, " +"serviceability and other industry trends to make sure he is aware of new " +"ideas. He then has his daily standups with the dev teams and meets one on" +" one with team members that have issues or that he needs to ask questions" +" of." +msgstr "Kevin starts his day by catching up on his feeds related to security, serviceability and other industry trends to make sure he is aware of new ideas. He then has his daily standups with the dev teams and meets one on one with team members that have issues or that he needs to ask questions of." + +#: ../../source/usability/personas.rst:333 +msgid "" +"Kevin spends the majority of his afternoon documenting the roadmap and " +"evaluating options to determine if they meet feature requests/needs and " +"how they fit into his strategies to meet enterprise compliance. Once a " +"week, he meets with Senior Leadership to report on progress as well as " +"identify any recommended changes to direction that he has. If leadership " +"has issues with his recommendations, he needs to wrap back around and " +"come up with other alternatives or bolster his arguments for proceeding " +"with his original recommendation." +msgstr "Kevin spends the majority of his afternoon documenting the roadmap and evaluating options to determine if they meet feature requests/needs and how they fit into his strategies to meet enterprise compliance. Once a week, he meets with Senior Leadership to report on progress as well as identify any recommended changes to direction that he has. If leadership has issues with his recommendations, he needs to wrap back around and come up with other alternatives or bolster his arguments for proceeding with his original recommendation." + +#: ../../source/usability/personas.rst:343 +msgid "Enterprise Developer - Rajiv" +msgstr "Enterprise Developer - Rajiv" + +#: ../../source/usability/personas.rst:345 +msgid "*Design and implement code*" +msgstr "*Design and implement code*" + +#: ../../source/usability/personas.rst:350 +msgid "8 years of experience" +msgstr "8 years of experience" + +#: ../../source/usability/personas.rst:351 +msgid "Java, Javascript, CSS, MVC frameworks, github" +msgstr "Java, Javascript, CSS, MVC frameworks, github" + +#: ../../source/usability/personas.rst:355 +#: ../../source/usability/personas.rst:452 +#: ../../source/usability/personas.rst:470 +msgid "To design and implement code" +msgstr "To design and implement code" + +#: ../../source/usability/personas.rst:356 +#: ../../source/usability/personas.rst:453 +#: ../../source/usability/personas.rst:471 +msgid "To leverage the best tools for the job" +msgstr "To leverage the best tools for the job" + +#: ../../source/usability/personas.rst:357 +#: ../../source/usability/personas.rst:454 +#: ../../source/usability/personas.rst:472 +msgid "To complete tasks in as efficient and timely manner as possible" +msgstr "To complete tasks in as efficient and timely manner as possible" + +#: ../../source/usability/personas.rst:361 +#: ../../source/usability/personas.rst:458 +#: ../../source/usability/personas.rst:476 +msgid "Not having enough time to complete tasks required" +msgstr "Not having enough time to complete tasks required" + +#: ../../source/usability/personas.rst:362 +msgid "" +"Being restricted by existing resources/tools that don’t enable the " +"ability to deliver new functionality" +msgstr "Being restricted by existing resources/tools that don’t enable the ability to deliver new functionality" + +#: ../../source/usability/personas.rst:364 +#: ../../source/usability/personas.rst:461 +#: ../../source/usability/personas.rst:479 +msgid "Too much bureaucracy in the organization" +msgstr "Too much bureaucracy in the organization" + +#: ../../source/usability/personas.rst:368 +msgid "" +"When Rajiv gets to the office he spends a few minutes catching up on his " +"feeds and checking email. Then he participates in his team’s standup " +"meeting and sets up some time with a coworker who he needs help from to " +"complete his story. Until he can meet with him, Rajiv works on fixing " +"bugs that have been found. Late morning, Rajiv has two project meetings " +"to attend and then has his quick meeting to unblock his story." +msgstr "When Rajiv gets to the office he spends a few minutes catching up on his feeds and checking email. Then he participates in his team’s standup meeting and sets up some time with a coworker who he needs help from to complete his story. Until he can meet with him, Rajiv works on fixing bugs that have been found. Late morning, Rajiv has two project meetings to attend and then has his quick meeting to unblock his story." + +#: ../../source/usability/personas.rst:375 +msgid "" +"After lunch, Rajiv finishes his story and starts on the next one in his " +"backlog. Usually there are additional bugs that get filed throughout the " +"afternoon so he reserves the last hour and half to work on those before " +"heading home." +msgstr "After lunch, Rajiv finishes his story and starts on the next one in his backlog. Usually there are additional bugs that get filed throughout the afternoon so he reserves the last hour and half to work on those before heading home." + +#: ../../source/usability/personas.rst:381 +msgid "Enterprise DevOps Developer - Devin" +msgstr "Enterprise DevOps Developer - Devin" + +#: ../../source/usability/personas.rst:383 +msgid "*Continuous integration/Continuous delivery*" +msgstr "*Continuous integration/Continuous delivery*" + +#: ../../source/usability/personas.rst:387 +msgid "" +"“Some folks think I’m a sys admin, others think I’m a coder. The truth " +"is, I’m both and a lot more!”" +msgstr "“Some folks think I’m a sys admin, others think I’m a coder. The truth is, I’m both and a lot more!”" + +#: ../../source/usability/personas.rst:394 +#: ../../source/usability/personas.rst:446 +msgid "Skilled in IT operations and software testing" +msgstr "Skilled in IT operations and software testing" + +#: ../../source/usability/personas.rst:395 +#: ../../source/usability/personas.rst:447 +msgid "Specializes in Java as well as Python and Perl" +msgstr "Specializes in Java as well as Python and Perl" + +#: ../../source/usability/personas.rst:396 +#: ../../source/usability/personas.rst:448 +msgid "Uses Jenkins and Ansible" +msgstr "Uses Jenkins and Ansible" + +#: ../../source/usability/personas.rst:400 +msgid "" +"Ensuring that all applications migrate smoothly throughout the entire " +"lifecycle, from the development process to production support." +msgstr "Ensuring that all applications migrate smoothly throughout the entire lifecycle, from the development process to production support." + +#: ../../source/usability/personas.rst:402 +msgid "" +"Ensuring that the automation process works efficiently among the team: " +"developers who implement features, system administrators who manage " +"access control, and operators who monitor the applications and servers." +msgstr "Ensuring that the automation process works efficiently among the team: developers who implement features, system administrators who manage access control, and operators who monitor the applications and servers." + +#: ../../source/usability/personas.rst:406 +msgid "" +"Identifying the root cause of problems in test, staging and production " +"environments, as well as the infrastructure." +msgstr "Identifying the root cause of problems in test, staging and production environments, as well as the infrastructure." + +#: ../../source/usability/personas.rst:411 +msgid "" +"Multiple tools, integration points, incompatibilities, and problems with " +"PaaS and IaaS create many obstacles." +msgstr "Multiple tools, integration points, incompatibilities, and problems with PaaS and IaaS create many obstacles." + +#: ../../source/usability/personas.rst:413 +msgid "" +"When a build cannot pass the tests, a lot of time is spent looking for " +"the team members who are responsible for the build or the specific " +"feature that is causing a problem. This is exacerbated when he does not " +"know the responsibilities of certain people on the team." +msgstr "When a build cannot pass the tests, a lot of time is spent looking for the team members who are responsible for the build or the specific feature that is causing a problem. This is exacerbated when he does not know the responsibilities of certain people on the team." + +#: ../../source/usability/personas.rst:420 +msgid "" +"Devin starts his workday by checking on the status of the overnight " +"builds. One build failed miserably, so his first order of business is to " +"find out why. After he figures out which component appeared to cause the " +"problem, he opens a Severity 1 ticket on that component so the " +"responsible developer will be notified immediately. Devin gets an " +"automated out-of-office notification from that developer, so he has to " +"inspect and fix the code himself, and then kick-off the test of the build" +" again." +msgstr "Devin starts his workday by checking on the status of the overnight builds. One build failed miserably, so his first order of business is to find out why. After he figures out which component appeared to cause the problem, he opens a Severity 1 ticket on that component so the responsible developer will be notified immediately. Devin gets an automated out-of-office notification from that developer, so he has to inspect and fix the code himself, and then kick-off the test of the build again." + +#: ../../source/usability/personas.rst:429 +msgid "" +"Because of the unexpected issue, Devin arrives late to the weekly DevOps " +"meeting with his team of developers, quality engineers, and product " +"managers. The main topic is the decreasing availability and performance " +"of the deployment system, so they need to plan for a more scalable and " +"performant solution. After this, he completes his daily status report " +"about the CI/CD pipeline to the engineering management team. Once that is" +" sent, Devin, intermittently coordinates work among his team members in " +"between the moments he gets to modify the scripts that orchestrate the " +"complete deployment of development, QA, and production environments." +msgstr "Because of the unexpected issue, Devin arrives late to the weekly DevOps meeting with his team of developers, quality engineers, and product managers. The main topic is the decreasing availability and performance of the deployment system, so they need to plan for a more scalable and performant solution. After this, he completes his daily status report about the CI/CD pipeline to the engineering management team. Once that is sent, Devin, intermittently coordinates work among his team members in between the moments he gets to modify the scripts that orchestrate the complete deployment of development, QA, and production environments." + +#: ../../source/usability/personas.rst:440 +msgid "" +"Enterprise DevOps Developer and Systems of Differentiation Developer - " +"Ryan" +msgstr "Enterprise DevOps Developer and Systems of Differentiation Developer - Ryan" + +#: ../../source/usability/personas.rst:459 +#: ../../source/usability/personas.rst:477 +msgid "" +"Being restricted by existing resources/tools that don’t enable him to " +"deliver new functionality" +msgstr "Being restricted by existing resources/tools that don’t enable him to deliver new functionality" + +#: ../../source/usability/personas.rst:464 +msgid "Enterprise and ISV Developer - Systems of Innovation - Ben" +msgstr "Enterprise and ISV Developer - Systems of Innovation - Ben" + +#: ../../source/usability/personas.rst:466 +msgid "*Design and Implement Code*" +msgstr "*Design and Implement Code*" + +#: ../../source/usability/personas.rst:482 +msgid "Traditional ISV" +msgstr "Traditional ISV" + +#: ../../source/usability/personas.rst:486 +#: ../../source/usability/personas.rst:504 +msgid "To build, develop and sell consumer or enterprise software" +msgstr "To build, develop and sell consumer or enterprise software" + +#: ../../source/usability/personas.rst:487 +#: ../../source/usability/personas.rst:505 +msgid "Partner with platform providers to sell more software" +msgstr "Partner with platform providers to sell more software" + +#: ../../source/usability/personas.rst:488 +#: ../../source/usability/personas.rst:506 +msgid "Ensure customers are satisfied and their needs are being met" +msgstr "Ensure customers are satisfied and their needs are being met" + +#: ../../source/usability/personas.rst:489 +#: ../../source/usability/personas.rst:507 +msgid "" +"Work with multiple teams including partner, customer and internal to " +"address issues and concerns" +msgstr "Work with multiple teams including partner, customer and internal to address issues and concerns" + +#: ../../source/usability/personas.rst:494 +#: ../../source/usability/personas.rst:517 +msgid "Different customers have different requirements that can be conflicting" +msgstr "Different customers have different requirements that can be conflicting" + +#: ../../source/usability/personas.rst:496 +#: ../../source/usability/personas.rst:519 +msgid "There is always something that needs to be corrected" +msgstr "There is always something that needs to be corrected" + +#: ../../source/usability/personas.rst:497 +msgid "Can’t ship on a quick enough schedule to satisfy the customer base" +msgstr "Can’t ship on a quick enough schedule to satisfy the customer base" + +#: ../../source/usability/personas.rst:500 +msgid "Next-Gen ISV" +msgstr "Next-Gen ISV" + +#: ../../source/usability/personas.rst:509 +msgid "To ship apps faster" +msgstr "To ship apps faster" + +#: ../../source/usability/personas.rst:510 +msgid "To leverage containers and other emerging technologies as soon as possible" +msgstr "To leverage containers and other emerging technologies as soon as possible" + +#: ../../source/usability/personas.rst:512 +msgid "Multi-modal development" +msgstr "Multi-modal development" + +#: ../../source/usability/personas.rst:513 +msgid "SaaS model first, then deploy in organization" +msgstr "SaaS model first, then deploy in organization" + +#: ../../source/usability/personas.rst:522 +msgid "Business Operations - Isaac" +msgstr "Business Operations - Isaac" + +#: ../../source/usability/personas.rst:524 +msgid "*Management of the Operations Team*" +msgstr "*Management of the Operations Team*" + +#: ../../source/usability/personas.rst:528 +msgid "B.S. in Information Systems" +msgstr "B.S. in Information Systems" + +#: ../../source/usability/personas.rst:529 +msgid "8 years experience - Cloud Services (IaaS, PaaS, SaaS)" +msgstr "8 years experience - Cloud Services (IaaS, PaaS, SaaS)" + +#: ../../source/usability/personas.rst:530 +msgid "Specializes in Java, Python; knows C, C++" +msgstr "Specializes in Java, Python; knows C, C++" + +#: ../../source/usability/personas.rst:531 +msgid "Expert knowledge of UNIX, LINUX and Windows" +msgstr "Expert knowledge of UNIX, LINUX and Windows" + +#: ../../source/usability/personas.rst:535 +msgid "" +"Ensuring successful day-to-day operations of the technology " +"infrastructure and that all Service Level Agreements (SLA) with customers" +" are met, and creating plans and providing support for instances when an " +"SLA is compromised." +msgstr "Ensuring successful day-to-day operations of the technology infrastructure and that all Service Level Agreements (SLA) with customers are met, and creating plans and providing support for instances when an SLA is compromised." + +#: ../../source/usability/personas.rst:539 +msgid "" +"Quickly receiving and reviewing real-time reports of critical SLA " +"criteria: availability, system response times, security/privacy, disaster" +" recovery time, call center resolution time, dispute mediation, and " +"change management." +msgstr "Quickly receiving and reviewing real-time reports of critical SLA criteria: availability, system response times, security/privacy, disaster recovery time, call center resolution time, dispute mediation, and change management." + +#: ../../source/usability/personas.rst:543 +msgid "" +"Scheduling, budgeting, and staffing system maintenance and upgrades to " +"ensure maximum operational performance." +msgstr "Scheduling, budgeting, and staffing system maintenance and upgrades to ensure maximum operational performance." + +#: ../../source/usability/personas.rst:548 +msgid "" +"Technological and financial limitations make it very challenging to " +"migrate legacy applications to the cloud" +msgstr "Technological and financial limitations make it very challenging to migrate legacy applications to the cloud" + +#: ../../source/usability/personas.rst:553 +msgid "" +"The first order of business for Isaac is to review the reports of system " +"operations from the previous day. He’s especially interested in the " +"availability numbers because a big software upgrade was applied to a few " +"servers overnight. Fortunately, system availability was not affected, and" +" the upgrade should improve the numbers for system response time, so it " +"was a win-win for customers and Isaac, who constantly keeps his eye on " +"the SLA commitments." +msgstr "The first order of business for Isaac is to review the reports of system operations from the previous day. He’s especially interested in the availability numbers because a big software upgrade was applied to a few servers overnight. Fortunately, system availability was not affected, and the upgrade should improve the numbers for system response time, so it was a win-win for customers and Isaac, who constantly keeps his eye on the SLA commitments." + +#: ../../source/usability/personas.rst:561 +msgid "" +"Afterwards, Isaac attends a meeting with his staff to discuss the exit " +"strategy plan for a customer who will be leaving their service at the end" +" of the month. A smooth transition is a must." +msgstr "Afterwards, Isaac attends a meeting with his staff to discuss the exit strategy plan for a customer who will be leaving their service at the end of the month. A smooth transition is a must." + +#: ../../source/usability/personas.rst:565 +msgid "" +"Isaac then has a series of meetings with the technical leads on his staff" +" to discuss proposals for rolling out new server hardware during the next" +" quarter. He needs to balance capacity and performance with the tight " +"budget he’s been given for expansion, so he needs lots of details so he " +"can evaluate and select from the multiple options on the table." +msgstr "Isaac then has a series of meetings with the technical leads on his staff to discuss proposals for rolling out new server hardware during the next quarter. He needs to balance capacity and performance with the tight budget he’s been given for expansion, so he needs lots of details so he can evaluate and select from the multiple options on the table." + +#: ../../source/usability/personas.rst:572 +msgid "Product Manager - Pablo" +msgstr "Product Manager - Pablo" + +#: ../../source/usability/personas.rst:574 +msgid "*Customer and industry liaison to the product and the company*" +msgstr "*Customer and industry liaison to the product and the company*" + +#: ../../source/usability/personas.rst:578 +msgid "" +"“A lot of my time is spent gathering resources, coordinating various " +"teams to agree on decisions or work to achieve customer goals. I need to " +"spend more time distilling down ideas and driving agreement across " +"disparate teams. My role is about working with other to build the grand " +"plan. Improving communication, clarity on commitment and direction, would" +" result in more timely decision making.”" +msgstr "“A lot of my time is spent gathering resources, coordinating various teams to agree on decisions or work to achieve customer goals. I need to spend more time distilling down ideas and driving agreement across disparate teams. My role is about working with other to build the grand plan. Improving communication, clarity on commitment and direction, would result in more timely decision making.”" + +#: ../../source/usability/personas.rst:588 +msgid "" +"5+ years experience, including project management + software development " +"environment" +msgstr "5+ years experience, including project management + software development environment" + +#: ../../source/usability/personas.rst:590 +msgid "Deliver multiple projects, cross-functionally" +msgstr "Deliver multiple projects, cross-functionally" + +#: ../../source/usability/personas.rst:591 +msgid "Expert planner with business process definition" +msgstr "Expert planner with business process definition" + +#: ../../source/usability/personas.rst:592 +msgid "Influencer in org up to SVP with more experience" +msgstr "Influencer in org up to SVP with more experience" + +#: ../../source/usability/personas.rst:596 +msgid "Understand product’s business + UX needs" +msgstr "Understand product’s business + UX needs" + +#: ../../source/usability/personas.rst:597 +msgid "" +"Coordinate design, development, delivery, documentation, launch, sales " +"enablement + requests, service, integration, support." +msgstr "Coordinate design, development, delivery, documentation, launch, sales enablement + requests, service, integration, support." + +#: ../../source/usability/personas.rst:599 +msgid "" +"To work with stakeholders, UX + Dev to transform requirements into " +"experiences to deliver + assure all are met." +msgstr "To work with stakeholders, UX + Dev to transform requirements into experiences to deliver + assure all are met." + +#: ../../source/usability/personas.rst:601 +msgid "" +"Managing market requirements, trends, competitive landscapes, " +"constraints, cost, models, time, scope, risks and P+L to the executive " +"team." +msgstr "Managing market requirements, trends, competitive landscapes, constraints, cost, models, time, scope, risks and P+L to the executive team." + +#: ../../source/usability/personas.rst:604 +msgid "Manage customer partnerships + grow business opportunities" +msgstr "Manage customer partnerships + grow business opportunities" + +#: ../../source/usability/personas.rst:605 +msgid "Understanding company's strategic goals + reflecting those in the product" +msgstr "Understanding company's strategic goals + reflecting those in the product" + +#: ../../source/usability/personas.rst:610 +msgid "Stakeholder buy in" +msgstr "Stakeholder buy in" + +#: ../../source/usability/personas.rst:611 +msgid "Delivering on time" +msgstr "Delivering on time" + +#: ../../source/usability/personas.rst:612 +msgid "Visibility into cross functional statuses" +msgstr "Visibility into cross functional statuses" + +#: ../../source/usability/personas.rst:613 +msgid "Having enough time to spend with all the team and juggling priorities" +msgstr "Having enough time to spend with all the team and juggling priorities" + +#: ../../source/usability/personas.rst:614 +msgid "Driving problem resolution" +msgstr "Driving problem resolution" + +#: ../../source/usability/personas.rst:618 +msgid "" +"Pablo begins his day by checking his calendar, sees what meetings he has " +"today. Next he reviews emails and follows up on any IMs that he may not " +"have responded to. If any fires have occurred overnight, Pablo will jump " +"on resolving issues or unblocking progress. He gets on a couple of " +"customer calls and works to either gain insights or resolve issues with " +"the customer. His day is full of meetings with co-workers, executives and" +" conversations with customers. He is always working to coordinate and " +"manage the products across teams and throughout the company, as well as " +"with the customer base. This also means that Pablo occasionally touches " +"base with some of the Sales and Customer Experience teams. He " +"occasionally goes on site to visit customers + partners. He typically " +"makes rounds with Development + Project Management to assure that " +"everything is on track. Pablo says that his role requires him to wear " +"many hats. He considers his role part visionary, traffic coordinator, " +"technologist and communicator. “I love my job, it energizes and exhausts " +"me, all at the same time! Have more data to provide insights and guidance" +" would give me more time to focus on gaining deeper insights into " +"customer + market needs, rather than focusing on if the work is going to " +"get done.”" +msgstr "Pablo begins his day by checking his calendar, sees what meetings he has today. Next he reviews emails and follows up on any IMs that he may not have responded to. If any fires have occurred overnight, Pablo will jump on resolving issues or unblocking progress. He gets on a couple of customer calls and works to either gain insights or resolve issues with the customer. His day is full of meetings with co-workers, executives and conversations with customers. He is always working to coordinate and manage the products across teams and throughout the company, as well as with the customer base. This also means that Pablo occasionally touches base with some of the Sales and Customer Experience teams. He occasionally goes on site to visit customers + partners. He typically makes rounds with Development + Project Management to assure that everything is on track. Pablo says that his role requires him to wear many hats. He considers his role part visionary, traffic coordinator, technologist and communicator. “I love my job, it energizes and exhausts me, all at the same time! Have more data to provide insights and guidance would give me more time to focus on gaining deeper insights into customer + market needs, rather than focusing on if the work is going to get done.”" +