E' qui: https://git.lattuga.net/transitails/italian
...
...
@@ -37,7 +41,7 @@ E' qui: https://git.lattuga.net/transitails/italian
Per essere abilitati in scrittura, iscrivetevi a git.lattuga.net e chiedete in lista di accettarvi l'utente.
#Git comandi quotidiani
## Git comandi quotidiani
Tutte le righe che iniziano con $ sono da digitare nel terminale, a volte sotto c'è la risposta del terminale, oppure niente. In generale nei sistemi unix-like se il terminale dopo aver dato un comando non vi risponde niente, vuol dire che tutto è andato bene.
Il pulsante TAB è vostro amico per completare tutti i percorsi dei file e soprattutto quando usate git add. Le frecce su e giù della tastiera vi danno gli ultimi comandi che avete lanciato, così andate velocissim*. Tutto quello che inizia con [hagfsa] va sostituito con il nome che fa al caso vostro. Se vi trovate ad un certo punto intrappolati nel terminale e c'è ESC in fondo, niente paura, è vim, quindi fate: ESC : q
...
...
@@ -88,6 +92,13 @@ Verificate che il commit ci sia
L'alias `graph` mostra un "grafo" della situazione corrente, in modo da riconoscere come sono disposte le varie branch e dove siete voi.
L'alias `lg` e' simile, ma non mostra TUTTE le branch possibili e immaginabili. Di default mostra solo lo stato corrente (tipo git log, ma piu' stringato). Se fatte tipo `git lg master mia-branch` potete vedere come sta messa la vostra branch rispetto al master. E' in avanti? indietro? ecc.
# Lavoro da affrontare
...
...
@@ -292,3 +303,47 @@ Oppure in grafica dal browser:
* revisione (non chiaro: quando si sceglie chi revisiona?)
* merge dentro master
Ogni tanto (quando?) si fanno dei pacchi di traduzioni. Un pacco e' un insieme di filename che vanno tradotti. Ogni pacco viene tradotto da una persona.
Supponiamo di tradurre la divina commedia, e di fare 3 pacchi: Inferno, Purgatorio e Paradiso. Petrarca si accolla di tradurre l'Inferno, e lo fa in una branch che chiama, appunto "inferno". traduce tutti i file `wiki/src/inferno/*.po`, quindi fa `git commit -m "inferno tradotto"`.
A questo punto qualcuno deve revisionare la branch. Si fa avanti Laura. Laura fa `git fetch origin && git checkout origin/inferno`. Prima guarda le differenze introdotte da Petrarca, con `git log -p origin/inferno`.
Gli sembrano ok, ma per controllare che si vedano anche bene nel wiki lo builda con `./build-website` e poi lo guarda da firefox. Nota che Petrarca, sbadato, ha fatto alcuni piccoli errori nel markup del wiki che "rompono" delle immagini. Petrarca aveva tradotto la riga
[[!img \"caronte.png`"]]
con
[[img \"caronte.png\"`]]
Laura corregge e fa commit sulla stessa branch `git commit wiki/src/inferno/terzocanto.po -m "fix immagine caronte" && git push origin inferno`.
Non trova altri errori, quindi fa
git checkout master
git merge inferno
Potrebbe subito fare `git push origin master` ma, per non sbagliare, fa un diff:
git diff origin/master..master
E controlla se tutto torna. Ci sono conflitti? Quel cambiamento al `!img` c'e' ancora? bene, ora possiamo fare
git push origin master
## Call for translations
Prima di una release, in lista tails-l10n arriva un'email "Call for translations". Come si procede a quel punto?
# [[!tails_ticket 11717 desc="Consider dropping launchers from the Desktop"]]
Even though there was a general support for dropping the launchers, but a long discussion when (3.0 or earlier) the launchers on the Desktop should be removed and if the launchers in Applications Favorites should be added earlier or at the same time. It is unclear how much people still depend on a Trash icon on the desktop and if new users will find our documentation, if there is not Desktop launcher. In particular new users, who are not used to the Gnome desktop and Linux, do need an obvious entry point to our documentation.
We finally decided to keep the Desktop launchers for now, if that is not too much work, and get rid of all the launchers if it's too much trouble. We can drop the launchers, when we do have a "take a tour" feature to introduce new users to Tails and the Gnome desktop.
If wanted Trash and Home could already be dropped now or with 3.0 and we will see if and how many users complain.
# [[!tails_ticket 11615 desc="What about keybase.io?"]]
keybase.io makes it possible to link PGP keys with social media accounts like @Tails_live. While many people liked the idea of using this for adding more trust-paths to the Tails signing key, it was decided that we will drop this suggestion at least for now, because the benefit for Tails is rather small. In particular there already are links from the signing key to the Twitter account, e.g. via the documentation on the signed ISO image.
Also no one of the Tails key-master, who would need to do the actual work, was present.
# [[!tails_ticket 11663 desc="Clarifying the scope of hardware support"]]
While we had the general impression that the ticket raises a valid concern, it was not clear what precise question we could discuss or answer during the meeting. We decided to reassign the ticket to the author and ask for clarification what to do.
# [[!tails_ticket 11775 desc="Decide when to close down tails-support"]]
We decided to follow sajolida's proposal in the ticket. The close down should also be announced on Twitter, in the blog and the documentation needs to be update.
The monthly report, that should be out before September 15, should already announce the announcement of the closure. The actual announcement in the blog will also explain the reasons for the closure.
Because tails-support has so little traffic, we decided that the possibility to answer people who already asked a question will probably not be a problem.
# [[!tails_ticket 11767 desc="Gender neutral translations in German: discuss MITM"]]
This topic came up in a discussion between the German translators: The word "man" in "man-in-the-middle" could/should be replaced by some other term like "machine", "computer", or "attacker". In German the term "Mensch in der Mitte" could be used. There were a number of arguments in favor and against the proposal:
- "Man-in-the-middle" is the term people and the literature are using and what people will search for. Another term could be mistaken for another kind of attack.
- Google also finds "man in the middle", when one searches for "machine in the middle" or "attacker in the middle".
- Everything but "machine in the middle" will lead to abbreviations like AITM or HITM, that can't be searched for.
- One could write something along the lines of "attacker-in-the-middle (more often called man-in-the-middle, MITM)". One would need to check each page using the term for understandability.
This ticket was added to the agenda in the last minute and we decided to keep it for the next meeting.
# Volunteers to handle "[Hole in the roof](https://labs.riseup.net/code/versions/198)" tickets this month
Most participants already have enough work to do and did volunteer for another Hole in the roof ticket, but some people are already actively working on #7700.
# Volunteers to handle important [tickets flagged for next release, but without assignee](https://labs.riseup.net/code/projects/tails/issues?query_id=226)
There were only two tickets of this kind. Both were decided not be extremely important and for both it was not clear how to proceed.
