Rosetta should not assign Karma when importing.

Bug #35631 reported by Carlos Perelló Marín
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Carlos Perelló Marín

Bug Description

Rosetta is still giving karma to people that translated imported translations instead of doing it only when they use Rosetta to do translations. Because of this, Dapper imports are increasing a lot of people's karma -- even for people that don't even have an active Launchpad account.

Clarifying, there are 4 ways that new translations are added to Rosetta:

  1. end-user translates using the web application
  2. end-user downloads pofile, translates and uploads
  3. maintainer uploads tarball with template and translations
  4. buildd assembly generates a tarball with template and translations

Only 1 and 2 (which require the end-user has a valid Launchpad account) should assign Karma.

Changed in rosetta:
assignee: nobody → carlos
status: Unconfirmed → Confirmed
Revision history for this message
Stuart Bishop (stub) wrote :

It might be worth finally fixing the database permissions of the poimport database user, minimizing the rights it gets in the database. In particular, if the poimport user doesn't have rights to insert kara exceptions will be raised whenever it attempts to do so making it obvious where the error is.

Revision history for this message
Carlos Perelló Marín (carlos) wrote :

There are imports from users that should get karma so that solution is not possible, unless we decide to give karma only when you use the web UI to translate.

Changed in rosetta:
status: Confirmed → In Progress
Changed in rosetta:
status: In Progress → Fix Committed
Changed in rosetta:
status: Fix Committed → Fix Released
Christian Reis (kiko)
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.