Closed Bug 1159432 Opened 10 years ago Closed 10 years ago

Cleanup projects on localize.mozilla.org/pl

Categories

(Mozilla Localizations :: pl / Polish, defect)

Product:
Mozilla Localizations
Component:
pl / Polish
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: stef, Unassigned)

References

(
URL
)

Details

Please remove projects that we do not translate (empty Last Activity column or Need Translation column equal to Total) via Verbatim: Add-ons Find My Device Firefox Marketplace Firefox Marketplace Communication Dashboard Firefox Marketplace Front End Firefox Marketplace Light (DO NOT TRANSLATE) Firefox Marketplace Payment Processor Firefox Marketplace Payments Front End Firefox Marketplace Stats Master Firefox OS and Social API Directory Also, please do not add any new projects to localize.mozilla.org/pl without explicit request from Aviary.pl team.
Adding Pike (CC), who probably knows better how we handle such requests. My view is as follows. 1. Adding projects to Verbatim only on explicit request from community is currently not possible. Whenever new project comes up, we enable it for all requested locales and Verbatim picks all of them. 2. You team can decided, whether it wants to use Verbatim or any other tool for localization, but it's only Verbatim (and Pontoon) where we have permission defined for localizers to work with GitHub repositories. Which is why all projects should remain enabled in Verbatim, even if just for the sake of uploading translations and commiting to repositories. 3. Working directly with -l10n repositories via pull requests breaks our permission system, which is just another reason why developers (who can merge them) mostly don't pay attention to PRs. 4. Note that not having projects exposed for your locale in tools like Verbatim and Pontoon means less exposure to new contributors and higher barrier to entry.
Blocks: 1159436
(In reply to Matjaz Horvat [:mathjazz] from comment #1) > 1. Adding projects to Verbatim only on explicit request from community is > currently not possible. Whenever new project comes up, we enable it for all > requested locales and Verbatim picks all of them. Then make it possible. Removing projects right after addition could be acceptable workaround. > 2. You team can decided, whether it wants to use Verbatim or any other tool > for localization, but it's only Verbatim (and Pontoon) where we have > permission defined for localizers to work with GitHub repositories. Which is > why all projects should remain enabled in Verbatim, even if just for the > sake of uploading translations and commiting to repositories. Then fix the permission system since it is clearly broken and shouldn't be used that way in a first place. It should be possible to contribute to all projects with via vcs. > 3. Working directly with -l10n repositories via pull requests breaks our > permission system, which is just another reason why developers (who can > merge them) mostly don't pay attention to PRs. It is not about working directly with l10n repositories via pull requests and if that breaks some permission system then it is clearly broken anyway. > 4. Note that not having projects exposed for your locale in tools like > Verbatim and Pontoon means less exposure to new contributors and higher > barrier to entry. Right now, rather opposite.
Generally speaking, there are a lot of deficiencies in the l10n tools and processes at mozilla. Most of those impact a variety of teams, many of them keep new people from contributing. Stef, the problems you face aren't raised by anybody else. Thus it's not a good investment of our time to try to change the localization infrastructure for you only. I'd love to have infrastructure that's collaborative to the extent that we can let you work like you want to, but realistically, that's years out. Until then, I'm afraid you'll need to find peace with what we can offer. It's going to be easier for you, and it's going to be easier for us, and eventually allow you to become a more impactful member of the mozilla community. Regarding the status of the actual projects here, I'm sadly lightyears away from understanding their impact myself, so I can't really comment on that. (PS: feedback we got from the nordic meetup was that we should have status pages that explain that, and now I agree even more)
Hi Stefan, I want to address the projects you listed above. - Master Firefox OS is tied to FFOS launches. It used to be done through a text document and the site was hosted externally. It was not until two months ago that the site was migrated to internal hosting and content is now stored in Verbatim/github as well as Amara. It is version specific but all versions for a particular locale is stored in one big file. This allows repeating strings to be reused. Polish should be available in 1.1 and 2.0: https://l10n.masterfirefoxos.com/pl/1-1/ or https://l10n.masterfirefoxos.com/pl/2-0/. The frequency of site visits drops significantly after the phone is launched in the market. - Marketplace: *Firefox Marketplace Front End* *Firefox Marketplace Payments Front End* Firefox Marketplace Firefox Marketplace Communication Dashboard Firefox Marketplace Light (DO NOT TRANSLATE - this was created for a few locales) Firefox Marketplace Payment Processor Firefox Marketplace Stat Marketplace is not version specific or platform specific. It is available on desktop and FFOS. In fact, MP is one of the basic features for the FFOS. Removing it means it will be available in English only for end users. There is no string freeze and the product evolves over time with updates every so often. If the resource is tight, the community can focus on the two components marked with ** above. These two components are end user facing, not for developers. I would advice keeping these two up to date on a monthly basis. The dashboard shows Polish is in relatively good standing compared to other locales: https://l10n.mozilla-community.org/~flod/webstatus/mpstats/. Peiying
I'm just trying reorganize Polish team after I realized I was one of last active members, being told that it is better not to abandon projects and that we should be careful accepting translations (to prevent "crap"). I was searching for possible contributors and ways to attract them but found localize.mozilla.org… I don't feel like I'm asking about something new, just keep offering direct access to vcs please (hg.mozilla.org and svn.mozilla.org so far), stop forking l10n community and recreating whole ecosystem - right now, Verbatim hurts Polish localization team. On the other hand, if there is an requirement to use Verbatim to localize Mozilla projects then I must have missed discussion or announcement about this - could you please point me to it and something explaining relation between Verbatim and official Mozilla localization team? (and resolve this bug accordingly).
No longer blocks: 1159436
Blocks: 1159436
(In reply to Stefan Plewako [:stef] from comment #0) > Please remove projects that we do not translate (empty Last Activity column > or Need Translation column equal to Total) via Verbatim: > > Add-ons > Find My Device > Firefox Marketplace > Firefox Marketplace Communication Dashboard > Firefox Marketplace Front End > Firefox Marketplace Light (DO NOT TRANSLATE) > Firefox Marketplace Payment Processor > Firefox Marketplace Payments Front End > Firefox Marketplace Stats > Master Firefox OS and Social API Directory Marketplace Marketplace Commbadge Marketplace Fireplace Marketplace Spartacus Marketplace Stats Marketplace Zippy and translate elsewhere: Firefox Accounts Firefox Accounts Payments Firefox Hello
Stefan, Does that look OK now? https://localize.mozilla.org/pl/ I removed all projects but Master Firefox OS, which has a lot of suggestions. Are you sure you want to remove them?
(In reply to Matjaz Horvat [:mathjazz] from comment #7) > Does that look OK now? > https://localize.mozilla.org/pl/ Wonderful, thank you! > I removed all projects but Master Firefox OS, which has a lot of > suggestions. Are you sure you want to remove them? That is exactly the one of the reasons to remove unmaintained projects from Verbatim. :( I didn't know about them, so I tried to log in to Verbatim (using my moz ldap creditainlais) but got: Server Error An error has occurred. Thank you for your patience. Unknown password hashing algorithm 'LDAP_yCMxHyEXNLBnTTadXsEW86YXkr2QA6yG'. Did you specify it in the PASSWORD_HASHERS setting? If you need assistance, you may refer to this error as 9626312e81104c209212489151326961$36cc62b8ccbe00ed56ea6446dce1a834. I will port suggestions by hand to github pr and update this bug when ready, thx.
Oh that server error... Since you no longer want to use Verbatim, I think the easiest fix is to create a new account and I'll give you permission once it's created.
(In reply to Matjaz Horvat [:mathjazz] from comment #7) > I removed all projects but Master Firefox OS, which has a lot of > suggestions. Are you sure you want to remove them? I don't know if should see them on https://localize.mozilla.org/pl/masterfirefoxos/translate.html#filter=suggestions if not logged but if they are in https://github.com/mozilla/masterfirefoxos-l10n/blob/master/pl/LC_MESSAGES/django.po (those marked as fuzzy?) then Master Firefox OS could be removed from Verbatim.
I'm stupid. There are 0 suggestions for Master Firefox OS. Those were fuzzy strings. Removed.
Thank you! I don't see other unmaintained projects on localize.mozilla.org/pl and if new projects will appear I will fill follow-up bug.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.