Re: Where are release notes?

On 2018/10/05 15:10, Jean-Baptiste wrote:
> It was true, but isn't anymore, the documentation team was using publican (XML based) and now uses Antara (asciidoc based).
> The current projects in Zanata refers to the XML ones, so no need to unlock them.

Hi Jean Baptiste

Thank you for working hard for the team. Now I am feeling fear that many 
important things are moving forward in the dark without any interaction 
with many of translators here. Could you mind pause a bit?

> 
> I'm working with the docs team to enable translations, some information are there:
> https://pagure.io/fedora-docs/design-documents
> 
> We should be able to translate documentations of the release notes by the release. Adam and I are working on this almost everyday.

I have a few questions.

First, Antra can't deal with zanata? If it can, it is best to keep using 
zanata for a while until everything to be cleared and confirmed. if it 
can't, any background what made docs team to move from publican to antra?

Second, I would like to know clear reason/cause if any move our platform 
to somewhere is really required?

1)If it is because the translators wish to have better featured 
platform, please carry balloting system in order to make a decision as a 
whole translation team. Every language team should have a chance to say 
yes or no.

2) If it is because it has to happen due to zanata issue, then the 
authority (redhat or council) should make official announcement for us 
and share their expectation to us. If the expectation is "move 
platform", then no longer needs balloting system, and it places us 
better position in order to discuss with devel team.

> 
> If you go in the l10n repositories, you'll see Weblate commits. I used it for my tests and will propose the community to take the opportunity to test the tool for a few days. Anyway, we made sure the process is platform agnostic.
> 
> If you want to have a close follow up of the progress of  this, go to the fedora docs on telegram or irc. I'll come back here to ask for testers.

Before testing, as said, we should go through the steps of "clarify the 
situation" and "identify whether we move or stay zanata". In case we 
DECIDE(1) or NEED(2) to move, then we can move forward to PLAN it, such 
as "list all possible tools (incl. weblate)", "evaluate/test the tools 
listed", "vote", "approach devel team", etc.

Please let me press this point, the hardest part in entire process, is 
convincing devel team. There were 900 translators of 90+ language teams, 
70 packages with associated developers, 29 books with associated authors 
and web team, all had to agree and take action for the move last time. 
Especially every developers have to setup their repository from scratch 
again.  We lost certain number of translators and developers when moving 
from transifex to zanata.

Therefore, we better gather all the necessary information first 
(rationalizing phase) and develop a plan (planning phase) in written 
form, then implement the plan (action phase) in order to minimize any loss.

my 2 cents

noriko

> 
_______________________________________________
trans mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/[email protected]