Split l10n_server and l10n_community in two different packages.
Jose Reyero - October 4, 2009 - 14:14
| Project: | Localization server |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Description
As I see this issue queue growing, I am concerned this starts getting too big to handle it easily. Also there are two different sets of modules in this package that provide completely different features.
- The localization server, connectors, packager, etc..
- The group enabled translation UI, permissions, etc..
I think it makes sense to split them in two projects: l10n_server and l10n_community. The second should require the first and rely on its API of course, but maybe at some point you can do a set up on which you just need the server part enabled, then have a different UI, not team enabled, or not UI at all just running with l10n_client to translate local modules and repackage.
Whatever, even if they're always used together, I think it will help the development process having these two packages separated.