Le 24/10/2016 à 18:13, Fabio Alessandro Locati a écrit :
Hi Jean-Baptiste,
This is true for the generic Open Source world, but is not true for
Fedora (nor any other distro).
If you want to create a package for Fedora you MUST use the pkgs.fpo git
(soon it will be pagure). I think this is right and needed as a project.
Best,
Fale
I hope Fedora is no fully part the « Open Source world », I'm not sure
to understand this phrase.
pkgs.fpo is just the place to keep the source files (mainly spec and
patches if I understand it correctly).
Let's imagine you plug Zanata on it without talking with the project
about it, it means local fork.
And it sound incompatible with our values
https://fedoraproject.org/wiki/Foundations
Now, let's talk about Zanata. I'll write a full article about it so
people can understand.
What it is good for :
* technical interface (it can eat and produce many files, even if not
really connected with project source code management tool)
* translation interface (it's modern enough, translation memory is good)
What are the downside:
* team management (who did what, where, when, discussion)
Well, we are in Infrastructure list, let's have a game by making a
parallel with git.
In this role play:
* the project maintainer of a git project is the translation coordinator
(which I am for french language, if someone don't know and read this),
* each file is a fedora package.
You're a project maintainer:
* files arrives and leaves without you knowing about it,
* files are edited without you knowing about it (you just know last edit),
* you have only in-file research and can only have diff per string and
not globally to the file,
* to know what the team did, you have to go in each team member page, it
will tell you for the two last month which files were edited by the
user, nothing else,
* you can't discuss with people in another way than per string.
Would you really like to promote this tool as-is for this use-case?
Zanata works fine in some use-cases. I say it's not working well for the
one I have. And I am convince after many discussion the use-case I have
for the french translation team is the same for most/every Fedora
translation teams.
We can always argue a small team can do well without this features. Or
some team do not care about quality control/team review, etc.
But without the tools to help growing and being efficient, we can't tell
we're gonna be successful.
To respond Alex comment: I'm not against Zanata, I'm against the idea it
can do everything and is perfectly fitted for wide platform translation.
Talking about Fedora integration and "multiple softwares/platform makes
it harderd for new contributor". Let's have another case study :
the Fedora L10N newcomer have to create FAS account, apply for cvsl10n
FAS group, register in Zanata, register to trans mailing list and
introduce himself, register to local mailing list and introduce himself.
By change, he use his fasaccount@xxxxxxxxxxxxxxxxx and mailing list
registration doesn't work, or don't do things in the way we expect... I
don't even speak about local team rules/habits.
--
Jean-Baptiste Holcroft
_______________________________________________
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
