Hi Maciej, That would work too. I'll admit, part of me liked the 'one project per domain name' model, but I see what you are saying and agree we probably don't want to propagate too many projects in Transifex. As I understand it now, the rule would be:
- translations for the docs app in the repo go to the *django-docs* project in Transifex - everything else goes to the *djangoproject.com <http://djangoproject.com> *project, optionally to separate resources for each app if that logically or practically makes more sense (which in one case at the moment would also be for a separate domain name, dashboard.djangoproject.com) Does that sound right? And are there any apps (besides 'dashboard') that folks feel strongly should be given their own resource in Transifex right now? They can always be moved later, too, so we don't need to get it perfect. I'll wait a couple days in case of any other feedback, otherwise my plan will be to: - keep the *dashboard/locale/* directory as-is BUT direct it to its own resource inside the *djangoproject.com <http://djangoproject.com>* project (this way, if we ever change our minds, it will be easier to move it back to its own project, too) - rename *www.djangoproject.com <http://www.djangoproject.com>* back to *djangoproject.com <http://djangoproject.com>* Looking forward to any more feedback, and thanks again for working through this with me. Cheers, Tobias On Tue, Feb 19, 2019 at 4:00 AM Maciek Olko <maciej.o...@gmail.com> wrote: > Hi Tobias, > > Wouldn't we want to put dashboard strings as a resource in > djangoproject.com to keep things simple? (In my previous mail I meant > domain philosophically, like in "domain-driven design", not necessarily an > Internet domain. I'm sorry for not being precise.) > > Thank you for your work, I keep translating to Polish :) > > Cheers, > Maciej > > wt., 19.02.2019, 02:45 użytkownik Tobias McNulty <tob...@caktusgroup.com> > napisał: > >> Hi everyone, >> >> The re-org is complete and the translations can now be found in their >> respective places: >> >> - dashboard.djangoproject.com >> <https://www.transifex.com/django/dashboard-djangoproject-com/dashboard/> >> - docs.djangoproject.com (website strings) >> <https://www.transifex.com/django/django-docs/website-strings/> >> - www.djangoproject.com >> <https://www.transifex.com/django/www-djangoproject-com/dashboard/> (in >> case you had this one up in a browser already, note that I changed the >> slug >> to match the others, so it is now "www-djangoproject-com") >> >> Please feel free to continue translation of these projects/resources, and >> thank you very much for all your help. It is worth noting that there is one >> particular issue in GitHub to localize the fundraising app >> <https://github.com/django/djangoproject.com/issues/377>, however, >> someone will need to add some strings to the code itself before this can be >> completed. >> >> In case it's useful to anyone, I had some fun with Bash to get the >> already-completed translations to their new homes, hopefully safely (or if >> there are problems you can tell me what I did wrong :): >> https://gist.github.com/tobiasmcnulty/732e014bc140be504efd1afb81e217b4 >> >> Finally, I am working on updating the PR >> <https://github.com/django/djangoproject.com/pull/866> for these changes >> and will be grateful for any feedback. >> >> Thanks again, >> Tobias >> >> >> On Mon, Feb 18, 2019 at 6:02 PM Tobias McNulty <tob...@caktusgroup.com> >> wrote: >> >>> Hi everyone, >>> >>> You are incredible! We already have dp.com at least partially >>> translated into *10 languages *(one more than when I started writing >>> this email :)! A huge thank you to everyone who has jumped in to help >>> already. >>> >>> I've looked into this a bit more and will be going with Claude's and >>> Maciej's suggestion, namely, to have *one locale directory for each >>> domain name*. This means that in Transifex I will: >>> >>> - rename the new "djangoproject.com" project to " >>> www.djangoproject.com" >>> - add a new project for "dashboard.djangoproject.com" (currently it >>> has only one string, but we might as well set it up to prepare for more) >>> - create a new resource in the "django-docs" project called >>> "website-strings" (open to other name suggestions here) >>> >>> For docs.djangoproject.com and dashboard.djangoproject.com I will push >>> up the translations that have already been made. But if you are actively >>> translating while I make the switch, some translations may be lost. To help >>> mitigate this, I will do my best to timebox the re-org. *If possible, >>> please do not make any new translations for the "djangoproject.com >>> <http://djangoproject.com>" project in Transifex from 1am till 3am UTC on >>> 19 February.* This applies only to the this specific project -- i.e., >>> *translations >>> for other projects including django-docs will be unaffected* -- and >>> I'll post again here once the re-org is complete. >>> >>> Maciej, I looked for your comment but I don't see it -- could you point >>> me in the right direction or let me know what your comment was? :) >>> >>> Many thanks again to everyone for your help and patience while I am >>> working on this. >>> >>> Cheers, >>> Tobia >>> >>> On Mon, Feb 18, 2019 at 1:56 PM Maciek Olko <maciej.o...@gmail.com> >>> wrote: >>> >>>> I am +1 to Option 2, which allows a domain-driven placement, even if >>>> some files are going to have very few messages. >>>> >>>> PS I left some review comments regarding location comments in >>>> translation source files in one of your pull request. >>>> >>>> Great initiative :) >>>> Regards, >>>> Maciej >>>> >>>> pon., 18.02.2019, 16:21 użytkownik Tobias McNulty < >>>> tob...@caktusgroup.com> napisał: >>>> >>>>> Claude, I'm in -- many thanks! >>>>> >>>>> I have a project started here: >>>>> https://www.transifex.com/django/djangoproject-dot-com/ >>>>> >>>>> That said, I have a question about how to best set this up. >>>>> >>>>> djangoproject.com is unique: It houses strings that apply to a number >>>>> of different sites, some of which have a single Django app and others of >>>>> which rely on multiple Django apps. One of those sites (and apps) is >>>>> docs.djangoproject.com, which puts us in the potentially confusing >>>>> spot of having two different projects in Transifex that handle translation >>>>> for what is a single website: https://docs.djangoproject.com. >>>>> >>>>> I was originally leaning towards having a single project-level locale >>>>> directory <https://github.com/django/djangoproject.com/pull/865> to >>>>> handle all the translations for strings in the "djangoproject.com" >>>>> repo ("Option 1"), but having seen how we have Transifex set up, I'm >>>>> wondering if that's a less-than-optimal approach. >>>>> >>>>> *I believe* that we could instead keep one locale directory per app >>>>> <https://github.com/django/djangoproject.com/pull/864> ("Option 2"), >>>>> and then in our Transifex config decide *on a per-app *basis what >>>>> project in Transifex should house the translations. For now, that would >>>>> likely mean that the "docs" app in the dp.com repo would go to >>>>> "django-docs" in transifex (to a "static-website-strings" or similarly >>>>> named resource) and everything else would go to the "djangoproject.com" >>>>> project I set up and linked above, with resources named for the app. >>>>> If/when we get to this point, we could potentially split off ' >>>>> dashboard.djangoproject.com' to its own Transifex project. This >>>>> option does have the unfortunate consequence of needing to move >>>>> app-specific HTML templates into their respective app directories, but if >>>>> it helps simplify the translation process I think it would be well worth >>>>> the effort (and is mostly done, I think, as part of this proof-of-concept >>>>> PR). >>>>> >>>>> Does Option 2 sound like a reasonable approach? What do others think? >>>>> >>>>> On Mon, Feb 18, 2019 at 9:16 AM Claude Paroz <cla...@2xlibre.net> >>>>> wrote: >>>>> >>>>>> Le 18.02.19 à 01:55, Tobias McNulty a écrit : >>>>>> (...) >>>>>> > Is there someone on this list who could make me an Admin (or >>>>>> Project >>>>>> > Coordinator for such a project) in our Transifex account? My >>>>>> username is >>>>>> > tobias_dsf. >>>>>> >>>>>> Done. Thanks for pushing this forward! >>>>>> >>>>>> Claude >>>>>> -- >>>>>> www.2xlibre.net >>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "Django internationalization and localization" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to django-i18n+unsubscr...@googlegroups.com. >>>>>> To post to this group, send email to django-i18n@googlegroups.com. >>>>>> Visit this group at https://groups.google.com/group/django-i18n. >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Django internationalization and localization" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to django-i18n+unsubscr...@googlegroups.com. >>>>> To post to this group, send email to django-i18n@googlegroups.com. >>>>> Visit this group at https://groups.google.com/group/django-i18n. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Django internationalization and localization" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to django-i18n+unsubscr...@googlegroups.com. >>>> To post to this group, send email to django-i18n@googlegroups.com. >>>> Visit this group at https://groups.google.com/group/django-i18n. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Django internationalization and localization" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-i18n+unsubscr...@googlegroups.com. >> To post to this group, send email to django-i18n@googlegroups.com. >> Visit this group at https://groups.google.com/group/django-i18n. >> For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to the Google Groups > "Django internationalization and localization" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-i18n+unsubscr...@googlegroups.com. > To post to this group, send email to django-i18n@googlegroups.com. > Visit this group at https://groups.google.com/group/django-i18n. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django internationalization and localization" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-i18n+unsubscr...@googlegroups.com. To post to this group, send email to django-i18n@googlegroups.com. Visit this group at https://groups.google.com/group/django-i18n. For more options, visit https://groups.google.com/d/optout.
