Done, created branch in launchpad and updated wiki page for Azerbaijani,
will start translation as soon as possible.
Thanks for information.

On 15.10.2015 02:31, Mark Sapiro wrote:
> On 10/14/2015 04:09 PM, Emin Mastizada wrote:
>> Wiki username: EminMastizada
>
> OK. You now have write access.
>
>
>> When Mailman 3 will be able for translations?
>
> For info, you can refer to
> <https://gitlab.com/mailman/mailman/issues/85>. At the moment, no one is
> moving forward on this and there is no schedule.
>
> If you want to help move this forward, I suggest joining
> [email protected] at
> <http://mail.python.org/mailman/listinfo/mailman-developers> and posting
> there.
>
>
>> Also how to get access in launchpad?
>
> All the Mailman 2.1 stuff is world readable at
> <https://launchpad.net/mailman>.
>
> If you want to be able to create your own branches or other things there
> for merging, register at <https://login.launchpad.net/>. Then, once
> logged in, you can push a branch to <https://code.launchpad.net/mailman>.
>
>
>> Can Mailman 2.1 be translated in launchpad? If no, will it be ok to add
>> translation to my github repo and submit using that repository?
>
> Mailman 2.1 is not set up for translation in Launchpad. If you wish to
> help do that, we can try to do it. Otherwise, the preferred workflow is
> for you to create your own branch off the head of the Mailman 2.1 branch
> and do your translating there using any tools you have available. If the
> result is in a public bzr branch somewhere that I can merge directly,
> that is easiest for me, but I am willing to work with you and will
> definitely accept your work from your github repo.
>

-- 
Emin Mastizada
Mozilla Representative @ Mozilla Corparation
Computer Engineering @ Istanbul Technical University
Data Ninja @ pyninjas
+90 539 932 6639
http://www.mastizada.com


_______________________________________________
Mailman-i18n mailing list
Posts: [email protected]
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-i18n/archive%40mail-archive.com

Reply via email to