Overview and general discussion
37 views
Skip to first unread message
Tobias Killer
Jul 17, 2017, 4:51:23 PM7/17/17
to qubes-tr...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello and welcome to this mailing list "qubes-translation"!
Below, I'd like to introduce this mailing list to you.
# Why this mailing list? #
This mailing list is mainly for discussing
translation/localization/internationalization purposes related to
Qubes OS [1] which is hosted on GitHub [5] consisting of several
projects. Moreover, it shall provide an easy access for translators
and other helpers who don't have or don't want a Github account.
# How to join and leave this mailing list #
To subscribe to this mailing list, send a blank email to
<qubes-transla...@googlegroups.com> and follow the upcoming
instructions. A Google account is not needed. To unsubscribe, send a
blank email to <qubes-translat...@googlegroups.com> and
follow the upcoming instructions.
Even if you don't have subscribed to this list, you may follow the
discussions here [2] and you may also reply to the list by sending an
email to <qubes-tr...@googlegroups.com>.
# Goal #
The goal is to set up and run a system that provides localized
up-to-date versions of the Qubes OS website, documentation and software.
Notes:
When a change has been made to the original website, documentation or
software, the translated versions shall also get updated as soon as
possible. For reaching this, an appropriate translation workflow has
to be established. The steps in that workflow shall be feasible for
humans; however, bots should be programmed and used where useful and
possible.
# History #
Following discussions and decisions have been made in the past (GitHub
issues):
#1333: "Decide how to handle doc/website language translations" [6]
- - Treats URL, path and source file schemes. However, I couldn't find
any realization of them.
- - Notes that translations will be treated as untrusted since the Qubes
OS team cannot read them all. Thus, they won't be signed by the Qubes
OS team.
#1452: "Create automated workflow for translation of Markdown content" [7]
- - Sketches how to upload the *.md files as *.txt files (since Markdown
wasn't supported then) to Transifex and download back again.
- - Discusses a Spanish translation sprint.
- - Addresses the problem of badly formatted Markdown files.
- - Refers to a small tool [12] that inserts line breaks where sentences
heuristically end. However, it does not remove line breaks between
parts of a same sentence and it does not pay attention to Markdown
list elements, escaped periods etc.. Also, the heuristics could be better.
- - Sketches a priority list of what to translate first.
- - Mentions a need for a "GitHub integration", instead of using ZIP files.
#2599: "Add support for translations in Qubes Manager" [8]
- - Seems to show that support for translating the "Qubes Manager"
software has been implemented.
#2652: "Implement website translations" [9]
- - Shows Andrew's ToDo list concerning necessary preparations in order
to provide a usable infrastructure. However, currently no list point
is checked yet.
- - Shows a proposal for a language switch.
#2824: "Translation Guidelines" [10]
- - Refers to an early version of my translation guidelines proposal [13].
- - Refers to the belonging discussion thread [14].
- - Refers to the official Documentation Guidelines [15].
- - Refers to a proposed Translation Workflow [16].
- - Discusses that workflow.
# Current status #
To get all the phrases localized, we use the service of Transifex [3]
to get Qubes OS translated [4]. There, the "Localization Lab" team
[11] helps us.
The documentation files are written in the Markdown format [21][22].
Transifex supports the Markdown file format now [17]. In the past,
when Markdown was not supported yet, *.md files were renamed to *.txt
files and uploaded to Transifex. After being translated, the files
should be downloaded and renamed back again. However, I don't see any
result yet.
So, many people currently translate old *.txt files uploaded to
Transifex while we have much newer versions in *.md.
Today, there is still no translated page online (as far as I can see).
# What to do next? (unsorted list) #
[ ] Add this mailing-list to the list of mailing-lists of Qubes OS [18].
[ ] We should test if Transifex' support of Markdown will work and fit
our needs.
[ ] Remove the *.txt files from Transifex and upload the *.md files
instead as soon as they are formatted pretty well.
[ ] Adapt the webserver filesystem hierarchy to fit our needs. (In my
view, we should use directories named "en-US" etc. for the
translations while keeping file names unmodified. Links in the
Markdown files should be relative, not absolute. To be discussed.) See
#1333 [6].
[ ] Implement a language switch. See #2652 [9].
[ ] Set up a test environment/directory on the server to test the
localized versions.
[ ] Set up a translation workflow (including translation guidelines
and a priority list concerning which page to translate first). See
#2824 [10][16].
[ ] Using the "Translation Memory Autofill" feature on Transifex
[19][20] doesn't work well if there are multiple sentences in a line
or multiple lines for one sentence in a original file. Thus, the
translation workflow should have a step to "beautify" the canonical
files before uploading them to Transifex. This is important and should
work well, so, this step should be made by machine if possible. See
#1452 [7][12].
[ ] Notify the translators at Transifex about the new translation
guidelines to follow.
[ ] Localize the *website* and *documentation* of Qubes OS.
[ ] Automate (sub-)processes of the translation workflow(s). Note: Our
bots should log their activities.
[ ] Implement a mechanism that inserts a top banner on every page
which says "This page is outdated." if there is a newer canonical version.
[ ] Implement a mechanism that inserts a top banner on every
non-canonical page which says something like "Warning: The following
is not the official version, thus, parts could be untranslated or
translated misleadingly. If you do not trust this version, please
refer to the English (US) version." which shall show up on every
non-canonical page.
[ ] Localize the *software* of Qubes OS. (This could need its own
Translation Workflow.) See #2599 [8].
I suggest that you may pick up a point you like to do or to discuss
and tell me (send an email to both me and this mailing list at the
same time). I'll coordinate the tasks.
Please answer to this email if you have to say something about the
list above (proposals for additions, deletions, modifications) or
something general. If you want to implement or discuss some point of
this list, please create a new email thread with a subject line
containing at least a short version of that point. E.g., if you want
to specify what bots should log, the subject line could be "Logging
bot activities: Specify what to log".
# Miscellaneous #
I'm looking for a co-leader who has experiences in getting software
and/or websites localized and could help when making decisions.
However, it's not a big problem to do it alone.
Please find attached my OpenPGP key. You may use it to verify the
digital signatures of the emails I'll write to this list.
Please do not top-post [23].
If there is anything unclear or if there are any questions or
suggestions, just tell me.
Regards,
Tobias Killer
[1] https://www.qubes-os.org/
[2] https://groups.google.com/forum/#!forum/qubes-translation
[3] https://www.transifex.com/
[4] https://www.transifex.com/otf/qubes/
[5] https://github.com/QubesOS
[6] https://github.com/QubesOS/qubes-issues/issues/1333
[7] https://github.com/QubesOS/qubes-issues/issues/1452
[8] https://github.com/QubesOS/qubes-issues/issues/2599
[9] https://github.com/QubesOS/qubes-issues/issues/2652
[10] https://github.com/QubesOS/qubes-issues/issues/2824
[11] https://www.transifex.com/otf/public/
[12] https://github.com/gsganden/sentence-separator
[13]
https://groups.google.com/d/msgid/qubes-devel/b8290681-9137-bf33-6dbf-ac6a663df69f%40posteo.de
[14] https://groups.google.com/d/topic/qubes-devel/a4gg3g4UuJg/discussion
[15] https://www.qubes-os.org/doc/doc-guidelines/
[16]
https://github.com/tokideveloper/qubes-doc/blob/translation-workflow/basics_user/translation-workflow.md
[17] https://docs.transifex.com/formats/markdown
[18] https://www.qubes-os.org/mailing-lists/
[19] https://docs.transifex.com/setup/translation-memory
[20] https://docs.transifex.com/setup/translation-memory/enabling-autofill
[21] https://daringfireball.net/projects/markdown/syntax
[22] https://github.github.com/gfm/
[23] https://en.wikipedia.org/wiki/Posting_style
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEE9VOPt2yY9xS+XKzULaXvb25AsygFAlltIzIACgkQLaXvb25A
syicXg/+M6faA0Bc8GPq0Z0MchmGVdhwM+5Yc7tXtLqjVlKt4H9a5tggBIxMxmpm
xij9usLJs3EyZC323n5YOhagqaieVk2+uZ1/qPrPTZVS69t9V//TQGL7Dt46pf4Y
BQSWapMY9EqK/NEgNZBuPYK0cVv11vZEyWPNZDCMxJ2ACFo4hpTaY9/Uy8ojag4g
+YC0xZerFwTrxEslUMEZ5tIfupf4mx3HGUiaPMkgpcEurxdexm6XB8ByVzpSeLgL
Sm0mMuzUXs/p8AG7zp9dkxnlJ7fD5pMc2B+//Ghi4PiEBkEH0hd3kzfn1lSPn2DC
9lGoDta380hX6bDgPAG0fi7AQb9Hnw5scMh6WK8kN//9DfujdvDDy4vxmyWEFNCg
r5INA6Z65k24hWv3XM562TfWQ50KAxVmaQ1FrQe5YfLa0Dn9+nppRZfCNDUW1XKa
qa54V/Us2KQJDKBqRl/Zp69a7DmTxnHdNUaPBQQ2nR0qDoCeJ8UEL09R5POJc9Ic
1MafYMVnEz7x0YKflKQtUf4ef0nrMtabHazWTHNv+ZDbWln7j9nYF1CnkHDe8atp
0g7V3W2Sblh+/DIBFHDCr63CvntayU1qC6UFMIa74WBaw6ZKzuzQ092kY0FzMLBc
EeBniPnAb3Vk5BDqq7V0h56tBQlbAOLb62Pg+yG4zNmGJJOhe04=
=hzoo
-----END PGP SIGNATURE-----
Hash: SHA256
Hello and welcome to this mailing list "qubes-translation"!
Below, I'd like to introduce this mailing list to you.
# Why this mailing list? #
This mailing list is mainly for discussing
translation/localization/internationalization purposes related to
Qubes OS [1] which is hosted on GitHub [5] consisting of several
projects. Moreover, it shall provide an easy access for translators
and other helpers who don't have or don't want a Github account.
# How to join and leave this mailing list #
To subscribe to this mailing list, send a blank email to
<qubes-transla...@googlegroups.com> and follow the upcoming
instructions. A Google account is not needed. To unsubscribe, send a
blank email to <qubes-translat...@googlegroups.com> and
follow the upcoming instructions.
Even if you don't have subscribed to this list, you may follow the
discussions here [2] and you may also reply to the list by sending an
email to <qubes-tr...@googlegroups.com>.
# Goal #
The goal is to set up and run a system that provides localized
up-to-date versions of the Qubes OS website, documentation and software.
Notes:
When a change has been made to the original website, documentation or
software, the translated versions shall also get updated as soon as
possible. For reaching this, an appropriate translation workflow has
to be established. The steps in that workflow shall be feasible for
humans; however, bots should be programmed and used where useful and
possible.
# History #
Following discussions and decisions have been made in the past (GitHub
issues):
#1333: "Decide how to handle doc/website language translations" [6]
- - Treats URL, path and source file schemes. However, I couldn't find
any realization of them.
- - Notes that translations will be treated as untrusted since the Qubes
OS team cannot read them all. Thus, they won't be signed by the Qubes
OS team.
#1452: "Create automated workflow for translation of Markdown content" [7]
- - Sketches how to upload the *.md files as *.txt files (since Markdown
wasn't supported then) to Transifex and download back again.
- - Discusses a Spanish translation sprint.
- - Addresses the problem of badly formatted Markdown files.
- - Refers to a small tool [12] that inserts line breaks where sentences
heuristically end. However, it does not remove line breaks between
parts of a same sentence and it does not pay attention to Markdown
list elements, escaped periods etc.. Also, the heuristics could be better.
- - Sketches a priority list of what to translate first.
- - Mentions a need for a "GitHub integration", instead of using ZIP files.
#2599: "Add support for translations in Qubes Manager" [8]
- - Seems to show that support for translating the "Qubes Manager"
software has been implemented.
#2652: "Implement website translations" [9]
- - Shows Andrew's ToDo list concerning necessary preparations in order
to provide a usable infrastructure. However, currently no list point
is checked yet.
- - Shows a proposal for a language switch.
#2824: "Translation Guidelines" [10]
- - Refers to an early version of my translation guidelines proposal [13].
- - Refers to the belonging discussion thread [14].
- - Refers to the official Documentation Guidelines [15].
- - Refers to a proposed Translation Workflow [16].
- - Discusses that workflow.
# Current status #
To get all the phrases localized, we use the service of Transifex [3]
to get Qubes OS translated [4]. There, the "Localization Lab" team
[11] helps us.
The documentation files are written in the Markdown format [21][22].
Transifex supports the Markdown file format now [17]. In the past,
when Markdown was not supported yet, *.md files were renamed to *.txt
files and uploaded to Transifex. After being translated, the files
should be downloaded and renamed back again. However, I don't see any
result yet.
So, many people currently translate old *.txt files uploaded to
Transifex while we have much newer versions in *.md.
Today, there is still no translated page online (as far as I can see).
# What to do next? (unsorted list) #
[ ] Add this mailing-list to the list of mailing-lists of Qubes OS [18].
[ ] We should test if Transifex' support of Markdown will work and fit
our needs.
[ ] Remove the *.txt files from Transifex and upload the *.md files
instead as soon as they are formatted pretty well.
[ ] Adapt the webserver filesystem hierarchy to fit our needs. (In my
view, we should use directories named "en-US" etc. for the
translations while keeping file names unmodified. Links in the
Markdown files should be relative, not absolute. To be discussed.) See
#1333 [6].
[ ] Implement a language switch. See #2652 [9].
[ ] Set up a test environment/directory on the server to test the
localized versions.
[ ] Set up a translation workflow (including translation guidelines
and a priority list concerning which page to translate first). See
#2824 [10][16].
[ ] Using the "Translation Memory Autofill" feature on Transifex
[19][20] doesn't work well if there are multiple sentences in a line
or multiple lines for one sentence in a original file. Thus, the
translation workflow should have a step to "beautify" the canonical
files before uploading them to Transifex. This is important and should
work well, so, this step should be made by machine if possible. See
#1452 [7][12].
[ ] Notify the translators at Transifex about the new translation
guidelines to follow.
[ ] Localize the *website* and *documentation* of Qubes OS.
[ ] Automate (sub-)processes of the translation workflow(s). Note: Our
bots should log their activities.
[ ] Implement a mechanism that inserts a top banner on every page
which says "This page is outdated." if there is a newer canonical version.
[ ] Implement a mechanism that inserts a top banner on every
non-canonical page which says something like "Warning: The following
is not the official version, thus, parts could be untranslated or
translated misleadingly. If you do not trust this version, please
refer to the English (US) version." which shall show up on every
non-canonical page.
[ ] Localize the *software* of Qubes OS. (This could need its own
Translation Workflow.) See #2599 [8].
I suggest that you may pick up a point you like to do or to discuss
and tell me (send an email to both me and this mailing list at the
same time). I'll coordinate the tasks.
Please answer to this email if you have to say something about the
list above (proposals for additions, deletions, modifications) or
something general. If you want to implement or discuss some point of
this list, please create a new email thread with a subject line
containing at least a short version of that point. E.g., if you want
to specify what bots should log, the subject line could be "Logging
bot activities: Specify what to log".
# Miscellaneous #
I'm looking for a co-leader who has experiences in getting software
and/or websites localized and could help when making decisions.
However, it's not a big problem to do it alone.
Please find attached my OpenPGP key. You may use it to verify the
digital signatures of the emails I'll write to this list.
Please do not top-post [23].
If there is anything unclear or if there are any questions or
suggestions, just tell me.
Regards,
Tobias Killer
[1] https://www.qubes-os.org/
[2] https://groups.google.com/forum/#!forum/qubes-translation
[3] https://www.transifex.com/
[4] https://www.transifex.com/otf/qubes/
[5] https://github.com/QubesOS
[6] https://github.com/QubesOS/qubes-issues/issues/1333
[7] https://github.com/QubesOS/qubes-issues/issues/1452
[8] https://github.com/QubesOS/qubes-issues/issues/2599
[9] https://github.com/QubesOS/qubes-issues/issues/2652
[10] https://github.com/QubesOS/qubes-issues/issues/2824
[11] https://www.transifex.com/otf/public/
[12] https://github.com/gsganden/sentence-separator
[13]
https://groups.google.com/d/msgid/qubes-devel/b8290681-9137-bf33-6dbf-ac6a663df69f%40posteo.de
[14] https://groups.google.com/d/topic/qubes-devel/a4gg3g4UuJg/discussion
[15] https://www.qubes-os.org/doc/doc-guidelines/
[16]
https://github.com/tokideveloper/qubes-doc/blob/translation-workflow/basics_user/translation-workflow.md
[17] https://docs.transifex.com/formats/markdown
[18] https://www.qubes-os.org/mailing-lists/
[19] https://docs.transifex.com/setup/translation-memory
[20] https://docs.transifex.com/setup/translation-memory/enabling-autofill
[21] https://daringfireball.net/projects/markdown/syntax
[22] https://github.github.com/gfm/
[23] https://en.wikipedia.org/wiki/Posting_style
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEE9VOPt2yY9xS+XKzULaXvb25AsygFAlltIzIACgkQLaXvb25A
syicXg/+M6faA0Bc8GPq0Z0MchmGVdhwM+5Yc7tXtLqjVlKt4H9a5tggBIxMxmpm
xij9usLJs3EyZC323n5YOhagqaieVk2+uZ1/qPrPTZVS69t9V//TQGL7Dt46pf4Y
BQSWapMY9EqK/NEgNZBuPYK0cVv11vZEyWPNZDCMxJ2ACFo4hpTaY9/Uy8ojag4g
+YC0xZerFwTrxEslUMEZ5tIfupf4mx3HGUiaPMkgpcEurxdexm6XB8ByVzpSeLgL
Sm0mMuzUXs/p8AG7zp9dkxnlJ7fD5pMc2B+//Ghi4PiEBkEH0hd3kzfn1lSPn2DC
9lGoDta380hX6bDgPAG0fi7AQb9Hnw5scMh6WK8kN//9DfujdvDDy4vxmyWEFNCg
r5INA6Z65k24hWv3XM562TfWQ50KAxVmaQ1FrQe5YfLa0Dn9+nppRZfCNDUW1XKa
qa54V/Us2KQJDKBqRl/Zp69a7DmTxnHdNUaPBQQ2nR0qDoCeJ8UEL09R5POJc9Ic
1MafYMVnEz7x0YKflKQtUf4ef0nrMtabHazWTHNv+ZDbWln7j9nYF1CnkHDe8atp
0g7V3W2Sblh+/DIBFHDCr63CvntayU1qC6UFMIa74WBaw6ZKzuzQ092kY0FzMLBc
EeBniPnAb3Vk5BDqq7V0h56tBQlbAOLb62Pg+yG4zNmGJJOhe04=
=hzoo
-----END PGP SIGNATURE-----
Florian Brandes
Jul 18, 2017, 9:36:54 AM7/18/17
to qubes-tr...@googlegroups.com, tokidev
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
On 07/17/2017 10:51 PM, Tobias Killer wrote:
> # What to do next? (unsorted list) #
>
> [ ] Add this mailing-list to the list of mailing-lists of Qubes OS [18].
I quickly wrote something about the qubes translation mailing list. Please see [1]
> # What to do next? (unsorted list) #
>
> [ ] Add this mailing-list to the list of mailing-lists of Qubes OS [18].
for information. I'm open to suggestions, otherwise I would create a pull request
later.
[1] https://github.com/gador/qubesos.github.io/blob/master/pages/mailing-lists.md
Regards,
Florian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQI0BAEBCAAeBQJZbg7wFxxmbG9yaWFuLmJyYW5kZXNAZ214LmRlAAoJEKf3MHt6
BMRJxs8QAIZod4oY3adD0eSSB4mqIku2du1NsHmLtYJMjOPEHfCNXSw8cWqJAVTu
pucylV/qs6ihVFfmk3Q0oW7zMwusfrO+J0p6UThweqwiKbUc2uwkrJ1m3hbXyO6r
i9Y1DqJRQIapSRt0fKSztjhpB8NTF+kwZBHBhqhvISP2m9qII35LzzfIvy4ID7ab
lEdJaQUbjbiIv6/moPhRBzyxFlxyyv6w6HjfDveEDE9kfWeqkfgNVdjrCgYP9OD0
CnhuerSkbs1r3k0qPdFLYOIpBof0BsAnf+owFPOtB/aA+K7UAuVLEUoHARzF0wJu
0KGLUvZPqmMvTV99zKXExCLTV1BVtxClgvqZ++TWTaudxcAPzPaS8qIVBfHEEtiw
3HQaTVMXP91Yj4rRZOAhxBfS+pa2GEu4knK4lZdp0q7dtP3wd+T8vF9JywnWTdHe
XH6P8HpeVffZuTvd3RRH0IaMsoSaE8se7+fItAIJHYZjgf2kzuQYCV97xZ1Ej0Np
seWsxIclvkcUHSLiJHFB8ieKFGtQSwEhrDVPqHdCgemea2iLqlNTPORTCzhoM2FM
IiUsQgJ75vPQukL7otPNHGmtGJxdU2PoQUjbqOKNCScsRNaWURgZ6yJOFLVUmfGf
LOojmwUuLt6eePyczKiXC5KnBuGuPrIY65aV7/R+GnxorWLvaV2D
=Bjg8
-----END PGP SIGNATURE-----
Michael Carbone
Jul 18, 2017, 3:52:44 PM7/18/17
to qubes-tr...@googlegroups.com
Florian Brandes:
the formatting and tweak the content to match other list descriptions.
--
Michael Carbone
Qubes OS | https://www.qubes-os.org
@QubesOS <https://www.twitter.com/QubesOS>
PGP fingerprint: D3D8 BEBF ECE8 91AC 46A7 30DE 63FC 4D26 84A7 33B4
> On 07/17/2017 10:51 PM, Tobias Killer wrote:
>
>> # What to do next? (unsorted list) #
>
>> [ ] Add this mailing-list to the list of mailing-lists of Qubes OS [18].
>
> I quickly wrote something about the qubes translation mailing list. Please see [1]
> for information. I'm open to suggestions, otherwise I would create a pull request
> later.
>
> [1] https://github.com/gador/qubesos.github.io/blob/master/pages/mailing-lists.md
Thanks for starting this! I submitted a pull request to (hopefully) fix
>
>> # What to do next? (unsorted list) #
>
>> [ ] Add this mailing-list to the list of mailing-lists of Qubes OS [18].
>
> I quickly wrote something about the qubes translation mailing list. Please see [1]
> for information. I'm open to suggestions, otherwise I would create a pull request
> later.
>
> [1] https://github.com/gador/qubesos.github.io/blob/master/pages/mailing-lists.md
the formatting and tweak the content to match other list descriptions.
--
Michael Carbone
Qubes OS | https://www.qubes-os.org
@QubesOS <https://www.twitter.com/QubesOS>
PGP fingerprint: D3D8 BEBF ECE8 91AC 46A7 30DE 63FC 4D26 84A7 33B4
Florian Brandes
Jul 19, 2017, 1:47:45 AM7/19/17
to qubes-tr...@googlegroups.com, mic...@qubes-os.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
On 07/18/2017 09:52 PM, Michael Carbone wrote:
> Florian Brandes:
>> On 07/17/2017 10:51 PM, Tobias Killer wrote:
>>
>>> # What to do next? (unsorted list) #
>>
>>> [ ] Add this mailing-list to the list of mailing-lists of Qubes OS [18].
>>
>> I quickly wrote something about the qubes translation mailing list. Please see [1]
>> for information. I'm open to suggestions, otherwise I would create a pull request
>> later.
>>
>> [1] https://github.com/gador/qubesos.github.io/blob/master/pages/mailing-lists.md
>
> Thanks for starting this! I submitted a pull request to (hopefully) fix
> the formatting and tweak the content to match other list descriptions.
>
Hi Michael,
> Florian Brandes:
>> On 07/17/2017 10:51 PM, Tobias Killer wrote:
>>
>>> # What to do next? (unsorted list) #
>>
>>> [ ] Add this mailing-list to the list of mailing-lists of Qubes OS [18].
>>
>> I quickly wrote something about the qubes translation mailing list. Please see [1]
>> for information. I'm open to suggestions, otherwise I would create a pull request
>> later.
>>
>> [1] https://github.com/gador/qubesos.github.io/blob/master/pages/mailing-lists.md
>
> Thanks for starting this! I submitted a pull request to (hopefully) fix
> the formatting and tweak the content to match other list descriptions.
>
thanks! Merged your pull request. I think, it looks good. If noone has any objection,
I will submit the pull request today for Qubes.
Florian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
BMRJWWsP/3TSqNis9ZyR2S8w4uSfHZb1SOW1pVF+H9MnsdcJglnX3FnIN+i+LIt+
p7i8EKYr68ryCr5eu7mgNSR/Ek8YOSvyaeCb48oaYwA3Pgfv6+m4tYsNft1oNLkZ
m9Fm0UnBkh/LVmjuh+OAStkgSgYoNcT4NHflQe8Mn1bRhrNbGETHN2AtxltUjHXX
WY0jsfsJBu2YBSqztSIZuwivrjE9kniQz/c1Rs2tmqodJJdBoRD0unmhYzAgX7SE
FHIlHukrxCS/HNV/RGRZBydbNvpVEaJFoVqIEyOxo+Fp/NgXKmGw+bJe53ZkK0QT
e9/1WaIicIyLArZife/CVA7/fBEQU4543eUdF/7tD+QwyPoZBACKMDHp8TOg8547
cX6DwTB5IJYBIvigkIdnknAb2G/SZBaa5EYYbccghtUfNrvwQYzmYFD8OY7jBvQd
ey0XMKTgYOG21M6NM70VQweTAYSIgZtaYWwjqf7wp+SjBKSMwN6m7lMlP1TqjTqH
E0YkxJ53+pwi+bkPGFw3nh5+DzAGOF+cf9AaQD9IJh9gSCtgRqDaDgAFmzK3cj1y
lBXfKb1vbc0KP3aW7lVfoHUycjJlWmu1PxFOdF0+Q5Ts11q2NBzkgyZDNBtQVGhe
YLa/JFXSMotZ/437GYE4W5DB9R3VOFtywU+loUOf/7m+fcWCmRf8
=zXBO
-----END PGP SIGNATURE-----
Tobias Killer
Jul 19, 2017, 3:22:21 PM7/19/17
to Florian Brandes, qubes-tr...@googlegroups.com, mic...@qubes-os.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
Am 19.07.2017 um 07:47 schrieb Florian Brandes:
> On 07/18/2017 09:52 PM, Michael Carbone wrote:
>> Florian Brandes:
>>> On 07/17/2017 10:51 PM, Tobias Killer wrote:
>>>
>>>> # What to do next? (unsorted list) #
>>>
>>>> [ ] Add this mailing-list to the list of mailing-lists of
>>>> Qubes OS [18].
>>>
>>> I quickly wrote something about the qubes translation mailing
>>> list. Please see [1] for information. I'm open to suggestions,
>>> otherwise I would create a pull request later.
>>>
>>> [1]
>>> https://github.com/gador/qubesos.github.io/blob/master/pages/mailing-lists.md
>
>>>
>> Thanks for starting this! I submitted a pull request to
>> (hopefully) fix the formatting and tweak the content to match
>> other list descriptions.
>
>
> Hi Michael,
>
> thanks! Merged your pull request. I think, it looks good. If noone
> has any objection, I will submit the pull request today for Qubes.
Looks good!
> On 07/18/2017 09:52 PM, Michael Carbone wrote:
>> Florian Brandes:
>>> On 07/17/2017 10:51 PM, Tobias Killer wrote:
>>>
>>>> # What to do next? (unsorted list) #
>>>
>>>> [ ] Add this mailing-list to the list of mailing-lists of
>>>> Qubes OS [18].
>>>
>>> I quickly wrote something about the qubes translation mailing
>>> list. Please see [1] for information. I'm open to suggestions,
>>> otherwise I would create a pull request later.
>>>
>>> [1]
>>> https://github.com/gador/qubesos.github.io/blob/master/pages/mailing-lists.md
>
>>>
>> Thanks for starting this! I submitted a pull request to
>> (hopefully) fix the formatting and tweak the content to match
>> other list descriptions.
>
>
> Hi Michael,
>
> thanks! Merged your pull request. I think, it looks good. If noone
> has any objection, I will submit the pull request today for Qubes.
Have a lot thanks!
>
> Florian
>
Tobias
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEE9VOPt2yY9xS+XKzULaXvb25AsygFAllvsUsACgkQLaXvb25A
syjGhg/+ICvDQK6wAjQeM8qG1bOAP+jinJqK9Ho9bvOzMCvt3y+HCegHelKutUOk
hju5Ordk/VaHcBcqu3CT5Q00d5Qr1mz9yVfppwMaAJQNF5hyrHzVFWr9l4cu8hX4
WSB3lsj/VGdnzDx1MH8cbASRpgdx4wQUp4rgHTiq7nPKS+DD4eaEKzeJXfeXukha
2Y7xXPPpYRj+rvoyomOx0hlHvQ2bW3awi5HDVUY4+l2fhqFTT5OyIbZkyXsDZ0ph
9/o+kCa7QFqfhYaZUDhCjuKdJWeNkIVV7usAp8nnavKMCF3bxeRvw8AwMMaSoART
rCuL+9wS0mkdS0rMqUO5GPOmhbn+FZVbkIsyo1LXZu0QuhHK3RbwcGUK09ag23Zp
hUtmz4Mm7ty9PNi7z8HvQ+Sd2ptAaLw12idnyHOH5GU3BvBiVuVC/aMp8PiRfcUU
WiZ6DldlJqCqK0ajc+mdcDGUymD6LNGA8psqsKPVHfjgLiQ+PFnRlRc143iwJezg
rsHmrbVP9lIoDiiJdn2T0V0zh9HpCpeXQZng1ryLozMTdeJ7LaqczyfURRSaXPk6
zcPxQpFq152ChRKCJ/0O9ObhRvnMIlh7TasSOAfMEcJ3UJuoyh7XgeoNs48SwD5Y
TgREFv1kVNcoxah6jsVVR1otANhqO+xOFkPe/8VziYOv0O0loRQ=
=ip3I
-----END PGP SIGNATURE-----
Tobias Killer
Jul 17, 2018, 2:19:05 AM7/17/18
to qubes-tr...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello everyone,
Hash: SHA256
My public OpenPGP key expired, so, please find attached my updated one.
Regards,
Tobias Killer
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEE9VOPt2yY9xS+XKzULaXvb25AsygFAltNikEACgkQLaXvb25A
sygc1w//WqmD+Gxyz/UPRsls1a58qGFh6SuW+kYDueH/Y57xrslWfr4J+Fk11BwL
BjAInE68v753vHvBeexakd2lIyL9ifUT6gGLo9ZfGMcV3ze16L2RGZGwgX5hi97a
bddERMOQOrqn/m5ypoahUfjNarjRPeDUPNoQPOLCYDPqpT9BPn0tu4ImImV3+bXm
u4c7Pu0olmF73hitLvpwoBLJUMQ8cgy0zz+RGowAwlTIz5MnEC+Y4LXl1IVxGzWm
t083mWe74vGXYer0SJrE2hx6dOR/cSNZPgke4WwEOdENs8xtNY6eAYgVRbhKm7mG
SUsx8TPjUa5fQZPAaoTZ7PCgM/Y1nJxrQWkaDSfxG+sx4sCmS5o/TrWQKDJxoZJp
8EIc4SEAPeVwawEoO1AFR+P2sgs3Ue6BLLw/9u8+cm1mjEUG2VQgHRDkVn9k9nKs
oeh5mQIuPD9I1dP2iA5h3OXVyVDMdYDaBv9Om2z15cJHJTykxuNdOpaEQFOxavTp
Q2XSsdSsSzZfCynC5+VB1wivb+dl7/SFnvr1ZlvQsj6/Diws1JKsZR4AcGhHWPFD
/czlEHj6NZeBoKjhe0etc2lZy8DTuM/z+3x5I6g25CtkdHmTTOsxRecVH56JEV33
ms8vQLHshC9zgm0/nqV0ggP8KIjk800QE+WCZKm5zuSE8Mg0cmg=
=Pa/y
-----END PGP SIGNATURE-----
Reply all
Reply to author
Forward
0 new messages