Re: [Tails-l10n] People confirmed and where fork [Tails-l10n…

Borrar esta mensaxe

Responder a esta mensaxe
Autor: Cristian Salamea
Data:  
Para: Tails localization discussion
Asunto: Re: [Tails-l10n] People confirmed and where fork [Tails-l10n - Was Tails pages and announcements in spanish]

El 21/06/2014, a larjona@??? 13:58, Leonardo Nc <lenieco@???> escribió:

> Hi, I just added what Laura suggested as a workflow in https://pad.riseup.net/p/es-trans-tails, please check and add more info for clarifying the way we will be working at the translation together.


Thanks Leonardo ! so get start it.
About your doubts in pad, if we work in one repo then each one fork it, review will be more easy :-).


>
> :)
>
>
> 2014-06-21 12:59 GMT-05:00 Laura Arjona Reina <larjona@???>:
> El 21/06/14 19:42, Cristian Salamea escribió:
>
>
> El 21/06/2014, a las 12:01, sajolida@??? escribió:
>
> Emma Peel:
> i was following the howto!
> i thought that maybe some of the other members had already set up one.
> otherwise i can fork it on repo.or.cz
>
> Note that you most likely need one repo per person, so I suggest
> requesting one for you to tails-sysadmins@???.
>
>
> So we got people now i can confirm participation and where fork.
>
> Ok we got this people: https://pad.riseup.net/p/es-trans-tails so we can discuss now where fork, using git we got 3 options:
>
> * Github
> * Gitorious
> * Request a repo to tails-sysadmin
>
> Comments !
>
> If I am not wrong, each person should fork/clone the main repo, and he or she can choose where their public copy will be, it doesn't matter where it is (for example, mine would be in Gitorious, other people could use the Tails facilities...). All of us would set a remote being the main repo (our "upstream"). When I want to make a translation, I make a branch in my local repo, translate, and give the (public) URL of the branch so other people can pull it and/or review or change.
>
> Other people can do the same. We don't need to use the same forge, since we all use git and it's designed to work in a decentralized way.
>
> When a translation is ready, we give (again) the URL of the ready-to-merge branch and somebody with permissions in the main Tails repo will merge the translation, and the rest of us will fetch/pull from the main repo ("upstream") again so we all are up-to-date again.
>
> I hope I understood it well! If I'm wrong, please tell me :)
>
> Regards
> Laura Arjona
> https://wiki.debian.org/LauraArjona
>
>
>
>
> --
> sajolida
>
>
> _______________________________________________
> Tails-l10n mailing list
> Tails-l10n@???
> https://mailman.boum.org/listinfo/tails-l10n
> To unsubscribe from this list, send an empty email to Tails-l10n-unsubscribe@???.
>
> _______________________________________________
> Tails-l10n mailing list
> Tails-l10n@???
> https://mailman.boum.org/listinfo/tails-l10n
> To unsubscribe from this list, send an empty email to Tails-l10n-unsubscribe@???.
>
>
> _______________________________________________
> Tails-l10n mailing list
> Tails-l10n@???
> https://mailman.boum.org/listinfo/tails-l10n
> To unsubscribe from this list, send an empty email to Tails-l10n-unsubscribe@???.
>
>
>
> --
>
> Leonardo NC
> about.me/leonardo.nc
>
>
> GPG Key
> _______________________________________________
> Tails-l10n mailing list
> Tails-l10n@???
> https://mailman.boum.org/listinfo/tails-l10n
> To unsubscribe from this list, send an empty email to Tails-l10n-unsubscribe@???.