Hello, On 06/28/2015 08:04 AM, Ashley Camba Garrido wrote: > Damn, forgot the link. > > https://github.com/ashwoods/deps/blob/master/draft/xxxx-model-internalization.rst
I think the DEP is well-motivated; thanks for picking up this topic. This is a problem that would be useful to have some standardized approach for in core, because of the third-party-models issues you mention in the DEP, and the ugly monkeypatching generally required to implement translatable models. The implementation section of your DEP is obviously very preliminary still. Here's what I think would be required for an accepted DEP in this area (and yes, this will be a lot of work): - Review of the commonly-used third-party packages implementing model translation (e.g. the top three or four from https://www.djangopackages.com/grids/g/model-translation/), comparing their API and implementation strategy, with examples. - Discussion of the range of differing needs around model translation (e.g. some sites have many languages and add languages frequently, others have a small fixed set of languages; these situations lend themselves to preferring different implementations). - Based on the above, a proposed model-translation-backend API that can support these different needs; ideally one which would allow for any of the popular implementation strategies (unless you can make a case that some strategy is strictly inferior in all cases and does not need to be supported.) - A working proof-of-concept implementation of this backend API, with at least two working backends implemented that use different strategies for storing and loading translations. I think you could look at the (accepted in 1.8) template backends DEP (https://github.com/django/deps/blob/master/accepted/0182-multiple-template-engines.rst) for a good example of the level of detail and comprehensiveness you would need to achieve in your DEP before proposing it for acceptance. You should also review the DEP process: https://github.com/django/deps/blob/master/final/0001-dep-process.rst#pre-proposal I think your idea is a good DEP candidate, which means you've completed the first step (pre-proposal). One of the next steps will be to find a core developer who is willing to fill the Shepherd role (primary reviewer). I will consider whether I could do this, but I'm not sure. Good luck, and thanks for the proposal! Carl -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/5596CC61.101%40oddbird.net. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
