Good questions, I'll try to address them: There will never be a dependence on the Launchpad infrastructure, no OFBiz source code is stored or maintained outside ASF boundaries and only current committers can commit changes to OFBiz.
Launchpad (there are alternatives too...) is only used for supporting the translation process. With the patch we've provided you can export the labels to a Gettext format and uploaded them to Launchpad periodically. After translation the (.po) files containing the translated labels can be download from Launchpad and merged back into OFBiz. I might repeating myself but the main goal to set up an environment like Launchpad is to separate the translation process from software development and provide a place where it's easy to collaborate on OFBiz translations and provide OFBiz in as many languages as possible. Also non-committers could join these translation projects. Another benefit is that developers developers and translators don't get in the way of each other and cause merge conflicts like the situation is today. There's still a lot to sort out an therefore my only request right now is to set up a test for a limited time to see if this could work for OFBiz. -Jeroen On Mon, Jan 19, 2009 at 10:57 PM, David E Jones <[email protected]> wrote: > > I don't want to discourage looking into this, but if I understand right this > proposal would result in the main source of the localized labels being > Launchpad. This means there is a place outside of SVN where the source > artifacts live, and that is a problem. It also means infrastructure the > project depends on that is outside of the ASF infra. Part of the reason that > is not allowed is because it becomes a liability being outside of ASF > control, and extra effort to manage since all committers will need access to > it. And what about non-committers, would they be allowed access to it? The > ASF policy answer for anything regarding source is no. > > -David > > > On Jan 19, 2009, at 6:16 AM, Jacques Le Roux wrote: > >> Yes sure, sounds like a good approach >> >> Jacques >> >> From: "Jeroen van der Wal" <[email protected]> >>> >>> I totally agree on having the community the ability to speak out. But >>> before setting a vote I would like to set up a Launchpad project so >>> the community can experience how translating OFBiz could work. We >>> could open the project for evaluation for a limited time and have the >>> project removed if the community declines the concept. >>> -Jeroen >>> On Sun, Jan 18, 2009 at 12:37 PM, Jacques Le Roux >>> <[email protected]> wrote: >>>> >>>> This should be a community decision. I propose to set a vote for it. Of >>>> course only binding votes will have an effect in case no consensus >>>> emerges. >>>> >>>> Jacques >>>> >>>> From: "Jeroen van der Wal" <[email protected]> >>>>> >>>>> We've extended the code which was contributed to Jira issue >>>>> https://issues.apache.org/jira/browse/OFBIZ-2008 and think we now have >>>>> the perfect solution for managing OFBiz translations. It uses >>>>> Launchpad https://translations.launchpad.net/ to host the >>>>> translations. The good thing about Launchpad is that it free and it >>>>> doesn't require us to set up and manage any infrastructure. With >>>>> Launchpad we can trivially avoid the legwork involved in making OFBiz >>>>> available in as many languages as possible. >>>>> >>>>> The solution requires the following steps: >>>>> 1. Export the label files (.xml) to a Gettext template file (.pot) and >>>>> for each language a translation file (.po); >>>>> 2. Upload the files to the OFbiz translation project on Launchpad; >>>>> 3. Have the community (also non-technical people) add, modify and >>>>> comment translations through a web-interface; >>>>> 4. Download language files (.po) from Launchpad >>>>> 5. Import and merge translations into OFBiz label files. >>>>> >>>>> Our patch handles step 1 and 5. When new labels are added to OFBiz >>>>> only the template files has to be uploaded to Launchpad and will be >>>>> made available to the communities to be translated. >>>>> >>>>> Now the formal part: We tried setting up a project on Launchpad but >>>>> were contacted by the Launchpad admin to ask approval of the "project >>>>> author" to set up the translation project. The reason for this is to >>>>> prevent angry project authors and dead translation projects. More >>>>> about the Launchpad translation policy can be found here >>>>> https://help.launchpad.net/TranslationsImportPolicy >>>>> >>>>> After the project author (David?) has given approval we will set up >>>>> the Launchpad translation project and hopefully bring translations to >>>>> a higher level. >>>>> >>>>> Thanks, >>>>> >>>>> Jeroen van der Wal >>>>> >>>> >>>> >>> > >
