Add Turkish language to l.d.o

What's you relation to http://l10n.drupaltr.org/ and/or http://drupal.org/project/tr ?

Hi,
I am one of the tiny committers of http://l10n.drupaltr.org/
The site admin erdemkose (http://drupal.org/user/48382) is doing his military service now.
How can we proceed?

We'd need to turn off contributions on http://l10n.drupaltr.org/ to signal that we have a single definitive source at localize.drupal.org. If we keep contributions being turned on there, translators will have a hard time merging translations as well as users will have a hard time figuring out where to get the latest translations from. That is why I'm trying to have a clean picture of how previous work is integrated and then discontinued. If we do not integrate or do not discontinue previous work, then we merely open a new parallel channel, which is not going to be good for anybody.

Hi Gábor,
How can we proceed then?
We can announce that all translation efforts will be done at localize.drupal.org to the turkish community using drupa on various forums and lists.
Do we need strict measures to stop activity on http://l10n.drupaltr.org ?

As I've said " We'd need to turn off contributions on http://l10n.drupaltr.org/ "

Hi again,
As I've said we do not have administrative control on the site, so we cannot turn off anything.
As far as I understand, you cannot do anything either.
Can you please tell us the best way to translate drupal 7 in turkish other than localize.drupal.org?

What Gábor means is that if the contributions are still enabled on http://l10n.drupaltr.org/, users will not understand where they are supposed to add contributions, while we want to have a single server used for the translations; differently, the purpose of having a central localization server would be vanished.

Is erdemkose the only person to have administrative access to that server? I'd expect that someone going to military service tries to find backup personnel.

I still have internet access and I am ready to do anything necessary to move our localization to l.d.o. Is it enough to replace our site with a message to forward every visitor to l.d.o?

Hopefully erdemkose is online.
We are looking forward your instructions.

@erdemkose: we'd need the translations from the existing server exported as .po files (if not done already), so that the team can migrate them, and the previous contributions are built on instead of reset.

I have exported the translations for each project from l10n.drupaltr.org by selecting "All" releases and "All in one file" format.

Created team at http://localize.drupal.org/languages/tr

Please expect that there might be bumps in the service. You are among the beta-tester of this live instance. Thanks for helping out and please report issues as you find them! Your team members can now join and help import existing translations and work on more translations.

Also note that I've set this up so that it uses a controlled model (that group admins moderate translations). If you'd rather work in an open model (that everyone can directly submit translations), that is up to you and you can edit your group node to reconfigure anytime.

Consequently, I've also removed the team's listing from the standalone servers at http://drupal.org/project/l10n_server

Welcome on board!