Open Stack

Thanks to great help by Akihiro, the translation spec [1] has
implemented the first steps (1-4) and all the python projects as well as
django projects with one module use this setup just fine!

Now it's time to decide how to continue with repositories that have more
than one module.

We currently only translate a single repository with more than one
module - horizon - and special case it. We can continue doing it this way.

But there're a few more repositories that want translations in the
future and have multiple modules, so let's discuss how to continue - or
whether to wait until those are ready.

Looking at repositories, here's a list in the form "repository =>
modules" that Akihiro compiled:
* horizon => horizon, openstack_dashboard (both django modules)
* vitrage-dashboard => vitrageentities, vitragealarms,
vitragedashboard (all django modules)

* astara-horizon : astara_horizon (namespace package),
astara_horizon.astara_openstack_dashboard (django)
* networking-sfc : networking_sfc (python), sfc_dashboard (django)

Akihiro has proposed one change [2] that can be used for horizon and
also vitrage-dashboard. Or we ask vitrage-dashboard to use a single module.

The other two repositories have both a python and a django repository
which needs special casing, like step 6 of the spec [1]. But those are
not asking yet for translation.

What do you suggest to do with these options:

1) Keep status quo for now?
2) Merge [2] to simplify scripts for horizon and vitrage
3) Implement step 6 - even if no repo currently uses it
4) Anything else?

Andreas


[1]
http://specs.openstack.org/openstack-infra/infra-specs/specs/translation_setup.html
[2] https://review.openstack.org/#/c/280711/

-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
       HRB 21284 (AG Nürnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126