Move all my non-Spanish translations to someone else

Bug #280673 reported by Carlos Perelló Marín
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

Due to my old work as a Launchpad developer, Launchpad has a lot of translations tagged as coming from me. However, I'm not able to speak so many languages ;-).

Right now, I'm not able to use Launchpad for translations because I need to decide whether I accept using BSD license or not for my translations, and there are a lot of translations that were not done by me but that will be affected by the decision I choose.

My suggestion is to move the owner of those translations to whatever default is used now for automatic imports when Launchpad cannot find who should get credit. This change should affect all non Spanish translations, and any Spanish translation for Firefox, OpenOffice and KDE, given that I didn't translate for those projects ever.

As a hint to implement this change, you will need a script to do it in batches, because the number of rows to update is quite big. That's the reason I didn't change this before leaving, I didn't have time to prepara, validate and get it executed before my leave.

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

I forgot the magic words...

Pretty please.....

:-P

Revision history for this message
Данило Шеган (danilo) wrote :

We'll think about it. We feel it's nicer if people can blame you for the problems that come up in such translations.

Changed in rosetta:
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Carlos Perelló Marín (carlos) wrote :

Hello?

It's quite "boring" having to logout to be able to search for translation problems... really.

I have four options:

- Keep logging out and dream on the day I will be able to use Launchpad translations again.
- Change a huge amount of translations, which I don't own, to BSD license (and see whether your script to handle that task scales well :-P)
- Remove a huge amount of translations from Launchpad (which I guess will prevent me to do any future contribution).
- Go to Serbia and get Danilo fixing this with the pressure of crashing his car... (at some point I will go again, but I hope not for this :-P).

But I prefer if you add the fifth option... fix the database data!!!

Thanks for listen, byebye.

/me goes to a corner and starts crying...

Revision history for this message
Данило Шеган (danilo) wrote :

Carlos, we'll do this but as you probably can guess, we are just very busy with many other things.

Since I don't really understand what problems do you have because of this, I am assuming that this is all just a misunderstanding. I thought this was mainly about credit, but reading your last message it seems it's not.

We are not changing any translations in our database depending on your choices of the license any more (that's why we had a time limit on people to make their choice): anything that is 'imported' (well, origin == RosettaTranslationOrigin.SCM :) is under upstream license, and anything which is not 'imported' is under BSD. We also won't be removing any translations for people who decide to change their mind suddenly: everything that's in the DB is assumed to have gotten in either as imported or BSD licensed. If some people feel particularly annoyed because they missed the deadline, we'd be happy to consider removing their translations on a case-by-case basis.

So, you can freely accept/reject BSD license (but if you reject it, you won't be able to translate with LP Translations until you accept it again), and no data will be destroyed.

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

Hmm, I didn't know the process was limited on time.

Then, this is still pending, but not as high priority as I thought initially, given that it's just a matter of credit, as you just pointed.

Thanks for the clarification, your car is safe now :-D

Curtis Hovey (sinzui)
Changed in launchpad:
importance: Medium → Low
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.