Drupal 6 upgrade

I think, after version ~D6.5 the Gues can think about it. :)

brmassa: I would not suggest you working on a Drupal 6 port yet. There are still heavy UI changes coming to the l10n_server and our dependent module, organic groups is not yet available for Drupal 6. From the OG project page:

OG will begin porting to Drupal6 as soon as Views enters into beta phase.

Technically, OG is not a requirement for l10n_server, but for any serious translation site with more then one languages (ie. the site we are working to set up on drupal.org) it is essential. Since l10n_server is a huge (well not in the views sense, but still) codebase already, so maintaining two versions, one for D5 and the other for D6 is not reasonable IMHO.

Also, is Views 2 completely node independent, so we can do listing of stuff which are not in any connection to nodes?

brmassa: As I said, we are going to have some major UI changes soon. I'd envision it would be much more interesting to try to replicate that UI with Views 2, once we have that committed.

Well, not abandoned. I managed to get the project module patch in place recently, and now pinging Young Hahn hard to work on the UI issues. Feel free to help out there, if you'd like to see this project progress. As soon as we have the UI patch in and organic groups is ready for Drupal 6, we can think about porting this to Drupal 6. I am not sure our focus should be porting first and then installing on drupal.org though (we were waiting long enough for contributions to hit the stage). What do you think?

I strongly think we should work on the new UI first, since it is far superior to the current lame UI. Reproducing the current lame UI with views is work we need to throw out anyway, so you'd better try and work with the new UI. I might as well commit the new UI so that people would finally work on fixing the subtle bugs of it.

Any news about the porting of the module to drupal 6? Thanks!

As far as I see, Organic Groups (and its dependency Views) is not yet close to being ready for Drupal 6. I'd love to use improvements in the Drupal 6 version of the translation template extractor for l10n_server however, so I am hopeful OG and Views will be out sooner then later. Views is still a moving target as its API breaking changes showed recently.

¿? I'm using Organic Groups with no problems (except for the themes and languages, but that can be hacked) What do you mean with "not close to being ready"?

Views 2 has changed, but as far as I tested, both Organic Groups and Views work fairly stable in Drupal6. Does anyone has any plans or dates for the port in mind? Massa told about posting the code around July, did he manage to do it?

As Massa told at first, I think this module could help a lot for spreading Drupal 6. Thanks for the hard work!

I did not see results of this porting code. The UI changes went ahead, and now we have a much better UI for Drupal 5. It should be possible to reproduce with Views 2 theming. Two notes:

1. I don't see how would this module's Drupal 6 port help spreading Drupal 6. The Drupal 5 module can fully parse and translate Drupal 6 (and almost even Drupal 7) modules. How would porting this module help spreading Drupal 6?

2. The drupal.org redesign includes putting together drupal.org project functionality under the roof of project.drupal.org. The translation server is going to live there. At this point project module is Drupal 5 software. We will most probably live on the same Drupal instance, so will move or stay with project module's base Drupal version. If project is not updated by that time, we could end up with a requirement to actively maintain a Drupal 5 version of this module for drupal.org. It does not seem like there are resources for active maintenance of a completely different Drupal 6 port and a Drupal 5 version (existing patches and issues are not looked at by active contributors in the issue queue even). At the same time, I would hate to have this module as a bottleneck on project.drupal.org for a Drupal 6 upgrade, so I'll direct project module maintainers here to provide some input.

Went ahead and asked the project module maintainers:

Hey,

You get this mail because you are either listed as a project module
maintainer or you are aclight :). The Localization Server
(l10n_server) project, which is used by many translation teams to
manage translation of Drupal projects to different languages is
planned to be deployed on Drupal.org (for an awful long time now).
This module skips CVS altogether for translators, so they can
contribute much simpler, use tailor made remote clients, share
translations among branches of modules and cross-modules, etc (which
are all not possible with CVS).

This module was planned to be set up on translate.drupal.org or
something along these lines, but the drupal.org redesign calls for
project.drupal.org to be set up with this functionality with the
project module and the l10n_server functionality "integrated" on one
site. So at this point, it seems pointless to set up l10n_server
somewhere else and then take time to merge the two sites again. This
opens possibilities to integrate on the same database, such as looking
up projects and releases on the same db, which is great, since it
leads to best performance. On the other hand, it also requires the two
modules to work on the same base Drupal version (5 vs 6 at this
point).

I'd love to have some discussion on how do we approach the setup, what
should I look at/work on to make this as smooth as possible. I'd like
to get this server out on drupal.org to the public as soon as
possible, since otherwise people will not enjoy the great sides of
this solution, and in some cases will look for other ways without
considering this way. Management of a server for all translation teams
one-by-one is a huge human and machine resource waste (they all need
to set it up, download and parse releases, etc).

I'd say the most important question is whether I should run and port
the module to Drupal 6 (http://drupal.org/node/247814), since this
module would hold back setting up project.drupal.org on Drupal 6, or I
should comfortably improve on the existing (and only) Drupal 5 branch.

Thanks for your input,
Gábor

why am i not subscribed to this? :)

I've been working all day on this, and did a straight port to Drupal 6. It works with potx 6.x-2.x and the RC of OG (which does not require Views, yay :). I'll post that later today, once some remaining l10n_drupalorg issues are straightened out and then we will see what can be done towards better views integration.

Tested lots of the operations being done on the server. Obviously not all, but this patch looks like a quite decent update for all the modules included in the package. Tested with potx-6.x-2.x (the module will not work with the 1.x branch), and the organic groups release candidate. Parsing, releases, errors, the filtering and translations UI, summary screens, groups, permissions, etc. still work.

Full commit message available at http://drupal.org/cvs?commit=146436 (yes, I've also did a follow up commit to move all po directories to translations). There are no string changes only one string addition, so did not regenerate the .po files yet.

Will roll a new alpha release on both Drupal 5 and Drupal 6 for you to test. I'd love to make the Drupal 6 version the main supported platform and make several great changes. Better utilization of the potx-2.x branch error messages is on the plans, as well as better hook_requirements checking, more features for l10n_localpacks, a project module integrator, Views module based lists, and so on. I'd love to see other issues suggesting such improvements.

5.x is no longer supported?
Very sad :(
I want to update the http://drupaler.ru, but I can not do it (Dupal 6.x has a bug with locale): #325074: Hard error with locale (#282178: Language negotiation overhaul)

I will try use patch the kernel: http://drupal.org/node/222401#comment-844115

The Drupal 5 version of this module is not supported anymore as posted on the project page.